Skip to Content

This document is in continuation of http://scn.sap.com/docs/DOC-45574

In this document I’m going to explain about processing Deliveries in SD & Goods Receipts in MM Modules using EDI- IDocs, Outbound and inbound deliveries in Logistics Execution.   After completion of GR in MM, a confirmation message is sent back to SD module as a Proof of delivery.

Prerequisites:

1. A sales order created against the PO as explained in above link.

2. Knowledge of Inbound and outbound deliveries.

Follow the below steps for processing outbound and inbound deliveries with IDocs.

Step1. Create Condition Record in transaction NACR for message type LAVA as shown below.


/wp-content/uploads/2013/08/1_269567.jpg

Enter the Sales Organization (6666) and Customer Number (100211) with Transmission medium 6 (EDI).


/wp-content/uploads/2013/08/2_269568.jpg

Note: The Partner function maintained here (SH) is to be used in step No. 2   as partner role.

Step2. In Transaction WE20 for partner profile customer (100211) maintain outbound parameters with partner role SH, message type DESADV & Basic Type DESADV01 as explained in the previous document Part1.


/wp-content/uploads/2013/08/3_269569.jpg

In Message control tab maintain message type LAVA with process code SD05 as shown below.

/wp-content/uploads/2013/08/4_269576.jpg

Step3. In Transaction WE20 for partner profile Logical System (RD2CLNT800) maintain inbound parameters with message type DESADV and process code DESA.

/wp-content/uploads/2013/08/7_269577.jpg

Follow the below steps for processing Proof of Delivery with IDocs.

Step4. In Transaction XD02 for Customer  100211 in sales area (6666, 66, 66) data shipping tab, mark the check box of relevant for POD as shown below.

/wp-content/uploads/2013/08/8_270052.jpg

Note: If you mark this check box you can bill the customer only after receipt of Proof of delivery from him. You can also mark this check box in sales order Item shipping tab.

/wp-content/uploads/2013/08/2_269568.jpg

Step5: Create Condition Record in transaction NACR for message type OPOD as shown below.

/wp-content/uploads/2013/08/9_269629.jpg

Enter the inbound delivery document type (EL) and vendor Number (2096) with Transmission medium 6 (EDI).

/wp-content/uploads/2013/08/10_269630.jpg

Note: The Partner function maintained here (VN) is to be used in step No. 6   as partner role.

Step6. In Transaction WE20 for partner profile vendor (2096) maintain outbound parameters with partner role VN, message type STPPOD & Basic Type DELVRY03 as explained in the previous document Part1.

/wp-content/uploads/2013/08/11_269634.jpg


In Message control tab maintain message type OPOD with process code OPOD as shown below.


/wp-content/uploads/2013/08/12_269635.jpg

Step7. In Transaction WE20 for partner profile Logical System (RD2CLNT800) maintain inbound parameters with message type STPPOD and process code DPOD.

/wp-content/uploads/2013/08/13_269637.jpg

Testing:

Step1. Create outbound delivery in Transaction VL01N for the sales order created in previous document Part1.

/wp-content/uploads/2013/08/14_269638.jpg

Carryout Post Goods Issue by entering storage location (0001) & Picked quantity (10).

/wp-content/uploads/2013/08/15_269639.jpg

Make sure that message LAVA was sent successfully in VL02N >> Extras >> Delivery Output >> Header.

Step2. In Transaction WE02 Check the outbound & inbound IDoc status of message type DESADV.


/wp-content/uploads/2013/08/16_269640.jpg

Step3. In Transaction ME23N check the Purchase order is updated with inbound delivery in Item confirmations tab. Note the Inbound delivery number and go to transaction VL32N

/wp-content/uploads/2013/08/17_269642.jpg

Step4. In Transaction VL32N carryout Post Goods Receipt by entering receiving storage location & Quantity in stock placement tab.

/wp-content/uploads/2013/08/18_269643.jpg

/wp-content/uploads/2013/08/19_269644.jpg

