Search Results cz_imp_rules




Overview
Explore in AI Chat

Overview

The CZ_IMP_RULES table resides in the CZ schema and belongs to the Oracle Configurator (CZ) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. As its description indicates, it is a staging or interface table used to import rule definitions into the Configurator rule repository. Rather than serving as the runtime source of truth for active configuration rules, CZ_IMP_RULES acts as a transient landing area where rule metadata is loaded from external sources, validated, and then processed into the primary rule tables during an import run.

The table carries 67 documented columns, giving it a broad footprint that captures rule identity, effectivity, presentation attributes, security masking, and import-control fields. Because the Configurator rule engine depends on consistent metadata across rules, grids, signatures, and effectivity sets, this staging table must carry foreign-key references to each of those entities so that the import process can reconcile them upon promotion.

From a dimensional modeling perspective, the heuristic Data Vault classification of CZ_IMP_RULES is standalone. This suggests that, for analytical or warehouse purposes, the table is best modeled as an independent structure rather than as a hub, link, or satellite. It does not decompose cleanly into a single business key, and its relationships are import-time associations rather than persistent business relationships, which reinforces the standalone classification.

Key Information Stored

Although 67 columns are documented, the most consequential for import logic and downstream reconciliation include the following:

The metadata documents two unique indexes, SYS_IL0000324915C00043$$ and SYS_IL0000324915C00044$$, which are LOB indexes rather than true business-key candidates. Practically, the business-key candidate remains RULE_ID, with PERSISTENT_RULE_ID offering a possible alternate persistent identifier.

Common Use Cases and Queries

Typical usage centers on monitoring, validating, and troubleshooting Configurator rule imports. A common pattern checks which rows failed disposition:

  • Querying CZ_IMP_RULES for rows where REC_STATUS or DISPOSITION indicates an error after a given RUN_ID.
  • Joining to CZ_SUB_CON_SETS, CZ_GRID_DEFS, CZ_DEVL_PROJECTS, CZ_EFFECTIVITY_SETS, and CZ_SIGNATURES via the documented foreign keys to confirm that referenced entities exist before promotion.
  • Reporting on rule counts by RULE_TYPE and EXPR_RULE_TYPE for a specific import run.
  • Reconciling effectivity windows using EFFECTIVE_FROM/EFFECTIVE_UNTIL against downstream rule tables.

A representative query filters staging rows by run and disposition:

SELECT RULE_ID, NAME, RULE_TYPE, REC_STATUS, DISPOSITION FROM CZ_IMP_RULES WHERE RUN_ID = :run_id AND REC_STATUS = 'ERROR';

Related Objects

The foreign keys documented for CZ_IMP_RULES identify its most significant related objects:

  • CZ_SUB_CON_SETS — joined on SUB_CONS_ID, linking rules to subordinate constraint sets.
  • CZ_GRID_DEFS — joined on GRID_ID, tying rules to grid definitions.
  • CZ_DEVL_PROJECTS — joined on DEVL_PROJECT_ID, associating rules with development projects.
  • CZ_EFFECTIVITY_SETS — joined on EFFECTIVITY_SET_ID, providing effectivity context.
  • CZ_SIGNATURES — joined on SIGNATURE_ID, linking rules to configurator signatures.

These relationships define the import-time dependency graph and should be validated in any promotion or reconciliation program that reads from CZ_IMP_RULES.