Hi,

I’ve updated this document adding an example run in WM and added business case scenarios where this solution should be implemented and cases where  quantity difference could happen.

Is it possible to PGI when delivery and picking quantities are different? In many forums i’ve seen answers that this is not possible.

However, it is possible when the picking quantity is greater than delivery quantity (over picking). Do you want to know how? Keep reading!

Before changes

1.JPG

After

2.JPG

Let’s go:

Customizing, logistics, shipping, Configure Global Shipping Data

3.JPG

Tick on entry GI for over picking

4.JPG

Now, run OVM1 to customize error messages VL 019 from E (error) to W (warning)

5.JPG

That’s all.

When posting goods issue, if delivery quantity differs from picking quantity, which is the case, posted quantity is that of delivery quantity.

7.JPG

Once billed document, flow for line item displays it as completed

8.JPG

Let’s see what happens when working with WM.

We can create a TO with different picking quantity and confirm this quantity when confirming TO. When doing PGI, differences between delivery quantity and picking quantity remain in storage location 916 and have to be removed.

0.JPG

What’s the business case?

I found different business case to use this setting in the system:

  • Avoid issues when running PGI automated processes due to differences between quantities in delivery and picking (over delivery).
  • Solve error VL 632 in WM. Rounding differences may happen if sales unit measure in master material is smaller than the base unit of measure: in delivery, the quantities in base unit of measure are calculated internally with 3 decimals (further details in OSS note 1621474).
  • Overpass incompleteness procedure for delivery item if used field V50UC-OVPIK (picking qty > qty to be delivered) as a result of rounding differences (OSS note 707208).

In which cases could we have different quantities?

  • I could happen due to manual mistakes when typing picked quantities in warehouse or when receiving picked quantities by IDOC, barcode scanning, a malfunctioning of an interface… as shown in examples in this document.
  • if sales unit measure in master material is smaller than the base unit of measure: in delivery, the quantities in base unit of measure are calculated internally with 3 decimals leading to differences because of rounding.

Regards,

JM

To report this post you need to login first.

