Search Results mtl_system_items_intf_sets_s




Overview
Explore in AI Chat

Overview

APPS.EGO_MASS_UPDATE_PVT is a private (PVT) PL/SQL package body in the Oracle E-Business Suite Applications schema that provides the back-end engine for the Mass Update of items functionality within Oracle Product Information Management (PIM). In EBS 12.1.1 and 12.2.2, the EGO product family (Enterprise Governance, Ownership, and item master) is responsible for item definition, item attributes, and organization assignment. The private package is the implementation layer beneath the public mass update APIs and user interfaces, encapsulating the heavy lifting of validating, staging, and applying bulk attribute changes to items across one or more inventory organizations. Because it is a PVT package, its procedures are not part of the supported public API surface; they are intended to be called by sibling EGO public package wrappers, concurrent programs, or the mass update UI flow rather than by customer code directly. The package status is documented as VALID and it is not referenced by any other database object, confirming its role as a terminal implementation unit invoked from external entry points rather than a shared dependency for downstream code.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within the package body. Parameter lists are not published and must not be assumed; the descriptions below cover purpose only.

  • ITEM_ORG_ASSIGNMENT — Performs the assignment of items to inventory organizations as part of the mass update operation. It drives the organization-level processing, drawing on the temporary organization table and the item master and interface tables to associate items with the target organizations selected for the mass update run.
  • WRITE_DEBUG — Emits diagnostic or debug output during mass update processing. It relies on the FND_FILE utility to write messages to the concurrent program log and output files, and on FND_PROFILE to determine whether debug output is enabled for the current session.
  • CLEAR_TEMP_TABLES — Cleans up the temporary staging tables used by the mass update process. It removes residual rows from the item and organization temporary tables so that subsequent mass update runs begin from a clean state and do not process stale data.

Tables Accessed

The package reads and writes several documented tables via APPS synonyms.

  • EGO_MASSUPDATE_ITEM_TMP — Temporary staging table holding the set of items targeted by the mass update. Written during setup and cleared by CLEAR_TEMP_TABLES.
  • EGO_MASSUPDATE_ORG_TMP — Temporary staging table holding the target organizations for the organization assignment step, consumed by ITEM_ORG_ASSIGNMENT.
  • MTL_SYSTEM_ITEMS_B — The item master base table; read and updated as the persistent target of mass attribute changes.
  • MTL_SYSTEM_ITEMS_INTERFACE — The open interface table for item import, used when mass update changes are propagated through the item interface rather than applied directly.
  • MTL_SYSTEM_ITEMS_INTF_SETS_S — The interface set sequence used to generate unique set identifiers for interface records, explaining why this object is a documented dependency.
  • MTL_PARAMETERS — Organization parameters, read to resolve organization-specific defaults and validation rules.
  • DUAL — Used for scalar evaluations and sequence-style lookups.

Utility dependencies include FND_API, FND_FILE, FND_GLOBAL, FND_PROFILE, FND_REQUEST, ERROR_HANDLER, and STANDARD.

Usage Notes

EGO_MASS_UPDATE_PVT is invoked indirectly. Typical entry points are the Mass Update concurrent programs and the item mass update UI flow in PIM, which call the public EGO mass update APIs; those APIs in turn delegate to the private procedures documented here. It may also be called from custom PL/SQL only at the risk of relying on an unsupported private interface. Because the package manages its own temporary tables, callers must not assume the temp tables are empty before invoking it; CLEAR_TEMP_TABLES is the supported mechanism for resetting state. Debug tracing is controlled through FND_PROFILE settings and surfaced through FND_FILE logs, which is the primary means of diagnosing mass update failures in both 12.1.1 and 12.2.2.