1.2.11 Party

This topic provides information about functional enhancements in the Party.

Table 1-4 Enhancements in Oracle Banking Party

Summary Description
Closed NAICS Codes Handling

OB Party is enhanced to handle Closed NAICS Codes during Party Onboarding and Amendment for SMB Party.

  • Closed NAICS Codes are no longer selectable during SMB Party Onboarding and Amendment.
  • Existing Parties remain unaffected if their currently assigned NAICS Code is Closed.

Impacted APIs:

  • POST — /service/v1/smb/onboardParty
  • POST — /service/v1/smb/partyAmend
  • PATCH — /ob/obpy/party/v1/smb/amendParty
  • PATCH, PUT — /service/v1/smb/businessDetails
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v2/smb/amendParty

Impacted UIs:

  • Party Management
    • Onboarding
    • Amendment
  • Insta Party Management
    • Onboarding
    • Amendment
  • Data Segment Amendment
    • Business Details
  • KYC Management
    • Create
    • Update
Party Deceased Status for SMB Party Type

The SMB Party Amendment process is enhanced to capture and maintain deceased status accurately by introducing a Deceased toggle and a Deceased Date field. Deceased Party are not be allowed to be added as Relationships.

Impacted APIs:

  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH, PUT - /service/v1/smb/businessDetails
  • POST - GET - /ob/obpy/party/v1/smb/businessDetails/.search
  • POST, PATCH, PUT - /ob/obpy/party/v1/partyToAccount
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/owner
  • PUT - /ob/obpy/party/v1/partyToParty/owner/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/guarantors
  • PUT - /ob/obpy/party/v1/partyToParty/guarantors/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/authorizedSignatory
  • PUT - /ob/obpy/party/v1/partyToParty/authorizedSignatory/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/suppliers
  • PUT - /ob/obpy/party/v1/partyToParty/suppliers/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/trustee
  • PUT - /ob/obpy/party/v1/partyToParty/trustee/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/beneficiary
  • PUT - /ob/obpy/party/v1/partyToParty/beneficiary/{id}
  • POST, PATCH - /ob/obpy/party/v1/partyToParty/relatedParty
  • PUT - /ob/obpy/party/v1/partyToParty/relatedParty/{id}
  • PUT - /ob/obpy/party/v2/partyToParty/relatedParty/{id}
  • POST, PATCH - /ob/obpy/party/v2/partyToParty/relatedParty
  • PUT - /ob/obpy/party/v2/partyToParty/relatedParty/{id}
  • POST, PATCH - /ob/obpy/party/v2/partyToParty/relatedParty

Impacted UIs:

  • Party Management - SMB Amendment, View
  • Insta Party Management - SMB Amendment, View

Migration Impact:

Note: SMB Party Info Migration process already support Deceased Flag and Date of Deceased

Amend Party Details on Closed Branch Branch and Role Based User Access Validation
  • Introduced new configurable properties in Property Maintenance to control Branch Access and Role Based Validation during Party Onboarding and Amendment.
    • New Property: USER_BRANCH_ACCESS_VALIDATE
      • Values: true / false
      • Default: false
  • Introduced Onboarding Branch during Party Onboarding. Onboarding Branch can be selected based on Property Maintenance for Branch Access and Role Based Validation.

Closed Branch Codes Handling

  • Enhancement to handle Closed Branch Codes during Party Onboarding and Amendment of a Party.
    • Closed Branch Codes are no longer selectable during Party Onboarding.
    • Existing Parties remain unaffected if their currently assigned Branch is Closed.
  • Branch Code cannot be changed during Amendment.

Note: Party to Party and Party to Account currently does not consider Branch Access and Role Based Access Validations.

