C_PurOrdValueWithPlnd
Purchase Order Value with Planned Spend
C_PurOrdValueWithPlnd is a Consumption CDS View that provides data about "Purchase Order Value with Planned Spend" in SAP S/4HANA. It reads from 3 data sources (P_UNSGNDMATGRPTXT, P_PurgCatPlndSpndItems, I_PurchasingCategoryMatlGroup). It has 11 associations to related views. It is used in 4 Fiori applications: Unused Contracts, Invoice Price Variance, Purchase Order Value and Scheduling Agreement Value, ....
Data Sources (3)
| Source | Alias | Join Type |
|---|---|---|
| P_UNSGNDMATGRPTXT | _Doc | left_outer |
| P_PurgCatPlndSpndItems | P_PurgCatPlndSpndItems | left_outer |
| I_PurchasingCategoryMatlGroup | PurchasingCategoryMatlGroup | left_outer |
Parameters (3)
| Name | Type | Default |
|---|---|---|
| P_DisplayCurrency | displaycurrency | |
| P_Language | sylangu | |
| P_DateFunction | datefunctionid |
Associations (11)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | C_MM_MaterialGroupValueHelp | _MaterialGroup | $projection.MaterialGroup = _MaterialGroup.MaterialGroup |
| [0..1] | C_MM_SupplierValueHelp | _Supplier | $projection.Supplier = _Supplier.Supplier and $projection.CompanyCode = _Supplier.CompanyCode |
| [1..1] | C_MM_MaterialValueHelp | _Material | $projection.Material = _Material.Material and $projection.Plant = _Material.Plant |
| [0..1] | C_PurchasingGroupValueHelp | _PurchasingGroup | $projection.PurchasingGroup = _PurchasingGroup.PurchasingGroup |
| [0..1] | C_PurchasingOrgValueHelp | _PurchasingOrganization | $projection.PurchasingOrganization = _PurchasingOrganization.PurchasingOrganization |
| [1..1] | I_Plant | _Plant | $projection.Plant = _Plant.Plant |
| [1..1] | I_PurchasingDocumentType | _PurchasingDocumentType | $projection.PurchasingDocumentType = _PurchasingDocumentType.PurchasingDocumentType and $projection.PurchasingDocumentCategory = _PurchasingDocumentType.PurchasingDocumentCategory |
| [1..1] | I_PurgDocumentItemCategory | _PurgDocumentItemCategory | $projection.PurchaseOrderItemCategory = _PurgDocumentItemCategory.PurchasingDocumentItemCategory |
| [1..1] | I_PurchasingDocumentCategory | _PurchasingDocumentCategory | $projection.PurchasingDocumentCategory = _PurchasingDocumentCategory.PurchasingDocumentCategory |
| [1..1] | I_CompanyCode | _CompanyCode | ActualSpend.CompanyCode = _CompanyCode.CompanyCode |
| [1..1] | I_CompanyCode | _ReceivingCompanyCode | $projection.ReceivingCompanyCode = _ReceivingCompanyCode.CompanyCode |
Annotations (11)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | CPOVALPLNDVSACTL | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| EndUserText.label | Purchase Order Value with Planned Spend | view | |
| VDM.viewType | #CONSUMPTION | view | |
| OData.publish | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #L | view |
Fiori Apps (4)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F0575 | Unused Contracts | Analytical | You use this app to identify the number of contracts not used within the last 365 days, from the current date. You can also find the target and released amount of the unused contracts. From 1809 release onward this app has been enhanced to consider/include central purchase contracts also |
| F0682 | Invoice Price Variance | Analytical | This KPI determines the trend in which invoice price varies over a period of 12 months and is calculated monthly. This is a trend tile, based on the key performance indicator, weighted material price. |
| F1378 | Purchase Order Value and Scheduling Agreement Value | Analytical | You can use this app to retrieve the order value for all the purchase orders over time. The app also helps to determine the KPI value of the purchase orders for a given set of filter criteria such as the materials, supplier, and plant. The business value of the app is that you can determine all the current value of all purchase orders in the system. |
| F1380 | Purchase Order Average Delivery Time | Analytical | You can use this app to check the average delivery time of orders to the suppliers. |
Unused Contracts
Business Role: Strategic Buyer
You use this app to identify the number of contracts not used within the last 365 days, from the current date. You can also find the target and released amount of the unused contracts. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app. The KPI is displayed in the following views: •By Supplier•By Purchasing Group•By Purchasing Organization•Document
Invoice Price Variance
Business Role: Strategic Buyer
This KPI determines the trend in which invoice price varies over a period of 12 months and is calculated monthly. This is a trend tile, based on the key performance indicator, weighted material price. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app. The KPI is displayed in the following views: •By Supplier•By Material Group•By Purchasing Category•By Purchasing Group•Document•Trend
Purchase Order Value and Scheduling Agreement Value
Business Role: Strategic Buyer
You can use this app to retrieve the order value for all the purchase orders within a stipulated time. The app also helps to determine the KPI value of the purchase orders for a given set of filter criteria such as the materials, supplier, and plant. The business value of the app is that you can determine all the current value of all purchase orders in the system. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app. This KPI is displayed in the following views: •By Supplier•By Purchasing Category•By Material Group•By Purchasing Group•By Plant•By WBS Element•Document•Trend
Purchase Order Average Delivery Time
Business Role: Strategic Buyer
Using the Purchase Order Average Delivery Time Weighted app, you can check the average delivery time of orders to the suppliers. The role Strategic Buyer (SAP_BR_BUYER) is required to access the app. The app is displayed in the following views: •By Supplier•By Material Group•By Plant•By Purchasing Category•Document
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_PurOrdValueWithPlnd.
-- 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: CPOVALPLNDVSACTL
-- Parameters: P_DisplayCurrency : displaycurrency, P_Language : sylangu, P_DateFunction : datefunctionid
CREATE VIEW C_PurOrdValueWithPlnd AS
SELECT * -- field list not available in parsed metadata
LEFT OUTER JOIN I_PurchasingCategoryMatlGroup AS PurchasingCategoryMatlGroup ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN P_UNSGNDMATGRPTXT AS _Doc ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN P_PurgCatPlndSpndItems ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN C_MM_MaterialGroupValueHelp AS _MaterialGroup ON MaterialGroup = _MaterialGroup.MaterialGroup -- association [1..1]
LEFT OUTER JOIN C_MM_SupplierValueHelp AS _Supplier ON Supplier = _Supplier.Supplier AND CompanyCode = _Supplier.CompanyCode -- association [0..1]
LEFT OUTER JOIN C_MM_MaterialValueHelp AS _Material ON Material = _Material.Material AND Plant = _Material.Plant -- association [1..1]
LEFT OUTER JOIN C_PurchasingGroupValueHelp AS _PurchasingGroup ON PurchasingGroup = _PurchasingGroup.PurchasingGroup -- association [0..1]
LEFT OUTER JOIN C_PurchasingOrgValueHelp AS _PurchasingOrganization ON PurchasingOrganization = _PurchasingOrganization.PurchasingOrganization -- association [0..1]
LEFT OUTER JOIN I_Plant AS _Plant ON Plant = _Plant.Plant -- association [1..1]
LEFT OUTER JOIN I_PurchasingDocumentType AS _PurchasingDocumentType ON PurchasingDocumentType = _PurchasingDocumentType.PurchasingDocumentType AND PurchasingDocumentCategory = _PurchasingDocumentType.PurchasingDocumentCategory -- association [1..1]
LEFT OUTER JOIN I_PurgDocumentItemCategory AS _PurgDocumentItemCategory ON PurchaseOrderItemCategory = _PurgDocumentItemCategory.PurchasingDocumentItemCategory -- association [1..1]
LEFT OUTER JOIN I_PurchasingDocumentCategory AS _PurchasingDocumentCategory ON PurchasingDocumentCategory = _PurchasingDocumentCategory.PurchasingDocumentCategory -- association [1..1]
LEFT OUTER JOIN I_CompanyCode AS _CompanyCode ON ActualSpend.CompanyCode = _CompanyCode.CompanyCode -- association [1..1]
LEFT OUTER JOIN I_CompanyCode AS _ReceivingCompanyCode ON ReceivingCompanyCode = _ReceivingCompanyCode.CompanyCode -- association [1..1]
;
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