3.1.2 Inbound for Non-Mandatory Entities Creation

This topic describes the information about Inbound Non-mandatory Entity Creation.

This batch processes data of non-mandatory entities from staging tables (i.e Bill Details, Payments, Repayment Schedule, Arrear Details, Collateral Details etc ) to update/insert data related to delinquent accounts already onboarded in Collections.

This batch processes data for the following entities:

• Account Arrears
• Bill Details
• Repayment Schedule
• Payment Details
• Party Address
• Party Contact
• Party Employment Details
• Party Identity Details
• Collateral Details
• Collateral Charge Details
• Collateral Linkage Details
• Collateral Ownership Details

JobName: obcrInbNonManEntityCreationBatch

Dependent Batch/Job: Not Applicable

Multi-threaded: Yes

URI: <protocol>:obcr-entity-data-services/jobLauncher/run/

Mandatory Headers:

Table 3-4 Mandatory Headers

Parameter Name	Value	Mandatory	Description
appld	CRENTITYDATA	Yes	The application ID of the host service.

Specifyfollowing parameters while executing this batch:

Table 3-5 Parameters

Parameter Name	Value	Mandatory	Description
microServiceName	obcr-entity-data-services	Yes	Name of micro service
appId	CRENTITYDATA	Yes	The application ID of the host service.
contextRoot	obcr-entity-data-services	Yes	Context root value
overrideDate	2021-03-07	No	It must be in yyyy-mm- ddformat. It is required to run the batch for a specific day.
productProcessrCode	TPH	No	Value of Product Processor is required only if user wants to run this batch for a particular product processor.
timestamp	20260210190234.34300	No	Batch running timestamp in YYYYMMDDHHMMSS.SSSSS

Success/Failure Details:

• User can verify the record level status in the respective staging tables.
• For a successful processing of a record, Process Status will be updated as ‘S’ and for failure of records the same will be updated as ‘F’.