Applicant Data Mart ETL - Naming Standards
Informatica-IICS Naming Conventions:
We would follow these naming conventions when creating mapping jobs in IICS as we begin to build the etl process flow.
Mapping - Dimension build:
Mapping step1: CS100_TMP_<coretbl>
Mapping step2: CS200_WIP_<coretbl>
Mapping step3: CS300_INT_<coretbl>
Mapping step4: CS400_SCD_<DimTableName>
Mapping - Fact build:
Mapping step1: CS600_WIP_<FactTbl>
Mapping step2: CS700_INT_<FactTbl>
Mapping Step3: CS800_<FactTbl>
Mapping task could be named <Mapping_name>_MT
Taskflow could be named CS001_Applicant
Please note that not all dimension builds would have all 5 (or more) of these steps. All the intermediate tables (with suffixes _TMP,_WIP & _INT) should be built in UMS_INTEGRATION_DEV database and the final dimension tables and the fact table should be housed in UMS_DM_DEV database.
The core tables that are required for the admissions data mart build already exist in UMS_INTEGRATION_DEV, we brought these core tables as CS_SCD_<table_name> from STGDB into UMS_INTEGRATIION_DEV in one of our etl taskflows which would run daily before the applicant datamart build taskflow can be run.