Search Results cz_fce_files_s

Overview

APPS.CZ_FCE_COMPILE is a compiled PL/SQL package body in the Oracle E-Business Suite database, owned by the APPS schema and reported with a VALID status. It belongs to the Oracle Configurator (CZ) product family, which provides the model-based configuration engine used to validate and price configured items across Order Management, Quoting, and iStore. The "FCE" prefix denotes the Feature Compilation Engine, the subsystem responsible for transforming the declarative configuration model — features, option classes, effectivity sets, and rule expressions — into run-time compiled representations that the Configurator can evaluate efficiently.

In EBS 12.1.1 and 12.2.2, the package operates as part of a tightly coupled compilation and validation stack, alongside sibling units such as CZ_FCE_COMPILE_UTILS, CZ_FCE_DATA, and CZ_DEVELOPER_UTILS_PVT. Its central business role is to drive the compilation of model logic so that configuration sessions can be tested, debugged, and executed deterministically. It also exposes a reporting entry point, suggesting it can emit diagnostic output describing compilation state and outcomes.

Key Procedures and Functions

Four documented program units are recorded for this package:

• REPORT — Produces a report of compilation activity or outcomes. This is the only entry point whose name implies a user- or administrator-facing result set, and it is typically the routine surfaced when a model must be inspected after a compile run.
• COMPILE_LOGIC — The principal driver that compiles the configuration logic derived from features, nodes, and rules into a form the run-time engine can consume.
• COMPILE_LOGIC__ — A companion or helper variant of the main compilation routine, conventionally used for an alternate or invoked-differently code path to the primary COMPILE_LOGIC.
• DEBUG_LOGIC — Supports diagnostic tracing of the logic being compiled, assisting developers in isolating model errors during development or troubleshooting.

The presence of a debug routine paired with compilation and reporting routines is characteristic of Configurator developer tooling: the model developer compiles, observes, and corrects, then recompiles.

Tables Accessed

The package reads and writes a broad set of CZ configuration and metadata tables, referenced through APPS synonyms:

• Model structure: CZ_DES_CHART_CELLS, CZ_DES_CHART_FEATURES, CZ_PS_NODES, CZ_PS_PROP_VALS, CZ_EXPRESSION_NODES, CZ_MODEL_REF_EXPLS — the feature/option hierarchy and the Boolean/expression nodes that define configuration logic.
• Rules and effectivity: CZ_EFFECTIVITY_SETS and the rule/entry tables (CZ_RULES, CZ_RP_ENTRIES), which determine when logic is active.
• Items and properties: CZ_ITEM_MASTERS, CZ_ITEM_PROPERTY_VALUES, CZ_ITEM_TYPE_PROPERTIES, CZ_PROPERTIES, CZ_CONVERSION_RELS_V — the item attributes that participate in configuration.
• Files and staging: CZ_FCE_FILES and CZ_FCE_FILES_S — the FCE file tables. This is the object most directly tied to the search term "cz_fce_files_s"; CZ_FCE_FILES is the base table and _S the corresponding sequence-backed surrogate key, used when the compilation engine writes generated FCE output rows.
• Utilities and infrastructure: FND_GLOBAL for session context, DBMS_LOB, DBMS_UTILITY, UTL_RAW, and PLITBLM for character and raw data handling.

Usage Notes

CZ_FCE_COMPILE is not invoked directly by end users. It is called from Configurator model compilation flows in the Configurator Developer and from concurrent programs that validate and compile configuration models, and it is referenced by three other packages in the same subsystem. Custom code and extensions that manipulate CZ_FCE_FILES or CZ_FCE_FILES_S must account for this package's compilation cycle, since the compiler writes FCE file rows through those tables. Because the package is documented as "not referenced by any database object" in ETRM, its dependencies flow outward from it rather than into it from unrelated schemas. Administrators should treat recompilation of this package as a model-affecting operation and revalidate affected configuration models afterward.