Functional gaps in RISE versus brownfield.

The standard SAP framing of RISE with SAP is that the platform offers feature parity with brownfield, plus the additional capabilities of the cloud delivery model. The standard buyer experience in 2026 is that feature parity is not quite parity. There are functional gaps between RISE and brownfield, some of which matter to specific buyers and some of which do not. A buyer who signs a RISE contract without a documented understanding of the functional gaps will discover them in production, when remediation is expensive and slow. This article documents the functional gap categories in RISE versus brownfield, and the disciplined approach to identifying which gaps matter for a specific buyer.

Direct database access

The first functional gap is direct database access. Brownfield deployments allow direct database access for reporting, integration, and operational tooling. RISE deployments restrict direct database access to defined SAP managed interfaces. For buyers who have built operational tooling, reporting infrastructure, or integration patterns on direct database access, the RISE constraint requires rebuilding the tooling against the SAP managed interfaces.

The countermove is to inventory all direct database access patterns before the RISE decision and assess the rebuild cost. Some patterns are easy to migrate. Some require significant rebuild. The inventory is the input to the gap analysis, and the analysis tells the buyer whether direct database access is a blocking constraint or a manageable adjustment.

Custom basis administration

Brownfield deployments allow the buyer's basis team to administer the system directly, with full access to system configuration, transport management, performance tuning, and emergency operations. RISE deployments delegate basis administration to SAP, with the buyer's team operating at a higher abstraction level. For buyers with mature basis teams, the transition removes operational levers the team is accustomed to using.

The countermove is to map the buyer's basis operations and identify which operations the RISE model supports, which it restricts, and which it removes entirely. The map shows the buyer where the operating model will change and where the team's skills will need to evolve. Some basis teams welcome the change. Some find it constraining. The choice depends on the specific operations the team relies on.

Custom code object types

Brownfield supports the full range of ABAP object types and modification depths. RISE supports a defined subset, with restrictions on certain object types and on modifications that touch SAP standard objects. The custom code estate that runs on brownfield will not all run unchanged on RISE. Some objects require remediation. Some require rebuild. Some have no direct equivalent and require functional redesign.

The countermove is to scan the custom code estate against the RISE supported object list and produce a remediation map. The map identifies which objects can move unchanged, which require modification, which require rebuild, and which require functional redesign. The remediation map is then priced into the migration cost, and the gap becomes a cost line in the TCO.

Extension tooling

Brownfield extensions are built primarily in classic ABAP, sometimes with additional layers in middleware or external systems. RISE extensions are expected to be built in the SAP Business Technology Platform, using cloud appropriate patterns and the BTP development tooling. The development model is different, the deployment model is different, and the operational model is different.

The countermove is to assess the buyer's developer capability for the BTP model before committing to RISE. A team that is strong in classic ABAP and weak in cloud development patterns will need training and tooling investment to operate effectively in the RISE extension model. The investment is part of the gap cost.

Integration patterns

The integration patterns that work on brownfield are not all available on RISE. Direct file system integration is limited. Direct RFC calls require rework. Some middleware patterns require redesign. The buyer who is integrating with dozens of systems will find that the integration estate requires a meaningful percentage of rework, and the rework is not equivalent across patterns.

The countermove is to inventory the integration estate and classify each integration by the rework category it falls into. Direct support, with no change required. Modification, with defined work. Redesign, with significant work. Rebuild, with full reimplementation. The classification produces an integration cost line that is grounded in the actual estate, not in a heuristic.

Reporting and analytics tooling

Brownfield reporting often relies on direct database queries, custom report types, and analytical patterns that have been built up over years. RISE reporting relies on SAP managed analytical capabilities, including embedded analytics, the SAC integration, and the data services that the RISE bundle includes. The reporting estate that exists on brownfield is rarely all reproducible on RISE without rework.

The countermove is to inventory the reporting estate and assess each report against the RISE analytical model. Some reports map directly. Some require new tooling. Some require a fundamentally different analytical approach. The inventory produces a reporting transition cost that is part of the migration line in the TCO.

Conclusion

The functional gap between RISE and brownfield is real, but it is not uniform. Some buyers face a small gap that is easily managed. Some buyers face a large gap that materially changes the TCO. The discipline is to assess the gap honestly before the RISE decision, with a structured inventory of database access patterns, basis operations, custom code, extensions, integrations, and reporting. The assessment produces a gap cost that goes into the TCO, and the TCO then tells the buyer whether the RISE business case still stands. A buyer who skips the gap assessment will face the gaps in production, when the cost is higher and the leverage is lower. The investment in gap assessment before signature is the investment that protects the entire RISE business case.