1. Oracle Banking Corporate Lending - OFSAA Integration guide
  2. OBCL - OFSAA Integration
  3. Integration Process

1.4 Integration Process

OBCL has pre-defined staging tables required for OFSAA extracts. During EOFI batch, the module wise data is extracted to staging tables in OBCL. OBCL provides a control table to indicate successful data extraction. OFSAA pulls the data from the tables in OBCL using the DIH connector.

The transfer or extraction of data from OBCL to OFSAA differs based on the staging tables as follows:
  • Master table - Incremental data between two extraction dates are transferred.
  • Maintenances and contract tables - Entire transaction data are transferred in each extraction.
  • Transaction table - Data related to the transactions created on the extraction date are transferred.
During data extraction you can check the status of the extraction routines in the table OLTB_JOB_ES_CONTROL. The column STATUS shows whether the routine is in progress (W) or has failed (F) or has completed successfully (S). At the time of extraction all the routines from maintenance table OLTM_DEST_ES_TABLES are inserted to OLTB_JOB_ES_CONTROL for the current extraction date with initial status as W. This status is updated accordingly when the routine is completed successfully (S) or unsuccessfully (F).

Extraction Log

You can have the logs generated as part of EOD for each table. EOD log captures the complete extraction process. The table level extraction log contains the details of each data transfer. The error logs are maintained in OLTBS_LOG_ES table.

Errors in the data extraction process and the failure reasons are logged in an error data store. These errors are rectified manually and the batch is run again for the failed data.

Parent topic: OBCL - OFSAA Integration