Impacted APIs :

  • POST - /service/v1/retail/onboardParty
  • POST - /ob/obpy/party/v2/retail/party-onboardings
  • POST - /service/v1/retail/partyAmend
  • POST - /ob/obpy/party/v2/retail/party-amendments
  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH, PUT - /service/v1/retail/basicInfo
  • GET - /service/v1/retail/basicInfo/{externalCustomerNo}
  • POST - /ob/obpy/party/v1/retail/basicInfo/.search
  • PATCH, 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
  • PATCH, PUT - /service/v1/retail/idInfo
  • GET - /service/v1/retail/idInfo/{externalCustomerNo}
  • POST - /ob/obpy/party/v1/retail/idInfo/.search
  • PATCH, PUT - /service/v1/retail/contactInfo
  • GET - /service/v1/retail/contactInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/retail/contactInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/partyAddInfo
  • GET - /ob/obpy/party/v1/retail/partyAddInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/retail/partyAddInfo/.search
  • PATCH, PUT - /service/v1/retail/taxInfo
  • POST - GET - /ob/obpy/party/v1/retail/taxInfo/.search
  • PATCH, PUT - /service/v1/retail/employment
  • POST - GET - /ob/obpy/party/v1/retail/employment/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/consentPreference
  • GET - /ob/obpy/party/v1/retail/consentPreference/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/retail/consentPreference/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/partyServiceMember
  • POST - GET - /ob/obpy/party/v1/retail/partyServiceMember/.search
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH, PUT - /service/v1/smb/businessDetails
  • POST - GET - /ob/obpy/party/v1/smb/businessDetails/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/addressInfo
  • GET - /ob/obpy/party/v1/smb/addressInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/smb/addressInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/contactInfo
  • GET - /ob/obpy/party/v1/smb/contactInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/smb/contactInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/taxInfo
  • POST - GET - /ob/obpy/party/v1/smb/taxInfo/.search
  • POST - GET - /ob/obpy/v1/party/.search
  • POST - GET - /ob/obpy/v1/partyInfo/.search
  • GET - /service/v1/getParty/{partyId}

Impacted UIs:

  • Party Management -SMB Onboarding, Amendment, View
  • Insta Party Management - SMB Onboarding, Amendment, View
  • KYC Management - SMB Create, Update
Note:
  • No Impact of Branch Access Validation on Migration.
  • Party Info Migration process already support Migration of Parties on Closed Branch.
Data Segment Amendments
  • New UIs have been introduced to support amendments for selected individual Data Segment level for Party Information, Party Relationship (Related Party Relationship Only) and Party to Account Relationship.
  • When amendments are initiated through these Data Segment Amendment UIs, the system generates events containing only the amended fields, rather than the complete Data Segment payload.

Impacted UIs:

Data Segment Amendment

  • Basic Info & Citizenship
  • Business Details
  • Current Address
  • ID Details
  • Contact Details
  • Tax Declaration
  • Salaried Employment
  • Self-Employed
  • Consent & Preferences
  • Additional Info
  • Service Member Info
  • Party To Account
  • Party To Party
Contact Details - Verification Fields and File Upload Capability

New Field Introduction

  • New fields have been added to the Contact Details data segment to capture contact verification information.
  • Verification fields are read-only in the UI and can be populated/updated only via API or file upload.
  • Manual verification fields remain editable in the UI (and can also be maintained via API/file upload where applicable).

File Upload

  • New File Upload process is introduced to update Contact Details
  • Key Capabilities
    • Enables add / replace / remove operations for Contact Details associated with a Party via file upload.
    • For replace and remove, uniquely identify the target contact record using params in the upload file.
    • Reject Operation, If the provided param combination does not resolve to a single unique record.

Field Value Handling Rules

  • Empty string ("") or literal "null"
    • Interpreted as an explicit request to delete/clear the existing value.
    • System will overwrite the field and set it to blank/removed.
  • Literal "no_update"
    • Interpreted as no change requested.
    • System will ignore the field and retain the existing value.
  • Duplicate Records (Replace Operation)
    • If duplicate records are provided for a replace operation, the feed will follow an upsert behavior:
      • Subsequent records will overwrite earlier records for the same identified contact entry.

Note: OB Party Contact Patch API FA Codes must be mapped to required Role for File Upload Bulk Amendment Process.

