SAP's portfolio includes specialised industry solutions for manufacturing, utilities, retail, pharmaceuticals, oil & gas, and more. Each sector brings unique licensing mechanics combining named user licences with engine metrics tied to industry-specific volumes. This independent guide helps CIOs and licensing professionals navigate SAP's dual licensing model, avoid compliance pitfalls, and optimise costs across every industry vertical.
This guide is part of our SAP Licensing Knowledge Hub. For S/4HANA-specific guidance, see SAP S/4HANA Licensing: The Complete Guide.
SAP's software portfolio is not one-size-fits-all. It includes a range of industry-specific solutions tailored to sectors such as manufacturing, utilities, retail, pharmaceuticals, oil and gas, financial services, and many others. These specialised SAP modules address the unique business processes, regulatory requirements, and compliance needs of each sector.
With these powerful industry-focused tools comes the complexity of licensing them correctly. Licensing for industry solutions can differ significantly from standard SAP ERP licensing, often involving a combination of traditional named-user licences and package or engine licences based on industry-specific metrics such as production orders, meter points, barrels produced, or retail store counts.
| Licence Type | How It Works | Industry Relevance |
|---|---|---|
| Named User Licences | Tied to individuals. Every person accessing SAP requires an appropriate named user licence. Categories: Professional, Limited Professional, Employee Self-Service, Developer. | Required across all industries. User classification (plant manager vs shop-floor worker) determines licence tier and cost. |
| Package (Engine) Licences | Usage-based licences for specific SAP modules measured with industry-relevant metrics. Purchased in blocks or tiers alongside named users. | Oil & gas: barrels/wells. Retail: stores/POS transactions. Manufacturing: production orders. Utilities: contracts/meter points. |
Both are required simultaneously. Most industry solutions need sufficient named users for the people using the system plus an engine licence that covers the transactional volume. Missing either creates compliance exposure. The engine licence alone does not cover users, and named user licences alone do not cover engine-metric usage.
| Industry | Key SAP Solutions | Typical Engine Metrics | Key Licensing Considerations |
|---|---|---|---|
| Manufacturing | S/4HANA Manufacturing, SAP ME, SAP IBP | Production orders/year, units produced, number of plants | Indirect access via IIoT devices, MES systems, barcode scanners |
| Utilities | SAP IS-U, S/4HANA Utilities | Active customer contracts, meter points, billable consumption records | Engine metrics scale with operational size. Customer portals create indirect access risk. |
| Retail | S/4HANA Retail, SAP CAR | Retail locations, POS data volume, sales orders | E-commerce and POS integrations make Digital Access critical. |
| Pharmaceuticals | S/4HANA Life Sciences, SAP ATTP | Serial numbers managed, batch records, compliance transactions | Strict validation requirements. ATTP licensed by managed serial numbers. |
| Oil & Gas | SAP for Oil & Gas, Upstream/Downstream | Wells managed, barrels produced/refined, hydrocarbon accounting records | Multiple entities across exploration, production, refining each need licensing. |
| Financial Services | S/4HANA Finance, SAP Treasury & Risk | Transaction volumes, financial instruments managed | Package licences based on transaction volumes. Regulatory compliance critical. |
Manufacturing companies rely on SAP to manage production planning, scheduling, inventory management, plant maintenance, and quality management.
| Component | Licence Type | Detail |
|---|---|---|
| Production planners & managers | Professional User | Broad transaction access across modules. Full-feature licence required. |
| Shop-floor operators | Limited / Employee | Only confirm operations or enter time data. Lower-tier licence reduces cost. |
| Manufacturing engines | Package (Engine) | Metrics: production orders processed/year, units produced, or number of plants. |
| IIoT / MES integrations | Digital Access | Sensors creating maintenance orders or inventory movements = indirect usage. |
Manufacturing licensing example. A mid-sized manufacturer running SAP S/4HANA has 50 Professional user licences for engineers and managers, 200 Limited Worker licences for production staff, and a package licence allowing up to 100,000 production orders per year. They also use SAP IBP licensed for multiple forecasts and high data volumes. Regular internal checks ensure production order counts do not surpass entitlements.
Indirect access in manufacturing is a growing risk. Equipment-to-SAP integrations, IIoT devices, MES systems, barcode scanners, that create or read SAP data constitute indirect usage. Under SAP's rules, this must be licensed either through generic user licences for devices or, increasingly, by counting documents via the Digital Access model.
| Metric | What It Measures | Scaling Impact |
|---|---|---|
| Active customer contracts | Number of end-customer accounts managed in SAP | A water utility serving 500,000 households needs an engine for 500K contract accounts |
| Active meter points | Number of physical connection/metering points | Smart meter rollouts can dramatically increase meter point counts mid-contract |
| Billable consumption records | Volume of billing records processed per period | Aligns cost with utility throughput and seasonal peaks |
Customer portals create significant indirect access exposure. Utilities with self-service portals allowing customers to view bills, submit meter readings, or request service changes are triggering SAP transactions via non-SAP users. This is a prime Digital Access scenario. Utilities should evaluate whether the Digital Access document model or existing user licences cover this activity.
| Challenge | Licensing Implication |
|---|---|
| Large workforce | Hundreds or thousands of store staff, planners, and buyers. Many only need limited functionality. Careful tier classification saves significant cost. |
| Engine metrics | SAP CAR licensing can depend on data volume and number of retail locations integrated. POS data volume and sales order counts are common metrics. |
| E-commerce and POS integrations | Online orders hitting SAP, POS systems creating sales documents. High-volume Digital Access scenarios. Document-based licensing typically essential. |
| Seasonal peaks | Retail volumes spike during holidays. Engine metrics must accommodate peak periods, not just averages. Under-licensing at peak = non-compliance. |
Digital Access is especially critical in retail. E-commerce platforms and point-of-sale systems generate enormous volumes of sales orders, delivery documents, and invoices in SAP, all without direct SAP user logins. This makes Digital Access licensing one of the largest cost items for retail SAP deployments.
| Solution | Engine Metric | Key Risk |
|---|---|---|
| SAP ATTP | Volume of managed serial numbers or transactions | Drug serialisation volumes can grow rapidly with new product launches or market expansions |
| Quality Management | Batch records / quality inspection transactions | Every batch requires documentation. Undercounting creates compliance gaps. |
| Production planning | Production orders for drug manufacturing | Must cover both internal manufacturing and contract manufacturing (CMO) scenarios |
Pharma compliance = licence compliance. In pharmaceuticals, systems must support stringent audit requirements (FDA, EMA). Licence compliance and documentation are as critical as regulatory compliance. SAP audit findings in pharma can trigger both financial penalties and regulatory scrutiny. Maintain meticulous records of licence entitlements, user assignments, and engine metric consumption.
Across every industry, Digital Access (formerly known as indirect access) is the single largest compliance risk for SAP customers. When third-party systems, customer portals, e-commerce platforms, IoT devices, or middleware create transactions in SAP without direct user logins, those interactions must be licensed.
| Industry | Common Digital Access Scenarios | Risk Level |
|---|---|---|
| Manufacturing | IIoT sensors creating maintenance orders, MES systems posting production confirmations, barcode scanners updating inventory | High |
| Utilities | Customer self-service portals, smart meter data feeds creating consumption records, field-service mobile apps | High |
| Retail | E-commerce orders, POS systems creating sales documents, warehouse management system integrations | Very High |
| Pharmaceuticals | LIMS posting quality results, serialisation systems creating tracking records | Medium-High |
| Financial Services | Trading platforms creating journal entries, external risk systems feeding SAP treasury | Medium |
SAP offers two approaches: the traditional Named User model (every user, direct or indirect, needs a licence) or the Digital Access document model (licence by counting specific business documents created by non-SAP systems). For most industry solutions with heavy third-party integration, the document model is more cost-effective.
| Change | Impact on Industry Solutions |
|---|---|
| Full User Equivalents (FUEs) | RISE uses FUEs instead of traditional named user categories. Industry-specific user roles must be mapped to FUE categories correctly. |
| Digital Access included in RISE | Standard RISE subscriptions typically include Digital Access coverage. However, "included" does not mean "unlimited." Verify high-volume scenarios in writing. |
| Industry add-on subscriptions | Advanced industry capabilities (Retail, Automotive, Life Sciences) may require additional subscriptions on top of the base S/4HANA licence. |
| Dual-run licensing | Running ECC and S/4HANA in parallel during migration requires licences for both. Negotiate dual-use rights explicitly. |
| Engine metrics persist | Industry engine metrics do not disappear in S/4HANA. They may be repackaged or bundled, but the underlying consumption-based model continues. |
SAP industry solutions are specialised software packages designed to meet the unique needs of specific sectors: manufacturing, utilities, retail, pharmaceuticals, financial services, oil and gas, healthcare, and more. They extend SAP's core ERP capabilities with industry-specific processes, compliance features, and metrics.
Through a dual model: Named User licences (for every person accessing SAP, classified by role) plus Package/Engine licences (usage-based metrics specific to the industry module, such as production orders, meter points, or retail locations). Both are typically required simultaneously.
Engine licences are usage-based SAP licences measured by industry-specific metrics rather than user counts. Examples: number of production orders per year (manufacturing), active customer contracts (utilities), number of retail locations (retail), managed serial numbers (pharmaceuticals). They are purchased in blocks and used alongside named user licences.
Digital Access covers scenarios where non-SAP systems (e-commerce platforms, customer portals, IoT devices, POS systems) create transactions in SAP without direct user logins. SAP requires these interactions to be licensed, either via named users or by counting specific business documents. For industry solutions with heavy third-party integration (retail, manufacturing, utilities), Digital Access is often the largest hidden compliance risk.
S/4HANA introduces Full User Equivalents (FUEs) instead of traditional named user categories, bundles Digital Access into RISE subscriptions (but not unlimited), and may require separate add-on subscriptions for advanced industry capabilities. Engine metrics persist in S/4HANA. The 2027 ECC deadline creates urgency for migration planning.
Shop-floor operators who only confirm operations, enter time data, or view production schedules typically qualify for Limited or Employee licence tiers, significantly cheaper than Professional licences. Avoid defaulting all users to Professional. A mid-sized manufacturer can save 40-60% on user licences through accurate classification.
Engine metric scaling (smart meter rollouts can dramatically increase meter point counts mid-contract), customer portal indirect access (customers triggering SAP transactions without SAP licences), and user misclassification across diverse roles. Utilities should monitor engine metrics monthly and address portal access via Digital Access licensing.
Retail generates enormous volumes of sales orders, delivery documents, and invoices through e-commerce platforms and POS systems, all without direct SAP user logins. These document volumes can run into millions per year, making Digital Access one of the largest cost items for retail SAP deployments.
Yes. SAP solutions are highly customisable, allowing businesses to tailor functionalities and workflows to specific operational requirements. However, custom development may introduce additional licensing considerations (Developer licences, custom module licences) and must be documented for audit compliance.
Run SAP's measurement tools (USMM, LAW) regularly. Clean up user records and roles. Monitor engine metric consumption against entitlements. Document all third-party integrations and their Digital Access implications. Engage independent advisory for complex industry deployments.
RISE significantly reduces indirect access risk because Digital Access is typically included in the subscription. However, "included" does not mean "unlimited." High-volume integrations, atypical interface patterns, or scenarios exceeding fair-use thresholds may still incur additional charges. Always verify coverage in writing.