Make sure that message OPOD was sent successfully in VL32N >> Extras >> Delivery output.

Step5. In Transaction WE02 Check the outbound & inbound IDoc status of message type STPPOD.


/wp-content/uploads/2013/08/20_269645.jpg

Step6. In Transaction VLPODA check the Proof of delivery document created against the outbound delivery.

/wp-content/uploads/2013/08/23_269649.jpg

/wp-content/uploads/2013/08/21_269646.jpg

/wp-content/uploads/2013/08/22_269647.jpg

Step7. In Transaction VLPODL confirm the Proof of Delivery as shown below.

/wp-content/uploads/2013/08/24_269648.jpg

/wp-content/uploads/2013/08/25_269650.jpg

If the Status is success then you can process Billing to the customer.

/wp-content/uploads/2013/08/26_269652.jpg

-End Of Document Part2

In Continuation of this document I will explain about ‘processing billing in SD and logistics invoice verification in MM for the above business process using IDocs’ in my next document http://scn.sap.com/docs/DOC-45778

Thanks For Reading & Please share your reviews & feedback….

Regards

Satish


To report this post you need to login first.

11 Comments

You must be Logged on to comment or reply to a post.

  1. Udaya SN

    Your docs always need Exceptional rating.. as a new user to this forum I’m extremely happy looking at the repository available/shared..

    (0) 
  2. Mladen Kovacic

    Hi Satish,

    Your blog is very valuable for our proof of concept.

    We tried to configure this scenario exchanging DESADV and STPPOD messages and in our case it worked partially.

    After posting outbound delivery inbound delivery was created, but after we post inbound delivery STPPOD IDOC is generated but in a filed E1EDL20/VBELN of STPPOD IDOC there is inbound delivery number and outbound delivery POD data were not updated.

    What is in a field E1EDL20/VBELN of STPPOD IDOC in your case?

    In our system there is no OPOD message as a standard so we have to configure it from scratch. We put it in a procedure E10001 with requirement 17.

    Also, we have to configure some parts in customizing:

    1. Logistic Execution, Shipping, Deliveries, Proof of Delivery, Set POD-Relevance Depending on Delivery Item Category: Item category ELN – POD Relevant (X – Relevant for POD), POD Automatic (T – Partly-Automated POD)
    2. Logistic Execution, Shipping, Deliveries, Proof of Delivery, Define Reasons for Quantity Differences: we created two reasons (one for + and one for +) and mark them as a default

    We also mark a supplier in Control Data, Reference part as A – Always send POD

    So, these are our settings. Do we missed something to configure?

    Regards,

    Mladen Kovacic

    (0) 
    1. Mladen Kovacic

      Hello,

      I found what was a source of a probelm:

      we were messing with LIKP-LIFEX value (clearing it) when creating inbound delivery.

      After we correct it the outbound STPPOD contain in E1EDL20/LIFEX number of outbound delivery and now it correctly update POD data.

      Thanks again for your blog.

      Mladen Kovacic

      (0) 
  3. Corentin Corentin

    Hi

    It is a very useful document. Good work!

    just one question about That kind of scénario. Is it possible to do the same thing in standard with request of quotation and quotation.

    I Explain my requirement. Two plants within the same group in the same client. the first plant create an RFQ and send it to the second company wich create a RFQ in its system. The second company create in its turn a quotation and send it to the first company wich create a quotation in its Sap system. One company is the vendor and the other one the customer but in the same group and in the same client.

    Is it possible to map and automate that kind of process with IDOC in standard SAP system Like sales order and purchase order.

    Thanks for your help

    best regards

    (0) 
  4. Hakan Türkkan

    Dear Mr. Satish Babu,

    Thank you for your contribution to community. Your post help me a lot.

    Now we are discussing how manage cancellations and reverse deliveries.

    Do you have any suggestion how to delete inbound delivery, if I reverse outbound delivery?

    Best Regards,

    (0) 

Leave a Reply