Study guide
11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
Key Takeaways Explain This Topic AI
The SAP S/4HANA Migration Cockpit, opened with the Migrate Your Data app, migrates data with local staging tables, a remote SAP HANA staging schema, or directly from an SAP system.
Migration templates are XML or CSV files of at most 100 MB; mapping tasks, an optional simulation, and the migration follow, with 8 parallel jobs by default.
End-to-end, integration, data migration, and user acceptance tests are formal and documented in the SAP Cloud ALM Test Preparation, Test Plans, and Test Execution apps.
Regression tests after upgrades are the customer's responsibility and can be automated with Tricentis Test Automation for SAP.
Last updated: October 2026
Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
The last two units of the S4C03 course cover the final steps before go-live: loading business data into the new system and proving that the configured processes work. Both matter to a sales consultant, who typically owns migration objects such as customers or open sales orders and writes the test cases for order-to-cash processes.
The SAP S/4HANA Migration Cockpit
The SAP S/4HANA Migration Cockpit moves data from as many SAP or non-SAP legacy systems as needed. It is opened with the Migrate Your Data app in all deployments of SAP S/4HANA, although the functions and available templates can differ by deployment. You need authorization for the app and for each type of data, because the cockpit uses the same APIs and checks as the business apps; creating a bank through migration is checked like creating it in Manage Banks . Single master data records can instead be created with the master data scripts provided as accelerators in SAP Signavio Process Navigator.
Method How It Works When to Use
Staging tables, local schema The cockpit creates a staging table in SAP S/4HANA for each migration object, filled from XML or CSV templates The standard approach
Staging tables, remote SAP HANA schema Staging tables are created in a separate SAP HANA database that customer ETL code or SAP Data Services fills (described in scope item 2Q2 , Data Migration to SAP S/4HANA from Staging ) More setup, but efficient for large volumes
Migrate data directly from SAP system An RFC connection to an SAP ERP system on a compatible release; the data is converted to the SAP S/4HANA data model during the transfer SAP source systems
Guided Procedure with Staging Tables
Create a migration project and select the migration objects. The objects offered depend on the business processes active in the system, and the rule of thumb is to migrate all of them, because each supports processes. Check each object's documentation for the app that validates the result, and migrate predecessor objects first.
Download the template: XML includes two information tabs with tips on common errors, while CSV leaves more room for data. A single file, or a ZIP file, may be at most 100 MB . Paste values only, because copied formatting corrupts the file.
Upload the filled template and prepare the staging tables.
Process the mapping tasks: value mapping (target value for each source value) and fixed values (defaults for target fields).
Optionally simulate , then migrate ; both steps can be cancelled. By default, 8 jobs run in parallel so that other users are not affected; Job Management can change this.
Check the migration results through the links to the relevant apps, create a correction file if errors occurred, and close the project, optionally setting a data retention period.
Status, Statistics, and Extensibility
The Data Migration Status app summarizes all migration objects and uses Situation Handling to notify you when a simulation or migration has finished, so you can work on other tasks meanwhile (SAP Note 2681413). Its extended statistics , active by default, show source values, mapped target values, and target IDs for validation and auditing; switching them off for an object also deletes the statistics already collected. Custom fields that are enabled for APIs in the Custom Fields app are added to the relevant migration object automatically. The Migration Object Modeler changes source and target structures and their mapping; never change template headers or columns in Excel, because that corrupts the file.
Test Strategy
Test When Formal?
Unit and string tests During configuration and customization Informal
End-to-end process, integration, and data migration tests Realize phase, in the test system after the integrations are set up and the data is migrated Formal, documented in SAP Cloud ALM
User acceptance test (UAT) Realize phase, by the customer LoB experts who took part in the fit-to-standard workshops Formal; all issues must be resolved before the Deploy phase
Regression tests Run phase, after release upgrades Customer responsibility, ideally automated
The customer experts from the workshops are the best UAT testers: they reported the requirements and already know how to navigate the system. If an upgrade happens before go-live, the partner team pauses the implementation to test the processes built so far against the new release. When custom logic changes a standard process, the standard test case must be adapted as well, so that automated tests check the custom outcome. The Scope and Dependencies spreadsheet in SAP Signavio Process Navigator ( Accelerators → Getting Started ) helps plan the tests.
Test Management in SAP Cloud ALM
Test Preparation app: create test cases from the finalized scope. For SAP Best Practices processes, the titles of the test procedures are pulled in from the process's test script. Give the case a title such as the process name plus "UAT", select the scope, the solution process, and its process flow diagram, choose the activities in scope (small changes to the steps are possible), set the status to Prepared , and save. Testers still need the test script itself from SAP Signavio Process Navigator; custom processes can be uploaded as custom test cases.
Test Plans app: group one or more test cases, for example into an end-to-end test plan for a line of business, assign a tester and a time window, and set the status to In Testing . The plan then appears as a task in the tester's Overview app. Testers must exist as SAP Cloud ALM users, which the IT Contact arranges.
Test Execution app: record whether each test procedure passed or failed and, if not, why.
Tricentis Test Automation for SAP is available to SAP Enterprise Support customers for automated tests of SAP user interfaces and APIs, and it comes with test automation content for regression tests of new cloud releases. SAP Cloud ALM remains the orchestrator of test management and the application lifecycle, while Tricentis executes the automated tests. It is activated with the wizard Set Up Tricentis Test Automation for SAP in the administration area of SAP Cloud ALM.
Worked Example: Order-to-Cash Data and Tests
A sales consultant prepares go-live for order to cash.
In Migrate Your Data , the consultant creates a project with the objects for customers (business partners), products, sales prices, and open sales orders, respecting that customers and products must exist before open orders. Templates are filled in XML format, kept under 100 MB, uploaded, mapped, simulated, and migrated.
Data Migration Status sends a notification when the open sales orders are migrated, and the extended statistics show how many records were loaded per sales organization.
In Test Preparation , the consultant creates a test case "Sell from Stock - UAT" with the relevant test procedures and sets it to Prepared.
In Test Plans , the case is assigned to two customer sales experts with a one-week window and set to In Testing. They record the results in Test Execution , and open issues are fixed before the Deploy phase.
Tip
Separate the migration questions (cockpit methods, 100 MB template limit, 8 default jobs, Data Migration Status) from the testing questions (formal versus informal tests, UAT by customer experts, Cloud ALM test apps, Tricentis for regression).