Search Results bom_comp_attr_ctx_assocs_b_s

Overview

APPS.BOM_UDA_OVERRIDES_PVT is a private PL/SQL package body in the Oracle E-Business Suite Bills of Material module. It implements the internal logic for managing User Defined Attribute (UDA) overrides applied to bill of material components. In EBS, User Defined Attributes are extensible flexfield-style attributes registered through the EGO (Product Information Management / extensibility framework) metadata model. When a component on a bill is assigned attribute values that differ from the values inherited from its attribute context, those deviations are persisted as overrides. BOM_UDA_OVERRIDES_PVT provides the encapsulated create, copy, and delete operations that keep these component-level overrides synchronized with the underlying component definition.

The package is classified as a PVT (private) API, meaning it is intended for internal consumption by other BOM and extensibility packages rather than as a public integration interface. The metadata confirms the object is VALID in the APPS schema and that it is not referenced by any database object, which is consistent with a package body whose public specification (BOM_UDA_OVERRIDES_PVT package) exposes the entry points to callers.

Key Procedures and Functions

The documented package exposes two procedures:

• COPY_COMP_UDA_OVERRIDES — Duplicates the set of UDA override records associated with a source bill component to a target component. This supports scenarios such as copying a bill or component structure where the attribute customizations defined at the component level must be carried forward to the new component record.
• DELETE_COMP_UDA_OVERRIDES — Removes the UDA override rows belonging to a specified bill component. This is invoked when component customizations are cleared, when a component is re-created, or during cleanup of obsolete override data.

Both procedures operate on the component-level override data managed by the extensibility framework and are wrapped in the standard FND_API error-handling convention, returning a success or error status through the standard API parameter mechanism. No parameter lists are published, as this is a private package body.

Tables Accessed

The dependency list shows the package reading and writing the following objects:

• BOM_COMPONENTS_EXT_B and BOM_COMPONENTS_EXT_TL — the base and translated tables holding extensible component attribute values. These are the primary targets for persisted overrides.
• BOM_COMP_ATTR_CTX_ASSOCS_B and BOM_COMP_ATTR_CTX_ASSOCS_B_S — the association and sequence tables linking components to their attribute contexts, used to determine which attributes and context apply to a given component.
• EGO_ATTR_GROUP_METADATA_OBJ, EGO_ATTR_METADATA_OBJ, EGO_ATTR_METADATA_TABLE, EGO_DATA_LEVEL_B, EGO_EXTFWK_S — extensibility framework metadata and sequence objects that define attribute groups, attribute definitions, data levels, and surrogate key generation.
• EGO_USER_ATTRS_COMMON_PVT — the shared private API used to manipulate user attribute values, providing the low-level read/write logic the override procedures delegate to.
• FND_API and FND_GLOBAL — standard EBS API utilities and session context (user, responsibility, login) used for error handling and auditing.
• DUAL and PLITBLM — utility references for singleton queries and PL/SQL table handling.

Usage Notes

Because BOM_UDA_OVERRIDES_PVT is a private package body, it is not called directly by external integrations. It is invoked indirectly through the public BOM_UDA_OVERRIDES_PVT specification and by other BOM or extensibility packages that need to propagate or remove component-level UDA customizations. Typical invocation points include the Bills of Material forms and related concurrent programs when a bill or component is copied, updated, or deleted, and when the attribute context association for a component changes. Custom code should not call the private body directly; developers requiring override maintenance logic should use the public specification or the documented EGO_USER_ATTRS_COMMON_PVT interface. The metadata records that the package is referenced by one other package, confirming its role as a supporting internal dependency rather than a standalone entry point.