Results for “cefv_bank_branches”

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

Overview

CEFV_BANK_BRANCHES is an Oracle EBS business view owned by the APPS schema and validated against the CE - Cash Management product. It is classified by ETRM as a business view rather than a base table, meaning it exposes a curated, presentation-oriented projection of bank branch data intended for reporting, inquiry, and integration consumption rather than transactional maintenance. The view is implemented over the internal view CE_BANK_BRANCHES_V and inherits its read-only behavior through a WITH READ ONLY clause, so consumers can query branch and bank reference data without risk of mutating the underlying Cash Management records.

In EBS 12.1.1 and 12.2.2, this view serves as a stable reporting surface for bank, branch, and contact information used across Cash Management functions and any external or custom application that requires branch reference data. Because it is owned by APPS and marked VALID, it can be referenced directly from customer SQL, concurrent programs, and interface extracts.

Underlying Base Objects

ETRM documents a single referenced base object for this view: CE_BANK_BRANCHES_V (VIEW). CEFV_BANK_BRANCHES does not reach into the tables beneath CE_BANK_BRANCHES_V directly; instead it layers a column-renaming and formatting projection over that view. The documented view text confirms a straightforward SELECT from CE_BANK_BRANCHES_V BB WITH READ ONLY, aliased as BB, with output columns renamed and, in several positions, populated with typed NULL placeholders (TO_CHAR(NULL), TO_DATE(NULL), TO_NUMBER(NULL)) to preserve a fixed column contract for downstream consumers.

The presence of these NULL placeholders indicates that CEFV_BANK_BRANCHES is designed to match an expected column layout while only certain positions carry live data. It also exposes a descriptive flexfield style label column, '_LA:BB.BANK_INSTITUTION_TYPE:CE_LOOKUPS:INSTITUTION_TYPE:MEANING', which resolves the institution type meaning from the INSTITUTION_TYPE lookup.

Key Columns

The view exposes bank and branch identifiers and descriptive attributes, address elements, contact details, and EFT/EDI settlement references.

• BRANCH_PARTY_ID / BANK_BRANCH_ID: unique identifier for the bank branch party record.
• BANK_NAME, BANK_NAME_ALT, BANK_NUMBER: bank-level identification, including alternate name.
• BANK_BRANCH_NAME, BANK_BRANCH_NAME_ALT, BRANCH_NUMBER, BANK_BRANCH_TYPE: branch-level identification and classification.
• ADDRESS_LINE1 through ADDRESS_LINE4, CITY, PROVINCE/STATE, ZIP, COUNTRY, COUNTY: geographic and address data.
• CONTACT_FIRST_NAME, CONTACT_MIDDLE_NAME, CONTACT_LAST_NAME, CONTACT_PREFIX, CONTACT_TITLE, plus AREA_CODE and PHONE: branch contact information. The CONTACT_MIDDLE_NAME column is the documented contact attribute matching the search term "contact_middle_name".
• EFT_USER_NUMBER, EFT_SWIFT_CODE, EDI_ID_NUMBER: electronic settlement and routing identifiers.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: audit/WHO columns.
• _LA:INSTITUTION_TYPE: descriptive flexfield lookup value for the bank institution type.

Common Use Cases and Queries

Typical usage includes branch reference extracts, payment/EFT routing validation, and report queries that need contact and address details for a branch. Because the view is read only, it is safe for ad hoc querying and joins to payment or supplier records.

SELECT bb.branch_party_id, bb.bank_name, bb.bank_branch_name,
       bb.contact_first_name, bb.contact_middle_name, bb.contact_last_name,
       bb.eft_swift_code, bb.edi_id_number
FROM   apps.cefv_bank_branches bb
WHERE  UPPER(bb.bank_branch_name) LIKE UPPER(:branch_pattern)
ORDER BY bb.bank_name, bb.bank_branch_name;

Consumers requiring middle-name contact detail, institution-type meaning, or settlement identifiers can query these columns directly without accessing CE_BANK_BRANCHES_V or the base Cash Management tables, preserving support and upgrade stability.