Customer Standard Return - Returns Overview - Returns Steps - Transfer To Scrap - CDS View #COE

[david_maksymec]

In the Manage Customer Returns – Version 2 app there is a Returns Overview section for each of the return order items that provides the return steps. The first level in this example is the customer return with shipment to plant. This first level step includes the following steps: returns order, returns delivery, goods receipt, inspection, logistical follow-up, credit memo request, goods movement for valuation and credit memo. The next first level step in the example is transfer to scrap with the next level step below that being goods movement to scrap. 

We are trying to develop a report that uses either a CDS View or an API that will provide this information. The main issue that we are encountering is that the goods movement to scrap return step under transfer to scrap does not appear to be related to the return order itself. When I view the material document information for the goods movement to scrap transaction it does not contain the return order. Please advise how this relationship can be determined and provide the CDS Views or APIs that can be utilized to recreate the Return Steps that appear under the Returns Overview section of the Manage Customer Returns – Version 2 app. Thank you

[Dave_He]

Hello @david_maksymec ，

Thanks for your question. To address your requirement of developing a report that captures the return steps, including the goods movement to scrap, and relates them to the return order, you need to understand the underlying data model and relationships in SAP S/4HANA Cloud. Here I can provide approach to achieve this:

Step 1:The key entities involved in the return process are:
- Return Order
- Return Delivery
- Goods Receipt
- Inspection
- Logistical Follow-up
- Credit Memo Request
- Goods Movement (including movement to scrap)

Step 2: Identifying Relevant CDS Views and APIs:

1. **CDS Views:**
- **I_ReturnOrder**: Provides details about the return order.
- **I_ReturnDelivery**: Provides details about the return delivery.
- **I_MaterialDocument**: Provides details about material documents, including goods movements.
- **I_InspectionLot**: Provides details about inspection lots.
- **I_CreditMemoRequest**: Provides details about credit memo requests.
- **I_GoodsMovement**: Provides details about goods movements.

2. **APIs:**
- **API_RETURN_ORDER_SRV**: For return order details.
- **API_MATERIAL_DOCUMENT_SRV**: For material document details.
- **API_INSPECTION_LOT_SRV**: For inspection lot details.
- **API_CREDIT_MEMO_REQUEST_SRV**: For credit memo request details.

Step 3: Establishing Relationships
To establish the relationship between the return order and the goods movement to scrap, you need to trace the document flow. Here’s how you can do it:

1. **Return Order to Return Delivery:**
- Use the `I_ReturnOrder` CDS View to get the return order details.
- Use the `I_ReturnDelivery` CDS View to get the return delivery details related to the return order.

2. **Return Delivery to Goods Receipt:**
- Use the `I_MaterialDocument` CDS View to get the goods receipt details related to the return delivery.

3. **Goods Receipt to Inspection:**
- Use the `I_InspectionLot` CDS View to get the inspection details related to the goods receipt.

4. **Inspection to Logistical Follow-up:**
- Use the `I_GoodsMovement` CDS View to get the logistical follow-up details related to the inspection.

5. **Logistical Follow-up to Goods Movement to Scrap:**
- Use the `I_GoodsMovement` CDS View to get the goods movement to scrap details.
- Ensure that the goods movement to scrap is linked to the logistical follow-up step.

Step 4: Creating the CDS View or Report
You can create a custom CDS View or report that joins these standard CDS Views to fetch the required data.

Conclusion
By following the above steps, you can create a report that captures the return steps, including the goods movement to scrap, and relates them to the return order. This approach leverages standard CDS Views and APIs provided by SAP S/4HANA Cloud, ensuring that the solution is robust and maintainable.

Hope it can help.

Best Regards

Dave