GROW with SAP and Indirect Access: How Third-Party Integrations Trigger Digital Access Charges in Public Cloud

The Misconception That Is Costing GROW Customers Money

When SAP introduced the Digital Access model in 2018, it replaced the old indirect access (named user) model for connected systems with a document-based charging framework. For legacy on-premise and RISE customers, this was well-documented and much discussed. For GROW customers, the implications have been less widely understood — partly because SAP's sales materials for GROW tend to focus on the simplicity of the subscription model and downplay the complexity of integration licensing.

The reality is that GROW with SAP uses the same Digital Access licensing framework as other SAP products. If a third-party system — a CRM, a WMS, an e-commerce platform, a custom application — creates, updates, or triggers one of the nine Digital Access document types in GROW, that activity generates a document charge. Those charges are separate from your FUE-based subscription fee and can be substantial depending on your transaction volumes.

Our indirect access advisory team has seen GROW customers discover significant unexpected Digital Access exposure after go-live, when their integration architecture was already fixed and the contractual window to address the issue had passed.

The Nine Digital Access Document Types

SAP Digital Access licensing covers nine specific document types. Any of these documents created or triggered by a non-SAP system connecting to GROW may generate a document charge:

How Third-Party Integrations Trigger GROW Digital Access Charges

E-Commerce Platforms

Organisations running Shopify, Magento, SAP Commerce Cloud, or other e-commerce platforms that write Sales Orders directly to GROW via API or middleware will trigger Digital Access charges per Sales Order document created. For high-volume retailers, this can represent tens of thousands of documents per month. The per-document rate under Digital Access and the total estimated volume must be calculated and budgeted before integration go-live.

Warehouse Management Systems

Third-party WMS platforms (Manhattan Associates, Blue Yonder, Infor WMS) that create or update Delivery documents or Material Documents in GROW generate Digital Access charges. Integrated WMS scenarios — which are extremely common in manufacturing, retail, and logistics — can generate hundreds of thousands of Material Documents annually.

EDI and Customer Order Integration

EDI-based customer order integration is one of the highest-volume Digital Access scenarios. If your EDI platform (SPS Commerce, TrueCommerce, Cleo) creates Sales Orders in GROW from customer EDI 850 messages, each order triggers a charge. Organisations processing thousands of EDI orders per day face significant Digital Access exposure that may not have been factored into the original GROW business case.

HR and Payroll Integrations

Payroll system integrations that post Journal Entries to GROW's financial modules can trigger Digital Access charges per posting document. Depending on payroll frequency and employee count, the volume can be material. Integration between third-party HR systems and GROW's FI module should be reviewed against the Digital Access document type list.

Custom Applications and Automation

Custom applications built on ABAP Cloud or BTP that interact with GROW core processes may or may not trigger Digital Access depending on how they are architected. BTP-based extensions using SAP's clean core APIs are generally not subject to additional Digital Access charges — but custom integrations that bypass the standard API layer and write directly to GROW data objects may be treated differently. Architecture decisions made during implementation have long-term commercial consequences.

How to Protect Your GROW Contract Against Digital Access Overexposure

The most effective time to address Digital Access risk in GROW is before signature and before integration architecture is finalised. The following measures significantly reduce exposure:

1. Conduct a Pre-Contract Digital Access Assessment

Before signing GROW, map every planned third-party integration against the nine Digital Access document types. For each integration, estimate the annual document volume. This assessment provides the commercial basis for negotiating a Digital Access allowance into your GROW contract or for identifying integration architectures that avoid triggering charges.

2. Negotiate a Digital Access Allocation in Your Contract

Many GROW contracts can be structured to include a Digital Access document allocation — a defined number of documents per year that are covered within the subscription fee. This allocation, and its renewal escalation terms, must be in the Order Form to be enforceable. SAP will not offer this proactively; it must be explicitly requested and negotiated.

3. Design Integrations to Use SAP-Standard APIs

Where possible, design third-party integrations to use SAP's standard cloud APIs and BTP integration services. SAP-standard API access in GROW's public cloud environment is generally included within the subscription and does not trigger additional Digital Access charges in the same way as deep system-to-system integrations. Engage your SAP technical architect and independent licensing advisor before finalising your integration design.

Related Guides

• SAP Indirect Access Explained: The Complete Enterprise Guide
• SAP Digital Access Licensing: The Complete Guide to Document-Based Charges
• SAP Digital Access Document Types: Which Trigger Charges and How to Control Them
• GROW with SAP Negotiation Tactics 2026
• SAP Digital Access Measurement: Why SAP's Own Tools Overcount
• Our SAP Indirect Access Advisory Service