ERPClimb logoERPClimb

SAP QM S/4HANA Quality Management, Migration, Public Cloud and Architecture Interview Questions

S/4HANA Quality Management, Migration, Public Cloud and Architecture is a standard block in SAP QM interviews. It is rarely asked as a definition; it is asked as a situation you have to talk your way through.

This page carries 21 reviewed SAP QM s/4hana quality management, migration, public cloud and architecture interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 14 mid-level and 5 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Treat the answers as a starting structure, not a script. Interviewers in SAP QM rounds follow up on whatever you sound least certain about, so the value is in being able to keep going after the first answer.

21 S/4HANA Quality Management, Migration, Public Cloud and Architecture questions with answers

easyS/4HANA Quality Management, Migration, Public Cloud and Architecture

1. In S/4HANA Public Cloud, what is the standard scope for Quality Management integration with Materials Management, and what QM functions are typically out of scope for the initial rollout?

Public Cloud QM standard scope covers inspection lot creation from goods receipt, inward/outward movements, and quality notifications integrated with MM procurement processes via predefined Fiori apps and Best Practice scope items. Advanced customization such as custom inspection plan logic, complex sampling procedures beyond standard catalogs, and classic transaction-based configuration (like extensive user-exits) are typically restricted, pushing teams toward standard configuration via SSCUI and BTP extensions for gaps.
easyS/4HANA Quality Management, Migration, Public Cloud and Architecture

2. In S/4HANA Public Cloud, which QM-related objects are typically included in a data migration governance scope when integrating with MM master data, and why are these limited compared to on-premise?

Governance scope usually covers material master QM view data, inspection plans, and basic inspection characteristics because Public Cloud restricts custom migration objects to the SAP-delivered Migration Cockpit templates (Manage Your Migration Projects app). Complex objects like custom inspection plan versions or legacy inspection results history are often excluded since extensibility for migration is limited to released APIs and predefined templates, unlike on-premise where LSMW or direct table load flexibility exists.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

3. Your organization runs S/4HANA Public Cloud QM and the analytics team wants a custom quality KPI dashboard combining inspection lot data with defect notification data. What governance constraints must the architecture account for?

In Public Cloud, direct ABAP development and core data model changes are restricted, so the dashboard must rely on released APIs, CDS views exposed via extensibility, or embedded analytics (Fiori analytical apps) rather than custom database access. Governance requires using the extensibility guidelines (in-app or side-by-side via BTP), respecting the Fit-to-Standard scope, and ensuring any custom CDS views only consume released extension points to remain upgrade-stable and supportable.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

4. For a quality data migration project also touching Plant Maintenance notifications, how do you architect API usage to ensure governance and avoid tight coupling between QM and PM custom integrations?

I would design the integration using released communication APIs (such as the Quality Notification and Maintenance Notification OData/SOAP APIs) exposed through defined communication scenarios, avoiding direct table access or RFC calls into internal structures. Governance would include an API catalog documenting versioning and deprecation policies, contract testing between QM and PM integration points, and a central integration layer (BTP Integration Suite) decoupling point-to-point dependencies so future changes to either module's internal implementation don't break the other.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

5. You are designing Fiori role assignments for quality inspectors in an S/4HANA transformation project that also requires integration with a BTP-based mobile inspection app. What key considerations shape your role and authorization design?

I would design business catalogs and business roles aligned to PFCG role concepts mapped to Fiori launchpad spaces, ensuring inspectors get only relevant apps like Record Usage Decision and Result Recording. For BTP integration, I'd configure a principal propagation or OAuth2SAMLBearerAssertion communication arrangement so the mobile app authenticates using the same identity, with restricted communication scenarios exposing only required APIs. I'd also validate authorization objects for inspection lot status changes to prevent unauthorized UD postings from the mobile layer.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

6. A client planning S/4HANA Public Cloud implementation assumes the full ECC QM scope, including complex sample-drawing procedures and dynamic modification rules, is available out-of-box. During scoping, you discover several ECC features are not part of the Public Cloud QM scope. How would you troubleshoot and address this scope gap for the PP integration processes?

I would validate the actual released scope items and Fiori apps for QM in the Public Cloud scope documentation rather than assuming ECC parity, since Public Cloud has a defined, more limited functional scope focused on core inspection processing. For dynamic modification rules or complex sampling not covered, I would assess whether standard configuration alternatives (simpler sampling procedures) meet the business need, or whether the PP integration requires a Private Cloud or on-premise deployment for that specific process, escalating a deployment model reconsideration if the gap is business-critical.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

7. Your client is transforming from ECC QM to S/4HANA and wants to standardize on Fiori Quality apps with embedded analytics. How would you design architecture governance to ensure consistency and prevent app sprawl across plants?

