What is I_SalesOrderItmSubsqntProcFlow in SAP S/4HANA?

I_SalesOrderItmSubsqntProcFlow is a composite CDS view in SAP S/4HANA. Subsequent Process Flow of Sls Ordr Item It contains 19 fields.

Which tables does I_SalesOrderItmSubsqntProcFlow read from?

I_SalesOrderItmSubsqntProcFlow reads data from: I_SalesDocItmSubsqntProcFlow.

What VDM layer is I_SalesOrderItmSubsqntProcFlow?

I_SalesOrderItmSubsqntProcFlow is classified as a Composite view that combines data from multiple basic views.

I_SalesOrderItmSubsqntProcFlow

DDL: I_SALESORDERITMSUBSQNTPROCFLOW Type: view_entity COMPOSITE

19 Fields 1 Data Sources 2 Associations 1 OData Services 1 Fiori Apps

Subsequent Process Flow of Sls Ordr Item

I_SalesOrderItmSubsqntProcFlow (Composite)

Package: Explore, extend and adapt the SAP S/4HANA Cloud Private Edition with built-in and side-by-side extension capabilities.

Sales

I_SalesOrderItmSubsqntProcFlow is a Composite CDS View that provides data about "Subsequent Process Flow of Sls Ordr Item" in SAP S/4HANA. It reads from 1 data source (I_SalesDocItmSubsqntProcFlow) and exposes 19 fields with key fields SalesOrder, SalesOrderItem, DocRelationshipUUID. It has 2 associations to related views. It is exposed through 1 OData service (UI_RFM_STORE_HANDOVERORDER). It is used in 1 Fiori application: Hand Over Orders.

SAP Help Documentation

Category	Sales Orders

Purpose
This CDS view provides the prerequisites for answering questions about the subsequent items of a sales order item (that is, the process flow). Example business questions could include: Which subsequent items does my sales order item have? What's the document category of the subsequent item of my sales order item? Which process flow level is this subsequent document on? The process flow level describes the degree of separation between a document and its subsequent documents. For example, for a delivery document (which is the direct successor of a sales order), the value would be 00 . For a billing document, the value would be 01 . When was the subsequent item created? To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .

Prerequisites
Authorizations You have authorizations to access the relevant sales order types. You have authorizations to access the relevant sales areas.

Structure
Further important fields Important fields in this view include the following: Field Name Description SubsequentDocumentCategory Category of the subsequent document SubsequentDocument ID of the subsequent document SubsequentDocumentItem Number of the subsequent item ProcessFlowLevel Process flow level of the subsequent document

View on SAP Help Portal →

SAP API Hub

State	C1
Line of Business	Sales
Application Component	SD-SLS-SO
Capabilities	Data Source in SQL Select, Association Target for Defining CDS Entities, Data Source for Defining CDS Entities
Package	Sales for SAP S/4HANA Cloud Private Edition
Description	This CDS view provides the prerequisites for answering questions about the subsequent items of a sales order item (that is, the process flow). Example business questions could include:<ul> <li><p>Which subsequent items does my sales order item have?</p></li> <li><p>What's the document category of the subsequent item of my sales order item?</p></li> <li><p>Which process flow level is this subsequent document on? The process flow level describes the degree of separation between a document and its subsequent documents. For example, for a delivery document (which is the direct successor of a sales order), the value would be 00. For a billing document, the value would be 01.</p></li> <li><p>When was the subsequent item created?</p></li> </ul> <p>To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views.</p>

Documentation

Analytics with CDS Views — Build Analytics for S/4HANA Cloud Private Edition ABAP CDS views replicated to SAP Cloud Platform
CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Private Edition Private Edition CDS Views on SAP Business Accelerator Hub
Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Private Edition and consume them as APIs
Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
SAP Extensibility Explorer for SAP S/4HANA Cloud Private Edition — Explore SAP S/4HANA Cloud Private Edition Extensibility options by leveraging the sample scenarios from SAP
SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Private Edition
View Browser — Search, browse and tag CDS Views

Data Sources (1)

Source	Alias	Join Type
I_SalesDocItmSubsqntProcFlow	SubsequentProcFlowItem	from

Associations (2)

Cardinality	Target	Alias	Condition
[1..1]	I_SalesOrder	_SalesOrder	`$projection.SalesOrder = _SalesOrder.SalesOrder`
[1..1]	I_SalesOrderItem	_SalesOrderItem	`$projection.SalesOrder = _SalesOrderItem.SalesOrder and $projection.SalesOrderItem = _SalesOrderItem.SalesOrderItem`

Annotations (8)

Name	Value	Level
EndUserText.label	Subsequent Process Flow of Sls Ordr Item	view
VDM.viewType	#COMPOSITE	view
VDM.lifecycle.contract.type	#PUBLIC_LOCAL_API	view
AccessControl.authorizationCheck	#CHECK	view
ObjectModel.usageType.dataClass	#TRANSACTIONAL	view
ObjectModel.usageType.serviceQuality	#C	view
ObjectModel.usageType.sizeCategory	#XL	view
Metadata.ignorePropagatedAnnotations	true	view

