Search Results branch_code




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_SS_BANK_BRANCH_BRANCH_LOV_V is a reporting and list-of-values (LOV) view within the Oracle E-Business Suite Payroll (PAY) module, specifically scoped to Japanese localization functionality. The view exposes the set of enabled bank branch records used by Oracle Payroll for Japan, presenting each branch together with its owning bank code, branch code, branch name, phonetic (Kana) branch name, and effective date ranges. Because the view filters to ENABLED_FLAG = 'Y', it returns only currently active branches suitable for selection in forms, concurrent programs, and integration interfaces.

The name suffix "_LOV_V" indicates the object is intended to back an LOV region in an Oracle Forms-based EBS screen, most likely within a Japanese bank or payroll setup form where an end user must pick a valid branch. The view is owned by APPS and is treated as an Oracle proprietary, confidential object documented in ETRM 12.2.2. Its behavior is consistent across Oracle EBS 12.1.1 and 12.2.2 because the underlying definition relies on a synonym to a base table that remains stable in both releases.

Underlying Base Objects

The view is defined over a single referenced base object, PAY_JP_BANK_BRANCHES, accessed through a synonym. The view performs no joins; it is a projection and filter over that table. The documented view text is:

Two implementation details are significant. First, the ENABLED_FLAG = 'Y' predicate restricts the result set to enabled branches only, so disabled or obsolete entries in the base table are invisible to consumers of the view. Second, the NVL expressions substitute default sentinel dates for null effective dates: 01010001 (1 January, year 1) for a missing start date and 31124712 (31 December, year 4712) for a missing end date. This guarantees that every row returns a bounded date range, which is important for date-driven LOV validation logic.

Key Columns

  • BANK_CODE — Identifier of the parent bank. Together with BRANCH_CODE it forms the logical key used for ordering and lookup.
  • BRANCH_CODE — The branch identifier, and the field the user searched for. This is the value typically captured into payroll or payment setup when a branch is selected.
  • BRANCH_NAME — The display name of the branch, normally presented in the LOV list to the end user.
  • BRANCH_NAME_KANA — The phonetic Kana rendering of the branch name, supporting Japanese-language matching and sorting conventions.
  • START_DATE_ACTIVE — Beginning of the branch's active period, defaulted to 01010001 when null.
  • END_DATE_ACTIVE — End of the branch's active period, defaulted to 31124712 when null.

Common Use Cases and Queries

The primary use case is populating an LOV that allows a user to select a valid Japanese bank branch. A typical lookup by branch code is:

  • SELECT bank_code, branch_code, branch_name FROM apps.pay_jp_ss_bank_branch_lov_v WHERE branch_code = :branch_code;
  • SELECT branch_code, branch_name, branch_name_kana FROM apps.pay_jp_ss_bank_branch_lov_v WHERE bank_code = :bank_code ORDER BY branch_code;
  • SELECT COUNT(*) FROM apps.pay_jp_ss_bank_branch_lov_v WHERE bank_code = :bank_code;

Integration and reporting scenarios include validating that a stored branch code still corresponds to an enabled branch, extracting a branch reference list for a payment file, and driving date-effective checks using the defaulted START_DATE_ACTIVE and END_DATE_ACTIVE columns. Because only enabled branches are exposed, the view is appropriate wherever downstream logic must exclude inactive branches without adding its own filter.