Results for “cz_expression_nodes_s”

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

Overview

APPS.CZ_PS_COPY is a PL/SQL package body belonging to the Oracle E-Business Suite product family commonly associated with Oracle Configurator and the Oracle Advanced Product Catalog / Designer (CZ schema) data model. Its documented API classification is OTHER, indicating that it is an internal utility package rather than a public or published interface. The package provides cloning and copy functionality for PS (product structure / configuration model) constructs, allowing an existing development project, its node hierarchy, its rules sub-schema, and associated supporting definitions to be duplicated under a target project. This supports scenarios in which a configuration model must be replicated, versioned, or migrated between projects without manual re-entry of every node, rule, and feature.

The package body carries the header identifier czpscpb.pls 120.0, dated 2005/05/25, and declares a package-level global, GLOBAL_ORIG_SYS_REF, typed against CZ_DEVL_PROJECTS.orig_sys_ref. A batch constant BATCH_SIZE of 20000 and a counter numRecords indicate that the copy operations are performed in bounded batches to control resource consumption on large hierarchies. An internal ENCLOSE_FOLDER variable is also declared for folder handling during the copy process. The package exposes six documented procedures and functions in total, and it is not referenced by any other package, confirming its role as a top-level, independently invoked utility. Logging is handled through the autonomous-transaction procedure LOG_REPORT, which writes rows into CZ_DB_LOGS with a fixed status code of 11276 so that diagnostics survive rollback of the main transaction.

Key Procedures and Functions

• PROJECT_COPY — The principal entry point. Orchestrates the duplication of a source development project into a destination project, driving the subordinate copy steps and recording progress through the logging mechanism.
• COPY_PS_NODE_SUBTREE — Copies the hierarchy of product structure nodes beneath a given parent, preserving parent-child relationships and node ordering so that the target model retains the same structural shape as the source.
• COPY_RULES_SUBSCHEMA — Reproduces the rule definitions associated with the copied structure, including the expression and expression-node data that back those rules.
• COPY_FUNC_COMPANION — Copies functional companion specifications and their sequence values, ensuring that companion components referenced by the configuration model remain valid in the target project.
• COPY_RULE_SEQ — Assigns or reproduces sequence numbering for rules so that evaluation order in the target project mirrors the source project.
• TEST — A diagnostic or validation routine used to exercise the package logic without performing a production copy.

The body additionally contains a local Initialize procedure that resets the record counter and registers the sequence names used during copying, including CZ_PS_NODES_S, CZ_FILTER_SETS_S, and CZ_SUB_CON_SETS_S, indicating that surrogate keys for the copied entities are drawn from these database sequences.

Tables Accessed

All tables are referenced through APPS synonyms. The copy operation reads and writes the configuration model tables: CZ_DEVL_PROJECTS (source and target project header), CZ_PS_NODES equivalents via the node copy path, CZ_FILTER_SETS and CZ_SUB_CON_SETS_S for filter and sub-configuration set assignment, CZ_EXPRESSIONS and CZ_EXPRESSION_NODES for rule logic, and CZ_FUNC_COMP_SPECS with CZ_FUNC_COMP_SPECS_S for functional companion definitions. Feature and layout metadata is handled through CZ_COMBO_FEATURES, CZ_DES_CHART_CELLS, CZ_DES_CHART_COLUMNS, CZ_DES_CHART_FEATURES, CZ_GRID_CELLS, CZ_GRID_COLS, and CZ_GRID_DEFS, which carry the design chart and grid presentation of the model. Run-time diagnostics are persisted in CZ_DB_LOGS, and environment parameters are read from CZ_DB_SETTINGS.

Usage Notes

CZ_PS_COPY is not a public API and is not invoked by any other package in the documented dependency set. It is therefore expected to be called either from Oracle Configurator / Designer administrative forms that offer a copy or duplicate action, or from a concurrent program or custom PL/SQL script supplied by a implementation team performing bulk model duplication. Because the procedures operate in batches and the logging routine commits independently, run-time behavior should be monitored through CZ_DB_LOGS when large hierarchies are processed. Implementations should treat the package as internal and re-validate its behavior after any EBS upgrade, particularly between 12.1.1 and 12.2.2 where the underlying CZ schema objects and Online Patching editioning rules may affect direct invocation.