Example: Returns Processing in Service Parts Management 

Purpose

You use this process in the Service Parts Execution business scenario. The process describes how the supplier and customer process returns in SAP Supply Network Collaboration (SAP SNC).

Prerequisites

The supplier uses SAP ERP with activated Service Parts Management as a back-end system. SAP only delivers standard XSLT mappings for message integration with SAP SNC for this back-end system.

Process

...

       1.      The supplier sends a return delivery instruction to SAP SNC from the back-end system.

The back-end system generates the return delivery instruction based on a return delivery order from SAP Customer Relationship Management (SAP CRM).

The transfer occurs as follows:

                            a.      The back-end system generates the RETINS.DELVRY05 IDoc for the return delivery instruction and sends this to SAP NetWeaver.

                            b.      SAP NetWeaver maps the IDoc to an XML message of the ReturnDeliveryInstructionNotification type and sends this to SAP SNC.

       2.      To find out about RMAs that have just arrived and that are to be processed, the customer calls the RMA overview or the RMA due list on the Web user interface in SAP SNC. In the RMA overview, the customer finds the quantity for each RMA number that can be returned.

       3.      Based on the RMAs, the customer creates a returns ASN on the Web UI. The customer can include multiple RMA numbers in a returns ASN, provided they have specific data in common (see Processing Returns ASNs). On the Web UI, the customer can cancel RMA numbers that are no longer required (see Functions for Returns Processing).

If the customer does not have Web access, the supplier can create ASNs in SAP SNC on the customer's behalf. The same functions are available to the supplier on the Web UI of SAP SNC to process returns ASNs.

       4.      In returns ASN processing, the customer manually packs the items from the returns ASN into handling units (HU). The customer prints the returns ASN, the tags for the ASN items, and the HU labels and uses these documents as follows:

○       The customer can attach the printed returns ASN to the return as a delivery note.

○       The customer uses the tags for the ASN items to label the products that belong to an item in the returns ASN (that is, to an RMA).

○       The customer uses the HU labels to label the HUs.

       5.      If the customer has finished processing the returns ASN, and wants to send the returns ASN to the supplier, the returns ASN can be published in the Web UI. SAP SNC then sends the returns ASN to the supplier’s backend system. The transfer occurs as follows:

○       SAP SNC sends the returns ASN to SAP NetWeaver as a DespatchedDeliveryNotification with a set returns indicator.

○       SAP NetWeaver maps the DespatchedDeliveryNotification to the IDoc DESADV.DELVRY04 (message variant CHR) and sends the IDoc to the back-end system.

○       The back-end system updates the inbound delivery.

       6.      If the customer wants to cancel a published returns ASN, the customer asks the supplier to send a cancellation returns ASN from the back-end system to SAP SNC. The transfer occurs as follows:

                            a.      The back-end system generates the IDoc DELIF.DELVRY05 (message variant CHR) for the cancellation returns ASN, and sends the IDoc to SAP NetWeaver.

                            b.      SAP NetWeaver maps the IDoc to an XML message of the type DeliveryInformation and sends this XML message to SAP SNC.