Search Results ego_attr_grps_assoc_interface

Overview

The EGO_ATTR_GRPS_ASSOC_INTERFACE table is a staging and open-interface table within the Oracle E-Business Suite Advanced Product Catalog (EGO) module. Its documented purpose is to associate an Attribute Group with an ICC — an Item Catalog Category — thereby defining which attribute groups apply to a given catalog category node. Because attribute groups govern the descriptive and extensible attributes available to items classified under a category, this association is fundamental to how attribute inheritance and validation behave across the product catalog.

As the "INTERFACE" suffix indicates, the table is not the final destination for this relationship. It is a transient staging area populated by external processes or bulk load routines, then consumed by concurrent programs that validate the rows and migrate valid associations into the permanent catalog metadata tables. Records progress through a processing lifecycle evidenced by status, transaction, and request columns. The heuristic Data Vault classification mined from its foreign key structure is standalone; in Data Vault modeling terms, this table functions most naturally as a link-style staging structure referencing the MTL_ITEM_CATALOG_GROUPS_B hub, with the processing audit columns acting as satellite-style descriptive attributes attached at load time.

Key Information Stored

The table contains twenty documented columns. The most significant are:

• ASSOCIATION_ID — the surrogate primary key uniquely identifying each interface row.
• ITEM_CATALOG_GROUP_ID — foreign key to MTL_ITEM_CATALOG_GROUPS_B; identifies the catalog category group receiving the association.
• ITEM_CATALOG_NAME — business-friendly name of the target catalog, useful as a business-key candidate during validation and troubleshooting.
• ATTR_GROUP_ID — identifier of the attribute group being associated; the core payload of the transaction.
• ATTR_GROUP_NAME — descriptive name of the attribute group, serving as a secondary business-key candidate.
• DATA_LEVEL and DATA_LEVEL_ID — indicate the hierarchical level and identifier at which the association applies within the catalog structure.
• SET_PROCESS_ID, TRANSACTION_ID, and TRANSACTION_TYPE — control columns linking related rows into a single import operation and defining the operation's nature.
• PROCESS_STATUS — the critical lifecycle flag (typically pending, processed, or error) that drives the import concurrent program.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — standard concurrent manager audit columns identifying the submission that processed the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking insert and update activity.

The composite of (ITEM_CATALOG_GROUP_ID, ATTR_GROUP_ID) is the natural business key that the import process uses to detect duplicates against existing associations.

Common Use Cases and Queries

Typical usage centers on bulk loading catalog attribute group configurations from external systems, migrating configurations between instances, and monitoring interface failures. A common diagnostic query isolates failed rows before resubmitting the import program:

• Selecting all rows where PROCESS_STATUS indicates an error, ordered by REQUEST_ID, to trace failures back to a specific concurrent request.
• Joining to MTL_ITEM_CATALOG_GROUPS_B on ITEM_CATALOG_GROUP_ID to confirm that each staged association points to a valid, active catalog category before processing.
• Grouping by SET_PROCESS_ID or TRANSACTION_ID to measure success and failure counts per import batch.
• Reconciling source-system extracts against staged rows using ITEM_CATALOG_NAME and ATTR_GROUP_NAME to detect orphaned or misspelled attribute group references.

Reporting teams also use the table to audit which attribute groups were introduced into the catalog and when, leveraging CREATION_DATE and PROGRAM_UPDATE_DATE for change-history analysis. Because rows are transient, most organizations purge or archive processed records periodically.

Related Objects

The most significant dependencies are:

• MTL_ITEM_CATALOG_GROUPS_B — the sole documented foreign key target, joined on ITEM_CATALOG_GROUP_ID. This table defines the catalog category hierarchy.
• MTL_ITEM_CATALOG_GROUPS_TL — provides translated catalog names for validation and reporting joins.
• EGO_ATTR_GROUPS_B and EGO_ATTR_GROUPS_TL — hold the attribute group definitions referenced by ATTR_GROUP_ID and ATTR_GROUP_NAME.
• EGO_ATTR_GRPS_ASSOC (the permanent association table) — the validated destination into which interface rows are promoted.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace processing submissions and their outcomes.
• FND_APPLICATION and FND_PROGRAM — resolve PROGRAM_APPLICATION_ID and PROGRAM_ID to the concurrent program that executed the import.

These relationships make the table a bounded, well-defined staging point within the Advanced Product Catalog's attribute management flow.