Results for “branch_name_kana”

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

Overview

PER_JP_BANK_LOOKUPS is a concatenated database view owned by the APPS schema in Oracle E-Business Suite. It is delivered as part of the PER (Human Resources) product family and specifically supports the Japanese localization of Oracle Payroll and Human Resources. As its description states, the view is a "Concatenated view of PAY_JP_BANKS and PAY_JP_BANK_BRANCHES." It therefore presents a single, denormalized result set that joins Japanese bank header information to its associated branch records.

Because Oracle EBS stores bank master data and bank branch data in separate tables, reporting and integration processes frequently need both levels of information in one row. PER_JP_BANK_LOOKUPS serves this purpose by exposing bank attributes (code, name, and phonetic kana name) alongside branch attributes (code, name, and phonetic kana name). The view is read-only in nature; it does not introduce new persisted data but rather projects columns from its two base synonym objects. The status of the object is VALID, indicating it is compiled and available for query.

Underlying Base Objects

The view is defined over two referenced base objects, both resolved through synonyms within the APPS schema:

• PAY_JP_BANKS (SYNONYM) — the parent table holding Japanese bank definitions, including bank code, bank name, and bank name kana.
• PAY_JP_BANK_BRANCHES (SYNONYM) — the child table holding branch definitions, including branch code, branch name, branch name kana, and audit columns.

The view text joins these objects with an equijoin on the bank code:

FROM PAY_JP_BANK_BRANCHES BCH, PAY_JP_BANKS BNK WHERE BCH.BANK_CODE = BNK.BANK_CODE

This inner join means the view returns only branches that have a matching bank record. Banks without branches, or branches referencing a non-existent bank code, are excluded. The relationship is effectively a one-to-many join from bank to branch, expanded into a flat row per branch.

Key Columns

The view exposes eleven columns, drawn from the two base objects:

• BANK_CODE — the unique identifier for the Japanese bank; the join key between the two base tables.
• BANK_NAME — the registered name of the bank.
• BANK_NAME_KANA — the phonetic (kana) rendering of the bank name, used for searching and sorting in Japanese.
• BRANCH_CODE — the code identifying the specific bank branch.
• BRANCH_NAME — the registered name of the branch.
• BRANCH_NAME_KANA — the phonetic (kana) rendering of the branch name. This column is particularly relevant to searches such as "branch_name_kana," which are used to locate branches by their phonetic reading.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns carried from the branch record, supporting traceability and change tracking.

Common Use Cases and Queries

Typical uses include Japanese payroll bank transfer setup, employee bank detail validation, and reporting that requires both bank and branch names with kana readings. A sample query to find branches by phonetic name is:

SELECT bank_code, bank_name, branch_code, branch_name, branch_name_kana
FROM apps.per_jp_bank_lookups
WHERE branch_name_kana LIKE 'ｼﾝｼﾞｭｸ%';

To list all branches for a given bank:

SELECT bank_name, branch_code, branch_name, branch_name_kana
FROM apps.per_jp_bank_lookups
WHERE bank_code = '0001'
ORDER BY branch_name_kana;

Because the view joins bank and branch data, it is well suited for LOV (List of Values) definitions and concurrent program extracts that populate bank transfer files for Japanese payroll processing.