Search Results ego_orchestration_util_pub




Overview
Explore in AI Chat

Overview

EGO_ORCHESTRATION_UTIL_PUB is a public PL/SQL package in the APPS schema that forms part of the Oracle E-Business Suite Product Information Management (PIM) orchestration layer. It provides utility APIs used to stage, import, and process item and bundle data that flows through the EGO (Oracle Product Hub / Product Information Management) orchestration engine.

The package exposes procedures and functions for managing bundle collections, retrieving supplier information, processing translated (TL) rows, and saving incoming XML payloads. It is classified as a PUB API, meaning it is intended for supported external invocation by other Oracle modules and by customer extensions. The source header identifies the package as obsolete at the script level in later patch streams, yet the public interfaces remain documented and are still referenced by orchestration batch flows.

Key Procedures and Functions

  • PRE_PRE_PROCESS_BATCHES — A function that performs preparatory processing on a bundle collection prior to the main batch run, accepting a bundle collection identifier and a commit flag, returning a numeric status.
  • GET_SUPPLIER_INFO — Resolves an external supplier identifier, type, and level into the internal supplier ID and supplier name.
  • ADD_BUNDLES_TO_COL — Adds a set of bundles, supplied as a CLOB, into a bundle collection and returns the new collection identifier. Supports an entity name and an optional commit.
  • GET_BUNDLES_FROM_COL — Returns bundles from a collection as an XMLTYPE, paged by prior bundle ID and maximum element count.
  • SAVE_DATA — The central persistence routine. Accepts an XML CLOB payload plus commit flag, source system ID, default batch name, and returns new and error bundle collection identifiers. This is the procedure most commonly associated with the "save_data" search.
  • PROCESS_TL_ROWS — Processes translated rows for a given table, batch, unique ID, bundle, XML data, entity name, and column name, supporting multi-language attribute loading.
  • Set_ICC_For_Rec_Bundle / Set_ACC_For_Rec_Bundle — Set item catalog category (ICC) and attribute catalog category (ACC) assignments for a record bundle, returning status and a GPC list.
  • Set_ICC_For_Rec_Collection — Applies ICC assignments at the record collection level.

Tables Accessed

The supplied ETRM metadata does not enumerate the underlying tables accessed through APPS synonyms, and no tables are listed as documented references. In practice, orchestration utility routines of this type operate against the EGO bundle collection and bundle staging structures (for example, the EGO bundle collection and bundle tables) and the translated-attribute tables implied by PROCESS_TL_ROWS. Because the metadata lists the table inventory as empty, the exact physical table set should be confirmed by inspecting the package body in the target instance rather than assumed.

Usage Notes

EGO_ORCHESTRATION_UTIL_PUB is normally invoked indirectly. Product Hub batch import concurrent programs, the orchestration engine, and item import flows call SAVE_DATA and ADD_BUNDLES_TO_COL to stage and persist XML payloads, while PROCESS_TL_ROWS handles translated content. Direct calls are typically restricted to custom integrations that must feed bundles or supplier data into orchestration, or to diagnostic scripts that exercise PRE_PRE_PROCESS_BATCHES and the Set_ICC/Set_ACC routines.

Callers should honor the returned status codes, which follow the standard FND_API convention (S for success, E for error, U for unexpected error), and should pass the commit flag deliberately to control transaction boundaries. Because the script header marks the package obsolete, any custom usage should be validated against the specific 12.1.1 or 12.2.2 instance, and Oracle-supported alternatives should be considered wherever they exist.