Results for “bank_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PER_JP_BANK_LOOKUP_V is a Japanese localization view owned by the APPS schema and catalogued under the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is simply "JP specific," indicating that it exists to serve Japan legislative requirements rather than a global, cross-region business function. The view exposes a de-duplicated list of Japanese banks, returning the bank code alongside two name attributes: the standard bank name and the bank name expressed in kana script. Because it presents a clean, pre-joined lookup set, the view is typically consumed as a reference or list-of-values source in HR and payroll-related reporting rather than as a transactional entity in its own right.

The user search term bank_name_kana maps directly to one of the three columns the view publishes, which confirms the object as the appropriate source when kana-form bank names must be retrieved or displayed.

Underlying Base Objects

The view is defined over two synonyms recorded in the ETRM metadata: PAY_JP_BANKS and PAY_JP_BANK_BRANCHES. The defining query joins the branch table to the bank table on the common key BANK_CODE, then projects the bank-level attributes outward. The full view text is:

SELECT V.BANK_CODE, V.BANK_NAME, V.BANK_NAME_KANA
FROM (SELECT BNK.BANK_CODE, BNK.BANK_NAME, BNK.BANK_NAME_KANA,
             BCH.BRANCH_CODE, BCH.BRANCH_NAME, BCH.BRANCH_NAME_KANA
      FROM PAY_JP_BANK_BRANCHES BCH, PAY_JP_BANKS BNK
      WHERE BCH.BANK_CODE = BNK.BANK_CODE) V
GROUP BY V.BANK_CODE, V.BANK_NAME, V.BANK_NAME_KANA

The inner query performs an equijoin between the branch and bank entities, producing one row per bank-branch combination. The outer query then applies a GROUP BY across BANK_CODE, BANK_NAME, and BANK_NAME_KANA. The practical effect of this grouping is to collapse the branch-level fan-out and return a distinct, bank-level result set. Branch columns are computed in the inline view but deliberately excluded from the final projection, so the view functions as a bank master lookup derived from the branch hierarchy.

Key Columns

• BANK_CODE — The unique identifier for the Japanese bank. This is the joining key between PAY_JP_BANKS and PAY_JP_BANK_BRANCHES and the primary lookup key for the view.
• BANK_NAME — The bank name in its standard (typically kanji or formal) representation.
• BANK_NAME_KANA — The bank name rendered in kana script. This is the column surfaced by the user's bank_name_kana search and is the distinguishing attribute of the view, supporting kana-sensitive display, sorting, and matching requirements specific to Japanese operations.

Common Use Cases and Queries

Typical usage centers on validating, displaying, or populating Japanese bank information in HR and payroll contexts. A straightforward lookup by bank code:

SELECT bank_code, bank_name, bank_name_kana
FROM   apps.per_jp_bank_lookup_v
WHERE  bank_code = :p_bank_code;

A kana-oriented search, useful where the operator enters kana text:

SELECT bank_code, bank_name, bank_name_kana
FROM   apps.per_jp_bank_lookup_v
WHERE  bank_name_kana LIKE :p_kana_pattern
ORDER  BY bank_name_kana;

The view also serves as a list-of-values source for bank selection fields, supplying BANK_CODE as the value and BANK_NAME_KANA as the displayed description. Because the view is read-only and its GROUP BY collapses branch detail, it should not be used to retrieve branch-level records; queries requiring branch codes or branch kana names must address PAY_JP_BANK_BRANCHES directly. Where report output must align with Japanese naming conventions, joining the view back to transactional tables on BANK_CODE provides consistent kana rendering.