informatica mdm multidomain edition - 1. - unclaimed life

Informatica MDM Multidomain Edition (Version 1)

Unclaimed Life Insurance Data Management Solution Guide

Informatica MDM Multidomain Edition Unclaimed Life Insurance Data Management Solution Guide

Version 1May 2014

Copyright (c) 2014 Informatica Corporation. All rights reserved.

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, <[email protected]>. 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 Developer’s 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.

Part Number: MDM-DUG-10000-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica My Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Support YouTube Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Unclaimed Life Insurance Data Management Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . 1

Users of Unclaimed Life Insurance Data Management Solution. . . . . . . . . . . . . . . . . . . . . . . . . 2

Architecture - Informatica Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Data Transfer Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Configuration 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

Chapter 3: Solution Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Source Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

MDM Hub Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Base Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Lookup Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Landing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Custom Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Staging Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

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

Chapter 4: Data Load Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Initial Load Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

SSA Death Master File Incremental Load Process - Add. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

SSA Death Master File Incremental Load Process - Update. . . . . . . . . . . . . . . . . . . . . . . . . . 43

SSA Death Master File Incremental Load Process - Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . 44

TPA/Policy Admin/Customer Master Incremental Load Process - Add. . . . . . . . . . . . . . . . . . . . 45

TPA/Policy Admin/Customer Master Incremental Load Process - Update. . . . . . . . . . . . . . . . . . 45

Chapter 5: Reference Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

ii Table of Contents

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table of Contents iii

PrefaceThe Unclaimed Life Insurance Data Management Solution Guide explains how insurance companies can get information about deceased people and identify beneficiaries. An administrator can use the information in this guide to configure the Unclaimed Life Insurance Data Management Solution. This guide assumes that you are familiar with Informatica MDM Multidomain Edition.

Informatica Resources

Informatica My Support PortalAs an Informatica customer, you can access the Informatica My Support Portal at http://mysupport.informatica.com.

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 DocumentationThe 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 [email protected]. 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.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide

iv

http://mysupport.informatica.com

mailto:[email protected]


http://www.informatica.com


solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through email at [email protected].

Informatica Support YouTube ChannelYou can access the Informatica Support YouTube channel at http://www.youtube.com/user/INFASupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at [email protected] or send a tweet to @INFASupport.

Informatica MarketplaceThe 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 VelocityYou 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 [email protected].

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support.

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



http://www.youtube.com/user/INFASupport


http://www.informaticamarketplace.com




http://www.informatica.com/us/services-and-training/support-services/global-support-centers/

C H A P T E R 1

Introduction to Unclaimed Life Insurance Data Management Solution

This chapter includes the following topics:

• Unclaimed Life Insurance Data Management Solution Overview, 1

• Users of Unclaimed Life Insurance Data Management Solution, 2

• Architecture - Informatica Components, 2

• Data Transfer Process, 4

Unclaimed Life Insurance Data Management Solution Overview

The Unclaimed Life Insurance Benefits Act of 2011 requires insurance companies to identify beneficiaries of deceased people and to settle all insurance claims. The Unclaimed Life Insurance Data Management Solution (the Solution) integrates Informatica services and Informatica MDM Multidomain Edition to ensure compliance with the act.

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:

Near real-time data transfer

The target system subscribes to a queue to get notifications when Java Message Service publishes records with updated decedent information to the queue.

Real-time data transfer

The target system uses composite services to look up 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.

Users of Unclaimed Life Insurance Data Management Solution

Users of Unclaimed Life Insurance Data Management Solution (the Solution) include insurance organizations, governments, law enforcement agencies, and medical hospitals.

The following users can use the Soluiton to identify beneficiaries, verify death, and prevent identity fraud:

Insurance and pension fund organizations

Insurance and pension fund organizations can use the Death Master File to identify the beneficiaries of a deceased person. After identifying the beneficiaries, the organizations can contact the beneficiaries and settle the claims.

Law enforcement agencies

As part of investigations, law enforcement agencies and investigative firms can use the Death Master File to verify the death of a person.

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.

Architecture - Informatica ComponentsThe Unclaimed Life Insurance Data Management Solution (the Solution) uses the Informatica services, Informatica Developer, and Informatica MDM Multidomain Edition to transfer information about deceased people from source systems to target systems.

The following image shows the Informatica components that the Solution uses:

2 Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution

The following text explains 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.

Data Integration Service

The Data Integration Service establishes integration between the MDM Hub and different source systems.

Model Repository Service

The Model Repository Service enables the Developer tool to connect to the model repository.

MDM Hub

The Data Integration Service establishes integration between the different source systems and the MDM Hub.

Informatica Data Director

A data steward uses Informatica Data Director to approve or reject requests to merge records.

Informatica Address Doctor

The Solution uses Informatica Address Doctor to standardize addresses in the incoming records.

Architecture - Informatica Components 3

Informatica ActiveVOS

You can use Informatica ActiveVOS to build internal workflows in the MDM Hub. The Solution starts a workflow when a data steward approves or rejects a merge request. You can use ActiveVOS to build this workflow. However, it is not required to use ActiveVOS to configure the Solution.

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.

