R_PPS_PurOrderHeaderExtension
PPS Fields on Purchase Order Header
R_PPS_PurOrderHeaderExtension is a Basic CDS View that provides data about "PPS Fields on Purchase Order Header" in SAP S/4HANA. It reads from 1 data source (pps_ekko_ext) and exposes 23 fields with key field PurchaseOrder. It has 1 association to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| pps_ekko_ext | pps_ekko_ext | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | R_PurchaseOrder | _PurchaseOrder | $projection.PurchaseOrder = _PurchaseOrder.PurchaseOrder |
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #PRIVILEGED_ONLY | view | |
| EndUserText.label | PPS Fields on Purchase Order Header | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| VDM.lifecycle.contract.type | #SAP_INTERNAL_API | view | |
| VDM.viewType | #BASIC | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.dataClass | #MIXED | view |
Fields (23)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PurchaseOrder | ebeln | ||
| PPSPurchaseOrderDescription | document_description | |||
| PPSPurgDocClassfctnCode | document_confidential | |||
| PPSFuturePostingDate | future_pstng_date | |||
| PPSPerdOfPerfStartDate | pps_perop_beg_hdr | |||
| PPSPerdOfPerfEndDate | pps_perop_end_hdr | |||
| PPSSmartNumberHeader | pps_hdr_smart_number | |||
| PPSSmartDocumentNumber | pps_smart_document_number | |||
| PPSSmartNumberHeaderIsManual | pps_hdr_is_smart_number_manual | |||
| ActivePurchasingDocument | activepo | |||
| PurchasingDocVersionReasonCode | reasoncode | |||
| PPSRevisionComment | version_reason_txt | |||
| PPSNumberOfModification | modificationnumber | |||
| PPSModificationType | modificationtype | |||
| PPSModificationTypeText | modificationtypetext | |||
| PPSModificationIdentifierCode | pps_modification_identifier | |||
| PPSPurOrderHeaderStatus | pps_hdr_status | |||
| PPSFedSystApprvlDate | pubps_apprvl_dte | |||
| PPSFedSystStatus | pubps_apprvl_sts | |||
| PPSFedSystLogHandle | pubps_log_handle | |||
| PurchaseOrderType | _PurchaseOrder | PurchaseOrderType | ||
| PurchasingOrganization | _PurchaseOrder | PurchasingOrganization | ||
| PurchasingGroup | _PurchaseOrder | PurchasingGroup |
@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #PRIVILEGED_ONLY
@EndUserText.label: 'PPS Fields on Purchase Order Header'
@Metadata.ignorePropagatedAnnotations: true
@VDM.lifecycle.contract.type:#SAP_INTERNAL_API // View R_PPS_PURORDERITEMEXTENSION has prefix R_; shall be annotated
@VDM.viewType: #BASIC
@ObjectModel.usageType:{
serviceQuality: #X,
sizeCategory: #S,
dataClass: #MIXED
}
define view entity R_PPS_PurOrderHeaderExtension
as select from pps_ekko_ext
association [1..1] to R_PurchaseOrder as _PurchaseOrder on $projection.PurchaseOrder = _PurchaseOrder.PurchaseOrder // uncommented @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
{
key ebeln as PurchaseOrder,
// smart_number_hdr as SmartNumberHdr,
// milestone_plan_id as MilestonePlanId,
document_description as PPSPurchaseOrderDescription,
document_confidential as PPSPurgDocClassfctnCode,
future_pstng_date as PPSFuturePostingDate,
pps_perop_beg_hdr as PPSPerdOfPerfStartDate,
pps_perop_end_hdr as PPSPerdOfPerfEndDate,
pps_hdr_smart_number as PPSSmartNumberHeader,//@JIRA-KEY<S4PPS-17682>
pps_smart_document_number as PPSSmartDocumentNumber, //@JIRA-KEY<S4PPS-9998>
pps_hdr_is_smart_number_manual as PPSSmartNumberHeaderIsManual, //@JIRA-KEY<S4PPS-10861>@JIRA-KEY<S4PPS-17682>
activepo as ActivePurchasingDocument,
reasoncode as PurchasingDocVersionReasonCode, //PurchasingReasonCode,
version_reason_txt as PPSRevisionComment,
//BOC @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
modificationnumber as PPSNumberOfModification,
modificationtype as PPSModificationType,
modificationtypetext as PPSModificationTypeText,
pps_modification_identifier as PPSModificationIdentifierCode, //@JIRA_KEY<S4PPS-15688
pps_hdr_status as PPSPurOrderHeaderStatus, //@JIRA_KEY<S4PPS-9359
//EOC @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
//BOC @JIRA-KEY <S4PPS-11741> <C5256742>
pubps_apprvl_dte as PPSFedSystApprvlDate,
pubps_apprvl_sts as PPSFedSystStatus,
pubps_log_handle as PPSFedSystLogHandle,
//EOC @JIRA-KEY <S4PPS-11741> <C5256742>
_PurchaseOrder.PurchaseOrderType, // uncommented @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
_PurchaseOrder.PurchasingOrganization, // uncommented @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
_PurchaseOrder.PurchasingGroup // uncommented @JIRA-KEY <S4PPS-7397> <S4PPS-15061> <C5368396>
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"R_PURCHASEORDER",
"PPS_EKKO_EXT"
],
"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