Results for “rule_notes”

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

Overview

The CZ_PSN_TYPED_RULE_REFS_V view is a Configurator (CZ) product dictionary object owned by the APPS schema. It presents a consolidated, typed view of the rules that are referenced by product structure nodes (PS nodes) within a configurator model. Its principal role is to expose the association between a model's physical/logical node structure and the typed rules attached to those nodes, together with the detailed attributes of each rule.

Because the view joins two other Configurator views, it reconciles two dimensions of configuration data: the structural placement of a rule (which model, which node, whether it is a referenced rule or inherited from an enclosing model) and the rule definition itself (its type, datatype, signature, template, presentation behaviour, and effectivity). This makes it useful for reporting on configuration rule usage, for integration routines that need to walk a model's rule set, and for diagnostic queries during Configurator implementation and troubleshooting in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The documented referenced base objects are:

• CZ_PSNODE_RULE_REFS_V (VIEW) — supplies the product structure node side of the join, aliased as P2RUL. It contributes model identity, node identity, parent relationships, node name, rule reference flags, folder context, and rule naming/typing at the node level.
• CZ_TYPED_RULES_V (VIEW) — supplies the rule definition side, aliased as TRUL. It contributes detailed rule typing, datatype, template and signature information, presentation and mutability flags, effectivity data, and rule text.
• CZ_UTILS (PACKAGE) — documented as a referenced object, typically invoked through expressions in the view's SQL for derivations or helper logic.

The view is defined as a join on P2RUL.RULE_ID = TRUL.RULE_ID, meaning every row represents one rule reference on a PS node paired with its corresponding typed rule definition. Only rules that exist in both source views are returned.

Key Columns

• MODEL_ID, PSN_MODEL_ID, RULE_MODEL_ID — model identifiers for the node's model, the PS node model, and the rule's owning development model respectively.
• PSN_EXPL_ID, RULE_EXPL_ID — model reference explosion identifiers for the node reference and the rule reference.
• REFERENCED_RULE_FLAG, RULE_IN_ENCLOSING_MODEL_FLAG — indicate whether the rule is referenced from another model and whether it resides in an enclosing model.
• PS_NODE_ID, PARENT_ID, PS_NODE_NAME, PSN_PS_NODE_TYPE — the node identity, hierarchy and type within the product structure.
• RULE_ID, PERSISTENT_RULE_ID, RULE_NAME, RULE_TYPE, RULE_TYPE_CODE, RULE_TYPE_LABEL, DETAILED_RULE_TYPE, RULETYPE_DATATYPE — rule identification and typing attributes.
• EXPR_ROOT_RULE_TEMPLATE_ID, SIGNATURE_ID, TEMPLATE_TOKEN, TEMPLATE_PRIMITIVE_FLAG, PRESENTATION_FLAG, MUTABLE_FLAG, CLASS_NAME, INSTANTIATION_SCOPE — rule template, signature and runtime behaviour characteristics.
• RULE_FOLDER_ID, RULE_FOLDER_TYPE, RULE_SEQ_NBR_IN_FOLDER — folder grouping and ordering of the rule.
• RULE_DISABLED_FLAG, RULE_INVALID_FLAG — status indicators for the rule reference and definition.
• RULE_EFFECTIVE_FROM, RULE_EFFECTIVE_UNTIL, RULE_EFFECTIVE_USAGE_MASK, RULE_EFFECTIVITY_SET_ID — effectivity attributes controlling when a rule applies.
• RULE_TEXT, RULE_DESCRIPTION, RULE_NOTES, CHECKOUT_USER — textual and administrative attributes.

Common Use Cases and Queries

Typical scenarios include auditing which rules are attached to nodes in a model, identifying rules shared through referenced models, and validating effectivity or disabled status during Configurator development. A representative query lists all rules for a given model:

SELECT ps_node_id, ps_node_name, rule_name, rule_type, detailed_rule_type, rule_disabled_flag, rule_effective_from, rule_effective_until FROM cz_psn_typed_rule_refs_v WHERE model_id = :p_model_id ORDER BY parent_id, rule_name;

To find rules referenced from other models, filter on the reference flag:

SELECT model_id, ps_node_name, rule_name, rule_model_id FROM cz_psn_typed_rule_refs_v WHERE referenced_rule_flag = 'Y';

To inspect effectivity gaps or invalid rules, query on the status and effectivity columns. Because the view is a join of two other views, queries should be constrained by MODEL_ID or RULE_ID for performance, and callers should treat the underlying CZ_UTILS logic as an implementation detail that may be recompiled between 12.1.1 and 12.2.2.