Académique Documents
Professionnel Documents
Culture Documents
(Version 1)
Version 1
May 2014
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use
and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in
any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S.
and/or international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14
(ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us
in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica
On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and
Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world.
All other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights
reserved.Copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta
Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems
Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All
rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights
reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights
reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved.
Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright ej-
technologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights
reserved. Copyright yWorks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved.
Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All
rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright 2003-2010 Lorenzi Davide, All
rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright
EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All
rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright
Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha,
Inc. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions
of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in
writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software
copyright 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License
Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any
kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California,
Irvine, and Vanderbilt University, Copyright () 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and
redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or
without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 () MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http://www.dom4j.org/ license.html.
The product includes software copyright 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to
terms available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations
regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software copyright 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at
http:// www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are
subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at
http:// www.pcre.org/license.txt.
This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://
www.stlport.org/doc/ license.html, http:// asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://
httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/
license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-
agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html;
http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/
2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://
forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://
www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://
www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/
license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://
www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js;
http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://
protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5-
current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; and https://github.com/lyokato/libgeohash/blob/master/LICENSE.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution
License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License
Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/
licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-
license-1.0) and the Initial Developers Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab.
For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject
to terms of the MIT license.
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460;
8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending.
DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the
implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is
error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and
documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software
Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT
INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT
LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Chapter 2: Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Solution Package Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Import Metadata Changelist into the Repository Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Add Custom Java Cleanse Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Add Custom MDM Hub User Exits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Import Application Components into Informatica Data Director. . . . . . . . . . . . . . . . . . . . . . . . . . 9
Import Data Integration Mappings into the Developer Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Perform Post-Import Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Deploy Composite Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table of Contents i
Trust Value Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Data Cleansing and Standardization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MDM Hub User Exits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Match and Merge of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Hierarchy Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
External Match for TPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Inbound Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Map_DMF_DIM_Landing_Party_DM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Map_IDI_DIM_Landing_Party_DM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Map_Insurance_DIM_Landing_Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Map_Insurance_DIM_Landing_Party_DM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Map_Insurance_DIM_Landing_Party_Role_Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . 27
Map_Insurance_DIM_Landing_Postal_Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Map_PA_DIM_Landing_Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Map_PA_DIM_Landing_Party_DM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Map_PA_DIM_Landing_Party_Role_Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Map_PA_DIM_Landing_Postal_Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Map_TPA_Party_Party_DM_EMI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Outbound Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Decedent Information Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Error and Validation Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Map_Party_DM_EMO_TPA_Party_Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Composite Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Informatica Data Director User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Hierarchy Configuration in Informatica Data Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Subject Area - Person. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Subject Area - Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Subject Area - Auto. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Subject Area - Life. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Subject Area - Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Custom Tasks and Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
ii Table of Contents
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Informatica Resources
The site contains product information, user group information, newsletters, access to the Informatica
customer support case management system (ATLAS), the Informatica How-To Library, the Informatica
Knowledge Base, Informatica Product Documentation, and access to the Informatica user community.
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you
have questions, comments, or ideas about this documentation, contact the Informatica Documentation team
through email at infa_documentation@informatica.com. We will use your feedback to improve our
documentation. Let us know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your
product, navigate to Product Documentation from http://mysupport.informatica.com.
iv
solutions to common problems, compare features and behaviors, and guide you through performing specific
real-world tasks.
Informatica Marketplace
The Informatica Marketplace is a forum where developers and partners can share solutions that augment,
extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions
available on the Marketplace, you can improve your productivity and speed up time to implementation on
your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com.
Informatica Velocity
You can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world
experience of hundreds of data management projects, Informatica Velocity represents the collective
knowledge of our consultants who have worked with organizations from around the world to plan, develop,
deploy, and maintain successful data management solutions. If you have questions, comments, or ideas
about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com.
Online Support requires a user name and password. You can request a user name and password at
http://mysupport.informatica.com.
The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.
Preface v
CHAPTER 1
Insurance companies can use the Solution to extract information about deceased people from source
systems, such as Social Security Administration (SSA) Death Master File (DMF), and load into the MDM Hub.
The Solution uses a Data Integration Service to extract this information. Batch jobs within the MDM Hub
match the incoming records with the records in the MDM Hub. The records that are not merged automatically
are sent to a data steward. After a data steward approves the merge, the MDM Hub publishes records of
deceased people through the outbound mappings and Java Message Service.
The Policy Administration system or any other target system can use the following methods to get records
with updated decedent information:
1
Batch data transfer
The target system uses batch transfer to load the file with updated decedent information into their
database.
When target systems get records with updated decedent information, the insurance company must identify
the beneficiaries of the deceased people and settle all claims.
The following users can use the Soluiton to identify beneficiaries, verify death, and prevent identity fraud:
Governments
To identify deceased people and prevent identity fraud, state governments, local governments, and
security firms can compare the Death Master File with financial, credit, payment, and other applications.
Medical hospitals
Medical hospitals, researchers, and medical treatment programs can use the Death Master File to track
former patients and study subjects.
The following image shows the Informatica components that the Solution uses:
Informatica Administrator
An administrator uses Informatica Administrator to create the Model Repository Service and Data
Integration Service. An administrator might also configure Informatica Developer to connect to the model
repository.
Informatica Developer
Informatica Developer (the Developer tool) connects to the model repository through the Model
Repository Service. An administrator of the MDM Hub uses the Developer tool to import inbound and
outbound mappings and change the mappings as required.
Application Services
The Informatica services access the domain configuration repository to maintain connections and
metadata for the domain.
MDM Hub
The Data Integration Service establishes integration between the different source systems and the MDM
Hub.
Hub Server
The Hub Server is a J2EE application that you must deploy on an application server. The Hub Server
processes data within the Hub Store and integrates the MDM Hub with external applications. The Hub
Server is the run-time component that manages core and common services for the MDM Hub.
Hub Store
The Hub Store stores and consolidates business data for the MDM Hub. The Hub Store consists of the
MDM Hub Master Database and Operational Reference Store.
The following image shows the data flow from source systems to target systems:
The Data Integration Service establishes integration between the different source systems and the MDM Hub.
The following is the high-level process about how the Solution transfers data from source systems to target
systems:
1. When you run the required inbound dataflow script, the inbound mappings extract information about
deceased people from source systems, such as the SSA DMF, and loads it into the MDM Hub.
2. Stage jobs within MDM Hub use cleanse functions and Informatica Address Doctor to clean and
standardize incoming records.
Configuration
This chapter includes the following topics:
Configuration Overview, 6
Prerequisites, 7
Solution Package Components, 7
Import Metadata Changelist into the Repository Manager, 8
Add Custom Java Cleanse Library, 8
Add Custom MDM Hub User Exits, 9
Import Application Components into Informatica Data Director, 9
Import Data Integration Mappings into the Developer Tool, 9
Perform Post-Import Tasks, 10
Deploy Composite Services, 10
Configuration Overview
To configure Unclaimed Life Insurance Data Management Solution, perform the following tasks:
6
Prerequisites
Before you configure Unclaimed Life Insurance Data Management Solution, perform the following tasks:
1. Install and configure Informatica 9.5.0. Create a Data Integration Service and a Model Repository
Service. Configure the Developer tool to connect to the Model Repository.
2. Install Informatica MDM Multidomain Edition 9.7.0.
3. If you have not created an Operational Reference Store (ORS), create an ORS after you install the
database. After you create the ORS, import the seed into the ORS. The seed contains the initial
metadata, such as REPOS tables, and other objects that the MDM Hub requires in the Hub Store.
4. Install Informatica MDM Multidomain Edition Resource Kit 9.7.0.
5. Configure the MDM Hub to use Address Doctor Cleanse Engine.
6. Optionally, configure the MDM Hub to use Informatica ActiveVOS workflow.
Download the Solution from the following URL and extract the files:
https://community.informatica.com/solutions/informatica_unclaimed_life_insurance_data_mgmt
After you extract the files, the top level folder is MDM Solution that contains the following folders:
Custom
The following folders are available inside the Custom folder:
Cleanse Function
Contains the CLEANSE.jar file that you must add to cleanse and standardize data coming from
different source systems.
Web_App
Contains the DIMService.zip file that includes the searchParty and getParty composite services.
Use these services from a target system to search for postal addresses and insurance policies of
parties stored in the MDM Hub.
IDD
Contains the InfaDIMasterHub.zip that you must import through Informatica Data Director. The ZIP file
contains the components to set up the application for a data steward.
Met Export
Contains the DIM_MET_EXPORT_06032014_HF1.change.xml file that you must import to get MDM Hub
metadata. The MDM Hub metadata includes components, such as landing tables, user exits, lookup
tables, staging tables, base objects, and match/merge rules.
Prerequisites 7
Integration
The Mercury DI folder is available inside the Integration folder. The Mercury DI folder contains the
DIM_HF1_03032014.xml file that you must import through the Developer tool to configure the inbound and
outbound data integration mappings. The following folders are available inside the Mercury DI folder:
Sample Files
Contains sample error files, source files, outbound files, and validation files.
Scripts
Contains scripts for the inbound and outbound data flows. You can change these scripts as
required.
8 Chapter 2: Configuration
Add Custom MDM Hub User Exits
The user exits available with Unclaimed Life Insurance Data Management Solution validate incoming records
for add, update, and delete requests.
1. In the Hub Console, under Utilities, click User Object Registry and click Add.
2. Enter a description for the user exit.
3. Browse to find the DIM971.jar file available inside the <InstallDirectory>\MDM Solution\Custom\Hub
User Exit\Siperian folder or the DIMVOS.jar file available inside the <InstallDirectory>\MDM
Solution\Custom\Hub User Exit\ActiveVOS folder. Use DIMVOS.jar if you have integrated ActiveVOS
with Informatica MDM Multidomain Edition.
4. Restart the application server.
1. Start Informatica Data Director Configuration Manager. Use the following URL:
https://hostname:port/bdd/config
2. Click Import Complete IDD Application (ZIP) and browse to find the InfaDIMasterHub.zip file
available inside the <InstallDirectory>\MDM Solution\IDD folder.
3. Under Bind Logical ORS, select the ORS from the list. You must select the ORS that you created when
you installed MDM Multidomain Edition.
4. Click Save.
5. See the validation results and resolve any errors.
1. In the Developer tool, open the inbound data integration mapping objects and specify the path of the
source files.
2. Open the outbound data integration mapping objects and specify the path where you want the mappings
to create the output files.
3. Specify the appropriate database connection properties for the source and target database objects.
4. Save the changes.
5. Test and run the individual mappings and resolve any errors.
6. Use the Developer tool to deploy the DIM_App application to the Data Integration Service. The application
is available in the DIM_HF1_03032014.xml file.
7. Change the scripts for inbound and outbound data workflows as required.
10 Chapter 2: Configuration
CHAPTER 3
Solution Components
This chapter includes the following topics:
Source Systems, 11
MDM Hub Components, 12
Hierarchy Management, 21
External Match for TPA, 22
Inbound Mappings, 22
Outbound Mappings, 34
Composite Services, 35
Informatica Data Director User Interface, 36
Hierarchy Configuration in Informatica Data Director , 36
Custom Tasks and Workflows, 40
Source Systems
Source systems are systems that send decedent information to the MDM Hub.
Unclaimed Life Insurance Data Management Solution (the Solution) integrates with the following source
systems:
Lookup System
System that stores standard lookup values, such as gender, prefix, and title.
SSA System
Social Security Administrator system that sends the Death Master File.
Social Security Administration is a standard system that stores decedent information of people with Social
Security numbers. The other systems are representation of systems that send decedent information to the
MDM Hub. You can integrate other systems that contain decedent information with the Solution.
11
MDM Hub Components
MDM Hub components process incoming records from different source systems and send records with
updated decedent information to the downstream systems.
The following MDM Hub components are included with this solution:
Base objects
Lookup tables
Landing tables
Custom tables
Staging tables
Packages and queries
Trust settings
Data cleansing and standardization
User exits
Match and merge of data
Base Objects
The match and merge job in the MDM Hub updates the relevant base objects to store consolidated data.
The following base objects are available for Unclaimed Life Insurance Data Management Solution:
C_BO_AGRMNT
Stores details about insurance agreements.
C_BO_PRTY_DM
Stores party personal information, such as first name, last name, prefix, death date, and gender.
C_BO_PSTL_ADDR
Stores postal addresses.
C_BR_PRTY_PSTL_ADDR
Stores information about the relationship between party and postal address. In addition, it stores
information about the type of postal address and the usage type of postal address.
C_BR_PRTY_RLE_AGRMNT
Stores information about the relationship between party and agreement. In addition, it stores information
about the role and sub role of a person in an insurance agreement.
Lookup Tables
The MDM Hub processes need party information, such as gender, prefix name, country, and state, to process
data. The lookup base tables store this information.
The following lookup base tables are available for Unclaimed Life Insurance Data Management Solution:
C_BT_AGRMT_TYP
Stores information about the type of insurance agreement.
C_BT_FLG
Stores information about the flag.
C_BT_GNDR
Stores information about the gender.
C_BT_PRFX_NM
Stores information about the prefix name.
C_BT_PRTY_RLE_AGRMNT
Stores information about the role of a person in an insurance agreement.
C_BT_PRTY_SUB_RLE_AGRMNT
Stores information about the sub role of a person in an insurance agreement.
C_BT_PRTY_TYP
Stores information about the type of party.
C_BT_PSTL_ADDR_TYP
Stores information about the type of the postal address.
C_BT_PSTL_ADDR_USG_TYP
Stores information about the usage type of the postal address.
C_BT_PSTL_ADDR_VLDTN_STS
Stores information about the validation status of the postal address.
C_BT_SFX_NM
Stores information about the suffix name.
C_BT_STATE
Stores information about the state.
Landing Tables
Landing tables derive their structure from the base objects. A single landing table stores data from all source
systems for a particular entity. Each landing table has a column Source System that distinguishes between
data from different source systems.
C_L_AGRMNT
Landing table to stores details about insurance agreements from all source systems.
C_L_LKP_ADDR_USG_TYP
Stores information about usage type of the postal address sent from the Lookup source system.
C_L_LKP_ADDR_VLDTN_STS
Stores information about the validation status of the postal address sent from the Lookup source system.
C_L_LKP_AGRMNT_TYP
Stores information about the type of insurance agreement, such as auto, life, or property, sent from the
Lookup source system.
C_L_LKP_FLG
Stores information about the flag sent from the Lookup source system.
C_L_LKP_GNDR
Stores information about the gender sent from the Lookup source system.
C_L_LKP_PRFX_NM
Stores information about the prefix name sent from the Lookup source system.
C_L_LKP_PRTY_RLE_AGRMNT
Stores information about the role of a person in an insurance agreement sent from the Lookup source
system.
C_L_LKP_PRTY_SBRL_AGRMNT
Stores information about the sub role of a person in an insurance agreement sent from the Lookup
source system.
C_L_LKP_PRTY_TYP
Stores information about the party type sent from the Lookup source system.
C_L_LKP_PSTL_ADDR_TYP
Stores information about the address type sent from the Lookup source system.
C_L_LKP_SFX_NM
Stores information about the suffix name sent from the Lookup source system.
C_L_LKP_STATE
Stores information about the state.
C_L_PRTY_DM
Landing table to store party information from all source systems.
C_L_PRTY_PSTL_ADDR
Landing table to store the relationship between party and postal address.
C_L_PRTY_RLE_AGRMNT
Landing table to store the relationship between party and agreement. This table also stores the role and
sub role of a party.
C_L_PSTL_ADDR
Landing table to store postal address from all source systems.
Custom Tables
Custom tables store information about error records, new records, and custom tasks that the MDM Hub
processes create for a data steward.
The following custom tables are available for Unclaimed Life Insurance Data Management Solution:
C_L_CUSTOM_TASK
Stores information about the custom tasks that the MDM Hub processes create for a data steward.
C_L_NEW_RCDS
Stores all records that do not exist in the MDM Hub.
C_L_LST_PBLSHD
Stores information about the batch process names and the date on which the processes published the
file with updated decedent information.
Staging Tables
Staging tables stage data before the MDM Hub processes process the staged data and update the base
object records.
The following staging tables are available for Unclaimed Life Insurance Data Management Solution:
C_S_CM_AGRMNT
Stores the details of insurance agreements sent from the Custom Master source system.
C_S_CM_PRTY_DM
Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the
Custom Master source system.
C_S_CM_PRTY_PSTL_ADDR
Stores information about the type of postal address and the usage type of postal address sent from the
Customer Master source system. In addition, it stores information about the relationship between party
and postal address.
C_S_CM_PRTY_RLE_AGRMNT
Stores information about the role and sub role of a person in an insurance agreement sent from the
Customer Master source system. In addition, it stores information about the relationship between party
and agreement.
C_S_CM_PSTL_ADDR
Stores the postal addresses sent from the Customer Master source system.
C_S_IDI_PRTY_DM
Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the
Internal Decedent Information source system.
C_S_IDI_PRTY_PSTL_ADDR
Stores information about the type of postal address and the usage type of postal address sent from the
Internal Decedent Information source system. In addition, it stores information about the relationship
between party and postal address.
C_S_IDI_PSTL_ADDR
Stores the postal addresses sent from the Internal Decedent Information source system.
C_S_LKP_ADDR_USG_TYP
Stores information about the usage type of postal addresses sent from the Lookup source system.
C_S_LKP_ADDR_VLDTN_STS
Stores information about the validation status of postal addresses sent from the Lookup source system.
C_S_LKP_CNTRY
Stores country code and country description sent from the Lookup source system.
C_S_LKP_FLG
Stores information about the flag sent from the Lookup source system.
C_S_LKP_GNDR
Stores information about the gender sent from the Lookup source system.
C_S_LKP_PRFX_NM
Stores information about the prefix name sent from the Lookup source system.
C_S_LKP_PRTY_RLE_AGRMNT
Stores information about the role of a person in an insurance agreement sent from the Lookup source
system.
C_S_LKP_PRTY_SBRL_AGRMNT
Stores information about the sub role of a person in an insurance agreement sent from the Lookup
source system.
C_S_LKP_PRTY_TYP
Stores information about the party type sent from the Lookup source system.
C_S_LKP_PSTL_ADDR_TYP
Stores information about the type of postal address sent from the Lookup source system.
C_S_LKP_SFX_NM
Stores information about the suffix name sent from the Lookup source system.
C_S_LKP_STATE
Stores information about the state sent from the Lookup source system.
C_S_PA_AGRMNT
Stores the details of insurance agreements sent from the Policy Admin source system.
C_S_PA_PRTY_DM
Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the
Policy Admin source system.
C_S_PA_PRTY_PSTL_ADDR
Stores information about the type of postal address and the usage type of postal address sent from the
Policy Admin source system. In addition, it stores information about the relationship between party and
postal address.
C_S_PA_PRTY_RLE_AGRMNT
Stores information about the role of a person in an insurance agreement sent from the Policy Admin
source system. In addition, it stores information about the relationship between party and agreement.
C_S_PA_PSTL_ADDR
Stores the postal addresses sent from the Policy Admin source system.
Packages
To complete the processing of data, MDM Hub processes need data from different tables. Packages contain
the relevant queries that get the required data for processing.
The MDM Hub processes use the following packages to get data:
Trust for Death Date, Death Indicator, and External Match Indicator
The following table shows the trust setting for death date, death indicator, and external match indicator
attributes:
Customer Master 60 60
Policy Admin 60 60
SSA 90 90
The Decay, Duration, and Graph values for the preceding trusts are 12, Month, and Linear.
Customer Master 90 90
Policy Admin 90 90
SSA 60 60
The Decay, Duration, and Graph values for the preceding trusts are 12, Month, and Linear.
Graph
In the MDM Hub, you can use the Cleanse Function tool to graphically configure a function. Graph
functions have multiple input values and output values.
Cleanse List
A cleanse list is a logical grouping of string functions that the MDM Hub processes run at runtime in a
predefined order. Use cleanse lists to standardize specified string values and to remove extraneous
characters from input strings.
Note: You can view all the cleanse functions in the MDM Hub under Cleanse Functions.
The following Java class implements the MDM Hub user exits:
Records with Change flag as A that create new records must not exist in the MDM Hub. The post
land user exit identifies all such records before staging them and writes these records in the
custom error table C_L_ERR with the published flag as N.
Records with Change flag as D that delete decedent information must exist in the MDM Hub. The
post land user exit identifies the records with change flag as D and validates them as follows:
1. If a record does not exist in the MDM Hub, the user exit inserts the record into the error
table and the is_rjctd flag is set to Y that prevents it from staging.
2. If a record exists and is merged with other records in the MDM Hub, the user exit loads the
record as pending in the MDM Hub and stores it in the C_L_CUSTOM_TASK custom task table.
Records with Change flag as U that update decedent information must exist in the MDM Hub.
The post land user exit identifies the records with change flag as U. If such records do not exist in
the MDM Hub, the user exit stores the records in error table with the published flag as N.
com.infa.solutions.dim.userexit.PostLoadImplementation
If a record comes from a source system other than SSA, the post load user exit inserts the record into
the C_L_NEW_RCDS custom table, which tracks the new records in the current load process. If a record is
an update request and exists in the C_L_CUSTOM_TASK table (as inserted into the current batch group),
the user exit creates a DecedentRollBack task.
com.infa.solutions.dim.userexit.PostMatchImplementation
If a match is run on the MRS_Party ruleset, the post match user exit identifies all the records present in
the C_L_NEW_RCDS table as part of the current batch process and performs the following actions:
If a record comes from a source system other than SSA and IDI without death information and
matches with a record in the base object, an error is reported with a message Add request for an
already deceased Party.
If a record is from the IDI source system and does not match with the records in the base object, an
error is reported with a message Deceased record does not have the party record.
MRS_PARTY_EXTERNAL
MRS_Party (Default)
MRS_Party_IDD
MRS_Account_IDD
MRS_Address (Default)
The MRS_Party_Address (Default) ruleset performs an exact match of party and address data.
Hierarchy Management
A person can have life insurance, auto insurance, or property insurance. A person can also have multiple
postal addresses. For example, a person might have taken life insurance when residing at Address A and
auto insurance when residing at Address B. The relationship between person, insurance policies, and
addresses is available as a hierarchy in Informatica Data Director. The name of the hierarchy that represents
this relationship between different entities is Agreement Hierarchy. A data steward can manage this hierarchy
in Informatica Data Director based on the custom tasks that the MDM processes create.
The following table lists the entity types for this solution:
Entity Object Entity Type Code Entity Type Display Name Description
Hierarchy Management 21
External Match for TPA
MDM Hub External Match utility matches the records from the Third Party Administrator (TPA) system against
the records from SSA DMF and Internal Decedent Information system.
1. Uses inbound mappings to populate the EMI table with the required data.
2. Runs the Match on the MRS_PARTY_EXTERNAL ruleset.
3. Uses outbound mappings to extract the matched records from the EMO table and then publishes a CSV
file.
Inbound Mappings
Inbound mappings populate data into the landing tables from files coming from the different source systems.
Map_DMF_DIM_Landing_Party_DM
This mapping populates the MDM Party landing table with data from the standard fixed length SSA DMF file
provided by the Government.
Operation Insert
SYSTIMESTAMP() LAST_UPDATE_DATE
N/A PRFX_NM
LTRIM(RTRIM(CONCAT(CONCAT( FULL_NM
CONCAT(CONCAT(CONCAT(CON
CAT(RTRIM(FirstName),'
'),RTRIM(MiddleName)),'
'),RTRIM(LastName)),'
'),RTRIM(NameSuffix))))
N/A PRTY_TYP
N/A GNDR_CD
IIF(Flag='D','N','Y') DTH_IND
'SSA' SRC_SYS
IIF(IS_SPACES(Flag),'A',Flag) CHNG_FLG
N/A HUB_STATE_IND
N/A IS_RJCTD
Map_IDI_DIM_Landing_Party_DM
This mapping populates the MDM Party, Postal Address, and Party Postal Address landing tables with data
from the internal decedent information file that comes from Internal Decedent Information (IDI) source
system.
Operation Insert
Inbound Mappings 23
Source Column Expression/Lookup Target Table Name Target Column Name
Name
SYSTIMESTAMP() LAST_UPDATE_DATE
Map_Insurance_DIM_Landing_Agreement
This mapping populates the Agreement landing table with Agreement data that comes from the insurance
solution source system.
Operation Insert
Inbound Mappings 25
Map_Insurance_DIM_Landing_Party_DM
This mapping populates the MDM Party landing table with Party data from the insurance solution source
system.
Operation Insert
Operation Insert
Map_Insurance_DIM_Landing_Postal_Address
This mapping populates the MDM Postal Address and Party Postal Address landing tables with Postal
Address and Party Postal Address data from the insurance solution source system.
Operation Insert
Inbound Mappings 27
The following table describes the mapping:
Source Table Source Column Name Expression/ Target Table Name Target Column
Name Lookup Name
Map_PA_DIM_Landing_Agreement
This mapping populates the Agreement landing table with Agreement data from the Policy Admin source
system.
Operation Insert
Map_PA_DIM_Landing_Party_DM
This mapping populates the MDM Party landing table with Party data from the Policy Admin source system.
Operation Insert
Inbound Mappings 29
The following table describes the mapping:
Map_PA_DIM_Landing_Party_Role_Agreement
This mapping populates the MDM Party Role In Agreement landing table with Party Role In Agreement data
from the Policy Admin source system.
Operation Insert
Map_PA_DIM_Landing_Postal_Address
This mapping populates the MDM Postal Address and Party Postal Address landing tables with Postal
Address and Party Postal Address data from the Policy Admin source system.
Operation Insert
Source Table Source Column Name Expression/ Target Table Name Target Column
Name Lookup Name
Inbound Mappings 31
Source Table Source Column Name Expression/ Target Table Name Target Column
Name Lookup Name
Operation Insert
PRFX_NM LTRIM(RTRIM(ROWID
_OBJECT))
FRST_NM N/A
MDL_NM N/A
LST_NM N/A
ADDR_LN_1 N/A
ADDR_LN_2 N/A
ADDR_LN_3 N/A
ADDR_LN_4 N/A
Inbound Mappings 33
Source Column Expression/Lookup Target Table Name Target Column Name
Name
Outbound Mappings
The outbound mappings publish records with updated decedent information and create an error report and a
validation report.
The mappings create two outbound CSV files, one for update in decedent Information and another for
merged records. After creating the outbound files, the mappings run the following SQL statement to update
the control table (C_L_LST_PBLSHD):
Incoming record from the IDI source system has decedent information for a non-existing Individual in any
of the business lines.
Incoming record is a policy request for a deceased Individual.
The Social Security number in the incoming record is not valid.
The death date in the incoming record is not valid.
The outbound data integration mappings generate the error report from the Error Table (C_L_ERR). The error
report contains all records that have the PUBLISHED indicator as N. After generating the report, the
mappings run the following SQL statement to set the PUBLISHED indicator to Y for published records:
The outbound data integration mappings generate the validation report by taking the union of all records from
the reject tables. The mappings use the following filter logic to get records from all reject tables:
After generating the report, the mappings run the following SQL statement to update the control table
(C_L_LST_PBLSHD):
Map_Party_DM_EMO_TPA_Party_Output
This outbound mapping generates Party External Match Output report as a CSV file from the
C_BO_PRTY_DM_EMO party external match table. To generate the Party External Match Output file, the
mappings join the Party, Party EMI, Party EMO, and match information tables.
Composite Services
Target systems can use composite services to lookup for party records based on the specified search
parameters.
searchParty
Uses fuzzy matching to get parties based on the specified search parameters. The service optionally
retrieves policy details of the person. Use the following parameters to search for parties:
name
street
city
state
postalCode
Composite Services 35
country
govtIdType
govtIdValue
returnPolicyInd
Except the returnPolicyInd parameter, the data type for all other parameters is string. The
returnPolicyInd parameter is of boolean data type. If you specify yes for this parameter, the service
returns policy details of all parties.
getParty
Uses exact matching to get parties based on the recordKey parameter.
A data steward uses Informatica Data Director to perform the following tasks:
Search and view the policy details and address details of a deceased or a non deceased person.
Manage the tasks that the MDM processes create based on data loaded from different source systems.
Manage the relationship between party, policy, and address as part of hierarchy management.
Subject Area Group (Display Primary Table Subject Area (Display Name)
Name)
Element Value
Show Xref No
The following table shows the child details of the subject area person:
Name (Display Name) Child Type Match Path to Child Order of Child
Element Value
Show Xref No
The following table shows the child details of the subject area address:
Name (Display Name) Child Type Match Path to Child Order of Child
Element Value
Show Xref No
The following table shows the child details of the subject area auto:
Name (Display Name) Child Type Match Path to Child Order of Child
Element Value
Show Xref No
The following table shows the child details of the subject area life:
Name (Display Name) Child Type Match Path to Child Order of Child
Element Value
Show Xref No
The following table shows the child details of the subject area property:
Name (Display Name) Child Type Match Path to Child Order of Child
The match and merge job in the MDM Hub creates a custom task in the following cases:
When a delete request comes from SSA Death Master File for a record that matched and merged with
base object record.
When an update from an internal system tries to remove the decedent information from the base object
record.
In the preceding cases, a data steward uses Informatica Data Director to approve or reject the task. The
behavior on approval or rejection is explained as follows:
When a data steward approves a task, the MDM Hub processes promote the pending Xref, remove
decedent information from the base object record, and generate a Decedent Status Rollback notification.
When a data steward rejects a task, the MDM Hub processes hard delete the pending Xref and do not
generate a rollback notification.
After you copy the full SSA Death Master File, Policy Admin file, TPA system file, and MDM data file in the
designated source directory, the inbound mappings load data from all the files into the MDM landing tables
41
after applying the relevant filters. In the MDM Hub, start the BG_All_Inbound batch group that performs the
following tasks:
1. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records. The staging jobs also move
the records from the landing tables to the staging tables.
2. The load jobs within the batch group move the records from the staging tables to the base objects.
3. The match and merge job matches the incoming records coming from different source systems and
consolidate records. If the job identifies potential matches, the job create merge tasks. A data steward
uses Informatica Data Director to approve or reject these tasks.
4. JMS publishes the records with updated decedent information to the JMS Queue. The downstream
systems can subscribe to the JMS Queue to get the updated records.
5. The outbound mappings generate a CSV file that contains records with updated decedent information
from the batch control table. The downstream systems can consume the data available in the published
files.
The following image shows the incremental load process for an Add request:
After you copy the delta SSA Death Master File in the designated source directory, the inbound data
integration mappings load the records into the MDM landing tables after applying the relevant filters. In the
MDM Hub, start the BG_All_Inbound batch group that performs the following tasks:
1. The post landing user exit defined for add requests validates records in the landing tables. When an add
record comes for a record that was previously sourced from the SSA DMF file and exists in the MDM
Hub, the user exit flags the record in the error report. The inbound mappings load the record as an
update.
2. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records. The staging jobs then
move the records from the landing tables to the staging tables.
The following image shows the incremental load process for an Update request:
After you copy the delta SSA Death Master File in the designated source directory, the inbound data
integration mappings load the changed records into the MDM landing tables after applying the relevant filters.
In the MDM Hub, start the BG_All_Inbound batch group that performs the following tasks:
1. The post landing user exit defined for an update request validates records in the landing tables. When an
update record comes without a corresponding record in the MDM Hub, the user exit flags the record in
the error report. The inbound mappings load the record as an insert.
2. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records. The staging jobs then
move the records from the landing tables to the staging tables.
3. The validation rules in the MDM Hub change trust scores of incoming records as required.
4. The match and merge job matches the incoming records with the records that exist in the MDM Hub. If
the job identifies potential matches, the job creates merge tasks. A data steward uses Informatica Data
Director to approve or reject these tasks.
5. JMS publishes the records with updated decedent information to the JMS Queue. The downstream
systems can subscribe to the JMS Queue to get the updated records.
The following image shows the incremental load process for a Delete request:
After you copy the delta SSA Death Master File in the designated source directory, the inbound data
integration mappings load the changed records into the MDM landing tables after applying the relevant filters.
In the MDM Hub, start the BG_All_Inbound batch group that performs the following tasks:
1. The post landing user exit defined for delete requests validates records in the landing tables. When a
delete record does not have a corresponding record that exists in the MDM Hub, the user exit flags the
record in the error report.
2. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records. The custom cleanse
functions map the delete records with Hub state indicator as Deleted.
3. The staging jobs move the records from the landing tables to the staging tables.
4. Because a data steward must approve the delete request, the match and merge job creates a task. A
data steward uses Informatica Data Director to approve the task. After a data steward approves the task,
the job removes the decedent information from the consolidated record and generates a Decedent
Status Rollback notification.
5. JMS publishes the records with updated decedent information to the JMS Queue. The downstream
systems can subscribe to the JMS Queue to get the updated records.
6. The outbound data integration mappings generate a CSV file that contains records with updated
decedent information from the batch control table. The downstream systems can consume the data
available in the published files.
The following image shows the incremental load process for an Add request:
In the MDM Hub, start the BG_All_Inbound batch group that performs the following tasks:
1. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records.
2. The staging jobs move the records from the landing tables to the staging tables.
3. The validation rules in the MDM Hub change trust scores of incoming records as required.
4. The match and merge job matches the incoming add records from all source systems and consolidates
records. If the job identifies potential matches, the job creates merge tasks. A data steward uses
Informatica Data Director to approve or reject these tasks. After a data steward approves merge tasks,
the match and merge job generates a report containing records that merged with records from SSA
Death Master File that exist in the MDM Hub.
5. JMS publishes the records with updated decedent information to the JMS Queue. The downstream
systems can subscribe to the JMS Queue to get the updated records.
6. The outbound mappings generate a CSV file that contains records with updated decedent information
from the batch control table. The downstream systems can consume the data available in the published
files.
The following image shows the incremental load process for an Update request:
1. The staging jobs within the batch group use custom cleanse functions to cleanse and standardize the
incoming records. Informatica Address Doctor standardizes address records.
2. The validation rules in the MDM Hub change trust scores of incoming records as required.
3. The match and merge job matches the incoming records with the records that exist in the MDM Hub. If
the incoming update record has a higher trust score, the job updates the consolidated record with the
incoming values. If the incoming update record has null decedent information from a system that
previously sent the same record with decedent information, the job creates a task. A data steward uses
Informatica Data Director to approve the task. After a data steward approves the task, the job overwrites
the consolidated record with null values and generates a Decedent Status Rollback notification.
4. JMS publishes the records with updated decedent information to the JMS Queue. The downstream
systems can subscribe to the JMS Queue to get the updated records.
5. The outbound mappings generate a CSV file that contains records with updated decedent information
from the batch control table. The downstream systems can consume the data available in the published
files.
Reference Information
This chapter includes the following topic:
Additional Resources, 47
Additional Resources
Base Objects, Landing Tables, Staging Tables, Custom Tables, Lookup Tables
For more information about the structure of the tables, see the BaseObjects_Tables.xls file available in
the ZIP file that you downloaded from Informatica Marketplace.
47
INDEX
D O
data load workflows overview
initial 41 architecture 4
non SSA - add 45 business case 2
non SSA - update 45 overview 1
48