1.8.3 Integration Process of EAC and Customer Status

EAC process

• This integration is to verify the settlement account and account CIF in a contract. This service validates the customer and customer account and returns success or fail.
• The synchronous call request is inserted into OLTB_REQ_MASTER with process status as U.
• New stage table contains the tag values required to build the request for each contract
  • OLTB_EAC_ACC_MASTER
  • OLTB_EAC_ACC_DETAIL
• The system validates account CIF or account based on few parameters (frozen/ dormant/no debit/no credit, and so on) and an appropriate error message appears.

Customer Status

• This integration is to verify the frozen, deceased and where about unknown status for the counterparty and Borrower CIF of a contract.
• The synchronous call request is inserted into OLTB_REQ_MASTER with process status as U.
• New stage table contains the tag value required to build the request for each contract
  • OLTB_CUST_STATUS
• The system validates the counterparty and borrower based on few parameters (frozen/ deceased/where about unknown/invalid customer) and an appropriate error message appears.

Inactive Customer Status

If a customer does not have any single contract active, then an update is sent to FCUBS using QueryCustSts service is consumed by OBCL to handoff the customer status (Active/ Inactive) to FCUBS system.

• System sends an update if customer does not have any single contract active. Here customer in respective PPs considered as Inactive
• System sends an update if customer does have at least one contract active. Here customer in respective PPs considered as Active