SAP TM
How SCM Champs Helped a Construction Products Manufacturer Reduce Freight Costs by 8% with SAP TM
SAP TM project at a glance
A construction products manufacturer with 5 plants and 3 distribution centres replaced spreadsheet-based transportation planning with embedded
SAP Transportation Management in 7 months. Freight cost per shipment fell by 8%, and planners now spend 55% less time building loads.
| Project detail | Summary |
| Industry | Construction products manufacturing |
| Region | Southeast and Midwest USA |
| Sites | 5 plants and 3 distribution centres |
| Systems | SAP S/4HANA; embedded SAP EWM at 2 distribution centres |
| SAP TM scope | Advanced TM, embedded in S/4HANA, including the VSR optimiser |
| Freight profile | About 970 truckload and LTL shipments a week across 38 carriers |
| Timeline | 7 months to go-live in two waves, plus 6 weeks of hypercare |
| SCM Champs role | Assessment, design, implementation and hypercare |
| Headline results | Freight cost per shipment down 8%; planner time down 55%; freight invoice disputes down 60% |
| Freight cost per shipment | Planner time on transportation planning | Freight invoice disputes |
| 8% lower | 55% less | 60% fewer |
Why were transportation costs rising despite an established logistics operation?
The client ships roughly 4,200 truckload and LTL orders a month from 5 plants and 3 distribution centres, about 970 a week, to customers across the Southeast and Midwest. A network of 38 carriers moves that freight over about 600 lanes, at an annual freight spend of around $58 million. Until this project, 6 transportation planners built loads in spreadsheets, tendered them by email and phone, and checked carrier invoices one at a time.
Six symptoms stood out, and each had a different root cause.
| What the client experienced | Root cause |
| Rising freight cost per shipment, with little control over transportation spend | Rates sat in 41 spreadsheets and PDF contracts, so nobody had a single view of rates, lanes and carrier performance |
| Loads planned in spreadsheets and email | Planning was not system-driven, so consolidation depended on each plannerâs experience and average truck fill stood at 74% |
| Carriers chosen by habit instead of cost or performance | No central carrier and rate management; only about 55% of loads went to the lowest-cost eligible carrier |
| Poor coordination with carriers | Tenders and confirmations ran by email and phone, with no record of acceptance by lane |
| Limited visibility into shipment status and cost | Transportation data was spread across the ERP, spreadsheets and carrier portals, so delays usually surfaced when customers called |
| Slow, error-prone freight invoice checks | Freight cost was calculated by hand, and invoices were verified one by one: 10% were disputed, and settlement took 25 days |
What needed to change to bring freight costs under control with SAP TM
SCM Champs tied each problem to the SAP TM capability that would address it and the metric that would prove it worked. The same metrics are reported again in the results.
| Problem | SAP TM capability used | Metric tracked |
| Manual planning | Freight unit building, load consolidation and the VSR optimizer | Truck fill rate; planning time per planner per day |
| Carrier selection | Carrier selection rules with allocations; automated tendering | Loads awarded to the lowest-cost eligible carrier; first-tender acceptance rate |
| Freight cost control | Freight agreements and automatic charge calculation | Freight cost per shipment |
| Freight settlement | Freight settlement integrated with invoice verification | Invoice discrepancy rate; settlement cycle time |
| Shipment visibility | Execution tracking, carrier status events and reporting | On-time delivery; time to detect delays |
How SCM Champs set up SAP Transportation Management to improve freight planning and cost control
SCM Champs configured Advanced SAP TM embedded in the clientâs S/4HANA system, so deliveries, freight and finance data now sit on one platform. The table shows how each step of the process changed, and the sections below explain what was configured.
| Process step | Before | After |
| Order release | Planners pulled open deliveries into spreadsheets | Outbound deliveries from S/4HANA create freight units automatically |
| Load planning | Loads built by hand, plant by plant | Freight unit building rules and the VSR optimizer propose consolidated loads |
| Carrier selection | Preferred carrier chosen by habit | Selection rules rank eligible carriers by contracted cost, allocation and performance |
| Tendering | Email and phone | Electronic tender with automatic escalation to the next carrier |
| Execution | Status chased by phone | Carrier status events update each freight order |
| Settlement | Manual rate lookup and invoice-by-invoice checks | Charges calculated automatically; carrier invoices matched to freight settlement documents |
Transportation planning and load consolidation
Freight unit building rules convert every outbound delivery from S/4HANA into a freight unit, grouped by origin plant, ship-to region and requested delivery window. Planning profiles then control how the VSR optimizer builds loads across about 600 lanes and about 970 shipments a week. The optimizer proposes consolidated and multi-stop loads against vehicle capacity and delivery windows, and planners review the exceptions instead of building every load by hand. Average truck fill rose from 74% to 82%.
Carrier selection, tendering and freight agreements
SCM Champs loaded 52 freight agreements covering 38 carriers. Carrier selection rules rank eligible carriers by contracted cost, lane allocation and recent performance. Each load is tendered electronically to the top-ranked carrier as an EDI 204 load tender. If that carrier declines or does not respond within 2 hours, SAP TM escalates to the next carrier on the list. 32 of the 38 carriers respond by EDI 990; the other 6, all smaller carriers, use a web portal.
Freight cost calculation and settlement
Rate tables and calculation sheets hold base rates, fuel surcharges and accessorial charges by lane, so SAP TM calculates the expected cost of every freight order before the truck leaves. After delivery, a freight settlement document is created and posted to finance as an accrual. Carrier invoices arrive by EDI 210 and are matched to that document in invoice verification. Differences within a tolerance of 2% post automatically, and anything beyond that goes to a review queue.
Transportation execution and shipment visibility
Carriers send pickup, departure and delivery events by EDI 214, and SAP TM records them against each freight order. Planners see late pickups and at-risk deliveries as alerts, and the logistics team works from SAP Fiori apps that show on-time delivery, carrier scorecards and freight cost per shipment.
SAP TM integration with existing business systems
| System | Role |
| S/4HANA | Supplies sales orders and deliveries and receives accruals and invoice postings. |
| SAP EWM (2 distribution centres) | Embedded EWM uses the planned truck sequence to drive picking and loading. |
| Carrier EDI (204, 990, 214 and 210) | Messages run through the clientâs integration middleware. |
How SCM Champs delivered the SAP TM implementation
The project took 7 months from kickoff to the final go-live, inside the 5 to 8 months SCM Champs typically needs for a TM implementation of this scope, even with 5 plants rolled out in two waves. Hypercare added another 6 weeks.
| Phase | Duration | What SCM Champs did |
| Discover | 4 weeks | Reviewed freight processes, planning practices, carrier contracts and 12 months of cost data |
| Design | 6 weeks | Defined SAP TM scope, process changes, optimiser constraints and integration requirements |
| Build | 10 weeks | Configured planning, carrier management and freight settlement; built the EDI, S/4HANA and EWM integrations |
| Test | 6 weeks | Validated end-to-end processes and carrier data exchange with business users |
| Deploy | 4 weeks | Managed cutover, data migration and go-live: 2 plants in wave one, 3 plants two weeks later |
| Hypercare | 6 weeks | Resolved issues, supported planners and stabilised operations |
Key Challenge - Carrier rate data. The clientâs rates lived in 41 spreadsheets and PDF contracts, each with its own lane definitions and accessorial terms. SCM Champs used the Discover and Design phases to standardise them into one lane and zone structure, reconciled them with procurement and each carrier, and loaded the result as 52 freight agreements before the build started. Without that step, the optimiser and the carrier selection rules would have worked from the wrong prices.
What improved after SCM Champsâ SAP TM implementation?
Once operations stabilised after the final go-live, freight cost per shipment was 8% lower, planners spent 55% less time on transportation planning, and freight invoice disputes fell by 60%.
| Business area | Metric | Before SAP TM | After SAP TM | Change |
| Freight costs | Freight cost per shipment | $1,150 | $1,058 | â8% |
| Transportation planning | Truck fill rate | 74% | 82% | +8 points |
| Transportation planning | Planning time per planner per day | 4.0 hours | 1.8 hours | â55% |
| Carrier selection | Loads awarded to the lowest-cost eligible carrier | about 55% | 89% | +34 points |
| Carrier selection | First-tender acceptance rate | not tracked | 87% | n/a |
| Freight settlement | Freight invoice discrepancy rate | 10% | 4% | â60% |
| Freight settlement | Settlement cycle time | 25 days | 10 days | â60% |
| Shipment visibility | On-time delivery | 90% | 94% | +4 points |
| Shipment visibility | Time to detect a delay | next day, usually after a customer call | under 2 hours | n/a |
On about 50,400 shipments a year, the lower cost per shipment is worth roughly $4.6 million annually.
How we measured this. Results are measured 6 months after the final go-live against the previous 12-month average. Freight cost per shipment is adjusted for fuel surcharges and lane mix, so market rate movements and a changing shipment profile do not flatter the result. The share of loads awarded to the lowest-cost eligible carrier before go-live is estimated from a sample of 500 historical loads. The other baselines come from the clientâs ERP, carrier invoices and a planner time study.
Trade-offs. Planning time rose for the first 4 weeks after each wave while planners learned to work from optimiser proposals. Carrier onboarding also took effort: the 6 smaller carriers without EDI still use a web portal, which keeps a manual step in tendering for about 5% of loads. SAP TM adds licence, support and rate-maintenance effort that the spreadsheet process did not carry. The savings covered the project and licence costs within about 14 months of go-live.
What the client says about SCM Champs
âBefore SAP TM, our planners built loads in spreadsheets and we chose carriers largely out of habit. Today every load is planned, tendered and settled in one system. Freight cost per shipment is down 8%, invoice disputes have fallen by 60%, and my team spends its time on exceptions, not spreadsheets. SCM Champs took the time to understand our carrier contracts before touching the system, and that made the difference.â
Director of Transportation
Lessons learned from the project
Four lessons carry over to any freight transformation of this kind.
Fix the rate data before you configure it. Rates that are wrong in the system are wrong on every load. Consolidating 41 sources into 52 freight agreements took about 5 weeks, and it was the most valuable work in the project.
Roll out in waves. Starting with 2 plants gave the team a tested template for the other 3 and kept the risk contained.
Bring planners into the design. A planner from each plant joined the design workshops, which is why the team trusted the optimizerâs proposals once it was live.
Onboard carriers in parallel with the build. EDI onboarding takes longer than configuration. Starting it during Design meant 32 of 38 carriers were live at go-live.
Technologies used
SCM Champs combined SAP software with the clientâs existing carrier network. Each component below played a specific role in the project.
| Technology | Role in the project | Impact |
| SAP S/4HANA | Core system for sales orders, deliveries and finance | Freight units, accruals and invoice postings run on one platform, with no separate transportation system to reconcile |
| SAP TM (Advanced, embedded) | Planning, carrier selection, tendering, charge calculation, settlement and execution | Replaced spreadsheet planning and is behind the 8% lower freight cost per shipment |
| VSR optimizer | Load building and consolidation | Contributed to the rise in truck fill from 74% to 82% and the 55% drop in planning time |
| Freight agreements and charge calculation | Rates, fuel surcharges and accessorials for 38 carriers | Gives planners the expected cost of a load before tendering and gives settlement a basis to check invoices against |
| Freight settlement and invoice verification | Matches carrier invoices to settlement documents | Cut disputes from 10% to 4% and settlement from 25 to 10 days |
| Carrier EDI (204, 990, 214, 210) | Electronic tenders, responses, status events and invoices | Replaced email and phone coordination and made carrier performance measurable |
| SAP EWM (2 distribution centres) | Warehouse picking and loading | Aligns picking and loading with the planned truck sequence |
Is your transportation operation facing similar challenges?
You may benefit from an SAP TM assessment if you recognise these signals.
| What you see | What it usually points to |
| Freight spend keeps rising without a clear reason | No single view of rates, lanes and carrier performance |
| Shipments are planned in spreadsheets or emails | Consolidation depends on individual planners |
| Carriers are chosen by habit rather than cost and performance | No central carrier and rate management |
| Freight invoices are checked manually and disputes are common | Charges are not calculated and matched in the system |
| You find out about delays only after they happen | No execution tracking or carrier status events |
| You are still on SAP TM 9.x or LE-TRA and planning the move to S/4HANA | A migration is the moment to redesign planning, not just move it |
Looking to reduce transportation costs and improve freight management?
Running transportation operations with rising freight costs, manual planning or inefficient carrier management? SCM Champs can assess your current transportation processes and show where SAP TM can reduce freight spend and improve execution. Book a 30-Minute Call with an SAP TM Consultant, or get a Freight Cost Assessment.