Search Results ego_import_option_sets_s

Overview

EGO_IMPORT_BATCHES_PKG is the PL/SQL package responsible for managing import batch definitions and their lifecycle within the Oracle EBS Product Information Management (PIM) / EGO (Engineering) schema. An import batch represents a logical grouping of records that are staged and processed together — for example, items, structures, or engineering change data being introduced into Oracle from an external source system. The package embodies the standard Oracle EBS table-handling (row CRUD) pattern around the EGO_IMPORT_BATCHES_B and EGO_IMPORT_BATCHES_TL tables, while extending that pattern with business-level operations that create batches and advance batch status through processing states.

The object is documented as VALID under the APPS schema and is classified as OTHER in the ETRM API registry. It is not referenced by any other database object, indicating that it is called directly by EBS forms, concurrent programs, or custom code rather than being nested inside other server-side packages. In the 12.1.1 and 12.2.2 code lines, this package forms part of the underlying infrastructure that supports enterprise-wide data import and bulk maintenance routines.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within this package:

• INSERT_ROW — Inserts a new import batch definition record, populating the transactional entity table along with its corresponding translatable (TL) row for the required languages.
• LOCK_ROW — Acquires a row-level lock on a batch definition prior to modification, ensuring concurrency safety during updates performed through the EBS forms layer.
• UPDATE_ROW — Updates the attributes of an existing import batch definition row, following the standard Who-columns and TL synchronization conventions used across Oracle Forms-based maintenance packages.
• DELETE_ROW — Removes a batch definition and its associated language rows, respecting the referential semantics of the base and translation tables.
• ADD_LANGUAGE — Creates additional translation rows in EGO_IMPORT_BATCHES_TL for languages in which the batch name or description has not yet been defined. It relies on the FND_LANGUAGES reference to identify installed languages.
• CREATE_IMPORT_BATCH — The primary business API. It assembles and persists a new import batch, deriving and validating the option set, source system, and structure-related attributes before writing the base and translation rows.
• UPDATE_BATCH_STATUS — Transitions an existing batch between processing states (for example, from an open/staged state to a processed or error state), which governs how the batch is subsequently consumed by the import engine.

Tables Accessed

The package reads and writes the core batch definition tables: EGO_IMPORT_BATCHES_B (base, language-independent attributes) and EGO_IMPORT_BATCHES_TL (translated name and description). Option-set configuration is sourced from EGO_IMPORT_OPTION_SETS and its _S variant, and the originating system is validated against EGO_SOURCE_SYSTEM_EXT. Engineering-context validation draws on ENG_ENGINEERING_CHANGES, ENG_LIFECYCLE_STATUSES, and lookup views such as ENG_CHANGE_ORDER_TYPES_VL.

Structure-related imports reference BOM_ALTERNATE_DESIGNATORS and BOM_STRUCTURE_TYPES_B, while MTL_PARAMETERS and MTL_SYSTEM_ITEMS_INTF_SETS_S supply inventory organization defaults and interface-set context. FND_LANGUAGES supports multilingual handling, and DUAL is used for singleton queries.

Usage Notes

This package is typically invoked from the Oracle Forms-based import batch maintenance UI, where the standard INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, and ADD_LANGUAGE pattern drives the block-level CRUD operations. Business-level creation and status changes are performed through CREATE_IMPORT_BATCH and UPDATE_BATCH_STATUS by concurrent programs or custom integrations that stage and process imported data. Because it is not referenced by any other database object, callers must invoke it explicitly.