Solution : https://service.sap.com/sap/support/notes/448919 (SAP Service marketplace login required)
Summary :
In SAP systems, sales orders with identical partner functions but different partners result in a delivery split, aligning with standard operations. Confusion arises when an additional partner function, particularly a forwarding agent, is involved, leading to inconsistent system responses. Utilizing VL04 or VL10 spawns multiple orders due to the unique treatment of forwarding agents in the due list, affecting delivery combination. Conversely, combining orders in dialog usually merges them. A resolution involves using the ABAP Editor to introduce corrections that standardize responses concerning delivery splits impacted by partner data. This is achieved through specific implementation of user-exits and setting behavior controls via indicators in the updated standard.
Key words :
additional key words partner, delivery split basically occurs, form routine force_partner_split, delivery due list, partner function if_parvw, correct standard functioning, delivery split occurs, partner functions differing, additional partner function, item partners correctly
Related Notes :
| 546203 | Dely split due to forwarding agent w/ 'Deliver sales order' |
| 524145 | Delivery split for missing mandatory partner forwarding agnt |
| 385473 | Customer-specific partner relationship missing in delivery |
| 363508 | Incor.delivery split in relation to unloading point |
| 332055 | Schedulng agmt rel. overwrites VBKD receiving point |
| 193319 | VL034: Partner function incorrectly displayed |
| 156422 | Release type in delivery for scheduling agreement incorrect |
| 154065 | Incorrect item creation during batch determination |
| 144800 | Order combination after upgrade to Release 4.5 |
| 140278 | Statistics group customer f. deliveries w/o SD ref. |
| 107303 | Copying partners fr. order item to delivery header |