3.1 Inbound Mandatory Entity Creation

This topic describes the information about to Inbound Mandatory Entity Creation.

Mandatory Entities (mandatory to onboard new account):

• Account Details
• Account Party Details
• Party Details
• Party Name Details

Product Processor sends new delinquent account data into OBC staging tables for above 4 mandatory entities with RECORD_TYPE = 'I'.

• Once the required data is received in the staging area , OBC processes all new delinquent accounts and relevant entities , where RECORD_TYPE flag value is 'I' in all the entities.
• While processing the Party related data system verifies that at least one record for each mandatory entity is available else rejects the account onboarding.
• For Party and Party Name details received for a new delinquent account where Party already exists then.
  • Updates the record where Party No and Name Type already exists.
  • For new Name type received, new record is inserted.
• After batch processing, the system marks each record as Success (S) or Failed (F). Records with either status are excluded from subsequent batch runs

Checks and validations:

1. If data is missing for any of the mandatory entity then record is rejected.
2. If any mandatory fields is missing then record is rejected.
3. If data movement of any of the staging table related to the account ( either Account Entities, Party Entities ) to main entity schema is failed, entire account data movement is rolled back. The Failed account gets marked appropriately with proper error code. Account is marked rejected in all related entities including Party.