Results for “apfv_bank_branches”

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

Overview

APFV_BANK_BRANCHES is a business view in the Oracle E-Business Suite Payables (AP) module. It presents bank and bank branch information maintained in Oracle Payables in a form suitable for inquiry, reporting, and integration with electronic payment and electronic data interchange (EDI) processes. The view is defined over the AP_BANK_BRANCHES table and is exposed as a read-only object (the view text terminates with WITH READ ONLY), meaning no DML is permitted against it directly.

The object is documented as a "business view," which in ETRM terminology indicates that it is one of the views used by the applications' business logic or by external interfaces rather than a purely technical or DBA-owned object. Notably, the ETRM metadata records that the view is "Not implemented in this database," so the definition provided in the documentation reflects the shipped definition rather than a confirmed runtime instance on the source environment. This distinction is important when validating availability across an actual 12.1.1 or 12.2.2 instance: the view exists in the data model and documentation, but implementations should confirm its presence in their own database before depending on it.

Because the view surfaces EFT and EDI attributes, it is commonly used where bank branch data feeds payment formats and remittance or bank-file transmissions. It is related to the user search term edi_id_number, which appears as a column in the view and corresponds to the EDI identification number stored for a bank branch.

Underlying Base Objects

The view is defined as a simple projection with no joins or aggregations. Its SQL selects directly from the AP_BANK_BRANCHES table, aliased as BB, and each exposed column maps one-to-one to a column of that table. The ETRM metadata states that referenced base objects are "none documented" and the owner is not recorded, but the view text itself unambiguously identifies AP_BANK_BRANCHES as the source.

Several entries in the SELECT list are not plain table columns but descriptive-flex or lookup markers. For example, the expression referencing INSTITUTION_TYPE resolves the institution type through AP_LOOKUP_CODES, and the '_DF:SQLAP:AP_BANK_BRANCHES:BB' and '_DF:JG:JG_AP_BANK_BRANCHES:BB' markers denote descriptive flexfield contexts for the SQLAP (Payables) and JG (global) applications. These markers drive the naming and population of flexfield segments when the view is used in reporting tools.

Key Columns

• BANK_BRANCH_ID — Primary identifier for the bank branch record.
• BANK_NAME / ALTERNATE_BANK_NAME — Bank name and its alternate-language equivalent.
• BANK_NUMBER — The bank number used to identify the institution.
• BANK_BRANCH_NAME / ALTERNATE_BANK_BRANCH_NAME — Branch name and its alternate-language equivalent.
• BANK_BRANCH_NUMBER — Branch number, listed in the column documentation as BANK_BRANCH_NUMBER and derived from BANK_NUM.
• BANK_BRANCH_TYPE / "_LA:INSTITUTION_TYPE" — Branch type and the lookup-resolved institution type.
• ACTIVE_DATE / END_DATE — Effective and end dates, mapped to START_EFFECTIVE_DATE and END_EFFECTIVE_DATE in the column list.
• Address and contact columns — ADDRESS_LINE1 through ADDRESS_LINE4, CITY, COUNTY, STATE, ZIP, COUNTRY, plus AREA_CODE, PHONE, and contact name fields.
• EFT_USER_NUMBER and EFT_SWIFT_CODE — Identifiers used for electronic funds transfer and SWIFT messaging.
• EDI_ID_NUMBER — The Electronic Data Interchange identification number assigned to the bank branch, used in EDI-based payment and remittance processing.
• "_DF" and "_DF:GLBL" — Descriptive flexfield placeholders for application-specific and global segments.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include reviewing active bank branches for payment setup, extracting branch EDI and EFT identifiers for third-party or bank-format integrations, and populating reports that require institution type. A basic query retrieving the identifier and EDI number is:

SELECT bank_branch_id, bank_name, bank_branch_name, edi_id_number
FROM   apfv_bank_branches
WHERE  edi_id_number IS NOT NULL;

Filtering active branches by effective date is also common:

SELECT bank_name, bank_branch_name, eft_swift_code, edi_id_number
FROM   apfv_bank_branches
WHERE  active_date <= SYSDATE
AND   (end_date IS NULL OR end_date >= SYSDATE);

The view is declared read-only, so it is suitable for SELECT-based reporting and integration extracts only. Implementers should confirm the object's presence in the target instance, given the ETRM note that it was not implemented in the documented database.