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.
   For example:

   • Customer
   • Account

   Note:

   The Pipeline Type must be selected as Data.
2. Open the newly created data pipeline(s) in the Pipeline Designer.
3. Drag and drop two High Level Dataset widgets for each pipeline and configure the datasets.
   1. Provide a name for each widget. For example,
      • Customer Pipeline:
        • Stage Party Master Extension
        • Customer Lookup
      • Account pipeline:
        • Stage Casa Accounts Extension
        • Account Lookup
   2. Set the Tables for each HLD widget as the following:
      • Customer pipeline:
        • The Stage Party Master Extension widget must be mapped to the Stage Party Master Extension table.
        • The Customer Lookup widget must be mapped to the Customer Lookup table where the datatype of V_CUST_INTRL_ID is VARCHAR2(50 ).
      • Account pipeline:
        • The Stage Casa Accounts Extension widget must be mapped to the Stage Casa Accounts Extension table.
        • The Account Lookup widget must be mapped to the Account Lookup table.
   3. Create Filters on the tables as shown below:
      • Stage Party Master Extension:
        • Processing Date = TO_DATE( $MISDATE, 'YYYY-MM-DD')
        • Data Origin = $DATAORIGIN
      • Stage Casa Account Extension:
        • Processing Date = TO_DATE( $MISDATE, 'YYYY-MM-DD')
        • Load Run Identifier = 1
        • Data Origin = $DATAORIGIN
   4. Save the HLD widget.
4. In the Pipeline Designer, drag and drop a Persist widget from the widgets pane located in the upper-right corner of the designer pane. Connect the HLD widgets to the Persist widget using the connectors. This step should be repeated for each pipeline.
5. Configure the Persist widget, using the steps in Creating Persist.
   1. In Source Datasets, link the tables as follows:
      • Customer Pipeline:
        • Stage Party Master Extension
        • Customer Lookup
      • Account pipeline:
        • Stage Casa Accounts Extension
        • Account Lookup
   2. Set the Target Table as the following tables:
      • Customer pipeline: Customer Dimension Extension
      • Account pipeline: Account Dimension Extension
   3. Set the Persist Type as SCD.
   4. In the Output pane of the Join section, select the join tables from the drop-down lists.
      • Customer: Set the first table as Stage Party Master Extension , the Join Operator as Inner Join, and the second table as Customer Lookup.
      • Account: Set the first table as Stage Casa Accounts Extension , the Join Operator as Inner Join, and the second table as Account Lookup

      Note:

      Tables must be mapped in the order listed above. The Stage table must be mapped before the Lookup table.
   5. In the Output pane of the Join section, map the columns as shown in the following tables:

      Table 16-1 Customer Column Joins

      Table Name	Column Name	Join Operator	Table Name	Column Name
      Stage Party Master Extension	Party Identifier	=	Customer Lookup	Customer Identifier Note: You must join to the first Customer Identifier listed, which should be of data type VARCHAR2(50 )
      Stage Party Master Extension	Data Origin	=	Customer Lookup	Data Origin
      Customer Lookup	Data Origin	=		$DATAORIGIN

      Table 16-2 Account Column Joins

      Table Name	Column Name	Join Operator	Table Name	Column Name
      Stage Casa Accounts Extension	Account Identifier	=	Account Lookup	Account Identifier
      Stage Casa Accounts Extension	Data Origin	=	Account Lookup	Data Origin
      Account Lookup	Data Origin	=		$DATAORIGIN

   6. In the Map section of the Persist widget configuration, map the columns. The following columns are mandatory and must be mapped as shown. Columns can be mapped in any order.

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

      Column Name	Stage Party Master Extension Table	SCD Option Type	Customer Lookup Table	Manual Expression
      Customer Surrogate Key		Surrogate		FCC_CUST_DIM_EXT_SEQ.nextval
      Run Skey		Direct		$RUNSKEY
      Party Identifier		Unique	Customer Identifier
      Latest Record Indicator		Direct		'Y'
      Data Origin	Data Origin	Direct
      Start Date	Processing Date	Direct
      End Date		Direct		'31-DEC-2099'

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

      Logical Name	Stage CASA Accounts Extension	SCD Option Type	Account Lookup	Manual Expression
      Account Surrogate Key		Surrogate		FCC_ACCT_DIM_EXT_SEQ.nextval
      Run Skey		Direct		$RUNSKEY
      Account ID		Unique	Account Identifier
      Latest Record Indicator		Direct		'Y'
      Data Origin	Data Origin	Direct
      Start Date	Processing Date	Direct
      End Date		Direct		'31-12-2099'

   7. 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.