Search Results print_font_size




Overview
Explore in AI Chat

Overview

AR_BPA_PAGE_SETUPS_B is a Receivables (AR) base table in Oracle E-Business Suite, owned by the AR schema. It was introduced with Release 11i and is used by the Bill Presentment Architecture (BPA) feature. The table stores the physical page-layout definitions that govern how bill and invoice documents are presented when rendered through BPA. In this role it functions as a master definition table consumed by the page-rendering and template-assembly components of the Bill Presentment Architecture.

The ETRM metadata classifies this object heuristically as hub-leaning in a Data Vault model. In practice this means AR_BPA_PAGE_SETUPS_B behaves like a durable hub of page-setup entities: it holds one row per page-setup record, keyed by a stable surrogate identifier, with descriptive attributes (dimensions, margins, fonts) attached to it. The translations and templates that depend on it act as the surrounding satellite and link structures, referencing the hub by its primary key.

Key Information Stored

The table is documented with 18 physical columns. The surrogate primary key is PAGE_SETUP_ID, enforced through the constraint AR_BPA_PAGE_SETUPS_B_PK. A second unique index, AR_BPA_PAGE_SETUPS_B_U1, is defined on the pair (PAGE_SETUP_ID, ZD_EDITION_NAME), which serves as a business-key candidate and supports the editioning mechanism used in later 12.2.x releases.

The most significant columns fall into three groups:

The description field associated with each page setup is not held here; it resides in the translation table AR_BPA_PAGE_SETUPS_TL, which is joined by PAGE_SETUP_ID.

Common Use Cases and Queries

Typical usage centers on reporting and validating BPA page configurations, identifying seeded versus custom setups, and tracing which templates consume a given page setup. A representative query against the base table is:

  • SELECT page_setup_id, page_width, page_height, page_unit_of_measure, seeded_flag FROM ar.ar_bpa_page_setups_b; — to list all configured page setups and their dimensions.
  • A join to the translation table retrieves the human-readable name: SELECT b.page_setup_id, t.description FROM ar.ar_bpa_page_setups_b b, ar.ar_bpa_page_setups_tl t WHERE b.page_setup_id = t.page_setup_id;
  • To find templates that depend on a page setup: SELECT t.template_id, t.page_setup_id FROM ar.ar_bpa_templates_b t WHERE t.page_setup_id = :page_setup_id;
  • To isolate custom (non-seeded) configurations for migration or review: filter on seeded_flag = 'N'.

These patterns support setup audits, BPA configuration reports, and migration validation between environments such as 12.1.1 and 12.2.2.

Related Objects

The documented foreign-key relationships identify the following dependent objects:

  • AR_BPA_PAGE_SETUPS_TL — the translation table, joined via AR_BPA_PAGE_SETUPS_TL.PAGE_SETUP_ID = AR_BPA_PAGE_SETUPS_B.PAGE_SETUP_ID, holding language-specific descriptions.
  • AR_BPA_TEMPLATES_B — the bill template base table, joined via AR_BPA_TEMPLATES_B.PAGE_SETUP_ID = AR_BPA_PAGE_SETUPS_B.PAGE_SETUP_ID, which associates a template with its page-layout definition.

Together these constitute the core BPA page-setup cluster. Because PAGE_SETUP_ID is a hub key, any additional BPA tables referencing page setups by that identifier should be treated as dependents of this table.