Data Transfer ProcessThe Unclaimed Life Insurance Data Management Solution (the Solution) reads decedent information from various source systems and sends the updated decedent information to the downstream systems.

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.

4 Chapter 1: Introduction to Unclaimed Life Insurance Data Management Solution

3. Match and merge jobs use multiple match rules to match incoming records with the records in the MDM Hub.

4. If the MDM Hub cannot automatically merge records, it creates tasks for a data steward.

5. A data steward approves or rejects merge records through Informatica Data Director.

6. When you run the required outbound dataflow script, the outbound mappings write merged records to a file and publish an error report and a validation report.

7. Java Message Service publishes automatically merged records to a queue.

8. The target systems can access records with updated decedent information.

Data Transfer Process 5

C H A P T E R 2

ConfigurationThis 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 OverviewTo configure Unclaimed Life Insurance Data Management Solution, perform the following tasks:

1. Import metadata changelist or promote metadata changelist.

2. Add custom Java cleanse library.

3. Add custom MDM Hub user exits.

4. Import application components into Informatica Data Director.

5. Import data integration mappings into the Developer tool.

6. Configure inbound and outbound mappings.

7. Test inbound and outbound mappings.

8. Configure inbound and outbound dataflow scripts.

9. Deploy composite services.

6

PrerequisitesBefore 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.

Solution Package ComponentsThe Unclaimed Life Insurance Data Management Solution Accelerator (the Solution) is available as a ZIP file on Informatica Marketplace.

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.

Hub User Exit

Contains the DIM971.jar file Siperian version and DIMVOS.jar file ActiveVOS version. You must add one of these files to the MDM Hub. Use the ActiveVOS version if you have integrated ActiveVOS with Informatica MDM Multidomain Edition. The jar file contains user exits that validate incoming records 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

https://community.informatica.com/solutions/informatica_unclaimed_life_insurance_data_mgmt

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.

Import Metadata Changelist into the Repository Manager

You must apply the MDM Hub metadata changelist for Unclaimed Life Insurance Data Management Solution in your target environment. The MDM Hub metadata includes components, such as landing tables, user exits, lookup tables, staging tables, base objects, and match/merge rules. Metadata import works for all type of databases that the MDM Hub supports.

1. In the Hub Console, click Repository Manager.

2. Click the Import tab or the Promote tab.

3. Click the button next to the Source field.

The Open Repository dialog box appears.

4. Click File Repository.

5. Browse to find the DIM_MET_EXPORT_06032014_HF1.change.xml metadata file available inside the <InstallDirectory>\MDM Solution\Met Export folder.

6. Select all the schema components or changed schema components and apply the changes.

Add Custom Java Cleanse LibraryMultiple custom cleanse functions are available with Unclaimed Life Insurance Data Management Solution. These functions cleanse and standardize the data coming from different source systems.

1. In the Hub Console, under Model, click Cleanse Functions.

2. Click Cleanse Functions > Add Java Library.

3. Browse to find the Cleanse.jar file available inside the <InstallDirectory>\MDM Solution\Custom\Cleanse Function folder.

4. Enter a name and description for the library.

8 Chapter 2: Configuration

Add Custom MDM Hub User ExitsThe 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.

Import Application Components into Informatica Data Director

When you load decedent information from different source systems into the MDM Hub, the match and merge job creates tasks for a data steward. A data steward uses Informatica Data Director to approve or reject these tasks. To set up the application for a data steward, import the application components into the Informatica Data Director.

1. Start Informatica Data Director Configuration Manager. Use the following URL:

https://hostname:port/bdd/config2. 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.

Import Data Integration Mappings into the Developer Tool

The inbound mappings populate data into the landing tables from files coming from different source systems. The outbound mappings publish records with updated decedent information, and create an error report and a validation report.

1. In the Informatica Developer, click File > Import.

2. Under Informatica, select Import Object Metadata File, and click Next.

3. Browse to find the DIM_HF1_03032014.xml file available inside the <InstallDirectory>\MDM Solution\Integration\Mercury DI folder, and click Next.

Add Custom MDM Hub User Exits 9

4. Select the components from the source and select the target project where you want to import the objects.

5. Click Next and Finish.

Perform Post-Import TasksAfter you import mappings, change inbound and outbound mappings, and change the inbound and outbound dataflow scripts as required.

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.

Deploy Composite ServicesTarget systems can use searchParty and getParty composite services to look up parties, postal addresses, and insurance policies that are stored in the MDM Hub.

1. In the DIMService.zip file available inside the <InstallDirectory>\MDM Solution\Custom\Web_App folder, change the files inside the Config folder as required.

2. Run the Build.xml file from the command line.

The command generates a WAR file based on the changes you made to the configuration files.

3. Deploy the WAR file on the application server.

4. After you deploy the WAR file on the application server, use the following URL to get the WSDL:

http://{hostname}:{port}/DIMCompositeService/MDMDIMService?wsdl

10 Chapter 2: Configuration

C H A P T E R 3

