8 Configuring Entity UDPs for Application Data Interface of Data Integration Hub

In OFSAA DIH Application, the uploaded data model is visible as Application Data Interface (ADI). These ADI names are given through erwin data model entity UDP for each table. For any new table addition, which is added as a part of customization must consist of a valid value in the following entity UDPs to get the proper ADI names in DIH.

· OFSAA Data Interface Name: This Entity UDP expects the logical name of the table or logical name for a group of tables, which will be displayed as an ADI in DIH. This UDP is mandatory for all Stage and Results tables to get a valid ADI in DIH, which corresponds to each table in the data model.

· OFSAA Data Interface Subtype: This Entity UDP expects the logical name of a table where the table is part of a group of tables where we have a group name in OFSAA Data Interface Name UDP. This UDP is optional and applicable only if you have a one OFSAA Data Interface Name against a group of tables.

Topics:

· Sample for OFSDF

· Sample for OIDF

Sample for OFSDF

For illustration, see the following samples for OFSDF:

· STG_CASA, STG_LOAN_CONTRACTS, STG_TD_CONTRACTS, and FCT_COMMON_ACCOUNT_SUMMARY are defined as a group of tables, and the UDPs for the tables are given in the following table:

Table 3: Sample OFSDF Entity UDP for a group of tables
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_CASA	Customer Account	CASA Contracts
STG_LOAN_CONTRACTS	Customer Account	Loan Contracts
STG_TD_CONTRACTS	Customer Account	Term Deposits
FCT_COMMON_ACCOUNT_SUMMARY	Customer Account	Common Account Summary

· If there are Stage and Fact tables for a similar purpose, you must define the same name for the OFSAA Data Interface Name and OFSAA Data Interface Subtype.

Table 4: Sample OFSDF Entity UDP for a similar purpose Stage and Fact tables
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_ACCT_FEATURE_MAP	Account Feature Map	Account Feature Map
FCT_ACCOUNT_FEATURE_MAP	Account Feature Map	Account Feature Map

· If you have independent tables such as only one table, which is either a stage or dim or fact, then the OFSAA Data Interface Subtype can be left blank.

Table 5: Sample OFSDF Entity UDP for an independent table
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_VEHICLE_MASTER	Vehicle Master
FCT_TXN_CHANNEL	Transaction Channel
DIM_ACCOUNT	Account Dimension

Sample for OIDF

For illustration, see the following samples for OIDF:

· STG_ANNUITY_CONTRACTS, STG_LOAN_CONTRACTS, STG_RETIREMENT_ACCOUNTS, and FCT_COMMON_POLICY_SUMMARY are defined as a group of tables, and the UDPs for the tables are given in the following table:

Table 6: Sample OIDF Entity UDP for a group of tables
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_ANNUITY_CONTRACTS	Customer Account	Annuity Contracts
STG_LOAN_CONTRACTS	Customer Account	Loan Contracts
STG_RETIREMENT_ACCOUNTS	Customer Account	Retirement Accounts
FCT_COMMON_POLICY_SUMMARY	Customer Account	Common Policy Summary

· If there are Stage and Fact tables for a similar purpose, you must define the same name for the OFSAA Data Interface Name and OFSAA Data Interface Subtype

Table 7: Sample OIDF Entity UDP for a similar purpose Stage and Fact tables
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_PARTY_ROLE_MAP	Party Role Map	Party Role Map
FCT_PARTY_ROLE_MAP	Party Role Map	Party Role Map

· If you have independent tables such as only one table, which is either a stage or dim or fact, then the OFSAA Data Interface Subtype can be left blank.

Table 8: Sample OIDF Entity UDP for an independent table
TABLE_NAME	OFSAA Data Interface Name	OFSAA Data Interface Subtype
STG_VEHICLE_MASTER	Vehicle Master
FCT_CLAIM_TRANSACTION	Claim Transaction
DIM_ACCOUNT	Account Dimension