Results for “ar_bpa_template_fields_u1”

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

Overview

The AR_BPA_TEMPLATE_FIELDS table, owned by the AR (Receivables) schema, is a transactional data object used by the Bill Presentment Architecture (BPA) module in Oracle E-Business Suite. Bill Presentment Architecture enables organizations to design custom bill and invoice presentation templates, uploading external layout files that define which fields appear on a rendered bill and how those fields map to underlying transaction data. AR_BPA_TEMPLATE_FIELDS stores the individual field definitions extracted from these uploaded template files, making it the fine-grained metadata repository that describes the composition of each BPA template. The object has been in use since Release 11i and remains VALID in the 12.1.1 and 12.2.2 codelines, with FND Design Data registered as AR.AR_BPA_TEMPLATE_FIELDS.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. It carries descriptive attributes (such as FIELD_NAME and ITEM_ID) attached to a parent business entity, AR_BPA_TEMPLATES_B, rather than acting as an independent hub or a many-to-many link. The table’s primary access path is the parent template, which is consistent with a satellite hanging off a template hub.

Key Information Stored

The table contains nine documented columns, of which the most significant are:

• TEMPLATE_FIELD_ID – The surrogate primary key, a NUMBER(15) that uniquely identifies each field row. It is enforced by the unique index AR_BPA_TEMPLATE_FIELDS_U1 in the APPS_TS_TX_IDX tablespace.
• TEMPLATE_ID – A NUMBER(15) foreign key to AR_BPA_TEMPLATES_B, identifying the parent template to which the field definition belongs. It is the business-key candidate for grouping fields by template and is supported by the non-unique index AR_BPA_TEMPLATE_FIELDS_N1.
• FIELD_NAME – A VARCHAR2(255) holding the field name extracted from the uploaded template file. This is the descriptive label that ties a presentation element back to its source layout.
• ITEM_ID – A NUMBER(15) identifying the item with which the field is associated, allowing fields to be scoped to specific bill lines or items.
• Standard Who columns – LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide full audit tracking of who created and last modified each field definition.

The distinction between the surrogate key (TEMPLATE_FIELD_ID) and the business-key candidate (TEMPLATE_ID, from the unique index) is important: TEMPLATE_FIELD_ID guarantees row identity, while TEMPLATE_ID provides the natural grouping context for each template. Data resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

Common Use Cases and Queries

Typical use cases include auditing which fields are defined for a given bill template, diagnosing rendering issues where an expected field is missing from a printed bill, and migrating or comparing template definitions across environments. A standard query pattern joins the table to its parent template:

• List fields for a template: SELECT template_field_id, field_name, item_id FROM ar.ar_bpa_template_fields WHERE template_id = :template_id ORDER BY field_name;
• Locate a field by name: SELECT template_id, template_field_id FROM ar.ar_bpa_template_fields WHERE field_name = :field_name;
• Audit changes: SELECT field_name, last_updated_by, last_update_date FROM ar.ar_bpa_template_fields WHERE template_id = :template_id ORDER BY last_update_date DESC;

Related Objects

The most significant related objects are:

• AR.AR_BPA_TEMPLATES_B – The parent template table; joined on TEMPLATE_ID = AR_BPA_TEMPLATE_FIELDS.TEMPLATE_ID. This is the only documented foreign-key relationship.
• APPS.AR_BPA_TEMPLATE_FIELDS – The APPS synonym exposing the table to application code and concurrent programs.
• AR_BPA_TEMPLATE_FIELDS_U1 – Unique index on TEMPLATE_FIELD_ID, serving as the primary-key access path.
• AR_BPA_TEMPLATE_FIELDS_N1 – Non-unique index on TEMPLATE_ID supporting parent-child lookups.
• Bill Presentment Architecture concurrent programs and APIs – The BPA template upload and generation routines that populate and consume these field definitions.

No other database objects are documented as referencing AR_BPA_TEMPLATE_FIELDS, confirming its role as a dependent child within the BPA template model.