Search Results cz_pricing_structures




Overview
Explore in AI Chat

Overview

CZ_PRICING_STRUCTURES is an interface table owned by the CZ schema within the Oracle E-Business Suite Configurator module. Its documented purpose is to serve as the interface table for pricing requests generated during configurator runtime sessions. When a user configures a model or an option class in Oracle Configurator, pricing logic must evaluate the selected components, quantities, units of measure, and pricing attributes. CZ_PRICING_STRUCTURES acts as the staging mechanism through which the Configurator communicates the configured item structure to the pricing engine so that list prices, selling prices, and message data can be returned and applied to the configuration.

From a Data Vault modeling perspective, the mined relationship metadata classifies this table as satellite-leaning. This suggests it is best understood as a descriptive, context-bearing table attached to a parent configuration session entity, rather than as a hub holding durable business keys or a link resolving many-to-many relationships. Its rows are session-scoped and transient by nature, consistent with an interface staging object.

Key Information Stored

The table is documented with twelve columns and two unique indexes. The primary key, CZ_PRICING_STRUCTURES_PK, is a composite surrogate defined over CONFIGURATOR_SESSION_KEY and SEQ_NBR. These two columns together provide the technical row identity. The business-key candidate is captured by CZ_PRICING_STRUCTURES_U1, a unique index over CONFIGURATOR_SESSION_KEY and CONFIG_ITEM_ID, which ties each record to a specific configured item within a session.

  • CONFIGURATOR_SESSION_KEY — identifies the configurator runtime session that owns the pricing request rows.
  • SEQ_NBR — sequence number providing ordering and, with the session key, the composite primary key.
  • CONFIG_ITEM_ID — the configured item identifier; combined with the session key it forms the unique business key.
  • PARENT_CONFIG_ITEM_ID — self-referencing pointer establishing the hierarchical parent-child structure of configured items.
  • PS_NODE_ID — foreign key to CZ_PS_NODES, linking the row to the pricing structure node definition.
  • ITEM_KEY and ITEM_KEY_TYPE — identify the inventory item and the key type used to resolve it.
  • QUANTITY and UOM_CODE — the requested quantity and its unit of measure.
  • LIST_PRICE and SELLING_PRICE — the pricing values returned or requested for the configured item.
  • MSG_DATA — message payload, typically carrying pricing errors, warnings, or informational responses.

Common Use Cases and Queries

The most frequent operational need is diagnosing pricing failures or auditing the pricing requests generated for a given configurator session. A typical query joins the interface rows to their parent pricing structure node and filters by session key:

  • Session inspection: SELECT config_item_id, parent_config_item_id, item_key, quantity, list_price, selling_price FROM cz.cz_pricing_structures WHERE configurator_session_key = :session_key ORDER BY seq_nbr;
  • Error triage: filtering on msg_data IS NOT NULL to isolate rows where pricing returned warnings or errors.
  • Hierarchy reconstruction: walking PARENT_CONFIG_ITEM_ID and CONFIG_ITEM_ID to rebuild the configured bill of materials.
  • Price reconciliation: comparing LIST_PRICE against SELLING_PRICE to validate discount or adjustment behavior.
  • Integration monitoring: counting rows per session to confirm that pricing requests were staged and consumed correctly.

Related Objects

CZ_PRICING_STRUCTURES participates in a small set of documented relationships anchored by its foreign key and unique index definitions:

  • CZ_PS_NODES — referenced through CZ_PRICING_STRUCTURES.PS_NODE_ID; the parent pricing structure node that supplies node-level context for each request row.
  • CZ_PRICING_STRUCTURES_PK — composite primary key over CONFIGURATOR_SESSION_KEY and SEQ_NBR.
  • CZ_PRICING_STRUCTURES_U1 — unique index over CONFIGURATOR_SESSION_KEY and CONFIG_ITEM_ID, enforcing one pricing structure row per configured item per session.
  • Configurator session and configuration tables in the CZ schema that share CONFIGURATOR_SESSION_KEY as the session correlation key.
  • Oracle Pricing (QP) interfaces, which consume the staged pricing requests produced from this table.
  • Configurator runtime APIs that populate and read CZ_PRICING_STRUCTURES during model evaluation.

Because the object is an interface table, its contents should be treated as transient session data rather than persistent master data; reporting should generally target it within the active session window.