Results for “ar_bpa_template_fields”

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

Overview

AR_BPA_TEMPLATE_FIELDS is an Oracle Receivables (AR) base table that supports the Bill Presentment Architecture (BPA) framework. First delivered in Release 11i and retained through Oracle EBS 12.1.1 and 12.2.2, it stores the individual field-level definitions that make up a Bill Presentment template. Where AR_BPA_TEMPLATES_B holds the header or template-level record, AR_BPA_TEMPLATE_FIELDS describes each distinct data element associated with that template, including its logical field name and any related item identifier used for rendering or display.

From a dimensional modeling perspective, the metadata structure is classified heuristically as satellite-leaning. This is a modeling suggestion rather than a declarative fact: the table's grain (one row per template field) and its single foreign key relationship to a parent hub-like table (AR_BPA_TEMPLATES_B) are consistent with a satellite attached to a parent entity, but they may also resemble a link depending on business context. The table is owned by the AR schema and is marked VALID.

Key Information Stored

Nine documented physical columns define this object. The most significant are the surrogate identifier, the parent reference, and the business attributes that give the record meaning:

• TEMPLATE_FIELD_ID — the surrogate primary key, enforced by the unique index AR_BPA_TEMPLATE_FIELDS_U1 and the AR_BPA_TEMPLATE_FIELDS_PK constraint. It uniquely identifies each template field row.
• TEMPLATE_ID — foreign key referencing AR_BPA_TEMPLATES_B, tying every field to its owning template. This is the principal join column.
• FIELD_NAME — the logical name of the field as presented within the template.
• ITEM_ID — identifier of the related item (for example, a BPA item or data element) associated with the field.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created and last modified the row and when.

The unique index on TEMPLATE_FIELD_ID acts as the business-key candidate for the surrogate. No additional composite unique index is documented, so FIELD_NAME and ITEM_ID operate as descriptive attributes rather than guaranteed keys.

Common Use Cases and Queries

Typical usage centers on inspecting, rendering, or migrating BPA template configurations. Common scenarios include:

• Listing all fields for a given template:

SELECT TEMPLATE_FIELD_ID, FIELD_NAME, ITEM_ID
FROM   AR.AR_BPA_TEMPLATE_FIELDS
WHERE  TEMPLATE_ID = :template_id;

• Joining fields to their template header to report configuration:

SELECT t.TEMPLATE_ID, t.NAME, f.FIELD_NAME, f.ITEM_ID
FROM   AR.AR_BPA_TEMPLATE_FIELDS f,
       AR.AR_BPA_TEMPLATES_B t
WHERE  f.TEMPLATE_ID = t.TEMPLATE_ID
ORDER  BY t.TEMPLATE_ID, f.TEMPLATE_FIELD_ID;

• Auditing recent changes to template field definitions using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Data migration/diagnostics: comparing field counts per template to detect incomplete template setups.

Related Objects

The FK relationship documented in the metadata identifies the primary dependency:

• AR_BPA_TEMPLATES_B — parent table joined via AR_BPA_TEMPLATE_FIELDS.TEMPLATE_ID = AR_BPA_TEMPLATES_B.TEMPLATE_ID. This is the key reference for nearly all queries.
• AR_BPA_TEMPLATES_TL — the translated/descriptive table for templates, frequently joined for displayable template names.
• AR_BPA_TEMPLATE_FIELDS_PK / AR_BPA_TEMPLATE_FIELDS_U1 — the primary key constraint and unique index on TEMPLATE_FIELD_ID.
• Other BPA configuration tables (e.g., BPA item and display metadata objects in the AR BPA family) may reference FIELD_NAME/ITEM_ID values at the application layer, though they are not represented by a direct FK in this metadata.

Because BPA is a presentation-layer feature, most runtime consumption of this table occurs through the Bill Presentment Architecture templates rather than direct DML. Direct updates are uncommon and, when required, should respect the audit columns and the parent template relationship.