Search Results cz_imp_rules_n0

Overview

The CZ.CZ_IMP_RULES table is the primary interface (staging) table for rule import within the Oracle EBS 12.1.1 / 12.2.2 configuration and rules engine (CZ) schema. It belongs to the APPS_TS_INTERFACE tablespace, which confirms its role as a transient import structure: records are loaded here from external sources or CDL (Constraint Definition Language) scripts and then processed by the rule import program. Per the ETRM metadata, only CDL rules may be imported through this mechanism.

Each row represents a single rule definition to be loaded into the CZ modelling framework, carrying both the rule's structural attributes (type, expression references, folder placement, project association) and administrative control fields (run identifiers, record status, disposition) that drive the import process.

The Data Vault heuristic mined from the foreign-key structure classifies this object as standalone. In Data Vault modelling terms, this is best treated as an interface or staging object that feeds one or more raw vault hubs and links — particularly a Rule hub keyed by RULE_ID and a link associating rules with projects (DEVL_PROJECT_ID) and effectivity sets (EFFECTIVITY_SET_ID) — rather than a persisted hub, link, or satellite in its own right.

Key Information Stored

Of the 67 documented columns, the following carry the substantive rule definition and import control content:

• RULE_ID (NUMBER) — Associates the import record with a modelling Rule. This is the strongest business-key candidate for the rule identity.
• NAME (VARCHAR2 255) and DESC_TEXT (VARCHAR2 2000) — The rule name and descriptive text.
• RULE_TYPE (NUMBER) — Encodes the rule category: 21 Logic, 22 Numeric, 23 Compat, 24 Compat Table, 25 Func Preselect, 26 Func Validate, 27 Comparison, 28 RULETYPE, 29 Func Comp, 30 Design Chart.
• EXPR_RULE_TYPE (NUMBER) — Describes the rule operation: Requires, Implies, Excludes, Negates, Defaults, NumSelections, Sets, Contributes, Supplies, or Consumes.
• ANTECEDENT_ID and CONSEQUENT_ID — Identify the antecedent and consequent expressions of the rule.
• REASON_ID — References a CZ_LOCALIZED_TEXTS record holding the message shown when the rule is violated.
• RULE_FOLDER_ID — Locates the rule within a folder/sequence; GRID_ID links an Explicit Compatibility definition.
• DEVL_PROJECT_ID — Identifies the project/model associated with the record.
• INVALID_FLAG — '1' flags the rule invalid, '0' valid.
• RUN_ID, REC_STATUS, and DISPOSITION — Import-batch control columns, indexed by CZ_IMP_RULES_N0, used to track processing outcomes.
• EFFECTIVE_FROM, EFFECTIVE_UNTIL, EFFECTIVITY_SET_ID, and SIGNATURE_ID — Effectivity and signature governance attributes.

The documented unique indexes, SYS_IL0000324915C00043$$ and SYS_IL0000324915C00044$$, are LOB indexes on APPS_TS_INTERFACE and are not business-key candidates; they support LOB columns in the table. Genuine uniqueness is not enforced by a non-LOB unique constraint in the documented schema, so RULE_ID combined with RUN_ID serves as the practical key. Two NONUNIQUE indexes, CZ_IMP_RULES_N0 (RUN_ID, REC_STATUS, DISPOSITION) and CZ_IMP_RULES_N1 (RUN_ID, RULE_ID), drive import processing and lookup performance.

Common Use Cases and Queries

Typical scenarios include monitoring import batch progress, resolving failed rows, and auditing rule definitions before promotion into the production rule set.

• Batch status reporting — count records by disposition for a given import run:
  SELECT REC_STATUS, DISPOSITION, COUNT(*) FROM CZ.CZ_IMP_RULES WHERE RUN_ID = :run_id GROUP BY REC_STATUS, DISPOSITION;
• Identifying failed or unprocessed rows for reprocessing:
  SELECT RULE_ID, NAME, RULE_TYPE, REC_STATUS FROM CZ.CZ_IMP_RULES WHERE RUN_ID = :run_id AND REC_STATUS <> 'SUCCESS';
• Rule inventory by project and type, using indexed columns:
  SELECT RULE_TYPE, COUNT(*) FROM CZ.CZ_IMP_RULES WHERE DEVL_PROJECT_ID = :project_id GROUP BY RULE_TYPE;
• Validating rule validity before import — filter on INVALID_FLAG = '0' and inspect REASON_ID linkages to CZ_LOCALIZED_TEXTS for message completeness.
• Reconciling imported rules against existing definitions by joining on RULE_ID via CZ_IMP_RULES_N1.

Related Objects

The following foreign-key relationships are documented in the ETRM metadata and should anchor integration queries:

• CZ.CZ_SUB_CON_SETS — referenced by SUB_CONS_ID, associating a sub-constraint set with the rule.
• CZ.CZ_GRID_DEFS — referenced by GRID_ID, linking the grid/compatibility definition.
• CZ.CZ_DEVL_PROJECTS — referenced by DEVL_PROJECT_ID, tying the rule to its project/model.
• CZ.CZ_EFFECTIVITY_SETS — referenced by EFFECTIVITY_SET_ID, governing rule effectivity.
• CZ.CZ_SIGNATURES — referenced by SIGNATURE_ID, capturing the rule signature.

Beyond the foreign-key set, the REASON_ID column implies a dependency on CZ_LOCALIZED_TEXTS for violation messages, and the rule import concurrent program consumes this table as its source. Queries should restrict access by RUN_ID to isolate batches in this shared interface table.