It can. JIT delivers parts on time against a schedule; JIS goes further and delivers them in the exact sequence the vehicles are being assembled — so unit number one on the customer line gets its specific variant, then unit two, and so on. SAP supports JIS through sequenced call handling: the OEM sends a sequence signal, and the system drives production and shipping to that order, matching each finished part to its position in the customer's build. This is the most execution-sensitive delivery model in automotive, because a single mis-sequenced part stops the customer's line and triggers penalties. The design work is in the sequencing logic, the tight tie to shop-floor execution and the error-proofing — which is why JIS suppliers need the plan, the floor and the shipping process locked to one system rather than stitched across tools.

SAP Quality Management provides the backbone, and IATF 16949 alignment comes from configuring it to the automotive core tools. APQP and PPAP are run as structured workflows with the required documentation; control plans and inspection plans define what is checked, where and how often; results recording captures the measurements. Non-conformances flow into defect processing and 8D problem-solving. The piece that matters most for automotive is traceability: with batch and serial management, every finished component is linked to the batches of raw material, the production order, the equipment and the operators involved — so if a field issue arises you can reconstruct genealogy and pinpoint exactly which parts are affected. That is the difference between a tightly scoped containment and a recall of everything you cannot rule out. SAP holds the records; the configuration makes them audit-ready.

Component margins are thin, so material movement shows up fast — and SAP's costing is where you catch it. Standard costing gives you a planned cost per part; actual costing and variance analysis show where reality diverged, so when steel, aluminium or resin moves you can see the impact by part and by customer rather than discovering it at close. Landed cost captures freight, duty and handling so the cost you defend in a repricing conversation is the true one. Scrap and yield are tracked into cost, which matters when material is your dominant cost driver. For OEM contracts with material-price pass-through or index clauses, having auditable actual costs is what lets you actually invoke them. The value is not just accurate numbers — it is the visibility to renegotiate or reprice with evidence while the movement is still recoverable.

Both are options, and the right answer depends on what you already run. SAP provides its own manufacturing execution through SAP Digital Manufacturing, which integrates natively with S/4HANA and can be the MES for the plant. If you have an established third-party MES that your operators and processes are built around, SAP integrates to it rather than forcing a replacement — production orders and schedules flow down to the MES, and confirmations, quantities, scrap and quality results flow back up so the ERP always reflects what actually happened on the line. The important design decision is the boundary: the ERP owns the plan, the material and the cost; the MES owns real-time execution and machine-level detail. We define that interface cleanly so you get shop-floor reality in your ERP without duplicating systems of record.

Yes, and running them together is usually the point. The OEM programmes and the OES / aftermarket channel share the same plant, the same part masters and the same costing, but differ in how they are planned, priced, packaged and sold — OEM is schedule- and sequence-driven with tight delivery windows, while aftermarket is more forecast-and-stock, sold through distributors and service networks with its own pricing and often its own branding. SAP handles both from one system: different planning strategies and sales channels sit on shared master data, so you see true demand on shared components, avoid double-planning the same production capacity, and get one consolidated view of margin across both channels. Splitting them into separate systems tends to hide exactly the cross-channel picture — shared capacity, shared inventory, blended margin — that you most need to manage.