SAP’s commitments to the European Commission do not automatically release every BPC customer from a combined maintenance agreement. But they do change the conversation—and give BPC NetWeaver customers a timely reason to examine support, cost, and roadmap decisions that may have been treated as fixed.
In July 2026, the European Commission accepted legally binding commitments from SAP concerning maintenance and support for on-premises business software. The commitments apply worldwide for ten years. They address several practices that the Commission believed could restrict customers from changing support providers, reducing maintenance, or returning to SAP support later.
Among the changes are greater flexibility to organize support across parts of an SAP landscape, broader access to alternative licensing metrics, clearer rules around initial support terms, elimination of reinstatement fees, and reduced back-maintenance charges for customers who return to SAP support.
For CIOs, this is not simply a procurement footnote. It may create more room to decide which systems still justify SAP maintenance, which require more specialized application support, and which should be modernized or replaced.
SAP BPC 10.1 for SAP NetWeaver remains important to many finance organizations. It often supports planning, forecasting, consolidation, reporting, and other processes that have been refined over many years. Replacing it can be a major transformation involving data, processes, integrations, controls, user adoption, and organizational change.
At the same time, BPC NetWeaver is approaching a significant maintenance milestone. SAP mainstream maintenance runs through December 31, 2027, with optional extended maintenance through December 31, 2030. SAP has also stated that it does not plan further product enhancements for BPC NetWeaver.
That creates a familiar dilemma. A customer may not be ready—or may not have a compelling business case—to replace BPC. Yet the support experience may already feel increasingly disconnected from the needs of the operating environment. Many customers pay SAP maintenance while also relying on internal experts or outside BPC specialists for the practical help required to keep the application performing.
Historically, customers with BPC included alongside ERP, BW, and other SAP products often assumed that BPC support could not be treated separately. Even if a specialist provider offered better day-to-day BPC support, the customer risked adding another bill without reducing SAP maintenance. That made a better service model look uneconomic.
SAP’s new commitments create a reason to revisit that assumption. Depending on the customer’s agreements, licensing metric, product groupings, BPC usage, and SAP’s implementation rules, it may be possible to organize support differently or reduce duplicative costs.
The word “may” matters. An actively used BPC environment should not automatically be described as shelfware, and the absence of future enhancements does not by itself prove that a particular contract can be terminated. Every customer should review its own agreements and the final published procedures before acting.
Column5 created BPC Lifeline for organizations that want to keep BPC stable, responsive, and useful while retaining control of their long-term roadmap. It is not a promise that BPC should run forever, and it is not a forced migration program. It is a support and modernization option designed around the system the customer actually operates.
Specialist BPC application support with priority-based, contractual response commitments.
Proactive health assessments and quarterly reviews—not only reactive ticket handling.
Performance tuning across consolidations, business rules, data flows, and the user experience.
BPC eLearning to reduce knowledge risk and support administrator and user continuity.
Optional managed hosting and clearer ownership across the application and infrastructure stack.
Optional governed AI through Darwin AI, allowing customers to introduce a modern natural-language experience without first replacing BPC.
For customers that are eligible to separate BPC-related support, Lifeline may also reduce duplicative spending. For others, it can still fill operational gaps while SAP maintenance remains in place. The correct answer depends on the economics and risks of each environment.
How is BPC licensed and grouped within our current SAP maintenance agreements?
What portion of our annual SAP maintenance and outside-services spend is attributable to keeping BPC operational?
Which BPC support services do we actually receive from SAP, and which are performed by internal staff or specialists?
What technical, security, skills, and performance risks must we manage through 2027 and 2030?
Would we create more value by maintaining BPC longer, modernizing selected parts of the experience, or accelerating migration?
The most important result of SAP’s commitments is not that every customer should leave SAP support. It is that customers may have more choices and therefore more leverage to align support with business value.
For BPC NetWeaver customers, that means evaluating the support contract and the application roadmap together. A thoughtful review can determine whether Lifeline is a better service model, a bridge to a future EPM platform, or simply one option among several.
Column5 can help assess the current contract structure, BPC support costs, environment health, and modernization choices—while preserving SAP support where it continues to make sense.