4.25 Configuring Batch Audit Trial

Configuring the batch audit trail provides traceability and transparency for batch operations within the system. This enables compliance monitoring, supports internal reviews, and facilitates easy extraction of audit reports for regulatory or business needs.

To configure the batch audit trail, follow the steps:

1. Access the Atomic Schema and open the CS_APPLN_PARAMS table.
2. Enable the batch audit trail by setting the CS_BATCH_AUDIT parameter to 'Y'.
   When the CS Data Load And Event Generation batch is executed, it triggers the CSBatchAudit task. This task internally calls F_POPULATE_BATCH_DATA_AUDIT, which inserts data into the following audit tables:

   • CS_CUST_AUDIT (All the customer attributes screened for EDQ)
   • CS_EE_AUDIT (All the external entity attributes screened for EDQ)
   • CS_MATCHES_AUDIT (All the matches data from EDQ)
   • CS_WATCHLIST_AUDIT (All the matched watchlist data from EDQ)
   • CS_UNSCREENED_CUSTDATA (All the unscreened data will be stored here):
   Customers or external entities without names are not screened by default. To enable screening for these unnamed records, set the following property to Y in both customer-screening.properties and external-entity-screening.properties:
3. After batch processing is completed, generate screened data reports:
4. Navigate to FIC_HOME/CS-OAS-Report-Queries.
5. Choose from the following sample SQL files based on your reporting needs:
   • ZIPPER_ALERT_EE_AUDIT.sql — External Entities (Zipper alerts)
   • ZIPPER_ALERT_CUST_AUDIT.sql — Customer Data (Zipper alerts)
   • ECM_CASE_EE_AUDIT.sql — External Entities (ECM case)
   • ECM_CASE_CUST_AUDIT.sql — Customer (ECM case)

   Select a sample query and customize it as needed for your requirements, then execute it in the Atomic schema to generate the desired report.