Search Results ego_ext_table_metadata_obj




Overview

The APPS.EGO_COM_ATTR_VALIDATION package body is a server-side PL/SQL component within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 codebase, residing in the APPS schema with a status of VALID. It belongs to the Oracle Product Information Management (PIM) / EGO (Engineering and Product Data) module, which supports extensible attributes, attribute groups, and user-defined attribute sets in the Inventory and Product Management domains.

The package's principal business function is the runtime validation and resolution of attribute values against Oracle EBS attribute-group metadata. It ensures that values entered or defaulted for user-defined and flexfield-backed attributes conform to the metadata definitions stored in the EGO attribute framework. It is classified under API classification OTHER, meaning it is a utility/support package rather than a formally published public API. It is referenced by no other database objects, and its dependency chain places it near the core of the attribute validation logic, consuming metadata objects such as EGO_ATTR_GROUP_METADATA_OBJ, EGO_EXT_TABLE_METADATA_OBJ, and user-attribute data objects.

Key Procedures and Functions

Four documented procedures are exposed by this package body:

  • VALIDATE_ATTRIBUTES — The primary entry point for validating one or more attribute values for a given attribute group. It checks entered values against metadata rules and flags non-conformant input.
  • GET_ATTR_VALUE_FROM_DB — Retrieves the currently persisted value of an attribute directly from the underlying EGO user-attribute data tables. This supports default resolution and comparison scenarios.
  • IS_ATTRIBUTE_GROUP_TELCO — Determines whether a specified attribute group corresponds to the Telecommunications (TELCO) context. This conditional check drives telecom-specific validation or default behavior.
  • VALIDATE_DEFAULT_COMPATTR — Validates default values applied to common attributes, ensuring that supplied defaults are compatible with the attribute group metadata before they are accepted.

No parameter signatures are documented in the reference metadata, and none should be assumed.

Tables Accessed

Two database objects are documented as tables referenced through APPS synonyms:

  • EGO_FND_DSC_FLX_CTX_EXT — An extension table linked to FND descriptive flexfield context metadata (FND_DESCR_FLEX_CONTEXTS_VL is also in the dependency list). It supplies the context and segment information needed to resolve flexfield-backed attribute values.
  • PLITBLM — A standard Oracle PL/SQL table-of-array type used for passing arrays of values between procedures within the package, particularly relevant to the EGO_COL_NAME_VALUE_PAIR_ARRAY structures in the dependency list.

The package also depends on EGO_COL_NAME_VALUE_PAIR_ARRAY, EGO_COL_NAME_VALUE_PAIR_OBJ, EGO_USER_ATTR_DATA_OBJ, EGO_USER_ATTRS_COMMON_PVT, EGO_USER_ATTRS_DATA_PVT, and EGO_USER_ATTR_DATA_TABLE, indicating it relies on the private EGO user-attribute APIs to read and write attribute instance data.

Usage Notes

Because it is referenced by no other database object and is classified OTHER, EGO_COM_ATTR_VALIDATION is not a formally published API. It is invoked internally by EGO user-attribute processing logic—most likely through the EGO_USER_ATTRS_COMMON_PVT and EGO_USER_ATTRS_DATA_PVT private packages—during attribute value submission from the EGO/PIM user interfaces, including attribute-group setup and item attribute entry forms.

The IS_ATTRIBUTE_GROUP_TELCO procedure indicates that telecom industry attribute sets receive targeted handling, and the VALIDATE_DEFAULT_COMPATTR procedure supports default-value propagation for common attributes. Customizations should avoid direct calls to this package where a documented public API exists, but reading its behavior is useful when diagnosing validation or default errors on extensible attributes in EBS 12.1.1 and 12.2.2. Always confirm the package status is VALID after patching, since upstream metadata changes to EGO_ATTR_GROUP_METADATA_OBJ can affect compilation.