Search Results hz_imp_load_stage1




Overview
Explore in AI Chat

Overview

HZ_IMP_LOAD_STAGE1 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Oracle Trading Community Architecture (TCA) bulk import infrastructure, specifically the staging layer that supports the Customer/Party Import process. Its principal responsibility is to transform raw imported data that has been loaded into the interface (staging) tables into the structured work-unit format that the downstream party and account import routines consume. In practical terms, HZ_IMP_LOAD_STAGE1 sits near the front of the import pipeline: records arrive from external sources or the Import Batch interface, and this package prepares, partitions, and enqueues that data so that subsequent processing phases can validate, de-duplicate, and ultimately create HZ_PARTIES, HZ_LOCATIONS, and related entities.

The package is classified as an "OTHER" API rather than a public, supported interface. It is an internal worker package invoked by the TCA import framework rather than by customer-written application code.

Key Procedures and Functions

A single documented procedure is exposed by the ETRM metadata for this package:

  • WORKER_PROCESS — The core processing routine of the package. Its purpose is to read the staged import records and construct the work units that drive later phases of the import. It acts as a worker, meaning it is designed to be driven by a parent process or concurrent manager that supplies the batch context, processes the associated staging data, and writes the resulting work items into the HZ_IMP_WORK_UNITS table. Parameter lists are not documented and should not be assumed; callers should treat the signature as internal.

No other procedures or functions are documented in the ETRM metadata for this object.

Tables Accessed

The package reads and writes the following staging tables through APPS synonyms:

  • HZ_IMP_BATCH_DETAILS — Holds the individual import records associated with a batch. WORKER_PROCESS reads these detail rows to determine which records require staging and to build the corresponding work units.
  • HZ_IMP_BATCH_SUMMARY — Holds batch-level header and control information, including batch status and counts. It is used to identify the batch being processed and to coordinate status updates as staging progresses.
  • HZ_IMP_WORK_UNITS — The output table. WORKER_PROCESS inserts the work-unit records that enumerate the discrete actions (such as creating a party or a location) to be performed by later import stages.

Usage Notes

HZ_IMP_LOAD_STAGE1.WORKER_PROCESS is not intended to be called directly from custom forms or ad hoc SQL. In a standard EBS deployment it is invoked by the TCA party import concurrent programs, for example the "Import Batch to TCA Registry" and related customer import concurrent programs that orchestrate the staging, loading, and validation steps. The typical lifecycle is: data is loaded into the interface tables, a batch is created, the staging worker process is spawned to populate HZ_IMP_WORK_UNITS, and downstream packages then consume those work units to persist records into the TCA registry.

Because the object is classified as OTHER and its procedures carry no documented public signature, any direct invocation should be considered unsupported. Customizations should instead hook into the supported import concurrent programs, or read and validate the staging tables after the standard process completes. When diagnosing import failures, DBAs commonly inspect HZ_IMP_BATCH_SUMMARY, HZ_IMP_BATCH_DETAILS, and HZ_IMP_WORK_UNITS to determine whether WORKER_PROCESS completed successfully and whether work units were generated as expected. Dependency information confirms the package is self-contained within the APPS schema and references standard SYS constructs, with no dependency on or from other application packages beyond itself.