Search Results enabled_code




Overview

EGO_OBJ_ATTR_GRP_ASSOCS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the EGO — Advanced Product Catalog product family. Its documented purpose is to expose the association between attribute groups and objects, providing a denormalized, human-readable representation of the underlying object-to-attribute-group mapping records. In the ETRM metadata for both 12.1.1 and 12.2.2 the object is registered as a VALID VIEW under the APPS schema.

Because the physical association data is stored in a base table (EGO_OBJ_AG_ASSOCS_B) that carries only surrogate identifiers, the view exists to resolve those identifiers into meaningful names. It joins the base association records to object definitions, data level definitions, descriptive flexfield context extensions, and translatable context name/description rows, so that consumers receive display-ready values such as the object name, attribute group display name, and data level name. This makes the view a natural integration and reporting surface for anyone building extracts, BI queries, or interfaces that must interpret attribute group assignments without performing the translation and lookup joins manually.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

Key Columns

  • ASSOCIATION_ID — primary identifier of the object-to-attribute-group association record.
  • OBJECT_ID / OBJECT_NAME — the associated object and its resolved name from FND_OBJECTS.
  • CLASSIFICATION_CODE — classification context carried on the association.
  • ATTR_GROUP_ID — surrogate identifier of the attribute group.
  • APPLICATION_ID, ATTR_GROUP_TYPE, ATTR_GROUP_NAME — the owning application, descriptive flexfield name, and flexfield context code defining the attribute group.
  • ATTR_GROUP_DISP_NAME, ATTR_GROUP_DESCRIPTION — translated display name and description of the attribute group.
  • DATA_LEVEL, DATA_LEVEL_INT_NAME, DATA_LEVEL_ID — the data level at which the association applies, with both display and internal naming.
  • ENABLED_CODE, VARIANT — the enabled flag and variant indicator controlling association applicability.

Common Use Cases and Queries

Typical scenarios include auditing attribute group assignments per object, validating which groups are enabled at a given data level, and feeding downstream catalog or integration processes with resolved group names. A representative query filtering to enabled associations for a specific object follows:

SELECT association_id,
       object_name,
       attr_group_type,
       attr_group_name,
       attr_group_disp_name,
       data_level,
       enabled_code
FROM   apps.ego_obj_attr_grp_assocs_v
WHERE  object_id     = :p_object_id
AND    enabled_code  = 'Y'
ORDER  BY attr_group_disp_name;

Because the view applies the language filter USERENV('LANG'), results are returned in the session's current language, making it suitable for localized reporting. Joins to EGO_DATA_LEVEL_VL allow grouping by data level, and joins to FND_OBJECTS-derived columns support reporting across the object registry. As with any APPS-owned view, queries should be executed from an application responsibility or with appropriate APPS schema access.