6.6 Loading Mapper Maintenance through Backend

Load each Physical table in Atomic Schema with V_MAP_ID as mentioned against each mapper, V_MEMBER_1

=> Customer Specific Value Dimension's Member Code, V_MEMBER_2 => Standard Dimension’s Member Code.

Table 6-2 The list and details of the Mapper physical tables

Physical Table	V_MAP_ID
MAP_MITG_TYP_STD_MITGN_TYP	1514359498413
MAP_DIM_IRC_STD_IRC	1511442223838
MAP_PROD_CODE_STD_PROD_TYPE	1511441227779
MAP_DIM_LOB_STD_LOB	1511442482993
MAP_CRDLN_PUR_STD_CRDLN_PUR	1511528494678
MAP_PARTY_TYP_STD_PARTY_TYP	1511441945154
MAP_BAL_CAT_STD_BAL_CAT	1514359600480
MAP_CRDLN_TYP_STD_CRDLN_TYP	1511527713328
MAP_CREDIT_SCR_MDL_REG_MDL	1497513837744
MAP_DIM_GL_ACCT_STD_GL_TYPE	1523447233065
MAP_GL_CODE_REP_LINE	1494610765133
MAP_RECVR_TYP_STD_RECVR_TYP	1524045220417
MAP_VEHCL_TYP_STD_VEHCL_TYP	1524044256132
MAP_WRTOFF_STD_WRTOFF_REASN	1524044617123