Begin of 2018 we have changed the license metric of SAP Application Interface Framework (AIF) from a named user based to a transaction based pricing model. I think that transaction based metric pretty much makes sense because it best reflects the value of the solution to our customers. The more messages monitored and processed through SAP AIF, the more valuable the solution for our customers.
Since then I have received many questions from customers and partners about the new license model. Also the fact that SAP AIF has become an integral part of the SAP S/4HANA technology both for on-premise and for cloud, led to some uncertainties around licensing.
So, let's try to shed some light into the license topic hopefully addressing most of your questions asked.
The metric is Transactions. The number of transactions is counted per year.
A transaction corresponds to a message that is processed or monitored in SAP AIF.
In principle, a transaction corresponds to a single entry that is displayed in the SAP AIF monitor.
Technically speaking, the audit report counts all entries within all single index tables of SAP AIF. Note that for each interface a single index table exists, and each AIF message is recorded in the same.
Examples
SAP AIF is sold in blocks of one million transactions. There are three tiers defined whereas price per block goes down the higher the yearly transactional volume. The license material number for all tiers is 7020287.
In addition, as of March 2nd 2020, AIF is also available as SAP S/4HANA Cloud for Application Interface Framework, extended edition (fka Single Tenant Edition). This is a cloud offering for any medium and large customer covering the full scope of functionalities necessary to build a holistic system in the cloud with focus on S/4HANA innovation. The functionality is available in modular packages, which can be combined. Each package has a subscription price, which included licenses, enterprise support, infrastructure, and application management service. All packages follow the same commercial terms and have been created along the same commercialization model. It is licensed by the same transaction based metric and blocks of 1 Million transactions per year (license material ID 8008257).
For a concrete price tag per block and overall costs, please reach out to your account representative.
You need to determine the number of transactions per year based on business transactions from past years or expected volume in future. Either you know roughly the number of business documents that you exchange during a specific time frame such as number of orders in your system generated per year. Or you may look into the respective message monitors. This depends on the technology used.
Although the old SAP AIF material codes have been removed from the price list, existing customers can buy under the “more of the same” principle.
This however does not apply to customers that have converted to the SAP S/4HANA Enterprise Management license as the user based licensing is obsolete in this scenario. Here, you need to buy under the new transaction based model. Usually, a conversion credit for your past purchase can be issued. In this case, please reach out to your account representative.
SAP AIF as stand-alone product for developing, processing and monitoring your interfaces:
SAP AIF as integral part of SAP S/4HANA:

In SAP S/4HANA Public Cloud, customers cannot maintain or develop their own AIF interfaces. The applications within SAP S/4HANA Public Cloud ship pre-delivered AIF interfaces. In the Fiori launchpad, the AIF monitoring can be accessed via the message dashboard. Hence, the usage of SAP AIF in SAP S/4HANA Public Cloud is included in the SAP S/4HANA Public Cloud product license.
On an SAP S/4HANA system, we have transactions going through AIF from applications where SAP ships AIF interfaces such as Central Finance for instance which is included in the respective product license and we have additional transactions going through AIF from AIF interfaces that customers have maintained on their own. The challenge is how are the volumes separated with respect to license auditing? All AIF interfaces that SAP ships are actually shipped within namespaces starting with a /. If you create your own custom AIF interfaces, you can only do so within your own custom namespace, / is not allowed here. So, it's simple, the audit report only counts the number of transactions within custom namespaces, i.e., those not starting with a /.
I would also like to point you to the SAP note 2293938 - License Check for SAP Application Interface Framework. This note explains very well the licensing for the different usage of SAP AIF.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 72 | |
| 59 | |
| 52 | |
| 34 | |
| 34 | |
| 32 | |
| 31 | |
| 28 | |
| 28 | |
| 25 |