Search Results eft_swift_code




Overview
Explore in AI Chat

Overview

IBY_EXT_BANK_BRANCHES_V is a PL/SQL view owned by the APPS schema within Oracle E-Business Suite, delivered as part of the IBY (Payments) product module. It presents a flattened, harmonized representation of external bank branch information drawn from Oracle Cash Management's bank branch repository. Its underlying purpose is to expose bank branch master data to Oracle Payments integration and reporting components through a standardized column layout that conforms to the IBY external party data model.

In Oracle EBS 12.1.1 and 12.2.2, the view functions as a bridge between Cash Management's banking setup data and the Payments module, which requires branch identifiers, addresses, and settlement routing attributes when building payment instructions, formatting remittance files, and processing electronic funds transfers. Because the view is valid in the APPS schema and carries the OPERATION_FLAG and OBJECT_VERSION_NUMBER columns typical of TCA-style integration views, it is suited both to direct SQL querying and to consumption by Oracle Payments' programmatic and file-based payment flows.

Underlying Base Objects

The view is defined over a single documented base object: CE_BANK_BRANCHES_V, itself a view in the Cash Management module. The relationship is strictly one-to-one and read-only — IBY_EXT_BANK_BRANCHES_V selects from CE_BANK_BRANCHES_V without joins, unions, or aggregations, so no additional rows or columns are introduced beyond those explicitly projected. ETRM documents CE_BANK_BRANCHES_V as the sole referenced base object, meaning that maintenance of the underlying branch records (insert, update, and end-dating) is performed through Cash Management and TCA functionality, not through this view. The IBY view therefore acts as a consumer rather than a maintenance interface.

Key Columns

The view exposes twenty-eight columns. Identifying and relationship attributes include BRANCH_PARTY_ID, the primary party identifier of the branch, and BANK_PARTY_ID, which links the branch to its parent bank party. Descriptor columns comprise BANK_BRANCH_NAME, BANK_BRANCH_NAME_ALT, BRANCH_NUMBER, BANK_BRANCH_TYPE, and DESCRIPTION.

Address information is provided through ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, PROVINCE, ZIP, COUNTRY, and HOME_COUNTRY. Settlement-critical fields include EFT_SWIFT_CODE and EFT_USER_NUMBER, used to populate payment formatting and clearing instructions. Date-effective attributes START_DATE and END_DATE support historical and current branch selection.

Integration control columns are generated as literals rather than sourced from the base view: CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are hard-coded to 1; CREATION_DATE and LAST_UPDATE_DATE are set to SYSDATE; OBJECT_VERSION_NUMBER is 1; and OPERATION_FLAG is set to 'Y'. These constants signal that the view is intended for read-only extraction into downstream processes that expect a valid, insertable-shaped row structure.

Common Use Cases and Queries

Typical uses include identifying branches attached to a given bank, retrieving SWIFT or EFT routing details for payment formatting, and validating active branches by date range. Example queries:

  • Retrieve all branches for a bank: SELECT BRANCH_PARTY_ID, BANK_BRANCH_NAME, BRANCH_NUMBER FROM IBY_EXT_BANK_BRANCHES_V WHERE BANK_PARTY_ID = :p_bank_party_id;
  • Fetch EFT/SWIFT attributes: SELECT BRANCH_NUMBER, EFT_SWIFT_CODE, EFT_USER_NUMBER FROM IBY_EXT_BANK_BRANCHES_V WHERE BRANCH_PARTY_ID = :p_branch_party_id;
  • Filter active branches: SELECT * FROM IBY_EXT_BANK_BRANCHES_V WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);