Search Results ps_node

Overview

APPS.CZ_POPULATORS_PKG is a VALID package body in the Oracle E-Business Suite APPS schema that belongs to the Oracle Configurator (CZ) product family. Its central responsibility is the management of "populators" — configurable logic units that populate selections, properties, or defaults into a configuration model during runtime configuration of a model or item. The package operates on the intersection of the Configurator runtime engine and the Configurator developer-time model repository, and it forms part of the mechanism by which Oracle Configurator resolves and materializes nodes, expressions, and text values within a configuration session. In EBS 12.1.1 and 12.2.2, the CZ schema objects are owned by APPS, and this package is invoked through APPS synonyms. Its dependency list shows direct references to the model repository tables (CZ_POPULATORS, CZ_PS_NODES, CZ_IMP_PS_NODES, CZ_EXPRESSIONS, CZ_MODEL_REF_EXPLS), to multilanguage text tables (CZ_INTL_TEXTS, CZ_LOCALIZED_TEXTS), and to Oracle Application Object Library APIs (FND_API, FND_MSG_PUB), indicating that it participates in runtime configuration flows and returns API-style status and message information. The classification recorded in the ETRM metadata is OTHER, meaning it is an internal supporting package rather than a published, externally callable API.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions in the package body. Parameter lists should be confirmed against the actual source in the target instance, as they are not reproduced in the metadata.

• REGENERATE — Regenerates compiled or stored population logic for a populator. This is the mechanism used after a populator definition, its expressions, or its associated nodes are changed, so that the persisted runtime representation is brought back into sync with the developer-time definition.
• PREVIEW — Produces a preview of the result of applying a populator, without committing the result to the configuration. This supports developer-time verification of populator behavior.
• EXECUTE — Performs the actual runtime execution of a populator against a configuration instance, reading expressions and node definitions and applying resulting values.
• REPOPULATE — Reapplies the populator's values to an existing configuration, typically to refresh values after an upstream change or a model update.

Together these four entry points cover the lifecycle of a populator: define, verify, run, and re-sync. The package also depends on CZ_SECURITY_PVT, CZ_UTILS, and CZ_TYPES, which supply security checks, utility routines, and shared PL/SQL types respectively.

Tables Accessed

The package accesses model repository and runtime tables through APPS synonyms. CZ_POPULATORS holds the populator definitions, and CZ_POPULATORS_PKG itself appears in the dependency list as a self-reference, consistent with recursive or helper calls within the package. CZ_PS_NODES, CZ_PS_NODES_S, CZ_IMP_PS_NODES, and CZ_IMP_PS_NODE hold the model structure and import-time node representations consumed by execution. CZ_EXPRESSIONS and CZ_EXPRESSION_NODES provide the expression trees evaluated by the populator, while CZ_MODEL_REF_EXPLS links model references to those expressions. CZ_ITEM_MASTERS and CZ_ITEM_TYPES supply the item definitions being configured. CZ_FILTER_SETS, CZ_PROPERTIES, and CZ_DB_SETTINGS provide filtering, property, and runtime setting data. Text labels and translations are read from CZ_INTL_TEXTS, CZ_INTL_TEXTS_S, and CZ_LOCALIZED_TEXTS. Developer project and run context data are read from CZ_DEVL_PROJECTS and CZ_XFR_RUN_INFOS_S, and CZ_DB_LOGS is used for logging or diagnostic output. The package also uses DBMS_SQL, indicating dynamic SQL construction in at least one path.

Usage Notes

CZ_POPULATORS_PKG is not a public integration API. It is invoked indirectly by Oracle Configurator runtime and developer-time components, and the metadata records that it is referenced by two other packages. In 12.1.1 and 12.2.2 the standard usage path is through the Configurator runtime engine, which calls EXECUTE and REPOPULATE as a configuration is built or refreshed, and through Configurator developer flows that call REGENERATE and PREVIEW when a populator definition is edited. Because it uses FND_API and FND_MSG_PUB, callers should expect an API-style return status plus a message stack rather than only a PL/SQL exception on failure.

Customizations that call this package directly should be treated as unsupported, since its procedures are internal and their signatures are not documented here or guaranteed across patches. Custom code that requires populator behavior should instead use the supported Oracle Configurator APIs and concurrent programs, and any dependency on the underlying tables listed above should be reviewed against each patch level of 12.1.1 and 12.2.2.