Solution ComponentsThis 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 SystemsSource 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:

Customer Master System

A system that contains customer master data.

Internal Decedent Information System

An internal system that sends decedent information.

Lookup System

System that stores standard lookup values, such as gender, prefix, and title.

Policy Admin System

a system that contains information about insurance policy holders.

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 ComponentsMDM 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 ObjectsThe 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 TablesThe 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.

12 Chapter 3: Solution Components

C_BT_CNTRY

Stores information about the country.

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 TablesLanding 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.

The following landing tables are available for this solution:

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.

MDM Hub Components 13

C_L_LKP_CNTRY

Stores information about the country 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 TablesCustom 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_ERR

Stores all records that had errors.

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 TablesStaging 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_AGRMNT_TYP

Stores information about the type of insurance agreement 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.


C_S_SSA_PRTY_DM

Stores personal information, such as first name, last name, prefix, death date, and gender, sent from the Social Security Administration source system.

PackagesTo 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:

• Data integration packages

• Hierarchy management packages

• Informatica Data Director packages

• MQ packages

• Services packages

Trust Value SettingsDifferent trust settings are assigned to the death information attributes.

Trust for Death Date, Death Indicator, and External Match IndicatorThe following table shows the trust setting for death date, death indicator, and external match indicator attributes:

Source System Maximum Minimum

Customer Master 60 60

Interna Decedent Information 90 90

Policy Admin 60 60

SSA 90 90

SYS0 100 100

The Decay, Duration, and Graph values for the preceding trusts are 12, Month, and Linear.

Trust for Death Source FlagThe following table shows the trust setting for the death source flag:


Customer Master 90 90

Interna Decedent Information 60 60

Policy Admin 90 90



SSA 60 60

SYS0 100 100

The Decay, Duration, and Graph values for the preceding trusts are 12, Month, and Linear.

Data Cleansing and StandardizationMultiple cleanse functions are available with Unclaimed Life Insurance Data Management Solution to cleanse and standardize incoming data.

The custom cleanse functions perform the following tasks:

• Extract particular fields values from concatenated values.

• Map source values to standard list of values.

• Populate conditional fields with constant values.

• Remove noise characters.

The following table lists the custom cleanse functions that cleanse and standardize data incoming data:

Custom Cleanse Function Function Type Description

Multi Compress Whitespace5 Graph Uses the standard Compress Whitespace function five times to remove whitespaces from five input strings at the same time. The standard Compress Whitespace function removes whitespaces for one input string.

Multi Compress Whitespace15

Graph Uses the Multi Compress Whitespace5 function three times to remove whitespaces from 15 input strings at the same time.

AddressStandardization5 Graph Uses Address Doctor to standardize the address fields.

PersonFullName Graph Generates the full name of a person by concatenating the first name, middle name, and last name if the full name in the incoming record is null.

SSN Validation Graph Validates the format of the Social Security Number (SSN) and standardizes the valid SSN into one single standard format.


Custom Cleanse Function Function Type Description

CL - Gender Cleanse List Standardizes the gender of the person. For example, if the gender in the incoming record is MALE or male, this function populates the gender in the output record as M.

CL - Prefix Cleanse List Standardizes the prefix in the name. For example, if the prefix in the incoming record is MR or mr, this function populates the prefix in the output record as Mr.

CL - Suffix Cleanse List Standardizes the suffix in the name. For example, if the suffix in the incoming record is JUNIOR, this function populates the suffix in the output record as Jr.

CL - Title Cleanse List Standardizes the title in the name. For example, if the title in the incoming record is PROF or DR, this function populates the title in the output record as Prof or Dr.

StandardizeDeathDate Java Function Validates the date of death and standardizes the valid date of death to a standard format.

you can create the following types of custom cleanse functions:

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.

MDM Hub User ExitsThe Post Land, Post Load, and Post Match user exits in MDM Hub validate incoming data from different source systems.

The following Java class implements the MDM Hub user exits:


com.infa.solutions.dim.userexit.PostLandingUserExit

This class implements MDM Hub PostLandingUserExit and overrides the processUserExit method to perform the following validations:SSA Records Validation

The user exits validate records from SSA Death Master File against the following scenarios:

• 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.

Internal Decedent Source Records Validation

The user exits validate records from the Internal Decedent Information (IDI) system with the decedent flag set to N against the records in the MDM Hub. If a record merged with other records, the user exit loads the record with pending state and inserts it into the C_L_CUSTOM_TASK custom task table.

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.

Match and Merge of DataMatch rulesets are available to match party data and address data and merge records.

The following match rulesets are available to match party data:

• MRS_PARTY_EXTERNAL

• MRS_Party (Default)

• MRS_Party_IDD


The search level of all the rules inside the preceding rulesets is Typical and the rules use fuzzy matching to match party names.

The following match rulesets are available to match address data:

• MRS_Account_IDD

• MRS_Address (Default)

The MRS_Party_Address (Default) ruleset performs an exact match of party and address data.

Hierarchy ManagementA 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

Party DM Person Person Represents an individual

