Search Results g_data_rows_uploaded_new

Overview

EGO_BULKLOAD_ENTITIES is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented API classification is OTHER, reflecting its role as an internal processing engine rather than a published integration interface. The package performs bulk import of item and bill-of-material (BOM) entity data, orchestrating the staged records held in the bulkload interface table and pushing them through the item and BOM APIs. The source header (EGOBKUPB.pls 120.13) indicates the package has been maintained across multiple releases and is the back-end engine behind the seeded bulkload concurrent program.

The package maintains several global constants that control processing state, including G_DATA_ROWS_READY_FOR_API, G_DATA_ROWS_UPLOADED_NEW, G_ITEM_API, and G_BOM_API. The variable g_data_rows_uploaded_new is the counter that tracks the number of newly uploaded rows during a run; it is initialized to zero by SetProcessConstants and incremented as records are successfully processed by the APIs. It is paired with G_DATA_ROWS_READY_FOR_API and the API type identifiers G_ITEM_API (10) and G_BOM_API (20), which distinguish item uploads from BOM uploads in the processing logic and logging.

Key Procedures and Functions

The ETRM metadata documents two procedures in the package:

• BULKLOADENTITIES — the primary driver procedure. It reads staged entity records from the bulkload interface and invokes the appropriate item or BOM APIs, using the global API identifiers to route each row. It manages the counters, including g_data_rows_uploaded_new, to report how many new entities were successfully uploaded.
• RUN_IMPORT_PROGRAM — the concurrent-program entry point. It initializes processing constants through SetProcessConstants, resolves the debug profile option (INV: Debug Trace), and calls the main bulkload logic, writing progress and error messages to the concurrent log via Write_Debug.

Internal helper logic includes SetProcessConstants, which establishes return-status constants (success, warning, error, unexpected error) and initializes the global counters, and Write_Debug, which conditionally writes messages to the concurrent manager log when debug tracing is enabled.

Tables Accessed

The package references the following tables through APPS synonyms:

• EGO_BULKLOAD_INTF — the bulkload interface table. It stores the staged item and BOM entity rows that the package reads and processes. Rows are typically marked as uploaded as their counters are incremented, providing run-level status reporting.
• EGO_RESULTS_FMT_USAGES — accessed for formatting results, supporting the output of bulkload processing results in the expected structure.

Usage Notes

EGO_BULKLOAD_ENTITIES is invoked indirectly through the seeded bulkload concurrent program rather than by direct API calls from custom code. Because the package body exposes only the two documented procedures and is classified as OTHER, Oracle does not guarantee its internal globals—including g_data_rows_uploaded_new—as a supported extension point. Developers who query or reference these variables, or who call BULKLOADENTITIES directly from custom programs, do so at their own risk across patches and upgrades. The referenced-by count of zero confirms the package is a top-level processing engine, not a shared utility. For diagnostics, enabling the INV: Debug Trace profile option causes Write_Debug to emit detailed messages to the concurrent request log, which is the supported way to observe counters such as g_data_rows_uploaded_new during a bulkload run.