Results for “cz_imp_im_main”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CZ_IMP_IM_MAIN is a public PL/SQL package body in the Oracle E-Business Suite 12.1.1 and 12.2.2 codebase. It belongs to the Oracle Configurator (CZ) schema and supports the Configuration Workbench import and migration facility. Its primary responsibility is to convert staged configuration data staged in the CZ_IMP_* interface tables into the corresponding production tables (CZ_PROPERTIES and related structures) so that item master properties, item types, item type properties, property values, and runtime configuration data are moved from an external or legacy source into the EBS configuration repository.

The internal naming convention (CND_, MAIN_, RPT_) reflects the three phases of each import unit: condition/validation, main transformation/load, and reporting of import results. The package was last shipped as version 120.1.12020000.2 and remains present in both the 12.1.1 and 12.2.2 releases; it is registered in ETRM with API classification OTHER. Fault handling is a central design concern: the body is written around the x_error BOOLEAN pattern, returning status flags from CZ_UTILS.LOG_REPORT and incrementing a FAILED counter when the MAX_ERR ceiling or a SQL exception is hit.

Key Procedures and Functions

The package exposes fifteen documented procedures, organized in triads that mirror the import lifecycle:

• CND_ITEM_MASTER, CND_ITEM_PROPERTY_VALUE, CND_ITEM_TYPE, CND_ITEM_TYPE_PROPERTY, CND_PROPERTY — Condition/validation routines. They mine rows from the corresponding CZ_IMP_* staging tables, check for null flags, duplicates, and data inconsistencies, and set error indicators before the actual load proceeds.
• MAIN_ITEM_MASTER, MAIN_ITEM_PROPERTY_VALUE, MAIN_ITEM_TYPE, MAIN_ITEM_TYPE_PROPERTY, MAIN_PROPERTY — Main transformation procedures. They perform the actual insert/update of imported rows into the production configuration tables, applying the defaulting and delete-flag logic seen in the source (for example, DELETED_FLAG and DECIMAL_QTY_FLAG defaulted to '0').
• RPT_ITEM_MASTER, RPT_ITEM_PROPERTY_VALUE, RPT_ITEM_TYPE, RPT_ITEM_TYPE_PROPERTY, RPT_PROPERTY — Reporting procedures. They publish per-entity import results, including error counts and duplicate counts, into the run-result tables for user review.

The documented body source for CND_ITEM_MASTER illustrates the shared pattern: a cursor over CZ_IMP_ITEM_MASTER filtered by RUN_ID and REC_STATUS IS NULL, a COMMIT_SIZE batching mechanism, MAX_ERR enforcement via CZ_ADMIN.IMP_MAXERR_REACHED, and per-row exception handling that invokes CZ_UTILS.LOG_REPORT to set x_error and increment FAILED.

Tables Accessed

• CZ_IMP_ITEM_MASTER, CZ_IMP_ITEM_PROPERTY_VALUE, CZ_IMP_ITEM_TYPE, CZ_IMP_ITEM_TYPE_PROPERTY, CZ_IMP_PROPERTY — Staging/interface tables read and updated by the CND_ and MAIN_ procedures; rows are selected by RUN_ID and updated through ROWID.
• CZ_PROPERTIES — Production configuration property repository written by the property load routines.
• CZ_XFR_RUN_INFOS and CZ_XFR_RUN_RESULTS — Transfer run control and result tables used to track each import execution and record its outcome.
• DBMS_UTILITY and PLITBLM — Oracle-supplied packages referenced for utility calls and PL/SQL table handling during processing.

Usage Notes

CZ_IMP_IM_MAIN is not an end-user API; it is invoked from the Oracle Configurator import and migration concurrent programs and from custom loaders that stage data into the CZ_IMP_* tables. A caller first populates the interface tables and obtains a RUN_ID, then calls the CND_, MAIN_, and RPT_ procedures in sequence for the entity being imported, passing COMMIT_SIZE and MAX_ERR control parameters. Because the procedures use x_error BOOLEAN and FAILED OUT NOCOPY counters rather than raising top-level exceptions, custom code must inspect the returned status and the CZ_XFR_RUN_RESULTS rows. Two other packages reference CZ_IMP_IM_MAIN, so the signature of its entry points should be treated as a public contract. In 12.1.1 and 12.2.2 the behavior is identical; the differences are confined to underlying CZ table releases and patching, and any modifications should be avoided in favor of wrapping calls through supported concurrent program interfaces.