Agreement - Auto- Life- Property

- Auto- Life- Property

Represents life insurance, property insurance, and auto insurance agreements

Postal Address Addr Address Represents the postal address of the party

The following table explains the different relationship types:

Relationship Object

Relationship Type Code

Display Name Entity Type 1 EntityType 2 Direction

Party Postal Address

Person Address Person Address Person Address Entity 1 to Entity 2

Party Role in Agreement

Auto Policy to Person

Auto Policy to Person

Auto Person Entity 1 to Entity 2


Life Policy to Person

Life Policy to Person

Life Person Entity 1 to Entity 2


Property Policy to Person

Property Policy to Person

Property Person Entity 1 to Entity 2

Hierarchy Management 21

External Match for TPAMDM 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.

The utility performs the following tasks to match data:

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 MappingsInbound mappings populate data into the landing tables from files coming from the different source systems.

Map_DMF_DIM_Landing_Party_DMThis mapping populates the MDM Party landing table with data from the standard fixed length SSA DMF file provided by the Government.

Source Object Fixed length file

Target Object C_L_PRTY_DIM

Data Filters N/A

Operation Insert

The following table describes the mapping:

Source Column Name Expression/Lookup Target Column Name

SOCIAL SECURITY NUMBER N/A GOVT_ID

LAST NAME RTRIM(LastName) LST_NM

NAME SUFFIX RTRIM(NameSuffix) SFX_NM

FIRST NAME RTRIM(FirstName) FRST_NM

MIDDLE NAME RTRIM(MiddleName) MDL_NM

VERIFIED OR PROOF CODE N/A VRFCTN_CD

DATE OF DEATH (MM,DD,CC,YY) N/A DTH_DT

DATE OF BIRTH (MM,DD,CC,YY) N/A BIRTH_DT


Source Column Name Expression/Lookup Target Column Name

SYSTIMESTAMP() LAST_UPDATE_DATE

SOCIAL SECURITY NUMBER SRC_PRTY_ID

N/A PRFX_NM

LTRIM(RTRIM(CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(RTRIM(FirstName),' '),RTRIM(MiddleName)),' '),RTRIM(LastName)),' '),RTRIM(NameSuffix))))

FULL_NM

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_DMThis 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.

Source Object CSV File 'IDI'

Target Object C_L_PRTY_DIM, C_L_PSTL_ADDR, C_L_PRTY_PSTL_ADDR

Data Filters N/A

Operation Insert


Source Column Name

Expression/Lookup Target Table Name Target Column Name

PARTY_ID N/A C_L_PRTY_DIM PRTY_ID

FIRST_NM N/A C_L_PRTY_DIM FRST_NM

Inbound Mappings 23

Source Column Name


MIDDLE_NM N/A C_L_PRTY_DIM MDL_NM

LAST_NM N/A C_L_PRTY_DIM LST_NM

FULL_NM N/A C_L_PRTY_DIM FULL_NM

PARTY_TP N/A C_L_PRTY_DIM PRTY_TP

BIRTH_DT N/A C_L_PRTY_DIM BIRTH_DT

GENDER_CD N/A C_L_PRTY_DIM GNDR_CD

DEATH_IND N/A C_L_PRTY_DIM DTH_IND

DEATH_DT N/A C_L_PRTY_DIM DTH_DT

FED_GOV_ID N/A C_L_PRTY_DIM FED_GOV_ID

SUFFIX_NM N/A C_L_PRTY_DIM SFX_NM

PREFIX_NM N/A C_L_PSTL_ADDR PRFX_NM

ADDRESS_ID N/A C_L_PSTL_ADDR ADDR_ID

ADDR_LINE_1 N/A C_L_PSTL_ADDR ADDR_LINE_1



ADDR_LINE_4 N/A C_L_PRTY_PSTL_ADDR ADDR_LINE_4

ADDRESS_TYPE N/A C_L_PSTL_ADDR ADDR_TYP

COUNTY N/A C_L_PSTL_ADDR COUNTY

CITY N/A C_L_PSTL_ADDR CITY

STATE N/A C_L_PSTL_ADDR STATE

COUNTRY_CD N/A C_L_PSTL_ADDR CNTRY_CD

POSTAL_CD N/A C_L_PSTL_ADDR PSTL_CD

POSTAL_EXT_CD N?A C_L_PRTY_PSTL_ADDR PSTL_EXT_CD

PARTY_ID C_L_PRTY_PSTL_ADDR PRTY_ID

ADDRESS_ID C_L_PRTY_PSTL_ADDR ADDR_ID

'IDI' String Constant C_L_PRTY_PSTL_ADDR SRC_SYS

SYSTIMESTAMP() C_L_PSTL_ADDR LAST_UPDATE_DATE


Source Column Name


'IDI' String Constant C_L_PSTL_ADDR SRC_SYS

SYSTIMESTAMP() C_L_PRTY_DIM LAST_UPDATE_DATE

'IDI' String Constant C_L_PRTY_DIM SRC_SYS

SYSTIMESTAMP() LAST_UPDATE_DATE

