A_ComplaintProcessFlow_3
Complaint Process Flow Entity
A_ComplaintProcessFlow_3 is a Consumption CDS View that provides data about "Complaint Process Flow Entity" in SAP S/4HANA. It reads from 1 data source (I_SDDocumentCategoryText) and exposes 7 fields with key fields PrecedingDocument, PrecedingDocumentItem. It has 1 association to related views. It is exposed through 1 OData service (API_CMPLPROCESSFLOWDETAIL_3). Part of development package VDM_CMH_SD.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_SDDocumentCategoryText | _Category | inner |
Parameters (2)
| Name | Type | Default |
|---|---|---|
| P_SubsequentDoc | sddocument | |
| P_SubsequentDocItem | sddocumentitem |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | A_CmplSubsqntProcessFlow | _SubsequentProcFlowDocItem | _SubsequentProcFlowDocItem.PrecedingDocument = $projection.PrecedingDocument and _SubsequentProcFlowDocItem.PrecedingDocumentItem = $projection.PrecedingDocumentItem |
Annotations (12)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Complaint Process Flow Entity | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| ObjectModel.modelingPattern | #NONE | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #XL | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| VDM.lifecycle.contract.type | #PUBLIC_REMOTE_API | view | |
| OData.entitySet.name | ComplaintProcessFlow | view | |
| OData.entityType.name | ComplaintProcessFlow_Type | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| API_CMPLPROCESSFLOWDETAIL_3 |
Fields (7)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PrecedingDocument | _SDDocMultiLevelProcFlow | PrecedingDocument | |
| KEY | PrecedingDocumentItem | _SDDocMultiLevelProcFlow | PrecedingDocumentItem | |
| PrecedingDocumentCategory | _SDDocMultiLevelProcFlow | PrecedingDocumentCategory | ||
| DocumentTypeDescription | I_SDDocumentCategoryText | SDDocumentCategoryName | ||
| PrecedingDocStatus | _ProcessFlowStatus | SubsequentDocStatus | ||
| PrecedingDocStatusDesc | _ProcessFlowStatus | SDProcessStatusDesc | ||
| _SubsequentProcFlowDocItem | _SubsequentProcFlowDocItem |
@EndUserText.label: 'Complaint Process Flow Entity'
@AccessControl.authorizationCheck: #MANDATORY
@ObjectModel: {
modelingPattern: #NONE,
supportedCapabilities: [#TRANSACTIONAL_PROVIDER],
usageType: {
dataClass: #MIXED,
serviceQuality: #C,
sizeCategory: #XL
}
}
@AccessControl.personalData.blocking: #NOT_REQUIRED
@Metadata.ignorePropagatedAnnotations: true
@VDM.viewType: #CONSUMPTION
@VDM.lifecycle.contract.type:#PUBLIC_REMOTE_API
@OData: {
entitySet: { name: 'ComplaintProcessFlow' },
entityType: { name: 'ComplaintProcessFlow_Type' }
}
define view entity A_ComplaintProcessFlow_3
with parameters
P_SubsequentDoc : sddocument,
P_SubsequentDocItem : sddocumentitem
as select distinct from I_SDDocumentMultiLevelProcFlow as _SDDocMultiLevelProcFlow
left outer to one join I_ComplaintProcessFlowStatus as _ProcessFlowStatus on _SDDocMultiLevelProcFlow.PrecedingDocument = _ProcessFlowStatus.SalesDocument
and _SDDocMultiLevelProcFlow.PrecedingDocumentItem = _ProcessFlowStatus.DocumentItemNumber
inner join I_SDDocumentCategoryText as _Category on _SDDocMultiLevelProcFlow.PrecedingDocumentCategory = _Category.SDDocumentCategory
and _Category.Language = $session.system_language
association [0..*] to A_CmplSubsqntProcessFlow as _SubsequentProcFlowDocItem on _SubsequentProcFlowDocItem.PrecedingDocument = $projection.PrecedingDocument
and _SubsequentProcFlowDocItem.PrecedingDocumentItem = $projection.PrecedingDocumentItem
{
key _SDDocMultiLevelProcFlow.PrecedingDocument,
key _SDDocMultiLevelProcFlow.PrecedingDocumentItem,
_SDDocMultiLevelProcFlow.PrecedingDocumentCategory,
_Category.SDDocumentCategoryName as DocumentTypeDescription,
_ProcessFlowStatus.SubsequentDocStatus as PrecedingDocStatus,
_ProcessFlowStatus.SDProcessStatusDesc as PrecedingDocStatusDesc,
_SubsequentProcFlowDocItem
}
where
(
_SDDocMultiLevelProcFlow.SubsequentDocument = $parameters.P_SubsequentDoc
and _SDDocMultiLevelProcFlow.SubsequentDocumentItem = $parameters.P_SubsequentDocItem
and _SDDocMultiLevelProcFlow.PrecedingDocumentCategory = 'C'
)
or(
_SDDocMultiLevelProcFlow.PrecedingDocument = $parameters.P_SubsequentDoc
and _SDDocMultiLevelProcFlow.PrecedingDocumentItem = $parameters.P_SubsequentDocItem
and(
_SDDocMultiLevelProcFlow.PrecedingDocumentCategory = 'H'
or _SDDocMultiLevelProcFlow.PrecedingDocumentCategory = 'K'
or _SDDocMultiLevelProcFlow.PrecedingDocumentCategory = 'L'
)
)
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