C_PriceVarianceQuery
Price Variance
C_PriceVarianceQuery (Consumption)
Package: Explore, extend and adapt the SAP S/4HANA Cloud Private Edition with built-in and side-by-side extension capabilities.
Sourcing & Procurement
C_PriceVarianceQuery is a Consumption CDS View that provides data about "Price Variance" in SAP S/4HANA. It reads from 1 data source (C_PriceVarianceCube) and exposes 44 fields with key field PurchaseOrderItem. It is used in 5 Fiori applications: Supplier Evaluation by Quantity (Version 2), Supplier Evaluation by Price (Version 2), Supplier Evaluation by Time (Version 2), ....
SAP API Hub
| State | C1 |
|---|---|
| Line of Business | Sourcing & Procurement |
| Application Component | MM-PUR-ANA |
| Capabilities | Analytical Query |
| Package | Sourcing & Procurement for SAP S/4HANA Cloud Private Edition |
Documentation
- Analytics with CDS Views — Build Analytics for S/4HANA Cloud Private Edition ABAP CDS views replicated to SAP Cloud Platform
- CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Private Edition Private Edition CDS Views on SAP Business Accelerator Hub
- Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Private Edition and consume them as APIs
- Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
- Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
- SAP Extensibility Explorer for SAP S/4HANA Cloud Private Edition — Explore SAP S/4HANA Cloud Private Edition Extensibility options by leveraging the sample scenarios from SAP
- SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
- VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Private Edition
- View Browser — Search, browse and tag CDS Views
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| C_PriceVarianceCube | C_PriceVarianceCube | from |
Parameters (4)
| Name | Type | Default |
|---|---|---|
| P_DisplayCurrency | displaycurrency | |
| P_StartDate | vdm_validitystart | |
| P_EndDate | vdm_validityend | |
| P_DateFunction | datefunctionid |
Annotations (16)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | CMMSEBYPRICEQRY | view | |
| EndUserText.label | Price Variance | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #PRIVILEGED_ONLY | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| VDM.viewType | #CONSUMPTION | view | |
| OData.publish | true | view | |
| Analytics.settings.maxProcessingEffort | #MEDIUM | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| Analytics.query | true | view | |
| AbapCatalog.preserveKey | true | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_QUERY | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
Fiori Apps (5)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F1661A | Supplier Evaluation by Quantity (Version 2) | Analytical | With the Supplier Evaluation by Quantity app, you can determine the quantity variance, which is based on the variance between the ordered quantity and delivered quantity of items. Both the excess and less delivered quantities are considered. |
| F1663A | Supplier Evaluation by Price (Version 2) | Analytical | With the Supplier Evaluation by Price app, you can determine the score of a given supplier in an organization based on the variance in the price of ordered items and delivered items. The score is calculated over a period of one year and is based on the difference in the purchase order amount and invoice amount. Both the excess and less price are considered as variance. |
| F1664A | Supplier Evaluation by Time (Version 2) | Analytical | You can use this app to determine the score of a given supplier in an organisation based on the difference in time between the ordered date of items and delivered date of items. The score is calculated over a period of 365 days. Both the late and earlier deliveries of items are considered as variance. |
| F2309A | Supplier Evaluation by Quality (Version 2) | Analytical | With the Supplier Evaluation by Quality app, you can determine the scores for given suppliers based on the inspection lot. |
| F3295A | Supplier Evaluation By Quality (for Quality Notification) (Version 2) | Analytical |
Supplier Evaluation by Quantity (Version 2)
Business Role: Strategic Buyer
With the Supplier Evaluation by Quantity app, you can determine the quantity variance, which is based on the variance between the ordered quantity and delivered quantity of items. Both the excess and less delivered quantities are considered. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app. The score is determined over a period of 365 days. The KPI is displayed in the following views: •By Supplier•By Purchasing Group•By Purchasing Organization•By Material Group•Document•Trend
Supplier Evaluation by Price (Version 2)
Business Role: Strategic Buyer
This new app is a replacement for the app , which is planned to be deprecated with SAP S/4HANA Cloud 2102. We recommend that you start using this new app instead of the old app Supplier Evaluation by Quality (Deprecated). SAP Fiori ID for this app is F3295A. You can now view number of purchase orders and number of purchase order items with this app.
Supplier Evaluation by Time (Version 2)
Business Role: Strategic Buyer
You can use this app to determine the score of a given supplier in an organization based on the difference in time between the ordered date of items and delivered date of items. The score is calculated over a period of 365 days. Both the late and earlier deliveries of items are considered as variance. The role Strategic Buyer (SAP_BR_BUYER) is required to access the role. The KPI is displayed in the following views: •By Supplier•By Purchasing Group•By Purchasing Organization•By Material Group•Document•Trend
Supplier Evaluation by Quality (Version 2)
Business Role: Strategic Buyer
This app determines the score of a supplier in an organization based on the weighted average of the quantity, price, and time variances. The score is calculated over a period of 365 days. It combines scores from the weighted hard facts available from the different criteria (price, time, and quantity), and the soft facts available from questionnaire results. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app.
Supplier Evaluation By Quality (for Quality Notification) (Version 2)
Business Role: Strategic Buyer
With this app you can evaluate suppliers based on score that is calculated on the basis of quality complaints received. You can identify the suppliers with less received complaint notifications and thus with higher quality evaluation score. This helps you to determine the suppliers with the best performance and reliability. This app can also help you to decide which supplier to select if the purchasing conditions such as quality and price of material, quotation and delivery time are the same.
Fields (44)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| resultElementDateFunctionStartDate | ||||
| resultElementDateFunctionEndDate | ||||
| P_DisplayCurrency | ||||
| P_StartDate | ||||
| P_EndDatekeyPurchaseOrder | Purchasing Document | |||
| KEY | PurchaseOrderItem | PurchaseOrderItem | Item Number of Purchase Order | |
| PurgDocMigrtnIsCmpltdForAnlyts | PurgDocMigrtnIsCmpltdForAnlyts | Indicator for Data Migration of Schedule Line | ||
| SuplrEvalRelevantDocCategory | SuplrEvalRelevantDocCategory | Supplier Evaluation Configuration for Document Category type | ||
| PurchaseOrderDate | PurchaseOrderDate | Purchase Order Date | ||
| CalendarYear | CalendarYear | Calendar Year | ||
| CalendarQuarter | CalendarQuarter | Calendar Quarter | ||
| CalendarMonth | CalendarMonth | Calendar Month | ||
| CalendarWeek | CalendarWeek | Calendar Week | ||
| PurchasingOrganization | PurchasingOrganization | Purchasing Organization | ||
| PurchasingGroup | PurchasingGroup | Purchasing Group | ||
| CompanyCode | CompanyCode | Receiver Company Code | ||
| Supplier | Supplier | Supplier | ||
| SupplierCountry | SupplierCountry | Supplier Country/Region | ||
| Region | Region | Region (State, Province, County) | ||
| Plant | Plant | Valuation Area | ||
| Material | Material | Material Number | ||
| MaterialGroup | MaterialGroup | Material Group | ||
| PurchasingCategory | PurchasingCategory | Purchasing Category ID | ||
| PurgCatName | PurgCatName | Purchasing Category Name (Deprecated) | ||
| PurchasingDocumentCategory | PurchasingDocumentCategory | Purchasing Document Category | ||
| PurchasingDocumentCategoryName | Purchasing Document Category Name | |||
| Currency | Currency | Valuation Crcy | ||
| PurchaseOrderQuantityUnit | PurchaseOrderQuantityUnit | Purchase Order Unit of Measure | ||
| OrderPriceUnit | OrderPriceUnit | Order Price Unit (Purchasing) | ||
| DisplayCurrency | DisplayCurrency | Display Currency | ||
| PriceVarianceInPct | PriceVarianceInPct | Price Variance in Percentage | ||
| PriceVarianceAmount | PriceVarianceAmount | Price Variance Amt | ||
| PurchaseOrderNetPriceAmount | PurchaseOrderNetPriceAmount | |||
| InvoicePrice | InvoicePrice | |||
| PriceVarianceScore | PriceVarianceScore | Price Variance Score | ||
| NumberOfPurchaseOrders | NumberOfPurchaseOrders | Number of Purchase Orders | ||
| NumberOfPurchaseOrderItems | NumberOfPurchaseOrderItems | Number of Purchase Order Items | ||
| SuplrEvalPriceVarcInPercent | Price Variance in Percentage | |||
| SuplrEvalPriceVarianceAmt | Price Variance Amount | |||
| AmountPerPurchaseOrderPrcUnit | PO price per OPU | |||
| PerInvoicePrcUnitAmount | Invc price per OPU | |||
| DeliveredQuantity | DeliveredQuantity | Delivered Quantity | ||
| OrderedQuantity | OrderedQuantity | Purchase Order Quantity | ||
| PriceVarianceScoreValue | Variance Score |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view C_PriceVarianceQuery.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
-- SQL view name: CMMSEBYPRICEQRY
-- Parameters: P_DisplayCurrency : displaycurrency, P_StartDate : vdm_validitystart, P_EndDate : vdm_validityend, P_DateFunction : datefunctionid
CREATE VIEW C_PriceVarianceQuery AS
SELECT
resultElement: 'DateFunctionStartDate' AS resultElementDateFunctionStartDate,
resultElement: 'DateFunctionEndDate' AS resultElementDateFunctionEndDate,
binding: [ { targetParameter: 'P_DateFunction', type: #PARAMETER, value : 'P_DateFunction' AS P_DisplayCurrency,
P_StartDate : $parameters.P_StartDate AS P_StartDate,
PurchaseOrderItem,
PurgDocMigrtnIsCmpltdForAnlyts,
SuplrEvalRelevantDocCategory,
PurchaseOrderDate,
CalendarYear,
CalendarQuarter,
CalendarMonth,
CalendarWeek,
PurchasingOrganization,
PurchasingGroup,
CompanyCode,
Supplier,
SupplierCountry,
Region,
Plant,
Material,
MaterialGroup,
PurchasingCategory,
PurgCatName,
PurchasingDocumentCategory,
_PurchasingDocumentCatName._Text[1: Language = $session.system_language].PurchasingDocumentCategoryName AS PurchasingDocumentCategoryName,
Currency,
PurchaseOrderQuantityUnit,
OrderPriceUnit,
DisplayCurrency,
PriceVarianceInPct,
PriceVarianceAmount,
PurchaseOrderNetPriceAmount,
InvoicePrice,
PriceVarianceScore,
NumberOfPurchaseOrders,
NumberOfPurchaseOrderItems,
cast( 1 as mm_ana_price_var_pct) AS SuplrEvalPriceVarcInPercent,
cast( 1 as abap.curr(13,3) ) AS SuplrEvalPriceVarianceAmt,
cast( 1 as abap.curr(13,3) ) AS AmountPerPurchaseOrderPrcUnit,
cast( 1 as abap.curr(13,3) ) AS PerInvoicePrcUnitAmount,
DeliveredQuantity,
OrderedQuantity,
cast( 1 as mm_a_variance_score ) AS PriceVarianceScoreValue
FROM C_PriceVarianceCube
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA