UPOV_ORIGIN_DEST_DET
Allocated Origin Destination combination
UPOV_ORIGIN_DEST_DET is a CDS View that provides data about "Allocated Origin Destination combination" in SAP S/4HANA. It reads from 4 data sources (gho_allocres_h, t006, gho_uom_rule_h, gho_uom_rule_i) and exposes 7 fields with key fields RunId, OriginNode, DestinationNode.
Data Sources (4)
| Source | Alias | Join Type |
|---|---|---|
| gho_allocres_h | header | inner |
| t006 | unit | inner |
| gho_uom_rule_h | uom_hrule | inner |
| gho_uom_rule_i | uom_irule | inner |
Annotations (7)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | UPOS_PR_ORIDEST | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.serviceQuality | #X | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| EndUserText.label | Allocated Origin Destination combination | view |
@AbapCatalog.sqlViewName: 'UPOS_PR_ORIDEST'
@AccessControl.authorizationCheck: #NOT_REQUIRED
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.usageType.serviceQuality: #X
@ObjectModel.usageType.sizeCategory: #L
@ObjectModel.usageType.dataClass:#TRANSACTIONAL
@EndUserText.label: 'Allocated Origin Destination combination'
define view UPOV_ORIGIN_DEST_DET
as select distinct from gho_allocres_i as item
inner join gho_allocres_h as header on header.alloc_run_id = item.alloc_run_id
and header.frequency = 'M'
and (
header.alloc_status = '01'
or header.alloc_status = '04'
)
and header.final_ind = 'X'
inner join gho_uom_rule_h as uom_hrule on uom_hrule.net_id = header.netid
and uom_hrule.medium = header.medium
and uom_hrule.valid_from <= dats_tims_to_tstmp(
header.prod_date, header.prod_time, 'UTC', $session.client, 'NULL'
)
and uom_hrule.valid_to >= dats_tims_to_tstmp(
header.prod_date, header.prod_time, 'UTC', $session.client, 'NULL'
)
inner join t006 as unit on unit.msehi = item.unit
inner join gho_uom_rule_i as uom_irule on uom_irule.uom_rule_id = uom_hrule.uom_rule_id
and uom_irule.dimension = 'VOLUME'
and uom_irule.dimension = unit.dimid
{
key item.alloc_run_id as RunId,
key item.origin_node_id as OriginNode,
key item.dest_node_id as DestinationNode,
item.unit,
item.wcdvlh_no,
item.invt_dt,
item.eff_to_dt
}
where
(
item.theo_act_ind = 'A'
or item.theo_act_ind = 'B'
or item.theo_act_ind = 'R'
or item.theo_act_ind = 'S'
or item.theo_act_ind = 'D'
or item.theo_act_ind = 'L'
)
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"GHO_ALLOCRES_H",
"GHO_ALLOCRES_I",
"GHO_UOM_RULE_H",
"GHO_UOM_RULE_I",
"T006"
],
"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