I would define a central Fiori catalog and role template covering apps like Manage Inspection Lots and Manage Quality Notifications, mapped to standardized business roles rather than plant-specific variants. Embedded analytics (CDS-based KPIs) should be governed through a shared analytics content library with change control via transport management, and a UI5 extension governance board reviewing any plant-specific customization requests to prevent divergence and duplicate app variants across the landscape.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

8. Your client is migrating quality data to S/4HANA Public Cloud, but custom ABAP-based extraction programs used in the legacy on-premise landscape cannot be reused. How would you approach quality data migration and ongoing analytics integration in this scoped environment?

In Public Cloud, direct database access and custom ABAP are restricted, so migration must rely on released APIs (e.g., SAP Migration Cockpit with predefined QM migration objects) and standard OData/communication scenarios instead of custom extraction programs. For analytics, use embedded analytics via CDS views and SAP Analytics Cloud connections rather than custom reports. This requires early scoping of which legacy fields map to standard APIs and flagging gaps for extensibility via the in-app or side-by-side extensibility model.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

9. When planning a release upgrade in S/4HANA On-Premise that impacts QM APIs integrated with PM notifications, what architecture steps should be taken to minimize disruption?

Review the release's API compatibility list and deprecation notes for QM-PM integration APIs (e.g., quality notification to maintenance notification linkage), running SAP's simplification item checks pre-upgrade. Regression-test integration scenarios in a sandbox with the upgraded release, validate custom code affecting API usage via ABAP Test Cockpit, and coordinate with PM team on notification workflow changes. Maintain a rollback plan and stagger upgrade across quality/test/production landscapes.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

10. During hypercare after a Public Cloud go-live, the analytics team reports that quality notification KPIs in the embedded analytics app do not match counts from a custom API extract. How do you approach root-causing this discrepancy?

I would first compare the filter criteria and time-slice logic between the Fiori analytical app and the API query, since embedded analytics often use different aggregation levels or status filters than raw OData extracts. Next, verify whether the API is pulling from the correct CDS view versus a compatibility view, check authorization-based row filtering, and confirm both sources use the same as-of date. Finally, validate with business on expected notification lifecycle states included in each count.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

11. You are rolling out a global QM template across multiple countries with varying inspection processes. How would you design Fiori roles and analytics to support both global governance and local flexibility?

Design a role hierarchy with global business roles containing core QM apps (inspection lot processing, results recording, notifications) and local business catalogs layered for country-specific apps or authorization restrictions. Use PFCG-derived roles mapped to Fiori catalogs/spaces, with global KPIs delivered via embedded analytics (CDS views) at corporate level and local variants filtered by plant/company code. Governance board approves any local catalog extensions to prevent role sprawl.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

12. During hypercare, plant maintenance orders are generating unexpected quality notifications for equipment defects, and the architecture team needs to decide governance for this cross-module behavior between QM and PM. What architectural considerations should guide the decision?

First confirm whether notification creation is standard integration (e.g., via configured notification origin/type linking PM and QM) versus a custom enhancement introduced during build, since unexpected volume often points to overly broad configuration scope rather than a defect. Establish clear governance on which module owns notification creation logic, document the integration touchpoint in the architecture decision log, and restrict changes to notification types/origins through change control rather than ad hoc hypercare fixes.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

13. During hypercare for a global QM template rollout, the PM team reports that maintenance notifications aren't automatically creating quality notifications as designed in the template blueprint for one rollout country. How would you architect the API-based troubleshooting approach?

Verify the integration configuration (notification type mapping, partner determination) is correctly transported to that country's client, then check whether the API/BAPI used for cross-application notification creation is being called by confirming interface logs or trace on the relevant integration framework. Compare the failing country's customizing against a working rollout wave using a delta comparison tool, and check if country-specific number ranges or authorization on the API user are blocking creation.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

14. A client on S/4HANA Public Cloud wants a real-time dashboard showing inspection results and defect rates by plant, but the clean core policy prohibits custom code in the ABAP core. How would you architect this analytics requirement?

Use released, whitelisted CDS-based analytical query APIs (OData or SAP API Business Hub content for QM) to expose inspection results and notification data without modifying the core. Build the dashboard in SAP Analytics Cloud or an embedded analytics app consuming these APIs, and if extra calculated fields are needed, implement them in the SAC data layer or via an in-app extensibility CDS view extension rather than core code changes, preserving upgrade stability.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

15. Explain how the clean core principle influences Fiori app and role design for Quality Management users in S/4HANA Public Cloud, and what role BTP typically plays when standard apps fall short.

