4.4.2.3 Processing Datamaps

This section provides the required datamaps for deriving and aggregating data based on the solution. Discussions of the datamaps appear in the order that processing must execute them during data loading, and include tables that describe each datamap. Datamap numbers that the accompanying tables provide also reflect this order.

Where predecessors exist, processing of datamaps cannot begin until completion of predecessor datamaps. These dependencies, or predecessors, may be internal to the datamap type, or external to the datamap type such as Summary datamaps dependent on watch list datamaps.

Note:

If there is any performance issue with the running sequence of datamaps, it can be re-arranged. However. the predecessor for the datamap must be completed before running the datamap.

Example: The following is the order for the datamap to run:

FrontOfficeTransactionParty_InstnSeqID 
FrontOfficeTransactionParty_HoldingInstnSeqID

If there is any performance issue with the datamap FrontOfficeTransactionParty_HoldingInstnSeqID, the datamap position can be rearranged in the batch script. Since there is the possibility that the previous process (FrontOfficeTransactionParty_InstnSeqID) is still running, the current datamap is waiting for the resources to be released.

Example for Internal Dependency

For example, processing can run the FrontOfficeTransactionParty_InstnSeqID datamap immediately after completion of FinancialInstitution_FOTPSPopulation and AccountToClientBank_FOTPSInstitutionInsert.

Example for External Dependency

Processing cannot run the AccountProfile_Trade datamap until and unless the FrontOfficeTransactionPartyRiskStage_EntityActivityRiskInsert datamap is run.