Map_Insurance_DIM_Landing_AgreementThis mapping populates the Agreement landing table with Agreement data that comes from the insurance solution source system.

Source Object Oracle Database Object C_B_AGRMNT

Target Object C_L_AGRMNT

Data Filters HUB_STATE_IND=1

Operation Insert


Source Column Name


ROWID_OBJECT LTRIM(RTRIM(ROWID_OBJECT))

C_L_AGRMNT SRC_AGRMNT_ID

AGRMNT_NUM N/A C_L_AGRMNT AGRMNT_NUM

AGRMNT_CLASS_CD N/A C_L_AGRMNT AGRMNT_CLASS_CD

AGRMNT_TP N/A C_L_AGRMNT AGRMNT_TYP

AGREEMENT_NAME N/A C_L_AGRMNT AGRMNT_NM

'CM' String Constant C_L_AGRMNT SRC_SYS

SYSTIMESTAMP() C_L_AGRMNT LAST_UPDATE_DATE

Inbound Mappings 25

Map_Insurance_DIM_Landing_Party_DMThis mapping populates the MDM Party landing table with Party data from the insurance solution source system.

Source Object Oracle Database Object C_B_PARTY


Data Filters PARTY_TP='Person' and HUB_STATE_IND=1

Operation Insert


Source Column Name



C_L_PRTY_DIM SRC_PRTY_ID











PREFIX_NM N/A C_L_PRTY_DIM PRFX_NM

LAST_UPDATE_DATE N/A C_L_PRTY_DIM LAST_UPDATE_DATE

'CM' String Constant C_L_PRTY_DIM SRC_SYS


Map_Insurance_DIM_Landing_Party_Role_AgreementThis mapping populates the MDM Party Role In Agreement landing table with Party Role In Agreement data from the insurance solution source system.

Source Object Oracle Database Object C_B_PARTY_AGRMNT

Target Object C_L_PRTY_RLE_AGRMNT

Data Filters ROLE_TP='Policy Holder' or ROLE_TP='Beneficiary' or ROLE_TP='Insured' or ROLE_TP='Insurer' and HUB_STATE_IND=1

Operation Insert


Source Column Name



C_L_PRTY_RLE_AGRMNT SRC_PRTY_AGRMNT_ID

HIERARCHY_CODE N/A C_L_PRTY_RLE_AGRMNT HIERARCHY_CD

REL_TYPE_CODE N/A C_L_PRTY_RLE_AGRMNT REL_TYPE_CD

AGRMNT_FK N/A C_L_PRTY_RLE_AGRMNT AGRMNT_ID

PARTY_FK N/A C_L_PRTY_RLE_AGRMNT PRTY_ID

ROLE_TP N/A C_L_PRTY_RLE_AGRMNT RLE_TYP

SUB_ROLE_TP N/A C_L_PRTY_RLE_AGRMNT SB_RLE_TYP

SYSDATE C_L_PRTY_RLE_AGRMNT LAST_UPDATE_DATE

'CM' String Constant C_L_PRTY_RLE_AGRMNT SRC_SYS

Map_Insurance_DIM_Landing_Postal_AddressThis 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.

Source Object Oracle Database Object C_B_ADDR, C_B_PARTY_ADDR

Target Object C_L_PSTL_ADDR, C_L_PRTY_PSTL_ADDR

Data Filters N/A

Operation Insert

Inbound Mappings 27


Source Table Name

Source Column Name Expression/Lookup

Target Table Name Target Column Name

C_B_PARTY_ADDR


C_L_PRTY_PSTL_ADDR

SRC_PRTY_PSTL_ADDR_ID

C_B_PARTY_ADDR

PARTY_FK N/A C_L_PRTY_PSTL_ADDR

PRTY_ID

C_B_PARTY_ADDR

ADDR_FK N/A C_L_PRTY_PSTL_ADDR

ADDR_ID

C_B_PARTY_ADDR

HIERARCHY_CODE N/A C_L_PRTY_PSTL_ADDR

HIERARCHY_CD

C_B_PARTY_ADDR

REL_TYPE_CODE N/A C_L_PRTY_PSTL_ADDR

REL_TYPE_CD

C_B_PARTY_ADDR

ADDR_TP N/A C_L_PRTY_PSTL_ADDR

ADDR_TYP

C_B_PARTY_ADDR

LAST_UPDATE_DATE N/A C_L_PRTY_PSTL_ADDR

LAST_UPDATE_DATE

'CM' String Constant

C_L_PRTY_PSTL_ADDR

SRC_SYS

C_B_ADDR ROWID_OBJECT LTRIM(RTRIM(ROWID_OBJECT))

C_L_PSTL_ADDR SRC_PSTL_ADDR_ID

C_B_ADDR ADDR_LINE_1 N/A C_L_PSTL_ADDR ADDR_LINE_1




C_B_ADDR COUNTY N/A C_L_PSTL_ADDR COUNTY

C_B_ADDR CITY N/A C_L_PSTL_ADDR CITY

