on 07-07-2015 9:20 PM
Hi,
I have one STO (Stock transport order) with 3 line items.
All line items have same ship to party, route, transportation group, loading group, sending plant/storage location, receiving plant/storage location, partners, Inco terms etc etc. Delivery date is also same (08/23/2015) for all three line items.
Basically all the shipping criteria fields are same and there is no reason for delivery split to be happened. Then also when I ran VL10B transaction (only for this STO), system created three different outbound deliveries.
I ran the SAP supplied report "zle_analyze_delivery_split" on two of the deliveries and came to know reason for split.
SAP did split the deliveries in this STO because of fact the field EKET-UZEIT is different. Please refer to below images.
My requirement is, as long as delivery date is same for all three line items - system should create only one outbound delivery.
In other words, my requirement is that system should ignore this "Time" field for delivery splitting and should create only one delivery (with delivery date 08/23/2015) (This delivery date should not be changed to current or any other date).
For us, practically it does not matter whether first line item delivery time is 8:25:03, second line delivery time is 20:09:53 and last line item has time 20:02:54 - as they are ultimately going to be deliver on same day 08/23/2015
All these times in STO are not manually entered by user during ME21N/ME22N. These timings have come automatically from purchase requisitions which were created in APO. When purchase requisition gets created/changed in APO, that time gets populated in purchase requisition table
EBAN-UZEIT.
Instead of going into much details about how APO calculated this time etc, from ECC standpoint I want to setup something where I can tell system not to consider "Time" for delivery split as long as delivery date is same. If delivery date is different then I agree that system should create different deliveries.
Does anyone have done this in your company or client ? if yes then your response would be appreciated.
What master data, configuration, OSS note or copy control can be the best solution ? How to achieve this ?
Please let me know if any further details are needed from my end.
Appreciate all the inputs.
You can add the required logic in USEREXIT_MOVE_FIELD_TO_LIPS in include MV50AFZ1
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Sundeep, Jaydip and Lakshmipathi for your responses and I will discuss these options to ABAPer.
It is strange that "Time" is hardcoded in copy control and can not be tackle either with some standard SAP note or some configuration or master data. SAP seems less flexible here.
Atleast they may have designed one SAP note for that.
It seems bit illogical that even one second of "Time" difference (with same delivery date) can result into delivery split.
Unless I hear some other option from anyone else, I will explore these options suggested by Sundeep, Jaydip and Lakshmipathi. Thanks again.
Hi,
This is standard functionality of SAP and its some of the fields are hard coded in copy control program. For instance, Time in your case, It is hard coded in the program not to split delivery based on time, because its obvious of not having same time on the same date.
Take the help of ABAPer and see what can be done in copy control routine. The table is ZUK and the field is ZUKRI which hold the information for splitting criteria.
Hope it gives you a head start.
Regards,
Jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check OSS Note 355404 - Why was there a delivery split during creation? and Note 546668 - FAQ: Delivery split when creating deliveries.
You can try to run program ZLE_ANALYZE_DELIVERY_SPLIT in SA38 to find the reason for the split.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sundeep,
Thanks for response. I already know what is causing the issue and reason for delivery split.
Question is "How to tell system that do not consider "Time" field in delivery splitting criteria".
I am sure this may be happening to many clients and industries and some one must have worked on it and must have resolved this by some way.
Inputs would be appreciated.
User | Count |
---|---|
91 | |
11 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.