SAP S/4HANA – Questions & Answers

SAP S/4HANA is SAP’s current ERP suite, built to run only on the SAP HANA in-memory database with a simplified data model and the Fiori user experience.

• ECC runs on many databases; S/4HANA runs only on SAP HANA.
• The data model is simpler (for example the Universal Journal and MATDOC replace many tables).
• Fiori is the main user interface, with SAP GUI still available.
• Business Partner replaces separate customer and vendor masters.
• Embedded analytics and real-time processing replace many batch jobs.

Level: Basic
Key terms: S/4HANA, ECC, HANA, Fiori, simplified data model

On-premise, private cloud edition (typically via RISE with SAP) and public cloud edition.

• On-premise: you run and manage the system yourself.
• Private cloud edition: a dedicated system managed by SAP or a hosting partner, with high flexibility for custom code.
• Public cloud edition: multi-tenant SaaS with standard processes and limited modification.
• SAP’s newer branding also uses names such as SAP Cloud ERP and SAP Cloud ERP Private, so check current naming.

Level: Basic
Key terms: On-premise, private cloud, public cloud, RISE

SAP HANA is an in-memory, column-oriented database that processes transactions and analytics on the same data in real time.

• Column storage and compression reduce data volume.
• In-memory processing speeds up reads and aggregations.
• S/4HANA removes pre-calculated aggregate tables and relies on the database for calculation.
• Code pushdown moves logic to the database for performance.

Level: Basic
Key terms: HANA, column store, in-memory, code pushdown

The Universal Journal is a single table that holds financial and controlling line items, so FI, CO, asset accounting and material ledger share one source of truth.

• Table ACDOCA replaces separate tables such as COEP, BSEG data for reporting, ANEP and others as the main store.
• No reconciliation is needed between FI and CO.
• It supports multiple ledgers and currencies and extension fields.
• Reports read directly from ACDOCA through CDS views.

Level: Basic
Key terms: ACDOCA, universal journal, ledger, reconciliation

SAP removed redundant tables, aggregates and indexes, and merged data into fewer, cleaner structures.

• Examples: MATDOC for material documents, ACDOCA for financials, Business Partner for customers and vendors, and a 40-character material number.
• Many old tables become compatibility views.
• Custom code that reads or writes old tables must be adapted.
• This reduces data volume and speeds up processing.

Level: Intermediate
Key terms: MATDOC, ACDOCA, compatibility view, simplification list

Fiori is SAP’s role-based, responsive user experience, and the Fiori Launchpad is the entry point that shows apps to users as tiles.

• App types: transactional, analytical and fact sheets.
• Launchpad content is organised by catalogs, groups or newer spaces and pages.
• Apps use OData services and SAPUI5.
• Roles and authorisations control what each user sees.

Level: Basic
Key terms: Fiori, Launchpad, spaces and pages, OData, SAPUI5

The S/4HANA core on the ABAP platform and HANA database, the Fiori front end, integration to other systems and SAP Business Technology Platform for extensions.

• The core holds business processes.
• Fiori front-end server is embedded in the same system in current releases.
• SAP BTP provides integration, extension and analytics services.
• Connected systems include SAP Ariba, SuccessFactors and third-party applications.

Level: Intermediate
Key terms: ABAP platform, Fiori, BTP, integration

SAP ships a new S/4HANA release each year; ECC 6.0 EHP 6 to 8 has mainstream maintenance until the end of 2027, with paid extended maintenance to 2030.

• Earlier ECC enhancement packages (EHP 0 to 5) reached the end of mainstream maintenance on 31 December 2025.
• S/4HANA 2025 is the latest release confirmed at the time of writing; SAP usually publishes a new one each autumn, so check for a 2026 version.
• Maintenance dates can change, so confirm them on SAP’s official roadmap.

Level: Intermediate
Key terms: End of maintenance, 2027, 2030, annual release

Greenfield is a fresh implementation, brownfield converts an existing ECC system, and bluefield (selective data transition) selects processes and data to carry over.

• Greenfield: clean design, minimal legacy, but higher effort and data migration.
• Brownfield: system conversion that keeps configuration and history, but can carry legacy problems.
• Bluefield: a hybrid, often with tools from partners for selective transition.
• The choice depends on custom code, process fit, data quality and timeline.

