Key Takeaways
- The average enterprise consumes only 55–65% of contracted BTP Integration Suite IU allocations — but still pays overages on specific sub-metrics like API call volumes.
- iFlow polling frequency is the single largest avoidable consumption driver in most enterprise landscapes.
- A structured iFlow inventory and API call audit typically reduces consumption by 20–35% without any loss of integration functionality.
- Dormant and retired integrations account for 10–20% of active IU consumption in mature SAP landscapes.
- Consumption optimisation evidence strengthens your negotiating position at renewal — lower documented consumption = legitimate grounds for a reduced commitment level.
⚠️ Independent SAP licensing advisory — not affiliated with SAP SE. SAP BTP, Integration Suite, and all SAP product names are trademarks of SAP SE.
Why SAP BTP Integration Suite Consumption Optimisation Matters
The consumption-based pricing model for SAP BTP Integration Suite sounds straightforward: pay for what you use, buy more when you need it. In practice, the model works differently. You commit to an annual minimum, pay overages above the contracted level, and lose any under-consumed capacity at year-end without credit or rollover.
This structure creates a specific problem for enterprise buyers: consumption is often asymmetric. You may have significant unused IU headroom in your overall allocation, yet still trigger overage charges on API Management call volumes or specific Cloud Integration flow execution metrics. Understanding which metrics you are under-consuming and which are generating overages is the starting point for any SAP licence optimisation exercise on a BTP Integration Suite contract.
In our experience reviewing enterprise BTP portfolios, a structured consumption review typically identifies 20–35% in addressable over-spend before any contract renegotiation. That reduction comes from technical optimisation — not from reducing integration capability. The detailed SAP BTP Integration Suite licensing guide explains how the IU model works; this article focuses on what to do about it.
Step 1: Build a Complete iFlow Inventory
The first step in any BTP Integration Suite optimisation project is building a complete inventory of deployed iFlows (integration flows). This sounds basic, but most enterprises do not have an accurate, current picture of their iFlow landscape. Integration flows get deployed for specific projects, and they run indefinitely even when the project ends, the system is retired, or the business process changes.
Export iFlow inventory from SAP BTP Cockpit
Use the Integration Suite monitoring dashboard to export a list of all deployed iFlows, including last execution timestamp, execution frequency, and current status (started, stopped, error). This export gives you the baseline for the optimisation analysis.
Classify by operational status
For each iFlow, determine whether it is: (a) actively used in production business processes, (b) deployed but unused (no executions in the last 90 days), (c) running in error state without business impact, or (d) supporting a retired system or concluded project. Category (b), (c), and (d) iFlows are candidates for decommissioning.
Map iFlow owners
Identify the business owner and technical owner for each active iFlow. Orphaned iFlows — those where no current team member can identify the owning business process — are high-priority decommissioning candidates. In complex enterprises, 20–30% of iFlows are effectively orphaned within 24 months of deployment.
Step 2: Audit iFlow Execution Frequency
Polling frequency is the primary controllable driver of BTP Integration Suite IU consumption. Many enterprise integrations were configured with polling intervals set during initial development — intervals that were conservative or experimental, and never revisited once the integration went live. A polling interval of every 30 seconds for an order status check that runs overnight will consume dramatically more IUs than a 5-minute interval for the same integration.
For each active production iFlow, review the execution frequency against the actual business requirement. The question to answer is: how frequently does this integration need to run to meet its SLA? In most cases, the answer is materially less frequently than the current configuration. Common optimisations include extending polling intervals for batch integrations, converting unnecessary polling to event-driven triggers where the source system supports webhooks or SAP Event Mesh, and consolidating multiple low-volume flows into a single scheduled batch flow.
Event-driven integration — where integration flows are triggered by an event rather than by a scheduled poll — is significantly more IU-efficient. For organisations on RISE with SAP or with SAP Event Mesh entitlements, converting key polling integrations to event-driven architecture reduces IU consumption substantially. This is both a technical optimisation and a licensing optimisation: our RISE with SAP advisory team frequently identifies this as a quick win for clients managing BTP consumption costs.
Not sure where your IU consumption is going?
Our SAP licence optimisation team performs forensic BTP consumption reviews — identifying the specific iFlows, API call patterns, and service plan mismatches that are driving your bill. Book a free consultation to understand your options.
Step 3: Analyse API Management Call Volumes
API Management within SAP BTP Integration Suite is licensed on API call volumes. This metric behaves differently from iFlow IU consumption — it can scale rapidly with external adoption of APIs, and overages can accumulate quickly if not monitored. The optimisation approach is different from iFlow tuning.
Start by pulling the API call volume report from Integration Suite's API Management console for the last 12 months. Identify the top 10 APIs by call volume and the top 10 calling applications. In most enterprise deployments, a small number of APIs account for the majority of call volume, and a small number of callers — often internal systems or batch jobs — account for the bulk of those calls.
Common sources of inflated API call volumes include internal systems polling SAP APIs for status updates that could be event-triggered, development and test environments making calls against production API endpoints (a compliance and cost issue), automated monitoring or health-check tools generating calls against production APIs, and third-party integration partners exceeding their agreed call quotas. Each of these can be addressed without reducing the business value of the API.
Step 4: Decommission Dormant and Retired Integrations
Every integration flow that is deployed and started in SAP BTP Integration Suite consumes resources — even if it never executes, even if it executes infrequently, and even if the system it integrates with no longer exists. Decommissioning unused integrations is the fastest way to reduce IU consumption without any business impact.
In enterprise landscapes, dormant integrations accumulate over time. S/4HANA migrations, system consolidations, and project completions leave behind integration flows that were never formally decommissioned. An audit of execution timestamps typically identifies a significant population of flows that have not executed in six months or more. These should be reviewed for decommissioning — the review is the only step that requires business stakeholder input.
When decommissioning, export and archive the iFlow design before deletion. This preserves the intellectual property in case the integration is needed in future, and satisfies the documentation requirements of change management processes. Archiving and decommissioning are separate steps — archive first, then decommission.
Step 5: Review Service Plan Assignments
SAP BTP Integration Suite capabilities are exposed through multiple service plans in the BTP Cockpit. Mismatches between service plan assignments and actual requirements are a frequently overlooked source of unnecessary cost. Specifically:
- Enterprise Edition capabilities on non-Enterprise instances: If your contract is Standard Edition, but your BTP Cockpit shows Enterprise Edition service plan assignments, you may have an unlicensed usage issue — or a billing discrepancy that deserves investigation.
- Non-production loads on production service plans: Development and test integration flows running on production service plans consume production IU allocations. Dedicated development subaccounts with their own service plan assignments (on lower-tier plans) prevent this leakage.
- Unused capability add-ons: If you purchased Integration Advisor or Open Connectors as add-ons but have no active users of those capabilities, those licences are wasted spend. Remove them from your next renewal unless you have a specific deployment timeline.
Using Consumption Evidence at Renewal
The output of a structured consumption review is not just cost reduction — it is negotiating evidence. When you approach your SAP BTP Integration Suite renewal with documented consumption data showing under-utilisation of your contracted IU allocation, you have a legitimate basis to request a reduced commitment level at renewal.
SAP's account team will resist reducing commitment. Their standard response is to project growth — "you'll need this headroom as your integration landscape expands." Push back on projections with historical data. If your consumption over the last three contract years has remained stable, growth projections are speculative. Demand that any over-commitment be justified with documented integration projects in the near-term pipeline.
Consumption-evidenced right-sizing, combined with timing the renewal to SAP's fiscal calendar and benchmarking against market prices, delivers the most significant reductions. Our detailed guide on SAP BTP Integration Suite negotiation tactics covers the commercial side in depth. Our SAP contract negotiation service applies both optimisation evidence and commercial expertise to deliver results enterprises cannot achieve without independent support.
Approaching a BTP Integration Suite renewal?
Our independent SAP contract negotiation team has achieved 35–55% reductions on BTP Integration Suite contracts — using consumption evidence, market benchmarks, and commercial leverage that enterprises rarely apply on their own. Start with a free consultation.
Tools and Data Sources for BTP Consumption Monitoring
Effective consumption management requires ongoing visibility, not just annual point-in-time reviews. The key data sources available to enterprise BTP buyers are:
- SAP BTP Cockpit: The primary management console for BTP services, subaccounts, and service instances. Provides IU consumption dashboards and service plan assignments at the subaccount level.
- Integration Suite Monitoring Dashboard: Within Integration Suite, the monitoring dashboard provides iFlow execution statistics, message processing logs, and API call volume reports. This is where the operational optimisation data lives.
- SAP for Me: SAP's customer portal increasingly surfaces BTP consumption analytics at the contract level. Monitor this for early warning of approaching overage thresholds.
- SAP BTP Usage Reports API: For organisations with mature FinOps practices, the BTP Usage Reports API allows programmatic extraction of consumption data into internal reporting systems. This enables daily monitoring and automated alerting on consumption trends.
Frequently Asked Questions
How do I see my current BTP Integration Suite IU consumption?
Integration Unit consumption is visible in the SAP BTP Cockpit under your global account's usage overview, and in more detail within Integration Suite's own monitoring section. SAP for Me also provides contract-level consumption summaries. For granular per-iFlow consumption data, the Integration Suite monitoring dashboard provides message processing statistics that can be used to estimate IU burn by flow.
What is a typical iFlow polling interval, and what should it be?
Default polling intervals in SAP BTP Integration Suite are often set at 1–5 minutes for timer-based flows. For batch integration use cases — overnight financial postings, daily master data syncs, weekly reports — intervals of 15–60 minutes or even scheduled batch runs (daily/weekly) are operationally equivalent. Reducing polling frequency on batch flows from every minute to every 15 minutes reduces execution count — and associated IU consumption — by 93% with no business impact.
Can I move integration flows between subaccounts to optimise licensing?
Yes, in many cases. SAP BTP supports multiple subaccounts within a global account, each with its own service plan assignments. Development and test integration flows should run in development subaccounts with lower-tier (or free tier) service plans, not in production subaccounts. Migrating non-production flows to the appropriate subaccount reduces production IU consumption without any functional change. This requires coordination with your BTP platform admin and a review of your contract's multi-environment provisions.
Will reducing my IU consumption trigger a pricing review from SAP?
SAP monitors consumption through SAP for Me and will use under-consumption as evidence that your renewal should reflect a lower commitment. This is not a threat — it is leverage. Enter the renewal conversation armed with your own consumption analysis, not SAP's interpretation of it. An independent review before renewal ensures you have the full picture, including any consumption drivers that are addressable, before SAP presents its version of your usage profile.
📬 SAP BTP Licensing Intelligence
Independent SAP BTP Insights — Free
Expert analysis on BTP consumption optimisation, contract strategy, and cost reduction. No vendor affiliation.