SAP Business Planning and Consolidation (BPC) review

The short answer

Buy SAP BPC Consider it only if you already run it, or already hold SAP licences and your SAP account team is actively proposing it for planning and consolidation inside your existing environment. Business Planning and Consolidation provides financial consolidation, planning and budgeting natively integrated with SAP ERP environments, and that integration is the entire reason anyone shortlists it.

Skip it as a new purchase until SAP confirms in writing that it is still sold to new customers and tells you the mainstream maintenance end date. The product URL returned HTTP 404 on 16 October 2026, which is not proof of retirement but is a reason to get the product's status settled before you spend evaluation time or sign a multi-year term.

Where SAP BPC fits

SAP BPC pricing

There is no SAP price to report for this product. No SAP page for Business Planning and Consolidation could be accessed on 16 October 2026: the product URL and three candidate pricing paths under it all returned HTTP 404, and a WebFetch attempt on the product URL returned HTTP 403. So no figure and no licence metric is recorded here, because none was seen, and nothing below is an estimate. Treat any figure you find on a third-party site as unverified until SAP or your SAP partner puts it in writing.

Four things to settle, and the first one is not about money.

1. Which product SAP is actually quoting. Business Planning and Consolidation is the older SAP planning and consolidation product and sits alongside SAP's newer planning and group reporting offerings. Ask SAP in writing which name is on the quote, whether this product is still sold to new customers, and what the support horizon for it is. Everything else depends on that answer.
2. The licence model, which could not be read from SAP's own pages. Ask whether the licence is per named user, per processor or per entity, and whether it is a perpetual licence with annual maintenance or a subscription. Those two shapes produce completely different budgets over five years, and the difference is not something to discover after signing.
3. The platform the quote assumes. Deployment matters here more than in a pure cloud product. Ask what database, application server and hosting are required, who pays for that infrastructure, and whether licences you already hold can be counted toward it. An apparently competitive software number can be undone by an infrastructure line nobody quoted.
4. Services, which usually dominate year one on an SAP planning project. Get licence, infrastructure and implementation quoted as three separate numbers, ask whether the work comes from SAP or a partner, and get a fixed-price statement of work if you can. Each of those three is negotiated differently and bundling them hides where your money is going.

What costs extra

• No add-on list and no add-on prices could be read, because no SAP page for this product was reachable on 16 October 2026.
• Infrastructure is the line most likely to be missing from a first quote on an on-premise or hosted deployment. Ask for it explicitly rather than assuming the software figure is the whole cost.
• A future migration. If this product's support horizon is shorter than your intended contract, ask now what moving to SAP's current planning or group reporting product would cost, and get that estimate alongside the quote rather than at the point you need it.

Implementation and commercial terms

Every row below records what could and could not be confirmed as of 16 October 2026. The first two rows are the findings. The rest are gaps, and each gap is a question to put to SAP in writing.

Published price

Could not be accessed on 16 October 2026. The product URL and three pricing paths returned HTTP 404.

Product page status

HTTP 404 on the product URL, and HTTP 403 to a WebFetch attempt on the same URL.

Still sold to new customers

Could not be confirmed from SAP's own site. Ask SAP directly.

Licence model

Unverified. Ask whether it is per named user, per processor or per entity, and perpetual or subscription.

Platform and hosting

Unverified. Ask what database, application server and hosting the quote assumes, and who pays for it.

Implementation fee

Unverified. Ask whether implementation comes from SAP or a partner, and ask for a fixed-price statement of work.

Free trial

Unverified. Ask whether a trial, sandbox or proof of concept system is available.

Budget nothing until SAP has answered the status question. Get written confirmation of which product is being quoted, whether it is still sold to new customers, and what the mainstream maintenance end date and upgrade path are. Then ask for licence, infrastructure and services as three separate numbers, check what your existing SAP agreement already covers and whether it sets your discount level, and ask what a later migration to SAP's current planning product would cost. If any of those answers is vague, that is your finding. For a readable comparison while you wait, IBM Cognos publishes two per user rates and Cube publishes the entity counts behind its tiers.

Source: SAP Business Planning and Consolidation product URL (not reachable), checked 16 October 2026. Confirm current prices with the vendor before you budget.

What SAP BPC gives up

How SAP BPC compares

On 16 October 2026 the honest comparison in this category is between vendors you can read something about and vendors you cannot. SAP's product page for this product returned HTTP 404. Oracle's EPM pricing paths did the same. Cube and Datarails publish the scale limits that set their tiers. IBM publishes two per user rates for Cognos Analytics bought from IBM. Every figure below comes from that vendor's own page, checked on 16 October 2026, and anything unpublished is recorded as unpublished rather than estimated.

What to ask in an SAP BPC demo

No trial terms could be verified, because the product URL returned HTTP 404 on 16 October 2026. So this is a conversation with SAP or your SAP partner rather than a product evaluation, and for this product the first two questions decide whether the rest of it is worth having.

1. Ask whether the product is still sold to new customers, and get the answer in writing. The URL for Business Planning and Consolidation no longer resolves on SAP's own site, so ask what it has been replaced by and which product SAP is recommending for your use case.
2. Ask for the mainstream maintenance end date and the upgrade path, in writing, before anything else. Include what a later migration to SAP's current planning or group reporting product would cost, because that number belongs in the business case for this one.
3. Get the licence model named. Per named user, per processor or per entity, and perpetual with maintenance or subscription. Then ask what your existing SAP agreement already covers and whether it sets the discount level on this scope.
4. Separate the three numbers. Software licence or subscription, the platform it runs on including database, application server and hosting, and the implementation work. Ask who pays for the infrastructure and ask for a fixed-price statement of work on the services.
5. Ask for a proof of concept on your own group structure. Load your real entities, intercompany balances and one currency translation, and see how much of the work is configuration against how much is custom build. On an SAP planning project that ratio is the project risk, and it is the thing a scripted demo will not show you.

Frequently asked questions about SAP BPC