Applying Extended Data Model Columns to the Business Layer

After extending your data model using the steps in Adding New Data Model Columns, and loading your data by running the AMLDataLoad batch, the additional columns are available in the Staging layer. To move this data into the Business layer, which allows the data to be used throughout the application, you must then load the extended data.

To configure loading of extended data, follow these steps:

1. Create new data pipelines for each entity type you selected when creating the data model extension, using the steps in Creating Pipelines.
2. Open the pipeline in the Pipeline Designer.
3. Drag and drop two High Level Dataset widgets and configure the datasets, setting the Source Dataset Tables as the following tables, respectively:
   • Customer: Stage Party Master Extension and Customer Lookup
   • Account: Stage CASA Accounts Extension and Account Lookup
4. Create a join between these datasets using a Persist widget from the widgets pane located in the upper-right corner of the designer pane and configure Persist widget, setting the Target Table as the following tables:
   • Customer: Customer Dimension Extension
   • Account: Account Dimension Extension
5. In the Map section of the Persist widget configuration, map the columns.
   1. The following columns are mandatory and must be mapped as shown:

      Table 16-1 Customer Dimension Extension Table Source Value Column Mappings

      Sequence	Column Name	Logical Name	Stage Party Master Extension	Customer Lookup	Manual Expression
      1	N_CUST_EXT_SKEY	Customer Surrogate Key			FCC_CUST_DIM_EXT_SEQ.nextval
      2	N_CREATED_RUN_SKEY	Run Skey			$RUNSKEY
      3	N_CUST_ID	Customer Identifier		Customer Identifier
      4	F_LRI_FL	Latest Record Indicator			Y
      5	V_DATA_ORIGIN	Data Origin	Data Origin
      6	D_START_DATE	Start Date	Processing Date
      7	D_END_DATE	End Date			'31-DEC-2099'

      Table 16-2 Account Dimension Extension Table Source Value Column Mappings

      Sequence	Column Name	Logical Name	Stage Casa Accounts Extension	Account Lookup	Manual Expression
      1	N_ACCT_EXT_SKEY	Account Surrogate Key			FCC_ACCT_DIM_EXT_SEQ.nextval
      2	N_CREATED_RUN_SKEY	Run Skey			$RUNSKEY
      3	N_ACCT_ID	Account ID		Account Identifier
      4	F_LRI_FL	Latest Record Indicator			Y
      5	V_DATA_ORIGIN	Data Origin	Data Origin
      6	D_START_DATE	Start Date	Processing Date
      7	D_END_DATE	End Date			'31-12-2099'

   2. Map the columns you created to extend the data model as needed.
6. Create Jobs for this pipeline using the steps in Creating Jobs.
7. Create a new task for each entity type you selected when creating the data model extension and add it to the Ingestion batch using the following precedence:
   • CustomerExtension task: Customer -> CustomerExtension -> CustomerAddData
   • AccountExtension task: Account -> AccountExtension -> AccountGroup

   Note:

   The names used here are as found in the out of box batches and tasks provided with the application. If you are using other batches and tasks in your implementation, follow the naming convention provided in your specific batches and tasks.