SAP ERP

Name: SAP ERP
Brand: SAP
Rating: 4.3 (3428 reviews)

Leader

We bring out the best in every business.

Est 1972|Valuation $254.5B|Raised $495.9M

LinkedIn 180K|Website|Web traffic 12.5M|FTEs 2,432|HQ Walldorf, Germany

MarketsIntake-to-Pay Production Planning ERP

Published Oct 15, 2026

01Common complaints

1. **Low-cost, rapid time-to-value required** - SAP implementations and operations tend to have higher up-front and ongoing costs; mid-market ERPs (NetSuite, Dynamics Business Central, Odoo, etc.) may be more appropriate for constrained budgets. 2. **Organization unwilling to standardize processes** - Public cloud ERP success often depends on adopting standard processes; replicating highly customized legacy workflows can increase cost and risk. 3. **Lack of executive alignment on data governance** - Poor data discipline can degrade outcomes and lead to expensive, low-value deployments. 4. **Strong concerns about managed service models or vendor lock-in** - Some practitioners prefer more direct operational control versus managed offerings; validate operational SLAs, escalation paths, and tooling access before committing. 5. **Unwillingness to change spreadsheet-driven reporting practices** - If the organization will not invest in an analytics layer and standardized definitions, reporting dissatisfaction is likely.

Deal disqualifiers / poor fit indicators

strong preference for heavy bespoke customization without appetite for process change
limited budget for change management and data governance
very small teams that cannot sustain SAP operations/skills

Product/portfolio and transition constraints

- **ECC maintenance timelines are a forcing function** for many customers. SAP’s maintenance schedule for Business Suite 7 core applications extends mainstream maintenance to the end of **2027**, with a stated long-term roadmap for S/4HANA through later years. - **Compatibility packs transition:** SAP announced a transition period affecting usage rights of compatibility packs in S/4HANA on-prem, which can impact customers relying on classical ECC functionality during migration.

Security risk reality (example)

A reported critical vulnerability in S/4HANA (CVE‑2025‑42957) was described as enabling significant compromise if unpatched, with limited exploitation reported in the wild by external sources. This highlights the need for disciplined patching and security operations.

Cloud edition functional constraints

Community discussions indicate S/4HANA Public Cloud can have functional restrictions relative to on-prem editions; these restrictions can be beneficial for standardization but may limit specialized scenarios.

02Why they buy

Validated strengths (supported by reviews and market behavior)

Functional breadth across finance and logistics, particularly for product-centric organizations with complex processes.
Large ecosystem and partner network that can support extensive transformation programs and integrations.

Claims that require careful validation

Assertions of superior performance or straightforward implementations depend heavily on partner quality, scope discipline, and organizational readiness.
Awards and rating excerpts should be treated as signals; buyers should sample critical reviews and confirm fit for their industry and processes.

Where competitors have clear advantages

Pricing transparency: Microsoft publishes list pricing for Finance; SAP pricing is more quote-driven.
Simplicity/lower complexity for some deployments: Some mid-market ERPs can deliver faster deployments with fewer specialized skills.

Why customers chose SAP (common drivers)

Across review summaries and practitioner discourse, common drivers include:

breadth of ERP coverage and process depth
fit for complex manufacturing, supply chain, and finance controls
global scalability and a large vendor ecosystem

03Field reports

Review platforms (quant + sample content)

**Gartner Peer Insights (SAP Cloud ERP / SAP S/4HANA Cloud)** - A Gartner Peer Insights page for “SAP Cloud ERP” displays a generally high average rating, with a distribution weighted toward positive ratings. A sample review described SAP as a provider of enterprise resource planning software for large enterprises. (Accessibility note: Gartner Peer Insights may limit access to full review text.) **G2 (SAP Cloud ERP / formerly SAP S/4HANA Cloud)** - G2 hosts a substantial number of reviews for “SAP Cloud ERP (formerly SAP S/4HANA Cloud).” The listing indicates a large review volume, but deeper extraction requires opening individual review pages. **TrustRadius (SAP Cloud ERP / formerly SAP S/4HANA Cloud)** - TrustRadius maintains a review page for SAP Cloud ERP. Vendor-published materials sometimes cite awards or favorable excerpts from TrustRadius; such citations should be reviewed alongside unfiltered customer feedback. **PeerSpot (SAP ERP)** PeerSpot’s SAP ERP review summary highlights common improvement areas identified by contributors: - High cost / unfavorable pricing model - Perceived non-intuitive UI for some users (especially legacy ECC/GUI experiences) - Integration challenges with other systems - Rigid customization patterns - Support responsiveness concerns in some reports - Reporting perceived as complex - Migration to S/4HANA noted as adding cost and project complexity

