F.9 AML Banking - Summary Datamaps

Summary Datamaps are used to calculate aggregations across various entities using the Trade, Transaction, Positions and Balances tables.

These datamaps populate various profile tables for different entities such as Account Profile, Household Profile, and Correspondent Bank Profile. The aggregation is done either daily, weekly or monthly depending on the business areas.

Optional Datamaps are used to perform processing to support other datamaps in multiple functional areas. These datamaps may or may not be completely relevant to a particular solution set. Execute the datamap if a scenario in your implementation requires this information.

Table F-9 AML Banking - Summary Datamaps

Datamap Number	Datamap Name	Predecessors
11160	AccountDailyProfile-Trade	NA
11170	AccountDailyProfile-Transaction	NA
11180	AccountProfile_Trade	11160
11190	AccountProfile_Transaction	11170
11200	AccountProfile_Stage Optional: Run the datamap if there is any record in Account Profile Stage.	NA
11210	AccountProfile_Position	11180 11190
11220	AccountProfile_Balance	10940 11160 11170 11180 11190 11210
20040	CorrespondentBankProfile	11180 11190 11200 11210 11220
20050	AccountATMDailyProfile	10940
11230	ChangeLog_AcctProfileInactivity	11180 11190 11200 11210 11220
11240	AccountPeerGroupMonthlyTransactionProfile	11180 11190 11200 11210 11220
20060	CorrespondentBankPeerGroupTransactionProfile	20040
20070	AccountChannelWeeklyProfile	10940
11300	AccountChangeLogSummary	The datamap should be executed once the change log processing is done.
11310	AccountToCustomerChangeLogSummary	The datamap should be executed once the change log processing is done.
11320	CustomerChangeLogSummary	The datamap should be executed once the change log processing is done.

Note:

The AccountChangeLogSummary, AccountToCustomerChangeLogSummary, and CustomerChangeLogSummary datamaps must be run with execute.sh from 8.0.2 onwards.