BW in 2027: what the dates mean

Contoso Motor Co. runs SAP BW 7.5 on SAP HANA in its own data center, in a three-system landscape BWD / BWQ / BWP. BWP has fed finance and sales reporting for more than a decade: margin by customer, sales by channel, inventory turns and the monthly management pack. After the SAP S/4HANA conversion, its extractors read from CMP instead of the old ECC system EP1. Noor, Contoso's data and analytics lead, has been asked by Grace's steering group for a recommendation on BWP. It starts with the dates.

The maintenance positions

What the dates do and do not mean

End of mainstream maintenance does not switch BW off. BWP will keep running on 1 January 2028. What changes is support: without extended maintenance, no new support packages, legal changes or security fixes. Extended maintenance costs extra and ends in 2030 anyway. So the real question is not "what happens in 2028?" but "what will Contoso's analytics platform be in 2031, and how do we get there with proof that the numbers stay right?"

The dates also interact with Contoso's S/4HANA program. BWP extracts from CMP using classic extractors such as 2LIS_13_VDITM (billing items) and 0FI_GL_14 (general ledger line items). Not every ECC extractor is supported in SAP S/4HANA; SAP documents this in the simplification item for BW extractors (SAP Note 2500202). Contoso checked its extractors during the conversion; any BW path must keep that list current, because the alternative to an unsupported extractor is often an SAP-managed data product or a CDS-based extraction.

Contoso’s BW today

BWP is not just reports. It holds Contoso’s monthly snapshots of inventory and open orders, history from the ECC years that no longer exists in CMP’s operational tables, and finance logic in transformations that the controllers rely on without knowing it is there. It also has people: two BW developers on Kenji’s team, Sam’s Basis team running it on premise, and roughly 300 users of Analysis for Office workbooks. Any path changes what those people do. A lift moves operations to SAP; a rebuild moves development to Datasphere skills; a retirement moves users to SAC or embedded analytics. Noor’s paper prices those changes alongside the licenses.

Noor also writes down what would change the recommendation. If SAP extends BW 7.5 support in the private cloud edition, the lift buys more time. If SAP-managed data products for Contoso’s finance and sales content become available earlier than expected, the rebuild gets cheaper. If the Monterrey company code 1910 needs BW reporting during Wave 2, scope grows. Listing these triggers in the paper lets the steering group revisit the decision on facts rather than on the next vendor presentation, and keeps the dates in the paper honest: each one carries the date it was last checked.