Community / social themes (Reddit)

Community posts often reflect practitioner perspectives and emphasize recurring pain points and practical considerations. **Negative / cautionary themes** - Implementation failure risk when process and data discipline are weak; some practitioners cite examples of significant project costs and poor outcomes when data integrity was not maintained. - Reporting mismatch versus entrenched spreadsheet processes; multiple contributors emphasize that ERP reporting often requires process redesign and changes to reporting practices. - Skepticism around cloud transition and managed service models; contributors note that ticket-based or remote support models can feel slower and that subscription/managed service costs require careful justification. **Positive / pragmatic themes** - Some consultants and customers report efficient public cloud implementations when scope was limited and standard processes were adopted; these accounts emphasize alignment of scope, partner quality, and change management.

Why some customers leave or resist moving forward

total cost of ownership (licenses, implementation, and ongoing skills)
perceived pressure to move to cloud and changing product direction
customizations and industry-specific processes that do not map cleanly to standard offerings

Vendor-published case references (examples)

SAP marketing mentions recognizable customer logos (e.g., Nestlé, Maire, Versuni) in the context of S/4HANA Cloud customer examples. **Critical evaluation:** - In this research session, sources naming these customers did not include detailed, independently verified metrics (e.g., cost savings, close-cycle reduction, inventory turns). Treat these references as illustrative rather than conclusive evidence of outcomes. - Buyers should request the following from vendors or references when evaluating claimed outcomes: - baseline vs post-change KPIs - methodology and time horizon - scope (which modules, which geographies) - partner involvement and total project spend

Migration research signals (industry surveys)

External reporting indicates uncertainty and delay among ECC customers approaching maintenance deadlines. Surveys and press coverage show a large portion of customers remain on ECC and have not finalized transition plans.

04Best fit

Company size

Typical fit: large, enterprise-scale organizations and/or multi-entity enterprises; larger mid-market organizations may be suitable for public cloud editions.
Practical rule: SAP is strongest when the organization can fund and staff a sizable transformation program.

Industries

Manufacturing (discrete/process)
Consumer goods
Energy/utilities
Pharmaceuticals/life sciences
Industrial services and complex distribution

Roles and personas

Economic buyers: CIO/CTO, CFO, COO, Head of Shared Services
Key stakeholders: VP Finance, Supply Chain, Manufacturing, Procurement, IT Enterprise Architecture, Security
End users: plant ops, procurement analysts, finance controllers, customer service, planners

Best-fit pain points

fragmented systems and need for global process standardization
complex supply chain/manufacturing planning and execution
compliance, auditability, and control requirements

05The pitch

What the product does (objective value proposition)

SAP ERP is SAP’s enterprise resource planning software family used to run core business processes (finance, procurement, manufacturing, supply chain, sales, asset management, etc.). In current market practice, “SAP ERP” often refers to: - **Legacy/core on-prem suite:** **SAP ERP / SAP ECC (ERP Central Component)** as part of SAP Business Suite 7 (historically the dominant large-enterprise ERP). - **Successor platform:** **SAP S/4HANA** (on‑prem and cloud variants), positioned by SAP as the successor platform to ECC. - **Cloud branding:** “SAP Cloud ERP” (naming varies over time, often closely associated with **SAP S/4HANA Cloud / SAP Cloud ERP**). Because buyers evaluating “SAP ERP” today usually end up deciding among **ECC life-extension vs S/4HANA (Public/Private) vs alternative ERP suites**, this report covers the ERP portfolio with emphasis on **S/4HANA Cloud** (current vendor growth focus) and the **ECC-to-S/4HANA transition**.

Target market and market positioning

