Search Results page_setup_name




Overview

AR_BPA_PAGE_SETUPS_TL is a translation (TL) table in the Oracle Receivables (AR) schema, owned by AR and validated in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores the language-specific, translatable attributes of Bill Presentment Architecture (BPA) page setups. BPA is the Release 11i-and-later framework that lets organizations define formatted, branded layouts for presenting bills and invoices to customers through self-service interfaces, and this table supplies the human-readable names and descriptions that appear for each page setup in each installed language.

The table is a child of AR_BPA_PAGE_SETUPS_B, the base (non-translated) table that holds language-independent page setup attributes. Every row in AR_BPA_PAGE_SETUPS_TL is anchored to a row in the base table through PAGE_SETUP_ID. Consistent with the ETRM metadata's heuristic Data Vault classification of "satellite-leaning," this object is best modeled as a satellite describing descriptive, language-dependent context around the base entity, rather than as an independent hub or a link between entities. The true business entity is the page setup in AR_BPA_PAGE_SETUPS_B; this table simply enriches it per language.

Key Information Stored

The documented physical schema contains 11 columns. The important ones are:

  • PAGE_SETUP_ID — Surrogate/foreign key to the parent base table AR_BPA_PAGE_SETUPS_B. It identifies which page setup the translated row belongs to.
  • LANGUAGE — The language code for the translated content. Together with PAGE_SETUP_ID it forms the primary key AR_BPA_PAGE_SETUPS_TL_PK.
  • PAGE_SETUP_NAME — The display name of the page setup in the given language.
  • PAGE_SETUP_DESC — The descriptive text for the page setup in the given language.
  • SOURCE_LANG — The language in which the row was originally authored, used by the translation framework to determine whether a row still reflects the source language.
  • ZD_EDITION_NAME — The editioning column that supports Online Patching in EBS 12.2.2, allowing different editions of the same logical row to coexist during an adop cycle.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each translated row.

The unique index AR_BPA_PAGE_SETUPS_TL_U1 on (PAGE_SETUP_ID, LANGUAGE, ZD_EDITION_NAME) enforces one translated row per page setup, per language, per edition, and is the strongest business-key candidate. The primary key AR_BPA_PAGE_SETUPS_TL_PK on (PAGE_SETUP_ID, LANGUAGE) defines the physical row identity.

Common Use Cases and Queries

Typical uses include retrieving localized page setup names for a BPA template configuration screen, auditing which language translations exist for each page setup, and reporting on translation coverage before a rollout. A common join pattern combines the translated table with its base table:

  • SELECT b.page_setup_id, t.page_setup_name, t.page_setup_desc, t.language FROM ar_bpa_page_setups_b b, ar_bpa_page_setups_tl t WHERE b.page_setup_id = t.page_setup_id AND t.language = USERENV('LANG');
  • To find page setups lacking a translation for a target language, outer-join the base table to the translated table and filter where t.page_setup_id IS NULL.
  • Reporting queries frequently constrain ZD_EDITION_NAME to the current edition when running in a 12.2.2 online-patching environment.

Because this is a translation table, direct DML is discouraged; changes should flow through the BPA setup APIs and the standard translation utilities.

Related Objects

  • AR_BPA_PAGE_SETUPS_B — Parent base table; join on PAGE_SETUP_ID. It holds the language-independent page setup definition.
  • AR_BPA_PAGE_SETUPS_TL_PK — Primary key constraint on (PAGE_SETUP_ID, LANGUAGE).
  • AR_BPA_PAGE_SETUPS_TL_U1 — Unique index on (PAGE_SETUP_ID, LANGUAGE, ZD_EDITION_NAME), the business-key candidate.
  • AR_BPA_PAGE_SETUPS_TL — Self-referencing rows across languages, enabling per-language comparison.
  • BPA configuration and template setup pages — UI and concurrent programs that read PAGE_SETUP_NAME and PAGE_SETUP_DESC for display and selection.

Together these objects form the page setup layer of Bill Presentment Architecture, with this translation table providing the localized presentation metadata.