Search Results parse_rules




Overview
Explore in AI Chat

Overview

APPS.CZ_RULE_TEXT_GEN is a server-side PL/SQL package within the Oracle E-Business Suite Oracle Configurator (CZ) product family. In release 12.1.1 and 12.2.2 it is registered with an API classification of OTHER and is owned by the APPS schema. Its stated purpose, taken directly from the package header comments, is to act as a Public API for Model Conversion. In practical terms the package is responsible for generating the textual representation of configuration rules that belong to a Configurator model.

The header identifies the package as the entry point through which rule text is produced for a given development project (model) and, optionally, for a single rule within that model. This supports the broader Model Conversion workflow, in which configuration models authored in the Configurator modeling environment are transformed into forms that can be rendered, interpreted, or migrated. The package exists in both the 12.1.1 and 12.2.2 code lines; the shipped source carries a header revision string referencing an April 2007 build, indicating that the API has remained stable across the 12.x family.

Key Procedures and Functions

The package exposes a single documented procedure: PARSE_RULES.

  • PARSE_RULES — The core API for rule text generation. It accepts a development project identifier that designates the model for which rule text must be generated, and an optional rule identifier that narrows the operation to a specific rule. When the rule identifier is omitted, the procedure operates across the model. It serves as the public conversion entry point, meaning callers invoke it rather than manipulating the underlying node and expression tables directly.

No other procedures or functions are documented in the ETRM metadata for this package; the public specification consists solely of PARSE_RULES. Internal helper logic is not exposed through the package interface.

Tables Accessed

The package reads and writes a set of Configurator model and rule tables through APPS synonyms. The documented references are:

  • CZ_RULES — Stores the configuration rules being converted; the source of rule identifiers supplied to PARSE_RULES.
  • CZ_EXPRESSION_NODES — Holds the node-level expression components that make up rule logic and are traversed during parsing.
  • CZ_PS_NODES — Contains the node definitions for the model structure, required to resolve expression references.
  • CZ_MODEL_REF_EXPLOSIONS — Provides the exploded model reference structure, linking rules to the model's component hierarchy.
  • CZ_PROPERTIES — Supplies property definitions referenced by rules and expressions.
  • CZ_DB_SETTINGS — Holds Configurator setup and configuration values that influence generation behavior.
  • PLITBLM — A generic PL/SQL table used for intermediate collections during processing.

Together these tables provide the rule definitions, expression trees, model structure, and configuration context needed to emit rule text for the target model.

Usage Notes

PARSE_RULES is invoked during Model Conversion operations, generally as a programmatic call from Configurator conversion logic rather than from a standard user-facing form. Because the ETRM metadata records that the package is referenced by one other package, it is consumed as a dependency of that higher-level conversion component, which supplies the development project identifier and, where applicable, a specific rule identifier.

Typical invocation patterns include server-side PL/SQL calls from concurrent program logic or from custom code that drives model conversion. When troubleshooting rule text output, the parameter governing scope is significant: passing only the project identifier processes all rules in the model, while passing a rule identifier restricts generation to that rule, which is useful for isolated testing or regeneration of a single rule. Because the package writes rule text derived from the CZ_RULES and expression tables, callers should ensure the model data is in a consistent state before invocation to avoid generating text from partially defined rules.