3.1.1 Inbound Entity Creation
This topic provides information about the Inbound Entity Creation process
This batch process inbound data from staging area like account and account party relationship and persist a new account and customer relationship details entities in Oracle Banking Collections Cloud Service. Customer related details are fetched from Oracle Banking Party based on the Customer id provided by the host system.
Job Name: obcr-inbound-entity-creation-batch
Dependent Batch/Job: Not Applicable
Multi-threaded: No
URI: <protocol>://obcr-entity-services/jobLauncher/runBatch/
Table 3-2 Mandatory Headers
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
appld | CRENTITY | Yes | The application ID of the host service. |
Specify following parameters while executing this batch:
Table 3-3 Parameters
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
runDate | 16062019 | Yes | It must be in ddmmyyyy format. |
branchCode | DMO | Yes | Branch code of the project. |
userId | ADMINUSER1 | Yes | User id of the user. |
- User can verify the record level status in the following tables in CR_ENTITY schema.
DM_INBOUND_ENTITY_CREATION_DRIVER
- For a successful processing of a record, the below condition should be satisfied. ERROR_CODE = Success and PROCESS_RESULT = 1
Parent topic: Entity Creation