Impacted APIs:

  • POST - /service/v1/retail/onboardParty
  • POST - /ob/obpy/party/v2/retail/party-onboardings
  • POST - /service/v1/retail/partyAmend
  • POST - /ob/obpy/party/v2/retail/party-amendments
  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH, PUT - /service/v1/retail/contactInfo
  • GET - /service/v1/retail/contactInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/retail/contactInfo/.search
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH, PUT - /ob/obpy/party/v1/smb/contactInfo
  • GET - /ob/obpy/party/v1/smb/contactInfo/{externalCustomerNo}
  • POST - GET - /ob/obpy/party/v1/smb/contactInfo/.search
  • GET - /service/v1/getParty/{partyId}
  • GET - /service/v1/partySearch
  • POST - GET - /ob/obpy/v1/party/.search
  • POST - GET - /ob/obpy/v1/partyInfo/.search

Note: Service are Impacted due to Field Introduction only.

Impacted UIs:

  • Party Management - Onboarding/Amendment/View Contact Details
  • Insta Party Management - Onboarding/Amendment/View Contact Details
  • Data Segment - Amendment / Contact Details

Migration Impact:

Note:
  • New Fields are not to be included as part of Migration process. File Upload process should be used to update Verification Fields.
Advance Search Service with Additional Fields

Following new field are added to Advance Search Service /ob/obpy/v1/partyInfo/.search

  • maskedTin - Controls whether taxIdentificationNumber is masked in responses
  • addressLine1 - First line of the customer’s address.
  • addressLine2 - Second line of the customer’s address
  • zipCode - Postal/ZIP code of the customer’s address.
  • customerStatus - Status of the customer (example,, Active, Inactive, Suspended)

Note: Fields will be only available in Service for search. The same are not be available in Advance Search UI.

Note: While using wildcards, any number of digits can be provided as TIN input, and the search will be performed accordingly. However, if masked in is set to "true", the response will return only the last four digits of the TIN, with all preceding digits masked.

Impacted APIs:

/ob/obpy/v1/partyInfo/.search
Party to Account Relationship File Upload
  • New File Upload process is introduced to update Party to Account Relationships
  • Key Capabilities
    • Enables add / replace / remove operations for Party to Account Relationship via file upload.
    • For replace and remove, uniquely identify the target party to account relationship record using cif id, accounts number and party relationship.
    • Reject Operation, If the provided combination does not resolve to a single unique record.
  • Field Value Handling Rules
    • Empty string ("") or literal "null"
      • Interpreted as an explicit request to delete/clear the existing value.
      • System will overwrite the field and set it to blank/removed.
    • Literal "no_update" .
      • Interpreted as no change requested.
    • System will ignore the field and retain the existing value.
  • Duplicate Records (Replace Operation)
    • If duplicate records are provided for a replace operation, the feed will follow an upsert behavior:
      • Subsequent records will overwrite earlier records for the same identified contact entry.
  • Immutable identifiers
    • The following fields are immutable and cannot be updated (including via replace):
      • CIF ID
      • ACCOUNT_NUMBER
      • PARTY_RELATIONSHIP
  • External validations
    • No external validation is performed for CIF ID and Account Number.

Note: OB Party to Account Patch API FA Codes must be mapped to required Role for File Upload Bulk Amendment Process.

All Party Relationship View

Added a new section that consolidates and displays all party to party relationships in a single view.

Impacted UIs:

  • Party Management
    • Amendment - Review
    • View
  • Insta Party Management
    • Amendment - Review
    • View
Audit Field Migration Support

Enhanced the OB Party Data Migration process to support migration of Audit Date/Time fields at the Data Segment level for:

  • Retail and SMB Party Information
  • Retail and SMB Party-to-Party Relationships
  • Retail and SMB Party-to-Account Relationships
Last Contact Details

Update Enhanced Party operations to introduce a Customer-Induced Indicator, and updated Last Contact details to reflect whether the activity was customer-induced or non-customer-induced.

