Search Results cz_func_comp_specs




Overview
Explore in AI Chat

Overview

The CZ_FUNC_COMP_SPECS table is a core repository within the Oracle E-Business Suite Configurator (CZ) module, present in both releases 12.1.1 and 12.2.2. It stores master definitions for functional companion objects. In the context of Oracle Configurator, a functional companion is a reusable logic component that encapsulates business rules, calculations, or user interface behaviors. This table acts as the central specification hub, defining the essential metadata and relationships for these components, which are then referenced and instantiated within specific configurator models and user interfaces. Its role is critical for maintaining the integrity and reusability of complex configuration logic across the application.

Key Information Stored

The table's primary key is FUNC_COMP_ID, a unique identifier for each functional companion specification. Key foreign key columns establish critical linkages to other Configurator entities. The DEVL_PROJECT_ID column ties the specification to a specific development project in the CZ_DEVL_PROJECTS table, organizing components within the development lifecycle. The COMPONENT_ID links to the CZ_PS_NODES table, connecting the logic specification to its corresponding node in the product structure or model hierarchy. The RULE_FOLDER_ID associates the companion with a specific folder for organizing business rules (CZ_RULE_FOLDERS), while MODEL_REF_EXPL_ID links to explanatory references in the CZ_MODEL_REF_EXPLS table. Together, these columns define what the companion is, where it belongs, and how it integrates into the broader configurator framework.

Common Use Cases and Queries

A primary use case is impact analysis and dependency tracking when modifying or retiring a functional companion. Developers and administrators query this table to understand where a component is used before making changes. Common reporting includes listing all functional companions within a specific development project or identifying companions associated with a particular model component. Sample SQL to retrieve core specifications with descriptive project information is foundational for such audits:

  • SELECT fcs.FUNC_COMP_ID, fcs.COMPONENT_ID, dp.PROJECT_NAME FROM CZ_FUNC_COMP_SPECS fcs JOIN CZ_DEVL_PROJECTS dp ON fcs.DEVL_PROJECT_ID = dp.DEVL_PROJECT_ID WHERE dp.PROJECT_NAME = '&PROJECT_NAME';

Another critical scenario involves troubleshooting configuration runtime behavior by tracing from a UI element back to its underlying logic specification, requiring joins through the CZ_UI_NODES table.

Related Objects

The CZ_FUNC_COMP_SPECS table is central to a network of key Configurator objects, as defined by its documented foreign key relationships. Tables that CZ_FUNC_COMP_SPECS references include:

  • CZ_DEVL_PROJECTS via DEVL_PROJECT_ID
  • CZ_PS_NODES via COMPONENT_ID
  • CZ_RULE_FOLDERS via RULE_FOLDER_ID
  • CZ_MODEL_REF_EXPLS via MODEL_REF_EXPL_ID

Conversely, tables that reference CZ_FUNC_COMP_SPECS, demonstrating its role as a parent specification, are:

  • CZ_FUNC_COMP_REFS via its FUNC_COMP_ID column, which stores references to functional companions from within other model entities.
  • CZ_UI_NODES via its FUNC_COMP_ID column, linking user interface elements directly to the logic defined in this specifications table.

These relationships underscore the table's function as the authoritative source for functional companion definitions, upon which both model logic (CZ_FUNC_COMP_REFS) and the user interface (CZ_UI_NODES) depend.