cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicate picking request in outbound delivery

rbucy
Explorer
0 Kudos

Hello all,

We have a 3PL business process with a non-WM storage location representing a 3PL warehouse.  We have the usual suite of interfaces to replicate deliveries, keep stock in balance, transfer material master information, transfer batch information, confirm picking, and goods issue deliveries.  We are having a very infrequent issue where a duplicate picking request is created on an outbound delivery, which increases the delivery quantity and results in over-billing to the customer.  The business process is:

  1. Outbound delivery is created in ERP and replicated to 3PL
  2. 3PL sends SHPCON message when picking is commenced
  3. 3PL sends SHPCON message when picking is completed
  4. 3PL sends SHPCON message when delivery is goods issued

The 2nd and 3rd SHPCON messages usually arrive and post simultaneously.  As a result, when the duplicate picking request occurs and increases the delivery quantity, the goods issue is occurring immediately as well before a correction can be made.  User exit EXIT_SAPLV55K_005 is used to update the picking quantity when the incoming SHPCON message is posted.

In relation to total deliveries processed, this error occurs rarely.  However, it is annoying to both the business and the customer, and we have been unable to find a correlation between the error and deliveries on which it occurs.  A similar issue was posted about on SCN at http://scn.sap.com/thread/3216412, and a solution was never posted to that thread.  I am grasping at straws and was just hopeful that somebody else may have encountered this and be able to direct me to a root cause and a solution.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello,

some ideas where to investigate:

what does the 2nd SHPCON update in your delivery? If you check VL03N before and after the 2nd SHPCON what changed? Why are quantities changed at "start of picking" (there is still nothing picked)

sending (receiving) multiple IDOCs to the same document (e.g. VBELN) somtimes causes trouble if processing of IDOCs are done asynchronous. If everything is technically 100% correct, the 3rd IDOC should run to a a IDOC inbound error with status like "delivery ... is locked by ..." because 2nd IDOC still locks VBELN. If not (which might be the case in your custom USER_EXIT), 3rd & 2nd IDOCs are processed in paralell which may cause this unlikely mess.

To avoid all of this,
- you can ask your 3PL if he adds a delay between 2nd and 3rd transmission. This is stupid but often easy to be done quickly.

- you can disable immediate processing in WE20 SHPCON inbound partner definition and schedule a job to process IDOCs in sequence (you may test this and see if these errors disappears)

- 3PL can switch to qRFC instead of tRFC (I assume 3PL uses tRFC) to process SHPCON in a sequence

Hope this gives you some ideas where to continue

Regards,

  Matthias

Former Member
0 Kudos

Maybe you can try the following to prevent over-delivery:-

1) define over-delivery limitation for each sales order item

2) activate over-delivery check on relevant delivery item category (V_TVLP-UEBPR)