SAP releases preliminary Indirect Access detection tool for customers

SAP releases preliminary Indirect Access detection tool for customers

  • Homepage
  • Posts
  • SAP releases preliminary Indirect Access detection tool for customers

SAP officially released its stand-alone tool for customers to estimate their annual consumption of business documents created via non-SAP applications on July 31st, 2018.

The long-awaited tool was released as a consequence to SAP’s April 2018 Indirect/Digital Access pricing update, which revolves around 9 types of business documents. The tool can be downloaded from the SAP marketplace as Note 2644139 (for ECC) and Note 2644172 (for S/4HANA)

Our SAP License Advisory group has been analyzing the note since its release, and we believe the following information is critical for you:

  1. In a previous blog post we explained SAP’s intent to charge for business documents created within the digital core (ECC/S4) stemming from 3rd party (non-SAP) systems, and that these fees will be based on the level of individual line-items. That is to say, one Sales Order including ten line items, would result in 10 documents at a starting price of 0,50 EUR per document. The attached sample output from SAP’s tool confirms the line-item approach. Our advice is to consider all present and future use cases for these 9 types of business documents, and realize that counting at the line-item level can produce drastically higher consumption levels than you may have previously expected.
  2. SAP is planning to add automatic discovery for Indirect Access to its regular USMM/SLAW audit process by the end of 2018. In other words, if you choose to wait until your 2019 annual self-measurement – SAP will force you to discuss your Indirect Access document consumption on the basis of their audit results. The current version of SAP’s preliminary tool still has the following limitations:SAP tool
  • SAP cannot distinguish between business documents created by non-SAP applications and licensed SAP applications, which means you have to manually specify technical users that are used to connect a non-SAP application to your SAP systems. For organizations with hundreds of technical users who are unsure of their interface landscape, the tool won’t produce helpful results.
  • SAP previously stated, that all productive processes including EDI are required to be licensed under its updated Indirect Access policy. The current iteration of SAP’s tool only focuses on technical users that you manually specify, and may drastically understate the actual, total volume of annual documents that require licensing as per the policy definition.
  • The tool cannot do a reconciliation for documents created by users behind external applications, who are otherwise licensed SAP named-users. This will be critical in order to avoid that SAP customers pay double for indirect access to SAP by already licensed users.
  • SAP stated previously, that additional processing as part of a workflow that was started by the creation of an initial business document will be free of charge. In other words, if the indirect creation of a Sales Order triggers the creation of additional documents such as Financial or Invoice documents (you can imagine your own scenarios here) – only the creation of the initial Sales Order (counted at the level of line-items) will incur a charge. All additional documents created to complete the process will be free of charge. The problem is that SAP’s current version of the tool doesn’t have a processing logic that factors process completion into its document count.

While it may seem premature to criticize SAP’s Indirect Access detection tool in its current iteration, the omission of critical logic for process, interface, and user reconciliation begs the question whether SAP intends to enable an accurate detection of Indirect Access documents that will be transparent for customers. If you are adopting SAP’s new document-based licensing policy, you’ll want to get in writing that no new document types can be added to your contract in the future – and what audit and detection methodology shall be followed by SAP to count your annual consumption.

Our internal SAP License Advisory group assists customers to quantify their Indirect Access usage, and negotiate beneficial licensing constructs that benefit clients long-term by adding financial guardrails and securing maximum trade-in value. VOQUZ’s samQ License Optimizer for SAP Software is your foundation for an objective data extraction and automation of all licensing processes. It can help you optimize SAP licensing fees for a consumption-based licensing model, with plenty of room for future growth and innovation.



2 thoughts on “SAP releases preliminary Indirect Access detection tool for customers”

  1. Hi Alex,

    you hit the nail on the head — the issue with SAP’s estimation tool is that it’s hard to develop a broad picture view of your organizations reliance on 3rd party interfaces. While you can specify ranges of users with SAP’s tool, it’s always limited to the system you’re in and you’re not getting a breakdown of direct vs. indirect scenarios (you speak of human use vs. RPA or batch jobs I imagine), and so far the tool hasn’t been able to separate documents created between SAP systems (free of charge) from documents from 3rd party applications that legitimately fit the Indirect Access description.

    SAP’s tool only lets you run spot checks — but their upcoming USMM 2.0 audit tool will count all documents in all systems, which can create significant non-compliance if you don’t understand the mechanics behind the definition of Indirect Access, your current contract terms, and negotiation tactics you have as a customer.

    I encourage you to speak with our License Advisory team to address your questions and concerns in more detail.

    Kind regards

  2. Hi Sebastian, nice article. Thanks.

    I know that to run the tool you need to input the technical account name which is used by the indirect access. But there are practical issues if you have many indirect access accounts, or if you are planning to automate human entry by bots and want to measure all current direct use by human users. Do you know if it’s possible to enter multiple account names or even wildcards, like in the usual SAP ranges? And does the tool then give one total output?

    Kind regards,

Leave a Comment

Your email address will not be published. Required fields are marked *

Contact us

Send a message

Request a callback

Contact us