C_B_ADDR STATE N/A C_L_PSTL_ADDR STATE

C_B_ADDR COUNTRY_CD N/A C_L_PSTL_ADDR CNTRY_CD

C_B_ADDR POSTAL_CD N/A C_L_PSTL_ADDR PSTL_CD

C_B_ADDR POSTAL_EXT_CD N/A C_L_PSTL_ADDR PSTL_EXT_CD

C_B_ADDR LATITUDE N/A C_L_PSTL_ADDR LATTD

C_B_ADDR LONGITUDE N/A C_L_PSTL_ADDR LNGTD


Source Table Name



C_B_ADDR VALIDATION_MSG N/A C_L_PSTL_ADDR VLDTN_MSG

C_B_ADDR LAST_UPDATE_DATE N/A C_L_PSTL_ADDR LAST_UPDATE_DATE

Map_PA_DIM_Landing_AgreementThis mapping populates the Agreement landing table with Agreement data from the Policy Admin source system.

Source Object CSV File ‘PA_AGRMNT_DATA’

Target Object C_L_AGRMNT

Data Filters N/A

Operation Insert


Source Column Name


AGRMNT_ID N/A C_L_AGRMNT SRC_AGRMNT_ID

AGRMNT_NUM N/A C_L_AGRMNT AGRMNT_NUM

AGRMNT_CLASS_CD N/A C_L_AGRMNT AGRMNT_CLASS_CD

AGRMNT_TP N/A C_L_AGRMNT AGRMNT_TP

AGREEMENT_NAME N/A C_L_AGRMNT AGREEMENT_NAME

'PA' String Constant C_L_AGRMNT SRC_SYS

SYSDATE C_L_AGRMNT LAST_UPDATE_DATE

Map_PA_DIM_Landing_Party_DMThis mapping populates the MDM Party landing table with Party data from the Policy Admin source system.

Source Object CSV FILE 'PA_PARTY_DATA'


Data Filters N/A

Operation Insert

Inbound Mappings 29


Source Column Name


PARTY_ID N/A C_L_PRTY_DIM SRC_PRTY_ID











PREFIX_NM N/A C_L_PRTY_DIM PRFX_NM

SYSDATE C_L_PRTY_DIM LAST_UPDATE_DATE

'PA' String Constant C_L_PRTY_DIM SRC_SYS

Map_PA_DIM_Landing_Party_Role_AgreementThis mapping populates the MDM Party Role In Agreement landing table with Party Role In Agreement data from the Policy Admin source system.

Source Object CSV File 'PA_PARTY_AGRMNT_DATA'

Target Object C_L_PRTY_RLE_AGRMNT

Data Filters N/A

Operation Insert



Source Column Name


PRTY_AGRMNT_ID N/A C_L_PRTY_RLE_AGRMNT SRC_PRTY_AGRMNT_ID

HIERARCHY_CODE N/A C_L_PRTY_RLE_AGRMNT HIERARCHY_CD

REL_TYPE_CODE N/A C_L_PRTY_RLE_AGRMNT REL_TYPE_CD

AGRMNT_FK N/A C_L_PRTY_RLE_AGRMNT AGRMNT_ID

PARTY_FK N/A C_L_PRTY_RLE_AGRMNT PRTY_ID

ROLE_TP N/A C_L_PRTY_RLE_AGRMNT RLE_TYP

SUB_ROLE_TP N/A C_L_PRTY_RLE_AGRMNT SB_RLE_TYP

SYSDATE C_L_PRTY_RLE_AGRMNT LAST_UPDATE_DATE

'PA' String Constant C_L_PRTY_RLE_AGRMNT SRC_SYS

Map_PA_DIM_Landing_Postal_AddressThis 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.

Source Object CSV File 'PA_ADDR_DATA'

Target Object C_L_PSTL_ADDR, C_L_PRTY_PSTL_ADDR

Data Filters N/A

Operation Insert


Source Table Name



CSV File 'PA_ADDR_DATA'

ADDR_ID N/A C_L_PRTY_PSTL_ADDR

SRC_ADDR_ID


PTY_ID N/A C_L_PRTY_PSTL_ADDR

SRC_PTY_ID


ADDR_LINE_1 N/A C_L_PRTY_PSTL_ADDR

ADDR_LINE_1

Inbound Mappings 31

Source Table Name





ADDR_LINE_2



ADDR_LINE_3



ADDR_LINE_4


ADDR_TYPE N/A C_L_PRTY_PSTL_ADDR

ADDR_TYPE


COUNTY N/A C_L_PRTY_PSTL_ADDR

COUNTY


CITY N/A C_L_PSTL_ADDR CITY


STATE N/A C_L_PSTL_ADDR STATE


COUNTRY_CD N/A C_L_PSTL_ADDR CNTRY_CD


POSTAL_CD N/A C_L_PSTL_ADDR PSTL_CD


POSTAL_EXT_CD N/A C_L_PSTL_ADDR PSTL_EXT_CD

SYSDATE C_L_PSTL_ADDR LAST_UPDATE_DATE

'PA' String Constant