Impacted APIs:

  • POST - /service/v1/retail/partyAmend
  • POST - /ob/obpy/party/v2/retail/party-amendments
  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH, PUT - /service/v1/retail/basicInfo
  • POST - GET - /ob/obpy/party/v1/retail/basicInfo/.search
  • PATCH, PUT - /service/v1/retail/addressInfo
  • POST - GET - /ob/obpy/party/v1/retail/addressInfo/.search
  • POST - GET - /ob/obpy/party/v1/addressInfo/.search
  • PATCH, PUT - /service/v1/retail/idInfo
  • POST - GET - /ob/obpy/party/v1/retail/idInfo/.search
  • PATCH, PUT - /service/v1/retail/contactInfo
  • POST - GET - /ob/obpy/party/v1/retail/contactInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/partyAddInfo
  • POST - GET - /ob/obpy/party/v1/retail/partyAddInfo/.search
  • PATCH, PUT - /service/v1/retail/taxInfo
  • POST - GET - /ob/obpy/party/v1/retail/taxInfo/.search
  • PATCH, PUT - /service/v1/retail/employment
  • POST - GET - /ob/obpy/party/v1/retail/employment/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/consentPreference
  • POST - GET - /ob/obpy/party/v1/retail/consentPreference/.search
  • PATCH, PUT - /ob/obpy/party/v1/retail/partyServiceMember
  • POST - GET - /ob/obpy/party/v1/retail/partyServiceMember/.search
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH, PUT - /service/v1/smb/businessDetails
  • POST - GET - /ob/obpy/party/v1/smb/businessDetails/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/addressInfo
  • POST - GET - /ob/obpy/party/v1/smb/addressInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/contactInfo
  • POST - GET - /ob/obpy/party/v1/smb/contactInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/smb/taxInfo
  • POST - GET - /ob/obpy/party/v1/smb/taxInfo/.search
  • PATCH, PUT - /ob/obpy/party/v1/partyToAccount
  • POST - GET - /ob/obpy/party/v1/partyToAccount/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/household
  • PUT - /ob/obpy/party/v1/partyToParty/household/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/household/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/poa
  • PUT - /ob/obpy/party/v1/partyToParty/poa/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/poa/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/serviceMember
  • PUT - /ob/obpy/party/v1/partyToParty/serviceMember/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/serviceMember/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/guardian
  • PUT - /ob/obpy/party/v1/partyToParty/guardian/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/guardian/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/custodian
  • PUT - /ob/obpy/party/v1/partyToParty/custodian/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/custodian/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/solicitor
  • PUT - /ob/obpy/party/v1/partyToParty/solicitor/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/solicitor/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/relatedToInsider
  • PUT - /ob/obpy/party/v1/partyToParty/relatedToInsider/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/relatedToInsider/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/owner
  • PUT - /ob/obpy/party/v1/partyToParty/owner/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/owner/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/guarantors
  • PUT - /ob/obpy/party/v1/partyToParty/guarantors/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/guarantors/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/authorizedSignatory
  • PUT - /ob/obpy/party/v1/partyToParty/authorizedSignatory/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/authorizedSignatory/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/suppliers
  • PUT - /ob/obpy/party/v1/partyToParty/suppliers/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/suppliers/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/trustee
  • PUT - /ob/obpy/party/v1/partyToParty/trustee/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/trustee/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/beneficiary
  • PUT - /ob/obpy/party/v1/partyToParty/beneficiary/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/beneficiary/.search
  • PATCH - /ob/obpy/party/v1/partyToParty/relatedParty
  • PATCH - /ob/obpy/party/v2/partyToParty/relatedParty
  • PUT - /ob/obpy/party/v1/partyToParty/relatedParty/{id}
  • PUT - /ob/obpy/party/v2/partyToParty/relatedParty/{id}
  • POST - GET - /ob/obpy/party/v1/partyToParty/relatedParty/.search
  • POST - GET - /ob/obpy/v1/party/.search
  • POST - GET - /ob/obpy/v1/partyInfo/.search
  • GET - /service/v1/getParty/{partyId}

Impacted UIs:

  • Party Management
    • Onboarding
    • Amendment
    • View
  • Insta Party Management
    • Onboarding
    • Amendment
    • View
  • Party to Party
  • Party to Account
  • Party History
    • Address History
Party Address History

Introduced a new capability to view a Party’s historical addresses. Users can filter results by Start Date and End Date to retrieve address history for a specific period. The historical address view includes all amended versions of the Party’s addresses over time.

Impacted APIs:

  • POST - /service​/v1​/retail​/party​/history
Remove Future Date Validation

Future Date is allowed for following fields on UI, Service and Migration

  • Retail / SMB - Basic Info / Business Details | memberStartDate
  • Retail / SMB | ID Details | validFrom
  • Retail / SMB | Tax Declaration | certificationDate
  • Retail / SMB | Tax Declaration | validFrom
  • Retail | Employment Details (Salaried/Self-Employed) | startDate
  • Retail | Additional Details | fidmdateOfReport
  • Retail / SMB | Party To Account | startDate

