I_PurchaseOrderNoteTP
Notes for Purchase Order
I_PurchaseOrderNoteTP is a Transactional CDS View that provides data about "Notes for Purchase Order" in SAP S/4HANA. It reads from 1 data source (R_PurchaseOrderNote) and exposes 12 fields with key fields Language, DocumentText, TechnicalObjectType, ArchObjectNumber, PurchaseOrder. It has 1 association to related views. Part of development package APPL_MM_PUR_PO_AI.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_PurchaseOrderNote | Document | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_PurchaseOrderTP | _PurchaseOrder | _PurchaseOrder.PurchaseOrder = $projection.PurchaseOrder |
Annotations (16)
| Name | Value | Level | Field |
|---|---|---|---|
| VDM.viewType | #TRANSACTIONAL | view | |
| AbapCatalog.sqlViewName | IPURORDNOTE | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| EndUserText.label | Notes for Purchase Order | view | |
| VDM.lifecycle.contract.type | #SAP_INTERNAL_API | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.draftEnabled | true | view | |
| ObjectModel.createEnabled | true | view | |
| ObjectModel.updateEnabled | true | view | |
| ObjectModel.deleteEnabled | true | view | |
| ObjectModel.writeDraftPersistence | PURORDNOTE_D | view |
Fields (12)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | Language | R_PurchaseOrderNote | Language | |
| KEY | DocumentText | R_PurchaseOrderNote | DocumentText | |
| KEY | TechnicalObjectType | R_PurchaseOrderNote | TechnicalObjectType | |
| KEY | ArchObjectNumber | R_PurchaseOrderNote | ArchitecturalObjectNumber | |
| KEY | PurchaseOrder | R_PurchaseOrderNote | PurchaseOrder | |
| ArchObjectNumberForEdit | R_PurchaseOrderNote | ArchitecturalObjectNumber | ||
| TechnicalObjectTypeForEdit | R_PurchaseOrderNote | TechnicalObjectType | ||
| DocumentTextForEdit | R_PurchaseOrderNote | DocumentText | ||
| LanguageForEdit | R_PurchaseOrderNote | Language | ||
| NoteDescription | R_PurchaseOrderNote | NoteDescription | ||
| FixedIndicator | R_PurchaseOrderNote | FixedIndicator | ||
| _PurchaseOrder | _PurchaseOrder |
@VDM.viewType: #TRANSACTIONAL
@AbapCatalog.sqlViewName: 'IPURORDNOTE'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Notes for Purchase Order'
@VDM.lifecycle.contract.type: #SAP_INTERNAL_API
@ObjectModel.usageType.serviceQuality: #C
@ObjectModel.usageType.sizeCategory: #L
@ObjectModel.usageType.dataClass: #TRANSACTIONAL
//@ObjectModel.entityChangeStateId: 'LastChangeDateTime'
@AccessControl.personalData.blocking: #NOT_REQUIRED
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.draftEnabled:true
@ObjectModel.createEnabled: true
@ObjectModel.updateEnabled: true
@ObjectModel.deleteEnabled: true
@ObjectModel.semanticKey: ['PurchaseOrder', 'ArchObjectNumberForEdit']
@ObjectModel.writeDraftPersistence: 'PURORDNOTE_D'
//@ObjectModel.dataCategory: #TEXT
define view I_PurchaseOrderNoteTP as select from R_PurchaseOrderNote as Document
association [1..1] to I_PurchaseOrderTP as _PurchaseOrder on _PurchaseOrder.PurchaseOrder = $projection.PurchaseOrder
{
key Document.Language,
key Document.DocumentText,
key Document.TechnicalObjectType,
key Document.ArchitecturalObjectNumber as ArchObjectNumber,
key Document.PurchaseOrder,
Document.ArchitecturalObjectNumber as ArchObjectNumberForEdit,
Document.TechnicalObjectType as TechnicalObjectTypeForEdit,
Document.DocumentText as DocumentTextForEdit,
Document.Language as LanguageForEdit,
Document.NoteDescription,
Document.FixedIndicator,
@ObjectModel.association.type: [ #TO_COMPOSITION_PARENT, #TO_COMPOSITION_ROOT ]
_PurchaseOrder
}
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