Skip to Content

PO confirmation with inbound delivery

Dear Gurus,

We are facing with the following business scenario on S/4 HANA 1809 system with embedded EWM system:

  • The buyer creates a PO for qty 100 and date 29.08.
  • Vendor Confirms that he can supply them for 30.08.
  • Based on vendor confirmation, buyer creates vendor confirmations (LA) to match with the data received from the vendor, this is important from two aspects: vendor post evaluation process and this confirmation line is MRP relevant, thus MRP will calculates with 30.08 instead of 29.08!

The problematic pont:

Once the goods arrives at our warehouse, inbound delivery has to be created manually via VL31N and during the document creation ASN No. has to be added because the EWM system uses that number as a control point (mandatory).

The problem is when we create the inbound delivery via VL31N with reference to that PO. it automatically creates a new confirmation line (LA), which is not acceptable from MRP point of view as the planning quantity is duplicated.

We can't create the inbound delivery at the time of vendor confirmed the date 30.08. because the ASN No. is not known and once one create the inbound delivery it is automatically distributed to EWM and ASN can't be added/updated anymore.

We thought some crazy ideas but non of them sounds idealistic and they are just theoretical:

  • Upon VL31N automatically creates the new confirmation, delete manually the original confirmation. This is not a good point neither from process point of view (because the manual steps) nor from vendor evaluation (confirmed qty and date vs. fact qty and date).
  • Create the Inbound Delivery when the vendor confirms originally the qty and date, leave the ASN No. empty and block the inbound delivery distribution to EWM. When the truck arrives, enter the ASN No., allow the inbound delivery distribution and that's all. This does not sounds standard SAP - anyway, is it possible to block distribution to EWM until the ASN field is filled?

Do you have any suggestion how to proceed?

Thank you and Best Regards,

Tamas

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Oct 29, 2019 at 09:07 PM

    It is technically possible to prevent the distribution of deliveries to external systems. One of the options is to make use of document incompletion - for example you can add field LIKP-VERUR with status group 58 in the incompletion procedure assigned to your delivery type. The idea is that in the standard system before the delivery is distributed the checks in routine 14 (LV07A014) are performed and among other fields there are checks for incompleteness for picking, packing and goods movement. If the criteria are not fulfilled the delivery is not distributed.

    Still, there can be cases where you do not need this ASN number in certain processes - for example it could be that not all your EL deliveries should have it (maybe you do not need to distribute all ELs). In this case to avoid unnecessary corrections of incomplete documents you can create a custom VOFM routine in the customer name range (starting with 900) where you perform the required checks according to your business needs and then you can assign it in VOFM->Requirements->Subsequent functions->Distribution.

    I cannot really say what is the right approach in your case but I agree with your opinion that option 1 is not a good idea.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.