Impacted APIs:

  • POST - /service/v1/retail/onboardParty
  • POST - /ob/obpy/party/v2/retail/party-onboardings
  • POST - /service/v1/retail/partyAmend
  • POST - /ob/obpy/party/v2/retail/party-amendments
  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH, PUT - /service/v1/retail/basicInfo
  • PATCH, PUT - /service/v1/retail/idInfo
  • PATCH, PUT - /ob/obpy/party/v1/retail/partyAddInfo
  • PATCH, PUT - /service/v1/retail/taxInfo
  • PATCH, PUT - /service/v1/retail/employment
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH, PUT - /service/v1/smb/businessDetails
  • PATCH, PUT - /ob/obpy/party/v1/smb/taxInfo
  • POST, PUT, PATCH - /ob/obpy/party/v1/partyToAccount

Impacted UIs:

  • Party Management
    • Onboarding
    • Amendment
  • Insta Party Management
    • Onboarding
    • Amendment
  • Party to Party
  • Party to Account
  • Data Segment Amendment
    • Basic Info & Citizenship
    • Business Details
    • Current Address
    • ID Details
    • Tax Declaration
    • Salaried Employment
    • Self-Employed
    • Additional Info
    • Party To Account
Address Standardization

The Address Data Segment has been enhanced as part of the address standardization initiative across Oracle Banking products, enabling a uniform and consistent approach to address management.

  • Address Structure: System now supports Structured and Unstructured address formats.

  • Address lifecycle support: System now supports past, current and future-dated addresses using standardized. Active/Inactive/Future definitions based on Effective Date and End Date.

  • Stronger address date validations: Introduced controls to ensure data integrity, including:
    • Only one Active address per Address Type at any time.
    • No overlapping address periods
    • No gaps in address history
    • Valid date ranges enforced
  • Replication rules to CMC:
    • CMC External Customer: Replicates the Active Communication Address.
    • CMC Customer Address: Replicates all address with Active Communication Address is set as Preferred.
  • Centralized Address Type maintenance: Address Types will be maintained in Common Maintenance for reuse across all OBCS products.

Key Notes

  • Unstructured Address: Unstructured Address fields names are preserved to avoid any disruption to existing clients.
  • Structured Address:
    • Field names updated and new structured fields introduced
    • Legacy field names in requests are not persisted in OB Party
    • Structured address format support is currently available for the Rest of World region in Party Management and Insta Party Management. The Data Segment Amendment UI displays both Unstructured and Structured address formats.

Migration Scope

  • Address enhancements are not included in Party Migration for this release; planned for a future release.

Configuration Prerequisites

  • For Record Maintenance and Address Maintenance, Common Core Address Types and OB Party Address Types (Entity Code) must match exactly:
    • C = Communication
    • R = Residential

Future Dated Address

  • Future-dated addresses are supported; however, a party must have an Active address (cannot exist with only a Future address).

Impacted APIs:

  • POST - /service/v1/retail/onboardParty
  • POST - /ob/obpy/party/v2/retail/party-onboardings
  • POST - /service/v1/retail/partyAmend
  • POST - /ob/obpy/party/v2/retail/party-amendments
  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH - /service/v1/retail/addressInfo
  • PUT - /service/v1/retail/addressInfo
  • GET - /service/v1/retail/addressInfo/{externalCustomerNo}
  • POST-GET - /ob/obpy/party/v1/retail/addressInfo/.search
  • POST-GET - /ob/obpy/party/v1/addressInfo/.search
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH - /ob/obpy/party/v1/smb/addressInfo
  • PUT - /ob/obpy/party/v1/smb/addressInfo
  • GET - /ob/obpy/party/v1/smb/addressInfo/{externalCustomerNo}
  • POST-GET - /ob/obpy/party/v1/smb/addressInfo/.search
  • POST-GET - /ob/obpy/v1/party/.search
  • POST-GET - /ob/obpy/v1/partyInfo/.search
  • GET - /service/v1/getParty/{partyId}
  • POST - /service/v1/initiatePartyOnboarding
  • POST - /service/v1/initiateCorpPartyOnboarding
  • POST - /service/v1/initiateSmePartyOnboarding
  • POST - /service/v1/initiateSMBPartyOnboarding
  • POST-GET - /ob/obpy/party/v1/address/latest/.search

