Scope item 2EJ and 2EL are being followed on the system. A purchase order with 12 items is created, where 1 item has a different storage location from the others. When the Sales Order is generated, because not all the PO line items have the same address, this ship-to party address on sales order header level is just coming from the customer master data. Within this sales order, the ship-to party of item 100 and 200 are manually changed to another business partner. And when creating outbound delivery for this order, only item 100 and 200 can be grouped into one single delivery note, but each of the other items are split into several pieces of notes.
SAP S/4HANA Cloud
Reproducing the Issue
- The scope item 2EJ and 2EL are set up on the system.
- A purchase order with 12 items is created, where 1 item has a different storage location from the others.
- The sales order is saved and the ship-to party of 2 items are manually changed into another business partner.
- Create the outbound delivery for this sales order, finding the sales order is split into 11 delivery notes and only those 2 items who have the same ship-to party are within one delivery note.
This is standard design. EDI scenario simulates "Create Sales Orders" by WebGUI(VA01). When creating sales order, system will get the address of BP master data first. And if this address is changed and the order is saved, it will generate new address ID for every order item(BP). So as design, this case will generate different address IDs for every ship-to party of items. Since those 2 items are changed into another BP, the address is determined again so that the system would consider these 2 items to be the same address ID. And for the other items, they will be split into different develiry notes per different ship-to party address ID.
2EL, 2EJ, Purchase Order, EDI, Address ID, Ship-to Party, Business Partner , KBA , SD-SLS-EDI , S/4HANA: Sales EDI Messages , SD-SLS-API , API , Problem