Search Results worker_process




Overview
Explore in AI Chat

Overview

HZ_IMP_LOAD_STAGE1 is the first-stage worker package within the Oracle E-Business Suite Trading Community Architecture (TCA) bulk import framework. Its business function is to consume "work units" produced during the earlier extraction and staging phases of a customer, supplier, or party import batch, then perform the stage-one matching and load activity required before the batch proceeds to subsequent stages. In Oracle EBS 12.1.1 and 12.2.2 the package is owned by APPS and is classified as an OTHER package, meaning it is not a public transactional API but rather an internal component of the HZ_IMP_* import infrastructure. The batch framework stages the work so that large imports can be parallelized; HZ_IMP_LOAD_STAGE1 represents the loop-driven engine that each concurrent worker executes against its assigned unit of interface data.

Key Procedures and Functions

The package exposes one documented procedure: WORKER_PROCESS. It is the entry point invoked by the import framework for stage one. Its purpose is to iterate over the work units belonging to a given batch and to drive stage-one processing to completion. The procedure accepts parameters identifying the batch, indicating the content source, specifying whether the run is a re-run, and supplying a batch mode flag (the formal parameter list is defined in the source header and should be treated as internal). Within its loop it calls HZ_IMP_LOAD_WRAPPER.RETRIEVE_WORK_UNIT to obtain the next orig system and orig system reference range, writes diagnostic output to the concurrent manager log via FND_FILE.PUT_LINE, and exits when no further work is returned. It also applies a session-level event to suppress skip scans during matching and manages a re-run flag so that, after a previously failed or resumed batch, records whose interface status is null are still picked up.

Tables Accessed

Through APPS synonyms the package references three documented tables:

  • HZ_IMP_WORK_UNITS: the partitioning table that defines each unit of work by batch, orig system, and orig system reference. It also stores hwm_stage, which the procedure reads to determine whether stage one has already completed at least once, thereby governing the re-run behavior.
  • HZ_IMP_BATCH_DETAILS: holds the individual interface rows for the batch, and is the primary source of party records examined and updated during stage-one matching.
  • HZ_IMP_BATCH_SUMMARY: records batch-level status and control information used to coordinate processing and to report overall batch progress.

Usage Notes

WORKER_PROCESS is not intended for ad hoc invocation. It is normally launched by the HZ import batch orchestration as a concurrent worker, one process per work unit range, under the control of the parent import program. It may also be called from custom code that re-drives a stalled batch or performs a controlled resume, but such callers must supply a valid batch identifier and the correct re-run and batch mode indicators. Because the procedure alters session behavior for matching and writes extensively to the concurrent log, it should be executed with logging enabled. In 12.2.2 the object remains an internal APPS-owned worker and is not referenced by other documented packages, reinforcing that it is a subordinate component of the HZ_IMP_LOAD framework rather than a reusable API.