Search Results ar_bpa_items_vl




Overview
Explore in AI Chat

Overview

AR_BPA_ITEMS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered under the Oracle Receivables (AR) product family. It is part of the Bill Presentment Architecture (BPA) data model, which underpins the configurable presentation of bills and statements delivered to customers through Oracle Receivables and related self-service interfaces. The view exposes the definition of individual bill presentation items — the configurable fields, labels, links, totals, images and flexfield prompts that make up a bill template — in the session language of the querying user.

Because it joins the base (B) table to the translation (TL) table on ITEM_ID and restricts rows to the current runtime language through USERENV('LANG'), the view returns exactly one translated row per item for the logged-in user. It therefore behaves as a reporting and integration-friendly read interface: application forms, concurrent programs and custom SQL can select descriptive attributes such as ITEM_NAME, DISPLAY_PROMPT and ITEM_DESCRIPTION without performing the translation join themselves. The DP (display prompt) values obtained here are the labels rendered on a bill or statement for each configured item, which is why searches on “display_prompt” return this object.

Underlying Base Objects

The view is defined over two documented base objects, referenced through APPS-owned synonyms:

  • AR_BPA_ITEMS_B — the base (non-translated) table holding item-level attributes including flags, data types, level definitions and foreign keys such as DATA_SOURCE_ID and URL_ID.
  • AR_BPA_ITEMS_TL — the translation table holding language-specific text: ITEM_NAME, ITEM_TEXT_VALUE, DISPLAY_PROMPT and ITEM_DESCRIPTION.

The defining predicate B.ITEM_ID = T.ITEM_ID AND T.LANGUAGE = USERENV('LANG') is the standard Oracle translation pattern. Every column from the B table is exposed unchanged; the four descriptive columns are drawn from T. Only rows with a translation matching the session language are returned, so a missing translation yields no row rather than a null-prompted row.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which prompts are defined for bill presentation, reconciling seeded versus customer-defined items, and feeding downstream reporting or integration extracts that must show the label a customer actually sees. The multilingual join makes the view suitable for global implementations where prompts differ by language.

List all enabled items with their prompts for the current language:

SELECT item_id, item_code, item_name, display_prompt, item_type, data_type
FROM   ar_bpa_items_vl
WHERE  display_enabled_flag = 'Y'
ORDER BY display_level, item_code;

Locate a specific prompt string:

SELECT item_id, item_code, display_prompt, item_description
FROM   ar_bpa_items_vl
WHERE  UPPER(display_prompt) LIKE '%INVOICE%';

Reconcile seeded items supplied by Oracle against customer-defined rows:

SELECT seeded_application_id, COUNT(*)
FROM   ar_bpa_items_vl
GROUP BY seeded_application_id;

Because the view filters by USERENV('LANG'), users must set the session language (for example via ALTER SESSION SET NLS_LANGUAGE or an ICX session) to retrieve the desired translation.