- **Primary fit:** large enterprises and upper mid-market organizations with complex, multi-entity operations, global footprints, regulated industries, and/or deep manufacturing/supply chain needs. - **Positioning:** positioned for enterprise process standardization and integration across business functions, often used alongside SAP’s broader product ecosystem (BTP, SuccessFactors, Ariba, IBP, EWM, TM, Signavio, etc.). - **Common buying trigger in the mid‑2020s timeframe:** approaching the end of mainstream maintenance for older SAP Business Suite releases and pressure to modernize. SAP has also communicated a long-term roadmap for S/4HANA extending into the next decade.

Get a comprehensive analysis of SAP ERP including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Low-cost, rapid time-to-value required
- SAP implementations and operations tend to have higher up-front and ongoing costs; mid-market ERPs (NetSuite, Dynamics Business Central, Odoo, etc.) may be more appropriate for constrained budgets.
Organization unwilling to standardize processes
- Public cloud ERP success often depends on adopting standard processes; replicating highly customized legacy workflows can increase cost and risk.
Lack of executive alignment on data governance
- Poor data discipline can degrade outcomes and lead to expensive, low-value deployments.
Strong concerns about managed service models or vendor lock-in
- Some practitioners prefer more direct operational control versus managed offerings; validate operational SLAs, escalation paths, and tooling access before committing.
Unwillingness to change spreadsheet-driven reporting practices
- If the organization will not invest in an analytics layer and standardized definitions, reporting dissatisfaction is likely.

Deal disqualifiers / poor fit indicators

strong preference for heavy bespoke customization without appetite for process change
limited budget for change management and data governance
very small teams that cannot sustain SAP operations/skills

Product/portfolio and transition constraints

ECC maintenance timelines are a forcing function for many customers. SAP’s maintenance schedule for Business Suite 7 core applications extends mainstream maintenance to the end of 2027, with a stated long-term roadmap for S/4HANA through later years.
Compatibility packs transition: SAP announced a transition period affecting usage rights of compatibility packs in S/4HANA on-prem, which can impact customers relying on classical ECC functionality during migration.

Security risk reality (example)

A reported critical vulnerability in S/4HANA (CVE‑2025‑42957) was described as enabling significant compromise if unpatched, with limited exploitation reported in the wild by external sources. This highlights the need for disciplined patching and security operations.

Cloud edition functional constraints

Community discussions indicate S/4HANA Public Cloud can have functional restrictions relative to on-prem editions; these restrictions can be beneficial for standardization but may limit specialized scenarios.

02Why they buy

Validated strengths (supported by reviews and market behavior)

Functional breadth across finance and logistics, particularly for product-centric organizations with complex processes.
Large ecosystem and partner network that can support extensive transformation programs and integrations.

Claims that require careful validation

Assertions of superior performance or straightforward implementations depend heavily on partner quality, scope discipline, and organizational readiness.
Awards and rating excerpts should be treated as signals; buyers should sample critical reviews and confirm fit for their industry and processes.

Where competitors have clear advantages

Pricing transparency: Microsoft publishes list pricing for Finance; SAP pricing is more quote-driven.
Simplicity/lower complexity for some deployments: Some mid-market ERPs can deliver faster deployments with fewer specialized skills.

Why customers chose SAP (common drivers)

Across review summaries and practitioner discourse, common drivers include:

breadth of ERP coverage and process depth
fit for complex manufacturing, supply chain, and finance controls
global scalability and a large vendor ecosystem

03Field reports

Review platforms (quant + sample content)

Gartner Peer Insights (SAP Cloud ERP / SAP S/4HANA Cloud)

A Gartner Peer Insights page for “SAP Cloud ERP” displays a generally high average rating, with a distribution weighted toward positive ratings. A sample review described SAP as a provider of enterprise resource planning software for large enterprises. (Accessibility note: Gartner Peer Insights may limit access to full review text.)

G2 (SAP Cloud ERP / formerly SAP S/4HANA Cloud)

G2 hosts a substantial number of reviews for “SAP Cloud ERP (formerly SAP S/4HANA Cloud).” The listing indicates a large review volume, but deeper extraction requires opening individual review pages.

TrustRadius (SAP Cloud ERP / formerly SAP S/4HANA Cloud)

TrustRadius maintains a review page for SAP Cloud ERP. Vendor-published materials sometimes cite awards or favorable excerpts from TrustRadius; such citations should be reviewed alongside unfiltered customer feedback.

PeerSpot (SAP ERP) PeerSpot’s SAP ERP review summary highlights common improvement areas identified by contributors:

