SAP consulting FAQ: S/4HANA, process mining, DRC, Fiori and Joule

It depends on your custom code.
If you can adopt SAP standard processes, Public Edition is enough: it is standardised SaaS, upgraded twice a year.
If you need to keep your full scope and custom code, choose Private Edition: you decide when to upgrade.
Both editions are available through RISE with SAP.

No path is better in principle; three criteria decide: your technical debt, your volume of custom code and your ECC deadline (end of mainstream maintenance at the end of 2027).
Brownfield converts your existing system, greenfield starts from a new installation, and bluefield selectively carries over your data and processes.
A four-to-eight-week scoping phase, supported by process mining, helps you choose.

From six months for a simple scope to more than eighteen months for multi-country programmes.
A four- to eight-week scoping phase, backed by process mining, makes the schedule reliable.

A single subscription: S/4HANA Cloud (Private or Public Edition), infrastructure and technical operations, and tools such as SAP Signavio.
GROW with SAP targets new Public Edition implementations.

The analysis of event logs (case, activity, timestamp) to reconstruct each actual process: steps, lead times, variants and deviations from the target model.

Usually four to eight weeks: data extraction then dashboards on a priority process, Order-to-Cash or Procure-to-Pay.

No: it applies to ECC, S/4HANA and non-SAP systems.
Before an S/4HANA conversion, it shows how existing processes actually run and the custom code really used.

BPMN 2.0 modelling, analysis of actual processes, governance and sharing, with native SAP connectors.
A Leader in the Gartner Magic Quadrant for Process Mining Platforms (2025) and in the Magic Quadrant for Process Intelligence Platforms (May 2026).

Yes, across the whole suite: BPMN 2.0 modelling (ISO/IEC 19510), process mining, governance and sharing, with functional knowledge of SAP modules.

Document compliance from the ERP: e-invoices in each country’s format, exchange via platform or Peppol, e-reporting and returns, with rules updated by SAP.

Yes: invoices in UBL, CII or Factur-X, exchange with your approved platform, statuses reported back into SAP and e-reporting data prepared.

Yes: Italy, Germany, Belgium, the Peppol network, SAF-T, VAT returns.
A single solution in SAP replaces local connectors.

Yes: native in S/4HANA (on-premise, Private or Public Edition) and available for ECC 6.0 subject to SAP packages and notes.
We favour a configuration that can be reused at the S/4HANA conversion.

Since 1 September 2026: receiving for all companies, issuing for large companies and mid-caps.
SMEs and micro-businesses issue from 1 September 2027, through an approved platform.

SAP’s SaaS analytics solution: BI, planning and AI-assisted predictive analytics, connected live to S/4HANA, BW/4HANA and Datasphere, and open to non-SAP sources.

Yes: budget, rolling forecasts and simulations in the same models as reporting.
A first budget cycle can be rolled out in three to four months.

Natively: SAC reads CDS views over a live connection, without replication.
For history and multiple sources, data flows through Datasphere or BW/4HANA.

A BI tool reports; SAC also lets you plan, with workflows, versions and collaborative input, connected live to SAP models.
It is part of SAP Business Data Cloud.

With an analysis of your actual processes, often with SAP Signavio, then two or three high-value use cases.
The technical building blocks (Fiori, BTP, automation) come next.

No: SAP Fiori and SAP BTP also work with ECC.
We prioritise workstreams that can be reused after conversion, as ECC leaves mainstream maintenance at the end of 2027.

Extensions live next to the ERP rather than inside its code (clean core): development, integration, data and AI in one place, and simpler upgrades.

A Fiori app or a targeted automation is delivered in a few weeks to three months.
Every short release carries a measured KPI: lead time, error rate or adoption.

A generative AI copilot launched in September 2023: it answers in natural language, retrieves data and triggers actions, within user authorisations.
Joule Studio builds custom agents.

With two or three high-value use cases, on reliable data and up-to-date authorisations: a measured pilot first, then scale-up with Joule Studio and SAP AI Core.

Yes for access rights: Joule works within your existing SAP authorisations.
Before any roll-out, we define data and usage governance with you.

No: in batches, starting with the most critical or costly ones.
Neptune DXP and Fiori coexist in the launchpad; each batch is approved before the next one.

The aim is to lose none: every migrated app must offer at least the same functionality as before.
The initial audit inventories each app (usage, criticality, dependencies).
Migration then runs in batches: Neptune DXP and Fiori coexist in the launchpad, and each batch is signed off before the next.

No.
No AI model (LLM) or external service is involved: all conversion rules are built into the tool and your code is never sent outside.
The rules grow with every weekly release.

Yes: Fiori is the native S/4HANA experience, and SAPUI5 relies on the OData, CDS and RAP standards.
Migrating avoids maintaining two UI technologies, in line with clean core principles.

Yes.
Your data is used only to process your request and is never passed on to third parties.

Yes, on +33 1 84 20 01 29, during business hours.
Written reply within two to three working days.