Search Results hz_imp_load_code_assignments




Overview
Explore in AI Chat

Overview

HZ_IMP_LOAD_CODE_ASSIGNMENTS is a PL/SQL package in the Oracle EBS Trading Community Architecture (TCA) / Receivables (AR) module, declared AUTHID CURRENT_USER and owned by the APPS schema. Its business function is to support the bulk import of party classification code assignments — that is, the association of standardized classification codes (such as industry codes, customer category codes, or other lookups defined by class category) to parties and party sites during data conversion, migration, or scheduled interface processing.

The package operates against the interface table HZ_IMP_CLASSIFICS_INT, which functions as the staging area for classification records entering the TCA model. The package exposes a PL/SQL collection type for nearly every column of that interface table — BATCH_ID, PARTY_ORIG_SYSTEM, PARTY_ORIG_SYSTEM_REFERENCE, CLASS_CATEGORY, CLASS_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE, INSERT_UPDATE_FLAG, RANK, INTERFACE_STATUS, ERROR_ID, and the standard WHO/audit and concurrent-program columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY_MODULE). It also declares collection types mapped to the destination table HZ_CODE_ASSIGNMENTS, including CODE_ASSIGNMENT_ID and OWNER_TABLE_ID. This strongly indicates the package is designed for bulk/batch loading of staged classification data into the base TCA tables.

Key Procedures and Functions

The ETRM documentation records a single documented program unit in this package:

  • LOAD_CODE_ASSIGNMENTS — The primary loader routine. Based on the surrounding metadata, this procedure consumes the staged rows in the HZ_IMP_CLASSIFICS_INT interface table (typically filtered by a batch identifier) and applies them to the destination code assignment records associated with parties. Because the package declares INSERT_UPDATE_FLAG and INTERFACE_STATUS collection types, the procedure is expected to honor the insert-versus-update indicator on each staged row and to stamp an interface status back onto the interface record to record success or failure. Records that fail validation are expected to be written to the error tables (HZ_IMP_ERRORS / HZ_IMP_TMP_ERRORS) with an associated ERROR_ID.

The parameter lists of these routines are not reproduced in the available metadata and should be confirmed against the live package specification before being invoked from custom code.

Tables Accessed

The package references the following tables through APPS synonyms:

  • HZ_IMP_CLASSIFICS_INT — The classification interface/staging table. Primary source of incoming rows; the package's collection types are modelled directly on its columns.
  • HZ_CODE_ASSIGNMENTS — The destination TCA table that stores code assignments for entities. The loader inserts or updates rows here; CODE_ASSIGNMENT_ID and OWNER_TABLE_ID are declared against this table.
  • HZ_IMP_ERRORS, HZ_IMP_TMP_ERRORS, HZ_IMP_ERRORS_S — Error capture and sequencing objects used to log rejected rows and assign error identifiers.
  • HZ_IMP_PARTIES_INT — Party-level interface staging, referenced to resolve or validate the party being classified.
  • HZ_IMP_CLASSIFICS_SG — A sequence/ID generation object for classification interface records.
  • HZ_PARTIES and HZ_ORGANIZATION_PROFILES — Base TCA party and organization profile tables, consulted to validate the target party and organization context before assignment.
  • DUAL and PLITBLM — Utility references supporting PL/SQL table operations.

Usage Notes

This package is not an end-user-facing API; it is an internal loader typically invoked by the TCA party/classification import concurrent programs (for example, the Customer Interface or party import batch processes) after data has been staged in HZ_IMP_CLASSIFICS_INT and the related party interface tables. The presence of REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID collection types confirms that the routine runs within a concurrent program context and is designed to propagate the request identifier to the loaded rows.

The package is referenced by one other package in the ETRM registry, indicating it forms part of a larger import-processing call chain rather than being called directly. Custom code should invoke the supported public TCA import APIs or concurrent programs rather than calling LOAD_CODE_ASSIGNMENTS directly, because the routine expects its input interface tables to be populated and sequenced correctly by the upstream import framework. All processing runs under the privileges of the invoking user (AUTHID CURRENT_USER), so appropriate APPS-level or TCA responsibility grants are required.