Search Results ego_import_batches_pkg




Overview
Explore in AI Chat

Overview

EGO_IMPORT_BATCHES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that manages the lifecycle of product data import batches within the Product Information Management (PIM) and Product Data Hub (PDH) modules. It is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer, an important consideration for any custom code that invokes it. The package encapsulates the core create, read, update, and delete operations against the EGO_IMPORT_BATCHES_B and EGO_IMPORT_BATCHES_TL tables, together with higher-level business logic used to construct fully-configured import batches from PIM Data Hub source systems. Applications use it to stage and control the ingestion of item, structure, and revision data supplied from external source systems into the EBS item master.

Key Procedures and Functions

  • INSERT_ROW — Inserts a new import batch record, accepting the batch identifier, organization, source system, batch type, assignee, status, object version number, name, description, and the standard Who columns.
  • LOCK_ROW — Performs a pessimistic locking read of an existing batch row, used to guarantee consistency before an update is applied.
  • UPDATE_ROW — Updates an existing batch row identically keyed as INSERT_ROW, including the Who audit columns.
  • DELETE_ROW — Removes a batch record by batch identifier.
  • ADD_LANGUAGE — Maintains the translated (TL) records for the batch, propagating the base-language row into the additional languages registered in FND_LANGUAGES.
  • CREATE_IMPORT_BATCH — The principal business-level entry point. It creates a batch for a given source system code (defaulting to PIMDH), organization, batch type, assignee, and batch name, and accepts options controlling match-on-data-load, default matching rules, single-match confirmation, import on data load, cross-reference-only import, revision import policy, and structure name.
  • UPDATE_BATCH_STATUS — Transitions the status of an existing import batch. This procedure is the object returned when searching for "update_batch_status". Status values drive the import processing workflow (for example, whether a batch is open, submitted, or complete), so this procedure is central to orchestrating batch progression.

Tables Accessed

The package reads and writes EGO_IMPORT_BATCHES_B and its translation table EGO_IMPORT_BATCHES_TL. It validates and resolves values using EGO_SOURCE_SYSTEM_EXT (source system registration), EGO_IMPORT_OPTION_SETS and EGO_IMPORT_OPTION_SETS_S (stored import configuration), MTL_PARAMETERS and MTL_SYSTEM_ITEMS_INTF_SETS_S (organization and interface set context), and BOM_STRUCTURE_TYPES_B and BOM_ALTERNATE_DESIGNATORS (structure and alternate definitions). Lifecycle and change context come from ENG_LIFECYCLE_STATUSES and ENG_ENGINEERING_CHANGES, while FND_LANGUAGES supports ADD_LANGUAGE and DUAL supports singleton validation logic.

Usage Notes

The package is normally invoked by PIM/PDH import forms, concurrent programs, and the Data Hub batch creation flow rather than being called directly by end users. Custom integrations that create or transition import batches should call CREATE_IMPORT_BATCH and UPDATE_BATCH_STATUS rather than the row-level DML procedures, to preserve validation of option sets and source systems. Because of AUTHID CURRENT_USER, the invoking schema must hold the required object privileges, and callers should commit explicitly after status changes. No other packages are documented as referencing this package.