Split rules have not been touched since go-live, but the network has changed since<\/li>\n<\/ul>\nMistakes to avoid:<\/strong><\/p>\n\n- Changing TM settings before understanding what SD is producing \u2014 and equally, changing SD before checking whether planning could have consolidated anyway<\/li>\n
- Removing split rules without finding out why they were set<\/li>\n
- Assuming every split is a configuration error<\/li>\n
- Ignoring master data \u2014 duplicate ship-to records or inconsistent shipping conditions can produce different delivery results that look like configuration problems<\/li>\n
- Over-customising delivery creation, which creates a maintenance problem for someone later<\/li>\n<\/ul>\n
Delivery split review checklist<\/h2>\n\n
\n\n\n| Question<\/th>\n | Why it matters<\/th>\n<\/tr>\n<\/thead>\n |
\n\n| Could planning have consolidated these anyway?<\/td>\n | Check this first \u2014 it decides whether SD is worth reviewing at all<\/td>\n<\/tr>\n |
\n| Are deliveries split by different shipping points?<\/td>\n | Different pickup locations limit what planning can combine<\/td>\n<\/tr>\n |
\n| Are requested delivery dates stricter than the customer needs?<\/td>\n | A frequent source of splits that add no operational value<\/td>\n<\/tr>\n |
\n| Are routes assigned consistently for similar orders?<\/td>\n | Inconsistent route determination creates unexplained splits<\/td>\n<\/tr>\n |
\n| Are shipping conditions aligned across similar customers?<\/td>\n | Feeds shipping point and route determination<\/td>\n<\/tr>\n |
\n| Does the same address exist under several ship-to records?<\/td>\n | Easily missed, easily fixed<\/td>\n<\/tr>\n |
\n| Is product master data consistent for similar items?<\/td>\n | Loading group and transportation group both influence splits<\/td>\n<\/tr>\n |
\n| Do splits follow a current business rule, or old habit?<\/td>\n | Rules outlive the network they were designed for<\/td>\n<\/tr>\n |
\n| Are custom routines still in copy control?<\/td>\n | Old customisation often survives longer than its reason<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\nHow SCM Champs helps<\/h2>\nDelivery split questions sit across two teams. SD owns the logic, transportation lives with the result, and neither side usually sees the full picture.<\/p>\n We help organisations review both together:<\/p>\n \n- Delivery creation logic \u2014 split criteria, copying control and routines<\/li>\n
- Master data consistency across ship-to records, shipping conditions and product data<\/li>\n
- Whether the split rules still match how the business distributes today<\/li>\n
- What the split hands over to Freight Unit Building and planning<\/li>\n
- Whether the fix belongs in SD at all, or further downstream<\/li>\n<\/ul>\n
The goal isn’t to remove splits. It’s to know which ones are costing you something and which are protecting you.<\/p>\n Frequently asked questions<\/h2>\nWhy does SAP create multiple deliveries for one customer?<\/strong> Because relevant delivery-combination or split criteria differ \u2014 commonly shipping point, ship-to party, delivery date, route or shipping conditions. Which criteria apply depends on your copying control and order-combination settings.<\/p>\nWhich delivery split criterion has the biggest impact on transportation?<\/strong> Delivery date is often the one that matters most, because the dates influence the time constraints planning works with. If those constraints cannot be satisfied together on a feasible tour, planning may not be able to combine the resulting Freight Units.<\/p>\nDoes the delivery split affect Freight Unit Building?<\/strong> It shapes the input. Each relevant delivery can become a delivery-based transportation requirement for SAP TM, depending on the integration and configuration. Freight Unit Building then applies its own rules to those requirements, so the number of deliveries does not automatically decide the number of Freight Units \u2014 and neither decides the final grouping, which happens in planning.<\/p>\nCan the delivery split increase transportation costs?<\/strong> It can, when planning cannot consolidate the resulting requirements. If planning combines them into one Freight Order, the split does not add cost.<\/p>\nShould every delivery split be removed?<\/strong> No. Many exist for good reasons \u2014 dangerous goods, temperature control, customer agreements. Removing a valid split can combine things that were deliberately kept apart.<\/p>\nHow does route affect the delivery split?<\/strong> Different routes usually lead to separate deliveries. Route determination typically depends on departure and destination zones, shipping condition and transportation group, so inconsistency in any of those shows up as unexplained splits.<\/p>\nCan different delivery dates prevent shipment consolidation?<\/strong> They can. The dates influence the time constraints planning works with, and if those constraints cannot be satisfied together on a feasible tour, the Freight Units may not be combined.<\/p>\nHow can companies review delivery split rules after migrating to S\/4HANA?<\/strong> Take real examples where the business expected one delivery and got several, and trace what differed. Migration often carries old rules forward into a network that has changed since they were written.<\/p>\nIn short<\/h2>\nDelivery creation is not only an SD activity. It shapes warehouse work, what transportation planning receives, and eventually freight cost.<\/p>\n But keep the order right. The delivery split is where transportation demand takes shape \u2014 it is not usually where consolidation fails. Review it once you know planning could not have fixed it anyway.<\/p>\n When you do review it, check master data consistency alongside configuration. Inconsistent ship-to records, shipping conditions, plant data or other relevant master data can create delivery results that look like configuration problems.<\/p>\n For the wider picture, see [why SAP TM creates too many Freight Orders].<\/em><\/p>\nNot sure whether your problem starts in SD, Freight Unit Building, or the planning run?<\/strong><\/p>\nSCM Champs can review the end-to-end process, identify the underlying cause, and show you what needs to change.<\/p>\n \u2192 Request a Free SAP TM Assessment<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"Quick answer SAP can create separate deliveries when relevant delivery-combination or split criteria differ. The…<\/p>\n","protected":false},"author":1,"featured_media":2154,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[357],"class_list":["post-2153","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sap-tm","tag-sd-delivery-split-criteria-in-s-4hana"],"_links":{"self":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2153","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/comments?post=2153"}],"version-history":[{"count":1,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2153\/revisions"}],"predecessor-version":[{"id":2155,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2153\/revisions\/2155"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/media\/2154"}],"wp:attachment":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/media?parent=2153"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/categories?post=2153"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/tags?post=2153"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} |