Skip to Content

WM pick not on delivery document flow

While testing the LT0G reversal of picking and recreating of TOs, I ran into a situation where the new TO for picking did not update the Delivery item status (VBUP-KOSTA). This TO does not show up on delivery doc flow (table VBFA) just for one line item, the same TO does look good for other delivery line items.

Because of this, subsequently using LT03 I was able to create a new TO. This was going to double up the actual picked quantity in the dynamic 916 bin - but there is no record of it in the Delivery. I realized this a deleted the new TO. Now the VBUP-KOSTA = A even though I am fully picked.

Any suggestion as to

  1. Why this could have happened
  2. Any fix programs. What I need is kind of the opposite of WS_CORR_VBFA_LTAP, so that I can add to VBFA table instead of deleting
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jan 13, 2017 at 09:49 AM

    Hi Raghu,

    1. Do you have custom codings which might have caused this issue but until it's reproducible, it's really hard to find the rootcause here.

    2. If you want the missing Transfer Order to be updated in the delivery document flow, then it has to be done manually via debugging at the table level or else, you can create a simple Z report. There is no standard report in this case from SAP.

    Since the stock has been moved correctly and if you are not going to reverse this delivery, then you can simply execute VL_COMPLETE for this delivery and then post GI instead of updating the missing TO entry in the VBFA.


    Add comment
    10|10000 characters needed characters exceeded

  • Jan 13, 2017 at 03:19 PM

    Thanks for replying Balaji. Yes, there was some custom code involved wrapping the LT0G for an RFC from an external system. The problem however turned out to be 2 separate issues.

    1) The document flow missing actually turned out to be normal, but confusing behavior where deleting a batch split line item removes the corresponding document flow. So, trying to compare the VBFA tables with the actual Transfer Orders will not work.

    2) The KOSTA issue, we could not replicate and are chalking it someone might have abandoned a program while debugging - We were on the development box for this.

    Being a development box, we did what most people do, just abandon the delivery and move on :)

    Add comment
    10|10000 characters needed characters exceeded