4 Regional Configuration

This library describes the regional configuration.

Oracle Banking Origination (OBO) has an ability to configure different geography requirements across varied implementation. Using the regional configurator feature, users are configured and enabled for a given Entity ID such as Default and Region Code.

The region specific configurations helps to ensure the workflows adhere to the geography practices, in terms of data capture and visualizations of the application screens. This model supports a framework which is used across OBMA domains to achieve specific end user experience.

Following region specific configuration are implemented:
    • Ability to set non-mandatory field to mandatory
    • Ability to set a field mandatory based on another field
    • Hiding a field
    • Capability to maintain LOV by geography
    • Capability to maintain default value in LOV for a given geography

This chapter describes US region specific configuration which are implemented in OBO.

The fields in below table are defaulted to the respective value from backend. These fields hidden on UI.

Table 4-1 Defaulted Values and Hidden on UI

Field Description
Preferred Currency

Defaulted to USD.

Appears in the Customer Information data segment of the Application Entry stage.

Account Currency

Defaulted to USD.

Appears in the Account Details data segment of the Application Entry stage.

Customer Type

Defaulted to Individual customer type.

Appears in the Customer Information data segment of the Application Entry stage.

Phone Banking

Defaulted to No.

From the Account Service Preferences data segment of the Application Enrichment stage.

Direct Banking

Defaulted to No.

From the Account Service Preferences data segment of the Application Enrichment stage.

Kisok Banking

Defaulted to No.

From the Account Service Preferences data segment of the Application Enrichment stage.

Passbook

Defaulted to No.

From the Account Service Preferences data segment of the Application Enrichment stage.

The fields in below table are not applicable for US region.

Table 4-2 Not Applicable

Field Description
Name in Local Language From in the Customer Information data segment of the Application Entry stage.
Citizenship By From the Customer Information data segment of the Application Entry stage.
Marital Status From the Customer Information data segment of the Application Entry stage.
Details Of Special Need From the Customer Information data segment of the Application Entry stage.
Remark for Special Need From the Customer Information data segment of the Application Entry stage.
Relationship Manager ID From the Customer Information data segment of the Application Entry stage.
Additional Info From all the Address section where applicable.
APY (in %) From the Interest Details data segment of the Application Enrichment stage.

The fields in below table are used with US nomenclature in the respective screen.

Table 4-3 Nomenclature Fields

Field Description
State/ Country Sub Division

The label is changed to State.

Appears in the below stages:

  • In the Address Details sections of the Customer Information data segment in the Application Entry stage.
  • In the Address Details sections of the Nominee Details data segment in the Application Entry stage.
Cheque

The label appears as Check.

Appears in the Account Details data segment of the Application Entry stage.

Appears in the Account Service Preferences data segment of the Application Enrichment stage.