Results for “lookup_code”

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

Overview

The view APPS.AP_BANK_CHARGE_BEAERER_SRS_V is a Payables (AP) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of valid, active values for the Bank Charge Bearer lookup type, presenting them in a normalized form suitable for concurrent program parameters and Oracle Reports / SRS (Standard Report Submission) parameter lists. The view carries a status of VALID in the ETRM metadata for release 12.2.2 and is owned by the APPS schema.

Its primary function is to translate the stored lookup codes for the BANK CHARGE BEARER lookup type into user-facing descriptions. In payment processing, the bank charge bearer determines which party—the remitter (supplier/internal), the beneficiary, or a shared arrangement—bears the bank charges associated with a payment. The view conditions the returned rows so that only lookup codes with no inactive date, or an inactive date in the future, are shown, effectively filtering out retired bearer options from any selection list. The intentionally misspelled name (BEAERER) is preserved in the delivered object and should be referenced exactly as shipped.

Underlying Base Objects

The documented base objects referenced by the view are AP_LOOKUP_CODES (itself a view) and FND_GLOBAL (a package). No physical base table is directly referenced in the view text.

• AP_LOOKUP_CODES — Supplies the lookup rows. The view filters on LOOKUP_TYPE = 'BANK CHARGE BEARER' and applies an active-date predicate of NVL(INACTIVE_DATE, SYSDATE+1) > SYSDATE. AP_LOOKUP_CODES is the Payables lookup layer built on the common FND lookup infrastructure.
• FND_GLOBAL — The standard Applications global context package, referenced in the documented dependency list. It is commonly used to derive runtime context such as the current application, user, or responsibility, though the excerpted view text does not visibly invoke it.

Because the view selects from AP_LOOKUP_CODES rather than the underlying FND_LOOKUP_VALUES table directly, it inherits whatever filtering and joins that intermediate view performs, and it further restricts the result set to a single lookup type.

Key Columns

The view projects two unnamed expressions, derived from the columns DISPLAYED_FIELD and LOOKUP_CODE of AP_LOOKUP_CODES:

• Description expression (first column) — A DECODE on LOOKUP_CODE. When the code is 'I' (internal), the full DISPLAYED_FIELD is returned. For any other code, the value is truncated at the first forward slash (/), returning the substring before the slash, or the literal 'SUPPLIER' if no substring can be derived. This maps stored bearer definitions to a clean display label.
• Bearer classification expression (second column) — A second DECODE converting the internal code into a semantic category: 'I' becomes 'INTERNAL'; 'S' becomes 'SUPPLIER'; and a NULL code ('N' as rendered in the text) also resolves to 'SUPPLIER'. This provides a standardized bearer type for downstream processing.
• Source attributes — The contributing columns from AP_LOOKUP_CODES, namely DISPLAYED_FIELD (the human-readable lookup description) and LOOKUP_CODE (the internal short code), along with INACTIVE_DATE and LOOKUP_TYPE used in the filtering predicates.

Common Use Cases and Queries

The view is typically consumed as a value set source for SRS concurrent program parameters, particularly payment-related reports and templates where a bank charge bearer must be selected. It may also be embedded in PL/SQL validation or in custom reports that need a consistent list of active bearer options.

A representative query retrieves all currently active bearer choices:

• SELECT * FROM APPS.AP_BANK_CHARGE_BEAERER_SRS_V;

To constrain results to supplier-borne charges only, filter the classified column:

• SELECT displayed_label, bearer_type FROM APPS.AP_BANK_CHARGE_BEAERER_SRS_V WHERE bearer_type = 'SUPPLIER';

Because the columns are unnamed expressions, callers must reference them positionally or with local aliases; application code should never assume column names beyond those documented. Administrators reviewing or extending bearer options should inspect the BANK CHARGE BEARER lookup in AP_LOOKUP_CODES, since the view reflects that configuration directly and honors inactive-date filtering at query time.