Implementing SAP S/4HANA Private Edition at Automotive Suppliers: Where Custom Extensions Concentrate and How to Decide in the Clean Core Era

---

Introduction: Why Automotive Suppliers Accumulate Custom Code

In SAP projects at automotive suppliers, requirements tend to revolve around industry-specific practices: forecasts versus delivery call-offs, provisional pricing, chargeable component supply to subcontractors, kanban, and matching against OEM acceptance data. Because these conditions vary by OEM customer, many companies built large volumes of custom code in the ECC era, particularly in Japan.

SAP S/4HANA Cloud Private Edition (RISE with SAP) changes the rules. Modifications of SAP objects are not permitted, extensions must be clearly separated from SAP code, and only released APIs and extension points may be used preferences · blog · wordpress seo metadata. The question is no longer just whether to build an extension, but where and how to build it.

This article is written for project managers and system integrators. It maps where extensions typically concentrate across SD, MM, PP, FI, and CO, and what to verify during requirements definition.

The Ground Rules: Extensibility in Private Edition

Clean Core Principles

SAP defines a clean core as one that is up to date, documented, unmodified, consistent, efficient, and has custom extensions decoupled from SAP source code work · blog · wordpress seo metadata. Extensions follow two architectural approaches: on-stack extensibility running on S/4HANA itself, and side-by-side extensibility running on SAP BTP work · blog · wordpress seo metadata.

From the 3-Tier Model to Clean Core Levels A–D

Since August 2025, SAP’s extensibility guidance has moved from the 3-tier model to a four-level evaluation: ABAP Cloud development (Level A) and classic ABAP development (Levels B, C, and D) work · blog · article length. ABAP Cloud is recommended for all new extensions, while classic extensibility remains available under defined rules work · blog · article length. PMs should tag every item on the extension backlog with its clean core level.

Extension Hotspots by Module

The following is based on functions that Japanese automotive templates and international partners position as beyond SAP standard. It is not a statistical measure of how often each extension occurs.

SD: Integrated Order Management and Provisional Pricing

Forecasts, firm orders, and delivery call-offs
SAP standard JIT/JIS keeps forecasts and delivery call-offs in separate tables within the scheduling agreement preferences · communication · reference links. In practice, however, suppliers must ingest OEM-specific EDI formats, perform reconciliation, and match acceptance data, which a Japanese template addresses through integration with an external integrated order management system work · blog · headings.

Provisional pricing and retroactive price changes
Japanese automotive suppliers commonly order, ship, and invoice at a provisional price, then update to the final price once agreed. One template delivers provisional sales pricing, retroactive billing price adjustment, and provisional purchase pricing as proprietary add-on functions work · blog · headings. Since retroactive billing itself exists in SAP standard work · blog, the key is to narrow the extension to Japan-specific elements such as validity periods and change history for provisional prices.

JIT/JIS and OEM-specific requirements
SAP’s next-generation JIT/JIS is designed to let customers introduce their own process steps through extensibility work · blog · target audience. Custom EDI fields that must appear on outbound labels are a typical requirement worldwide assets.dm.ux.sap.

MM: Provisional Purchase Pricing and Chargeable Subcontracting

Provisional purchase pricing
Purchase orders are issued at a provisional price and corrected when the final price is set, with a warning or error if goods are received while the price is still provisional work · blog · headings.

Chargeable component supply to subcontractors
In S/4HANA, subcontracting with chargeable components (SCC) now works with the Material Ledger, and adoption has grown learning.sap. However, SAP’s standard scenario does not define how to handle open purchase orders placed at the old price when the component price changes sap. That gap must be covered by an extension or by operating rules.

Cumulative quantity (CUM) reconciliation
Some partners claim SAP standard does not offer adequate CUM reconciliation community.sap, while SAP documentation describes cumulative quantity reconciliation for scheduling agreements community.sap. Validate with real data before deciding.

PP: Kanban, MES, and Shop-Floor Integration

S/4HANA provides Kanban (PP-KAB), Repetitive Manufacturing (PP-REM), and MES integration as standard assets.dm.ux.sap. Yet one Japanese template states that Japanese-style kanban operation is difficult with standard functions alone, and provides interfaces to bring production instructions, actuals, shipments, and receipts into the ERP work · blog · headings. PwC Japan also urges teams to drop the assumption that ERP only plans and MES only collects actuals, and to redesign the division of roles preferences · communication · reference links. Settle the ERP–MES split before debating PP extensions.

FI: Acceptance Matching, Payment Matching, and Self-Billing

Matching OEM acceptance data and incoming payments is part of the template scope work · blog · headings. For self-billing, where the OEM issues the invoice, SAP offers a separate product, SAP Self-Billing Cockpit, designed to identify errors and deviations early community.sap.

CO: Analytical Needs Covered Outside the Core

Actual costing is delivered as a standard S/4HANA capability sap. The Japanese template provides segment and product profitability and multidimensional cost visualization on SAP Analytics Cloud rather than inside the ERP work · blog · headings. We found no evidence indicating how common CO-specific custom code is.

Summary Table

Module	Extension candidates	SAP standard / related products	Implementation approach
SD	Integrated order management, provisional pricing, OEM-specific EDI and labels	Scheduling agreements, JIT/JIS, retroactive billing	External integration, extension points
MM	Provisional purchase pricing, SCC price changes, CUM reconciliation	SCC, cumulative quantity reconciliation	Validate standard first, then minimal extension
PP	Kanban, MES, and actuals interfaces	Kanban, REM, MES integration	API integration, redesigned role split
FI	Acceptance and payment matching	SAP Self-Billing Cockpit	Prefer industry products
CO	Multidimensional profitability and cost analytics	Material Ledger, actual costing	Analytics platform (e.g., SAC)