C_L_PSTL_ADDR SRC_SYS

SYSDATE C_L_PRTY_PSTL_ADDR

LAST_UPDATE_DATE

'PA' String Constant

C_L_PRTY_PSTL_ADDR

SRC_SYS


Map_TPA_Party_Party_DM_EMIThis mapping populates the MDM Party External Match table with Party External Match data from the Third Party Administrator (TPA) system.

Source Object CSV File 'TPA_Party_Input'

Target Object C_BO_PRTY_DM_EMI

Data Filters N/A

Operation Insert


Source Column Name


PRFX_NM LTRIM(RTRIM(ROWID_OBJECT))

FRST_NM N/A

MDL_NM N/A

LST_NM N/A

FULL_NM N/A C_BO_PRTY_DM_EMI PERSON_NAME

BIRTH_DT N/A C_BO_PRTY_DM_EMI EX_BIRTH_DT

GOVT_ID N/A C_BO_PRTY_DM_EMI ID

GNDR_CD N/A C_BO_PRTY_DM_EMI EX_GENDER

ADDR_LN_1 N/A

ADDR_LN_2 N/A

ADDR_LN_3 N/A

ADDR_LN_4 N/A

CITY N/A C_BO_PRTY_DM_EMI EX_CITY

STATE 'CM' String Constant C_BO_PRTY_DM_EMI EX_STATE

CNTRY_CD C_BO_PRTY_DM_EMI EX_COUNTRY

PSTL_CD C_BO_PRTY_DM_EMI EX_POSTAL_CODE

PSTL_CD_EXT C_BO_PRTY_DM_EMI EX_POSTAL_CODE_EXTENSION

Inbound Mappings 33

Source Column Name


Sequence ID of Key Generator

C_BO_PRTY_DM_EMI SOURCE_KEY

'TPA' String Constant C_BO_PRTY_DM_EMI SOURCE_NAME

'TPA Party External Input File' String Constant

C_BO_PRTY_DM_EMI FILE_NAME

GOVT_ID C_BO_PRTY_DM_EMI EX_IDENTIFIER

'N' C_BO_PRTY_DM_EMI EX_DEATH_SRC_FLAG

CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(CONCAT(CITY,' '),STATE),' '),CNTRY_CD),' '),PSTL_CD),' '),PSTL_CD_EXT)

C_BO_PRTY_DM_EMI ADDRESS_PART2

CONCAT(CONCAT(ADDR_LN_1,' '),ADDR_LN_2)

C_BO_PRTY_DM_EMI ADDRESS_PART1

CONCAT(CONCAT(PSTL_CD,' '),PSTL_CD_EXT)

C_BO_PRTY_DM_EMI POSTAL_AREA

Outbound MappingsThe outbound mappings publish records with updated decedent information and create an error report and a validation report.

Decedent Information UpdateMessages and triggers insert records with updated decedent information into the MQ data change table in the MDM Hub. The outbound mappings generate the outbound files by joining the MQ data change table with the base object and its XREF table. The mappings use the following filter logic to get changed records from the MQ data change table:

Filter Query: - last_update_date > (select PBLSHD_DT from C_L_LST_PBLSHD where FL_NM='DIM_Update_Outbound')

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):

Post SQL: - update C_L_LST_PBLSHD set PBLSHD_DT=sysdate where FL_NM='DIM_Update_Outbound'


Error and Validation ReportsWhen inbound mappings load data into the MDM Hub, the mappings generate an error report and a validation report as CSV files in the following cases:

• 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:

Post SQL: update c_l_err set "C_L_ERR"."PUBLISHED"='Y'

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:

Filter Query: - last_update_date > (select PBLSHD_DT from C_L_LST_PBLSHD where FL_NM='DIM_Validation_Error_Output')

After generating the report, the mappings run the following SQL statement to update the control table (C_L_LST_PBLSHD):

Post SQL: - update C_L_LST_PBLSHD set PBLSHD_DT=sysdate where FL_NM='DIM_Validation_Error_Output'

Map_Party_DM_EMO_TPA_Party_OutputThis 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 ServicesTarget systems can use composite services to lookup for party records based on the specified search parameters.

Target systems can use the following composite services:

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.

Informatica Data Director User InterfaceA user interface in Informatica Data Director is available that contains a customized dashboard to display graphical reports of the processed data. These reports appear as charts and are based on the custom charts available with the solution.

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.

Hierarchy Configuration in Informatica Data DirectorThe relationship between the core entities person, insurance policies, and addresses is configured as subject areas in the Informatica Data Director. As a result, a data steward can view a hierarchical representation of this relationship in the Informatica Data Director. The following subject areas are configured in IDD:

Subject Area Group (Display Name)

Primary Table Subject Area (Display Name)

Party Party Person

Postal Address Postal Address Address

Policy Agreement Auto

Policy Agreement Property

Policy Agreement Life


Subject Area - PersonThe following table shows the configuration of the person subject area:

Element Value

HM Entity Type Person

Subtype Column Party BO Class Code

Subtype Value Person