Impacted UIs:

  • Party Management
    • Onboarding
    • Amendment
    • View
  • Insta Party Management
    • Onboarding
    • Amendment
    • View
  • Data Segment Amendment
    • Current Address
  • Party History
    • Address History

Migration Impact:

Note: Data Migration is not enhanced as per Address Standardization will be taken up in subsequent releases.

SMB "Business Name-1" is renamed as "Doing Business As" Impacted APIs:
  • POST - /service/v1/smb/onboardParty
  • POST - /ob/obpy/party/v2/smb/party-onboardings
  • POST - /service/v1/smb/partyAmend
  • POST - /ob/obpy/party/v2/smb/party-amendments
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH / PUT - /service/v1/smb/businessDetails
  • POST - GET - /ob/obpy/party/v1/smb/businessDetails/.search
  • POST - GET - /ob/obpy/v1/party/.search
  • POST - GET - /ob/obpy/v1/partyInfo/.search
  • GET - /service/v1/getParty/{partyId}

Impacted UIs:

  • Party Management (SMB)
    • Onboarding
    • Amendment
    • View
  • Insta Party Management (SMB)
    • Onboarding
    • Amendment
    • View
  • Data Segment Amendment
    • Business Details

Migration Impact:

  • SMB Party Info
Adoption of DBMS Cloud Adoption of DBMS_CLOUD to accelerate, secure, and simplify the migration of Party domain data from flat files in OCI Object Storage to the Oracle database.

Functional Activity Code:

OBPY_FA_DATALOAD_RUN_BATCH_FOR_STAGE_TWO_TH REE_SERVICEAPI

Impacted APIs:
  • POST - /migrations/runBatchForStage2And3
Soft Delete Soft Delete is introduced to update record status and audit fields rather than physically removing the record. Soft delete is applicable at record level but not fields level.
  • Soft Delete is supported only via PATCH “remove” operations for Data Segments that support PATCH.
  • PUT and POST do not support Soft Delete for any Data Segment.
  • Soft-deleted records cannot reuse the same Record Identifier.
  • Soft Delete will be available only through Data Segment amendment UI that generate events containing amended fields only.
  • STP / Insta Amendment UIs will not support Soft Delete.
  • "includeDelete" parameter is introduced in search APIs to include or exclude soft deleted records.
  • For soft-deleted records, events will include audit attributes populated in event values, including:
    • Record Stat
    • Updated By
    • Updated Date
    • and related fields will be populated in the event values for soft-deleted records
  • Consent and Preference data segment - Question Cannot be Deleted.
  • Record stat modification for soft deleted record will be ignored in add and replace operation in Patch APIs.

Impacted APIs:

  • PATCH - /ob/obpy/party/v1/retail/granular
  • PATCH - /ob/obpy/party/v2/retail/granular
  • PATCH - /service/v1/retail/addressInfo
  • PATCH - /service/v1/retail/idInfo
  • PATCH - /service/v1/retail/contactInfo
  • PATCH - /ob/obpy/party/v1/retail/partyAddInfo
  • PATCH - /service/v1/retail/taxInfo
  • PATCH - /service/v1/retail/employment
  • PATCH - /ob/obpy/party/v1/retail/consentPreference
  • PATCH - /ob/obpy/party/v1/retail/partyServiceMember
  • PATCH - /ob/obpy/party/v1/smb/amendParty
  • PATCH - /ob/obpy/party/v2/smb/amendParty
  • PATCH - /ob/obpy/party/v1/smb/addressInfo
  • PATCH - /ob/obpy/party/v1/smb/contactInfo
  • PATCH - /ob/obpy/party/v1/smb/taxInfo
  • PATCH - /ob/obpy/party/v1/partyToAccount
  • PATCH - /ob/obpy/party/v1/partyToParty/household
  • PATCH - /ob/obpy/party/v1/partyToParty/poa
  • PATCH - /ob/obpy/party/v1/partyToParty/serviceMember
  • PATCH - /ob/obpy/party/v1/partyToParty/guardian
  • PATCH - /ob/obpy/party/v1/partyToParty/custodian
  • PATCH - /ob/obpy/party/v1/partyToParty/solicitor
  • PATCH - /ob/obpy/party/v1/partyToParty/relatedToInsider
  • PATCH - /ob/obpy/party/v1/partyToParty/owner
  • PATCH - /ob/obpy/party/v1/partyToParty/guarantors
  • PATCH - /ob/obpy/party/v1/partyToParty/authorizedSignatory
  • PATCH - /ob/obpy/party/v1/partyToParty/suppliers
  • PATCH - /ob/obpy/party/v1/partyToParty/trustee
  • PATCH - /ob/obpy/party/v1/partyToParty/beneficiary
  • PATCH - /ob/obpy/party/v1/partyToParty/relatedParty
  • PATCH - /ob/obpy/party/v2/partyToParty/relatedParty

