Results for “bank_code”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_JP_SS_BANK_LOV_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. As its description states, the view is used exclusively for the Japanese localisation and has no role in other legislations or global payroll processing. Its functional purpose is to supply a list of values (LOV) of bank codes and bank names to Oracle EBS forms and concurrent processes that require the user to select a Japanese financial institution. In the payroll context, this typically supports the entry of employee bank transfer information, such as the bank account designated for net pay disbursement.
The view presents a restricted projection of the underlying bank master data: only banks whose ENABLED_FLAG equals 'Y' are surfaced, and the result set is ordered by BANK_CODE. This filtering and ordering make the view suitable as a direct LOV source without additional query conditions. Status in the ETRM is recorded as VALID, and the object is available in both Oracle EBS 12.1.1 and 12.2.2, with the documented view text and column list consistent across both releases.
Underlying Base Objects
The view is defined over a single referenced object, documented in ETRM 12.2.2 as the synonym PAY_JP_BANKS. In practice, the view text selects from PAY_JP_BANKS, which resolves through the synonym to the corresponding APPS base table holding the Japanese bank master records. The relationship is therefore one-to-one with that table: PAY_JP_SS_BANK_LOV_V introduces no joins, aggregations, or derived tables of its own. Its logic consists solely of column projection, a hard-coded filter on ENABLED_FLAG, NVL-based defaulting of the date columns, and a sort order on BANK_CODE. Because the view is a thin wrapper, any change to the enabled status or descriptive attributes of a bank in the base table is reflected immediately in the LOV with no additional processing.
Key Columns
- BANK_CODE — The bank identifier. This is the primary selection key presented to users and the column on which the view is ordered.
- BANK_NAME — The bank name in the standard character set, used as the primary descriptive LOV value.
- BANK_NAME_KANA — The bank name expressed in Kana, supporting Japanese-language display and phonetic lookup.
- START_DATE_ACTIVE — The date from which the bank record is active. Where the base column is null, the view substitutes 01/01/0001 (TO_DATE('01010001','DDMMYYYY')).
- END_DATE_ACTIVE — The date through which the bank record is active. Where null, the view substitutes 31/12/4712 (TO_DATE('31124712','DDMMYYYY')), the conventional EBS "no end date" value.
The NVL treatment of the two date columns ensures that every row returned by the LOV carries a usable effective date range, preventing null-handling issues in the forms or logic that consume the view.
Common Use Cases and Queries
The principal use case is populating a bank selection LOV during Japanese payroll setup and employee bank detail entry. A typical query mirrors the view's own default behaviour:
SELECT bank_code, bank_name, bank_name_kana FROM apps.pay_jp_ss_bank_lov_v ORDER BY bank_code;— returns the enabled bank list in code order.SELECT bank_code, bank_name FROM apps.pay_jp_ss_bank_lov_v WHERE bank_name_kana LIKE :search_term;— supports phonetic lookup by Kana.SELECT bank_code, start_date_active, end_date_active FROM apps.pay_jp_ss_bank_lov_v WHERE SYSDATE BETWEEN start_date_active AND end_date_active;— restricts results to banks currently within their effective window, useful for validations and reports.
Because the view already excludes disabled banks, queries against it should not add their own ENABLED_FLAG predicate; doing so would be redundant. For diagnostic purposes, comparing the row count of PAY_JP_SS_BANK_LOV_V against the base bank table isolates records that have been disabled. The view is not intended for maintenance operations; bank master data should be updated directly in the underlying Japanese bank table.
-
View: PAY_JP_SS_BANK_LOV_V 12.1.1
This view is only used for the Japanese localisation.
APPS.PAY_JP_SS_BANK_LOV_V·↳ PAY_JP_BANKS·Explore PAY module →
-
View: PAY_JP_SS_BANK_LOV_V 12.2.2
This view is only used for the Japanese localisation.
APPS.PAY_JP_SS_BANK_LOV_V·↳ PAY_JP_BANKS·Explore PAY module →
-
This view is only used for the Japanese localisation.
APPS.PAY_JP_SS_BANK_BRANCH_LOV_V·↳ PAY_JP_BANK_BRANCHES·Explore PAY module →
-
APPS.PAY_JP_MAGTAPE_PAYMENTS_V·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_EXTERNAL_ACCOUNTS·↳ PAY_PAYROLL_ACTIONS·Explore PAY module →
-
APPS.PAY_JP_MAGTAPE_PAYMENTS_V·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_EXTERNAL_ACCOUNTS·↳ PAY_PAYROLL_ACTIONS·Explore PAY module →
-
This table is used for Japanese bank information.
-
This table is used for Japanese bank branch information.
-
This view is only used for the Japanese localisation.
APPS.PAY_JP_SS_BANK_BRANCH_LOV_V·↳ PAY_JP_BANK_BRANCHES·Explore PAY module →
-
Stores bank branch information to enable entry of bank account details with the correct branch information (e.g. GB bank, sort code, branch).
-
This table is used for Japanese bank information.
-
This table is used for Japanese bank branch information.
-
Stores bank branch information to enable entry of bank account details with the correct branch information (e.g. GB bank, sort code, branch).