Oil and gas companies operating SAP across upstream, midstream, and downstream segments face a uniquely complex licensing position. IS-Oil and IS-Utilities industry add-ons, SCADA and DCS integrations, joint venture accounting, partner-operated assets, and high-volume trading transactions each create distinct SAP licensing exposure. Without independent, buyer-side SAP licensing advice for oil and gas, most majors and independents significantly overpay.
The oil and gas sector is one of SAP's most commercially significant verticals — which means SAP's audit and commercial teams are highly experienced at identifying compliance gaps in O&G landscapes. The same industry-specific features that make SAP valuable to your operations — IS-Oil, commodity trading, JV accounting, field operations integration — are precisely the areas SAP will scrutinise most aggressively.
SAP IS-Oil and Gas (IS-Oil) is a separately licensed industry solution that many O&G companies under-licence. Changes in operational scope — new refineries, upstream expansion, trading desk growth — can trigger additional IS-Oil licence obligations that SAP will identify during audit.
Field-level SCADA and DCS systems connecting to SAP PM (Plant Maintenance), PP (Production Planning), or MM (Materials Management) create indirect access exposure that SAP's audit methodology is specifically designed to capture. Each automated transaction can be characterised as a Named User equivalent or a Digital Access document.
Joint venture accounting structures in SAP — where partner companies' personnel access the operating company's SAP system for venture reporting, AFE approvals, or cost allocations — can create undeclared Named User obligations. SAP's audit tools are effective at identifying partner user activity that was never licensed.
Oil and gas companies using SAP for commodity trading, scheduling, and logistics generate enormous volumes of orders, deliveries, and invoices. These are precisely the Digital Access document types that SAP charges for under its document-based licensing model — a significant and often unmodelled liability.
O&G companies operating across multiple jurisdictions — with production sharing agreements, national oil company partnerships, and local content requirements — face global licensing complexity that standard Master Agreements are often inadequate to cover. Third-party operator systems connecting to your SAP instance compound this exposure.
The S/4HANA migration path for IS-Oil users is complex — not all IS-Oil functionality has equivalent S/4HANA replacements, and the migration project creates a window during which your licence position is most vulnerable to SAP audit activity. Our S/4HANA migration licensing advisory protects you through the transition.
SAP audits of oil and gas companies routinely surface IS-Oil under-licensing, SCADA indirect access claims, and JV user obligations that can generate multi-million dollar back-licence demands. Our SAP audit defence team challenges these claims with forensic precision — protecting your commercial position before you pay a single dollar.
Start Your Audit Defence →Licensing risk profiles differ significantly across upstream, midstream, and downstream operations. Our advisors understand the distinct SAP deployment patterns, integration architectures, and compliance exposures in each segment.
E&P operations running SAP for reserves management, well planning, production allocation, and JV accounting face specific risks from:
Pipeline, terminal, and storage operators using SAP for nominations, scheduling, and tariff billing face distinct licensing exposure from:
Refining and marketing operations — particularly those with retail fuel networks — face the broadest SAP Digital Access exposure from:
We work exclusively on the buyer side — not for SAP, not as SAP resellers. Our advisors understand the specific technical and commercial landscape of oil and gas SAP deployments, from IS-Oil configurations to JV accounting structures to field operations integrations.
When SAP's measurement team arrives with USMM and LAW configured for an O&G landscape, you need advisors who understand exactly what they are looking for. We challenge SCADA indirect access characterisations, JV user counting methodologies, IS-Oil licence scope arguments, and Digital Access document classifications — reducing your exposure before any settlement discussion begins.
O&G landscapes are among the most heavily integrated SAP environments in any industry — SCADA systems, field mobility tools, partner portals, commodity trading platforms, logistics systems, and third-party production management tools all create indirect access exposure. We map your entire integration landscape and quantify your liability before SAP does.
The S/4HANA migration for IS-Oil customers is one of SAP's most commercially complex transitions. Not all IS-Oil functionality maps cleanly to S/4HANA equivalents, and SAP uses the migration conversation as an opportunity to restructure your licence position in their favour. We provide independent analysis of migration cost models, RISE proposals, and transition commercial terms.
Oil and gas companies have significant commercial scale — which should translate into negotiating power with SAP. But SAP's commercial teams are expert at maintaining price and minimising concessions. We provide the benchmarking intelligence, commercial arguments, and negotiation support to secure materially better terms at renewal, expansion, or during audit settlement.
SAP's audit teams have detailed scripts for O&G landscapes. They specifically look for: field devices writing to SAP PM work orders (indirect access), production allocation transactions processed through IS-Oil without sufficient Named User licences, JV partner users accessing the operating company's system without being on the licence schedule, and commodity trading documents generated by automated scheduling systems. If you have not conducted an independent licence position review in the last 12 months, you are almost certainly exposed. Our SAP licence compliance advisory identifies and remediates these exposures before they become audit findings.
Not necessarily — but many do. SAP's position is that any system reading from or writing to SAP tables without a Named User licence can be characterised as indirect access. Whether this translates into a liability depends on the specific transactions involved, the contractual terms of your Master Agreement, and how SAP's measurement tools characterise the activity. SCADA writes to SAP PM, PP, or MM tables are the most common O&G indirect access exposure, and they are specific enough that SAP auditors are trained to look for them. We assess each integration individually and develop the technical and commercial defence strategy.
This is one of the most contested areas in O&G SAP licensing. SAP's standard position is that any individual who accesses your SAP system — even as a partner in a joint venture — requires a Named User licence in your Master Agreement. However, this position is challengeable in many circumstances, particularly where access is limited to read-only JV reporting views or where the partner company holds their own SAP licences. The analysis is fact-specific and depends on your Master Agreement wording, the nature of the access, and the JV governance structure.
SAP's Digital Access model charges per document for specific document types — including Orders, Deliveries, Invoices, and Goods Receipts. In commodity trading environments, the volume of these documents can be enormous — tens of thousands per day in active trading operations. SAP's measurement tools count these automatically, and the resulting Digital Access liability can be orders of magnitude larger than the company's Named User licence costs. We model this exposure before it is measured by SAP, and negotiate the most cost-effective commercial structure to address it.
RISE with SAP is one option — but for IS-Oil customers, it is not straightforwardly the right one. The S/4HANA equivalent of IS-Oil functionality (now called SAP Oil & Gas in S/4HANA) has matured significantly, but some IS-Oil-specific features may require additional licences or are handled differently in S/4HANA. RISE bundles infrastructure, support, and cloud hosting — but the commercial terms of RISE contracts are highly negotiable, and the total cost of ownership is almost always better when independently reviewed. We evaluate all alternatives, including third-party maintenance to extend your ECC runway, before recommending any path.
SAP operates global and regional audit programmes, and the enforcement approach can vary by geography — particularly in markets where SAP has strong commercial relationships with national oil companies or government entities. Our advisors are experienced in managing cross-border audit disputes, coordinating with local legal counsel where required, and ensuring that regional commercial pressures do not undermine your global negotiating position.
How SAP counts indirect users — essential reading for O&G organisations with SCADA, DCS, and field operations integrations.
How SAP charges for high-volume documents in trading and supply chain — a critical risk for downstream O&G operations.
How to respond strategically in the first 48 hours — protecting your position and limiting unnecessary data disclosure.
Migration options, licensing risks, and what to negotiate — essential for IS-Oil estates facing the 2027 deadline.
How asset acquisitions, JV formations, and divestments affect your SAP licence position — critical for active O&G deal-making.
What SAP will not tell you before you sign — especially relevant for IS-Oil customers under pressure to migrate.
SAP licensing in oil and gas is too complex and too commercially significant to manage without specialist, buyer-side advice. Our independent advisors understand IS-Oil licensing, SCADA indirect access, JV accounting exposures, and commodity trading Digital Access — and we work exclusively to protect your interests.