Results for “branch_name”

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

Overview

The PAY_JP_BANK_BRANCHES table, owned by the HR schema and delivered as part of the Oracle E-Business Suite Payroll (PAY) module, is a country-specific reference table that stores Japanese bank branch information. It supports the localization requirements for Japan, where payroll disbursements through employee bank accounts must resolve to a valid domestic bank branch before a payment instruction can be generated. The table records the branch-level detail that complements the bank-level detail held in PAY_JP_BANKS, enabling EBS to validate, default, and format bank transfer records in the Japanese payroll and payment processes.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests the object behaves primarily as a descriptive satellite attached to the bank hub/reference structure rather than as an independent hub or a transactional link. It carries the attributes that describe a branch, keyed by its parent bank, and changes to descriptive (non-key) columns such as the branch name or enabled flag are typically tracked as satellite-style attribute updates.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• BANK_CODE — Identifies the parent bank; also the foreign-key column that references PAY_JP_BANKS.BANK_CODE.
• BRANCH_CODE — The branch identifier within a bank. Together with BANK_CODE it forms the surrogate/business primary key PAY_JP_BANK_BRANCHES_PK.
• BRANCH_NAME — The readable branch name, typically in the local character representation.
• BRANCH_NAME_KANA — The branch name rendered in Kana, used for phonetic sorting and matching.
• ENABLED_FLAG — Controls whether the branch record is active and selectable for new transactions.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Define the date-effective window during which the branch record is valid.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.

The surrogate primary key PAY_JP_BANK_BRANCHES_PK is defined on (BANK_CODE, BRANCH_CODE). Two unique indexes serve as business-key candidates: PAY_JP_BANK_BRANCHES_U1 on (BANK_CODE, BRANCH_NAME) and PAY_JP_BANK_BRANCHES_U2 on (BANK_CODE, BRANCH_NAME_KANA). These enforce uniqueness of the branch name and its Kana rendering within a given bank.

Common Use Cases and Queries

Typical uses include validating a branch entry against its parent bank, reporting active branches for a selection list, and joining branch names to payroll bank account assignments.

SELECT b.bank_name, br.branch_code, br.branch_name, br.branch_name_kana
FROM   pay_jp_banks b,
       pay_jp_bank_branches br
WHERE  b.bank_code = br.bank_code
AND    br.enabled_flag = 'Y';

To find branches active on a given date, filter on the date-effective columns:

SELECT branch_code, branch_name
FROM   pay_jp_bank_branches
WHERE  bank_code = :p_bank_code
AND    SYSDATE BETWEEN start_date_active
                   AND NVL(end_date_active, SYSDATE);

Reporting queries frequently use BRANCH_NAME_KANA for ordering, and joins to payroll assignment and payment tables to resolve the destination branch of employee disbursements.

Related Objects

• PAY_JP_BANKS — Parent reference table joined via PAY_JP_BANK_BRANCHES.BANK_CODE = PAY_JP_BANKS.BANK_CODE.
• PAY_JP_BANK_BRANCHES_PK, PAY_JP_BANK_BRANCHES_U1, PAY_JP_BANK_BRANCHES_U2 — Primary and unique indexes enforcing branch identity.
• Payroll Japanese bank/payment setup tables and the payroll bank account assignment objects that consume BANK_CODE and BRANCH_CODE during payment generation.
• HR/Payroll security and lookup views that expose branch selection to users.