Search Results convert_fc_by_model




Overview
Explore in AI Chat

Overview

APPS.CZ_CX_UTIL_PVT is a private PL/SQL utility package belonging to the Oracle Configurator (CZ) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is the migration and transformation of legacy functional companion rule data into the record structures used by Configurator extension rules. The package header identifies the transformation of "old functional companions to configurator extension rule recs," providing a bridge between pre-existing configuration model definitions and the extension rule framework exposed through the Configurator user interface.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking session rather than the package owner. The header carries a version marker of 115.0, dated 2003, indicating the code originated during the earlier Configurator release cycle and was carried forward into the 12.x code lines. As a private (PVT) API, it is not intended for direct customer invocation; it is consumed internally by Oracle Configurator migration logic.

Key Procedures and Functions

The package exposes a single documented procedure:

  • CONVERT_FC_BY_MODEL — Transforms legacy functional companion records associated with a given configuration model into Configurator extension rule records. The procedure accepts a model identifier and a deep migration flag as inputs, and returns a count of functional companions processed together with a return status and message data. A return status of 1 indicates successful conversion; 0 indicates failure. The procedure performs the conversion of rules but, as documented in the header comment, does not create event bindings for the newly transformed extension rules. Those bindings must be established separately by the calling process.

No other procedures or functions are documented for this package in the 12.2.2 metadata.

Tables Accessed

The procedure operates across the core Configurator data model. The referenced tables, accessed through APPS synonyms, fall into several functional groups:

  • Rule and rule storage — CZ_RULES, CZ_RULES_S, and CZ_RULE_FOLDERS hold the extension rule definitions and their folder organization into which converted records are written.
  • Functional companion sources — CZ_FUNC_COMP_SPECS and CZ_MODEL_REF_EXPLS contain the legacy functional companion specifications and model reference explanations being read and transformed.
  • Runtime and reference data — CZ_RP_ENTRIES and CZ_DB_SETTINGS supply runtime profile entries and database-level configuration settings that govern conversion behavior.
  • User interface definitions — CZ_UI_DEFS, CZ_UI_NODES, and CZ_UI_NODE_PROPS describe UI definitions, nodes, and node properties required to associate converted rules with their presentation structures.
  • Infrastructure — DUAL is used for singleton queries, and PLITBLM is the standard PL/SQL index-by table used for bulk processing and messaging.

Collectively, these tables confirm that the procedure reads legacy companion definitions, resolves associated model and UI context, and inserts corresponding extension rule records.

Usage Notes

CZ_CX_UTIL_PVT is invoked as part of the Configurator migration and setup lifecycle, typically when an existing configuration model containing legacy functional companions must be upgraded to use extension rules. Because it is a private API, calls originate from Oracle-supplied code — migration scripts, concurrent programs, or other Configurator packages — rather than from customer extensions. The metadata records no inbound references from other packages, reinforcing its role as a terminal utility called from higher-level migration drivers.

Administrators encountering the procedure during upgrade diagnostics should note two operational characteristics. First, the deep migration flag controls conversion scope; shallow and deep migrations produce different volumes of processed records as reported in the output count parameter. Second, event bindings are deliberately excluded from this procedure. Any migration routine that invokes CONVERT_FC_BY_MODEL must subsequently create the required event bindings, or converted rules will exist without the triggers needed to execute them at runtime. Custom code should not call this procedure directly in 12.1.1 or 12.2.2, as its behavior is tied to internal migration sequencing and is not covered by Oracle's public API support policy.