F.18 Processing BD Datamaps
The following table provides a list of datamaps and description for each datamap.
These datamaps are listed in order.
Table F-18 BD Datamaps
| Datamap Number | Datamap Name | Description |
|---|---|---|
| 10010 | EmployeeControlledAccount | This datamap creates entry for Employee personal accounts and Employee Related account using same tax ID |
| 60010 | PortfolioManagerPosition | The datamap is used to populate the portfolio manager positions. It reads tables (Account and Account Position), populated while executing Pre-processors and creates records to populate the PORTFOLIO_MGR_POSN table. |
| 60020 | AccountGroupProductAllocation | The datamap captures the actual proportionate distribution of holdings for an account group aggregated by reporting classifications. |
| 60030 | AccountProductAllocation | The datamap captures the actual proportionate distribution of holdings for an account aggregated by product classifications. |
| 60040 | UncoveredOptionExposureDaily | This datamap derives the value from the uncvrd_optns_smry_dly table and insert/updates the records in UNCVRD_OPTNS_EXPOSURE_DLY table. |
| 60050 | InvestmentAdvisorProfile | This datamap updates the Investment Manager Summary Month table from the daily activity |
| 60060 | RegisteredRepresentativeProfile | This datamap updates the Registered Representative Summary Month table with daily activity |
| 60070 | RegOToBorrower | This datamap use the fuzzy match logic to match the Regulation O list against the Borrower. |
| 60080 | InterestedPartyToEmployee | This datamap use fuzzy matcher to match Interested Parties in Account Scheduled Event table against Employee name. |
| 50010 | Customer_TotAcctUpd | This datamap calculates the total number of accounts for an institutional customer. |
| 10015 | FrontOfficeTransactionParty_SecondaryN ames | This datamap kicks off the Pass Thru process. It generates second orgininator and beneficiary records for Front Office Transaction. It also sets the pass thru flag based on the a set of expressions. |
| 10020 | FinancialInstitution_ThomsonDataInstituti onInsert | This datamap builds the many-to-one relationship in INSTN_MASTER that is the relationships between bics and feds with INSTN_SEQ_ID. The INSTN_MASTER table gets populated from BANK_REFERENCE_STAGE table. |
| 10030 | AccountToClientBank_ThomsonDataInstit utionInsert | This datamap builds the many-to-one relationship in ACCT_ID_INSTN_ID_MAP that is the relationships between bics and feds with INSTN_SEQ_ID. The ACCT_ID_INSTN_ID_MAP table gets populated from BANK_REFERENCE_STAGE table. |
| 10040 | FinancialInstitution_AIIMSPopulation | This datamap inserts new records in Financial Institution table from the ACCT_INSTN_MAP_STAGE table, the datamap creates unique identifiers for banks based on the third party vendors. |
| 10050 | AccountToClientBank_AIIMSInstitutionIns ert | This datamap creates unique identifiers for banks based BIC records on the third party vendors. 1) Retrieve Institution information from ACCT_INSTN_MAP_STAGE in comparison of INSTN_MASTER and loads it into ACCT_ID_INSTN_ID_MAP. |
| 10060 | AccountToClientBank_InstitutionInsert | This datamap creates unique identifiers for banks based on the third party vendors. 1) Retrieve Institution information from ACCT_INSTN_MAP_STAGE and load it into ACCT_ID_INSTN_ID_MAP. |
| 10070 | AccountToClientBank_InstitutionUpd | This datamap updates unique identifiers for banks based on the third party vendors. 1) Retrieve Institution information from ACCT_INSTN_MAP_STAGE and update it into ACCT_ID_INSTN_ID_MAP. |
| 10080 | FinancialInstitution_FOTPSPopulation | This datamap inserts new records in Financial Institution table for the institutions found in front office transaction party table for both party ID type code as IA and BIC, INSTN_SEQ_ID are OFSAAI generated. |
| 10090 | AccountToClientBank_FOTPSInstitutionIns ert | This datamap marks all institutions with an OFSAAI generated
INTSN_SEQ_ID in FOTPS.
1) Prior to this datamap execution the predecessor datamaps finds the new institutions from the transaction data and loads them in the INSTITUTION_MASTER. 2) This data map finds the new institutions from the transaction data for IA and BIC party ID type and loads them in the ACCT_ID_INSTN_ID_MAP table using OFSAAI generated INTSN_SEQ_ID from INSTITUTION_MASTER. |
| 10100 | AccountManagementStage | This datamap identifies the relationship between accounts and the employees who have a management role on that account. Management roles include positions such as Financial Advisor, Banker, and Registered Representative. |
| 10110 | LoanProfile_LoanProfileStage | This datamap is used to populate Loan Summary from LOAN_SMRY_MNTH_STAGE table. 1) Select set of information/columns from LOAN_SMRY_MNTH_STAGE table, if the record is new insert the details in LOAN_SMRY_MNTH else update the existing record. |
| 10112 | ServiceTeam_SprvsncdUpd | This datamap updates service team table with the Employee Maximum Supervision Code. |
| 10113 | InvestmentAdvisor_MangdAcctUpd | This datamap updates ManagedAccountNetworth and ActiveSubAccountCount column in InvestmentAdvisor table. |
| 10114 | Security_CIRRatingUpd | This datamap derives the column CIRRating and updates back to Security table. |
| 10116 | BackOfficeTransaction_CollateralUpd | This datamap updates Collateral Percentage , Collateral Value for that transaction. |
| 10120 | BackOfficeTransaction_OriginalTransactio nReversalUpd | This datamap handles reverserals for Back Office Transactions.
1) Select the set of information from today's BackOfficeTransaction to update records with columns CXL_PAIR_TRXN_INTRL_ID in BackOfficeTransaction table. 2) Updates the "cancellation pair" column in the original back office transaction table as per the "Internal ID" of the reversing or adjusting record. |
| 10130 | BackOfficeTransaction_CancelledTransacti onReversalCreditUpd | This datamap updates Cancelled Transaction details for CREDIT record
of Back Office Transactions.
1) Finds original-reversal back-office transaction pairs, links them via their respective transaction identifiers. 2) For original transactions: update Canceled Pairing Transaction Identifier by reversal transaction ID; 3) For reversal transactions: update the transaction's Debit Credit Code, Unit Quantity, Transaction Amount, Canceled Pairing Transaction Identifier by original transaction's field values, and Mantas Transaction Adjustment Code by 'REV'. |
| 10140 | BackOfficeTransaction_CancelledTransacti onReversalDebitUpd | This datamap updates Cancelled Transaction details for DEBIT record
of Back Office Transactions.
1) Finds original-reversal back-office transaction pairs, links them via their respective transaction identifiers. 2) For original transactions: update Canceled Pairing Transaction Identifier by reversal transaction ID; 3) For reversal transactions: update the transaction's Debit Credit Code, Unit Quantity, Transaction Amount, Canceled Pairing Transaction Identifier by original transaction's field values, and Mantas Transaction Adjustment Code by 'REV'. |
| 10150 | FrontOfficeTransactionParty_InstnSeqID | This datamap marks all the records of FO_TRXN_PARTY_STAGE table with institutions by OFSAAI generated INTSN_SEQ_ID. |
| 10160 | FrontOfficeTransactionParty_HoldingInstn SeqID | This datamap marks all the records of FO_TRXN_PARTY_STAGE table with
institutions by OFSAAI generated INTSN_SEQ_ID.
1) To update HOLDG_INSTN_SEQ_ID and HOLDG_ADDR_CNTRY_CD based on DATA_DUMP_DT and country code (BASE_COUNTRY). |
| 10170 | FinancialInstitution_AnticipatoryProfile | This datamap inserts new records in Financial Institution table for the institutions found in Anticipatory Profile table, INSTN_SEQ_ID are OFSAAI generated. This datamap should be executed before AccountToClientBank_AnticipatoryProfile datamap as generated INSTN_SEQ_ID will be used to populate Anticipatory Profile table. |
| 10180 | AccountToClientBank_AnticipatoryProfile | This datamap marks all institutions with an OFSAAI generated
INTSN_SEQ_ID in FOTPS.
1) Prior to this datamap execution the predecessor datamaps finds the new NTCPTRY_PRFL from the transaction data and loads them in the INSTITUTION_MASTER. 2) This data map finds the new institutions from the NTCPTRY_PRFL data and loads them in the ACCT_ID_INSTN_ID_MAP table using OFSAAI generated INTSN_SEQ_ID from INSTITUTION_MASTER. |
| 10190 | AnticipatoryProfile_AccountToClientBank | This datamap marks all institutions with an OFSAAI generated INTSN_SEQ_ID in the Anticipatory Profile tables. It should be executed after FinancialInstitution_AnticipatoryProfile and AccountToClientBank_AnticipatoryProfile datamaps are executed. |
| 50020 | DailyAggregateStage | This datamap populates DAILY_AGG_STAGE table with aggregated TRADE Data. DAILY_AGG_STAGE table in turn is used to populate OFFSETING_ACCT_PAIRS and TRADE_DAILY_TOT_CT_STAGE tables. |
| 50030 | OffsettingAccountPairStage | This datamap is used to populate OFFSETING_ACCT_PAIRS table by self-joining the table DAILY_AGG_STAGE to generate offsetting trade account pairs.The accounts have the lower ACCT_INTRL_ID while the offsetting accounts have the higher ACCT_INTRL_ID. |
| 50040 | TradeDailyTotalCountStage | This datamap aggregates the total trades done by that account for the current processing day. |
| 10200 | CustomerAccountStage_FrontOfficeTrans actionParty | This datamap populates the Customer Account Stage table with the Cust-Acct pairs which appears inFOTPS with Party type as IA. |
| 10210 | FrontOfficeTransaction_UnrelatedPartyUp d | This datamap updates the FOT table for records where UNRLTD_PARTY_FL is 'Y' with a value as 'N', by determining the pairs of parties (internal) in the role of Orig & Benef having either common Tax ID/Common Customer/Common HH. |
| 10220 | FinancialInstitution_SettlementInstruction | This datamap inserts new records in Financial Institution records for the institutions found in INSTRUCTION that have not been previously identified, INSTN_SEQ_ID are OFSAAI generated. This datamap should be executed before AccountToClientBank_SettlementInstruction datamap. |
| 10230 | AccountToClientBank_SettlementInstructi on | This datamap marks all institutions with an OFSAAI generated
INTSN_SEQ_ID in FOTPS.
1) Prior to this datamap execution the predecessor datamaps finds the new INSTRUCTION from the transaction data and loads them in the INSTITUTION_MASTER. 2) This data map finds the new institutions from the INSTRUCTION data and loads them in the ACCT_ID_INSTN_ID_MAP table using OFSAAI generated INTSN_SEQ_ID from INSTITUTION_MASTER. . |
| 10240 | SettlementInstruction_AccountToClientBa nk | This datamap updates Destination Institution and Physical Delivery Institution in INSTRUCTION table using the values from ACCT_ID_INSTN_ID_MAP table. |
| 40010 | FinancialInstitution_InsuranceTransaction | This datamap inserts new records in Financial Institution table for the institutions found in Insurance Transactions, INSTN_SEQ_ID are OFSAAI generated. This datamap should be executed before AccountToClientBank_InsuranceTransaction datamap as generated INSTN_SEQ_ID will be used to populate Anticipatory Profile table. |
| 40020 | AccountToClientBank_InsuranceTransacti on | This datamap marks all institutions with an OFSAAI generated
INTSN_SEQ_ID in FOTPS.
1) Prior to this datamap execution the predecessor datamaps finds the new institutions from the transaction data and loads them in the INSTITUTION_MASTER. 2) This data map finds the new institutions from the INSURANCE_TRXN data and loads them in the ACCT_ID_INSTN_ID_MAP table using OFSAAI generated INTSN_SEQ_ID from INSTITUTION_MASTER. |
| 40030 | InsuranceTransaction_AccountToClientBa nk | This datamap marks all institutions with an OFSAAI generated Institution Identifier in Insurance Transaction records. 1) Prior to this datamap execution Financial Institution and Account To Client Bank records are inserted. 2) Henceforth this datamap uses the Account To Client Bank table and updates Institution Identifier in Insurance table. |
| 10245 | WLMProcessingLock | This datamap applies lock to restrict UI accessibility for Watch list Management. |
| 10250 | WatchListEntry_WatchListEntryCurrDayIns ert | This datamap checks for records in watch list from source files for the current day, if there is no records, create the current day watch list records from the previous day. |
| 10260 | WatchListAudit_StatusUpd | This datamap take care of watchlist table for the modifications of the WL based on the new user interface WL utility. |
| 10270 | WatchList_WatchListSourceAuditInsert | This datamap takes into account the modifications of the watchlist
based on the new user interface WL utility.
1) Get all the records that are active from audit table. Order by created time. 2) Take the latest change for each LIST_SRC_CD Watch List and insert records in WATCH_LIST_SOURCE table. |
| 10280 | WatchList_WatchListSourceAuditUpd | This datamap takes into account the modifications of the watchlist
based on the new user interface WL utility.
1) Get all the records that are active from audit table. Order by created time. 2) Take the latest change for each LIST_SRC_CD Watch List and update records in WATCH_LIST_SOURCE table. |
| 10290 | WatchList_WatchListSourceUpd | This datamap takes into account the modifications of the watchlist
based on the new user interface WL utility.
1) Get all the records that are active from audit table. Order by created time. 2) Take the latest change for each LIST_SRC_CD Watch List and update records in WATCH_LIST_SOURCE table. |
| 10300 | WatchListEntry_WatchListAuditUpd | This datamap takes care of watch list entry table for the modifications of the WL based on the new user interface WL utility. |
| 10310 | WatchListEntryAudit_WatchListEntryUpda te | Thisdatamap take care of watchlist entry audit table for the modifications of the WL based on the new user interface WL utility. |
| 10320 | Customer_KYCRiskUpd | This datamap calculates risk, If the risk was List driven, then this can ignore that record. If it was BUS/GEO driven and there is KYC risk. Apply KYC Risk in Customer table. |
| 60090 | CorrespondentBankToPeerGroup | This datamap populates the CLIENT_BANK_PEER_GRP table by associating peer group identifiers in the ACCT_PEER_GRP table with institution identifiers in the ACCT_ID_INSTN_ID_MAP table. |
| 10330 | DerivedAddress_SettlementInstructionIns ert | This datamap inserts new addresses in the Derived Address table. It derives the addresses from the INSTRUCTION table. |
| 10340 | DerivedAddress_SettlementInstructionUp d | This datamap derives the addresses from the INSTRUCTION table. It updates addresses in the Derived Address table, if already existing. |
| 10350 | SettlementInstruction_PhysicalDlvryAddr Upd | This datamap updates Mantas Physical Delivery Address Identifier in INSTRUCTION table. |
| 10360 | DerivedAddress_FrontOfficeTransactioPar tyStageInsert | This datamap selects the distinct set of addresses from today's front-office transactions and if non-existent, inserts new address records into Derived Address. |
| 10370 | DerivedAddress_FrontOfficeTransactioPar tyStageUpd | This datamap selects the distinct set of addresses from today'sfront-office transactions and if existent, updates new address records into Derived Address. |
| 10380 | FrontOfficeTransactionParty_DerivedAddr ess | This datamap maintains the addresses in the DerivedAddress table. It derives the addresses from the FrontOfficeTransactionParty table. |
| 40040 | DerivedAddress_InsuranceTransactionInse rt | This datamap derives the addresses from the INSURANCE table, and inserts the addresses in to the Derived Address table. |
| 40050 | DerivedAddress_InsuranceTransactionUpd | This datamap derives the addresses from the INSURANCE table. If the address already exists in Derived Address table, it will update the addresses in to the Derived Address table. |
| 40060 | InsuranceTransaction_InstitutionAddrUpd | This datamap updates Mantas Institution Address Identifier in the Insurance Transaction table. 1) A new record is created in Derived Address table prior to this datamap execution. 2) Update the same Derived Address Sequence ID in INSURANCE_TRXN for CP_ADDR_MSTR_SEQ_ID column. |
| 40070 | DerivedEntity_InsuranceTransactionInsert | This datamap maintains the External Entity table. It derives the entities from the INSURANCE table on current processing date. |
| 40080 | DerivedEntity_InsuranceTransactionUpd | This datamap maintains the External Entity table. It derives the entities from the INSURANCE table on current processing date. |
| 10390 | DerivedEntity_FrontOfficeTransactionPart yInsert | This datamap maintains the External Entity table. It derives the entities from the Front Office and Front Office Party transaction table. |
| 10400 | DerivedEntity_FrontOfficeTransactionPart yUpd | This datamap maintains the External Entity table. It derives the entities from the Front Office and Front Office Party transaction table. |
| 10410 | DerivedEntity_SettlementInstructionInsert | This datamap maintains the External Entity table. It derives the entities from the Instruction table on current processing date. |
| 10420 | DerivedEntity_SettlementInstructionUpd | This datamap maintains the External Entity table. It derives the entities from the INSTRUCTION table. 1) Select the distinct set of names, accounts, institutions from today's Instructions and updates matching records in the External Entity table. |
| 10430 | CorrespondentBank_FrontOfficeTransacti onPartyStageInsert | This datamap populates the client bank table for current day transactions where there is an institution involved. |
| 10440 | CorrespondentBank_FrontOfficeTransacti onPartyStageUpd | This datamap maintains the Correspondent Bank table. Itderives the records from the FOTPS table. If there is an existing correspond bank record available, this datamap updates the LAST_ACTVY_DT for that record. |
| 10450 | WatchListStagingTable_WatchList | This datamap determines changes in the Watch List table Each entry is classified as Add, No Change, or Retire based on the comparison of the current-day watch list data to the previous-day watch list data. |
| 10460 | WatchListStagingTable_WatchListInstnIDU pd | This datamap only processes watch list entries that are External Accounts, Financial Institutions, and Internal Accounts. 1) It updates the Watch List Stage table with the corresponding Institution Sequence ID of the institution or account. |
| 10470 | PreviousWatchList_WatchList | This datamap save off current day's watch list records into PREV_WATCH_LIST |
| 10480 | DerivedAddress_WatchListNewCountries | This datamap inserts new countries from WL in the derived addresses table. |
| 10485 | WLMProcessingUnlock | This datamap releases the lock for Watch list Management. |
| 10490 | LinkStaging_FrontOfficeTransactionParty | This datamap loads the Link Stage with any entity associations from FOTPS, depending on the combination of Link Type Code defined. |
| 40090 | LinkStaging_InsTrxnDerivedEntDerivedAd d | This datamap loads the Link Stage with any entity associations from INSURANCE. |
| 10500 | LinkStaging_InstructionDerivedEntDerive dAdd | This datamap loads the Link Stage with any entity associations from instruction. Define the entity association based on existence of entity and address associations in data. |
| 10510 | NameMatchStaging | This datamap use fuzzy match to matchCandidate Name against the List Name and inserts records in Name Match Stage table. |
| 10520 | WatchListStagingTable_NameMatchStageI nsert | This datamap is a wrapper for the fuzzy matching mappings and scripts. 1) For each processing day, this datamap joins fuzzy names to their matched watch list records to create additional watch list records for subsequent application to transactional tables. |
| 10530 | DerivedEntityLink_LinkStage | This datamap selects the external entity links from today's Link Stage table and insert records in External Entity Link table in associations to various link tables. |
| 10540 | DerivedEntitytoDerivedAddress_LinkStage | This datamap writes link-stage associations to various link tables in External Entity Address Table. |
| 10550 | DerivedEntitytoInternalAccount_LinkStage | This datamap writes link-stage associations to various link tables in External Entity Account Table. |
| 10560 | DerivedAddresstoInternalAccount_LinkSta ge | This datamap writes link-stage associations to various link tables in Derived Account Address Table. |
| 10570 | WatchListStagingTable2_WatchListStage2 AcctExistence | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with ACCT entity. 2) For IA (ACCT table) watch list entries, the error status is assigned if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10580 | WatchListStagingTable2_WatchListStage2 CBExistence | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with CLIENT_BANK entity. 2) Evaluates the existence of the CLIENT_BANK entity and assigns a 'Warning"" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10590 | WatchListStagingTable2_WatchListStage2 CustExistence | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with CUST entity. 2) For CU (CUST table) watch list entries, the error status is assigned if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10600 | WatchListStagingTable2_WatchListStage2 DAExistence | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with DERIVED_ADDRESS entity. 2) Evaluates the existence of the DERIVED_ADDRESS record and assigns status to the record accordingly. |
| 10610 | WatchListStagingTable2_WatchListStage2 EEExistence | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with EXTERNAL_ENTITY entity. 2) Evaluates the existence of the EXTERNAL_ENTITY record and assigns a 'Warning"""" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10620 | WatchListStagingTable2_WatchListStage | Thisdatamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Check for watch list stage CUST_INTRL_ID flag if it is 'Y' means that this name is fuzzy matched. 2) Insert the watch list entry into the second processing table that is Watch list stage 2 table for both the fuzzy matched as well as exact name records. |
| 10630 | WatchListStagingTable2_AcctListMembers hipUpd | The datamap checks for entry membership in the corresponding entity list membership table. |
| 10640 | WatchListStagingTable2_CBListMembersh ipUpd | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with CB_LIST_MEMBERSHIP entity. 2) Evaluates the existence of the CB_LIST_MEMBERSHIP record and assigns a 'Warning"" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10650 | WatchListStagingTable2_CustListMember shipUpd | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with CUST_LIST_MEMBERSHIP entity. 2) Evaluates the existence of the CUST_LIST_MEMBERSHIP record and assigns a 'Warning"" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10660 | WatchListStagingTable2_EEListMembershi pUpd | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with EXTERNAL_NTITY_LIST_MEMBERSHIP entity. 2) Evaluates the existence of the EXTERNAL_NTITY_LIST_MEMBERSHIP record and assigns a 'Warning"" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10670 | WatchListStagingTable2_EEListMembershi pStatusUpd |
This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) It validates the list membership status of External Entities whose Last Activity Date is earlier than the current date. 2) Update the status of the watch list entry based the existence or non-existence of a corresponding list membership record. |
| 10680 | WatchListStagingTable2_DAListMembersh ipUpd |
This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) Processes all watch list entries that have a possible match with DERIVED_ADDR_LIST_MEMBERSHIP entity. 2) Evaluates the existence of the DERIVED_ADDR_LIST_MEMBERSHIP record and assigns a 'Warning"" status to the record if the entity does not exist in the entity table because these entity records are expected to exist. |
| 10690 | WatchListStagingTable2_DAListMembersh ipStatusUpd | This datamap validates each watch list entry and inserts into the processing table WATCH_LIST_STAGE2. 1) It validates the list membership status of DERIVED_ADDRESS whose Last Activity Date is earlier than the current date. 2) Update the status of the watch list entry based the existence or non-existence of a corresponding list membership record. |
| 10700 | WatchListStagingTable2_WatchListStage2 SeqIdUpd | This datamap updates the list risk of each valid watch list entity based on the entity Sequence ID. The datamap sets various flags and derives the highest List Risk value for each entity on the watch list. |
| 10710 | WatchListStagingTable2_WatchListStage2I ntrlIdUpd | This datamap updates the list risk of each valid watch list entity based on the entity Internal ID. The datamap sets various flags and derives the highest List Risk value for each entity on the watch list. |
| 10720 | Customer_WatchListStage2ListRisk | This datamap calculates the customer's effective risk and set the risk factor if the risk is not found for the current day in watch list stage table. After calculating the risk updates the CUST table. Use nulls for the List Risk and the List Source Code. |
| 10730 | CorrespondentBank_WatchListStage2Effe ctiveRisk | This datamap calculates the Client Bank Effective Risk and applies the Effective Risk and the List Risk to the CLIENT_BANKrecord. |
| 10740 | Customer_WatchListStage2EffectiveRisk | This datamap calculates the Effective Risk of Customer and applies the Effective Risk and the List Risk to the CUST record. |
| 10750 | DerivedAddress_WatchListStage2Effective Risk | This datamap calculates the Effective Risk of all derived address entities and applies the Effective Risk and the List Risk to the DERIVED_ADDRESS record. |
| 10760 | DerivedEntity_WatchListStage2EffectiveRi sk | This datamap calculates the Effective Risk of all external entities and applies the Effective Risk and the List Risk to the EXTERNAL_ENTITY record. |
| 10770 | WatchListStagingTable2_WatchListStage2 SeqId | This datamap calculates the Effective Risk of all entities and applies the Effective Risk and the List Risk to the entity record where sequence ID is not null. |
| 10780 | AccountListMembership_WatchListStage2 Insert | This datamap inserts List Membership records for entities into ACCT_LIST_MEMBERSHIP table that are new to a list. |
| 10790 | AccountListMembership_WatchListStage2 Upd | This datamap updates the existing retired ACCT_LIST_MEMBERSHIP records by setting List Removal Date to the current processing date. |
| 10800 | CorrespondentBankListMembership_Watc hListStage2Insert | This datamap inserts List Membership records for entities that are new to a list into CB_LIST_MEMBERSHIP table. |
| 10810 | CorrespondentBankListMembership_Watc hListStage2Upd | This datamap updates the existing retired CB_LIST_MEMBERSHIP records by setting List Removal Date to the current processing date. |
| 10820 | CustomerListMembership_WatchListStage 2Insert | This datamap inserts List Membership records for entities that are new to a list into CUST_LIST_MEMBERSHIP table. |
| 10830 | CustomerListMembership_WatchListStage 2Upd | This datamap updates the existing retired CUST_LIST_MEMBERSHIP records by setting List Removal Date to the current processing date. |
| 10840 | DerivedAddressListMembership_WatchLis tStage2Insert | This datamap maintains the Derived Address List membership table based on the current WL processing results. |
| 10850 | DerivedAddressListMembership_WatchLis tStage2Upd | This datamap maintains the Derived Address List membership tables based on the current WL processing results by setting List Removal Date to the current processing date. |
| 10860 | DerivedEntityListMembership_WatchListS tage2Insert | This datamap inserts List Membership records for entities that are new to a list into EXTERNAL_NTITY_LIST_MEMBERSHIP table. |
| 10870 | DerivedEntityListMembership_WatchListS tage2Upd | This datamap maintains the External Entity membership tables based on the current WL processing results by setting List Removal Date to the current processing date. |
| 10880 | Account_OverallEffectiveRiskUpd | This datamap updates the risk on the ACCT based on KYC, Primary customer, as well as other external risks. |
| 10881 | Account_AccountCustRiskUpd | This data map updates the risk on the ACCT based on KYC, Primary customer, as well as other external risks. |
| 10890 | Account_EffRiskUpdAfterWLRiskRemoval | This datamap Updates the account Effective Risk to the maximum of the business risk, geographic risk, and customer risk. The account Effective Risk was already set to the higher of the customer-supplied business and geography risk. List risk is ignored here, as this mapping is where we're removing list risk. |
| 10900 | Account_WatchListStage2EffectiveRisk | This datamap calculates all risk related values like Effective Risk of Acct and applies the Effective Risk, List Risk to the ACCT record. |
| 10910 | WatchListStagingTable2_WatchListStage2I ntrlId | This datamap calculates the Effective Risk of all entities and applies the Effective Risk and the List Risk to the entity record based on NTITY_INTRL_ID. |
| 10920 | BackOfficeTransaction_EffectiveAcctivityR iskUpd | This datamap updates the risk related values to all parties involved
in Back Office Transaction.
1) Select risk values from BACK_OFFICE_TRXN, ACCT, Offset Account in the sub query. 2) Derive the effective and activity risks from the transaction. 3) Update BACK_OFFICE_TRXN table using BO_TRXN_SEQ_ID in the main query. |
| 10930 | SettlementInstruction_EntityAcctivityRisk Upd | This datamap updates Entity Risk and Activity Risk in INSTRUCTION table |
| 10940 | FrontOfficeTransactionPartyRiskStage_En tityActivityRiskInsert | This datamap populates the Effective Risk and Activity Risk related values to all the parties in FO_TRXN_PARTY_RISK_STAGE table. |
| 10955 | AccountGroup_InvestmentObjectiveUpd | This datamap updates Investment Objective column in Account Group table. |
| 40100 | InsuranceTransaction_EntityAcctivityRisk Upd | This datamap updates the risk related values to all parties in
Insurance Transaction.
1) Select different risk related values from various tables like watchlist, external entity and derived address etc. 2) Updates Entity Risk and Activity Risk in INSURANCE_TRXN table. |
| 20010 | CorrespondentBank_JurisdictionUpd | This datamap updates the JRSDCN_CD and BUS_DMN_LIST_TX for an existing client bank record where either the JRSDCN_CD or the BUS_DMN_LIST_TX is null. |
| 20020 | CorrespondentBank_AcctJurisdictionReUp d | This datamap updates the jurisdiction for CLIENT_BANK (Correspondent Bank). |
| 20030 | FinancialInstitution_InstNameUpd | This datamap updates INSTN_NM for an existing INSTN_MASTER record. |
| 10960 | AccountGroup_JurisdictionUpd | This datamap updates the primary account in a HH with the jurisdiction & business domain present in Account table for it. |
| 10970 | TransactionPartyCrossReference_BackOffi ceTransaction | This datamap is used to build the record for Transaction Party Cross
Reference table from today’s Back Office Transactions.
1) Select the set of information from today's Back Office Transactions and insert records in Transaction Party Cross Reference table. 2) Parameter ProcessTransactionXRefFlag = 'N' or 'Y' accordingly. |
| 10980 | CashTransaction_FrontOfficeTransaction | This datamap is used to build the record for Cash Transaction Table
from today’s Front Office Transaction and Front Office Transaction
Party.
1) Select the set of Cash Transaction categories information from today's Front Office Transaction and Front Office Transaction Party to Insert records In Cash Transaction Table. 2) Some fields are not null-able. The NVL function is used in the SQL to plug the default values in place of a null. Also, various "NB" fields are set to zero whenever they are null in the expression prior to the inserting them into the target table. |
| 10990 | MonetaryInstrumentTransaction_FrontOff iceTransaction | This datamap select the set of information from today's Front Office Transaction and Front Office Transaction Party to Insert records In Monetary Instrument Transaction Table. |
| 11000 | TransactionPartyCrossReference_FrontOff iceTransaction | This datamap is used to build the record for Transaction Party Cross
Reference table from today’s Front Office Transaction and Front Office
Transaction Party.
1) Select the set of information from today's Front Office Transaction and Front Office Transaction Party to Insert records In Transaction Party Cross Reference Table. 2) Some fields are not null-able. The NVL function is used in the SQL to plug the default values in place of a null. Also, various "NB" fields are set to zero whenever they are null in the expression prior to the inserting them into the target table. 3) Parameter ProcessTransactionXRefFlag = 'N' or 'Y' accordingly. |
| 11010 | WireTransaction_FrontOfficeTransaction |
This datamap is used to build the record for Wire Transaction Table from today’s Front Office Transaction and Front Office Transaction Party. 1) Select the set of Wire Transaction categories information from today's Front Office Transaction and Front Office Transaction Party to Insert records In Wire Transaction Table. 2) Some fields are not null-able. The NVL function is used in the SQL to plug the default values in place of a null. Also, various "NB" fields are set to zero whenever they are null in the expression prior to the inserting them into the target table. 3) Parameter ProcessBankToBank= 'N' or 'Y' accordingly. |
| 11020 | WireTransactionInstitutionLeg_FrontOffic eTransaction | This datamap is used to build the record for Wire Transaction
Institution Leg Table from today’s Front Office Transaction and Front
Office Transaction Party.
1) Select the set of Wire Transaction categories and it should have more than 1 leg information from today's Front Office Transaction and Front Office Transaction Party to Insert records In Wire Transaction Institution Leg Table. 2) Some fields are not null-able. The NVL function is used in the SQL to plug the default values in place of a null. Also, various "NB" fields are set to zero whenever they are null in the expression prior to the inserting them into the target table. 3) Parameter ProcessBankToBank = 'N' or 'Y' accordingly. |
| 11030 | CashTransaction_FrontOfficeTransactionR evAdj | This datamap adjusts the reversals for Cash Transaction table.
1) Select the set of information from today's Front Office Transaction to update records with columns CXL_PAIR_TRXN_INTRL_ID, REBKD_TRXN_INTRL_ID in Cash Transaction table. |
| 11040 | MonetaryInstrumentTransaction_FrontOff iceTransactionRevAdj | This datamap adjusts the reversals for front office transaction tables in Monetary Instrument Transaction table |
| 11050 | WireTransaction_FrontOfficeTransactionR evAdj | This datamap adjusts the reversals for Wire Transaction table.
1) Select the set of information from today's Front Office Transaction to update records with columns CXL_PAIR_TRXN_INTRL_ID, REBKD_TRXN_INTRL_ID in Wire Transaction table. |
| 50050 | CustomerDailyProfile_BOT | This datamap aggregates Back Office Transaction data by Customer and Date and updates into CUST_SMRY_DAILY table. |
| 50060 | CustomerDailyProfile_FOTPS | This datamap aggregates Front Office Transaction data by Customer and Date and updates into CUST_SMRY_DAILY table. |
| 50070 | InstitutionalAccountDailyProfile_DEAL | This datamap updates INSTL_ACCT_SMRY_DAILY table from Deal, grouping by account and data dump date. |
| 50080 | CustomerDailyProfile_DEAL | This datamap updates CUST_SMRY_DAILY table from Structured Deal, grouping by customer and data dump date. |
| 50090 | InstitutionalAccountDailyProfile_INST | This datamap updates INSTL_ACCT_SMRY_DAILY table from Instruction, grouping by account and data dump date. |
| 50100 | CustomerDailyProfile_INST | This datamap updates CUST_SMRY_DAILY table from Instruction data, grouping by Customer and data dump date. |
| 50110 | InstitutionalAccountDailyProfile_CorpActi on | This datamap aggregates institutional trading activity, grouping by Account ID and data dump date. |
| 50120 | CustomerDailyProfile_CorpAction | This datamap aggregates Corporate Action trading activity, grouping by Customer ID. |
| 50130 | InstitutionalAccountDailyProfile_Trade | This datamap updates INSTL_ACCT_SMRY_DAILY table from Trade, grouping by account and data dump date. |
| 50140 | CustomerDailyProfile_Trade | This datamap updates CUST_SMRY_DAILY table from Trade data, grouping by customer and data dump date. |
| 60100 | ManagedAccountDailyProfile_SameDayTr ade | This datamap is used for the daily aggregation of the block allocation day trades data. This populates the managed account daily summary. |
| 60110 | ManagedAccountDailyProfile_Trade | This datamap is used for the daily aggregation of the block allocation trades data. This populates the managed account daily summary . |
| 60120 | ManagedAccountDailyProfile_BOT | This datamap populates MANGD_ACCT_SMRY_DAILY table using Back Office Transaction. |
| 11160 | AccountDailyProfile-Trade | This datamap performs daily aggregation of trades fromtrade table , Profit Loss from Account Realized Profit Loss table. |
| 11170 | AccountDailyProfile-Transaction | This datamap populates the table ACCT_TRXN_SMRY_DAILY using both Front office and Back Office transaction for that account on current processing date. |
| 11180 | AccountProfile_Trade | This datamap populates the table ACCT_SMRY_MNTH using ACCT_TRADE_SMRY_DAILY table for that account starting from Month Start date till current processing date. |
| 11190 | AccountProfile_Transaction | This datamap populates the table ACCT_SMRY_MNTH using ACCT_TRXN_SMRY_DAILY table for that account starting from Month Start date till current processing date. |
| 11200 | AccountProfile_Stage | This datamap populates the table ACCT_SMRY_MNTH using ACCT_PRFL_STAGE table for that account starting from Month Start date till current processing date. |
| 11210 | AccountProfile_Position | This datamap populates the table ACCT_SMRY_MNTH using ACCT_POSN table for that account starting from Month Start date till current processing date. Updates values by calculating aggregate values for AGGR_SHRT_PUT_EXPSR_AM, AGGR_SHRT_CALL_EXPSR_AM, SHRT_PUT_EXPSR_RATIO and SHRT_CALL_EXPSR_RATIO for each account internal ID present in ACCT_SMRY_MNTH. |
| 11220 | AccountProfile_Balance | This datamap populates the ACCT_SMRY_MNTH table usingACCT_BAL_POSN_SMRY. If there is already record in Account summary Month for Account and Month Start Date, then it will update the record. Else it will do insert, remaining columns defaulted to 0. |
| 60130 | HouseholdProfile | This datamap aggregates monthly account summaries into their respective households. All monthly records must be processed each day since account households are subject to change daily. |
| 50150 | InstitutionalAccountProfile | This datamap performs Insert or Update of Institutional Account Summary Month Table from its corresponding Daily table. Aggregate daily activity with counts and amounts for the current month. If already record exists for the account in the current month, the datamap will update the record, else insert a new record. |
| 50160 | CustomerProfile | This Datamap loads into CUST_SMRY_MNTH from CUST_SMRY_DAILY table. Check for the customer record exists for t he month, if record not available Insert records in CUST_SMRY_MNTH table |
| 60140 | ManagedAccountProfile | This datamap updates the Managed AccountSummary Month Table from its corresponding Managed Account Daily Summary table. |
| 60145 | AccountPosition_PercentofPortfolioUpd | This datamap updates Percent of Portfolio column in Account Position table. |
| 20040 | CorrespondentBankProfile | This datamap performs daily re-aggregation of the Correspondent Bank Summary Month table out of the account summary month table. |
| 20050 | AccountATMDailyProfile | This datamap calculates the total Transaction Amount for Account ATM Daily Profile Select information from Front Office Transaction, Account and Account ATM Daily Profile and insert or update (if record exist) into ACCT_ATM_SMRY_DAILY |
| 11230 | ChangeLog_AcctProfileInactivity | This datamap creates Change Log records that indicate a change in an accounts activity level as measured by the sum of deposits, withdrawals, and trades over a configurable time period (months). |
| 11240 | AccountPeerGroupMonthlyTransactionPro file | This datamap calculates average values and insert into Account Peer Group Monthly Transaction Profile. Select and calculate average values for withdrawal amount and count from ACCT_SMRY_MNTH table Insert the above values into ACCT_PEER_TRXN_SMRY_MNTH. |
| 20060 | CorrespondentBankPeerGroupTransaction Profile | This datamaps populate CorrespondentBankPeerGroupTransactionProfile
from Client Bank Summary Month.
1) Select set of information from CLIENT_BANK_SMRY_MNTH, CLIENT_BANK_PEER_GRP 2) Data is populated in the target table after aggregating the required columns. |
| 20070 | AccountChannelWeeklyProfile | This datamap populates the table ACCT_CHANL_SMRY_WKLY using FO_TRXN, BACK_OFFICE_TRXN table for that account starting from Weekly Start date till current processing date. |
| 40110 | InsurancePolicyDailyProfile_InsTrxnInsPoli cyBal | This datamap performs inserts or updates of Insurance Policy Summary Daily Table from the Insurance Transaction table on the current processing day. |
| 40120 | InsurancePolicyProfile_InsurancePolicyDail yProfile | This datamap performs updates of Insurance Policy Summary Month Table using the values from Insurance Policy Daily Profile table. 1) Records are inserted into Insurance Policy Daily Profile table prior to this datamap execution. 2) This datamap inserts new records or Updates matched records in Insurance Policy Profile table using the values from Insurance Policy Daily Profile table. |
| 50170 | CustomerBalance_ActiveOTCTradeCtUpd | This datamap counts the records in the Deal table which has an end date greater than or equal to the current date by customer and update the ACTV_OTC_TRD_CT column in customer balance table. |
| 60150 | AccountPositionDerived | This datamap processes account option position pair data and updates the corresponding account position records. Updates are made to attributes relating to uncovered option contracts |
| 60160 | AccountBalance_AcctPosnPair | This datamap processes account option position pair data and updates the corresponding account balance records. Updates are made to option market value long attributes. |
| 60170 | AccountBalance_Acctposn | This datamap aggregates current-day security positions by product category and account for update of the account balance record. Rejoins for single update to avoid deadlocks. |
| 60180 | HouseholdBalance | This datamap aggregates daily records of account balances data and inserts into household balances table based household group id. |
| 11300 | AccountChangeLogSummary | This datamap inserts new records to the ACCT_CHG_LOG_SMRY
table.
The datamap should be executed once the change log processing is done. |
| 11310 | AccountToCustomerChangeLogSummary | This datamap inserts new records to the CUST_ACCT_CHG_LOG_SMRY.
The datamap should be executed once the change log processing is done. |
| 11320 | CustomerChangeLogSummary | This datamap inserts new records to the CUST_CHG_LOG_SMRY
table.
The datamap should be executed once the change log processing is done. |
Note:
The AccountChangeLogSummary, AccountToCustomerChangeLogSummary, and CustomerChangeLogSummary datamaps must be run withexecute.sh from
8.0.2 onwards.