ARUN_SUP_SP_SO
Get supply specific SO online
ARUN_SUP_SP_SO is a CDS View that provides data about "Get supply specific SO online" in SAP S/4HANA. It reads from 4 data sources (aufk, arun_bdbs, ekes, ekko) and exposes 12 fields.
Data Sources (4)
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | ARUN_V_I_SUP_SO | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ObjectModel.usageType.sizeCategory | #XXL | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| AccessControl.personalData.blocking | #REQUIRED | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| EndUserText.label | Get supply specific SO online | view |
Fields (12)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| salesdoc_num | arun_bdbs | salesdoc_num | ||
| purchdoc_num | arun_bdbs | purchdoc_num | ||
| req_ind | arun_bdbs | req_ind | ||
| stock_source | arun_bdbs | stock_source | ||
| purchord_num | arun_bdbs | purchord_num | ||
| batch | arun_bdbs | batch | ||
| prodord_item | arun_bdbs | prodord_item | ||
| prodord_num | arun_bdbs | prodord_num | ||
| vendor | ekko | lifnr | ||
| ibd_num | ekes | vbeln | ||
| ibd_itm | ekes | vbelp | ||
| prodord_type | aufk | auart |
@AbapCatalog.sqlViewName: 'ARUN_V_I_SUP_SO'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #NOT_REQUIRED
@ObjectModel.usageType.sizeCategory: #XXL
@ObjectModel.usageType.serviceQuality: #X
@AccessControl.personalData.blocking: #REQUIRED
@ObjectModel.usageType.dataClass:#TRANSACTIONAL
@EndUserText.label: 'Get supply specific SO online'
define view ARUN_SUP_SP_SO as select from arun_bdbs as bdbs
left outer join ekko as ekko on(
bdbs.purchord_num = ekko.ebeln
)
left outer join ekes as ekes on(
ekes.ebeln = bdbs.purchord_num
and ekes.ebelp = bdbs.purchord_item
and ekes.etens = bdbs.confirmation_no
and bdbs.stock_source = 'L' )
left outer join aufk as aufk on(
aufk.aufnr = bdbs.prodord_num) {
bdbs.salesdoc_num as salesdoc_num,
bdbs.salesdoc_item as salesdoc_item,
bdbs.purchdoc_num as purchdoc_num,
bdbs.purchdoc_item as purchdoc_item,
bdbs.req_ind as req_ind,
bdbs.material_avail_date as material_avail_date,
bdbs.requested_date as requested_date,
bdbs.stock_source as stock_source,
bdbs.purchord_num as purchord_num,
bdbs.purchord_item as purchord_item,
bdbs.delivery_date_po as delivery_date_po,
bdbs.batch as batch,
bdbs.storage_location as storage_location,
bdbs.prodord_item as prodord_item,
bdbs.prodord_num as prodord_num,
ekko.lifnr as vendor,
ekko.bsart as purchord_type,
ekes.vbeln as ibd_num,
ekes.vbelp as ibd_itm,
aufk.auart as prodord_type
}
where bdbs.req_ind = 'VC'
or bdbs.req_ind = 'VI'
or bdbs.req_ind = 'VG'
or bdbs.req_ind = 'U1'
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"ARUN_BDBS",
"AUFK",
"EKES",
"EKKO"
],
"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