35.3 Additional Configurations for Data Transformation
By default, Data Transformations are not parsed by lineage component due to an unstructured format of SQL coding in the Data Transformation. However, the lineage component provides an option to provide the Data Transformation Mapping in a metadata form and utilize it in the lineage output.
Configuring the Data Flow name and its Mapping
The data flow name such as the Post Load Change (PLC) component name of the DT and the corresponding Target and Source tables used in the Post Load Change (PLC) Component name must be updated in the table FSI_DE_POP_DT_DATA_FLOW_MAP as shown below:
Table 35-4 Data Flow name and its Mapping
| DATA_FLOW_NAME | TARGET_TABLE | TARGET_COLUMN | TARGET_MEMBER | MAP_TYPE_ID | MAP_TYPE | SOURCE_TABLE | SOURCE_COLUMN | SOURCE_MEMBER | KEY_COLUMN_FLAG |
|---|---|---|---|---|---|---|---|---|---|
| <<FUNCTIONNAME>> | STG_ACCT_CREDIT_SCORE_DETAILS | N_BEHAVIOUR_SCORE | - | 1 | Direct | STG_VEHICLE_DETAILS | N_NO_OF_DAYS_DRIVEN_PER_WEEK | - | - |
Adding the Data Transformation in Run Relationship
The data flow name which are provided in the Datal Flow and its Mapping table, is processed by the lineage component only if the Batch for the data Transformation is added in FSI_DE_POP_RUN_RELATIONSHIP. For more information, see the Configuring prerequisite Run/ Batch.