Part of the Finance systems at end of life series.
The consolidation and EPM market runs on acronyms, and several of those acronyms refer to more than one product. A group CFO who mis-identifies which platform the group actually runs - BPC versus BFC, Oracle EPM versus HFM, 10.1 NetWeaver versus 10.1 for Microsoft - cannot read a vendor lifecycle notice correctly. This page does one job: it identifies each product in plain English and states what the vendor has published about its support horizon. It does not recommend a destination. For the full story on each product's lifecycle, follow the links into the finance systems end-of-life series.
Why these acronyms get confused
BPC and BFC are both SAP products, both handle consolidation, and both carry version numbers in the 10.x range - yet they have entirely separate codebases, separate support timelines, and separate histories. Oracle EPM is a family name, not a single application; HFM is one member of that family. Cognos Controller sits inside IBM's portfolio but is unrelated to SAP's products despite the overlap in functional territory. The ERP underneath - SAP ECC, SAP S/4HANA, Oracle E-Business Suite - is a separate layer again. Group Reporting, SAP's newer consolidation capability, is not BPC. Getting the identification wrong before reading a lifecycle notice is how finance teams misread their own risk position.
SAP BPC full form and meaning
SAP BPC stands for SAP Business Planning and Consolidation, and the abbreviation covers two technically distinct products that share a name but run on different platforms.
SAP BPC 10.1 for Microsoft runs on a Microsoft SQL Server and Analysis Services stack. According to SAP's published maintenance timeline, mainstream maintenance for this version ended in June 2026.
SAP BPC 10.1 for SAP NetWeaver runs on SAP's own NetWeaver platform. SAP's published timeline shows mainstream maintenance running to 31 December 2027, with optional extended maintenance available to 31 December 2030.
SAP BPC 11.x on BW/4HANA is a further variant, embedded within SAP's BW/4HANA data warehouse. Its lifecycle follows BW/4HANA's own roadmap rather than the 10.1 timelines above.
The practical consequence is that two group CFOs who both say 'we run BPC' may be looking at materially different support horizons depending on which platform variant their IT team actually deployed. Confirming the platform stack is the first step before reading any SAP lifecycle notice. The full lifecycle analysis is in the SAP BPC end-of-life article.
What is SAP BFC?
SAP BFC stands for SAP Business Objects Financial Consolidation. It is the former Cartesis FC product, acquired by Business Objects and then by SAP, and it is sometimes written 'SAP Financial Consolidation' or simply 'FC' in older contracts and IT inventories.
BFC is a standalone consolidation application with its own codebase, entirely separate from BPC. SAP has extended mainstream maintenance for BFC 10.1 to the end of 2030 and has stated that it plans no new functional investment in the product. The complete lifecycle picture, including what 'no new functional investment' means in practice for a group finance team, is in the SAP BFC end-of-life article, which is this site's authority on that product.
What is Oracle EPM?
Oracle EPM is a product family name, not a single application. It covers Oracle's enterprise performance management portfolio, which includes both the on-premises Hyperion suite and Oracle's cloud EPM services.
The on-premises Hyperion applications - Hyperion Financial Management, Hyperion Planning, FDMEE, Financial Close Manager, Data Relationship Management and others - are the products that most group finance teams running legacy Oracle EPM actually operate. Oracle EPM Cloud is a separate, cloud-native family. Describing Oracle EPM as a single product, or assuming that an on-premises HFM installation and an Oracle EPM Cloud subscription are interchangeable, is a common source of confusion when reading Oracle's published roadmap materials.
What is Hyperion Financial Management (HFM)?
Hyperion Financial Management, universally abbreviated HFM, is Oracle's on-premises statutory consolidation application and one member of the Hyperion suite within the Oracle EPM family.
HFM handles multi-entity consolidation, intercompany eliminations, currency translation and statutory reporting. It is distinct from Hyperion Planning, which handles budgeting and forecasting, though the two applications are frequently deployed together.
On support horizon: Oracle's Lifetime Support Policy for Oracle Applications, with an effective date of 7 August 2026, states that Hyperion 11.2 - covering HFM, Planning, FDMEE, Financial Close Manager, DRM and the other Continuous Innovation releases - has Premier Support through at least December 2037. Oracle reviews this date annually and has historically moved it forward approximately one year at a time. Hyperion is not end-of-life, and any planning assumption that treats it as such is not consistent with Oracle's published position. The detailed analysis of what Oracle has actually published, and what the 'at least' qualifier means, is in the Hyperion lifecycle article.
What is Cognos Controller?
IBM Cognos Controller is IBM's on-premises statutory consolidation application, part of the IBM Cognos portfolio and unrelated to SAP's or Oracle's product families.
IBM's published lifecycle information shows that Cognos Controller 11.0.x moved from standard to extended and sustained support on 30 April 2026, with end of extended support on 30 April 2030. Support for the earlier 10.3.x release ended in September 2021 per IBM's lifecycle page, so groups still on that version are outside IBM's standard support framework. The full support-horizon analysis is in the Cognos Controller end-of-support article.
Is SAP BPC going away?
The answer depends entirely on which BPC variant the group runs. For SAP BPC 10.1 for Microsoft, mainstream maintenance ended in June 2026 per SAP's published timeline - that variant has reached the end of its standard support life. For SAP BPC 10.1 for NetWeaver, mainstream maintenance runs to 31 December 2027 with optional extended maintenance to 31 December 2030 per SAP's published maintenance timeline. BPC 11.x on BW/4HANA follows a separate roadmap.
SAP has not published BPC on the same 'no new functional investment' terms it has applied to BFC, but the maintenance horizon for the 10.1 Microsoft variant is already behind us. A finance team that has not yet confirmed which variant it runs should do that before drawing any conclusion about urgency. The detailed lifecycle dates and their implications are in the SAP BPC end-of-life article.
What to do with this identification
This page stops at identification. Once a finance team has confirmed which product it runs and which support line applies, the next question is what options exist - and those options differ by product, by group size, and by the maturity of the finance function around the tool. The finance system end-of-support options article sets out the structural choices without ranking them. If the broader question is where the finance function stands relative to the level-5 AI-embedded frontier, the end-of-life series hub connects this identification work to that wider picture.
Common questions
What does SAP BFC stand for?
SAP BFC stands for SAP Business Objects Financial Consolidation. It is the former Cartesis FC product, acquired by Business Objects and subsequently by SAP, and is sometimes written 'SAP Financial Consolidation' or 'FC' in older contracts. It is a standalone consolidation application entirely separate from SAP BPC, with its own codebase and support timeline.
What is the difference between SAP BPC and SAP BFC?
SAP BPC (Business Planning and Consolidation) and SAP BFC (Business Objects Financial Consolidation) are two distinct SAP products that both cover consolidation but have separate codebases and separate support horizons. BPC originated from OutlookSoft; BFC originated from Cartesis. A group running BFC is not on the same support timeline as a group running BPC, and reading one product's lifecycle notice as if it applied to the other will produce the wrong conclusion.
Is Oracle HFM the same as Oracle EPM?
No. Oracle EPM is a family name covering multiple on-premises Hyperion applications and Oracle's cloud EPM services. Hyperion Financial Management (HFM) is one specific on-premises consolidation application within that family. A group that runs HFM is running one member of the Oracle EPM family, not the family as a whole.
What is the support status of Hyperion Financial Management in 2025?
Oracle's Lifetime Support Policy for Oracle Applications, with an effective date of 7 August 2026, states that Hyperion 11.2 - which includes HFM - has Premier Support through at least December 2037. Oracle reviews this date annually and has historically moved it forward approximately one year at a time. Hyperion is not end-of-life under Oracle's current published position.
When does IBM Cognos Controller support end?
IBM's lifecycle page shows that Cognos Controller 11.0.x moved from standard to extended and sustained support on 30 April 2026, with end of extended support on 30 April 2030. The earlier 10.3.x release reached end of support in September 2021 per IBM's published lifecycle information.