I_ProcurementProjectTP
Procurement Project - TP
I_ProcurementProjectTP is a Transactional CDS View that provides data about "Procurement Project - TP" in SAP S/4HANA. It reads from 1 data source (R_ProcurementProjectTP) and exposes 14 fields with key field ProcurementProjectUUID.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_ProcurementProjectTP | R_ProcurementProjectTP | projection |
Annotations (17)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #MANDATORY | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| ObjectModel.representativeKey | ProcurementProjectUUID | view | |
| ObjectModel.sapObjectNodeType.name | ProcurementProject | view | |
| ObjectModel.modelingPattern | #TRANSACTIONAL_INTERFACE | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.serviceQuality | #B | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| VDM.viewType | #TRANSACTIONAL | view | |
| VDM.lifecycle.contract.type | #PUBLIC_LOCAL_API | view | |
| EndUserText.label | Procurement Project - TP | view | |
| AbapCatalog.extensibility.extensible | true | view | |
| AbapCatalog.extensibility.allowNewDatasources | false | view | |
| AbapCatalog.extensibility.elementSuffix | PPJ | view | |
| AbapCatalog.extensibility.quota.maximumFields | 204 | view | |
| AbapCatalog.extensibility.quota.maximumBytes | 4080 | view | |
| AbapCatalog.extensibility.allowNewCompositions | true | view |
Fields (14)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | ProcurementProjectUUID | ProcurementProjectUUID | ||
| ProcurementProject | ProcurementProject | |||
| ProcurementProjectName | ProcurementProjectName | |||
| ExternalProjectReference | ExternalProjectReference | |||
| CompanyCode | CompanyCode | |||
| LastChangedByUser | LastChangedByUser | |||
| CreatedByUser | CreatedByUser | |||
| LastChangeDateTime | LastChangeDateTime | |||
| CreationDateTime | CreationDateTime | |||
| ProcurementProjectActvtnSts | ProcurementProjectActvtnSts | |||
| SourcingOrigin | SourcingOrigin | |||
| SourcingScenario | SourcingScenario | |||
| ProcmtPlanningSubprojectUUID | ProcmtPlanningSubprojectUUID | |||
| IsEndOfPurposeBlocked | IsEndOfPurposeBlocked |
@AccessControl.authorizationCheck: #MANDATORY
@Metadata.ignorePropagatedAnnotations:true
@ObjectModel:{representativeKey: 'ProcurementProjectUUID',
semanticKey: ['ProcurementProject'],
sapObjectNodeType.name: 'ProcurementProject',
modelingPattern: #TRANSACTIONAL_INTERFACE,
supportedCapabilities: [#TRANSACTIONAL_PROVIDER],
usageType: {
dataClass: #TRANSACTIONAL,
serviceQuality: #B,
sizeCategory: #L
}
}
@VDM:{
viewType: #TRANSACTIONAL,
lifecycle.contract.type: #PUBLIC_LOCAL_API
}
@EndUserText.label: 'Procurement Project - TP'
@AbapCatalog.extensibility: {
extensible: true,
dataSources: ['ProcurementProjectTP'],
allowNewDatasources: false,
elementSuffix: 'PPJ',
quota: { maximumFields: 204,
maximumBytes: 4080 },
allowNewCompositions: true }
define root view entity I_ProcurementProjectTP
provider contract transactional_interface
as projection on R_ProcurementProjectTP as ProcurementProjectTP
{
key ProcurementProjectUUID,
ProcurementProject,
ProcurementProjectName,
ExternalProjectReference,
CompanyCode,
LastChangedByUser,
CreatedByUser,
LastChangeDateTime,
CreationDateTime,
ProcurementProjectActvtnSts,
SourcingOrigin,
SourcingScenario,
ProcmtPlanningSubprojectUUID,
@Semantics.booleanIndicator: true
IsEndOfPurposeBlocked,
/* Compositions */
_ProcurementProjectPlant : redirected to composition child I_ProcurementProjectPlantTP
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"R_PROCUREMENTPROJECTTP"
],
"ASSOCIATED":
[
"I_PROCUREMENTPROJECTPLANTTP",
"R_PROCUREMENTPROJECTPLANTTP"
],
"BASE":
[
"R_PROCUREMENTPROJECTTP"
],
"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