Results for “property_data_type”

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

Overview

CZ_PROPERTIES_FOR_CONTEXT_V is a Configurator (CZ) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Configurator module and presents a flattened, denormalized projection of the configuration model metadata: the properties (rules) that are available within a given context type (signature), together with their binding, data-type, collection, and engine-compatibility characteristics. In effect, the view answers the question "which properties apply to which context, and how are they typed and bound?" for a model's context signatures.

Because the view surfaces engine-compatibility filtering and rule-type lookup labels, it is typically consumed by Configurator runtime logic, model validation reports, and integration programs that need to inspect the property/signature relationship without walking the highly normalized underlying CZ tables directly. It is read-only diagnostic and reporting metadata rather than a transactional interface.

Underlying Base Objects

The view is defined over the following documented base objects:

• CZ_DEVL_PROJECTS (SYNONYM) — supplies the development project / model identifier (P_MODEL_ID) that scopes the property set.
• CZ_MODEL_PROP_ENGTYP_COMPAT_V (VIEW) — restricts the signatures presented to those whose config engine type is compatible with the model.
• CZ_RULES (SYNONYM) — the property/rule records that carry the rule name, sequence, rule type, and template token.
• CZ_SIGNATURES (SYNONYM) — supplies both the context signature (context type) and the property signature (data type, mutable and collection flags).
• CZ_TYPE_RELATIONSHIPS (SYNONYM) — used three ways: as the numeric/type check (NUMCHK), as the sub-context relationship, and as the property-binding relationship (PRPBIND). It also drives the inline CONVS union that derives conversion bindings and the definite-binding flag.
• CZ_RULETYPECODES_LKV (VIEW) — the rule-type lookup source for the rule type code and label.
• FND_PROFILE (PACKAGE) — referenced by the view text to resolve profile options used in the model/engine compatibility logic.

Foreign-key style joins link signatures to rules on SIGNATURE_ID, and rules to bindings on RULE_ID = OBJECT_TYPE. Outer joins are used for the numeric type check so that rows without a numeric signature still qualify.

Key Columns

• CONTEXT_TYPE_ID / CONTEXT_TYPE_NAME — identifier and name of the context signature (the "context" under which the property applies).
• DEFINITE_BINDING_FLAG — indicates whether the conversion binding is definite (1) or not (0), derived from the CONVS union on REL_TYPE_CODE = 'CNV'.
• PROPERTY_RULE_TYPE_CODE / PROPERTY_RULE_TYPE_LABEL — rule-type code and its display label from CZ_RULETYPECODES_LKV.
• PROPERTY_SEQ_NBR — minimum sequence number of the rule within the context, giving ordering.
• PROPERTY_ID — the rule identifier, returned as a single value only when the aggregated MAX and MIN rule IDs agree; otherwise NULL (the DECODE guard collapses ambiguous multi-rule groups).
• PROPERTY_RULE_TYPE, PROPERTY_NAME, PROPERTY_TOKEN — rule type, name, and template token for the property.
• PROPERTY_DATA_TYPE — data type of the property signature, again NULL-collapsed when a context group contains mixed types.
• PROPERTY_MUTABLE_FLAG, PROPERTY_COLLECTION_FLAG — whether the property is user-mutable and whether it is a collection.
• ALL_NUMERIC_SIGS_FLAG — '1' when every signature in the group is numeric, computed as DECODE(COUNT(NUMCHK.SUBJECT_TYPE), COUNT(*), '1', '0') against the CZ_TYPE_RELATIONSHIPS numeric-check join; otherwise '0'. This is the column targeted by the search term all_numeric_sigs_flag.
• P_MODEL_ID — the development project / model the property set belongs to.

Common Use Cases and Queries

Typical scenarios include auditing which properties are numeric-only within a context, validating engine compatibility of model properties, and extracting property tokens for integration or migration analysis. A basic projection for a known model:

• Filter to numeric-only contexts: SELECT context_type_name, property_name FROM cz_properties_for_context_v WHERE all_numeric_sigs_flag = '1' AND p_model_id = :model_id;
• List mutable, collection properties per context: SELECT context_type_name, property_name, property_data_type FROM cz_properties_for_context_v WHERE property_mutable_flag = 'Y' AND property_collection_flag = 'Y';
• Enumerate definite bindings: SELECT property_name, property_rule_type_label FROM cz_properties_for_context_v WHERE definite_binding_flag = '1';

Because aggregation collapses ambiguous groups to NULL for PROPERTY_ID and PROPERTY_DATA_TYPE, consumers should treat NULL in those columns as "mixed within the context group" rather than "absent." All queries should be qualified by p_model_id where possible to bound result size.