High cost / unfavorable pricing model
Perceived non-intuitive UI for some users (especially legacy ECC/GUI experiences)
Integration challenges with other systems
Rigid customization patterns
Support responsiveness concerns in some reports
Reporting perceived as complex
Migration to S/4HANA noted as adding cost and project complexity

Community / social themes (Reddit)

Community posts often reflect practitioner perspectives and emphasize recurring pain points and practical considerations.

Negative / cautionary themes

Implementation failure risk when process and data discipline are weak; some practitioners cite examples of significant project costs and poor outcomes when data integrity was not maintained.
Reporting mismatch versus entrenched spreadsheet processes; multiple contributors emphasize that ERP reporting often requires process redesign and changes to reporting practices.
Skepticism around cloud transition and managed service models; contributors note that ticket-based or remote support models can feel slower and that subscription/managed service costs require careful justification.

Positive / pragmatic themes

Some consultants and customers report efficient public cloud implementations when scope was limited and standard processes were adopted; these accounts emphasize alignment of scope, partner quality, and change management.

Why some customers leave or resist moving forward

total cost of ownership (licenses, implementation, and ongoing skills)
perceived pressure to move to cloud and changing product direction
customizations and industry-specific processes that do not map cleanly to standard offerings

Vendor-published case references (examples)

SAP marketing mentions recognizable customer logos (e.g., Nestlé, Maire, Versuni) in the context of S/4HANA Cloud customer examples.

Critical evaluation:

In this research session, sources naming these customers did not include detailed, independently verified metrics (e.g., cost savings, close-cycle reduction, inventory turns). Treat these references as illustrative rather than conclusive evidence of outcomes.
Buyers should request the following from vendors or references when evaluating claimed outcomes:
- baseline vs post-change KPIs
- methodology and time horizon
- scope (which modules, which geographies)
- partner involvement and total project spend

Migration research signals (industry surveys)

External reporting indicates uncertainty and delay among ECC customers approaching maintenance deadlines. Surveys and press coverage show a large portion of customers remain on ECC and have not finalized transition plans.

04Best fit

Company size

Typical fit: large, enterprise-scale organizations and/or multi-entity enterprises; larger mid-market organizations may be suitable for public cloud editions.
Practical rule: SAP is strongest when the organization can fund and staff a sizable transformation program.

Industries

Manufacturing (discrete/process)
Consumer goods
Energy/utilities
Pharmaceuticals/life sciences
Industrial services and complex distribution

Roles and personas

Economic buyers: CIO/CTO, CFO, COO, Head of Shared Services
Key stakeholders: VP Finance, Supply Chain, Manufacturing, Procurement, IT Enterprise Architecture, Security
End users: plant ops, procurement analysts, finance controllers, customer service, planners

Best-fit pain points

fragmented systems and need for global process standardization
complex supply chain/manufacturing planning and execution
compliance, auditability, and control requirements

05The pitch

What the product does (objective value proposition)

Legacy/core on-prem suite: SAP ERP / SAP ECC (ERP Central Component) as part of SAP Business Suite 7 (historically the dominant large-enterprise ERP).
Successor platform: SAP S/4HANA (on‑prem and cloud variants), positioned by SAP as the successor platform to ECC.
Cloud branding: “SAP Cloud ERP” (naming varies over time, often closely associated with SAP S/4HANA Cloud / SAP Cloud ERP).

Because buyers evaluating “SAP ERP” today usually end up deciding among ECC life-extension vs S/4HANA (Public/Private) vs alternative ERP suites, this report covers the ERP portfolio with emphasis on S/4HANA Cloud (current vendor growth focus) and the ECC-to-S/4HANA transition.

Target market and market positioning

Primary fit: large enterprises and upper mid-market organizations with complex, multi-entity operations, global footprints, regulated industries, and/or deep manufacturing/supply chain needs.
Positioning: positioned for enterprise process standardization and integration across business functions, often used alongside SAP’s broader product ecosystem (BTP, SuccessFactors, Ariba, IBP, EWM, TM, Signavio, etc.).
Common buying trigger in the mid‑2020s timeframe: approaching the end of mainstream maintenance for older SAP Business Suite releases and pressure to modernize. SAP has also communicated a long-term roadmap for S/4HANA extending into the next decade.

Get a comprehensive analysis of SAP ERP including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →