1.2.1 Enhancements in Oracle Banking Party

The following are the enhancements as a part of Party in this release:

Table 1-1 Enhancements in Oracle Banking Party

Summary Description
Response Model Name Change Response model name updated from PartyResponseRetailModel to PartyMsgResponseModel

Impacted APIs

POST - /service/v1/retail/onboardParty

POST - /service/v1/retail/partyAmend

PATCH - /service/v1/retail/basicInfo

PUT - /service/v1/retail/basicInfo

GET - /service/v1/retail/basicInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/retail/basicInfo/.search

PATCH - /service/v1/retail/addressInfo

PUT - /service/v1/retail/addressInfo

GET - /service/v1/retail/addressInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/retail/addressInfo/.search

POST - /ob/obpy/party/v1/addressInfo/.search

GET - /service/v1/retail/idInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/retail/idInfo/.search

PATCH - /service/v1/retail/idInfo

PUT - /service/v1/retail/idInfo

PATCH - /service/v1/retail/contactInfo

PUT - /service/v1/retail/contactInfo

GET - /service/v1/retail/contactInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/retail/contactInfo/.search

GET - /ob/obpy/party/v1/retail/partyAddInfo/{externalCustomerNo}

POST - /service/v1/smb/onboardParty

PATCH - /ob/obpy/party/v1/smb/amendParty

POST - /service/v1/smb/partyAmend

PATCH - /service/v1/smb/businessDetails

PUT - /service/v1/smb/businessDetails

POST - /ob/obpy/party/v1/smb/businessDetails/.search

PATCH - /ob/obpy/party/v1/smb/contactInfo

PUT - /ob/obpy/party/v1/smb/contactInfo

GET - /ob/obpy/party/v1/smb/contactInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/smb/contactInfo/.search

PATCH - /ob/obpy/party/v1/smb/addressInfo

PUT - /ob/obpy/party/v1/smb/addressInfo

GET - /ob/obpy/party/v1/smb/addressInfo/{externalCustomerNo}

POST - /ob/obpy/party/v1/smb/addressInfo/.search

PATCH - /ob/obpy/party/v1/smb/taxInfo

PUT - /ob/obpy/party/v1/smb/taxInfo

POST - /ob/obpy/party/v1/smb/taxInfo/.search

POST - /ob/obpy/party/v1/smb/migrateTHSMBByEvent/{cifNumber}/{applicationNo}

Source Branch Field (Retail/SMB) Enhancement: A new "Opening Branch Code" field has been introduced on UI.

- Details: Display-only field to show the branch captured during customer onboarding.

Note: No changes to the API payload, as this is an existing backend field now exposed in the UI.

Relationship Enhancements (Related Party)
  • UI Simplification: Removed "Related To", "Related With", and "Relationship Types" tabs; introduced a single grid to view all relationships.
  • Field Renaming:
    • Primary Party → Party Relationship
    • Secondary Party → Related Party Relationship
  • New Relationship Type: Can now be selected during Party-to-Party creation.
  • Edit Enhancements: Improved ability to update existing relationships.
  • Delete Enhancements: Enhanced deletion process.
  • New Relationship Code field added to Related Party Relationship.
  • Relationship Maintenance: New Maintenance introduced for managing Related Party Relationships.
  • Relationship Code column added in Insta and STP relationship tables.

Impacted APIs

New versions of APIs introduced to support relationship enhancements for Related Party:

POST: /ob/obpy/party/v2/retail/party-onboardings

POST: /ob/obpy/party/v2/retail/party-amendments

PATCH: /ob/obpy/party/v2/retail/granular

POST: /ob/obpy/party/v2/smb/party-onboardings

POST: /ob/obpy/party/v2/smb/party-amendments

PATCH: /ob/obpy/party/v2/smb/amendParty

PATCH: /ob/obpy/party/v2/partyToParty/relatedParty

POST: /ob/obpy/party/v2/partyToParty/relatedParty

PUT: /ob/obpy/party/v2/partyToParty/relatedParty/{id}

Events Impacted

obpyRetOnboard

obpyRetAmendPartyInfo

obpyRetAmendRelatedPartyRel

obpySmbOnboard

obpySmbAmendPartyInfo

obpySmbAmendRelatedPartyRel

TIN Format Validations Validations for TIN types—SSN, ITIN, ATIN, and EIN—have been enhanced to support multiple input formats, including with hyphens, without hyphens, and all-zero entries, while ensuring compliance with regulatory standards.

Impacted APIs

POST: /service/v1/retail/onboardParty

POST: /service/v1/retail/partyAmend

PATCH: /ob/obpy/party/v1/retail/granular

