5.2 Oracle Banking Enterprise Limits and Collateral Management
Oracle Banking Enterprise Limits and Collateral Management requires the following services for Oracle® Banking Supply Chain Finance Cloud Service. Make sure that the following services are available before the implementation:
Table 5-2 Integration Touch Points
Integration Touch Point | Stage in OBSCF | Purpose | Mandatory Request Parameters | Mandatory Response Parameters |
---|---|---|---|---|
Limit Set Up |
|
The purpose of the API is to fetch limits of a party from ELCM and maintain in SCF. This would also be invoked during EOD for batch updates to the maintained limits in SCF. |
|
|
Block Limits | Processing - Finance Workflow | The purpose of the API is to block limits of the party whose limits are to be utilized in transaction in ELCM. |
|
|
Utilize Limits | Post Authorization - Finance Workflow |
The purpose of the API is to utilize the limits of the party whose limits were blocked during Processing. It will unblock and utilize the limits simultaneously. This would be used in disbursement. |
|
|
Release Limits | Post Authorization - Finance Workflow |
The purpose of the API is to release the limits of the party whose limits were utilized during Disbursement. It will be invoked during Settlement. |
|
|
Unblock Limits | Authorization Reject/Rollback - Finance Workflow |
The purpose of the API is to unblock the limits of the party whose limits were blocked during Processing. It will be invoked during disbursement. |
|
|
Query the Limit Details |
|
The purpose of the API is to fetch the liability number and line ID from ELCM. | Customer Id |
|
Note:
*Status, Error Code, and Error Description are mandatory response parameters in all touch points.Parent topic: Outbound API calls through Oracle® Banking Routing Hub