Search Results sys_c00243571

Overview

The PO.PO_UDA_AG_TEMPLATES table stores the definitions of Attribute Templates used by Oracle Purchasing. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, attribute templates provide a reusable container of user-defined attribute (UDA) group definitions and their associated context. Each row in this table describes a template that governs how one or more attribute groups are applied to a specific document level, document type, and document style within a functional area. The table therefore acts as the master catalog of templates from which the actual attribute group assignments are derived.

From a data modeling perspective, the documented heuristic Data Vault classification places this object as a standalone entity rather than a conventional link table. The absence of documented foreign key relationships to a parent hub means the table can be treated as its own source of truth for template identity, with a natural business key anchored on TEMPLATE_ID and the edition discriminator ZD_EDITION_NAME.

Key Information Stored

The primary key constraint SYS_C00243571 enforces uniqueness on TEMPLATE_ID, the surrogate identifier for each attribute template. The unique index PO_UDA_AG_TEMPLATES_U1 covers TEMPLATE_ID and ZD_EDITION_NAME, making this pair the business-key candidate that supports edition-aware lookups in 12.2.2 online patching environments.

• TEMPLATE_ID – Surrogate primary key uniquely identifying each attribute template.
• ENTITY_CODE – Identifies the business entity to which the template applies, driving which UDA framework processes the template.
• FUNCTIONAL_AREA – The Purchasing functional area, such as purchasing or sourcing, that owns the template.
• DOCUMENT_LEVEL – The level at which attributes are captured, for example header or line.
• DOCUMENT_TYPE – The document type, such as a purchase order or agreement, that the template targets.
• DOCUMENT_STYLE_ID – Reference to the document style that further qualifies template applicability.
• REVISION – Revision number supporting versioned template definitions.
• DATABASE_VIEW_NAME – The underlying view or object against which template attribute values are resolved.
• COMPILED_FLAG – Indicates whether the template definition has been compiled and is ready for runtime use.
• SRC_TEMPLATE_ID – Source template from which the current record was copied or derived.
• EFFECTIVE_FROM / EFFECTIVE_TO – Date range over which the template definition is active.
• Standard audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY capture who created and last modified the row and when.
• ZD_EDITION_NAME – Edition identifier used by the 12.2.2 online patching architecture to isolate edition-specific data.

Common Use Cases and Queries

Typical uses include auditing which templates are active for a given document type, validating that all required templates have been compiled, and tracing derived templates back to their source. A representative query to list active compiled templates for a document type is:

• SELECT template_id, entity_code, functional_area, document_level, document_type, compiled_flag FROM po.po_uda_ag_templates WHERE document_type = :doc_type AND compiled_flag = 'Y' AND (effective_to IS NULL OR effective_to >= SYSDATE);
• SELECT * FROM po.po_uda_ag_templates WHERE template_id = :template_id;
• SELECT template_id, src_template_id, revision FROM po.po_uda_ag_templates WHERE src_template_id IS NOT NULL CONNECT BY PRIOR template_id = src_template_id START WITH src_template_id IS NULL;

These patterns support configuration review, cleanup of uncompiled templates, and impact analysis before changes are promoted between environments.

Related Objects

Because the metadata classifies this table as standalone, no direct foreign keys are documented. Related objects are therefore identified by functional coupling and shared columns rather than enforced constraints:

• PO_UDA_AG_TEMPLATE_GROUPS – Links templates to the attribute groups they contain, joined on TEMPLATE_ID.
• PO_UDA_AG_DEFINITIONS – Defines the individual attribute groups that templates reference.
• PO_UDA_AG_INSTANCES – Holds runtime attribute values captured using a template.
• PO_DOCUMENT_TYPES_ALL and PO_DOCUMENT_STYLES_ALL – Provide the document type and style referenced by DOCUMENT_TYPE and DOCUMENT_STYLE_ID.
• FND_DOCUMENT_ENTITIES – Supplies the entity context linked through ENTITY_CODE.

Together these objects form the attribute template and user-defined attribute framework within Oracle Purchasing.