Week eighteen is a lousy time to find out how your plant actually works.
But that's usually when it happens. The happy-path training wraps up, second shift runs into a mixed pallet nobody drew in the blueprint, and somebody finally asks the question that should have come up in week one: who's allowed to break the sequence? The project dashboard is a lovely shade of green. The floor has a spiral notebook with coffee rings on it. Guess which one ships product.
Configuring SAP before you've mapped the work is backwards. It's like picking out drapes before anyone has agreed where the walls go.
What "map the work" actually means
Mapping the work means writing down what really happens, who makes the call, and what the floor quietly ignores, in the order a shift actually runs it. I don't mean the swimlane diagram that lives in a conference room and has never once smelled diesel.
The sequence matters more than the software: map it, agree on it, start from SAP standard, configure, then test. Get that order wrong and you'll pay good money for screens the building will cheerfully work around.
What the business should insist on
Before anyone flips a single switch in SAP, the business should demand three things.
First, describe the work the way the floor describes it. Receiving is a trailer at the door, a lot number the scan gun won't take, and a supervisor who already decided which bin it's going in. It doesn't get to be called "inbound delivery processing" until that sentence holds up on both shifts.
Second, name who decides on this shift. Who can freeze the sequence, and who can break it? If the answer is "raise a ticket," congratulations, you don't have a process. You have a delay with a status code.
Third, push back on any blueprint that's just a catalog of modules. Stock Room Management (WM), Extended Warehouse Management (EWM, the heavier-duty warehouse controls for bins, waves, and labor), materials management, quality: those are tools, not work. If your first workshop is organized around tools, you're already shopping for drapes.
If the program can't say yes to all three, week eighteen will teach you the real design anyway. You pay the tuition either way. The only question is whether you pay it up front or with interest.
How programs go sideways
Here's a made-up example, though if it sounds familiar, I'm not surprised. A discrete manufacturer with two plants rolls out one "global template," with every SAP workstream lined up in tidy columns. The template is very proud of itself.
Meanwhile, out on the floor, Plant A still stages to the old side door whenever the main dock is jammed. Plant B still issues parts from a cage the template declared obsolete. Quality still parks held batches in a side system until somebody keys the usage decision, usually after the truck is already sitting in the yard. The project configured the standard path. Second shift configured reality.
By week eighteen the exceptions are living in a spreadsheet, a radio call, a custom screen that "makes the gun work," and a Thursday meeting that will outlive everyone on the project. Either nobody mapped the work, or somebody mapped the PowerPoint version of it. Every test was a happy-path test, which is a shame, because the unhappy path is where the money moves.
Buying bolt-ons before the map exists makes it worse. Warehouse, transportation, yard, each one proudly "integrated" with a process nobody ever wrote down. That isn't a landscape, it's a stack of rumors with license fees. And no, the steering committee is not going to sort it out for you.
None of this is an argument against SAP. It's an argument against configuring first and meeting the plant later.
What SAP Signavio actually gets you
Once the floor has told its story, SAP Signavio, a family of process products, helps you check that story against data and share it with everyone who needs to see it.
The first thing it does is read the trail your SAP system already keeps. SAP Signavio Process Intelligence does process mining, meaning it rebuilds how the work really ran from timestamps your ERP records anyway: order created, delivery picked, goods issued. Since May 2026 it also includes the prebuilt ECC and S/4HANA content that used to be sold as SAP Signavio Process Insights. What you get is the documented flow sitting right next to the one that actually happened, every variant (all the creative ways a "standard" order really ships), the loops where a step repeats because somebody had to fix it, and the places where the hours pile up. Value cases can even put a dollar figure on a detour, assuming somebody does the math. Rework stops being a hunch and turns into a number.
It also draws the process so people can argue about it. SAP Signavio Process Modeler (called Process Manager until this year) draws in BPMN, the standard flowchart notation with the boxes and swimlanes. SAP Signavio Process Collaboration Hub publishes those diagrams so a shift lead can read and comment without buying a modeling license. A process map nobody on the floor can open is just a rumor with arrows.
For the other side of the dock door, SAP Signavio Journey Modeler maps what a customer, supplier, or employee goes through, linked to the processes underneath.
And it hands you somebody else's homework. Value accelerators are installable packages of process models, metrics, and dashboards. Reference content beats a blank whiteboard and a dry-erase marker that died sometime in 2019.
Start from standard before anybody writes a Z
SAP ships a mountain of "here's how this is supposed to run." Most programs crack it open right after the custom code is finished. (For the uninitiated, a "Z" is SAP-speak for custom code or a custom screen, since custom objects get names starting with Z. Every legacy system has a few. Some have a few thousand.)
SAP Signavio Process Navigator, which lives in SAP for Me at me.sap.com/processnavigator, is SAP's library of predefined processes. Look up a scope item (one of SAP's numbered, prepackaged processes) and you get the flow diagram, setup instructions, and test scripts, including versions that load into SAP Cloud ALM. A test script is basically a step-by-step job aid. Read it before anyone declares that standard "can't do our receiving."
SAP Activate is SAP's phase-by-phase implementation method. Its Explore phase is where the Fit-to-Standard workshop happens: somebody demos the standard process in a working system, the people who actually run the work say where it doesn't fit, and each gap becomes a written requirement. SAP's own training says to change only what you must, because every change gets rechecked at every upgrade. That's SAP politely telling you your customizations come with a mortgage.
SAP Cloud ALM (Application Lifecycle Management) keeps those requirements, tests, and go-live tasks tied to the process instead of buried in a ticket pile.
If you're still on ECC, two more tools are worth running. SAP Readiness Check compares your current system against what changes in S/4HANA, custom code included. SAP Signavio Process Insights, discovery edition, the successor to the old Process Discovery report, is a one-time analysis of your process performance using production ERP data, and it's free for customers on SAP maintenance. Both show you what you've got before anyone tries to sell you what you need.
Here's the quiet payoff: map first and the customizations start confessing. That custom screen that "makes the gun work" turns out to cover a putaway rule standard WM already has. The user exit (a hidden hook in SAP's code) for split pallets exists because nobody ever configured the standard step. Find those Zs before you haul them into the next system. Otherwise you aren't running SAP, you're curating a museum, and you pay admission at every upgrade.
Speak floor, hear SAPanese
A lot of mapping fails in translation, not in design. The shift lead says "the pallet is in the back." The consultant writes down a storage type. Everybody nods. Nobody checks. Week eighteen checks for them.
SAP has its own language. I call it SAPanese. It's precise, which is the whole point, but it isn't the language the floor runs on. The mapping session, Fit-to-Standard included, is where one gets translated into the other, out loud, with the people who do the work sitting at the table. Somebody in that room has to be bilingual. If nobody is, the requirement gets written in one language and tested in the other, and everyone acts shocked when it doesn't work.
Here's a starter phrasebook:
On the floor | In SAP |
|---|---|
"The pallet is in the back" | Storage type (the area) and storage bin (the exact slot) |
"Pick list" | Transfer order in Stock Room Management (WM); warehouse task, grouped into a warehouse order, in EWM |
"Hot order" | Delivery priority |
"The customer's special label" | Output determination plus a form (S/4HANA also offers newer output management) |
"Put it on hold" | Quality inspection stock or blocked stock, released by a usage decision |
"Approve it" | Release strategy or workflow |
"We fix it at month end" | Manual posting or adjustment |
"The shortage report" | MRP results: the stock/requirements list (MD04) |
Notice that "we fix it at month end" isn't really vocabulary. It's a confession that a step is missing somewhere upstream. Write down what gets fixed and who fixes it, or the process map comes out clean and the books don't.
Our Process-Mapping Notes have one column for what actually happens and another for the system or screen it lands on. Fill in both. That's the translation, on paper.
What the tools won't do for you
All of this software is genuinely useful, but let's keep expectations honest. Process mining only reads what SAP recorded, so it will never walk the dock, and it has no idea the side door exists. A diagram can show a decision, but a person still has to own it, and no tool is going to decide who gets to break the sequence. Fit-to-Standard will write the gap down neatly, but somebody with a spine still has to say no to the Z. And if the gap is a forklift, I promise you BPMN will not move a single pallet.
Where a specialist actually helps
Good help starts on the floor, not in a module matrix.
Walk one order, one receipt, one production run, one quality hold, and one shipment, start to finish, with the people who do the work, on the shift that actually runs it. Write down what happens, who decides, and what gets ignored. That list is your design. Hold it up against the Process Navigator standard before anybody says the word "custom." Put the agreed picture into Signavio so people can disagree with it in daylight. Then use Cloud ALM so every build and every test points back to that picture. Configuration comes third, and you turn on only what the map calls for. If the gap is labor or steel, buy labor or steel. Don't write custom code to paper over the fact that nobody agreed on who can break the sequence.
That's how we work at ETS.inc. We're an experience-and-knowledge-based consulting company delivering SAP services across North America with full-time experts who average close to 30 years of business experience and close to 25 years of SAP implementation experience. We run a flat resource model, which means you get people who have actually stood on a dock and in a plant, not a pyramid of fresh-faced consultants who discover your real process in week eighteen. Warehouse (WM and EWM) and logistics execution are part of that work. After go-live, our AMS team (application management support, the keep-the-lights-on crew) keeps that Thursday meeting from quietly becoming the process.
The job is making the system keep up with the work you already run. The building isn't going to wait for your swimlane.
What to bring to the first mapping session
Bring one flow, described in floor words: "trailer at door 7 to pickable stock," not "inbound." Bring the people who run it on second shift, not just their manager. Bring the paper you actually use, whether that's a clipboard sheet, a side spreadsheet, or a photo of the whiteboard. Bring every custom screen, report, and interface that touches that flow, along with who asks for it and why. Bring three exceptions from last month: what happened, who decided, and how long it took. Bring the standard, meaning the Process Navigator flow and test script for that scope item, printed out. And if you're on ECC, bring your Readiness Check and discovery edition results.
Leave the module map at the door. Same goes for any slide titled "Future State."
One thing to do in the next two weeks
Pick one flow the business can't fake: dock-to-stock, make-to-ship, or hold-to-release. For five shifts, write down what actually happens, who decides, and what the floor ignores, before anybody opens a configuration screen. No workshop, no consultants, no catering. A notebook will do.
That list is your map. Everything else is commentary.
If you'd like a second set of eyes to turn that notebook into a process picture and a delivery plan that tests the truth instead of the slide deck, that's exactly the kind of work we do at ETS.inc.
Get the Process-Mapping Notes
A printable 7-page field tool for the mapping session above: step capture, exceptions and rework loops, a customization log for the Zs, handoffs, and a fit-to-standard summary.