Level: Basic
Key terms: Greenfield, brownfield, bluefield, system conversion

SAP Readiness Check, Maintenance Planner, Software Update Manager with Database Migration Option, simplification item checks and the custom code migration tools.

• Readiness Check: analyses the ECC system for impact.
• Maintenance Planner: plans the target stack and creates the stack file.
• SUM with DMO: performs the update and database migration in one run.
• ATC and custom code migration: find and fix incompatible code.
• Data migration: Migrate Your Data app (formerly LTMC) for new loads.

Level: Intermediate
Key terms: Readiness Check, Maintenance Planner, SUM, DMO, ATC

The Software Update Manager with Database Migration Option updates the SAP software and migrates the database to HANA in a single downtime-optimised process.

• It combines the upgrade and the database migration.
• Reduces overall downtime compared with doing both steps separately.
• Needs a prepared target stack file from Maintenance Planner.
• Used for ECC to S/4HANA conversion and for later release upgrades.

Level: Intermediate
Key terms: SUM, DMO, downtime, stack.xml

Readiness Check analyses an ECC system for S/4HANA impact, and the Simplification Item Catalog lists the functional and technical changes between ECC and S/4HANA.

• Readiness Check covers custom code, add-ons, simplification items, sizing and data volume.
• Each simplification item has a SAP Note and describes the change and required action.
• Simplification Item Check runs against your system before conversion.
• Findings drive the project scope and effort.

Level: Basic
Key terms: Readiness Check, simplification item, SAP Note

The Maintenance Planner is an SAP tool that checks compatibility and generates the download basket and stack file for a conversion or update.

• Verifies that add-ons and components are supported in the target release.
• Produces the stack.xml file used by SUM.
• Works with the system landscape data sent from the customer system.
• Prevents downloading unsupported or wrong components.

Level: Intermediate
Key terms: Maintenance Planner, stack.xml, add-on compatibility

The Migration Cockpit loads data into S/4HANA using predefined migration objects; the Fiori app Migrate Your Data replaces the older LTMC transaction.

• Migration objects cover common data such as business partners, materials and open items.
• Two approaches: staging tables or file upload.
• The cockpit includes mapping, validation and simulation.
• Check the current release notes for supported objects.

Level: Intermediate
Key terms: Migration cockpit, Migrate Your Data, LTMC, migration object

Selective Data Transition moves only chosen company codes, history or processes into a new S/4HANA system, using a shell conversion or a similar approach.

• Suited to carve-outs, mergers and restructuring.
• Often involves partner tools and careful data scoping.
• Lets you restructure data while keeping some history.
• More complex and costly than a standard conversion.

Level: Advanced
Key terms: Selective data transition, shell conversion, carve-out

RISE with SAP is a subscription package that bundles S/4HANA Cloud (private edition), infrastructure, technical services, tools and BTP credits.

• SAP provides the managed environment and technical operations.
• Includes business process tools and, depending on the contract, extra services.
• The customer still owns business configuration and process design.
• Contract details vary, so check the current offer.

Level: Basic
Key terms: RISE with SAP, private cloud, subscription, BTP

Business Partner is the single master record for customers and vendors, and Customer-Vendor Integration synchronises it with the older customer and vendor tables.

• Transaction BP creates partners with roles such as FLCU00 (customer) and FLVN00 (vendor).
• CVI keeps data synchronised with KNA1, LFA1 and related tables.
• One partner can have several roles.
• Old transactions such as XK01 and XD01 are replaced by BP.

Level: Basic
Key terms: BP, CVI, FLVN00, FLCU00, LFA1

The leading ledger carries the main accounting; additional ledgers or extension ledgers support parallel accounting standards.

• Leading ledger 0L is the default.
• Non-leading ledgers store full parallel data for other standards.
• Extension ledgers store only the differences from a base ledger.
• All ledgers sit in ACDOCA with the ledger as a key field.

Level: Intermediate
Key terms: Leading ledger, extension ledger, parallel accounting, ACDOCA

