on 10-09-2014 11:35 AM
Hello,
I have created and inbound delivery with two items, based on two scheduling agreements (belonging to the same plant, company code and having the same storage location).
The only difference between the item in the Inbound delivery is the Reference document in the Predecessor data tab at item level.
After posting goods receipt, when I create a return delivery via MBRL transaction code using the material document a delivery split occurs (I got 2 outbound deliveries with one item each one with document type RLL).
I checked OSS notes 546668, 840219 and 1149708. Every thing is OK. But after analysis I found out that the root cause of the delivery split is the field VGBEL (Reference document in table LIPS).
So, when I create another inbound delivery with two items and one Reference document and after that create a return delivery MBRL I got one outbound delivery with two items.
Is it the standard behavior of SAP ? If yes, is there any User Exit to avoid the delivery split ?
Thanks in advance.
Maher.
Hello,
To achieve order combination in transaction MBRL you might create a new copy routine for delivery creation of delivery type RLL (order type source DL) in transaction VTLA (field data transfer VBAK)
Create a new routine in transaction VOFM, active it and then, assign it to VTLA instead of 301 routine (ril. data VBAK).
To achieve order combination in transaction MBRL you might use the following workaround (set order combination flag at data copy routine for RLL deliveries).
Create a new copy routine for delivery creation of delivery type RLL where field for order combination is set always:
FORM DATEN_KOPIEREN_901.
xkomdlgn-kzazu = 'X'.
perform daten_kopieren_301.
ENDFORM.
Thanks,
Maher.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I would suggest to check through split analysis as explained in the note: 399912 - Split analysis activation during delivery creation
Regards,
AKPT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello PRASOON,
I looked into the OSS note : 399912, unfortunately split analysis activation doesn't work for MBRL.
I followed all steps w/o success.
Actually, the program ZLE_ANALYZE_DELIVERY_SPLIT, provides the fields causing the split.
But in my case, there is no differences between my both outbound deliveries header data.
Any other clues or should I open an OSS note ?
Thanks
Maher.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
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.