Search Results insert_template_attribute

Overview

The APPS.EGO_TEMPL_ATTRS_PUB package body is a public PL/SQL API that supports the Oracle E-Business Suite attribute-template framework used primarily within Oracle Product Information Management (PIM) and the Item Master. Its principal business function is to manage the association between attribute groups and templates, and to synchronize template attributes so that descriptive flexfield and attribute-group definitions remain consistent with the item template structures stored in the EGO schema. In practice, this package allows forms, concurrent programs, and custom extensions to create, update, and synchronize the attributes that describe an item template without directly manipulating the underlying base tables. The package is classified as a public (PUB) API, indicating it is intended for external invocation. The source header denotes release R12C and a maintenance stamp of 2007, consistent with the code lineage carried forward into EBS 12.1.1 and 12.2.2. The package declares global variables for the current user and login identifiers (via FND_GLOBAL) and error-reporting constants, and it exposes a private helper (Get_Data_Level_ID) that resolves the data level for attribute groups. A well-known constraint encoded in that helper is that items originating from MTL_SYSTEM_ITEMS always use a data level of ITEM_ORG and an attribute group type of EGO_MASTER_ITEMS.

Key Procedures and Functions

ETRM documents four public procedures within this package body. Parameter lists are intentionally omitted here; the descriptions reflect documented purpose only.

• SYNC_TEMPLATE — Synchronizes a template definition as a whole, reconciling the template header and its associated attributes with the current attribute-group and data-level configuration.
• SYNC_TEMPLATE_ATTRIBUTE — Synchronizes an individual template attribute, ensuring that the attribute's metadata and flexfield usage align with the template and attribute-group definitions.
• INSERT_TEMPLATE_ATTRIBUTE — Inserts a new template attribute record into the template attribute structure, establishing the link between a template and a specific attribute. This is the entry point most commonly sought when users search for "insert_template_attribute".
• UPDATE_TEMPLATE_ATTRIBUTE — Modifies an existing template attribute, allowing properties or usages of an already-defined attribute to be revised.

Together these procedures form a create/update/synchronize lifecycle for template attributes, with the sync routines providing reconciliation logic and the insert/update routines providing direct maintenance.

Tables Accessed

The package reads and writes the following tables through APPS synonyms, as documented in ETRM 12.2.2:

• EGO_TEMPL_ATTRIBUTES — The primary table holding template attribute records; the insert, update, and sync procedures operate on this table.
• EGO_OBJ_AG_ASSOCS_B — Stores object-to-attribute-group associations used to determine which attribute groups apply to a given object or template.
• EGO_DATA_LEVEL_B — Holds data-level definitions; the private helper Get_Data_Level_ID queries it to resolve data-level identifiers for attribute groups.
• EGO_FND_DF_COL_USGS_EXT and FND_DESCR_FLEX_COLUMN_USAGES — Descriptive flexfield column-usage definitions that govern how flexfield segments are surfaced as attributes.
• EGO_FND_DSC_FLX_CTX_EXT — Extended descriptive flexfield context information supporting attribute-group configuration.
• MTL_ITEM_TEMPL_ATTRIBUTES — The item-template attribute link table, aligned when items originate from MTL_SYSTEM_ITEMS.
• DUAL — Used for simple single-row evaluations, such as global initialization.

Usage Notes

This package is typically invoked from the Oracle PIM/Item Master template setup forms, from concurrent programs that build or refresh item templates, and from custom PL/SQL extensions that must programmatically add or adjust template attributes. Because the routines are public, custom code should call them rather than performing direct DML against EGO_TEMPL_ATTRIBUTES, thereby preserving the validation, flexfield-usage, and synchronization logic embedded in the package. The package is referenced by one other package within APPS, indicating layered dependencies in the EGO attribute-template stack. Error handling uses the FND message stack (with the G_ADD_ERRORS_TO_FND_STACK constant set to 'Y'), so callers should inspect the message stack after invocation and honor the standard EBS API return conventions. Note that the ITEM_ORG / EGO_MASTER_ITEMS defaults should not be overridden for MTL_SYSTEM_ITEMS-sourced items.