Asset Accounting is integrated with the Universal Journal, and depreciation areas post in parallel as ledgers.

• New Asset Accounting is mandatory.
• Asset values are held in ACDOCA, and old tables such as ANLC are replaced by views.
• Parallel valuation is handled through ledgers.
• Depreciation runs are faster and more flexible.

Level: Intermediate
Key terms: New Asset Accounting, ANLC, ACDOCA, depreciation

The Material Ledger is embedded in inventory valuation so that actual costing and parallel currencies are available for all materials.

• Valuation data and price differences are stored in the Universal Journal.
• Actual costing can be activated on top.
• It supports multiple currencies and valuation views.
• Plan the migration of existing valuation data carefully.

Level: Intermediate
Key terms: Material Ledger, actual costing, valuation, CKMLCP

Central Finance replicates financial documents from source systems (SAP or non-SAP) into one S/4HANA system for central reporting and processes.

• Uses replication tools such as SLT or similar.
• Allows common reporting without migrating each system.
• Can include central payment and mapping of master data.
• A common step in transformation roadmaps.

Level: Intermediate
Key terms: Central Finance, SLT, replication, central reporting

Account-based profitability analysis (margin analysis) is the default and is integrated into the Universal Journal; costing-based CO-PA is still possible.

• Margin analysis reads from ACDOCA, so FI and CO-PA reconcile automatically.
• Costing-based CO-PA can be used in parallel for value fields and costing details.
• Profitability characteristics and derivation rules are still maintained.

Level: Intermediate
Key terms: Margin analysis, CO-PA, account-based, costing-based

Group Reporting is SAP’s consolidation solution built into S/4HANA that uses the Universal Journal data.

• Handles currency translation, intercompany elimination and consolidation.
• Uses the same data model and master data as accounting.
• It replaces older consolidation tools in new implementations.
• Often combined with SAP Analytics Cloud for reporting.

Level: Intermediate
Key terms: Group Reporting, consolidation, intercompany, SAC

SAP Credit Management (FIN-FSCM) replaces the older SD credit management, and bank and payment processes are increasingly centralised.

• Credit exposure and scoring come from Credit Management.
• Bank Account Management and Advanced Payment Management centralise bank data and payments.
• Business partners are linked to credit segments.
• Check the simplification list for what applies to your release.

Level: Intermediate
Key terms: FIN-FSCM, credit management, bank account management

Material documents are in the single table MATDOC, and the material number can be up to 40 characters.

• MKPF and MSEG become compatibility views.
• Stock totals are calculated rather than updated in many aggregate tables.
• Extended material numbers need interface and custom code checks.
• Old fields and reports must be adapted.

Level: Intermediate
Key terms: MATDOC, MKPF, MSEG, material number length

MRP Live (MD01N) runs the planning calculation in the HANA database, which makes it much faster than classic MRP.

• Classic MRP runs on the application server record by record.
• MRP Live uses database processing and works with MRP areas.
• Some classic functions behave differently, so test your planning scenarios.
• Fiori apps such as Monitor Material Coverage support planners.

Level: Intermediate
Key terms: MD01N, MRP Live, MRP area, HANA

Advanced ATP is the next-generation availability check, using HANA for fast checks, with new options like product allocation and alternative-based confirmation.

• Provides improved performance for large order volumes.
• Supports checks based on supply and demand, backorder processing and alternatives.
• It replaces classic ATP for many scenarios.
• Requires configuration and may need custom code review.

Level: Intermediate
Key terms: aATP, product allocation, backorder processing

SD gains simplified data structures, new credit management, revised output management and improved pricing and billing integration.

• Document flow and index tables are simplified.
• Credit checks use SAP Credit Management.
• Output management can use BRF+ and Adobe forms.
• Fiori apps support order management, billing and analytics.

Level: Intermediate
Key terms: SD, billing, credit management, output management

Output management uses BRF+ rules and Adobe forms for new output; the classic NACE output control still exists for compatibility.

• New output uses output types determined by BRF+ rules and email, print or XML channels.
• Classic NACE can be used for existing documents.
• Cloud and public editions rely on the newer approach.
• Plan migration of forms and rules.

