I_PPS_PurContrProcessFlow
PPS Process Flow for Purchase Contract
I_PPS_PurContrProcessFlow is a Composite CDS View that provides data about "PPS Process Flow for Purchase Contract" in SAP S/4HANA. It reads from 3 data sources (I_PurchaseContract, I_PurchaseContract, I_PurchaseContractItem) and exposes 23 fields with key fields PrecedingDocument, PrecedingDocumentItem, SubsequentDocument, SubsequentDocumentItem, PrecedingDocumentItem.
Data Sources (3)
| Source | Alias | Join Type |
|---|---|---|
| I_PurchaseContract | PC | inner |
| I_PurchaseContract | PC | inner |
| I_PurchaseContractItem | PCItem | inner |
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #MANDATORY | view | |
| EndUserText.label | PPS Process Flow for Purchase Contract | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| VDM.lifecycle.contract.type | #SAP_INTERNAL_API | view | |
| VDM.viewType | #COMPOSITE | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #XL | view | |
| ObjectModel.usageType.dataClass | #MIXED | view |
Fields (23)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PrecedingDocument | I_PurchaseContract | ActivePurchasingDocument | |
| KEY | PrecedingDocumentItem | |||
| KEY | SubsequentDocument | |||
| KEY | SubsequentDocumentItem | |||
| PrecedingDocumentCategory | ||||
| SubsequentDocumentCategory | ||||
| PurchaseContract | I_PurchaseContractItem | PurchaseContract | ||
| ActivePurchasingDocument | I_PurchaseContract | ActivePurchasingDocument | ||
| PurchaseContractItem | I_PurchaseContractItem | PurchaseContractItem | ||
| PurchaseContractType | I_PurchaseContractItem | PurchaseContractType | ||
| PurchasingOrganization | I_PurchaseContract | PurchasingOrganization | ||
| PurchaseRequisitionasPrecedingDocument | ||||
| KEY | PrecedingDocumentItem | |||
| KEY | SubsequentDocument | I_PurchaseContract | ActivePurchasingDocument | |
| KEY | SubsequentDocumentItem | |||
| PrecedingDocumentCategory | ||||
| SubsequentDocumentCategory | ||||
| PurchaseContract | I_PurchaseContractItem | PurchaseContract | ||
| ActivePurchasingDocument | I_PurchaseContract | ActivePurchasingDocument | ||
| PurchaseContractItem | I_PurchaseContractItem | PurchaseContractItem | ||
| PurchaseContractType | I_PurchaseContractItem | PurchaseContractType | ||
| PurchasingOrganization | I_PurchaseContract | PurchasingOrganization | ||
| PurchasingGroup | I_PurchaseContract | PurchasingGroup |
//@JIRA_KEY: <S4PPS-7279>
@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #MANDATORY
@EndUserText.label: 'PPS Process Flow for Purchase Contract'
@Metadata.ignorePropagatedAnnotations: true
@VDM.lifecycle.contract.type: #SAP_INTERNAL_API
@VDM.viewType: #COMPOSITE
@ObjectModel.usageType:{
serviceQuality: #D,
sizeCategory: #XL,
dataClass: #MIXED
}
define view entity I_PPS_PurContrProcessFlow
as
//PC
select distinct from I_PurchaseContractItem as PCItem
inner join I_PurchaseContract as PC on PCItem.PurchaseContract = PC.ActivePurchasingDocument //@JIRA-KEY<S4PPS-15594>
{
key PC.ActivePurchasingDocument as PrecedingDocument, //@JIRA-KEY<S4PPS-15594>
key cast( cast (PCItem.PurchaseContractItem as char10 ) as abap.numc (6) ) as PrecedingDocumentItem,
key cast (' ' as vdm_purchaserequisition) as SubsequentDocument,
key cast (' ' as abap.numc (6)) as SubsequentDocumentItem,
cast(cast ('K' as bstyp) as char4) as PrecedingDocumentCategory,
cast (cast (' ' as bstyp) as char4) as SubsequentDocumentCategory,
PCItem.PurchaseContract,
PC.ActivePurchasingDocument as ActivePurchasingDocument,
PCItem.PurchaseContractItem,
PCItem.PurchaseContractType,
PC.PurchasingOrganization,
PC.PurchasingGroup
}
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//PR -> PC
union all select distinct from I_Purchaserequisitionitem as PRItem
//@JIRA-KEY<S4PPS-17802>
inner join I_PurchaseContractItem as PCItem on PRItem.PurchaseRequisition = PCItem.PurchaseRequisition
and PRItem.PurchaseRequisitionItem = PCItem.PurchaseRequisitionItem
inner join I_PurchaseContract as PC on PCItem.PurchaseContract = PC.ActivePurchasingDocument //@JIRA-KEY<S4PPS-15594>
{
key PRItem.PurchaseRequisition as PrecedingDocument,
key cast( cast( PRItem.PurchaseRequisitionItem as char6 )as abap.numc (6) ) as PrecedingDocumentItem,
key PC.ActivePurchasingDocument as SubsequentDocument, //@JIRA-KEY<S4PPS-15594>
key cast( cast( PCItem.PurchaseContractItem as char6 ) as abap.numc (6) ) as SubsequentDocumentItem,
cast(cast ('B' as bstyp) as char4) as PrecedingDocumentCategory,
cast(PCItem.PurchasingObjectCategory as char4) as SubsequentDocumentCategory,
PCItem.PurchaseContract,
PC.ActivePurchasingDocument as ActivePurchasingDocument,
PCItem.PurchaseContractItem,
PCItem.PurchaseContractType,
PC.PurchasingOrganization,
PC.PurchasingGroup
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"I_PURCHASECONTRACT",
"I_PURCHASECONTRACTITEM",
"I_PURCHASEREQUISITIONITEM"
],
"ASSOCIATED":
[],
"BASE":
[],
"ANNO_REF":
[],
"SCALAR_FUNCTION":
[],
"VERSION":0,
"ANNOREF_EVALUATION_ERROR":""
}
}*/
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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