Search Results ego_massupdate_item_tmp

Overview

EGO_MASSUPDATE_ITEM_TMP is a transient staging table owned by the EGO schema within the Advanced Product Catalog module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table exists to hold item data during Mass Update flows, the functional path in which a user selects a set of items and applies attribute, category, revision, or supplier changes to them in a single operation. Rather than applying updates directly to the base item tables, the Mass Update process first materializes the candidate item set, the selected records, and the user-entered new values into this temporary structure, where they are validated, displayed, and ultimately processed.

From a Data Vault modeling perspective, the documented metadata classifies this object heuristically as standalone, meaning no foreign key relationships were mined that would place it as a dependent link or satellite. This is consistent with its role as a workflow-scoped staging area rather than a persisted integration or history table. Because it is keyed primarily by a batch identifier and a user identifier, it functions on a per-run, per-session basis, and rows are typically purged or superseded once the Mass Update transaction completes.

Key Information Stored

The table contains 64 documented columns. The most operationally significant are listed below.

• BATCH_ID — groups all rows belonging to a single Mass Update run, allowing multiple concurrent users or batches to coexist in the table without collision.
• USER_ID — the user who initiated the Mass Update flow; scopes the temporary data to the owning session.
• INVENTORY_ITEM_ID — the surrogate identifier of the item being updated, the principal business reference for each staged row.
• ORGANIZATION_ID — the inventory organization context in which the item is being viewed or updated.
• ITEM_NUMBER and DESCRIPTION — the human-readable item identifiers carried into the staging area for display and confirmation.
• ITEM_CATALOG_GROUP_ID — the catalog group context; this is the only documented foreign key, referencing MTL_ITEM_CATALOG_GROUPS_B.
• REVISION_ID, REVISION_CODE, REVISION_LABEL — revision information when mass updates are performed against revised items.
• CATEGORY_ID and CATEGORY_NAME — the category assignment values being applied or displayed.
• SELECTED_FLAG — indicates whether the user has marked a given row for inclusion in the update.
• C_ATTR_1 through C_ATTR_40 — forty reserved columns that hold the DFF or descriptive attribute values staged for mass update.
• STYLE_ITEM_ID — populated where the item participates in a style or SKU structure.
• SUPPLIER_ID, SUPPLIER_NAME, SUPPLIER_SITE, SUPPLIER_SITE_ID — supplier and supplier site context for mass update flows that touch sourcing or approved supplier information.

The ETRM metadata does not document an explicitly named surrogate primary key or a unique index on this table. In practice, uniqueness is implied by the combination of BATCH_ID, USER_ID, and INVENTORY_ITEM_ID or ORGANIZATION_ID. The standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN are present, though their value in a temporary staging object is largely diagnostic.

Common Use Cases and Queries

The primary practical use is troubleshooting and auditing in-flight or failed Mass Update processes. Because rows are short-lived, queries are most useful while a flow is active or when it has aborted without cleanup.

• Identify all rows staged for a specific user or batch:
  SELECT BATCH_ID, INVENTORY_ITEM_ID, ITEM_NUMBER, ORGANIZATION_ID, SELECTED_FLAG FROM EGO.EGO_MASSUPDATE_ITEM_TMP WHERE USER_ID = :user_id;
• Determine which items a user selected versus merely viewed: filter on SELECTED_FLAG = 'Y'.
• Inspect staged descriptive attribute values before commit by examining the relevant C_ATTR_n column alongside ITEM_NUMBER.
• Confirm catalog group context for updates by joining to MTL_ITEM_CATALOG_GROUPS_B on ITEM_CATALOG_GROUP_ID.
• Assess cleanup need by counting rows per BATCH_ID and LAST_UPDATE_DATE to detect orphaned staging data.

Reporting against this table is generally not appropriate for historical analysis, since content is transient. It is, however, a legitimate diagnostic source during implementation, testing, or support of the Mass Update feature.

Related Objects

• MTL_ITEM_CATALOG_GROUPS_B — referenced through EGO_MASSUPDATE_ITEM_TMP.ITEM_CATALOG_GROUP_ID; the only documented foreign key relationship.
• MTL_SYSTEM_ITEMS_B — the master item table whose rows are the ultimate target of the mass update; join on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_ITEM_REVISIONS_B — source of revision context referenced by REVISION_ID and REVISION_CODE.
• MTL_CATEGORIES_B — category definitions corresponding to CATEGORY_ID and CATEGORY_NAME.
• MTL_CATEGORIES_TL — translated category names used for display.
• MTL_ITEM_CATALOG_GROUPS_TL — translated catalog group names for the referenced group.
• EGO_MASSUPDATE_BATCH_TMP or equivalent Mass Update batch tables — companion staging objects holding the batch header and user selection context keyed by BATCH_ID.
• PO_VENDORS / PO_VENDOR_SITES_ALL — supplier and supplier site sources corresponding to SUPPLIER_ID and SUPPLIER_SITE_ID.

Because the object is standalone with a single documented foreign key, most dependencies are logical rather than enforced, and any integration or extension touching Mass Update should treat EGO_MASSUPDATE_ITEM_TMP as an internal, non-persistent working table.