Level: Intermediate
Key terms: BRF+, Adobe Forms, NACE, output type

Inventory management is simplified with the stock calculated from MATDOC, which reduces locking and data volume.

• Aggregates such as MARD quantities are replaced by calculations and views.
• Posting throughput improves because of reduced locking.
• Negative stock rules still exist and are configured.
• Custom code that reads old tables must be adapted.

Level: Intermediate
Key terms: MATDOC, MARD, negative stock, stock calculation

SAP offers extended warehouse, transportation and production planning as embedded options inside S/4HANA, sharing one platform.

• Embedded EWM provides bin-level warehouse management.
• Embedded TM supports freight planning and execution.
• Embedded PP/DS supports detailed scheduling.
• Licensing varies between basic and advanced scope.

Level: Advanced
Key terms: Embedded EWM, TM, PP/DS, licensing

Examples include XK01 and XD01 replaced by BP, classic MRP replaced by MRP Live, and SD credit management replaced by FIN-FSCM.

• LIS and some reporting structures are replaced by embedded analytics.
• Classic WM is in compatibility scope, with EWM as the target.
• Some transactions remain but are not recommended.
• Use the Simplification Item Catalog for the full list.

Level: Basic
Key terms: Simplification list, BP, MD01N, FIN-FSCM

Clean core means keeping the standard S/4HANA system free of modifications and building extensions in a way that does not change the SAP core.

• Use released APIs and extension points instead of direct changes.
• Prefer in-app extensibility and side-by-side extensions on SAP BTP.
• Keeps upgrades faster and less risky.
• SAP rates custom code and systems to show how clean they are, so check current tools.

Level: Basic
Key terms: Clean core, released API, BTP, extensibility

In-app (key user) extensibility, developer extensibility using ABAP Cloud, and side-by-side extensibility on SAP BTP.

• Key user: custom fields, logic and UI changes through Fiori apps.
• Developer (on-stack): ABAP Cloud development using released objects.
• Side-by-side: applications on BTP integrating through APIs and events.
• Choose based on complexity, data access and lifecycle needs.

Level: Intermediate
Key terms: Key user extensibility, ABAP Cloud, BTP, side-by-side

CDS views define data models in the database layer, and the Virtual Data Model is SAP’s structured set of CDS views for business data.

• Layers: basic (interface), composite and consumption views.
• Used for analytics, Fiori apps and APIs.
• Annotations add semantics such as UI and OData exposure.
• Developed in ABAP Development Tools.

Level: Intermediate
Key terms: CDS, VDM, interface view, consumption view

Use the ABAP Test Cockpit with S/4HANA readiness checks and the custom code migration tooling to find and fix problems.

• Check for removed tables, changed data model and incompatible statements.
• Remove unused code first to reduce effort.
• Adjust SELECT statements, use new APIs and test.
• Apply quick fixes where available and run unit tests.

Level: Intermediate
Key terms: ATC, SCI, custom code migration, SPDD

Users need roles with the Fiori catalogs, spaces and pages plus the back-end authorizations and active OData services.

• Business catalogs group apps, and roles assign them.
• Back-end authorizations are maintained in PFCG with SU24 defaults.
• OData services must be activated.
• SAP delivers business roles (SAP_BR_*) as a starting point.

Level: Intermediate
Key terms: PFCG, SU24, business catalog, SAP_BR

OData services expose business data for Fiori and integration, and SAP publishes released APIs on the SAP Business Accelerator Hub.

• Services can be created from CDS views or in ABAP (SEGW).
• Registered and activated through the gateway maintenance transactions.
• Released APIs are the stable choice for integration.
• Events and SOAP/REST APIs complement OData.

Level: Intermediate
Key terms: OData, SEGW, /IWFND/MAINT_SERVICE, released API

SAP BTP is SAP’s cloud platform for integration, data, analytics and application development that extends S/4HANA.

• Services include Integration Suite, Build, AI and analytics.
• Used for clean core side-by-side extensions.
• Connects to S/4HANA through the Cloud Connector or APIs.
• Licensing is usage-based.

Level: Intermediate
Key terms: BTP, Integration Suite, Cloud Connector, extension

