Search Results okx_config_pricing_v

Overview

OKX_CONFIG_PRICING_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product family. Its documented description is "Configurator Pricing." The view exposes pricing output generated by the Oracle Configurator pricing engine, making that data available to contract-oriented processes and to downstream reporting without requiring direct access to the underlying Configurator tables.

In Oracle EBS 12.1.1 and 12.2.2, the view carries a VALID status in the APPS schema, indicating that it compiles successfully against its base object and is safe for use in custom reports, concurrent programs, and interface logic. The object name follows the standard EBS convention in which the OKX prefix designates the Contracts Integration module. Because the view is a thin projection over a single Configurator table, its principal value is standardization: it presents a stable, named interface that insulates consumers from the physical layout of the Configurator pricing schema.

Note that "december 2025 pricing configurator V7.xlsx" is a spreadsheet artifact and is not an Oracle EBS object. Users searching that term are typically attempting to locate the underlying data that feeds such a workbook; OKX_CONFIG_PRICING_V is a plausible source when pricing is extracted from Configurator sessions and reconciled against contracts.

Underlying Base Objects

The view is defined over a single referenced base object, CZ_PRICING_STRUCTURES, accessed through a synonym. The documented view text is a simple projection with no joins, aggregations, or filters:

• SELECT CONFIGURATOR_SESSION_KEY, PS_NODE_ID, ITEM_KEY, ITEM_KEY_TYPE, QUANTITY, UOM_CODE, LIST_PRICE, SELLING_PRICE, MSG_DATA, SEQ_NBR FROM CZ_PRICING_STRUCTURES B

Because there is no WHERE clause, every row present in CZ_PRICING_STRUCTURES is returned. CZ_PRICING_STRUCTURES is an Oracle Configurator table that stores the flattened pricing structure for a configuration session, with one row per priced node. The alias "B" in the view text is a residue of an earlier, more complex definition but has no functional effect in the delivered projection.

Key Columns

• CONFIGURATOR_SESSION_KEY — Identifier of the Configurator session that produced the pricing row; the primary grouping key for reconciliation.
• PS_NODE_ID — The pricing structure node identifier, linking the row to a specific node in the configuration hierarchy.
• ITEM_KEY — The configured item or option identifier the node represents.
• ITEM_KEY_TYPE — Qualifies ITEM_KEY, distinguishing the type of key supplied (for example inventory item versus option class).
• QUANTITY — Quantity priced for the node in the session.
• UOM_CODE — Unit of measure associated with the quantity.
• LIST_PRICE — List price of the item or option at the time of configuration.
• SELLING_PRICE — Price after applicable modifiers, discounts, and adjustments.
• MSG_DATA — Message or diagnostic payload generated during pricing evaluation.
• SEQ_NBR — Sequence number controlling row ordering within the structure.

Common Use Cases and Queries

Typical uses include auditing configured pricing before contract creation in OKX, reconciling EBS pricing output against external workbooks or quotations, and extracting session-level price detail for reporting.

• Retrieve all pricing rows for a session, ordered by structure sequence:
• SELECT configurator_session_key, ps_node_id, item_key, quantity, uom_code, selling_price FROM apps.okx_config_pricing_v WHERE configurator_session_key = :session_key ORDER BY seq_nbr;
• Compare list and selling price to quantify discounting:
• SELECT item_key, list_price, selling_price, (list_price - selling_price) discount_amount FROM apps.okx_config_pricing_v WHERE configurator_session_key = :session_key;
• Review diagnostic messages emitted during pricing:
• SELECT ps_node_id, item_key, msg_data FROM apps.okx_config_pricing_v WHERE msg_data IS NOT NULL;

Always qualify the view as APPS.OKX_CONFIG_PRICING_V and grant select privileges through a custom responsibility rather than querying CZ_PRICING_STRUCTURES directly, preserving the supported interface boundary.