{"id":1979,"date":"2026-07-21T13:47:23","date_gmt":"2026-07-21T13:47:23","guid":{"rendered":"https:\/\/www.scmchamps.com\/sap-fixes\/?p=1979"},"modified":"2026-07-23T10:24:20","modified_gmt":"2026-07-23T10:24:20","slug":"sap-cross-delivery-handling-units-asr","status":"publish","type":"post","link":"https:\/\/www.scmchamps.com\/sap-fixes\/sap-cross-delivery-handling-units-asr\/","title":{"rendered":"Cross-Delivery Handling Units in SAP Advanced Shipping &#038; Receiving (ASR)"},"content":{"rendered":"<h3 class=\"text-text-100 mt-2 -mb-1 text-base font-bold\" dir=\"ltr\" data-sourcepos=\"2:1-2:86;75-160\">Improving Outbound Freight Consolidation Through Unified Handling Unit Processing<\/h3>\n<div class=\"overflow-x-auto w-full px-2 mb-6 print:overflow-x-visible\" dir=\"ltr\" data-sourcepos=\"4:1-10:57;162-726\">\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\"><\/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\"><\/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\"><strong>Client Industry<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Texas-based third-party logistics provider (3PL) specializing in outbound consolidation of automotive parts and industrial components for maquiladora supply chains (client anonymized under NDA)<\/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\"><strong>SAP Landscape<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">SAP S\/4HANA 2023 \u00b7 Embedded EWM \u00b7 Embedded Transportation Management \u00b7 Advanced Shipping &amp; Receiving (ASR)<\/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\"><strong>Scope<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Cross-Delivery Handling Unit enablement within the existing outbound ASR process<\/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\"><strong>Implementation Partner<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">SCM Champs<\/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\"><strong>Region<\/strong><\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Texas, USA \u2014 Dallas\u2013Fort Worth &amp; Laredo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"14:1-14:30;733-762\">Business Value at a Glance<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"15:1-15:120;763-882\"><em>A one-page summary for readers who need the essentials before reading further. It also works as a standalone handout.<\/em><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"17:1-17:23;884-906\"><strong>Business Challenge<\/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=\"18:1-20:99;907-1147\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"18:1-18:74;907-980\">Single physical pallets held product from multiple outbound deliveries.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"19:1-19:68;981-1048\">Standard processing forced a separate Handling Unit per delivery.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"20:1-20:99;1049-1147\">Duplicate dock touches, wasted trailer floor space, and rising detention on the DFW\u2013Laredo lane.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"22:1-22:17;1149-1165\"><strong>SAP Solution<\/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=\"23:1-25:84;1166-1422\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"23:1-23:79;1166-1244\">Cross-Delivery Handling Units enabled within the existing ASR outbound flow.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"24:1-24:94;1245-1338\">One Handling Unit spanning multiple Outbound Deliveries under a shared consolidation group.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"25:1-25:84;1339-1422\">The TM Freight Order remains the single orchestrating document across EWM and TM.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"27:1-27:68;1424-1491\"><strong>Business Outcomes<\/strong> (DFW\u2013Laredo lane, first 8 weeks post-go-live)<\/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=\"28:1-30:87;1492-1675\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"28:1-28:42;1492-1533\">Trailer utilization up from 67% to 88%.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"29:1-29:55;1534-1588\">Handling Units per shipment down ~40% (18.4 \u2192 11.2).<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"30:1-30:87;1589-1675\">Freight cost per shipment down ~20%; prep and loading times each down about a third.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"32:1-32:28;1677-1704\"><strong>SCM Champs Contribution<\/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=\"33:1-35:66;1705-1903\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"33:1-33:65;1705-1769\">Solution design and EWM\u2013TM integration for Cross-Delivery HUs.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"34:1-34:68;1770-1837\">BAdI-based consolidation-group validation (explicit enhancement).<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"35:1-35:66;1838-1903\">Testing, user training, cutover, and hypercare through go-live.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"37:1-37:213;1905-2117\"><strong>Snapshot<\/strong> \u2014 Industry: Automotive-parts 3PL \u00b7 SAP Scope: Embedded EWM + TM + ASR \u00b7 Warehouses: 2 (DFW + Laredo) \u00b7 Duration: 4.5 months \u00b7 Team: 4 FTE \u00b7 Result: trailer fill 67% \u2192 88%, ~40% fewer HUs per shipment<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"41:1-41:21;2124-2144\">Executive Summary<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"43:1-43:281;2146-2426\">The client is a Texas-based third-party logistics provider (3PL) operating on the Dallas\u2013Fort Worth\u2013to\u2013Laredo corridor, one of the busiest cross-border freight lanes in the United States. (Its full profile \u2014 sites, volumes, and SAP landscape \u2014 appears in Client Background below.)<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"45:1-45:317;2428-2744\">The business problem was rooted in daily warehouse reality. Operators frequently built a single physical pallet that carried product belonging to three or four different outbound deliveries destined for the same shipment \u2014 but standard outbound processing required each delivery to sit on its own Handling Unit (HU).<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"47:1-47:265;2746-3010\">The result was duplicated warehouse work \u2014 building, labeling, moving, and loading multiple pallets where one would do \u2014 along with wasted trailer floor space and higher detention charges on the long DFW-to-Laredo leg that feeds tightly scheduled border crossings.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"49:1-49:503;3012-3514\">The solution was to enable Cross-Delivery Handling Units within the client&#8217;s existing, stable Advanced Shipping &amp; Receiving (ASR) process. A Cross-Delivery HU allows items from more than one Outbound Delivery to be packed into a single HU while each delivery retains its own document integrity. The TM Freight Order continued to act as the single orchestrating document across <a href=\"https:\/\/www.openpr.com\/news\/4574470\/how-to-choose-the-right-sap-ewm-partner-specialist-vs-giant\" target=\"_blank\" rel=\"noopener\"><strong>Extended Warehouse Management (EWM)<\/strong><\/a> and Transportation Management (TM), so no parallel objects or middleware were introduced.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"51:1-51:287;3516-3802\">The business impact is detailed in the Results section below. Operators now consolidate multiple deliveries onto a single Handling Unit \u2014 the way they always did physically \u2014 so a shipment that once required several separate units moves through packing, loading, and Goods Issue as one.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"53:1-53:276;3804-4079\">SCM Champs delivered this outcome end to end \u2014 assessment, design, EWM and TM configuration, testing, training, cutover, and hypercare \u2014 almost entirely through standard SAP functionality, with a single, clearly identified BAdI enhancement for consolidation-group validation.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"55:1-55:206;4081-4286\">The engagement ran 4.5 months from kickoff to go-live, including a two-week hypercare window, delivered by a four-FTE SCM Champs team working alongside client-side EWM and logistics subject-matter experts.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"59:1-59:21;4293-4313\">Client Background<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"61:1-61:551;4315-4865\">The client is a third-party logistics provider specializing in the outbound consolidation of automotive parts and industrial components for maquiladora supply chains, operating in one of the busiest freight corridors in the United States. Its network is built around two distribution centers: a 250,000-square-foot domestic consolidation hub in the Dallas\u2013Fort Worth metroplex, and a 120,000-square-foot cross-dock and transload facility in Laredo that handles border-crossing freight destined for maquiladoras and automotive supply chains in Mexico.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"63:1-63:545;4867-5411\">The distribution model is almost entirely business-to-business. It mixes full-truckload consolidation with multi-customer less-than-truckload (LTL) shipments, and the Laredo site plays a specialized role in staging and transloading freight for cross-border movement. Combined daily volume runs between 600 and 900 outbound orders, drawn from an active base of about 18,000 SKUs with a wide range of pack profiles \u2014 palletized goods, crates, and loose cartons. Warehouse headcount is approximately 140 floor associates and supervisors per shift.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"65:1-65:515;5413-5927\">The SAP landscape is SAP S\/4HANA 2023 (on-premise), running Embedded EWM and embedded Transportation Management on the same S\/4HANA instance. This co-deployment is a prerequisite for Advanced Shipping &amp; Receiving, which the client had been running in production for its outbound shipping processes for roughly 18 months before this project began. The Cross-Delivery Handling Unit capability was therefore introduced as a targeted addition to a mature and stable ASR foundation, not as part of a new implementation.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"69:1-69:42;5934-5975\">Business Challenge \/ Problem Statement<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"71:1-71:307;5977-6283\">Picture the dock on a typical afternoon. A loader is staging freight for a Laredo-bound trailer, and in front of him sit three pallets that, by every physical measure, should be one. The cartons are the same size, they are going to the same place, and they would nest together perfectly on a single pallet.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"73:1-73:339;6285-6623\">But the system will not let him treat them as one unit \u2014 because the product on those cartons belongs to three different Outbound Deliveries. So he builds three pallets, labels three pallets, moves three pallets, and loads three pallets. Multiply that by a trailer, by a shift, by 600 to 900 orders a day, and the pattern is unmistakable.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"75:1-75:446;6625-7070\">This is not an edge case for the client \u2014 it is the core of the business. Because its value proposition is consolidation, it is routine for a single shipment, particularly one bound for a border crossing, to combine goods from several manufacturers and several Outbound Deliveries. Operators naturally want to place product from three or four deliveries onto one physical pallet, because that is the most space-efficient way to fill the trailer.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"77:1-77:202;7072-7273\">Standard outbound processing, however, did not permit one Handling Unit to span multiple deliveries. Each delivery had to be packed into its own HU. That single constraint rippled across the operation:<\/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=\"79:1-82:168;7275-7841\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"79:1-79:127;7275-7401\">Operators built and labeled multiple Handling Units for what was physically a single pallet, adding avoidable packing steps.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"80:1-80:124;7402-7525\">Every additional HU meant additional dock touches \u2014 moving, staging, and loading units that could have been consolidated.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"81:1-81:148;7526-7673\">Trailer floor space was used inefficiently, because the packing pattern was driven by system constraints rather than by how freight actually fit.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"82:1-82:168;7674-7841\">On the long DFW-to-Laredo leg, slower loading and lower trailer utilization added pressure on tightly scheduled cross-border departures and increased detention risk.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"84:1-84:510;7843-8352\"><strong>The cost of doing nothing.<\/strong> This was a recurring cost, not a one-time problem \u2014 every consolidation pallet forced into three units doubled or tripled the handling effort for zero operational benefit, and that cost scaled with volume as the business grew. In short, the warehouse was absorbing the cost of a document-level limitation with physical labor and wasted capacity. The client needed the system to model what the dock was already doing physically: one pallet, several deliveries, one Handling Unit.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"88:1-88:30;8359-8388\">Project Objectives &amp; Scope<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"90:1-90:15;8390-8404\"><strong>Objectives<\/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=\"91:1-95:110;8405-8919\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"91:1-91:120;8405-8524\">Simplify outbound warehouse execution by allowing one Handling Unit to carry items from multiple Outbound Deliveries.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"92:1-92:94;8525-8618\">Improve loading efficiency and trailer utilization on consolidation and cross-border lanes.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"93:1-93:86;8619-8704\">Reduce manual Handling Unit handling \u2014 fewer units to build, label, move, and load.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"94:1-94:105;8705-8809\">Enable unified shipment execution while preserving the document integrity of each individual delivery.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"95:1-95:110;8810-8919\">Achieve the above using standard ASR capability wherever possible, with any enhancement clearly identified.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"97:1-97:14;8921-8934\"><strong>In scope:<\/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=\"98:1-101:76;8935-9234\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"98:1-98:77;8935-9011\">SAP S\/4HANA 2023 with Embedded EWM and embedded Transportation Management.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"99:1-99:61;9012-9072\">Advanced Shipping &amp; Receiving (ASR) outbound process only.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"100:1-100:86;9073-9158\">Cross-Delivery Handling Unit enablement, configuration, and integration validation.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"101:1-101:76;9159-9234\">One BAdI-based consolidation-group validation in the packing work center.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"103:1-103:18;9236-9253\"><strong>Out of scope:<\/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=\"104:1-106:81;9254-9475\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"104:1-104:68;9254-9321\">Inbound and returns processing \u2014 not affected by this engagement.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"105:1-105:73;9322-9394\">Greenfield ASR setup \u2014 the ASR foundation was already live and stable.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"106:1-106:81;9395-9475\">Transportation planning redesign, carrier tendering logic, and Yard Logistics.<\/li>\n<\/ul>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"110:1-110:33;9482-9514\">SAP Standard Process Overview<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"112:1-112:250;9516-9765\">Before describing what SCM Champs configured, it is worth establishing how Cross-Delivery Handling Units behave in the standard Advanced Shipping &amp; Receiving process \u2014 because the capability is delivered SAP standard functionality, not custom logic.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"114:1-114:508;9767-10274\">A Cross-Delivery Handling Unit is a single packing unit, such as a carton or pallet, that contains products originating from more than one Outbound Delivery. Where standard packing associates an HU with a single delivery, a Cross-Delivery HU is recognized by the system as spanning several deliveries and is flagged accordingly in the relevant EWM screens (identified as a Cross-D HU). Each contributing delivery keeps its own identity and document flow; the HU simply becomes the shared physical container.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"116:1-116:47;10276-10322\">Two standard prerequisites govern the process:<\/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=\"118:1-119:243;10324-10758\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"118:1-118:192;10324-10515\"><strong>Shared consolidation group<\/strong> \u2014 all deliveries packed into the same Cross-Delivery HU must belong to the same consolidation group; otherwise the system prevents the cross-delivery packing.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"119:1-119:243;10516-10758\"><strong>Joint readiness<\/strong> \u2014 the deliveries sharing a Cross-Delivery HU must be set to &#8220;Ready for Shipping&#8221; together. Because they share one physical HU, selecting only one of them for that step results in an error; all must be processed as a set.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"121:1-121:387;10760-11146\">Within ASR, the packed HU is reflected against the Freight Order in Transportation Management, which remains the single orchestrating document. The HU is then loaded and Goods Issue is posted. Cross-Delivery Handling Units are supported as part of the standard ASR process in SAP S\/4HANA releases that include this capability; this project used that standard behavior as its foundation.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"125:1-125:21;11153-11173\">Solution Approach<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"127:1-127:441;11175-11615\">The approach was deliberately incremental. Because the client already ran a stable ASR outbound process, the goal was not to re-architect anything but to extend the existing flow so that consolidation pallets could be modeled as they physically existed. The design keeps the Freight Order as the single orchestrating document and layers Cross-Delivery HU behavior into the packing step, where the consolidation actually happens on the dock.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"129:1-129:22;11617-11638\"><strong>Why this approach<\/strong><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"131:1-131:82;11640-11721\">Before committing to Cross-Delivery HUs, the realistic alternatives were weighed:<\/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=\"133:1-136:256;11723-12503\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"133:1-133:125;11723-11847\"><strong>Live with it.<\/strong> The path of least effort, but it meant permanently accepting the ongoing cost described above. Rejected.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"134:1-134:197;11848-12044\"><strong>Throw labor at it.<\/strong> More associates could move the extra pallets faster, but this treats the symptom, scales cost with volume, and does nothing for trailer utilization or detention. Rejected.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"135:1-135:203;12045-12247\"><strong>Redesign the outbound process or build custom logic.<\/strong> A heavier, higher-risk route that would disturb a stable production system and introduce custom code to maintain. Rejected as disproportionate.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"136:1-136:256;12248-12503\"><strong>Enable Cross-Delivery Handling Units on the existing ASR foundation.<\/strong> This models the dock reality directly, uses delivered SAP standard functionality, keeps the Freight Order as the single source of truth, and requires no parallel objects. Selected.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"138:1-138:301;12505-12805\">The deciding factor was simple: the physical process was already correct, so the lowest-risk route was to let the system represent what the dock was doing rather than rebuild anything. Cross-Delivery HUs did exactly that using standard capability \u2014 the least disruption for the highest-value outcome.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"140:1-140:401;12807-13207\">At the level of business flow, the end-to-end process connects as follows. The critical point is the packing step: freight planning and delivery creation continue exactly as before, and the Cross-Delivery HU is formed during packing, after picking, when operators consolidate multiple deliveries onto one physical unit. From there, the single HU \u2014 not several \u2014 moves through loading and Goods Issue.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"144:1-144:40;13214-13253\">SAP Solution Design &amp; Implementation<\/h2>\n<blockquote class=\"ml-2 border-l-4 border-[hsl(var(--border-300)\/0.1)] pl-4 text-text-300\" data-sourcepos=\"146:1-146:222;13255-13476\">\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"146:3-146:222;13257-13476\"><strong>Standard SAP Capability<\/strong> \u2014 Unless explicitly identified as an enhancement, all solution components described in this case study were implemented using standard SAP S\/4HANA Advanced Shipping &amp; Receiving functionality.<\/p>\n<\/blockquote>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"148:1-148:561;13478-14038\"><strong>ASR integration model.<\/strong> The client&#8217;s outbound ASR integration was already configured through the TM\u2013EWM integration model, using the relevant Shipping Point (location type 1003) and Loading Point (location type 1200) business locations. These participate in the integration model and are among the settings that make a location relevant for ASR \u2014 part of the configuration, not on their own the entire activation. Because ASR was already live, the project verified that the existing model supported the Cross-Delivery HU flow rather than re-establishing it.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"150:1-150:1072;14040-15111\"><strong>Consolidation group and Handling Unit design.<\/strong> The heart of the design is the consolidation group. Since a Cross-Delivery HU may only span deliveries that share a consolidation group, the work centered on making that grouping automatic and consistent. In SPRO, under Define Consolidation Group Determination, a derivation rule was set to pull the TM Freight Order number as the consolidation group for every delivery belonging to the same shipment \u2014 so all deliveries planned onto one Freight Order were, by definition, eligible to share a Handling Unit. Packing was performed through transaction \/SCWM\/PACK (Pack Outbound Deliveries profile), surfaced to operators via a Fiori tile, Pack Handling Units \u2013 Cross Delivery (a custom tile built on the standard catalog). The HU was then created to hold items across those deliveries, with the system recognizing and flagging it as a Cross-Delivery HU. In practice, 2 to 4 outbound deliveries were consolidated per HU; the largest observed in the first month was 7 deliveries on a single oversized automotive-crate pallet.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"152:1-152:518;15113-15630\"><strong>Freight Order integration and document flow.<\/strong> Throughout, the TM Freight Order remained the single orchestrating document. The packed Cross-Delivery HU was reflected against the Freight Order, so TM retained an accurate picture of what was physically on the truck without duplicated or parallel objects. The deliveries sharing the HU were set to &#8220;Ready for Shipping&#8221; together, the HU was loaded against the Freight Order, and Goods Issue was posted \u2014 with the document flow updating consistently across EWM and TM.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"154:1-154:548;15632-16179\"><strong>Enhancement (Custom).<\/strong> A single BAdI-based validation was implemented in the packing work center. The BAdI <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">\/SCWM\/EX_CORE_PACK_VAL<\/code>, method <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">CHECK_CROSS_DELIVERY_CG<\/code> (implementation <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">ZSCM_CROSS_DLV_CG_CHECK<\/code>), validates consolidation-group alignment across the deliveries assigned to the same Freight Order at the moment of HU assignment \u2014 so misaligned deliveries are caught early rather than surfacing later as a &#8220;Ready for Shipping&#8221; error. This is the only custom component in the solution; every other element is standard ASR functionality.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"156:1-156:767;16181-16947\">The rationale for the enhancement was operational, not technical. Standard behavior correctly prevents an invalid Cross-Delivery HU, but does so downstream \u2014 at the readiness step \u2014 by which point operators may already have packed the pallet. Validating consolidation-group alignment during packing shifts the check to the moment of the decision, where a floor associate can act on it without rework. In practice, the mismatch the BAdI catches is not the routine case where every delivery already sits on the same Freight Order \u2014 it is the exception, such as a delivery that had not yet been assigned to that Freight Order at the moment the operator started packing, or a late re-plan that moved a delivery onto a different order after packing was already under way.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"158:1-158:71;16949-17019\"><em>Figure 1 \u2014 System Architecture (co-deployed on one S\/4HANA instance)<\/em><\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"160:1-160:275;17021-17295\">Because EWM and TM are co-deployed on the same S\/4HANA instance, Freight Order data is directly available to warehouse execution without replication into a separate EWM transportation object \u2014 the foundation on which ASR, and therefore Cross-Delivery HU processing, depends.<\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"164:1-164:33;17302-17334\">Challenges Faced &amp; Mitigation<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"166:1-166:187;17336-17522\">The engagement was an enhancement to a live production system, which raised specific risks around data consistency, user behavior, and process stability. Each was addressed deliberately.<\/p>\n<div class=\"overflow-x-auto w-full px-2 mb-6 print:overflow-x-visible\" dir=\"ltr\" data-sourcepos=\"168:1-173:270;17524-18796\">\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\">Challenge<\/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\">SCM Champs Mitigation<\/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\">Maintaining Handling Unit consistency across multiple Outbound Deliveries sharing one HU.<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Warehouse execution rules were designed to align with the ASR document flow, keeping HU content and delivery references consistent through packing, loading, and Goods Issue.<\/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\">Consolidation-group misalignment surfacing only as a downstream &#8220;Ready for Shipping&#8221; error.<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">A BAdI-based validation (the engagement&#8217;s single enhancement, <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">\/SCWM\/EX_CORE_PACK_VAL<\/code> \u2192 <code class=\"bg-text-200\/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]\">CHECK_CROSS_DELIVERY_CG<\/code>) was added in the packing work center to catch misaligned deliveries at the moment of HU assignment, before the error could occur.<\/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\">Warehouse operators unfamiliar with the Cross-Delivery HU process on a live system.<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">Hands-on warehouse simulation was run before go-live for 36 warehouse associates (12 per shift across three shifts at DFW) plus 4 Laredo cross-dock leads, walking them through building, labeling, and setting deliveries to Ready for Shipping as a set.<\/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\">Introducing change into a stable production ASR process without disrupting daily throughput.<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">End-to-end ASR scenario testing was performed rather than isolated task testing, and a phased go-live (April 14, 2026) with two-week hypercare protected daily order flow.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<hr class=\"border-border-200 border-t-0.5 my-3 mx-1.5\" \/>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"177:1-177:31;18803-18833\">Results &amp; Business Benefits<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"179:1-179:222;18835-19056\">On the floor, the change was immediate and visible: where an operator once built three pallets for one consolidated shipment, he now builds one \u2014 and the loaders stopped shuffling half-empty units to make the freight fit.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"181:1-181:498;19058-19555\">That is the shift in a sentence. The pallet that always should have been one unit finally is one unit, and every downstream step inherits the simplification. Before, a consolidated shipment generated a separate Handling Unit per delivery, each demanding its own labeling, movement, staging, and loading. After, a single Cross-Delivery HU carries those same deliveries as one physical unit and moves through readiness, loading, and Goods Issue exactly once. The benefits fall into three categories.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"183:1-183:25;19557-19581\"><strong>Operational benefits<\/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=\"184:1-186:87;19582-19842\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"184:1-184:103;19582-19684\">Fewer Handling Units built per consolidated shipment, since one HU can now span multiple deliveries.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"185:1-185:71;19685-19755\">Reduced dock handling \u2014 fewer units to label, move, stage, and load.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"186:1-186:87;19756-19842\">Packing patterns driven by how freight physically fits, not by document constraints.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"188:1-188:22;19844-19865\"><strong>Business benefits<\/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=\"189:1-191:66;19866-20111\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"189:1-189:71;19866-19936\">Faster shipment preparation on consolidation and cross-border lanes.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"190:1-190:109;19937-20045\">Improved trailer utilization, easing pressure on the DFW-to-Laredo leg and its scheduled border crossings.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"191:1-191:66;20046-20111\">Reduced exposure to detention charges caused by slower loading.<\/li>\n<\/ul>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"193:1-193:20;20113-20132\"><strong>System benefits<\/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=\"194:1-196:79;20133-20410\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"194:1-194:96;20133-20228\">The Freight Order remains the single orchestrating document \u2014 no parallel objects introduced.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"195:1-195:103;20229-20331\">Consistent document flow and visibility across EWM and TM through packing, loading, and Goods Issue.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"196:1-196:79;20332-20410\">Earlier error prevention at packing, reducing downstream readiness failures.<\/li>\n<\/ul>\n<blockquote class=\"ml-2 border-l-4 border-[hsl(var(--border-300)\/0.1)] pl-4 text-text-300\" data-sourcepos=\"198:1-199:56;20412-20682\">\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"198:3-199:56;20414-20682\">&#8220;For the first time, the screen matched the dock. We used to apologize to the system while we built the pallet anyway. Now the system works the way we do \u2014 one good pallet instead of three that don&#8217;t make sense.&#8221; \u2014 Warehouse Operations Manager, DFW Consolidation Hub<\/p>\n<\/blockquote>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"201:1-201:330;20684-21013\"><strong>Measured outcomes.<\/strong> The figures below compare an identical shipment profile \u2014 consolidated LTL trailers on the DFW\u2013Laredo lane \u2014 across the first eight weeks after cutover. The client has cleared them for publication on the condition that the end-manufacturers whose product sits inside the consolidated pallets are not named.<\/p>\n<div class=\"overflow-x-auto w-full px-2 mb-6 print:overflow-x-visible\" dir=\"ltr\" data-sourcepos=\"203:1-209:47;21015-21350\">\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\">KPI<\/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\">Before (Mar 2026)<\/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\">After (Jun 2026)<\/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\">Trailer Utilization (floor-loaded, Laredo lane)<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">67%<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">88%<\/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\">Average HUs per Shipment<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">18.4<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">11.2<\/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\">Shipment Preparation Time (mean)<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">47 min<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">29 min<\/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 Cost per Shipment (net, excl. fuel)<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">$1,842<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">$1,470<\/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\">Dock Loading Time (mean)<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">52 min<\/td>\n<td class=\"border-b-0.5 border-[hsl(var(--border-300)\/0.3)] py-2 pr-4 align-top\">34 min<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"211:1-211:581;21352-21932\">The pattern is consistent across every measure: Handling Unit count per shipment dropped roughly 40%, trailer fill rose more than 20 percentage points, and both shipment-preparation and dock-loading times improved by about a third. In cost terms, that is a reduction of $372 in net freight cost per shipment \u2014 about 20% \u2014 on a lane the client runs repeatedly. The same consolidation freed dock labor and trailer capacity that had previously been consumed building and moving redundant Handling Units, so the per-shipment saving is compounded by throughput the operation recovered.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"213:1-213:540;21934-22473\"><strong>Industry context \u2014 the size of the opportunity.<\/strong> For external perspective, published logistics data shows why outbound consolidation matters. U.S. industry studies put average trailer utilization at roughly 60\u201380%, and Flock Freight&#8217;s 2025 Shipper Research Study found that 58% of truckloads moved with empty trailer space in 2024 \u2014 up from 43% a year earlier.\u00b9 Consolidation programs that fill trailers more completely are consistently reported to reduce handling touches and deliver double-digit improvements in equipment utilization.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"215:1-215:117;22475-22591\"><em>These figures are industry benchmarks for freight consolidation generally \u2014 not measurements from this engagement.<\/em><\/p>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"219:1-219:36;22598-22633\">Lessons Learned &amp; Best Practices<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"221:1-221:138;22635-22772\">Several practical lessons emerged that transfer to any organization enabling Cross-Delivery Handling Units on an existing ASR foundation.<\/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=\"223:1-228:231;22774-24035\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"223:1-223:240;22774-23013\"><strong>Validate the warehouse process before enabling Cross-Delivery HUs.<\/strong> The capability is only as good as the consolidation-group discipline behind it; confirm that deliveries for a shipment can reliably share a consolidation group first.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"224:1-224:174;23014-23187\"><strong>Stabilize transportation planning before extending warehouse execution.<\/strong> A mature, stable ASR foundation made this a low-risk enhancement rather than a re-architecture.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"225:1-225:170;23188-23357\"><strong>Keep Handling Unit management aligned with shipment execution.<\/strong> HU content and delivery references must stay consistent all the way through loading and Goods Issue.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"226:1-226:198;23358-23555\"><strong>Test end-to-end ASR scenarios, not just individual warehouse tasks.<\/strong> The value \u2014 and the risks \u2014 of Cross-Delivery HUs appear at the seams between packing, readiness, loading, and Goods Issue.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"227:1-227:249;23556-23804\"><strong>Train users on the full document flow.<\/strong> Operators work far more confidently once they understand how Deliveries, Freight Orders, and Handling Units relate \u2014 especially the rule that shared deliveries must be set to Ready for Shipping together.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"228:1-228:231;23805-24035\"><strong>Shift error prevention upstream where it helps the floor.<\/strong> Moving the consolidation-group check to the packing step, via a targeted enhancement, prevented rework that standard downstream validation would have caught too late.<\/li>\n<\/ul>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"232:1-232:18;24042-24059\">Why SCM Champs<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"234:1-234:404;24061-24464\">The result turned on diagnosis, not just delivery. Early on, SCM Champs reframed the problem in a way the client had not: this was a modeling gap, not a technology gap \u2014 the warehouse was already consolidating freight correctly; the system simply was not allowed to represent it. That single distinction shaped every decision that followed, and it is why the engagement delivered high value at low risk:<\/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=\"236:1-239:160;24466-25006\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"236:1-236:107;24466-24572\"><strong>Diagnosis over delivery<\/strong> \u2014 named the real problem (a modeling gap) before touching any configuration.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"237:1-237:151;24573-24723\"><strong>Standard SAP over custom<\/strong> \u2014 solved it with delivered functionality, adding only one clearly identified BAdI where it measurably helped operators.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"238:1-238:123;24724-24846\"><strong>Extend, don&#8217;t re-architect<\/strong> \u2014 built on an ASR foundation that had run cleanly for 18 months instead of disturbing it.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"239:1-239:160;24847-25006\"><strong>De-risk a live operation<\/strong> \u2014 proved the change on the warehouse floor through hands-on operator simulation and a phased cutover, not just in a test client.<\/li>\n<\/ul>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"243:1-243:38;25013-25050\">SCM Champs&#8217; Role &amp; Value Delivered<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"245:1-245:447;25052-25498\">SCM Champs delivered the engagement end to end with a four-FTE team \u2014 a part-time solution architect, two senior EWM\/TM consultants, a change-management and training lead, and a cutover coordinator \u2014 working alongside the client&#8217;s own <a href=\"https:\/\/www.openpr.com\/news\/4574470\/how-to-choose-the-right-sap-ewm-partner-specialist-vs-giant\" target=\"_blank\" rel=\"noopener\"><strong>EWM<\/strong><\/a> and logistics experts. The timeline ran 4.5 months from kickoff to an April 14, 2026 go-live, with two weeks of hypercare ending April 28, 2026 (on-site at DFW for the first three days, then remote on-call).<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"247:1-247:267;25500-25766\">The client began cautious about touching a stable, live system \u2014 and SCM Champs treated that caution as a design constraint, not an obstacle. By go-live it had turned into confidence, because the change had been proven on the floor rather than only in a test client.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"249:1-249:38;25768-25805\"><strong>Scope of work, in delivery order:<\/strong><\/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=\"251:1-256:118;25807-26585\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"251:1-251:99;25807-25905\"><strong>Assess<\/strong> \u2014 map the dock reality of consolidation pallets against the system&#8217;s HU constraints.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"252:1-252:138;25906-26043\"><strong>Design<\/strong> \u2014 the Cross-Delivery HU solution and consolidation-group handling on the existing ASR foundation, with no parallel objects.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"253:1-253:175;26044-26218\"><strong>Configure &amp; integrate<\/strong> \u2014 EWM and TM setup, plus the one custom BAdI, validated for consistent document flow with the Freight Order as the single orchestrating document.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"254:1-254:93;26219-26311\"><strong>Test<\/strong> \u2014 end-to-end SIT and UAT scenarios with warehouse operators, not isolated tasks.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"255:1-255:156;26312-26467\"><strong>Train<\/strong> \u2014 hands-on simulation for 36 DFW associates (12 per shift, three shifts) plus 4 Laredo cross-dock leads on the full Cross-Delivery HU process.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"256:1-256:118;26468-26585\"><strong>Cut over &amp; support<\/strong> \u2014 phased go-live on April 14, 2026 with two weeks of hypercare to protect daily throughput.<\/li>\n<\/ol>\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"260:1-260:31;26592-26622\">Conclusion &amp; Future Roadmap<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"262:1-262:667;26624-27290\">This engagement turned a persistent dock-level inefficiency into a modeled, repeatable process. By enabling Cross-Delivery Handling Units on a stable Advanced Shipping &amp; Receiving foundation, the client can now pack a single physical pallet the way its operators always did \u2014 spanning multiple Outbound Deliveries \u2014 while the system keeps each delivery&#8217;s integrity intact and the Freight Order remains the single orchestrating document. The technical achievement was to deliver this almost entirely through standard SAP functionality, with a single, clearly identified enhancement addressing where the standard error check landed relative to the operator&#8217;s workflow.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"264:1-264:258;27292-27549\">The result is fewer Handling Units per shipment, less dock handling, faster shipment preparation, and better trailer utilization on the consolidation and cross-border lanes that define this business \u2014 achieved without disrupting a live production operation.<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"266:1-266:19;27551-27569\"><strong>Future roadmap<\/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=\"267:1-270:118;27570-28087\">\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"267:1-267:145;27570-27714\">SAP Yard Logistics integration \u2014 extending visibility and control from the dock into the yard, particularly valuable at the Laredo cross-dock.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"268:1-268:122;27715-27836\">Advanced Shipping &amp; Receiving optimization \u2014 continuing to refine consolidation and readiness handling as volumes grow.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"269:1-269:133;27837-27969\">Transportation planning automation \u2014 tightening the link between warehouse execution and carrier scheduling on cross-border lanes.<\/li>\n<li class=\"font-claude-response-body whitespace-normal break-words pl-2\" data-sourcepos=\"270:1-270:118;27970-28087\">Warehouse analytics \u2014 surfacing HU, loading, and utilization metrics to sustain and measure continuous improvement.<\/li>\n<li data-sourcepos=\"270:1-270:118;27970-28087\">\n<h2 class=\"text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold\" dir=\"ltr\" data-sourcepos=\"293:1-293:24;29656-29679\">Work With SCM Champs<\/h2>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"295:1-295:58;29681-29738\">Facing similar consolidation challenges in SAP EWM or TM?<\/p>\n<p class=\"font-claude-response-body break-words whitespace-normal\" dir=\"ltr\" data-sourcepos=\"297:1-297:289;29740-30028\"><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> helps logistics teams unlock hidden efficiencies using standard SAP capabilities \u2014 without disrupting live operations. From outbound consolidation and Cross-Delivery Handling Units to end-to-end ASR integration, our focus is measurable outcomes on your existing SAP investment.<\/p>\n<\/li>\n<li data-sourcepos=\"270:1-270:118;27970-28087\"><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Improving Outbound Freight Consolidation Through Unified Handling Unit Processing Client Industry Texas-based third-party logistics provider&#8230;<\/p>\n","protected":false},"author":1,"featured_media":1980,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[293,292,291],"class_list":["post-1979","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sap-fixes","tag-advanced-shipping-receiving","tag-advanced-shipping-receiving-asr","tag-cross-delivery-handling-units"],"_links":{"self":[{"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/posts\/1979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/comments?post=1979"}],"version-history":[{"count":5,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/posts\/1979\/revisions"}],"predecessor-version":[{"id":1992,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/posts\/1979\/revisions\/1992"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/media\/1980"}],"wp:attachment":[{"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/media?parent=1979"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/categories?post=1979"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scmchamps.com\/sap-fixes\/wp-json\/wp\/v2\/tags?post=1979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}