Impacted UIs:

  • Data Segment Amendment
    • Basic Info & Citizenship
    • Business Details
    • Current Address
    • ID Details
    • Contact Details
    • Tax Declaration
    • Salaried Employment
    • Self-Employed
    • Consent & Preferences
    • Additional Info
    • Service Member Info
    • Party To Account
    • Party To Party
Exclusion List is introduced in /ob/obpy/v1/party/.search Service / includeDelete As performance improvement initiative, an exclusion list is been added to POST-GET APIs

Impacted APIs:

  • POST GET - obpy-party-services/ob/obpy/v1/party/.search

Table 1-5 List of Functional Activity Codes

Functional Activity Code Action Description
OBPY_FA_DATALOAD_RUN_BATCH_FOR_STAGE_TWO_THREE_SERVICEAPI MIGRATION Dataload: run batch for stage two/three
OBPY_FA_DATALOAD_VIEW_PRESTAGING_FAILED_ERRORS_SERVICEAPI MIGRATION Dataload: view pre-staging failed errors
OBPY_FA_DS_AMEND_MENU MENU Data Segment amend menu
OBPY_FA_BASIC_INFO_AMEND_MENU MENU Basic Info amend menu
OBPY_FA_BUSINESS_DETAILS_AMEND_MENU MENU Business Details amend menu
OBPY_FA_ADDRESS_AMEND_MENU MENU Address amend menu
OBPY_FA_ID_AMEND_MENU MENU ID amend menu
OBPY_FA_CONTACT_AMEND_MENU MENU Contact amend menu
OBPY_FA_TAX_AMEND_MENU MENU Tax amend menu
OBPY_FA_SALARIED_AMEND_MENU MENU Salaried amend menu
OBPY_FA_SELF_EMPLOYED_AMEND_MENU MENU Self-employed amend menu
OBPY_FA_CONSENT_PREFERENCE_AMEND_MENU MENU Consent Preference amend menu
OBPY_FA_ADDITIONAL_INFO_AMEND_MENU MENU Additional Info amend menu
OBPY_FA_SERVICE_MEMBER_AMEND_MENU MENU Service Member amend menu
OBPY_FA_ADDRESS_WEB_PATCH PATCH Address web API update (PATCH)
OBPY_FA_ID_INFO_WEB_PATCH PATCH ID Info web API update (PATCH)
OBPY_FA_TAX_WEB_PATCH PATCH Tax web API update (PATCH)
OBPY_FA_ADD_INFO_WEB_PATCH PATCH Additional Info web API update (PATCH)
OBPY_FA_CONSENT_WEB_PATCH PATCH Consent web API update (PATCH)
OBPY_FA_BUSINESS_DETAILS_WEB_PATCH PATCH Business Details web API update (PATCH)
OBPY_FA_BASIC_INFO_WEB_PATCH PATCH Basic Info web API update (PATCH)
OBPY_FA_EMPLOYMENT_WEB_PATCH PATCH Employment web API update (PATCH)
OBPY_FA_CONTACT_WEB_PATCH PATCH Contact web API update (PATCH)
OBPY_FA_SERVICEMEMBER_WEB_PATCH PATCH Service Member web API update (PATCH)
OBPY_FA_ADDRESS_WEB_GET GET Address web API retrieve (GET)
OBPY_FA_ID_INFO_WEB_GET GET ID Info web API retrieve (GET)
OBPY_FA_TAX_WEB_GET GET Tax web API retrieve (GET)
OBPY_FA_ADD_INFO_WEB_GET GET Additional Info web API retrieve (GET)
OBPY_FA_CONSENT_WEB_GET GET Consent web API retrieve (GET)
OBPY_FA_BUSINESS_DETAILS_WEB_GET GET Business Details web API retrieve (GET)
OBPY_FA_BASIC_INFO_WEB_GET GET Basic Info web API retrieve (GET)
OBPY_FA_EMPLOYMENT_WEB_GET GET Employment web API retrieve (GET)
OBPY_FA_CONTACT_WEB_GET GET Contact web API retrieve (GET)
OBPY_FA_SERVICEMEMBER_WEB_GET GET Service Member web API retrieve (GET)
OBPY_FA_LAST_CONTACT_WEB_POST POST Save last contact date
OBPY_FA_LAST_CONTACT_WEB_GET GET Fetch last contact date
OBPY_FA_PARTY_LOV LOV Party list-of-values
OBPY_FA_RELATED_PARTY_REL_PATCH_WEB PATCH Related party relationship update (PATCH)
OBPY_FA_PARTY_PARTY_PATCH_MENU MENU Party-to-party patch menu
OBPY_FA_KYC_STATUS_GET GET Retrieve KYC status
OBPY_FA_CUST_LAST_TXNS_FETCH GET Fetch customer last transactions
OBPY_FA_CUST_UPCOMING_EVENTS_FETCH GET Fetch customer upcoming events
OBPY_FA_CUSTOMER_ALERTS_FETCH GET Fetch customer alerts
OBPY_FA_GET_PARTY_STAKEHOLDER GET Retrieve party stakeholder
OBPY_FA_CUSTOMER_SUMMARY_FETCH GET Fetch customer summary
OBPY_FA_CUSTOMER_DETAILS_FETCH GET Fetch customer details
OBPY_FA_CUSTOMER_SIGNIMAGES_FETCH GET Fetch customer signature images
OBPY_FA_CUSTOMER_HOUSEHOLD_FETCH GET Fetch customer household
OBPY_FA_CUST_HOUSEHOLD_FETCH GET Fetch customer household
OBPY_FA_CUSTOMER_SCHEMES_FETCH GET Fetch customer schemes
OBPY_FA_SAVORG_OD GET Retrieves savings organization overdraft organizational data (as provided)
OBPY_FA_BUSINESSPROCESS_GETBY_ID GET GET API to retrieve a Business Process by ID (as provided)
OBPY_FA_BUSINESSPROCESS_POST POST POST API to create a Business Process instance (as provided)
OBPY_FA_CURORG_OD GET Retrieves current organization overdraft snapshot (as provided)
OBPY_FA_BUSINESSPROCESS_HISTORY GET Retrieves Business Process history audit (as provided)
OBPY_FA_BUSINESSPROCESS_GET GET GET API to retrieve a Business Process instance (as provided)
OBPY_FA_RETAIL_PARTY_LIMITED_KYC_EXPIRED_EVENT EVENT Limited Party Expired Event (as provided)
OBPY_FA_SECTOR_BSD_PARTYDTLS GET Get Party based on sector Service API (as provided)
OBPY_FA_MEMO_SUMMARY GET Web API to get Memo Summary (as provided)
OBPY_FA_MEMO_EMB_POST POST Memo embedding API (as provided)
OBPY_FA_MEMO_INS_POST POST Memo insights fetch API (as provided)
OBPY_FA_PARTY_HISTORY_POST POST Fetch history data based on data segment code (as provided)
OBPY_FA_DS_HISTORY_MENU MENU Party History Menu (as provided)
OBPY_FA_ADDRESS_HISTORY_MENU MENU Address History Menu (as provided)
OBPY_FA_PARTY_ACCOUNT_PATCH_MENU MENU Party account patch menu
OBPY_FA_PARTY_ACCOUNT_PATCH_WEB PATCH Party account web API update (PATCH)

Parent topic: Release Enhancements