Running SAP? See how much you can save before your next renewal. Free analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
What SAP PP Third-Party Support Actually Means
SAP Production Planning (PP) orchestrates the entire manufacturing execution cycle: demand planning, MRP net requirements calculation, planned order creation, production order release, goods issue, operations confirmation, and goods receipt. In discrete manufacturing, PP manages work centres, routings, production orders, and shop floor control. In process manufacturing (PP-PI), it manages process orders, master recipes, process instructions, and PI sheets. For automotive suppliers, PP supports KANBAN, repetitive manufacturing (REM), and production supply areas (PSA) aligned with just-in-time delivery schedules. The PP module is not administrative software — it is the control system for your factory floor, integrated with MM for material availability, QM for quality inspection, PM for maintenance, and SD for make-to-order sales order production.
Third-party support for SAP PP provides continued maintenance, security advisory, and incident resolution for SAP ECC PP on EHP0 through EHP8, without SAP. Your MRP configurations, BOM structures, routing data, work centre calendars, capacity planning setup, production order types, and all PP-MM/PP-QM/PP-PM integration configurations remain supported under a TPS provider's SLA. SAP's maintenance fee escalation, extended maintenance surcharges, and S/4HANA migration pressure are eliminated from your planning horizon.
The strategic reality: SAP PP in S/4HANA introduces fundamental changes to the MRP processing architecture that require re-testing every custom MRP user exit, every ATP check configuration, and every PP-PS project manufacturing integration. For a mid-size manufacturer with 50–200 active work centres, 5,000–50,000 BOM positions, and custom PP-QM inspection lot triggering logic, the S/4HANA PP migration programme costs £600K–£2.8M and takes 18–36 months. SAP TPS provides the intelligent alternative.
SAP PP ECC Version Support Matrix
| SAP ECC Version | EHP Level | SAP Support Status | Mainstream End | TPS Available |
|---|---|---|---|---|
| SAP ECC 5.0 | — | Extended Maint. | Expired 2017 | Yes |
| SAP ECC 6.0 EHP0–EHP2 | EHP0–2 | Extended Maint. | Dec 2027 (w/surcharge) | Yes |
| SAP ECC 6.0 EHP3–EHP5 | EHP3–5 | Extended Maint. | Dec 2027 (w/surcharge) | Yes |
| SAP ECC 6.0 EHP6–EHP8 | EHP6–8 | Mainstream (→2027) | Dec 2027 | Yes |
The 2027 deadline creates commercial pressure that SAP uses deliberately. For manufacturers running complex PP environments, the honest assessment is: a migration programme started in 2025 will complete in 2028–2030 at best. TPS bridges that gap — supporting your ECC PP environment through the migration programme, maintaining production continuity while your S/4HANA programme team works without artificial urgency. The extended maintenance surcharge for EHP0–EHP5 adds £100K–£400K annually for large manufacturers — costs that TPS eliminates immediately.
Why SAP PP Customers Choose Third-Party Support
Force 1 — S/4HANA PP MRP Architecture Change
SAP's S/4HANA PP reimplementation replaces Classic MRP (transaction MD01/MD02/MD03) with MRP Live — a redesigned MRP processing engine that uses HANA in-memory processing for net requirements calculation. The change sounds like a performance improvement; for complex environments it is a migration barrier:
- MRP user exit deprecation: Classic MRP supports extensive user exit customisation — MDBF0001 (before MRP), MDBF0005 (after MRP), and multiple BAdIs for planning file entry control, lot size calculation, and source determination. S/4HANA's MRP Live has a different BAdI framework. All custom MRP user exits must be re-implemented, re-tested, and validated against historical MRP results — a process requiring 6–12 months of regression testing in manufacturing environments with complex ATP and special procurement logic.
- Predictive MRP (pMRP) for automotive: SAP S/4HANA introduces Predictive MRP as an additional planning layer for automotive demand-driven environments. pMRP requires configuration of forecast-driven MRP parameters that do not directly translate from ECC Classic MRP settings. Automotive Tier-1 suppliers operating JIT/JIS delivery models with customer-transmitted delivery schedules (via EDIFACT DELJIT/DELFOR messages) must re-validate their MRP-driven procurement planning behaviour against new pMRP algorithms.
- Production order re-architecture: S/4HANA simplifies the production order document structure in the Universal Journal. Custom production order enhancements, CO settlement rules, and cost object controlling configurations require re-testing. For manufacturers using Production Order Settlement to CO-PA for product costing, the CO-PA re-architecture required for S/4HANA (Account-Based CO-PA replacing Costing-Based CO-PA) intersects directly with PP cost object controlling — creating a complex interdependency that extends the PP migration programme.
Force 2 — PP-QM Integration and GxP Constraints
Pharmaceutical and food manufacturers using SAP PP integrated with QM for GMP production environments have specific constraints. Inspection lots triggered on goods receipt from production (movement type 101) and on in-process inspections (PP-PI process instructions triggering QM inspection lots) are part of the validated production system. Under GAMP 5/EU GMP Annex 11/FDA 21 CFR Part 11 Computer System Validation requirements, any change to the PP-QM integration behaviour requires a formal Change Control procedure and re-validation of the affected processes. The S/4HANA migration of PP-QM integration is a validated system change — meaning a full IQ/OQ/PQ validation re-execution programme at a cost of £180K–£650K before any PP go-live in a regulated manufacturing environment. TPS preserves the validated ECC PP-QM configuration without triggering a validation event.
Force 3 — Automotive JIT/JIS Delivery Constraint
Automotive Tier-1 and Tier-2 suppliers operating Just-in-Time (JIT) or Just-in-Sequence (JIS) delivery models with OEM customers have production planning systems certified against specific OEM logistics requirements — BMW's KANBAN integration, VW Group's delivery schedule processing, Toyota's JIDOKA-aligned production control. Any SAP PP platform change that alters the delivery schedule processing logic (EDIFACT DELJIT/DELFOR message handling, scheduling agreement release processing, or JIT delivery call generation) must be regression tested against OEM-defined test cases and approved by the OEM logistics team before deployment. These OEM approval processes take 12–24 months. No automotive manufacturer can complete a PP migration in the timeframe SAP's account teams suggest.
What would SAP PP TPS save your organisation?
GoVendorFree provides free SAP PP support cost assessments. We model your exact ECC environment, NLV, and extended maintenance exposure to calculate your precise TPS saving.
Get Your Free PP Cost AssessmentWhat SAP PP TPS Covers
GoVendorFree's SAP PP third-party support covers the complete Production Planning module and manufacturing execution stack:
- Master Data: Bills of Material (BOM), routings/master recipes, work centres/resources, production versions, and engineering change management (ECM) integration
- MRP/Planning: MRP Classic (MD01/MD02/MD03/MD04), planning file entries, MRP areas, special procurement keys, lot sizing procedures, and safety stock management
- Planned Orders and Production Orders: Planned order management, production order creation and release, order confirmation (CO11N/MFBF), and goods issue/receipt for production orders
- Capacity Planning: Work centre capacity, capacity requirements planning (CM01/CM21), available capacity management, and shift scheduling integration
- Repetitive Manufacturing (REM): Production line configuration, MFBF backflush, make-to-stock repetitive manufacturing, and line takt time management
- KANBAN: KANBAN control cycles, signal types (manual, classical, event-driven), KANBAN board configuration, and supply area management
- PP-PI (Process Industries): Process orders, master recipes, process instructions, PI sheets, and PP-PI integration with QM and batch management
- PP-MM Integration: MRP-driven purchase requisition generation, planned order to purchase order conversion, and production supply area replenishment
- PP-QM Integration: Inspection lot triggering at goods receipt from production, in-process inspection integration, and QM usage decision integration with production order status
- PP-CO Integration: Production order cost object controlling, goods issue valuation, confirmation costing, variance calculation, and settlement to CO-PA
Industry Cohort Analysis: Who Benefits Most from SAP PP TPS
Discrete Manufacturing — Multi-Level BOM and Complex Routing
Discrete manufacturers with multi-level BOM structures (5–15 levels), complex routings with 30–100 operations per finished good, and make-to-order sales order production (PP-SD integration) have the deepest dependency on stable, well-understood MRP logic. For an industrial equipment manufacturer with 2,000–5,000 configurable finished goods, the MRP planning parameters, lot sizing rules, and PP-SD integration logic represent years of operational tuning. Disrupting this with a S/4HANA PP migration without sufficient regression testing time is a production risk the business cannot accept. Combined SAP TPS across PP, MM, and FI typically delivers £150K–£620K annual saving for large discrete manufacturers.
Process Industry — Pharmaceutical and Chemical Manufacturing
Process manufacturers running SAP PP-PI for GMP-compliant batch manufacturing have the most constrained migration timeline. EU GMP Annex 11 and FDA 21 CFR Part 11 validation requirements mean that any S/4HANA PP-PI migration requires a full validation programme before go-live — independent of how well the technical migration is executed. For a mid-size pharmaceutical manufacturer producing 200–500 registered products across 10–30 production lines, the PP-PI validation programme takes 12–24 months and costs £180K–£650K. TPS preserves the validated system configuration, eliminates the validation trigger, and delivers 64–65% reduction in annual support costs.
Automotive Supply Chain — Tier-1 and Tier-2 Suppliers
Automotive suppliers embedded in OEM just-in-time supply chains have PP environments tightly coupled to OEM logistics systems. Delivery schedule message processing (EDIFACT DELJIT/DELFOR via SAP EDI — WE02/WE19/VL10D/MIGO), scheduling agreement call generation, and JIS sequence call management are PP configurations certified against specific OEM acceptance tests. Changing the PP platform requires OEM re-certification — a process controlled by the OEM, not by the supplier. Volkswagen Group, BMW, Toyota, and Stellantis all have supplier qualification processes for ERP system changes that take 12–24 months. No automotive supplier can migrate PP to S/4HANA on SAP's preferred timeline.
SAP PP TPS Cost Model
SAP's Migration Pressure Tactics for PP Customers
- "MRP Live in S/4HANA runs faster than Classic MRP." True for large MRP runs on HANA in-memory infrastructure. Irrelevant for most manufacturers whose ECC MRP runs complete within the overnight planning window already. Paying £600K–£2.8M for a migration to achieve faster MRP runs that were already within SLA is not a rational business case.
- "SAP PP in ECC will not get regulatory updates after 2027." Regulatory updates for PP are primarily driven by country-specific legal changes (which are generally limited for manufacturing modules) and by ISO/industry standard updates. GoVendorFree's TPS provides all required country-specific legal changes as part of the service. Manufacturing process regulatory compliance is controlled by quality management systems (IATF/GMP) — not by SAP ECC maintenance status.
- "PPDS (Production Planning and Detailed Scheduling) is better in S/4HANA." S/4HANA embedded PPDS (from SAP APO) is a genuine improvement for organisations that need advanced detailed scheduling. But PPDS migration from a standalone APO or integrated PP environment requires separate migration planning — it is not a simple PP upgrade. The PP/DS migration complexity is additional to the core PP migration cost.
- "Your competitors have already moved to S/4HANA." This claim does not survive scrutiny. The majority of large manufacturing SAP ECC customers have not completed S/4HANA migrations as of 2026. SAP's own data suggests less than 30% of ECC customer licence revenue has transitioned to S/4HANA. Your competitors on TPS are making rational financial decisions, not falling behind.
Ready to assess SAP PP third-party support?
GoVendorFree has supported SAP PP environments across discrete manufacturing, automotive, and pharmaceutical sectors since 2016. Our assessment is free and delivers a precise saving calculation.
Start Your Free SAP PP AssessmentTransitioning to SAP PP TPS: The Process
- PP landscape audit (weeks 1–2): Complete documentation of your SAP PP environment — EHP level, active PP sub-modules (discrete, REM, KANBAN, PI), MRP customisation inventory, BOM/routing complexity, and integration map (PP-MM, PP-QM, PP-PM, PP-SD, PP-CO).
- Production calendar alignment: TPS activation scheduled around plant shutdown periods, model year changeovers (automotive), and production programme milestones. Zero transition impact on live production planning.
- Regulatory compliance documentation: For GMP-regulated environments, GoVendorFree provides TPS transition documentation compatible with GAMP 5 Change Control requirements — ensuring the TPS transition does not trigger a validation event for the production system.
- PP-specialist engineer assignment: Dedicated PP engineers with specific industry experience (automotive, pharmaceutical, or discrete manufacturing) assigned to your account from day one.
- SAP maintenance wind-down: GoVendorFree manages SAP contract termination and S-user procedures, including all notification and documentation requirements.