{"id":2143,"date":"2026-08-11T13:33:43","date_gmt":"2026-08-11T13:33:43","guid":{"rendered":"https:\/\/www.scmchamps.com\/blog\/?p=2143"},"modified":"2026-09-11T12:10:27","modified_gmt":"2026-09-11T12:10:27","slug":"sap-deliveries-not-grouping-correctly","status":"publish","type":"post","link":"https:\/\/www.scmchamps.com\/blog\/sap-deliveries-not-grouping-correctly\/","title":{"rendered":"Too Many Freight Orders Created in SAP TM? How to Find the Real Cause"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">If SAP TM is creating too many Freight Orders and your planners are regrouping deliveries manually, then you need to analyse the following-\u00a0\u00a0<\/span><\/p>\n<ol class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"11:1-13:35;324-647\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"11:1-11:149;324-472\"><strong>The planning run first.<\/strong> Time windows, incompatibilities, capacity, lanes, and selection settings block more consolidation than anything else.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"12:1-12:140;473-612\"><strong>Freight Unit Building second.<\/strong> Check which rule was used, which strategy it applies, and whether it runs automatically or as a batch.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"13:1-13:35;613-647\"><strong>The SD delivery split last.<\/strong><\/li>\n<\/ol>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"15:1-15:149;649-797\">Most teams do this in reverse. They blame the delivery split, change a Freight Unit Building Rule that was working fine, and the problem comes back.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"19:1-19:37;804-840\">The problem, as most teams see it<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"21:1-21:94;842-935\">The sales order is correct. The delivery is created on time. Everything upstream looks clean.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"23:1-23:345;937-1281\">Then the delivery reaches transportation planning, and the result is not what anyone expected. Two trucks where one would have been enough. Loads that should have travelled together, planned apart.<\/p>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">And somewhere the planner is quietly fixing them manually, because the system isn\u2019t able to schedule transportation as expected.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This is one of the most frequent challenges with SAP transportation planning.<\/span>\u00a0And it is rarely caused by the thing people blame first.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"27:1-27:64;1415-1478\">Most teams notice it as a set of symptoms, not one clear fault:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"29:1-34:41;1480-1778\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"29:1-29:47;1480-1526\">More shipments than the volume seems to need<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"30:1-30:40;1527-1566\">Consolidation chances that get missed<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"31:1-31:64;1567-1630\">Planners regrouping requirements by hand before they can plan<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"32:1-32:55;1631-1685\">Extra effort in carrier selection and route planning<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"33:1-33:52;1686-1737\">Planning cycles that take longer than they should<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"34:1-34:41;1738-1778\">A steady stream of planning exceptions<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"36:1-36:132;1780-1911\">SCM CHAMPS sees this pattern regularly in SAP TM assessments. The deliveries are correct, and the gap sits somewhere else entirely.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"38:1-38:95;1913-2007\">The instinct is to look at the delivery. Something must be wrong with how the order was split.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"40:1-40:351;2009-2359\">Sometimes that is true. Often it is not. In many cases the delivery is exactly what the sales process meant it to be. The gap sits between three layers that are set up separately and are rarely reviewed together: how SD splits deliveries, how SAP TM turns those deliveries into Freight Units, and what the planning run is actually allowed to combine.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"42:1-42:73;2361-2433\">Each layer can be correct on its own. The plan can still come out wrong.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"44:1-44:159;2435-2593\">One note on language before we go further. What the business calls a <em>shipment<\/em> is a <em>Freight Order<\/em> in <a href=\"https:\/\/www.scmchamps.com\/blog\/sap-transportation-management-to-streamline-your-business-operations\/\"><strong>SAP TM<\/strong><\/a>. From here on, this article uses Freight Order.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"48:1-48:46;2600-2645\">Which layer is your problem? A quick check<\/h2>\n<div class=\"overflow-x-auto w-full px-2 mb-6 print:overflow-x-visible\" dir=\"ltr\" data-sourcepos=\"50:1-56:122;2647-3348\">\n<table class=\"min-w-full border-collapse text-sm leading-[1.7] whitespace-normal\">\n<thead class=\"text-left\">\n<tr>\n<th class=\"text-text-100 border-b-0.5 border-[hsl(var(--border-300)\/0.6)] py-2 pr-4 align-top font-bold\" scope=\"col\">What you see<\/th>\n<th class=\"text-text-100 border-b-0.5 border-[hsl(var(--border-300)\/0.6)] py-2 pr-4 align-top font-bold\" scope=\"col\">Most likely layer<\/th>\n<th class=\"text-text-100 border-b-0.5 border-[hsl(var(--border-300)\/0.6)] py-2 pr-4 align-top font-bold\" scope=\"col\">What to check first<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Freight Units look correct, but they still don&#8217;t combine<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\"><strong>Planning run<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Time windows, incompatibilities, capacity, lanes, selection<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">One delivery turns into several Freight Units<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\"><strong>Freight Unit Building<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">The FUB rule, its strategy, split quantities<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Two similar deliveries behave differently<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\"><strong>Freight Unit Building<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Condition-based rule determination<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Two deliveries exist where the business expected one<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\"><strong>SD delivery split<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Shipping point, ship-to, delivery date, route<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Grouping is good some days and bad on others<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\"><strong>Planning run<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Which Freight Units were selected into the same run<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span style=\"font-weight: 400;\">How Delivery Grouping Actually Works<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Here is the sequence of how order fulfillment is actually handled.\u00a0\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sales Order\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Outbound Delivery\u00a0\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transportation Requirement Created<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Freight Units Consolidated<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transportation Planning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Freight Order<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Execution<\/span><\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"66:1-66:251;3588-3838\">The <strong>outbound delivery<\/strong> says what needs to be delivered and how the order has been divided. The split happens for sales and fulfilment reasons \u2014 shipping point, ship-to party, delivery date, route, and other criteria, depending on how it is set up.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"68:1-68:213;3840-4052\">The <strong>transportation requirement<\/strong> is how that delivery enters transportation planning. An outbound delivery becomes a delivery-based transportation requirement, which carries the transport-relevant data forward.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"70:1-70:219;4054-4272\">A <strong>Freight Unit<\/strong> is a group of goods that SAP TM treats as one transportation requirement for planning. It is the smallest unit the system plans and moves, and it carries the constraints that planning has to respect.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"72:1-72:219;4274-4492\"><strong>Freight Unit Building<\/strong> turns those requirements into Freight Units. The logic sits in the Freight Unit Building Rule, which can be found by condition \u2014 meaning different deliveries can be handled by different rules.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"74:1-74:129;4494-4622\"><strong>Transportation planning<\/strong> takes the Freight Units and decides which of them can travel together. The result is Freight Orders.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"76:1-76:173;4624-4796\">Out of all these stages, only two actually decide how transport demand gets grouped: <strong>Freight Unit Building<\/strong> and <strong>planning<\/strong>. This is where most of the confusion starts.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"78:1-78:342;4798-5139\">Freight Unit Building can group in different ways, depending on the strategy in the rule. It can create one Freight Unit per document item, or group all compatible items of one document, or consolidate as much as possible. That last strategy does work across separate business documents, including delivery-based transportation requirements.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"80:1-80:115;5141-5255\">But the strategy is only half the answer. What matters just as much is <strong>how Freight Unit Building is triggered<\/strong>.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"82:1-82:374;5257-5630\">Most implementations run it automatically, so Freight Units are created the moment the delivery is saved. In that mode there is nothing to consolidate with yet \u2014 the other deliveries have not arrived. Consolidating across documents at this stage needs Freight Unit creation to run as a batch or interactive step instead. That is a deliberate design decision, not a default.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"84:1-84:283;5632-5914\">So the practical position for most companies is this: <strong>if your Freight Unit Building runs automatically on delivery save, cross-delivery grouping is happening at the planning step, not before it.<\/strong> Checking which mode you run takes minutes, and it tells you which layer to look at.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"88:1-88:53;5921-5973\">Why SAP deliveries don&#8217;t group the way you expect<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"90:1-90:69;5975-6043\">There are five common causes. Most real cases involve more than one.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"92:1-92:56;6045-6100\">1. The delivery split shapes what planning receives<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"94:1-94:94;6102-6195\">Take a simple example. Same customer, same destination, same week. SD creates two deliveries:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"96:1-97:24;6197-6244\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"96:1-96:24;6197-6220\">Delivery 1 \u2192 60 boxes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"97:1-97:24;6221-6244\">Delivery 2 \u2192 40 boxes<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"99:1-99:118;6246-6363\">Each becomes its own delivery-based transportation requirement. With automatic Freight Unit Building, that gives you:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"101:1-102:18;6365-6400\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"101:1-101:18;6365-6382\">FU 1 \u2192 60 boxes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"102:1-102:18;6383-6400\">FU 2 \u2192 40 boxes<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"104:1-104:76;6402-6477\">The business expected one truck. It now has two separate transport demands.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"106:1-106:313;6479-6791\">Nothing has gone wrong. Freight Unit Building handled each requirement as it arrived. The delivery split has simply become part of what transportation has to work with. How those requirements are finally grouped is still decided downstream \u2014 by the Freight Unit Building strategy in use, and by the planning run.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"108:1-108:216;6793-7008\">If planning can combine them, the earlier split becomes invisible and nobody notices. If it cannot, the business sees two Freight Orders for what it thinks of as one shipment, and a planner starts fixing it by hand.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"110:1-110:386;7010-7395\">The reverse case is just as common, and harder to spot. <strong>A single delivery can produce several Freight Units<\/strong> when the Freight Unit Building Rule splits by criteria the business did not intend \u2014 by item, by product, or by a quantity limit, depending on how the rule is set up. One delivery goes in, four Freight Units come out, and the planner is left wondering where they came from.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"112:1-112:280;7397-7676\">And because Freight Unit Building Rules can be found by condition, <strong>two deliveries that look identical to a business user can be handled by two different rules.<\/strong> This one is easily missed, because the deliveries themselves give no visible clue that anything different happened.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"114:1-114:45;7678-7722\">2. SD and TM group for different reasons<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"116:1-116:166;7724-7889\"><span style=\"font-weight: 400;\">A delivery is split for sales and fulfilment reasons. A transport is built for transportation reasons. These are two different operations and need to be handled separately.\u00a0 <\/span><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"118:1-118:47;7891-7937\">The criteria that drive each side may include:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"120:1-127:32;7939-8063\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"120:1-120:8;7939-7946\">Plant<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"121:1-121:17;7947-7963\">Shipping point<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"122:1-122:11;7964-7974\">Customer<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"123:1-123:8;7975-7982\">Route<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"124:1-124:16;7983-7998\">Delivery date<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"125:1-125:19;7999-8017\">Product or batch<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"126:1-126:14;8018-8031\">Destination<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"127:1-127:32;8032-8063\">Transport-relevant attributes<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"129:1-129:221;8065-8285\">A delivery might be split because two line items have different delivery dates. Transportation planning might want them on the same vehicle anyway, because the dates are two days apart and the truck passes the same door.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"131:1-131:116;8287-8402\">Both positions are reasonable. The system will only settle it if someone has decided, deliberately, which one wins.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"133:1-133:35;8404-8438\">3. Data and timing differences<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"135:1-135:255;8440-8694\">Freight Unit Building uses the data available at the moment the delivery enters transportation planning. If key transport-relevant information is missing, incomplete, or arrives later, the Freight Units can look different from what the business expected.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"137:1-137:259;8696-8954\">Availability at planning time matters too. If the relevant Freight Units are not available, or not selected together when the planning run executes, they cannot be considered together in that cycle. Requirements that were meant to travel together never meet.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"139:1-139:144;8956-9099\">This is one reason the same order pattern can produce a good plan one day and a poor one the next, with no configuration having changed at all.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"141:1-141:46;9101-9146\">4. The business changed, the logic didn&#8217;t<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"143:1-143:178;9148-9325\">Distribution models change. Companies add a hub, shift to direct-to-store, renegotiate delivery windows with major customers, or change how they consolidate for certain regions.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"145:1-145:166;9327-9492\">The delivery split logic and the Freight Unit Building Rules often stay exactly as they were designed \u2014 sometimes years earlier, for a network that no longer exists.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"147:1-147:262;9494-9755\">The result is a slow, quiet gap between how the business now wants goods moved and how SAP still creates transport requirements. Nobody raises it as a system issue, because nothing broke. The planners simply absorb the difference by hand, and it becomes normal.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"149:1-149:53;9757-9809\">5. Consolidation is blocked at the planning step<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"151:1-151:82;9811-9892\">This is the layer that gets checked last, and it explains a large share of cases.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"153:1-153:113;9894-10006\">Even when the Freight Units are exactly right, the planning run may not be able to combine them. Common reasons:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"155:1-160:63;10008-10397\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"155:1-155:53;10008-10060\">Pickup or delivery time windows that don&#8217;t overlap<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"156:1-156:85;10061-10145\">Incompatibility settings that keep certain products, customers, or locations apart<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"157:1-157:53;10146-10198\">Capacity limits on the selected means of transport<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"158:1-158:44;10199-10242\">Missing or incorrect transportation lanes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"159:1-159:92;10243-10334\">Selection settings that never bring the relevant Freight Units into the same planning run<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"160:1-160:63;10335-10397\">Planning profile settings that restrict what can be combined<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"162:1-162:262;10399-10660\">The practical test is simple. <strong>If the Freight Units look correct and the Freight Orders still don&#8217;t consolidate, the constraint is almost certainly in planning.<\/strong> Reviewing the delivery and the Freight Unit will not find it, no matter how long you spend there.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"166:1-166:32;10667-10698\">What this costs the business<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"168:1-168:82;10700-10781\">The technical detail matters less to leadership than what it produces downstream.<\/p>\n<div class=\"overflow-x-auto w-full px-2 mb-6 print:overflow-x-visible\" dir=\"ltr\" data-sourcepos=\"170:1-178:78;10783-11331\">\n<table class=\"min-w-full border-collapse text-sm leading-[1.7] whitespace-normal\">\n<thead class=\"text-left\">\n<tr>\n<th class=\"text-text-100 border-b-0.5 border-[hsl(var(--border-300)\/0.6)] py-2 pr-4 align-top font-bold\" scope=\"col\">What happens in SAP<\/th>\n<th class=\"text-text-100 border-b-0.5 border-[hsl(var(--border-300)\/0.6)] py-2 pr-4 align-top font-bold\" scope=\"col\">Business impact<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Deliveries are split unexpectedly<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">More transports to manage<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Freight Units aren&#8217;t planned together<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Missed consolidation opportunities<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Planners manually regroup requirements<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">More operational effort<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">The plan doesn&#8217;t reflect business rules<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Planning inefficiency<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Freight Orders are created unnecessarily<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Possible freight-cost leakage<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Planning exceptions increase<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">More manual intervention<\/td>\n<\/tr>\n<tr>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Data doesn&#8217;t follow expected grouping<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Reporting and visibility problems<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"180:1-180:224;11333-11556\">The cost is rarely dramatic on any single day. That is what makes it last. A planner spends twenty minutes regrouping requirements each morning, an extra vehicle goes out half full, and none of it is big enough to escalate.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"182:1-182:278;11558-11835\">Over a year, across a network, it adds up to real freight spend and a meaningful amount of planning capacity. It can also mean your transportation reporting no longer reflects how goods actually moved, because the plan in the system and the plan in practice have drifted apart.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"186:1-186:81;11842-11922\">How to identify whether the problem is SD, Freight Unit Building, or planning<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"188:1-188:167;11924-12090\">Working through the chain in order usually finds the gap within a few examples. Take one case where the business expected a different result and follow it end to end.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"190:1-190:41;12092-12132\">Step 1: Review the outbound delivery<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"192:1-192:72;12134-12205\"><strong>Ask:<\/strong> why did SAP split this order into these particular deliveries?<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"194:1-194:202;12207-12408\">Look at the attributes that differ between them \u2014 shipping point, ship-to party, delivery date, route. If two deliveries exist where the business expected one, the reason is usually visible right here.<\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"196:1-196:37;12410-12446\">Step 2: Review the Freight Units<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"198:1-198:127;12448-12574\"><strong>Ask:<\/strong> which Freight Unit Building Rule was applied, which strategy does it use, and how is Freight Unit creation triggered?<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"200:1-200:23;12576-12598\">Three things to check:<\/p>\n<ol class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"202:1-204:198;12600-13112\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"202:1-202:187;12600-12786\"><strong>Automatic or batch?<\/strong> Does Freight Unit Building run automatically on delivery save, or as a batch step? This decides whether cross-delivery grouping is even possible at this stage.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"203:1-203:128;12787-12914\"><strong>One delivery, several Freight Units?<\/strong> Check whether one delivery was split into several Freight Units, and on what basis.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"204:1-204:198;12915-13112\"><strong>Different rules for similar deliveries?<\/strong> Check whether deliveries that look alike were handled by different rules. This happens more often than teams expect when rules are found by condition.<\/li>\n<\/ol>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"206:1-206:39;13114-13152\">Step 3: Compare the grouping logic<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"208:1-208:113;13154-13266\">Put the delivery criteria and the transportation criteria side by side and look for the differences that matter:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"210:1-217:23;13268-13369\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"210:1-210:8;13268-13275\">Dates<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"211:1-211:12;13276-13287\">Locations<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"212:1-212:12;13288-13299\">Customers<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"213:1-213:9;13300-13308\">Routes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"214:1-214:18;13309-13326\">Shipping points<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"215:1-215:9;13327-13335\">Plants<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"216:1-216:11;13336-13346\">Products<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"217:1-217:23;13347-13369\">Transport attributes<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"219:1-219:121;13371-13491\">The question is not which side is right. It is <strong>which difference is actually stopping the outcome the business wants.<\/strong><\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"221:1-221:39;13493-13531\">Step 4: Review the planning result<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"223:1-223:118;13533-13650\"><strong>Ask:<\/strong> did the planning run combine those Freight Units the way the business expected, and if not, what stopped it?<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"225:1-225:247;13652-13898\">First check whether the Freight Units were even selected into the same planning run. Then check time windows, incompatibilities, capacity, and transportation lanes. Only after that is it fair to conclude that Freight Unit Building is the problem.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"227:1-227:190;13900-14089\"><strong>Most investigations go wrong right here<\/strong> \u2014 by stopping at the Freight Unit, assuming the fault must be in how it was built, and reconfiguring a rule that was working correctly all along.<\/p>\n<h2><span style=\"font-weight: 400;\">How to Fix Delivery Grouping Problems<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Solving Delivery Grouping Problems requires a strategic approach; otherwise, else it adds to problems instead of solving them.\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ensure you map the end-to-end process, which includes &#8211;<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Order creation\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delivery\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transportation requirement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Freight unit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Planning\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Freight orders<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Execution\u00a0<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Instead of following a traditional approach, follow a strategic approach that actually works.\u00a0<\/span><\/p>\n<h3 class=\"mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"241:1-241:48;14546-14593\">Decide the grouping rules you actually want<\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"243:1-243:94;14595-14688\">This is a business decision, and it needs to be stated clearly before anything is configured.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"245:1-245:250;14690-14939\">Which deliveries should travel together? For many companies the answer looks something like: same customer, same destination, compatible delivery window. The exact criteria depend on the transport strategy, the customer<\/p>\n<p><span style=\"font-weight: 400;\">commitments, and the network.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Align all three layers<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Check whether the delivery split rules, the Freight Unit Building Rules, and the planning settings \u2014 including incompatibilities, transportation lanes, and selection criteria \u2014 are all supporting the same goal.<\/span><\/p>\n<h3><b>Test real business scenarios<\/b><\/h3>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"257:1-257:68;15392-15459\">One order proves nothing. Test the situations that actually happen:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"259:1-266:71;15461-15721\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"259:1-259:44;15461-15504\">Multiple deliveries for the same customer<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"260:1-260:18;15505-15522\">Multiple plants<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"261:1-261:27;15523-15549\">Different delivery dates<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"262:1-262:21;15550-15570\">Partial quantities<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"263:1-263:19;15571-15589\">Different routes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"264:1-264:36;15590-15625\">Multiple customers on one vehicle<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"265:1-265:25;15626-15650\">Different destinations<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"266:1-266:71;15651-15721\">Deliveries that should consolidate, <strong>and deliveries that must not<\/strong><\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"268:1-268:120;15723-15842\">That last pair matters. A change that improves consolidation can also combine things that were deliberately kept apart.<\/p>\n<p><span style=\"font-weight: 400;\">These exceptions are your early warning, and reviewing<\/span><span style=\"font-weight: 400;\"> them frequently is what helps prevent the occurrence of exceptions.\u00a0\u00a0<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Can a New S\/4HANA Version Release Fix This?<\/span><\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"280:1-280:98;16247-16344\">Not really. Newer releases add more control around the problem, but they do not remove the cause.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"282:1-282:328;16346-16673\">Recent S\/4HANA releases have added things like mixed-loading checks during freight unit building and consolidation, packaging information carried from sales orders and deliveries into Freight Units, and warehouse-driven delivery splits through Advanced Shipping and Receiving (ASR). Each of these helps in a specific situation.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"284:1-284:44;16675-16718\">But two things are worth being clear about:<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"286:1-286:308;16720-17027\"><strong>The ASR delivery split solves a different problem.<\/strong> It handles cases where what was planned cannot actually ship \u2014 stock is short, or the truck is full at the loading door. It is warehouse-driven, and it needs EWM. It is not a fix for deliveries that should have been grouped together in the first place.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"288:1-288:333;17029-17361\"><strong>More features means more places the logic can drift.<\/strong> SD still splits for sales reasons. TM still groups for transport reasons. Planning still applies its own constraints. Adding more options does not make those three layers agree \u2014 someone still has to decide what the business actually wants and make sure all three support it.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"290:1-290:151;17363-17513\">This is not a new problem. It has existed as long as SD and TM have been separate. It is simply one that most teams still diagnose in the wrong order.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"294:1-294:28;17520-17547\">In practice: a real case<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"296:1-296:342;17549-17890\">A European consumer goods manufacturer running embedded TM in S\/4HANA, with over 200 daily outbound deliveries, came to SCM CHAMPS with a familiar problem. Planners were spending the first hour of every morning manually regrouping requirements that the system kept splitting across separate trucks \u2014 even for identical customer destinations.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"298:1-298:105;17892-17996\">Internally, everyone assumed the SD delivery split was creating too many deliveries from a single order.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"300:1-300:54;17998-18051\">The assessment traced it to the planning run instead.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"302:1-302:314;18053-18366\">The Freight Units were correctly built and fully able to consolidate. The planning engine could not combine them because the delivery time windows \u2014 taken rigidly from requested delivery dates on the sales orders \u2014 did not overlap, even when the physical delivery could easily have happened within a wider window.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"304:1-304:249;18368-18616\">Before anything could be configured, the business had to settle an explicit rule: deliveries for the same customer and destination could be planned together as long as the requested windows fell within the same calendar day and a \u00b13 hour tolerance.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"306:1-306:232;18618-18849\">With that decision made, the planning profile&#8217;s time window constraint was relaxed to allow consolidation across Freight Units whose windows overlapped within that tolerance \u2014 without changing any SD or Freight Unit Building logic.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"308:1-308:32;18851-18882\"><strong>Results within one quarter:<\/strong><\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"310:1-312:77;18884-19090\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"310:1-310:56;18884-18939\">The daily manual regrouping step disappeared entirely<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"311:1-311:74;18940-19013\">Regional Freight Orders dropped by 34% against the same delivery volume<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"312:1-312:77;19014-19090\">The planning team recovered over 20 hours per week of hand-correction time<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"314:1-314:510;19092-19601\"><em>A note for teams on newer releases:<\/em> there is now a second route to this kind of problem. TM-based scheduling for sales orders calculates loading, transport and unloading times and returns confirmed delivery dates. That can produce more realistic delivery windows at order entry, instead of correcting unrealistic ones later in planning. It does not replace the business decision above \u2014 you still have to agree what &#8220;can travel together&#8221; means \u2014 but it can stop the problem being created in the first place.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"318:1-318:30;19608-19637\">Frequently asked questions<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"320:1-321:306;19639-19996\"><strong>Why is SAP TM creating too many Freight Orders?<\/strong> Usually because the planning run cannot combine the Freight Units it was given. The most common blockers are delivery time windows that don&#8217;t overlap, incompatibility settings, capacity limits, missing transportation lanes, or selection settings that never bring the right Freight Units into the same run.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"323:1-324:224;19998-20292\"><strong>Why are my Freight Units not consolidating into one Freight Order?<\/strong> If the Freight Units themselves look correct, the constraint is in planning, not in Freight Unit Building. Check whether they were even selected into the same planning run first \u2014 that catches more cases than people expect.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"326:1-327:269;20294-20646\"><strong>How do I know if the problem is SD delivery splitting or Freight Unit Building?<\/strong> Take one real example and follow it. If two deliveries exist where the business expected one, look at the delivery split criteria. If one delivery produced several Freight Units, look at the Freight Unit Building Rule. If both look correct, the problem is in planning.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"329:1-330:222;20648-20926\"><strong>Why does one delivery create multiple Freight Units?<\/strong> Because the Freight Unit Building Rule is splitting by criteria the business did not intend \u2014 by item, by product, or by a split quantity. Check the strategy and the split quantities in the rule that was actually applied.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"332:1-333:195;20928-21175\"><strong>Two similar deliveries behaved differently. Why?<\/strong> Freight Unit Building Rules can be found by condition. Two deliveries that look identical to a business user can be handled by two different rules, and nothing on the delivery itself shows this.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"335:1-336:259;21177-21501\"><strong>Should Freight Unit Building run automatically or as a batch?<\/strong> It depends what you need. Automatic creation on delivery save is the common setup, but it cannot consolidate across deliveries, because the other deliveries have not arrived yet. Cross-document consolidation at this stage needs batch or interactive creation.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"338:1-339:171;21503-21731\"><strong>What blocks consolidation in the SAP TM planning run?<\/strong> Time windows that don&#8217;t overlap, incompatibilities, vehicle capacity limits, missing or wrong transportation lanes, selection settings, and planning profile restrictions.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"341:1-342:175;21733-21971\"><strong>Can a newer S\/4HANA release fix delivery grouping problems?<\/strong> Newer releases add useful controls, but they do not remove the cause. SD and TM still group for different reasons, and the three layers still have to be aligned deliberately.<\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"346:1-346:24;21978-22001\">How SCM CHAMPS helps<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"348:1-348:252;22003-22254\">Most companies dealing with this don&#8217;t need a new SAP TM implementation. They need to know <strong>which of the three layers is actually producing the wrong result<\/strong> \u2014 and that needs an end-to-end look at the process, not a look at one configuration object.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"350:1-350:189;22256-22444\">SCM CHAMPS helps organisations work out whether the gap sits in the delivery logic, in Freight Unit Building, or in transportation planning \u2014 and then decide what actually needs to change.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"352:1-352:28;22446-22473\">That work typically covers:<\/p>\n<ul class=\"[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1\" dir=\"ltr\" data-sourcepos=\"354:1-360:75;22475-22885\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"354:1-354:56;22475-22530\">Assessment of current SAP TM transportation processes<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"355:1-355:29;22531-22559\">SD-to-TM process alignment<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"356:1-356:72;22560-22631\">Analysis of delivery split, Freight Unit Building, and planning logic<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"357:1-357:74;22632-22705\">Identifying where the transportation plan diverges from business intent<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"358:1-358:60;22706-22765\">Identifying manual consolidation and planning workarounds<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"359:1-359:45;22766-22810\">Evaluating SAP TM automation opportunities<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"360:1-360:75;22811-22885\">Turning business transportation requirements into practical improvements<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"362:1-362:172;22887-23058\">The goal isn&#8217;t simply to change how SAP creates Freight Units. It is to make sure the transportation planning logic reflects how the business actually needs to move goods.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"364:1-364:119;23060-23178\"><strong>Not sure whether your problem comes from SD delivery splitting, Freight Unit Building, or the planning run itself?<\/strong><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"366:1-366:125;23180-23304\"><a href=\"https:\/\/www.businesswire.com\/news\/home\/20260627456050\/en\/SCM-Champs-Inc.-Earns-SAP-Partner-Recognition-Strengthening-End-to-End-Supply-Chain-Services\" target=\"_blank\" rel=\"noopener\"><strong>SCM CHAMPS<\/strong><\/a> can assess the end-to-end process, find the underlying gap, and show you where the improvement opportunities are.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"368:1-368:39;23306-23344\"><strong>\u2192 <a href=\"https:\/\/www.scmchamps.com\/contact-us\">Request a Free SAP TM Assessment<\/a><\/strong><\/p>\n<h2 class=\"mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"372:1-372:16;23351-23366\">The real fix<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"374:1-374:134;23368-23501\">Incorrect delivery grouping is not really a configuration issue. It is a sign that four layers have stopped agreeing with each other:<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"376:1-376:95;23503-23597\"><strong>Business requirement \u2192 SD delivery logic \u2192 Freight Unit Building \u2192 Transportation Planning<\/strong><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"378:1-378:219;23599-23817\">When they agree, the plan comes out the way the business expects and nobody thinks about it. When they don&#8217;t, planners compensate by hand \u2014 and because they are good at it, the underlying gap can stay hidden for years.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"380:1-380:208;23819-24026\">The goal is a transportation process where the delivery logic, the Freight Unit logic, and the planning logic all support the same thing: how the business actually wants to consolidate, plan, and move goods.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"382:1-382:77;24028-24104\">That usually starts with finding out which layer stopped agreeing, and when.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If SAP TM is creating too many Freight Orders and your planners are regrouping deliveries&#8230;<\/p>\n","protected":false},"author":1,"featured_media":2144,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[344,354,7,12,355,75],"class_list":["post-2143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sap-tm","tag-freight-unit-building","tag-sap-delivery-split","tag-sap-tm","tag-sap-transportation-management","tag-shipment-consolidation","tag-transportation-planning"],"_links":{"self":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2143","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=2143"}],"version-history":[{"count":6,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2143\/revisions"}],"predecessor-version":[{"id":2203,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/posts\/2143\/revisions\/2203"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/media\/2144"}],"wp:attachment":[{"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/media?parent=2143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/categories?post=2143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scmchamps.com\/blog\/wp-json\/wp\/v2\/tags?post=2143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}