This virtual data model (VDM) provides an overview of the stock that is currently in transit between an issuing location (for example, a store or a distribution center) and a receiving location, when the two locations are assigned to different company codes.
This virtual data model serves as the basis for customer-designed queries to answer the following questions:
How many units of a particular article are in transit to my location?
Of the stock units in transit, how many have already been shipped? How many have been received?
What is the cost and the retail value of the stock in transit?
The virtual data model consists of several reuse views, including the following:
CrossCompanyStockInTransit (CrossCompanyStockInTransit
)
This view provides an overview of the stock that is currently in transit between two locations that have different company codes, based on SAP ERP purchase orders.
Material valuated non-special stock facts (MaterialValuatedNonSpecialStockFacts
)
The view obtains an overview of the stock for material, not including special stock, from SAP ERP for Retail.
Material (Material
)
This view provides general data, such as the material name, type, group, and category.
These views are built on the following business objects:
Purchase Order
Material
Important attributes include the following:
Article
, ArticleBaseUnit
, OrderUnit
, OrderUnitToBaseUnitConvNumerator
, OrderUnitToBaseUnitConvDenominator
: Provide information about the stock in transit.
ReceivingPlant
, RecievingPlantCompanyCode
, IssuingPlant
, StorageLocation
, IssuingStorageLocation
: Provide information about the locations between which the stock is in transit.
Important measures include the following:
PurchaseOrder
, ScheduledQuantity
, ReceivedQuantity
, IssuedQuantity
: Provide information about stock quantities in transit.
PurchaseOrderValueAtCostInPOCurrency
and PurchaseOrderValueAtRetailInPOCurrency
: Provide the cost and the retail value of the ordered stock in the currency of the purchase order.
To interpret your cross company stock in transfer data, it is important to understand the calculation of certain measures included in the views in this VDM:
Measure | Description | Calculation |
---|---|---|
| Unit Of Measure Conversion Factor | if(("OrderUnitToBaseUnitConvDenominator" != 0), ("OrderUnitToBaseUnitConvNumerator" / "OrderUnitToBaseUnitConvDenominator"), "OrderUnitToBaseUnitConvNumerator") |
| Cost Per Stock Unit | if(("TotalVltdStockQuantity" != 0), (double ("TotVltdStockValueInCoCodeCrcy") /double ("TotalVltdStockQuantity")), 0) |
| Sales Value Per Stock Unit | if( ("TotalVltdStockQuantity" != 0), (double ("TotStkValAtSlsPrInCoCodeCrcy") /double ("TotalVltdStockQuantity")), 0 ) |
| In Transit Cross Company Stock Quantity | if(("ReturnsItem" = 'X'), ("ReceivedQuantity" - "IssuedQuantity"), ("IssuedQuantity" - "ReceivedQuantity")) |
| In Transit Cross Company Stock Quantity In Article Base Unit | if(("OrderUnitToBaseUnitConvDenominator" != 0), ("InTransitCCStockQuantity" * "OrderUnitToBaseUnitConvNumerator" / "OrderUnitToBaseUnitConvDenominator"), "InTransitCCStockQuantity") |
| In Transit Cross Company Stock Value at Cost | if(("PurchaseOrderQuantity" != 0), ("PurchaseOrderValueAtCostInPOCurrency" *" InTransitCCStockQuantity" /" PurchaseOrderQuantity"), 0) |
| In Transit Cross Company Stock Value at Retail | "SalesValuePerStockUnit" * "InTransitCCStockQuantity" * "UnitOfMeasureConvFactor" |
| Scheduled Quantity In Base Unit of Measure | if(("OrderUnitToBaseUnitConvDenominator" != 0), ("ScheduledQuantity" * "OrderUnitToBaseUnitConvNumerator" / "OrderUnitToBaseUnitConvDenominator"), "ScheduledQuantity") |
| Received Quantity In Base Unit of Measure | if(("OrderUnitToBaseUnitConvDenominator" != 0), ("ReceivedQuantity" * "OrderUnitToBaseUnitConvNumerator" / "OrderUnitToBaseUnitConvDenominator"), "ReceivedQuantity") |
| Issued Quantity In Base Unit of Measure | if(("OrderUnitToBaseUnitConvDenominator" != 0), ("IssuedQuantity" * "OrderUnitToBaseUnitConvNumerator" / "OrderUnitToBaseUnitConvDenominator"), "IssuedQuantity") |
The views use the following filters:
EKKO
Issuing plant is not empty and purchase document type is not of type Transport
("RESWK" != "") AND ("BSAKZ" != 'T')
EKPO
Item category in purchasing document is set to either Standard
, Subcontracting
, or Stock transfer
, and
If the purchase document is of type Stock transfer
, the posting logic type GI posting according to STO logic (stock in transit) Item
is not set to Statistical
, and
Purchasing document category is either a Purchase Order
(F) or a Scheduling Agreement
(L)
("PSTYP" IN ('0','3','7')) AND ("CCOMP" != '1') AND ("STAPO" != 'x') AND ("BSTYP" IN ('F','L'))
EKET
Issued stock quantity is not equal to the received stock quantity
("WAMNG" != "WEMNG")
The most important tables and views from which data is retrieved are:
TCURM
(MM Configuration Customizing)
T001W
(Plant)
T001K
(Valuation Area)
T001
(Company codes)
DD02T
(sap internal tables)
DD02L
(sap internal tables)
MBEW
(material valuation)
MARA
and MAKT
(general material data)
EKPO
and EKKO
(purchase order data)
EKET
(Scheduling Agreement data)
1 The terms material, article and product, as well as the terms plant, store and location, are used interchangeably in the naming of SAP HANA views and fields, and, as a result, in this documentation.