35 Comments

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

  1. prashanth gaddam

    Hi Joan,

    Nice post on over picking Qty than delivery Qty.

    May i know the business scenario where this will be required.

    As far as i know this is not suggestible  with the standard business process and practice.

    Also why the requirement is to over deliver.

    Sorry if this is a lame question and also for my understanding

    Thanks

    Prasha

    (0) 
    1. joan mas Post author

      Hi  Prashanth,

      thanks for your comments. The requirement is not to over deliver (if so, you would adjust delivery quantity). The situation is that you get from warehouse or your customer a picked quantity which is greater than delivery quantity.

      Business scenario?

      Though never used it, I can think on scenarios to avoid cancelling automated PGI processes because of this difference for example receiving picked quantity by IDOC or barcode scanning as well as human typing mistakes.  Anyone can add other?

      I’m sure that if SAP “opened” this option is because there are business cases for it…

      Regards,

      JM

      (0) 
    1. joan mas Post author

      Hi Jyoti,

      this approach would solve situations were reported picking quantity is wrong and would stop automated PGI processes.

      Regards,

      JM

      (0) 
      1. Jyoti Prakash

        But, don’t you think, this is contradictory. When in one place you are allowing “GI for over-picking“. And in other place your are not considering the over-picked quantities for GI.

        Is this applicable to WM or IM materials?

        Thanks, JP

        (0) 
        1. joan mas Post author

          Hi Jyoti,

          at the end, this is a business policy. If business decides that in case of differences, by previous experience, what should be taken always as correct is delivery quantity then it makes sense to tick on this field in custo to avoid issues when posting PGI in background processes. On the other side, if business policy is to check where the differences come from (and this may take time…) and once found, you can always adjust manually delivery quantity & picking quantity before PGI as per the results of your investigation on the difference.

          I’ve tested in IM so far.

          Regards,

          JM

          (0) 
          1. Jyoti Prakash

            I thank you for your patience for taking out your time and clarifying our doubts.

            I understand the solution discussed is result of your client’s business requirement. And that can differ from customer to customer & project to project. Even the material is handled.

            But, I would recommend you to update the points we discuss in this post and clearly explain the requirement statement. Especially, Material is IM managed.

            Thanks.

            Best Wishes,

            JP

            (0) 
  2. Typewriter TW

    Joan,

    Very nice! Thanks for sharing!

    1. The sales order qty is not the qty picked (and sent to the customer). Would that not cause any issues in reporting etc.

    2. During the processing of delivery i.e. before PGI; because of this difference, would there be any issue related to available stock?

    Or picking qty updates the available stock, for creation of further sales orders?

    3. In billing document, what about pricing of this “extra” qty; if the qty in the sales order has discounts, freights etc. (at item level), then how is the price populating correctly in the bill?

    (0) 
    1. joan mas Post author

      Hi TW,

      thanks for your comments.

      Customer will receive and be billed by delivery quantity. There’s no additional quantity. What you get here is a different picked amount (over pick).

      No problems related to available stock. In delivery, when you check available stock, Simulated requirements are those of delivery quantity, not picking quantity.

      As there is no extra quantity, in delivery, if you use pricing procedure, it is not affected by changing picked quantity nor is in billing.

      Regards,

      JM

      (0) 
      1. Deepak Sharma

        Hi John,

        Firstly thanks for this post.

        I have a doubt, how can i post invoice based on picked quantity.

        like delivery quantity= 10 and picked quantity= 12, so invoice based be on 12 quantity instead of 10, how?

        Regards,

        Deepak

        (0) 
                1. joan mas Post author

                  Hi Deepak,

                  in first step, customizing, (img, logistics execution, shipping, basic shipping functions, configure global shipping data) you set at client level global shipping parameters. Here click on field GI for over-picking. You can press F1 for further details on it.

                  second step is related to changing the message system produces when over picking from E (error) to W (warning). For example, you’re in VL02N and you type in as picking quantity a quantity greater than delivery quantity for the line item. The message you’ll get will change from error to warning allowing you to save your delivery.

                  Regards,

                  JM

                  (0) 
    1. joan mas Post author

      Hi  MoazzaM,

      Business scenario: I can think on scenarios to avoid cancelling automated PGI processes because of this difference for example receiving picked quantity by IDOC or barcode scanning as well as human typing mistakes. 

       

      I’m sure that if SAP has “opened” this option is because there are business cases for it…

      Regards,

      JM

      (0) 
  3. Suman Sardar

    Hi joan,

    Thanks for pointing out the above config but I am not very much satisfied by the business scenario.I think there must be some solid reason to have this config in the SAP for a specific business case but we have to find out.

    Would request you and all the fellow member to put some light on it although I will also try to figure out that anything can be reasonable answer for the same.

    Thanks,

    Suman$

    (0) 
    1. joan mas Post author

      Hi,

      You can use form routine USEREXIT_SAVE_DOCUMENT_PREPARE and
      USEREXIT_SAVE_DOCUMENT both in include MV50AFZ1 foryour validations in the deliveries. Refer to user exits available in deliveries in OSS note 415716.

      Regards,

      JM

      (0) 
  4. Dushyant Vig

    Hi,

    Well I am new to SD. And I have one doubt related to this case only.

    1 strange issue came in my business landscape, where a user has picked exactly the double quantity for 8 batches. The batch weight says 2.12 but, picked qty is 4.24. Even my PGI status at header level is “B” and Line item PGI is completed. Now, even if i try to do PGI, it gives me an error.

    So, two questions comes to my mind here:

    1) Why did the system allowed to pick exactly the double qty for each batch? As I m stimulating the same scenario but it is throwing me the error that my picked qty cant be greater than my Delivery qty.

    2) How the PGI status changes at line item but not at header level? Any explanation for the 2nd question will help too.

    Thanks and Regards:

    Dushyant Vig

    (0) 
    1. joan mas Post author

      Hi Dushyant.

      it´s very difficult to answer to your question. System shouldn´t have allowed it to happen unless:

      – your system was customized to overpass this control as explained in the document

      – there´s a bug in any abap coding developed in your system

      – there´s a bug in SAP standard

      If you can´t reproduce it anymore and no system updates have been applied, it looks like as if an abap coding delevoped inhouse was corrected later somehow. But if it happens again, check if custo explained in this document is in your system, if not, check OSS SAP notes or finally ask for the help of an abaper for debugging.

      Regards,

      JM

      (0) 

Leave a Reply