I read an ERP as a business first
I started as an SAP consultant, so I look at processes and handoffs before configuration. These samples show how I map a business, document what a system really does, and connect it to the companies around it.
Head of IT, truck and bus manufacturer, 2020 to 2023. Drawn for the SAP S/4HANA request for proposal.
Three companies, two OEMs, five systems: who sells what to whom
Before asking vendors for a price, I drew every transaction between the group's three companies, the two OEM partners, suppliers, banks and customers, and which system records each one. Vendors quoted against the real business, not a generic manufacturing template.
Pick a scenario to trace it through the companies and systems, step by step.
Design rules that came out of the map
- Vehicles built to stock stay on the manufacturer's books until the sales company sells them to an end customer; built-to-order vehicles are delivered to plan.
- The sales company runs the dealer system for vehicles, parts and workshops; its detailed ledger posts to SAP at day end.
- The manufacturer sits in a free zone, so BOI-promoted and standard materials are tracked apart and local content is calculated.
- A customer's own vehicle in for body-building is held as non-value stock.
- The holding company runs finance, IT, HR, procurement, facilities and imports for all three.
Scroll the map sideways to see all companies.
- Goods and vehicles
- Orders and data
- Invoices, money and claims
How the five systems talk
From the same RFP
| From | To | What moves | When |
|---|---|---|---|
| Dealer system | SAP | Detailed ledger for vehicles, service and parts; inventory; purchase orders that become sales orders | Day end |
| SAP | Dealer system | Customer master with credit limit and its history, vendor master, deliveries with VIN | Real time |
| SAP | Automated storage | Put-away and retrieval tasks by BOM set; acknowledgements back | Periodic |
| Product data (PDM) | SAP | Engineering BOM to production BOM; SAP returns standard cost and tolerance each quarter | Periodic, real time |
| HRIS | SAP | Payroll and personnel-cost postings | Month end |
| Dealer system | HRIS | Mechanics' and sales performance for incentives and commission | Day end |
| Dealer system | OEM systems | Service history both ways, warranty claims and acknowledgements, parts lists | Real time, day end |
| MES | SAP | Capacity, yield, breakdowns and maintenance plans (phase 2) | Planned |
SAP ECC and S/4HANA. Functional consulting since 2006: warehouse, HR and process design, then running ERP programmes as Head of IT.
Most ERP problems start at a handoff
Pick a process to see its main steps with the usual SAP transactions, which modules it crosses, where it posts, and what I check first when it goes wrong.
Current role, 2026. SAP ECC 6.0, one system and one client serving twelve companies. ERP replacement under evaluation.
An AS-IS blueprint built from the system, not from memory
Before a group can choose its next ERP, someone has to describe the current one honestly. Most design documents were years out of date, and the people who knew the history had moved on. So I built the blueprint from the system itself and asked process owners to confirm it.
How it was made
- Extract checklist64 configuration items, exported read-only, with personal data masked under PDPA.
- Evidence set34 configuration extracts, plus transaction volumes to show what is really used.
- AI draft under a directiveA detailed blueprint and a slide deck from one set of findings, with matching IDs in both.
- Evidence on every findingEach statement is tagged by how sure we are, so nobody mistakes a guess for a fact.
- Owner reviewConfirm, comment or correct each question in the deck; answers export to CSV for the record.
- Vendor-neutral designA global template that maps the same processes to S/4HANA, Dynamics 365, Oracle, IFS or Odoo.
Process landscape, as the review deck shows it
Companies anonymised
- Verified in data
- Configured, use derived
- Not set up
Five manufacturing companies, three sales or trading companies and four that use SAP for finance only.
A question from the deck
Low priority, needs confirmation
Three companies have a plant in SAP but no storage location, sales or purchasing set-up. Are they used for accounting only, and can their plants be treated as inactive for logistics?
Process owners record a status, their name and a comment for each of the 64 questions.
Current role, 2026. A key customer moving to IFS; our side on SAP ECC 6.0, with no integration platform and an ERP decision still open.
Connecting a customer's new ERP without tying either side to SAP
The obvious answer was to write the interface inside SAP. It would also have been thrown away at our own ERP migration. Instead I proposed a small ERP-neutral layer that we own, with everything SAP-specific in a thin adapter. When the ERP changes, only the adapter is replaced; the schema, mappings, customer connection and test files stay.
The scope became six API messages, each with an acknowledgement, and business rules both companies signed up to: frozen forecast windows, requested versus confirmed dates, and how changes and cancellations are reviewed.
Target architecture
Our side
- Customer ERP (IFS)Calls our API with a JWT; receives our calls with OAuth 2.0
- API and file gatewayThe only thing outside parties reach. Key-based access, allowlists, separate test and production
- Integration layerVersioned schema, validation, duplicate checks, code mapping, acknowledgements, retries, monitoring, archive
- Thin ERP adapterStandard IDocs and BAPIs over RFC, a few small extracts. No file or XML logic in ABAP
- SAP ECC 6.0 today, any ERP laterSwap the adapter, keep everything above it
| Layer option | Why consider it | Watch out for |
|---|---|---|
| SAP Integration Suite | Natural if the next ERP is S/4HANA | Ties us to SAP if we choose another ERP |
| Cloud integration service | ERP-neutral, SAP connectors, managed | New subscription, skills, data location |
| Open source, self-hosted | Cheapest licence, full control | Needs in-house skills to run |
| Everything in ABAP | Quickest to start | Not recommended: rewritten at migration |
The six messages, as swimlanes
Pick a flow
Time runs downward. Amber badges mark the six API messages where data crosses between companies.
Head of IT, truck and bus manufacturer, 2020 to 2023. SAP S/4HANA, dealer management, MES, HRIS and automated storage.
An ERP chosen from the business up
Before talking to vendors, I had process owners and key users write down how the business actually works, department by department, and tracked completion daily. That became the terms of reference, then the request for proposal, then the evaluation and the contracts.
Processes mapped by department
What the RFP asked every vendor for
Scope
Finance and controlling, materials, sales and distribution, production planning, plant maintenance, quality, and HR with payroll and time.
Commercials
- Licences, standard and add-on implementation costs
- Development estimates by complexity, easy to very hard
- On-premise versus cloud, priced for five years
- Disaster recovery at RPO 4 h and RTO 2 h, 99.9% SLA
Fit to requirements
- Every requirement answered as standard, workaround, custom or vendor solution
- Each custom item typed: report, interface, form, enhancement
- Priority and effort range per item
Evaluation
- Functional fit, architecture, integration, data migration
- Security and compliance, delivery method, references
- Total cost of ownership
Contracts then fixed the statement of work, SLA, change control, milestone payments, warranty and hypercare.