Clean core means avoiding modifications to standard QM Fiori apps and SAP-delivered business roles; instead, custom business catalogs/roles are built by copying and extending standard ones through supported extensibility, not core code changes. When standard apps lack needed functionality (e.g., a specific inspection dashboard), SAP BTP is used to build side-by-side extensions or custom Fiori apps that consume released APIs/CDS views, keeping the core untouched and upgrade-safe. Role design should still follow least-privilege principles using standard QM business catalogs as the base.
mediumS/4HANA Quality Management, Migration, Public Cloud and Architecture

16. During a global template rollout, regional QM leads need role-restricted access to embedded analytics tiles showing inspection lot backlog and defect rates by their own plants only, with some extensions built on BTP. How should Fiori roles and BTP integration be designed?

Design PFCG-derived business catalogs and role templates with organizational-level restrictions (plant, MRP area) built into the authorization objects behind the embedded analytics apps, then assign region-specific derived roles per rollout wave. For BTP extensions, use principal propagation and destination-based authorization so the extension app inherits the same plant-level restrictions rather than duplicating security logic, keeping the global template consistent while allowing local role variants.
hardS/4HANA Quality Management, Migration, Public Cloud and Architecture

17. In S/4HANA Public Cloud, what data archiving controls are available for inspection lots and quality notifications integrated with EWM, and what limitations should an architect anticipate?

Public Cloud provides standard SAP-delivered archiving objects accessible through Fiori apps for data volume management, following predefined residence and retention rules; custom archiving object changes are not permitted. For EWM-integrated inspection lots (e.g., quality inspection engine in decentralized EWM), archiving dependencies exist since inspection results tied to warehouse tasks must complete before archiving eligibility. Architects must anticipate limited customization of archiving variants and plan retention periods aligned with both ERP and EWM system landscapes.
hardS/4HANA Quality Management, Migration, Public Cloud and Architecture

18. A quality data migration project needs to preserve SD-relevant quality info records (customer-material inspection requirements) with minimal downtime, and integration monitoring shows intermittent failures posting migrated data through custom extensibility objects. What steps would you take to isolate the root cause?

Check the integration monitoring dashboard/logs for the specific error pattern (timeout vs data validation failure) tied to the custom extension used for quality info record migration; correlate failure timestamps with system load or batch job overlaps during migration cutover. Validate that custom field extensions used in the migration object correctly map SD customer-material fields, and test with a smaller data subset to isolate whether it's a volume/performance issue or a mapping defect in the extensibility logic.
hardS/4HANA Quality Management, Migration, Public Cloud and Architecture

19. In an S/4HANA Public Cloud manufacturing environment, quality info records are blocking sales order deliveries for a customer even though the inspection lot for the batch was already accepted (UD 'A'). How would you investigate the root cause across QM, SD, and batch management?

Check whether the delivery block originates from a quality info record configured at the customer/material level for shipment approval, which is independent of the inspection lot usage decision and can require separate release even after UD is set. Verify batch classification and characteristic values were updated from the inspection results, since delivery blocks in Public Cloud manufacturing scope often rely on batch characteristic checks rather than the lot's UD status alone, and confirm the SD delivery block reason code configuration.
hardS/4HANA Quality Management, Migration, Public Cloud and Architecture

20. During hypercare after a QM migration involving EWM extensibility for quality inspection at the warehouse, what controls should be enforced to safely manage post-go-live migration cockpit corrections?

Controls should include a formal change approval process for any Migration Cockpit reruns, restricting reruns to a defined hypercare window with documented business sign-off, and locking EWM extension fields once initial migration completes to avoid conflicting updates from parallel warehouse activity. Reconciliation reports comparing ACDOCA-independent QM data (inspection lots, results) between source and target should be reviewed before and after each correction, and all reruns should be logged for audit traceability.
hardS/4HANA Quality Management, Migration, Public Cloud and Architecture

21. As the solution architect, what controls would you put in place to protect a customer's QM-EWM integration during an S/4HANA release upgrade in a Public Cloud environment where custom logic cannot be directly modified?

Rely on release-independent extension points (BAdIs, released APIs) rather than core modifications so upgrades don't break integration logic; run the compatibility/simplification checks provided for each release to flag deprecated APIs used in QM-EWM inspection triggers. Establish a regression test suite covering inspection lot creation from EWM goods movements, execute it in the upgrade sandbox before productive transport, and maintain a rollback/mitigation plan with the customer's change advisory board if regression failures occur.

Related topics

Quality NotificationsInspection PlanningInspection LotsUsage DecisionQuality CertificatesResults RecordingDefect RecordingQM in ProcurementCalibration InspectionQM Master Data

Next practice step

Practice with Interview AITake a mock test