Search Results is_mutex

Overview

APPS.CZ_TYPES is a core PL/SQL package within the Oracle E-Business Suite (EBS) configuration management infrastructure, historically associated with the Oracle Configurator / Configurator Developer (CZ schema) module used to build, validate, and deploy product configuration models. In EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and carries a VALID status, indicating it is compiled and active. Its primary business function is to centralize type-checking and identity-resolution logic for configuration model objects: determining whether a given node, region, or persistent node possesses a particular type, resolving identifiers for user-interface and rule signatures, and answering availability questions about node properties. Because configuration models contain heterogeneous node types (regions, UI elements, property nodes, and persistent nodes), the package provides the canonical runtime predicates and identifier generators that other configuration components rely on to behave consistently.

The package is documented in ETRM with an API classification of OTHER rather than as a public or private API, reflecting that it functions largely as an internal utility layer consumed by other CZ packages and views. It is referenced by 24 other objects, underscoring its central role in the configuration object dependency graph.

Key Procedures and Functions

Documented metadata lists twelve procedures and functions. Their purposes are as follows:

• IS_MUTEX — Determines whether the given configuration object participates in a mutual-exclusion relationship, supporting validation of incompatible selections.
• GET_UI_SIGNATURE_ID — Returns the signature identifier associated with a user-interface element or template, used to track UI definition identity.
• IS_IT_REGION — Boolean predicate testing whether a node represents a region of the specified type.
• GET_PERSISTENT_NODE_ID — Resolves the identifier of a persistent node, bridging transient UI representation with stored configuration data.
• GET_RULE_SIGNATURE_ID — Returns the signature identifier for a configuration rule, supporting rule identity and change tracking.
• NODE_TYPE_AVAILABLE — Indicates whether a particular node type is available for the current model context.
• NODE_USER_PROPS_AVAILABLE — Determines whether user-defined properties are available for a node.
• NODE_CAPTION_PROPS_AVAILABLE — Determines whether caption properties are available for a node, affecting display rendering.
• GET_PS_NODE_TYPE — Returns the type of a persistent node, supporting type-directed processing.

The remaining documented entries complete the twelve-item list and follow the same predicate/identifier pattern. Parameter lists are not published in the metadata and should not be assumed.

Tables Accessed

Per documented metadata, the package references three objects via APPS synonyms:

• CZ_DEVL_PROJECTS — The Configurator Developer project header, supplying project context for type-availability checks.
• CZ_PS_NODES — The persistent node table, read to resolve node types and persistent node identifiers.
• DUAL — Used for singleton computations and constant evaluation.

Usage Notes

CZ_TYPES is invoked indirectly rather than through end-user screens. It is referenced by numerous CZ views (for example CZ_EXPLNODES_VALUES_EFF_CV, CZ_NODES_FOR_UIELEMS_EFF_CV, CZ_UI_TYPEDPSN_V) and by packages such as CZ_IMP_SINGLE, CZ_MODEL_CONVERT, CZ_MODEL_UTIL_PVT, CZ_POPULATORS_PKG, and CZ_UIOA_PVT. These consumers call CZ_TYPES during model import, conversion, UI generation, and rule evaluation, typically as part of Configurator Developer operations and runtime configuration. Custom code should treat it as an internal dependency and avoid direct invocation; upgrades between 12.1.1 and 12.2.2 should be validated for signature compatibility.