Search Results site_location_id




Overview
Explore in AI Chat

Overview

APPS.IBY_EXT_BANKS_V is a reporting and integration view in Oracle E-Business Suite that exposes external bank information for use by the Payments (IBY) module and downstream consumers. The view is owned by the APPS schema and is documented in ETRM for both 12.1.1 and 12.2.2. Its purpose is to provide a flat, denormalized projection of bank master data — bank party identifiers, institution details, addresses, and site location references — in a form suitable for outbound interfaces, data extraction, and inquiry screens.

The view is notable for its use of literal constants and pseudo-columns. Columns such as CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are hard-coded to the value 1, OBJECT_VERSION_NUMBER is set to 1, CREATION_DATE and LAST_UPDATE_DATE are populated with SYSDATE, and OPERATION_FLAG is fixed at 'Y'. This design indicates the view is intended as a read-only feed representing a single "active" operational state rather than a full audit trail.

Underlying Base Objects

The documented base object referenced by APPS.IBY_EXT_BANKS_V is a single view: CE_BANKS_V, aliased as CEBANK in the defining query. All exposed columns are drawn directly from this source, with no joins to additional tables at the IBY_EXT_BANKS_V level. CE_BANKS_V itself belongs to the Cash Management family of bank views and resolves the underlying bank party, bank branch, and bank account structures maintained through the standard EBS banking model.

Because the only dependency is CE_BANKS_V, the behavior of IBY_EXT_BANKS_V is entirely governed by that view. Consumers should be aware that CE_BANKS_V may apply filters or joins that are invisible at this layer; the projected column set is the definitive contract.

Key Columns

  • SITE_LOCATION_ID — The column most commonly targeted by searches. It carries the site location identifier associated with the bank record, enabling linkage to location and address structures.
  • BANK_PARTY_ID — The party identifier for the bank institution, the primary key for relating bank records to trading partners or suppliers.
  • BANK_NAME / SHORT_BANK_NAME / BANK_NAME_ALT — Primary, abbreviated, and alternate names for the institution.
  • BANK_NUMBER / BANK_INSTITUTION_TYPE / HOME_COUNTRY — Institution number, classification, and the country of domicile.
  • Address1–Address3, City, State, Zipcode, Country — The formatted address block sourced from ADDRESS_LINE1-3, CITY, STATE, ZIP, and COUNTRY.
  • DESCRIPTION / END_DATE — Free-text description and the effective end date of the bank record.
  • OPERATION_FLAG, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Interface control columns, hard-coded as described above.

Common Use Cases and Queries

Typical uses include populating external bank reference files, validating supplier bank details during payment processing, and resolving the SITE_LOCATION_ID for a given bank party. A common lookup by bank party is:

  • SELECT bank_party_id, bank_name, bank_number, site_location_id FROM apps.iby_ext_banks_v WHERE bank_party_id = :p_party_id;
  • SELECT bank_name, short_bank_name, city, country, site_location_id FROM apps.iby_ext_banks_v WHERE site_location_id = :p_site_location_id;
  • SELECT bank_party_id, bank_name, bank_number, address1, city, state, zipcode FROM apps.iby_ext_banks_v WHERE end_date IS NULL OR end_date > SYSDATE;

Because OPERATION_FLAG is always 'Y', the view is well suited to outbound staging where every row is treated as an active operation. Query performance is inherited from CE_BANKS_V, so joins against large bank populations should be filtered on BANK_PARTY_ID or SITE_LOCATION_ID where possible.