OData Services (1)

Service	Binding	Version	Contract	Release
UI_RFM_STORE_HANDOVERORDER	UI_RFM_STORE_HANDOVERORDER	V2	C1	NOT_RELEASED

Fiori Apps (1)

App ID	App Name	Type	Description
F4639	Hand Over Orders	Transactional

Hand Over Orders

Business Role: Retail Store Associate

This feature allows you to hand over click-and-reserve orders without cancellation of sales order. Instead, a billing document is created in the system for further processing.

Fields (19)

Key	Field	Source Table	Source Field	Description
KEY	SalesOrder	I_SalesDocItmSubsqntProcFlow	SalesDocument	Preceding sales and distribution document
KEY	SalesOrderItem	I_SalesDocItmSubsqntProcFlow	SalesDocumentItem	Preceding Item of an SD Document
KEY	DocRelationshipUUID	I_SalesDocItmSubsqntProcFlow	DocRelationshipUUID	SD Unique Document Relationship Identification
	SubsequentDocument	I_SalesDocItmSubsqntProcFlow	SubsequentDocument	Subsequent Sales and Distribution Document
	SubsequentDocumentItem	I_SalesDocItmSubsqntProcFlow	SubsequentDocumentItem	Subsequent Item of an SD Document
	SubsequentDocumentCategory	I_SalesDocItmSubsqntProcFlow	SubsequentDocumentCategory	Document Category of Subsequent Document
	ProcessFlowLevel	I_SalesDocItmSubsqntProcFlow	ProcessFlowLevel	Level of the document flow record
	SubsqntDocItmPrecdgDocument		SubsqntDocItmPrecdgDocument	Preceding sales and distribution document
	SubsqntDocItmPrecdgDocItem		SubsqntDocItmPrecdgDocItem	Preceding Item of an SD Document
	SubsqntDocItmPrecdgDocCategory		SubsqntDocItmPrecdgDocCategory	Document Category of Preceding SD Document
	CreationDate	I_SalesDocItmSubsqntProcFlow	CreationDate	Record Created On
	CreationTime	I_SalesDocItmSubsqntProcFlow	CreationTime	Time of Change
	LastChangeDate	I_SalesDocItmSubsqntProcFlow	LastChangeDate	Last Changed On
	SalesOrderType	_SalesOrder	SalesOrderType	Sales Order Type
	SalesOrganization	_SalesOrder	SalesOrganization	Sales Organization
	DistributionChannel	_SalesOrder	DistributionChannel	Distribution Channel
	OrganizationDivision	_SalesOrder	OrganizationDivision	Org. Division
	_SalesOrder		_SalesOrder
	_SalesOrderItem		_SalesOrderItem

Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.

-- Derived SQL interpretation of CDS view I_SalesOrderItmSubsqntProcFlow.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.

CREATE VIEW I_SalesOrderItmSubsqntProcFlow AS
SELECT
  SubsequentProcFlowItem.SalesDocument AS SalesOrder,
  SubsequentProcFlowItem.SalesDocumentItem AS SalesOrderItem,
  SubsequentProcFlowItem.DocRelationshipUUID AS DocRelationshipUUID,
  SubsequentProcFlowItem.SubsequentDocument AS SubsequentDocument,
  SubsequentProcFlowItem.SubsequentDocumentItem AS SubsequentDocumentItem,
  SubsequentProcFlowItem.SubsequentDocumentCategory AS SubsequentDocumentCategory,
  SubsequentProcFlowItem.ProcessFlowLevel AS ProcessFlowLevel,
  SubsqntDocItmPrecdgDocument,
  SubsqntDocItmPrecdgDocItem,
  SubsqntDocItmPrecdgDocCategory,
  SubsequentProcFlowItem.CreationDate AS CreationDate,
  SubsequentProcFlowItem.CreationTime AS CreationTime,
  SubsequentProcFlowItem.LastChangeDate AS LastChangeDate,
  _SalesOrder.SalesOrderType AS SalesOrderType,
  _SalesOrder.SalesOrganization AS SalesOrganization,
  _SalesOrder.DistributionChannel AS DistributionChannel,
  _SalesOrder.OrganizationDivision AS OrganizationDivision
FROM I_SalesDocItmSubsqntProcFlow AS SubsequentProcFlowItem
LEFT OUTER JOIN I_SalesOrder AS _SalesOrder ON SalesOrder = _SalesOrder.SalesOrder  -- association [1..1]
LEFT OUTER JOIN I_SalesOrderItem AS _SalesOrderItem ON SalesOrder = _SalesOrderItem.SalesOrder AND SalesOrderItem = _SalesOrderItem.SalesOrderItem  -- association [1..1]
;

Depth:

I_SalesOrderItmSubsqntProcFlow view_entity

I_SalesDocItmSubsqntProcFlow view_entity

A_SalesOrderItmSubsqntProcFlow view_entity