Search Results ego_bulkload_entities




Overview
Explore in AI Chat

Overview

EGO_BULKLOAD_ENTITIES is a PL/SQL package owned by the APPS schema that supports the bulk import of entities into Oracle E-Business Suite through the Excel-based import framework. In the context of Oracle EBS 12.1.1 and 12.2.2, it serves as the programmatic bridge between the product data hub (EGO) import utilities and the concurrent manager, enabling users to upload item, result format, and related entity data from spreadsheet templates and process them through the standard import pipeline. The package header carries a version identifier (120.5, dated 2007/07/12), reflecting its long-standing role in the EGO schema. Its API classification is recorded as OTHER, indicating it is not a public, formally certified API but is used internally by the Excel Import feature.

The package abstracts two distinct responsibilities: launching the import work itself, and registering the resulting concurrent request against the import batch so that downstream processes can track and reconcile the load. This makes it central to the automation of high-volume entity creation without manual data entry.

Key Procedures and Functions

Two documented procedures are exposed by the package:

  • BulkLoadEntities — This procedure is invoked from the Excel Import flow. It launches the concurrent program that performs the bulk entity load and then calls the underlying API to update the request identifier into the EGO_IMPORT_BATCHES_B table, ensuring the spawned request is linked to its originating batch. It receives the result format usage context, user, language, responsibility, and application identifiers, along with a start-upload flag and a data set identifier, and returns the standard concurrent ERRBUF and RETCODE out parameters for completion status.
  • Run_Import_Program — This procedure drives the actual import program execution. It accepts a broad set of import configuration parameters covering the result format usage, user/session context, run source, batch creation and naming, automatic import and matching behavior on data load, change order handling (option, category, type, name, number, description, and item inclusion), and the National/Inventory Reporting option, and returns an x_request_id out parameter identifying the submitted concurrent request. It is the entry point by which customized or automated import submissions are submitted to the concurrent manager.

Tables Accessed

The package accesses the following documented tables via APPS synonyms:

  • EGO_IMPORT_BATCHES_B — Referenced to record the concurrent request identifier against the batch record created or processed during the load, linking the batch to its executing request.
  • EGO_BULKLOAD_INTF — The bulk load interface table that holds the staged entity rows that the import program consumes during processing.
  • EGO_RESULTS_FMT_USAGES — Provides the result format usage context that governs how imported data is interpreted and formatted, keyed by the result format usage identifier passed into the procedures.

Usage Notes

EGO_BULKLOAD_ENTITIES is typically invoked indirectly rather than by end users. The primary path is through the Excel Import functionality in the EGO product data management module, where a business user uploads a populated spreadsheet and triggers the bulk load; this framework call reaches BulkLoadEntities, which in turn submits the import concurrent program through Run_Import_Program. Because Run_Import_Program exposes a comprehensive parameter set, it can also be called from custom concurrent program definitions, Oracle Forms personalizations, or bespoke PL/SQL automation that requires programmatic import submission outside the standard spreadsheet flow.

When invoking the package from custom code, the caller must supply valid user, responsibility, application, and language identifiers so that the import executes under the correct security context. The returned request identifier should be retained for monitoring and reconciliation. Since the package is not classified as a certified public API, custom integrations should be regression-tested against both 12.1.1 and 12.2.2, as internal signature behavior may differ between releases. The referenced tables must remain accessible and the EGO import concurrent programs must be enabled for the procedures to complete successfully.