S/4HANA SD Transformation, Migration, Public Cloud and Architecture

Lessons in this topic

• Why S/4HANA Changes SD: Business Drivers and the Learning Path MapUnderstand why organizations move SD from ECC to S/4HANA, what actually changes for sales processes, and how this parent topic sequences into detailed child lessons.
• Choosing and Sequencing an S/4HANA SD Migration Approach: New Implementation vs System Conversion vs Selective Data TransitionLearn how SD-relevant decisions differ across the three main S/4HANA migration approaches, what to validate during each, and how integration and cutover risks show up specifically in sales processes.

Interview questions covered

• Post S/4HANA conversion, billing documents intermittently fail with ATP-related errors that trace back to inconsistent material master data sourced from MDG, and finance flags mismatched revenue postings versus legacy billing. How do you diagnose and resolve this cross-functional issue?
• During cutover and hypercare on S/4HANA Public Cloud, why is application log monitoring (SLG1) important for SD-FI integration, and how does the clean core principle affect how errors are resolved?
• Two weeks into hypercare after an S/4HANA conversion, PP planners report that sales order-driven make-to-order production runs are failing to find the correct customer partner data, and the issue is traced to incomplete Business Partner/CVI synchronization. How do you diagnose and resolve this during hypercare?
• In S/4HANA Public Cloud, what interface monitoring controls are available to track sales data migration jobs and integration errors involving Transportation Management, given the restricted access to traditional backend monitoring transactions?
• During cutover to S/4HANA, why must open sales orders with credit checks and aATP checks be reconciled with FI before go-live weekend, and what is the typical sequencing?
• During hypercare after a cutover, sales orders created via a BTP Integration Suite interface from an external e-commerce platform are intermittently failing to reach S/4HANA. What monitoring and troubleshooting approach would you use to isolate the root cause?
• In an S/4HANA Public Cloud transformation for a company with integrated Transportation Management, what architectural constraints govern how Fiori Sales apps and Business Partner/CVI setup interact with TM shipment planning, and what governance controls should an architect enforce?
• After an S/4HANA conversion, output determination for sales order confirmations shifted from classic NAST-based output to the new Output Management framework (BRFplus rules with Adobe Forms), and finance is asking how output-related controls should be validated for SOX compliance. What control points would you assess?
• During hypercare, sales order interfaces from an MDG-driven customer master feed are creating orders with incomplete output determination, resulting in missing invoices/order confirmations for a subset of customers. How do you diagnose and resolve this?
• In a global template rollout, aATP product allocation checks are intermittently failing for orders created via an MDG-driven interface that syncs material master data across regions. Interface monitoring shows successful IDoc processing, but ATP results are inconsistent across plants. How do you investigate root cause?
• During hypercare after a clean core-aligned S/4HANA conversion, business partner data migrated through CVI causes intermittent sales order creation failures tied to PP-relevant material data links. How do you triage this without violating clean core principles?
• A global template rollout is planning an S/4HANA release upgrade that coincides with integrating EWM for a new warehouse site, and the BP/CVI (Business Partner/Customer-Vendor Integration) setup varies by country in the template. What upgrade risk would you flag regarding BP/CVI and EWM readiness?
• In a global template rollout, what application log controls should be established for open sales order migration to ensure data integrity across multiple country rollouts?
• During an S/4HANA conversion, the simplification item check flags SD-relevant items involving material number field length extension and its impact on PP integration (e.g., BOM and production order references). Using the Migration Cockpit, how do you plan the sequence to avoid breaking existing sales order-to-production linkages?
• As the architect responsible for cutover, what authorization and workflow controls would you enforce around use of the Migration Cockpit to prevent unauthorized mass changes to sales master and transactional data during hypercare?
• Your client is transforming to S/4HANA Public Cloud and wants advanced ATP (aATP) for backorder processing, but Group Reporting requires consistent consolidated views of committed vs. available stock across entities. What architecture considerations would you raise?
• During hypercare after go-live, EWM-integrated deliveries are triggering duplicate output determination via BRFplus for shipping notifications, flooding application logs. How would you architect a fix that avoids destabilizing the live output framework?
• During cutover for sales data migration, you discover that several customer master records were converted to Business Partners but their corresponding MM info records and purchasing views are inconsistent, causing intercompany sales order creation to fail. What is your troubleshooting approach?
• During fit-to-standard workshops for a Public Cloud transformation, the client insists on retaining a legacy custom vendor-consignment process tightly coupled with a non-standard BP/CVI extension, and the interface to MM stock valuation starts throwing inconsistent BP role errors in the sandbox. How do you address this in the workshop and technically?
• As solution architect for an S/4HANA conversion involving billing migration and integration with Transportation Management, how do you design authorization and workflow controls to prevent unauthorized billing document release during the transition period?

Related topics