SAP BEx (Business Explorer)

What it is

BEx — Business Explorer — is the classical front-end suite of SAP BW: the Query Designer where OLAP queries are defined, the Analyzer add-in that surfaces them in Excel, the Web Application Designer for browser output, the Report Designer for formatted output, and the Broadcaster for scheduled distribution. For two decades it was how BW data reached a business user.

The distinction that decides migration plans. The BEx client tools and the BEx query are not the same object, and SAP's retirement messaging concerns the tools. A BEx query is a query definition on an InfoProvider — restricted and calculated key figures, variables, exceptions, conditions, free characteristics — and that definition is consumed today by SAP Analysis for Microsoft Office, by SAP Analytics Cloud through live connections, and by BW/4HANA itself. Retiring the front-end does not retire the queries, and a plan built on the assumption that it does will propose rebuilding thousands of objects that do not need rebuilding.

What genuinely ends. The client tools, and with them the artefacts that only they produce: Web Application Designer templates, Report Designer layouts, Broadcaster distribution settings. These have successors of a different shape — SAC stories and applications, and SAC's own scheduling — rather than converters, and they carry real rebuild effort.

Where the queries themselves need work. BEx queries written against classical BW objects may need adjustment when the underlying provider changes during a BW/4HANA or Datasphere move, and some query features behave differently when consumed by SAC live connections than they did in the Analyzer. That is a targeted review of query features, not a wholesale rebuild — and the difference between those two framings is usually the difference between a viable programme and an abandoned one.

How to inventory. Count queries, then count the ones actually executed in the last quarter; separately count Web Application Designer templates, Report Designer layouts and Broadcaster settings. The first pair tells you what survives, the second group tells you what has to be rebuilt.

Why it matters

• The BEx tools end; the BEx query does not. A plan that misses the distinction proposes rebuilding thousands of query definitions that SAC and Analysis for Office consume as they are.

Key points

• The classical BW front-end suite: Query Designer, Analyzer, Web Application Designer, Report Designer, Broadcaster.
• 🔴 The retirement concerns the CLIENT TOOLS. The BEx query is a definition object on an InfoProvider and is consumed today by Analysis for Office and by SAC live connections.
• What genuinely ends: Web Application Designer templates, Report Designer layouts, Broadcaster distribution settings — rebuilt, not converted.
• Queries may need targeted review where the provider changes or where a feature behaves differently over a SAC live connection.
• Inventory in two parts: queries and their last-quarter execution, then the tool-specific artefacts.

Common pitfalls

• Reading the BEx sunset as a query sunset — Signal: "We must rebuild 3,000 BEx queries" Fix: The tools end, the query definitions do not. Separate the two before estimating.
• Forgetting the Broadcaster — Signal: A plan covering queries and reports but no distribution Fix: Broadcaster settings are distribution behaviour with business owners, and they have no converter.
• Sizing by total query count — Signal: A five-figure object count in the proposal Fix: Pull execution statistics. The live population is routinely a small fraction of what exists.

Decision framework

Sources

1. SAP Help — SAP BW/4HANA documentation
2. SAP Help — SAP Analysis for Microsoft Office
3. SAP Product Availability Matrix (maintenance horizons)
4. SAP Community — BEx and BW front-end boards