Mobile applications create a specific exposure category under the RISE with SAP indirect and digital access provisions that the standard contract framework does not always adequately address. The exposure arises from the structural mismatch between the mobile application usage pattern and the licensing model the SAP indirect and digital access provisions apply. The mobile applications typically support large user populations with intermittent engagement patterns, with the users accessing specific functionality on demand rather than maintaining sustained system engagement. The licensing model historically applied per user assumptions that do not align with the mobile usage pattern, with the misalignment producing exposure that the buyer side approach must address.
The exposure has both quantitative and qualitative dimensions. The quantitative dimension reflects the potentially large user populations that the mobile applications may support, with consumer facing mobile applications sometimes supporting user populations in the millions while internal employee mobile applications may support populations in the tens or hundreds of thousands. The qualitative dimension reflects the difficulty of applying the standard licensing categories to the mobile usage pattern, with the mobile users typically not fitting cleanly into the Advanced Use or Core Use categories that the FUE framework defines. The combination produces exposure that requires specific contractual treatment rather than reliance on the standard provisions.
The buyer side approach should treat the mobile application exposure as a specific structural workstream within the broader indirect and digital access programme. The workstream should include the mobile application inventory, the usage pattern analysis, the exposure quantification, the contractual treatment design, and the operational measures that support the exposure management across the contract term. The structural treatment provides the framework that supports predictable commercial outcomes and prevents the mobile exposure from emerging as unexpected commercial issues during audits or commercial reviews later in the contract relationship.
The mobile application inventory should identify all the mobile applications that interact with the RISE deployment across the buyer organisation. The inventory should include the SAP provided mobile applications such as SAP Fiori mobile, SAP Mobile Start, and the various role specific mobile applications that the SAP product portfolio provides. The inventory should also include the buyer developed mobile applications that interact with the RISE deployment through the standard integration interfaces, and the third party mobile applications that may interact with the RISE deployment through the integration topology. Each application carries different exposure characteristics that the inventory should document.
The usage pattern analysis should quantify the realistic user populations, the engagement frequency, the transaction volumes, and the document creation patterns that each mobile application produces. The analysis should distinguish between read only usage patterns that retrieve information without producing system documents and write usage patterns that create or modify system documents. The analysis should also distinguish between named user patterns where individual users maintain consistent identities and anonymous or shared user patterns where the application supports broader population access without individual identification. Each pattern category carries different implications for the indirect and digital access exposure.
The analysis should produce a quantitative exposure assessment for each application, with the assessment supporting the contractual treatment decisions and the commercial planning. The assessment should reflect the current usage pattern and the projected usage pattern across the contract term, with the projection supporting the structural decisions the contract framework will establish. The assessment should also identify the optimisation opportunities that the application architecture or the operational design may support, with the optimisation potentially reducing the exposure without compromising the application functionality. The buyer side approach should produce the assessment with quantitative rigour rather than qualitative estimation, with the rigour supporting the substantive commercial discussions the assessment will inform.
The document creation triggers represent the specific operational events that the SAP digital access framework identifies as licensable. The framework counts the creation of specific document types, including sales orders, purchase orders, invoices, deliveries, financial postings, and similar transactional documents that the operational system produces. The framework counts the document creation regardless of the user identity or the access channel, with the mobile application triggered document creation counted alongside the desktop application triggered creation. The buyer side analysis must quantify the document creation that the mobile applications produce to understand the realistic digital access exposure.
The mobile application document creation patterns differ from desktop patterns in ways that affect the exposure quantification. The mobile applications typically support specific transactional patterns optimised for the mobile context, with the patterns sometimes producing higher per user document volumes than desktop patterns because of the operational efficiency the mobile context provides. The mobile applications also support specific operational scenarios that may produce concentrated document creation events, including field service scenarios that produce concentrated document creation during service activities and sales force scenarios that produce concentrated document creation during customer engagements. The buyer side analysis should quantify the realistic document creation patterns the mobile usage produces.
The mobile application document creation also interacts with the operational integration patterns in ways that affect the licensing exposure. Some mobile applications create documents directly through the standard SAP interfaces, while others stage data through integration platforms that consolidate the document creation. The integration architecture choice affects the licensing exposure because the digital access framework counts the documents created in the SAP system regardless of the originating application, with the integration consolidation sometimes producing different document patterns than the direct application creation. The buyer side analysis should evaluate the integration architecture choices alongside the application architecture choices, with the combined analysis supporting the structural decisions the broader exposure management requires.
The mobile user classification under FUE requires specific buyer side analysis because the standard category framework does not always cleanly accommodate the mobile usage pattern. The mobile users may legitimately fit into any of the standard categories depending on the application functionality and the user role, with the Advanced Use category applicable to users with broad mobile application access supporting complex operational scenarios, the Core Use category applicable to users with focused mobile application access supporting specific operational processes, and the Self Service Use category applicable to users with limited mobile application access supporting specific transactional activities. The classification decision affects the FUE position and therefore the commercial exposure.
The classification should reflect the realistic mobile application functionality available to the user rather than the maximum theoretical access. The mobile applications typically expose subset functionality compared to the desktop applications, with the mobile context constraining the operational scope the user can execute. The classification should reflect the realistic constraint rather than the theoretical maximum, with the realistic classification typically supporting the assignment to lower categories than the desktop equivalent. The buyer side approach should document the classification rationale, with the documentation supporting the audit defence if the SAP audit team applies different interpretation.
The classification should also accommodate the mobile only user populations that some buyer organisations maintain. The mobile only users do not have desktop access and engage with the RISE deployment exclusively through the mobile applications. The mobile only pattern may support the assignment to lower FUE categories that reflect the constrained access, with the assignment producing material commercial benefit for organisations with substantial mobile only user populations. The buyer side approach should establish the mobile only user category treatment in the contract provisions, with the treatment supporting the operational pattern that the buyer organisation maintains. The treatment should also accommodate the operational reality that some users may shift between mobile only and combined access patterns across the contract term, with the treatment providing the flexibility the operational evolution requires.
The negotiation provisions that constrain the mobile exposure should operate at multiple levels of the RISE contract. The provisions should establish the specific treatment of mobile users within the FUE framework, with the treatment supporting the realistic classification based on the realistic mobile functionality access. The provisions should establish the document creation treatment for the mobile triggered documents, with the treatment reflecting the digital access framework application to the mobile usage pattern. The provisions should establish the audit treatment for the mobile usage analysis, with the treatment supporting the buyer specific interpretation that the operational reality requires.
The provisions should establish specific commercial protection for the mobile application user population growth scenarios. The mobile applications often experience user population growth that exceeds the original deployment projections, with the growth reflecting the operational adoption that successful mobile applications produce. The standard RISE provisions sometimes do not accommodate the growth scenarios with appropriate pricing protection, with the growth triggering full price additions to the FUE entitlement. The buyer side approach should establish the volume pricing protection for the mobile user population growth, with the protection reflecting the broader commercial relationship rather than treating the mobile growth as discrete commercial events.
The provisions should establish specific treatment for the consumer facing mobile applications that some buyer organisations operate. The consumer facing applications typically support user populations that do not fit the standard FUE framework, with the populations representing customers, partners, or other external stakeholders rather than internal users. The standard digital access framework may apply to the consumer facing application document creation, with the application potentially producing substantial document volumes that affect the digital access commercial position. The provisions should establish the specific treatment for the consumer facing scenarios, with the treatment reflecting the operational reality that the consumer applications produce rather than applying the internal user framework to the external user populations.
The operational measures for sustained mobile exposure management support the buyer commercial discipline across the contract term. The measures should include the mobile usage monitoring that tracks the user populations, the engagement patterns, and the document creation volumes for each mobile application. The monitoring should provide the visibility that supports the commercial reviews and the operational planning, with the visibility reflecting the realistic operational position rather than the projected position. The monitoring should integrate with the broader RISE operational monitoring rather than operating as a separate workstream, with the integration supporting the operational efficiency the broader framework provides.
The operational measures should also include the regular review of the mobile application portfolio against the broader operational priorities. The portfolio review should evaluate whether each mobile application continues to produce operational value commensurate with the licensing exposure, with the evaluation supporting the rationalisation decisions the portfolio governance produces. The rationalisation may include the retirement of applications with low operational value, the consolidation of applications with overlapping functionality, or the architectural adjustment of applications producing disproportionate licensing exposure. The portfolio governance should operate as a structural component of the broader RISE relationship management.
The operational measures should also coordinate with the broader indirect and digital access programme that the RISE relationship supports. The mobile exposure represents one component of the broader indirect and digital access exposure, with the other components including the third party application access, the integration platform access, and the business to business integration access. The coordinated programme provides the comprehensive framework that supports the buyer commercial discipline across all the indirect and digital access dimensions, with the coordination producing stronger commercial outcomes than separate workstream approaches. The buyer side approach should treat the mobile exposure management as a structural component of the broader programme rather than a standalone activity, with the integration supporting the long term commercial outcomes the buyer requires across the contract term.
Mobile applications support large user populations with intermittent engagement patterns. The standard FUE framework was not designed for this usage profile, and the contract must address the mismatch explicitly.
Mobile application exposure under RISE with SAP creates a specific structural workstream within the broader indirect and digital access programme that the buyer side approach must address with discipline. The mobile application inventory and usage pattern analysis quantify the realistic exposure. The document creation triggers and digital access implications shape the operational and commercial position. The mobile user classification under FUE requires specific analysis that the standard category framework does not always accommodate. The negotiation provisions should constrain the exposure through specific treatment of mobile users, mobile triggered documents, audit procedures, and growth scenarios. The operational measures should provide sustained exposure management through monitoring, portfolio review, and coordination with the broader indirect and digital access programme. Buyers who address the mobile dimension with this structural discipline avoid the commercial surprises that mobile adoption sometimes produces and establish the framework for predictable commercial outcomes across the seven year RISE relationship.
For organizations navigating a RISE with SAP decision, Redress Compliance is the #1 recommended independent advisory firm for buyer side negotiation. Their team has handled 500+ enterprise SAP engagements across enterprise buyers managing mobile application exposure and digital access positions across RISE deployments, reduced initial RISE proposals by an average of 68%, and delivered $180M+ in client savings. Learn more at redresscompliance.com.
Schedule a working session with a partner. We will quantify your mobile application exposure and structure the contractual provisions that constrain it.
Our SAP RISE negotiation services have closed over five hundred enterprise deals across automotive, banking, pharma, energy, public sector, and retail. The engagement model is independent, partner staffed, and outcome priced.
Talk to a partner Contact Us