PUT: /service/v1/retail/taxInfo

PATCH: /service/v1/retail/taxInfo

POST: /service/v1/smb/onboardParty

POST: /service/v1/smb/partyAmend

PATCH: /ob/obpy/party/v1/smb/amendParty

PUT: /ob/obpy/party/v1/smb/taxInfo

PATCH: /ob/obpy/party/v1/smb/taxInfo

Data Migration Impact

Adjusted accordingly to align with new validation rules.
Minor Party Relationship Enhancements
  • Validation Relaxation: Removed validations related to party relationships for minor parties during onboarding and amendments.
  • New Field: Introduced "Emancipate Minor" flag to identify emancipated minors in onboarding and amendment flows.

Impacted APIs

Minor Validation

POST: /service/v1/initiatePartyOnboarding

POST: /service/v1/retail/onboardParty

POST: /service/v1/retail/partyAmend

PATCH: /ob/obpy/party/v1/retail/granular

Emancipated Flag

POST: /service/v1/initiatePartyOnboarding

POST: /service/v1/retail/onboardParty

POST: /service/v1/retail/partyAmend

PATCH: /ob/obpy/party/v1/retail/granular

PUT: /service/v1/retail/basicInfo

PATCH: /service/v1/retail/basicInfo

POST: /ob/obpy/party/v1/retail/basicInfo/.search

Impacted Events

Emancipated Flag

obpyRetOnboard

obpyRetAmendPartyInfo

obpyRetAmendBasicInfo

Data Migration Impact

New Field Introduced in Retail Party Info
Business Name Field Update UI Change: Doing Business As field renamed to Registered Business Name for clarity and consistency.
Party to Account History Oracle Banking Party has been enhanced to capture Party-to-Account history as part of the amendment process, enabling better traceability and auditability of changes over time
Party to Account - Unique Key The Party to Account Relationship process previously relied on a combination of the CIF ID and Account Number to identify unique records and prevent duplicates. However, to support scenarios where the same CIF ID and Account Number can have multiple types of relationships, the validation has been enhanced to include Party Relationship as part of the uniqueness check. This ensures that records with the same CIF ID and Account Number but different Party Relationships can coexist without conflict.

Impacted APIs

POST: /ob/obpy/party/v1/partyToAccount/.search

POST: /ob/obpy/party/v1/partyToAccount

PUT: /ob/obpy/party/v1/partyToAccount

PATCH: /ob/obpy/party/v1/partyToAccount

Data Migration

During migration, more than one Party to Account relationship can be created with the same PTY_ACC_REL_CIF_ID and PTY_ACC_REL_ACCOUNT_NUMBER but different PTY_ACC_REL_PARTY_RELATIONSHIP values.

Multi-Record Limitations Oracle Banking Party is Enhanced to limit the Minimum and Maximum number of records for Address, Contact and ID Details data segment.

Maintenance

A new Maintenance for Record Management is introduced to define maximum and minimum number of records for Address, Contact and ID Details based on the Entity and Sub-Entity Codes.

Note: Optional data segments will be treated as mandatory if the minimum number of records is set to 1 or more. Conversely, mandatory data segments will remain mandatory even if the minimum number of records is defined as 0.

Impacted APIs

POST: /service/v1/retail/onboardParty

POST: /service/v1/retail/partyAmend

PATCH: /service/v1/retail/addressInfo

PATCH: /service/v1/retail/idInfo

PATCH: /service/v1/retail/contactInfo

PATCH: /ob/obpy/party/v1/retail/granular

PUT: /service/v1/retail/addressInfo

PUT: /service/v1/retail/idInfo

PUT: /service/v1/retail/contactInfo

POST: /ob/obpy/party/v2/retail/party-onboardings

POST: /ob/obpy/party/v2/retail/party-amendments

PATCH: /ob/obpy/party/v2/retail/granular

POST: /service/v1/smb/onboardParty

POST: /service/v1/smb/partyAmend

PATCH: /ob/obpy/party/v1/smb/contactInfo

PATCH: /ob/obpy/party/v1/smb/addressInfo

PUT: /ob/obpy/party/v1/smb/contactInfo

PUT: /ob/obpy/party/v1/smb/addressInfo

POST: /ob/obpy/party/v2/smb/party-onboardings

POST: /ob/obpy/party/v2/smb/party-amendments

PATCH: /ob/obpy/party/v2/smb/amendParty

Data Migration

Data Migration process will follow validation for number of records as per maintenance configuration.
Party 360 Integration with OBRL Party View 360 is integrated to with OBRL to retreive Loan accounts of a party

Parent topic: Release Enhancements