Search Display Package Package Person IDD Search

Potential Matches Link Column Full Name

Show Xref No

Label Label:{0} {Last Name}Exists No Attributes Format: {0}New Format: New {0}

The following table shows the child details of the subject area person:

Name (Display Name) Child Type Match Path to Child Order of Child

AddressHM Entity Type: Address

Reference Postal Address 1

Life PolicyHM Entity Type: Life

Reference Agreement 2

Life PolicyHM Entity Type: Auto


Life PolicyHM Entity Type: Property


Subject Area - AddressThe following table shows the configuration of the address subject area:

Element Value

HM Entity Type Address

Subtype Column Postal Address Class

Subtype Value Addr

Search Display Package Package Postal Address IDD Search

Hierarchy Configuration in Informatica Data Director 37

Element Value

Potential Matches Link Column N/A

Show Xref No

The following table shows the child details of the subject area address:


Party Reference Party DM 1

Subject Area - AutoThe following table shows the configuration of the auto subject area:

Element Value

HM Entity Type Auto

Subtype Column Agreement Class

Subtype Value Auto

Search Display Package Package Agreement IDD Search

Potential Matches Link Column Agreement Number

Show Xref No

The following table shows the child details of the subject area auto:


InsuredPartySubtype Column : Role TypeSubtype Value : Insured

Reference Party DM 1

AllPartiesSubtype Column : Party BO Class CodeSubtype Value : Person



Subject Area - LifeThe following table shows the configuration of the life subject area:

Element Value

HM Entity Type Life


Subtype Value Life



Show Xref No

The following table shows the child details of the subject area life:




BeneficiarySubtype Column : Role TypeSubtype Value : Beneficiary




Subject Area - PropertyThe following table shows the configuration of the property subject area:

Element Value

HM Entity Type Property


Subtype Value Property


Hierarchy Configuration in Informatica Data Director 39

Element Value


Show Xref No

The following table shows the child details of the subject area property:






Custom Tasks and WorkflowsMDM Hub processes create custom tasks in Informatica Data Director for a data steward.

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.


C H A P T E R 4

Data Load WorkflowsThis chapter includes the following topics:

• Initial Load Process, 41

• SSA Death Master File Incremental Load Process - Add, 42

• SSA Death Master File Incremental Load Process - Update, 43

• SSA Death Master File Incremental Load Process - Delete, 44

• TPA/Policy Admin/Customer Master Incremental Load Process - Add, 45

• TPA/Policy Admin/Customer Master Incremental Load Process - Update, 45

Initial Load ProcessThe inbound mappings read decedent information from different source systems, such as SSA Death Master File, TPA, Policy Admin, and Customer Master, and populate the landing tables after applying the relevant filters.

The following image shows the initial load process:

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.

SSA Death Master File Incremental Load Process - Add

If the first position in the delta SSA Death Master File is A or Blank, the incoming record type is Add.

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.

42 Chapter 4: Data Load Workflows

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.


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.

SSA Death Master File Incremental Load Process - Update

If the first position in the delta SSA Death Master File is C, the incoming record type is Update.

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.


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.


SSA Death Master File Incremental Load Process - Update 43


SSA Death Master File Incremental Load Process - Delete

If the first position in the delta SSA Death Master File is D, the incoming record type is Delete.

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.




TPA/Policy Admin/Customer Master Incremental Load Process - Add

The inbound mappings read decedent information add requests from different source systems, such as TPA, Policy Admin, and Customer Master, and populate the landing tables after applying the relevant filters.

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.


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.



TPA/Policy Admin/Customer Master Incremental Load Process - Update

The inbound mappings read decedent information update requests from different source systems, such as TPA, Policy Admin, and Customer Master, and populate the landing tables after applying the relevant filters.

The following image shows the incremental load process for an Update request:

TPA/Policy Admin/Customer Master Incremental Load Process - Add 45

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.


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.




C H A P T E R 5

Reference InformationThis chapter includes the following topic:

• Additional Resources, 47

Additional ResourcesBase 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.

Packages and Queries

For more information on the queries available in the packages, see the Packages_Queries.xls file available in the ZIP file that you downloaded from Informatica Marketplace.

Match and Merge

For more information about match rules, match columns, and merge paths, see the Match_Merge.xls file available in the ZIP file you downloaded from Informatica Marketplace.

47

I N D E X

Ccomponents

composite services 35custom tasks 40external match 22hierarchy 21IDD 36inbound mappings 22MDM hub 12outbound mappings 34source systems 11

configuration add cleanse library 8add user exit 9IDD 9import mappings 9import metadata 8post import 10

Ddata load workflows

initial 41non SSA - add 45non SSA - update 45

data load workflows (continued)SSA DMF - add 42SSA DMF - delete 44SSA DMF - update 43

MMDM hub

base objects 12custom tables 14data cleansing 18landing tables 13lookup tables 12match and merge 20packages 17staging tables 15trust 17user exits 19

Ooverview

architecture 4business case 2overview 1

48

informatica mdm multidomain edition - 1. - unclaimed life

Documents