SCM Champs helps businesses fix SAP TM systems that are already live but struggling. Freight units that will not consolidate, planners who rebuild every plan in Excel, TM and EWM showing different statuses, freight costs that do not match carrier invoices. We find what is actually causing it, and we fix that not the symptom.
40+ SAP TM projects · 12 years of SAP TM focus · 15+ countries · SAP TM certified consultants
SAP TM Problems We Commonly Fix
Why are SAP TM freight units not consolidating?
If SAP TM is not consolidating orders that should clearly travel together, it is usually because the Freight Unit Building Rule (FUBR) is splitting them on a field that no longer matters, such as an obsolete shipping condition or incoterm. Incompatibility settings that are too strict, transportation lanes that do not match how goods really move, and capacity limits set only by weight are the other common causes. In our experience this is almost always a configuration or master data issue, not a limitation of the optimizer. Fixing it is usually the fastest way to improve truck utilization on lanes where consolidation is failing.
Why are planners still using Excel instead of SAP TM?
Planners go back to Excel when the planning profile, optimizer settings and constraints no longer match how the business runs. The usual causes are hard constraints for delivery windows that do not exist in reality, a cost profile that puts freight cost ahead of service, and real limits like dock timings or driver hours that were never entered into the system. The plans come out wrong, trust goes, and the work moves to spreadsheets. To reduce manual planning, the settings have to reflect how the network actually operates — training alone will not bring planners back to the system.
Why are SAP TM and SAP EWM showing different statuses?
When shipment status is not updating between TM and EWM, the break is almost always at the handover points, where TM passes to ERP and ERP passes to EWM. The usual causes are master data maintained differently on each side, deliveries and freight orders created at different times, and failed messages sitting in queues that nobody monitors. It is normally one message type or one field that is broken, not the whole integration — which is why shipment status visibility can usually be restored without touching the wider interface.
Why don’t SAP TM costs match carrier invoices?
Freight cost variance in SAP TM builds up when rate tables and condition records are outdated or maintained in more than one place, when surcharges are missing from the charge calculation sheet, and when settlement is partly manual. Costs that are never allocated back to orders or customers make the gap harder to spot. Put planned cost, settled cost and the carrier invoice side by side for the same shipments and the pattern usually shows itself.
Can SAP TM problems be fixed without migrating to S/4HANA?
Often yes. Many consolidation, planning and freight cost problems come from data, configuration, planning logic, integration or process, and all of those can be addressed in your current system. Migrating before you have diagnosed the cause tends to carry the same gaps into a newer platform, where they usually cost more to fix.
Why SAP TM Stops Matching the Business
Most SAP TM systems are set up correctly at go-live. Then the business moves on.
New customers arrive. Routes change. Product mix shifts. Volumes grow. But the configuration inside SAP TM stays as it was, because nobody owns reviewing it. Master data drifts. Rules that made sense three years ago quietly block things today.
So people work around the system. A planner starts checking one thing in Excel. Someone calls the warehouse instead of trusting the status. A shortcut becomes the normal way of working. Once that happens, the system and the business are running on two different sets of rules, and every new problem looks like a system fault.
SAP TM is often not the problem. The problem is that the system no longer reflects how the business actually operates.
This is the work SCM Champs does. We come into systems that are already live, trace where the system and the business stopped matching, and bring them back together. Usually that means adjusting rules, cleaning data and fixing process gaps, not rebuilding anything.
Our 5-Layer SAP TM Diagnostic Approach
We work through five layers, in this order:
- Data — Is the master data correct and consistent across all systems?
- Configuration — Do the current rules still match how the business runs today?
- Planning logic — Are the constraints and optimizer settings appropriate for your network?
- Integration — Is information moving correctly between TM, ERP, EWM and your carriers?
- Process — Are people working the way the system was designed to expect?
We do not start by changing settings. Changing settings on top of bad data just moves the problem somewhere else. Problems that keep coming back after every fix usually trace to data or process gaps, not configuration alone, which is why we check those first.
Only once we know the actual cause do we define what needs fixing, rebuild it, and test it against real situations rather than clean test data.
Where to start looking
| If you are seeing… | Start by checking… |
| Orders not grouping, even with space available | Freight unit building rules and incompatibility settings |
| Planners rejecting system-generated plans | Planning profile, optimizer settings, constraints |
| Trucks leaving half empty | Resource and capacity master data |
| Planning runs slow or timing out | Planning horizon and selection criteria |
| TM and EWM status stuck | Integration points and error handling queues |
| Invoices not matching planned cost | Rate tables, charge calculation sheets, settlement setup |
| The same problem returning after every fix | Master data and process |
| People working around the system | Process design and user training |
This will not give you the full answer, but it will tell you which layer to start with.
SAP TM Consulting Services SCM Champs Offers
SAP TM Planning and Optimization We rework planning strategies, VSR optimizer settings and constraints so the system produces plans your planners will actually use. That usually means removing constraints that do not exist in reality, and adjusting the cost profile to match your real business priorities. The aim is to reduce manual planning, not to add another layer of workarounds.
Freight Unit and Freight Order Management We fix freight unit building rules, incompatibility settings and freight order configuration so orders that should travel together actually do. Most consolidation failures trace back to one rule or one master data gap, and that is what we look for. On lanes where this has been going wrong for a while, the effect on truck utilization is usually immediate.
Freight Cost and Settlement We clean up rate tables, condition records, surcharges and settlement configuration so planned, settled and invoiced costs line up, which brings freight cost variance down to something you can explain. We also set up proper cost allocation, so freight spend can be traced back to orders, customers or business units.
SAP TM–EWM Integration We fix the handover points between TM, ERP and EWM so shipment status moves without anyone chasing it, and both teams get the same visibility on where a load actually is. That covers master data alignment on both sides, message and queue error handling, and testing against real cases instead of clean test data.
SAP TM Implementation and Migration We deliver new SAP TM rollouts, move legacy transportation setups across, and handle migration into your S/4HANA landscape. Before any migration we check what genuinely transfers and what needs redesigning, so old problems do not travel with you.
SAP TM Post Go-Live Support We stay on after go-live with ongoing help on configuration, changes and new requirements as your business shifts. This is part of how we work, not a separate add-on, because most SAP TM problems appear months after the project team has left.
Do You Need S/4HANA to Fix SAP TM?
Usually not, and this is worth being clear about, because we see the same conversation repeatedly. A system underperforms, so the discussion turns straight to S/4HANA, as if a new platform will clear the problem on its own.
Sometimes it does. Often it does not.
The reason is simple. If freight units are not consolidating because of an obsolete field in a grouping rule, that rule follows you to the new platform. If planners distrust the system because the optimizer has constraints that do not exist in reality, those settings migrate too. If TM and EWM statuses do not match because master data is maintained differently on each side, that mismatch does not resolve itself during a technical migration. Data, configuration, planning logic, integration and process problems travel with you, and they are more expensive to unpick after a migration than before it.
Diagnose first, then decide.
Once you know which layer the problem sits in, the decision becomes straightforward. Many issues are fixable in your current system in weeks. Others genuinely do point towards a move.
Migration tends to make sense when transportation planning has to sit inside your S/4HANA landscape, when your own business rules need to drive planning instead of standard defaults, or when rate management and freight settlement need to work off the same data as the rest of finance.
Our role is to give you that answer honestly. We assess what you have, tell you what can be fixed where it stands, and tell you where a move to S/4HANA would genuinely add value. If migration is the right call, we will say so. If it is not, we will say that too.
Embedded TM vs Side-by-Side TM
SAP TM on S/4HANA can be deployed in two ways. Which one fits depends on your landscape, not on a general rule.
| Embedded TM | Side-by-Side TM | |
| Best suited for | Single S/4HANA landscape | Multiple ERPs or complex landscapes |
| Architecture | Runs inside S/4HANA | Runs as a separate system |
| Master data | More closely integrated | Integration and replication required |
| Typical complexity | Simpler shipper flows | Complex or multi-system transportation |
One point worth knowing early: if SAP ECC is still in your landscape, side-by-side is normally the workable option.
Deployment and licensing options change over time. Confirm the current position against SAP’s own documentation and your licensing agreement before making a decision.
Why Companies Bring SCM Champs Into an Existing SAP TM Landscape
You do not have to replace your current SAP partner to work with us.
Most of our clients already have someone managing their SAP landscape — an implementation partner, a managed services provider, or an internal IT team. That arrangement usually works fine for day-to-day operations. What it often cannot absorb is one specific SAP TM problem that has stayed unsolved for months, because it needs deep transportation expertise rather than broad SAP coverage.
That is where we come in. We take the single issue that is stuck consolidation, planning adoption, freight cost variance, TM–EWM integration, or performance after go-live — while your existing partner or internal team carries on managing everything else. No handover of the wider landscape, no disruption to existing contracts.
We fix what is stuck, explain clearly what caused it, and leave your team in a better position to keep it working.
Selected SAP TM Engagements
Fixing freight unit consolidation at a chemicals manufacturer
Problem: Two plants shipping into the same distribution network. Orders for the same customer, on the same day, consistently left on separate trucks. Truck utilisation on their primary lane was stuck at 62%.
Root cause: Two issues working together. A freight unit building rule from the original implementation was separating orders on a shipping condition field that had become obsolete. And their transportation lanes did not reflect a new cross-dock they had opened, so the optimizer could not see the valid shared route.
What changed: We removed the obsolete shipping condition from the consolidation rule and rebuilt the transportation lanes to include the new cross-dock. No custom development was needed.
Result: Truck utilization moved from 62% to 84% within six weeks. That took around 12 trucks per week off the road and reduced their transportation costs by over €400,000 a year.
Client name withheld under confidentiality agreement.
Restoring planner trust at a European FMCG distributor
Problem: Fourteen planners, each spending the first two hours of every day rebuilding the system’s freight orders in Excel before entering them back into SAP. The system-generated plan was effectively unused.
Root cause: The optimizer was running with hard constraints for delivery windows that did not exist in practice, and its cost profile prioritised freight cost over service. The business priority was the other way round. The planners knew this, and overrode the system to protect delivery promises.
What changed: We ran calibration workshops with the planners, converted the non-existent hard windows into soft constraints, and adjusted the cost profile to prioritise on-time delivery. We then ran a two-week simulation with the planners before switching it on.
Result: Manual planning time dropped by 30%. The system’s first plan became the accepted plan for 70% of orders, up from 20%. On-time delivery improved by 5%.
Client name withheld under confidentiality agreement.
About SCM Champs
SCM Champs is a specialist SAP Transportation Management (SAP TM) consultancy headquartered in Wilmington, Delaware, USA, with clients across multiple regions worldwide. SAP TM is at the core of what we do — it is not simply one service among many. It is our area of expertise.
With 12 years of SAP TM experience and more than 40 projects delivered, we help organizations implement, optimize, and stabilize SAP TM across complex transportation environments. Our experience covers everything from SAP TM 9.x to embedded SAP TM on S/4HANA, including implementation projects, performance and process optimization, and post-go-live challenges.
Our consultants have worked across 15+ countries, with strong experience in European road freight, complex LTL operations, and intermodal transportation. We support businesses across industries including chemicals, FMCG, retail distribution, and automotive logistics.
What sets us apart is our depth of SAP TM expertise. Our senior consultants are SAP TM certified and bring a practical understanding of both the technology and the day-to-day transportation processes behind it. Whether you are starting a new SAP TM journey, improving an existing solution, or resolving issues after go-live, we focus on practical solutions that deliver real business value.
USA Office:
3524 Silverside Road, Suite 35B
Wilmington, DE 19810, USA
Regions served: North America, Europe, and other global regions (consultants have worked across 15+ countries)
Team size: Not specified in the provided content
SAP TM versions supported: SAP TM 9.x to embedded SAP TM on S/4HANA
Book an SAP TM Assessment
If the same SAP TM issues keep coming back, they will not fix themselves. There is a reason underneath, and it can be found.
Let SCM Champs trace the issue across data, configuration, planning logic, integration and process. You will get a clear picture of what is holding your transportation back, and what it will take to fix it.
[Book an SAP TM Assessment]