WS_DELIVERY_UPDATE or WS_DELIVERY_UPDATE_2 ? What is the best ?

[douglasFarcic]

 If you are here and now, then it is likely that you need to do a Picking, PGI or update some information about a Delivery and you don't know the correct RFCfor this.

Or, you somehow got to one of these two functions and are thinking "I'm going to use WS_DELIVERY_UPDATE_2, it's the newest one after all." or "I'm going to use WS_DELIVERY_UPDATE_2, I think 1 had a lot of bugs and so they made 2"

Or, it could be that you did a Google search and saw one of the many articles written by an Indian and saw the recommendation to use WS_DELIVERY_UPDATE_2.

And then you create your beautiful (or not) code that makes use of WS_DELIVERY_UPDATE_2and when testing it seems like everything went well, but in the Production environment you start to notice some problems. And then, in a new Google search, you find solutions like:

• "Add DESTINATION NONE in the RFC call";
• "Run the SERIAL_INTTAB_REFRESH function before or after the WS_DELIVERY_UPDATE_2 function";

Well, I created this article to demystify this topic!

Just like you, I had problems using the WS_DELIVERY_UPDATE_2 function and so I went to ask the creator! No, I'm not talking about God, but about SAP. I contacted SAP Product Support and discovered that the WS_DELIVERY_UPDATE_2 RFC is not for us mere customers or consultants:

 Thank you Catherine!

Well friends, today we learned that we should use WS_DELIVERY_UPDATE, okay!?

I hope I helped in some way!

[juan_acuna]

Hi, I don't want to be negative, but if you check the header of both FMs WS_DELIVERY_UPDATE, WS_DELIVERY_UPDATE_2 you will see on both of them on the right side saying "Not released". So if you are expecting any SAP support none of them will have, and no, I don't have any alternative. Just wanted to highlight it becauase you can be spending a lot of time changing them and will also not be supported by SAP.