Improvement Request

When a Goods Receipt is cancelled in SAP ERP it is not clear under what
circumstances will the status of
the purchase order be updated in SAP SNC. It needs to be clarified when the
supplier can create a new
advanced shipping notification (ASN).
Request Reason
D7595 - Support GR Reversal process
When a goods receipt reversal is executed in ECC, SNC doesn't have standard
functionality to reverse the
corresponding ASN in SNC. It should be part of standard SNC functionality to
reverse the inbound delivery in
ECC and the ASN in ECC when a Good Receipt reversal is processed. Can this be
added to standard SNC?
D7599 - Update PO status when goods receipt is cancelled
When a Goods Receipt is cancelled in ECC, an Idoc message should be triggered
to update the PO status in
SNC. This should be standard SNC functionality.
D7617 - MIGO Vs VL32N
Currently Goods receipt for SNC related inbound deliveries is only supported via
VL32N transaction by SAP.
The solution provided by SAP to post a GR via MIGO is in the note "570991".
However, this note does not
send the actual GR quantity to SNC, hence creating a discrepancy on SOH data
on the SMI Monitor.
Other Terms
purchase order, advanced shipping notification, ASN, SAP SNC, collaboration,
D7599, D7599, goods
receipt, goods receipt cancellation, goods receipt reversal
Reason and Prerequisites
This note explains the goods receipt and goods receipt reversal process in SAP
SNC..

First, it need to be distinguished if the goods receipt document is cancelled or

some goods receipt quantities
were reduced, that is a goods receipt reversal.
The goods receipt document can be cancelled by movement type 102 in
transaction MIGO. In this
case the PO is opened again in SAP ERP and a new goods receipt can be issued.
Goods reversal or return delivery can be done via movement type 122 in
transaction MIGO. In this
case the PO is opened and a delivery note is created through the sales and
distribution module of SAP
ERP.
The overall system behavior at goods receipt and goods receipt reversal process
depends on different
factors:
if ASNs are used in the purchase order process or not
if GR is posted via transaction MIGO or VL32n
which ERP version is in use and which message type is sent to SNC (IDoc or XML)
if all relevant fields are mapped in SAP Netweaver PI system (e.g. at IDoc <->
XML mapping)
if customer extensions are implemented
This document does not cover the Service Parts Planning (SPP) scenarios
Using ASNs in the Purchase Order Process
In case of purchase orders the leading system is SAP ERP, however in case of
Advanced shipping
notifications (ASN) the leading system is SAP SNC. Advanced shipping
notification (ASN) is not reversed
automatically based on goods receipt reversal, as goods receipt reversal was
initiated by the customer, but
ASN was created by the supplier.
SAP ERP side transactions for GR reversal and cancellation:
When no ASN is in use, then MIGO to be used for inbound delivery and GR
reversal as well.
Movement type 102 to be used for goods receipt cancellation or 122 for goods
receipt reversal.
In case an ASN is in use, then at the SAP ERP side VL32N has to be used for
inbound delivery, and
VL09 to reverse inbound delivery. Alternatively, transaction MIGO can be used
against inbound
delivery to do GR and GR cancel without activating the customizing setting
TVSHP-SPE_INB_VL_MM,
but then GR has to be transferred using RSMIPROACT2 to update the ASN at SAP
SNC. (In case
when the customizing setting V_TVSHP-SPE_INB_VL_MM is active, then docflow
generated in
connection to the purchase order is activated in the logistics execution module of
SAP ERP, therefore
in this case transaction MIGO is also usable.)