F.1 Trade Finance Datamaps

This section provides the required datamaps for deriving and aggregating data. The datamaps appear in the order that processing must execute them during data loading. Where predecessors exist, processing of datamaps cannot begin the predecessor datamap has completed. Predecessors may be internal to the datamap type, or external to the datamap type, as shown in the following examples.

Example For Internal Predecessor

Processing can run the Frontofficetransactionparty_instnseqid datamap immediately after completion of Financialinstitution_fotpspopulation and Accounttoclientbank_fotpsinstitutioninsert.

Example For External Predecessor

Processing cannot run the Accountprofile_trade datamap until and unless the Frontofficetransactionpartyriskstage_entityactivityriskinsert datamap is run.

Note:

If there is a performance issue with the running sequence of datamaps, they can be re-arranged. However. the predecessor for the datamap must be completed before running the datamap. For example:

Run the following datamaps in order:
  1. FrontOfficeTransactionParty_InstnSeqID
  2. FrontOfficeTransactionParty_HoldingInstnSeqID If there is are performance issues with FrontOfficeTransactionParty_HoldingInstnSeqID, the datamap position can be rearranged in the batch script. Since there is the possibility that FrontOfficeTransactionParty_InstnSeqID is still running, the current datamap is waiting for the resources to be released.
The following sections describe the Trade Finance Datamaps:

Table F-1 Datamap Table Descriptions

Column Description
Datamap Number Unique, five-digit number that represents a particular datamap.
Datamap Name Unique name of each datamap.
Predecessor Indicator that processing of datamaps cannot begin until completion of predecessor datamaps.