Krit Jiarawattanakul

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

    FromToWhat movesWhen
    Dealer systemSAPDetailed ledger for vehicles, service and parts; inventory; purchase orders that become sales ordersDay end
    SAPDealer systemCustomer master with credit limit and its history, vendor master, deliveries with VINReal time
    SAPAutomated storagePut-away and retrieval tasks by BOM set; acknowledgements backPeriodic
    Product data (PDM)SAPEngineering BOM to production BOM; SAP returns standard cost and tolerance each quarterPeriodic, real time
    HRISSAPPayroll and personnel-cost postingsMonth end
    Dealer systemHRISMechanics' and sales performance for incentives and commissionDay end
    Dealer systemOEM systemsService history both ways, warranty claims and acknowledgements, parts listsReal time, day end
    MESSAPCapacity, 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.

      Modules involved

      Where it posts

      What I check first

      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.

      12companies documented
      44review slides, English and Thai
      64questions for process owners

      How it was made

      1. Extract checklist64 configuration items, exported read-only, with personal data masked under PDPA.
      2. Evidence set34 configuration extracts, plus transaction volumes to show what is really used.
      3. AI draft under a directiveA detailed blueprint and a slide deck from one set of findings, with matching IDs in both.
      4. Evidence on every findingEach statement is tagged by how sure we are, so nobody mistakes a guess for a fact.
      5. Owner reviewConfirm, comment or correct each question in the deck; answers export to CSV for the record.
      6. 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
      Record to report
      Cost and profitability
      Inventory and warehouse
      Procure to pay
      Plan (MRP)
      Order to cash
      Plan to produce
      Intercompany supply

      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.

      6API messages, both directions
      3layers: gateway, integration, ERP adapter
      1part to replace when the ERP changes

      Target architecture

      Our side

      1. Customer ERP (IFS)Calls our API with a JWT; receives our calls with OAuth 2.0
      2. API and file gatewayThe only thing outside parties reach. Key-based access, allowlists, separate test and production
      3. Integration layerVersioned schema, validation, duplicate checks, code mapping, acknowledgements, retries, monitoring, archive
      4. Thin ERP adapterStandard IDocs and BAPIs over RFC, a few small extracts. No file or XML logic in ABAP
      5. SAP ECC 6.0 today, any ERP laterSwap the adapter, keep everything above it
      Layer optionWhy consider itWatch out for
      SAP Integration SuiteNatural if the next ERP is S/4HANATies us to SAP if we choose another ERP
      Cloud integration serviceERP-neutral, SAP connectors, managedNew subscription, skills, data location
      Open source, self-hostedCheapest licence, full controlNeeds in-house skills to run
      Everything in ABAPQuickest to startNot 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.

      158processes mapped in 8 departments
      7SAP modules blueprinted
      156users scoped

      Processes mapped by department

      Human resources57
      After-sales service22
      Quality assurance21
      Finance and accounting20
      Paint shop16
      Truck and trailer production11
      Supply chain8
      Engineering3

      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.

      Hiring a Head of IT, IT Director or CIO?

      Open to Head of IT, IT Director and CIO roles in Thailand and Southeast Asia.

      krit.jiarawattanakul@gmail.com
      Phone
      +66 92 775 9933
      Based in
      Bangkok, Thailand
      Languages
      Thai and English
      Also at
      hirekrit.com