Results for “parent_signature_id”

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

Overview

The CZ_RULETEMPLS_BYLABEL_V view is a read-only database object owned by the APPS schema within the Oracle E-Business Suite Configurator product (CZ). It exposes Configurator rule templates keyed by their display label, aggregated at the level of the parent model signature. In EBS releases 12.1.1 and 12.2.2 the view carries a VALID status and forms part of the metadata layer that the Configurator runtime and its integration interfaces rely upon when resolving which rules, sub-templates, and template tokens may be offered during a configuration session.

Rather than storing data itself, the view consolidates information from the signature-argument structures, the rule definitions, and the compatibility signature view. Its principal purpose is to distinguish rules that share a common label from those that are ambiguous, and to flag whether a rule can be applied automatically or must be presented to the user for selection. This makes it useful for diagnostics, for building custom reports on configuration rules, and for integration programs that need to enumerate rules by their user-facing name.

Underlying Base Objects

The view is defined over three documented base objects:

• CZ_RULES (accessed through a synonym) — provides the rule identity, name, type, description text, sequence number, template token, and deletion flag.
• CZ_SIGNATURE_ARGUMENTS (synonym) — supplies the argument metadata for each rule signature, including argument index, data type, and deletion flag.
• CZ_COMPAT_TEMPL_SIGS_V (view) — supplies the parent and sub-template signature identifiers and the argument count used to group the result set.

The join is driven from CZ_COMPAT_TEMPL_SIGS_V to CZ_RULES on the sub-template signature identifier, with an outer join to CZ_SIGNATURE_ARGUMENTS so that rules without arguments are retained. Only non-deleted rules of type 100, 500, and 501 are considered, and arguments with a deleted flag of '0' and a data type of 3 (Boolean) are excluded from the argument count aggregation.

Key Columns

• PARENT_SIGNATURE_ID — identifier of the parent model or template signature to which the rule belongs.
• RULE_NAME — the rule label, derived from CZ_RULES.NAME, and the grouping attribute for the row.
• RULE_TYPE — the Configurator rule type (100, 500, or 501), governing the expression semantics.
• ARGUMENT_COUNT — number of arguments associated with the sub-template signature.
• USE_EXPR_TYPE — resolved expression type, computed so that a single rule under a label maps to a determinate type (200, 210, or 220) and multiple rules map to a multi-rule type (228 or 229).
• AVAIL_RULE_ID, AVAIL_SUBTEMPL_SIGNATURE_ID, AVAIL_TEMPLATE_TOKEN — return the corresponding value only when exactly one rule matches the label; otherwise NULL, signalling ambiguity.
• HAS_NONBOOLEAN_ARGUMENTS — set to 1 when a rule with a non-zero argument count has at least one non-Boolean argument.
• AVAIL_DESCRIPTION and SEQ_NBR — descriptive text and minimum sequence number for ordering.

Common Use Cases and Queries

The view is typically queried to determine whether a rule label is unambiguous before presenting it, and to retrieve the associated description and argument characteristics.

• Listing unambiguous rules for a parent signature: SELECT RULE_NAME, USE_EXPR_TYPE, AVAIL_RULE_ID FROM APPS.CZ_RULETEMPLS_BYLABEL_V WHERE PARENT_SIGNATURE_ID = :p_id AND AVAIL_RULE_ID IS NOT NULL ORDER BY SEQ_NBR;
• Detecting ambiguous labels requiring user selection: filter on AVAIL_RULE_ID IS NULL and AVAIL_TEMPLATE_TOKEN IS NULL.
• Identifying rules with non-Boolean arguments: WHERE HAS_NONBOOLEAN_ARGUMENTS = 1.
• Reporting rule descriptions by label: SELECT RULE_NAME, AVAIL_DESCRIPTION FROM APPS.CZ_RULETEMPLS_BYLABEL_V WHERE PARENT_SIGNATURE_ID = :p_id;

All such queries should include the APPS. prefix and observe the view's read-only nature; no DML is permitted against it.