Practical Checklist for PMs and System Integrators

Requirements (Fit-to-Standard)

1. Have you confirmed what standard functions and SAP industry products (JIT/JIS, Self-Billing Cockpit, Returnable Packaging Management) can cover?
2. Have you separated mandatory industry-practice requirements from requests that merely preserve legacy operations?
3. Have you validated contested areas, such as CUM reconciliation and retroactive billing, with real data?

Design and Build

1. Is every extension tagged with a clean core level (A–D), with justification and a remediation plan for Levels C and D?
2. Are you choosing between on-stack and side-by-side (SAP BTP) extensions based on data volume and response-time needs?
3. Have legacy ECC extensions been classified into replaceable by standard, needs remediation, and retain savictech?

Governance

1. Is extension approval a formal steering committee decision?
2. Can upgrade impact analysis be sustained after go-live?

Conclusion

In S/4HANA Private Edition projects at automotive suppliers, integrated order management, provisional pricing, chargeable subcontracting, kanban integration, and acceptance matching are where extensions concentrate. At the same time, many areas that required custom code in ECC, including retroactive billing, SCC, JIT/JIS, and actual costing, are now increasingly covered by standard functionality.

The job for PMs and system integrators is to identify the differences that truly matter for the business and implement them in line with clean core rules, decoupled from SAP code. Managing extensions by asking at what level and where to build them, rather than simply whether to build them, will shape upgrade effort and run costs after go-live.

---

References

1. SAP Learning, “Evaluating Use Cases for SAP S/4HANA Cloud Private Edition and SAP S/4HANA” https://learning.sap.com/courses/practicing-clean-core-extensibility-for-sap-s-4hana-cloud/evaluating-use-cases-for-sap-s-4hana-cloud-private-edition-and-sap-s-4hana_ef9d96d0-149d-447e-b7d6-11729ae19995
2. SAP Community, “For an in-depth look at clean core and how to implement it” https://community.sap.com/t5/technology-blog-posts-by-sap/for-an-in-depth-look-at-clean-core-and-how-to-implement-it-read-our-clean/ba-p/13984597
3. SAP Community, “ABAP Platform in SAP S/4HANA Cloud Private Edition and SAP S/4HANA 2025” https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/abap-platform-in-sap-s-4hana-cloud-private-edition-and-sap-s-4hana-2025/ba-p/14289979
4. PwC Japan, “SAP JIS/JIT & REM and MES Integration Template for the Automotive Industry” (Japanese) https://www.pwc.com/jp/ja/services/consulting/business-applications/sap/jis-jit-mes-template.html
5. Kobelco Systems, “HI-KORT for Auto Supplier: SAP ERP Template for Automotive Parts Manufacturers” (Japanese) https://www.kobelcosys.co.jp/solution_service/detail/hikort_auto/
6. SAP Help Portal, “Returnable Packaging” (references Retroactive Billing, SD-SLS-OA) https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/7b24a64d9d0941bda1afa753263d9e39/f265b65334e6b54ce10000000a174cb4.html
7. SAP Community, “Next-generation Just-In-Time Supply to Customer | Part 3” https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/next-generation-just-in-time-supply-to-customer-part-3/ba-p/13496929
8. SFC Automotive, “SAP Consulting” http://www.sfc-automotive.com/sap-consulting
9. Business Engineering Corporation, “SAP Chargeable Subcontracting Solution Explained, Part 1” (Japanese) https://column.b-en-g.co.jp/paid-supply01
10. Business Engineering Corporation, “SAP Chargeable Subcontracting Solution Explained, Part 2” (Japanese) https://column.b-en-g.co.jp/paid-supply02?hs_amp=true
11. AIM Computer Solutions, “Unlocking Automotive EDI Efficiency” https://www.aimcom.com/automotive-edi-white-paper/
12. SAP Help Portal, “Features” (cumulative quantity reconciliation) https://help.sap.com/docs/SAP_ERP/00b86df2555f4c83b47b97a5c1223904/4f7bb6535fe6b74ce10000000a174cb4.html
13. SAP Help Portal, “Key Features” (PP-KAB, PP-REM, PP-MES) https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/21aead0c98bd4755abdacd91c99e3393/a97b953db94145b3b8976dc5096cce32.html
14. SAP Learning, “Describing Features of SAP Self-Billing Cockpit” https://learning.sap.com/courses/describing-sap-for-automotive-supply-chain-and-manufacturing/describing-features-of-sap-self-billing-cockpit_f7b32e12-a659-47bd-96fa-4e801369f033
15. SAP Community, “How Product Cost Controlling Works in SAP S/4HANA” (Japanese) https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/sap-s-4hana%E3%81%AB%E3%81%8A%E3%81%91%E3%82%8B%E8%A3%BD%E5%93%81%E5%8E%9F%E4%BE%A1%E7%AE%A1%E7%90%86%E3%81%AE%E4%BB%95%E7%B5%84%E3%81%BF%E3%81%A8%E3%81%AF/ba-p/13552121
16. SAP, “RISE with SAP” https://www.sap.com/products/erp/rise.html

---

Disclaimer

Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.

---

Back to Top