Warehouse, freight and planning on SAP, cut over without stopping the dock.
Supply chain go-lives fail in public: trucks wait, pickers stand still, planners go back to spreadsheets. We plan SAP EWM, TM and IBP work around the physical operation first and the system second, and we rehearse on the floor before cut-over.
Cohash implements and migrates SAP Extended Warehouse Management, SAP Transportation Management and SAP Integrated Business Planning.
Most programs we see involve moving off SAP SCM 7.0, where APO, standalone EWM and TM run today, before mainstream maintenance ends in 2027. We design the warehouse process, the freight planning model and the IBP planning areas, then integrate them with S/4HANA and run go-lives one site at a time.
you probably need this if
APO runs your planning and the person who wrote its macros is the only one who can change them.
WM in ECC has to go with the S/4HANA conversion and nobody has scoped EWM yet.
A new site goes live before peak and the automation vendor hasn't seen your integration spec.
04 Feb 2020SAP SCM 7.0 mainstream maintenance ends 2027 SAP Supply Chain Management 7.0, home of APO and standalone EWM and TM, is a Business Suite 7 core application. Mainstream maintenance runs to the end of 2027, with optional extended maintenance to the end of 2030. source ↗
today · Oct 22, 2026
no date yetS/4HANA 2025 releaseSAP's 2025 release ships PP/DS changes and follows the two-year release cycle, with feature pack stacks in between. Embedded EWM and TM ride the same cycle.source ↗
no date yetRenamed SAP certificationsSAP Learning now lists EWM and TM certifications under SAP S/4HANA Cloud Private Edition names (C_S4EWM, C_S4TM) and IBP as SAP Certified - SAP Integrated Business Planning (C_IBP).source ↗
the story · sap ewm, tm & ibp estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your SAP EWM, TM & IBP estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · sap ewm, tm & ibp estate3 open
openAPO runs your planning and the person who wrote its macros is the only one who can change them.
recurringWM in ECC has to go with the S/4HANA conversion and nobody has scoped EWM yet.
blockedA new site goes live before peak and the automation vendor hasn't seen your integration spec.
exposure
EWM implementation and migrationTransportation ManagementIBP for supply chainAPO exit planningAutomation and MHE integrationHypercare and staffing
EWMS/4B2Bi
startrehearsehandover
Site and process walk
Design and fit
Floor rehearsal
Site-by-site cut-over
we are here
ready to hand over
Planning leaves SCM 7.0 on a schedule everyone knows, and the macros nobody used get…
The site goes live with tested integration to the automation, and peak runs on a process…
Warehouse process design with process types, storage control and wave rules per site
APO function map showing the IBP or S/4HANA replacement for each macro and heuristic
chapter 01 · where it hurts
Why teams reach out
APO runs your planning and the person who wrote its macros is the only one who can change them.
WM in ECC has to go with the S/4HANA conversion and nobody has scoped EWM yet.
A new site goes live before peak and the automation vendor hasn't seen your integration spec.
chapter 02 · what we change
How we solve it
EWM implementation and migration
Transportation Management
IBP for supply chain
APO exit planning
Automation and MHE integration
Hypercare and staffing
chapter 03 · how it runs
Our approach
Site and process walk
Design and fit
Floor rehearsal
Site-by-site cut-over
chapter 04 · where you end up
What changes
Planning leaves SCM 7.0 on a schedule everyone knows, and the macros nobody used get left behind.
The site goes live with tested integration to the automation, and peak runs on a process the team has already practiced.
Warehouse process design with process types, storage control and wave rules per site
APO function map showing the IBP or S/4HANA replacement for each macro and heuristic
what we do
Our SAP EWM, TM & IBP work
6 kinds of SAP EWM, TM & IBP work, each run by engineers who have done it on live tenants.
Embedded or decentralized EWM on S/4HANA, warehouse process types, storage control, wave and slotting design, RF and handheld transactions, and migration from WM or standalone EWM 9.x.
Freight units, planning profiles, carrier selection, tendering and freight settlement in SAP TM, integrated with sales and purchase orders in S/4HANA.
IBP planning areas, key figures and planning operators for demand, supply and inventory, with the data integration to S/4HANA that replaces APO DP and SNP.
A function-by-function map from APO DP, SNP, PP/DS and GATP to IBP, embedded PP/DS and aATP in S/4HANA, with the custom macros and BAdIs that need a new home.
Material flow system and PLC connections for conveyors and sorters, plus integration with third-party warehouse robotics, tested with the equipment vendor before go-live.
EWM, TM and IBP consultants for go-live support across shifts, onsite in the US or nearshore and offshore across time zones.
capability 01 / 06in production
EWMS/4B2Bi
EWM implementation and migration
Embedded or decentralized EWM on S/4HANA, warehouse process types, storage control, wave and slotting design, RF and handheld transactions, and migration from WM or standalone EWM 9.x.
IBP planning areas, key figures and planning operators for demand, supply and inventory, with the data integration to S/4HANA that replaces APO DP and SNP.
A function-by-function map from APO DP, SNP, PP/DS and GATP to IBP, embedded PP/DS and aATP in S/4HANA, with the custom macros and BAdIs that need a new home.
Material flow system and PLC connections for conveyors and sorters, plus integration with third-party warehouse robotics, tested with the equipment vendor before go-live.
We pieced these together from SAP EWM, TM & IBP situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
APO DP and SNP on SCM 7.0 with 300 custom macros
composite · not a client story
Beforethe situation
Demand and supply planning run in APO on SCM 7.0, with around 300 custom macros and a nightly heuristic chain. Mainstream maintenance ends in 2027 and the S/4HANA conversion is already scheduled.
What we dothe work
We list every macro and job in the planning chain and mark which are still used. Each one maps to IBP configuration, a planning operator or a process change. Demand planning moves to IBP first and runs one full cycle in parallel with APO before supply follows.
Afterwhere you end up
Planning leaves SCM 7.0 on a schedule everyone knows, and the macros nobody used get left behind.
case file 02
A new automated DC that must ship before November peak
composite · not a client story
Beforethe situation
There's a new distribution center with shuttle storage and a sorter, and it needs to ship before peak. Nobody from the automation vendor has met the SAP team, and the integration spec is still in draft.
What we dothe work
We agree the telegram and interface spec with the equipment vendor in the first weeks and test EWM against the vendor's emulator before the hardware is commissioned. Full-shift rehearsals run on the real equipment, with go-live set well before peak.
Afterwhere you end up
The site goes live with tested integration to the automation, and peak runs on a process the team has already practiced.
We don't start a step until the last one has produced something you can check.
step 01
Site and process walk
With the people who run it, we walk the warehouse or planning cycle and map inbound, putaway, picking, packing and shipping, or the monthly planning calendar. We write down where the current system is being worked around.
step 02
Design and fit
Depending on the product, that means warehouse process types, storage control and wave design in EWM, freight units and planning profiles in TM, or planning areas and key figures in IBP. We map APO functions to their new home one at a time.
step 03
Floor rehearsal
Users run full shifts on handheld devices, printers and conveyors in a test area. For IBP, planners run a full monthly cycle in parallel with the old process.
step 04
Site-by-site cut-over
One site or planning area at a time, with stock loaded and counted beforehand and hypercare on every shift, then the next site uses the refined runbook.
ai on sap ewm, tm & ibp
Where AI fits on SAP EWM, TM & IBP, and where it needs guardrails.
Joule's supply chain features are furthest along in SAP Integrated Business Planning, where AI-assisted supply optimization analysis is generally available. Joule with SAP Logistics Management, for warehouse and transportation planning, is in Early Adopter Care. For EWM and TM, agents today are mostly custom builds on BTP, so the work is integration and guardrails.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
EWMSAP EWM, TM & IBPdoes the work
SAP doesn't offer a standard EWM, TM or IBP MCP server, as far as we found. Agents get to S/4HANA and BTP services through Agent Gateway, and the Integration Suite MCP Gateway can expose OData APIs. Each agent we set up has a technical identity with warehouse- or plant-level authorizations. Goods movements and freight tendering stay behind a human approval.
AI-assisted supply optimization in IBP
This Joule feature tells you why an optimizer run left demand unmet or missed inventory targets. It relies on a cleanly configured planning area. We check the planning model before anything else, because a clear explanation of a bad model still gives you a bad plan.
Joule with SAP Logistics Management
SAP lists this as an Early Adopter Care release for warehouse and transportation planning tasks. It isn't generally available yet, so we'd run it as a pilot with a named planner checking every suggestion.
Custom agents for EWM and TM monitoring
SAP's own delivery teams have built Joule agents on BTP that classify TM and EWM integration errors and suggest fixes from SAP knowledge documents. We build similar agents for queue and interface monitoring, read-only at first, using Joule Studio and MCP tools.
APO macro and job documentation
Moving off APO means working through years of macros and heuristic chains. We have AI describe each macro and job. Then we map it to IBP configuration, a planning operator or a process change, and a planner confirms each mapping.
IBP plans demand and supply and sends the plan to S/4HANA. Orders flow from S/4HANA to TM for freight planning and to EWM for warehouse execution, while EWM drives conveyors and sorters through its material flow system.
01 · Planning
SAP IBPdemand · supply · inventory → SAP S/4HANA · supply plan
02 · ERP core
S/4
SAP S/4HANAorders · stock · aATP → SAP IBP · actuals · master data→ SAP EWM · deliveries→ SAP TM · freight requirements
B2Bi
Order managementSterling OMS · B2B EDI → SAP S/4HANA · sales orders
03 · Execution
EWM
SAP EWMputaway · picking · waves → Conveyors and sorters · transport orders
SAP TMfreight units · tendering → SAP EWM · loading plan→ Carriers · tendering
04 · Floor and partners
Conveyors and sortersMFS · PLC telegrams
Carrierstenders · status · invoices
Read the diagram as text
SAP IBP → SAP S/4HANA: supply plan
SAP S/4HANA → SAP IBP: actuals · master data
Order management → SAP S/4HANA: sales orders
SAP S/4HANA → SAP EWM: deliveries
SAP S/4HANA → SAP TM: freight requirements
SAP TM → SAP EWM: loading plan
SAP EWM → Conveyors and sorters: transport orders
SAP TM → Carriers: tendering
use cases
Typical SAP EWM, TM & IBP projects
The work teams usually bring us, and the platforms SAP EWM, TM & IBP has to talk to while we do it.
SAP-01APO DP and SNP still run demand and supply planning on SCM 7.0
common request
SAP-02A new distribution center needs EWM live before peak season
common request
SAP-03WM in ECC has to move to EWM as part of an S/4HANA conversion
common request
SAP-04Freight is planned in spreadsheets and tendered by email
common request
SAP-05Planners don't trust the consensus forecast and keep their own
common request
These are working documents, written against your configuration, so your team can run them without us.
design01
Warehouse process design with process types, storage control and wave rules per site
yours to keep
document02
APO function map showing the IBP or S/4HANA replacement for each macro and heuristic
yours to keep
document03
MHE and material flow integration spec agreed with the equipment vendor
yours to keep
tests04
Floor rehearsal script and results for each shift pattern
yours to keep
plan05
IBP planning area, key figure and operator design
yours to keep
runbook06
Site cut-over runbook with stock load and count procedure
yours to keep
talent and delivery · sap ewm, tm & ibp
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
SAP EWM functional consultant (inbound, outbound, waves)
SAP EWM MFS and automation integration consultant
SAP TM freight planning and settlement consultant
SAP IBP demand and supply planning consultant
IBP data integration developer (CI-DS, S/4HANA)
ABAP developer for EWM RF and enhancements
due diligence · sap ewm, tm & ibp
Questions to ask any partner, including us.
Put these to anyone bidding on your SAP EWM, TM & IBP work. The ones who've done it answer differently from the ones who've read about it.
Q1
Of all our APO macros and heuristics, which ones does anybody still use, and where does each one end up?
APO customizations don't migrate to IBP. A use-based inventory keeps the program from rebuilding logic that no planner relies on anymore.
Q2
Embedded or decentralized EWM for each of our sites, and why?
The choice affects uptime during ERP maintenance, sizing and how much the warehouse depends on S/4HANA. Make it per site, based on volume and automation.
Q3
How will you test integration with our conveyors and sorters before the hardware is even ready?
Material flow integration is a common go-live failure. Testing against a vendor emulator early leaves time to fix telegram mismatches.
Q4
How many full shifts will users rehearse on real devices before go-live?
Handheld transactions, label printers and RF performance only show their problems under real working conditions and full volume.
Q5
What does hypercare look like on night and weekend shifts?
Warehouses run around the clock. A support team that only works days leaves the hardest shifts without help in the first weeks.
01Embedded or decentralized EWM?
It depends on volume, automation and how much downtime the warehouse can take during ERP maintenance. Embedded EWM keeps one system and is simpler to run. Decentralized EWM suits high-volume or heavily automated sites that need to keep shipping while the ERP is down. We decide per site, not per company.
02What replaces APO when SCM 7.0 leaves maintenance?
For most companies, IBP takes over demand and supply planning, while PP/DS and aATP move into S/4HANA. Custom APO macros and heuristics don't migrate automatically. We inventory each one and decide whether IBP configuration, an operator or a process change replaces it.
03How do you avoid a warehouse go-live that stops shipping?
We rehearse with real users on handheld devices, real labels and real equipment in a test warehouse or a closed section of the building. Go-live is scheduled outside peak, with stock counted and loaded the night before, and a staffed hypercare team on every shift for the first weeks.
04Can TM handle our carrier tendering and freight audit?
Usually yes. SAP TM covers tendering, carrier selection and freight settlement. Integration with carrier networks, rate engines or a separate freight audit provider needs design, and that's where most of the effort goes.
05How long does an IBP implementation take?
It depends on how many planning processes go live together, the number of key figures and how clean the master data is. Demand planning alone is a smaller project than demand, supply and inventory together. Data integration with S/4HANA is often the critical path.
06Do you staff EWM and IBP roles into an existing team?
Yes. EWM, TM and IBP people are some of the hardest to find, and we place them on contract, contract-to-hire or permanent terms.
services
Related services
Projects on SAP EWM, TM & IBP usually end up touching one of these, so they're worth a look.
