Search Results ego_obj_ag_assocs_b_u2

Overview

The table EGO.EGO_OBJ_AG_ASSOCS_B is a core configuration object within the Oracle E-Business Suite (EBS) Enterprise Data Management (EGO) schema. It stores the associations between business objects and attribute groups, thereby defining how descriptive flexfield contexts (attribute groups) are attached to specific objects, classifications, and data levels. This relationship is fundamental to the extensibility framework used across Oracle EBS 12.1.1 and 12.2.2, where customers and integrators attach additional descriptive attributes to standard objects such as items, suppliers, or customers without altering the underlying base entities.

Heuristically, the mined foreign key structure classifies this object as a standalone entity rather than a hub, link, or satellite in a Data Vault sense. This is a modeling suggestion: the table behaves as an association record with its own surrogate key and business keys, but it does not participate in a strict hub-link-satellite topology according to the documented FK/PK relationships. It resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and it is registered under FND Design Data as EGO.EGO_OBJ_AG_ASSOCS_B.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is ASSOCIATION_ID (NUMBER 15), supported by the unique index EGO_OBJ_AG_ASSOCS_B_PK, which uniquely identifies each association record. Two unique indexes serve as business-key candidates. EGO_OBJ_AG_ASSOCS_B_U1 covers ASSOCIATION_ID and ZD_EDITION_NAME, and EGO_OBJ_AG_ASSOCS_B_U2 covers OBJECT_ID, CLASSIFICATION_CODE, ATTR_GROUP_ID, DATA_LEVEL_ID, and ZD_EDITION_NAME — this latter index is the one referenced when users search for "ego_obj_ag_assocs_b_u2."

The most significant business columns include OBJECT_ID (foreign key to FND_OBJECTS), which identifies the object to which an attribute group is bound; CLASSIFICATION_CODE, which narrows the binding to a category or subtype; ATTR_GROUP_ID (foreign key to EGO_FND_DSC_FLX_CTX_EXT), which points to the attribute group definition; and DATA_LEVEL_ID along with DATA_LEVEL, which specify the granularity at which the association applies. The ENABLED_FLAG column indicates whether the association is currently active. The VIEW_PRIVILEGE_ID and EDIT_PRIVILEGE_ID columns reference FND_FORM_FUNCTIONS.FUNCTION_ID to enforce data security. The standard WHO audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide full auditability.

Common Use Cases and Queries

Typical usage involves determining which attribute groups are enabled for a given object and classification, or auditing privilege assignments. A common query retrieves all active associations for an object:

• SELECT association_id, object_id, classification_code, attr_group_id, data_level_id FROM ego_obj_ag_assocs_b WHERE object_id = :p_object_id AND enabled_flag = 'Y';
• Checking privilege coverage: SELECT association_id, view_privilege_id, edit_privilege_id FROM ego_obj_ag_assocs_b WHERE attr_group_id = :p_group;
• Resolving the full binding through the business key: filter on OBJECT_ID, CLASSIFICATION_CODE, ATTR_GROUP_ID, and DATA_LEVEL_ID — the columns indexed by EGO_OBJ_AG_ASSOCS_B_U2.
• Reporting on associations created or modified within a period using CREATION_DATE and LAST_UPDATE_DATE.

These patterns support personalization diagnostics, security reviews, and migration validation between environments.

Related Objects

The most significant dependencies are the tables referenced by its foreign keys and the indexes that enforce its integrity:

• FND_OBJECTS — joined via OBJECT_ID to resolve the associated object definition.
• EGO_FND_DSC_FLX_CTX_EXT — joined via ATTR_GROUP_ID to resolve the attribute group context.
• FND_FORM_FUNCTIONS — joined via VIEW_PRIVILEGE_ID and EDIT_PRIVILEGE_ID to resolve data security privileges.
• EGO_OBJ_AG_ASSOCS_TL — the translation table that typically accompanies a _B base table for multilingual descriptions.
• Indexes EGO_OBJ_AG_ASSOCS_B_PK, EGO_OBJ_AG_ASSOCS_B_U1, and EGO_OBJ_AG_ASSOCS_B_U2 — enforcing uniqueness on the surrogate and business keys.
• EGO attribute-group APIs (for example, routines in the EGO attribute group management package) that create, update, or disable these associations programmatically.