Search Results cz_uprt_multiple_roots

Overview

The APPS.CZ_RULE_TEXT_GEN package body is a component of the Oracle E-Business Suite Configure-to-Order (CTO) and Oracle Configurator infrastructure, residing in the heterogeneous CZ_ schema family. Its central responsibility is the generation of textual representations of configuration rules. In EBS 12.1.1 and 12.2.2, configuration models frequently express their validity, compatibility, and selection logic as rule expressions. These expressions are persisted internally as structured parse trees, but they must also be presented to end users in a human-readable form — within the Configurator UI, printed documentation, or validation reports. CZ_RULE_TEXT_GEN performs the translation from the internal expression representation into textual rule statements, traversing the expression node graph and emitting operator, literal, property, and constant tokens accordingly.

The package appears in the ETRM registry with an API classification of OTHER, indicating it is an internal helper rather than a public or published API. Applications and forms do not call it directly; it is invoked by higher-level Configurator runtime packages that manage rule definition, validation, and model publication.

Key Procedures and Functions

Only one procedure is documented for this package:

• PARSE_RULES — Navigates the configuration rule expression structures and produces their corresponding textual rule output. It accepts a development project identifier and, optionally, a specific rule identifier; when no rule is supplied, the procedure processes the rules associated with the project. Internally the procedure references the full vocabulary of Configurator expression tokens — operators, literals, PSNodes, properties, system properties, constants, arguments, templates, FORALL constructs, iterators, WHERE clauses, and compatibility operators — along with data-type indicators for integer, decimal, boolean, and text values. It also defines the constant values for the mathematical entities pi and e. Clearly defined exceptions (CZ_UPRT_MULTIPLE_ROOTS, CZ_UPRT_UNKNOWN_TYPE, CZ_UPRT_INCORRECT_PROP, CZ_UPRT_INCORRECT_NODE) signal malformed or unsupported expression trees, allowing the calling layer to fail cleanly rather than emit corrupt rule text.

The constants EXPR_PSNODE, PS_NODE_TYPE_REFERENCE, and PS_NODE_TYPE_CONNECTOR indicate that the procedure understands both expression-tree nodes and Problem Space node references and connectors, enabling rule text to reference configuration nodes by name. No additional procedures or functions are documented in the ETRM metadata.

Tables Accessed

The package reads from the following tables, accessed through APPS synonyms:

• CZ_RULES — the master definition of configuration rules from which the target rule identifiers are obtained.
• CZ_EXPRESSION_NODES — stores the individual nodes of each rule's expression parse tree; the primary source for reconstruction of rule logic.
• CZ_PS_NODES — provides Problem Space node definitions referenced by expressions, supplying the display names used in generated text.
• CZ_PROPERTIES — holds model property definitions whose names and data types are rendered in rule statements.
• CZ_MODEL_REF_EXPLS — associates models with their referenced expressions, supporting resolution of rule ownership.
• CZ_DB_SETTINGS — configuration settings that influence rule generation behavior, including schema version handling.
• PLITBLM — the standard Oracle PL/SQL internal table used by the parser for intermediate token storage during text assembly.

Usage Notes

CZ_RULE_TEXT_GEN is an internal utility and is not intended to be called directly from custom code. It is invoked by the Configurator rule-management and model-publication flows when textual rule descriptions must be regenerated — for example, after rule edits in the Configurator UI, during model publication, or when producing rule documentation. Because the package raises named exceptions on invalid expression structures, callers should be prepared to handle these during rule maintenance operations. Customizations should target the documented public Configurator APIs rather than this package, and any review of rule text generation should account for its dependency on the referenced expression and property tables remaining internally consistent.