Embedded analytics uses CDS-based queries and Fiori analytical apps to report on live transactional data.

• Analytical queries are built on CDS views.
• Fiori apps such as KPI tiles and analytical list pages present results.
• Custom queries can be created by key users.
• For wide enterprise reporting, combine with SAP Analytics Cloud or a data warehouse.

Level: Intermediate
Key terms: Embedded analytics, analytical query, KPI, SAC

SAP Cloud ALM is the cloud-based application lifecycle tool for implementation and operations; Solution Manager is the older on-premise tool.

• Cloud ALM supports project, process and test management plus monitoring.
• It targets cloud and hybrid landscapes.
• Solution Manager remains for existing on-premise needs, but SAP’s direction is Cloud ALM.
• Check the current feature scope.

Level: Intermediate
Key terms: Cloud ALM, Solution Manager, monitoring, test management

Choose IDocs for existing batch-style SAP integration, APIs for real-time requests and events for loosely coupled, near real-time updates.

• IDocs remain supported and common.
• OData and REST APIs suit real-time integration.
• Business events through event brokers support decoupling.
• SAP Integration Suite helps with mapping and monitoring.

Level: Intermediate
Key terms: IDoc, API, event, Integration Suite

Combine unit, integration and user acceptance tests with data reconciliation and, where possible, test automation.

• Define test scope from the business process list.
• Reconcile financial balances, open items and stock between ECC and S/4HANA.
• Run mock conversions before the final cutover.
• Use test automation for regression testing.

Level: Intermediate
Key terms: Mock conversion, reconciliation, UAT, test automation

Archiving moves old data out of the HANA database to reduce memory use and cost.

• HANA memory is more expensive than disk.
• Clean up and archive before conversion to cut the size.
• Archiving objects and residence policies are used.
• Keep legal retention in mind.

Level: Intermediate
Key terms: Data archiving, ILM, data volume, HANA memory

Assess, prepare, convert and test: run readiness checks, clean up custom code and data, run mock conversions, then cut over.

• Run Readiness Check and the simplification item check.
• Clean up unused custom code, data and add-ons.
• Plan the stack using Maintenance Planner and run SUM in sandbox then dev.
• Perform multiple mock cutovers and rehearse downtime.
• Test, train users and prepare hypercare.

Level: Advanced
Key terms: Readiness Check, SUM, mock cutover, hypercare

Compare process fit, amount of custom code, data quality, timeline and the client’s wish to redesign.

• Greenfield suits clients with heavy customisation or poor data who want to redesign.
• Brownfield suits stable processes with good data and a limited budget.
• Consider risk, change impact and business disruption.
• A clear business case and a workshop with stakeholders are needed.

Level: Advanced
Key terms: Greenfield, brownfield, business case, process fit

Analyse usage, retire what is not used, fix what must stay and move extensions toward clean core.

• Use usage data and the ATC to find dead and incompatible code.
• Prioritise critical objects and rewrite where needed.
• Replace modifications with released extension points.
• Move large enhancements to BTP if practical.

Level: Advanced
Key terms: ATC, usage analysis, Z code, clean core

Run CVI preparation, clean the data and convert customers and vendors into Business Partners before or during conversion.

• Clean duplicates and fix missing data.
• Configure number ranges and BP roles.
• Run synchronisation and check the CVI cockpit.
• Validate with reports and sample transactions.

Level: Advanced
Key terms: CVI, BP, number range, data cleansing

Check roles and catalogs, back-end authorizations, OData activation, caches and error logs.

• Confirm the user’s role includes the catalog or space.
• Check the OData service is active in the gateway.
• Review authorization failures with SU53 or the trace.
• Clear the Launchpad cache and review the gateway error log.
• Confirm the app’s prerequisites and release.

Level: Advanced
Key terms: SU53, /IWFND/ERROR_LOG, PFCG, cache

Common problems are data quality, custom code, change management, scope creep and unclear business ownership.

• Start data cleansing early.
• Limit custom code and follow clean core.
• Run a strong change and training plan.
• Keep scope under control with governance.
• Test early and often with real business users.

Level: Advanced
Key terms: Data quality, change management, scope, governance