Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Output Data Sample

Output Data Sample

The output data set contains the primary keys, customer ID, address ID, and address type for each customer. After the mapping that you define cleanses and standardizes the source data, it loads the data into the LGC Party to Billing Address Stg staging table.
The primary keys that the staging process generates are loaded into the PKEY_SRC_OBJECT and the ADDRESS_ID columns. The primary key values consist of a trimmed customer ID value that is concatenated with the |Billing constant.
The ADDRESS_TYPE column contains the BILL constant that is populated through the OP_BILLINGTYPE output port of the Expression transformation.
The following data extract shows a sample of the customer data that is loaded into the LGC Party to Billing Address Stg staging table:
PKEY_SRC_OBJECT
PARTY_ID
ADDRESS_ID
ADDRESS_TYPE
SLS2051|Billing
SLS2051
SLS2051|Billing
BILL
SLS2052|Billing
SLS2052
SLS2052|Billing
BILL
SLS2053|Billing
SLS2053
SLS2053|Billing
BILL
SLS2054|Billing
SLS2054
SLS2054|Billing
BILL
SLS2055|Billing
SLS2055
SLS2055|Billing
BILL
SLS2056|Billing
SLS2056
SLS2056|Billing
BILL
SLS2000|Billing
SLS2000
SLS2000|Billing
BILL

0 COMMENTS

We’d like to hear from you!