SAP Community > Products and Technology > Enterprise Resource Planning > ERP Blogs by Members

> Step-by-Step Guide to ECC to S/4HANA Migration wit...

Step-by-Step Guide to ECC to S/4HANA Migration with Migration Cockpit

Kaushik_Samanta
Explorer
‎2025 Jan 13 12:35 PM

 14 Kudos

23,518 Views

Migration Project Overview: ECC to S/4HANA

The migration project from ECC to S/4HANA is divided into three key phases, each with distinct roles and responsibilities:

1. Pre-Migration

This phase lays the groundwork for a smooth migration.

Key Prerequisite: A BASIS consultant must apply SAP notes to the ECC server. This is essential to initiate the pre-migration process.

Primary Activities: Functional consultants play a crucial role in preparing the system for migration.

2. Technical Migration

This phase involves converting the data and the system to S/4HANA.

Responsible Teams: BASIS consultants and ABAP developers (ABAPers) are responsible for executing technical migration tasks.

Key Notes: All data will be migrated to S/4HANA, except for Rebate Agreement data.

3. Post-Migration

This phase ensures that all configurations and critical functionalities are operational.

Responsible Teams: Functional consultants are primarily responsible for post-migration tasks.

Primary Activities:

BP Configuration: Set up Business Partner roles and data.

Migrate Condition Master & Credit Master Data: Ensure all pricing conditions and credit limits are transferred.
Configure Credit Management: Update and align credit management settings with S/4HANA capabilities.

Optional Post-Migration Activities

Settlement Management Configuration: Align with S/4HANA's streamlined processes.

BRF+ (Business Rules Framework Plus): Configure advanced rules and workflows for decision automation.
1. Pre-Migration Configuration & Activities (In ECC)

To initiate the migration project, the BASIS consultant must apply the necessary SAP notes in the ECC system. Once this is done, the
following configuration and activities must be completed:

1. BASIS has to apply SAP notes, so we start with below configuration

2. CVI configuration ( Customer Vendor Integration / Direction Customer to BP)
3. Define BP roles
4. Define BP groupings
5. Define BP number ranges
6. Assign account groups to BP roles
7. Assign account groups to BP groupings
8. Upgradation check report generate (this report ensures system readiness to migrate customers and vendors to the BP framework)

Execution Details:

Transaction Code: SA38 or SE38

Program Name: PRECHEK_UPGRADATION_REPORT
Requirement: The report must complete successfully without errors to proceed with customer and vendor migration.

9. Simplification Item Check Report (this report identifies errors or inconsistencies across all modules before proceeding with migration)

Execution Details:

Program Name: /SDF/RC_START_CHECK

Error Code Guidance:

Return Code < 7: Errors can be skipped; migration activities (pre & post) can proceed.
Return Code = 7: Pre-migration can proceed, but issues will block post-migration activities.
Return Code > 7: Stop migration entirely and resolve errors before continuing.

10. Migration of Customers and vendors to Business Partners (BP) (all customers and vendors in the ECC server are migrated to the BP
framework using the SAP Migration Cockpit)

2. Technical Migration: ECC to S/4HANA

The technical migration phase involves converting the ECC system to S/4HANA. This critical process is managed by ABAP and BASIS
consultants, and it requires the client to halt business operations on the Production server during migration.

Key Activities in Technical Migration

Once we migrate all customers and vendors to BP successfully the we will inform technical team, to transfer all master data and Transactional
data to S4 Hana Server.

1. Data Conversion

Scope of Conversion:

Master Data: Includes customer, vendor, material, and other static data.
Transactional Data: Sales orders, purchase orders, and other ongoing business transactions.
Enhancements & Reports: Custom ABAP programs, reports, and user enhancements are adjusted for compatibility with
S/4HANA.
Custom Tables (Z Tables): Migrated to S/4HANA environment.
Conditions: Migrated partially; the rest is addressed in post-migration.
Rebate Agreement Master Data: Not converted during technical migration
 2. Condition Master Data Handling

After the technical migration, the Condition Master Data needs additional processing.
Reason: Data is updated in the ECC KONV table, but in S/4HANA, it must be migrated to the PRCD_ELEMENTS table.
Resolution:

Technical consultants apply relevant SAP Notes to redirect data to the correct tables (e.g., VAUK → VBAK, VUBP → VBAP).

3. Post-Migration Handover

Once the technical migration is successfully completed, the system is handed over to functional consultants for post-migration
activities.

3. Post-Migration Activities (S/4HANA System)

After the completion of the technical migration, the S/4HANA system will be operational. The functional consultant is responsible for ensuring
that all configurations and data migrations are completed to enable seamless business operations in the new system.

Core Post-Migration Activities:

1. BP Configuration (Direction: BP → Customer)

Align Business Partner (BP) data to ensure it maps correctly to customer data in the S/4HANA system.
Validate the consistency of BP roles, groupings, and mappings post-migration.

2. Migrate Condition Master

Transfer pricing and other condition records from the KONV table (ECC) to the PRCD_ELEMENTS table (S/4HANA).

3. Configure Credit Master

Set up credit management settings as per S/4HANA’s new credit management functionalities.
Map and validate credit limits for customers.

4. Migrate Credit Master

Transfer credit-related master data to the new system.

Ensure proper linking of credit data with Business Partner records.

Optional Configurations (Customer-Specific)

Configure Settlement Management

Set up the new Settlement Management framework to replace traditional rebate agreement functionality.

Configure BRF+ (Business Rules Framework Plus)

Implement BRF+ for generating and automating billing document outputs.

Configure rules for customized outputs as per the business requirements.

Advanced Available-to-Promise (AATP)

Configure and activate the AATP functionality for enhanced order fulfillment capabilities, including backorders and product
allocation.
Migration Process with Existing Landscape: Converting from ECC to S/4HANA

When migrating from ECC to S/4HANA with the existing landscape, a structured approach to ensure a smooth transition. Below are the key
steps to follow during the migration process:

1. Pre-Migration Preparation

Close and move any pending TRs (Transport Requests) that are near completion.
For TRs that can't be closed soon, inform BASIS consultants, who will back up and apply the TRs during "Hanatization."

2. Backup

Take a backup of the Production system to Development.

3. SAP Notes Application

BASIS consultants apply necessary SAP Notes for the migration process.
Configurations : Prerequisite for Migration Project

After BASIS applies SAP notes, the following steps are needed to initiate migration:

Step 1: Activate Post Processing Orders:

Go to SPRO → Cross Application Component → General Application Functions → Post Processing Office → Business Process → Activate
Creation of Post Processing Orders.

In ECC, the approach is Customer to BP. In S/4HANA, it will be BP to Customer, so this needs to be activated.

Optional in ECC, Required in S/4HANA:

CVI_03 – BP to Customer
CVI_04 – BP to Vendor
Step 2: Activate Function Modules (Required for Migration Cockpit)

Go to SPRO → Cross Application Component → SAP Business Partner → Data Distribution → Activate Function Modules

Check Function Modules Activation:

Ensure the following function modules are activated:

COM_BUPA_MWX_CREATE_MAIN
COM_BUPA_MWX_CREATE_REL
BUPA_CREATE_CHANGE_POINTER
BUPA_OUTBOUND_ALE_REL
MDS_BUPA_OUTBOUND

These modules are essential for proper Business Partner data handling and distribution during migration.
Step 3: Synchronization Control for Master Data

Go to SPRO → Cross Application Components → SAP Business Partner → Master Data Synchronization → Synchronization Control →
Synchronization Object.
Step 4: Activate PPO Request for Platform Objects

Go to SPRO → Cross Application Components → SAP Business Partner → Master Data Synchronization → Synchronization Control →
Synchronization Control.

activate the PPO request for platform objects in the dialogue. This is essential for the handling of post-processing of Business Partner data
during the migration process.

Step 5: Activate Synchronization Options for ECC to S/4HANA Migration

Go to SPRO → Cross Application Components → SAP Business Partner → Master Data Synchronization → Synchronization Control →
Synchronization Control.

Activating these synchronization options ensures the correct mapping and transfer of customer and vendor data to the Business Partner (BP)
model in S/4HANA.
Step 6: Activate Assignment of Contact Person for Customer Integration

Go to SPRO → Cross Application Components → SAP Business Partner → Master Data Synchronization → Customer-Vendor Integration →
BP Settings → Setting for Customer Integration.

This ensures that contact person data is properly linked and integrated during the migration from ECC to S/4HANA.
Step 7: Assignment Department number for Contact Person ( ECC & S4 Hana)

(i) Take Department number from ECC

SPRO → Sales & Distribution → master data → BP → Contact person → define standard department

Copy data from here and maintain same in S4 Hana with below steps

(ii) Maintain department number in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → BP relationships → Contact persons → define departments →
blank → new entries → past the data

(iii) Assignment department number for Contact person

Go to assign department number for contact person → new entry

assign Department CVI of (Customer/ vendor) with Department (BP)

Step 8: Assignment Contact person Function

(i) Take Contact person function from ECC

SPRO → Sales & Distribution → master data → BP → Contact person → define contact Function → Copy records

example- 01- Executive bond

(ii) Maintain Contact person function in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → BP relationships → Contact persons → define functions → paste
copy data

(iii) Assignment Contact person function

SPRO → Cross application components → SAP BP → business partner → setting for customer integration → filed assignment for customer
integration → assign attribute → Contact person →assign function for contact person

assign Function (CVI) with Function (BP)

Step 9: Assign Authority of Contact Person

(i) Take Contact person authority from ECC

SPRO → Sales & Distribution → master data → BP → Contact person → define authority → Copy records

(ii) Maintain Contact person authority in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → BP relationships → Contact persons → define authority → paste
copy data

(iii) Assignment Contact person function

SPRO → Cross application components → SAP BP → business partner → BP relationship → Contact person → Define power of attorney →
new entries → paste

Step 10: Assign VIP Indicator of Contact Person

(i) Take VIP Indicator from ECC

SPRO → Sales & Distribution → master data → BP → Contact person → define VIP Indicator

(ii) Maintain VIP Indicator in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → BP relationships → Contact persons → define VIP entries → paste

(iii) Assignment Contact person function

SPRO → Cross application components → SAP BP → business partner → BP relationship → Contact person → assign VIP Indicator →
assign VIP Indicator of customer with BP

Step 11: Assign Marital status

(i) Take Marital status from ECC

SPRO → Personal management → Personal administration → Personal Data → Personal data → create marital status

(ii) Maintain marital status in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → persons → marital status → maintain marital status → paste
records

(iii) Assignment Contact person function

SPRO → Cross application components → SAP BP → business partner → persons → marital status → assign marital status → assign marital
status CVI with BP

Step 12: Assign Legal form to legal status

(i) Take legal status from ECC

SPRO → Sales & distribution → master data → BP → Customer → marketing → Define legal status
(ii) Maintain legal status in S4 Hana system

SPRO → Cross application components → SAP BP → business partner → organization → maintain legal status

(iii) Assignment legal status

SPRO → Cross application components → SAP BP → business partner → organization → assign legal status

Step 13: Assign payment cards

(i) Take payment cards from ECC

SPRO → Sales & distribution → Billing → payment cards → maintain cards type

(ii) Maintain payment cards in S4 Hana system

SPRO → Cross application components → payment cards→ basic settings→ maintain payment card type → maintain

(iii) Assignment payment cards

SPRO → Cross application components → payment cards→ basic settings→ assign payment card

Step 13: Assign customer industries

(i) Take customer industries from ECC

SPRO → Sales & distribution → master data → BP →customers → marketing → define industry sector for customer

(ii) Maintain customer industry in S4 Hana system

SPRO → Cross application components → SAP BP → BP →organization → maintain industry system & industries → new entry

(iii) Assignment Industry system

SPRO → Cross application components → SAP BP → BP →organization → assign industry system & industries → select "industry
system" → define outgoing industry mapping"

note: for vendor need to map incoming industry mapping

Step 13: Address determination

SPRO → Cross application components → SAP BP → Basic settings → address determination → Define address types → maintain

Step 14: Forms of address

Copy from ECC

SPRO → personal management → personal administration → personal data →create forms of address
Maintain in S4

SPRO → Cross application components → SAP BP → Basic settings → forms of address → maintain

Step 14: maintain Tax numbers

SPRO → Cross application components → SAP BP → Basic settings → tax number → maintain tax number category

Step 15: maintain Geo Code for countries

SPRO → SAP Net-weaver → general settings → Basic settings → set geo code → process geographical data for countries →

Steps for Customer to Business Partner Migration

1. Find Customer Account Group & Entries:

Access the KNA1 table to identify the Customer Account Group.

Count the number of customer entries in the table.

2. Document Account Group Details:

Record the Customer Account Assignment Group, Number Intervals, From and To Number Range, and External Indicator.

3. Configure BP Settings:

In S/4HANA, configure the BP Account Assignment Group, BP Number Range, From and To Number Range, and External
Indicator to align with the customer settings.

4. Post-Migration Comparison:

After migration, compare the number of entries in KNA1 with BUT000 (Business Partner Master) and VI_LINK tables to ensure data
consistency.

These steps ensure the proper migration and synchronization of customer data to the Business Partner model in S/4HANA.

Before diving into the migration process, lets understand the migration scenarios and the Business Partner (BP) approach.

3 Migration Scenarios for BP Data Consistency

Scenario 1 – Both Tables Updated (Status: OK):

If both BUT000 (Business Partner) and CVI_LINK (Customer-Vendor Integration) tables are updated, the status is considered OK, indicating
successful migration.

Scenario 2 – BUT000 Updated, CVI_LINK Not Updated (Status: OK):

If only BUT000 is updated but CVI_LINK is not, the status is still considered OK. In this case, run the report
ZCUSTOMER_LINK_CHECK_REPORT to ensure the issue is tracked and resolved.

Scenario 3 – BUT000 Not Updated (Status: NOT OK):

If BUT000 is not updated, regardless of the CVI_LINK update status, the migration status is NOT OK. This requires raising an issue with SAP
support for resolution.

These scenarios help in quickly identifying and resolving migration issues for customer and BP data synchronization.
BP APPROACH

1. BP = CUSTOMER 3. BP # CUSTOMER

BP ≠ VENDOR BP ≠ VENDOR

2. BP ≠ CUSTOMER 4. BP = CUSTOMER ( not in use)

BP = VENDOR BP = VENDOR

BP Table- BUT000

BP- Customer Link Information – CVI_CUST_LINK

LINK FIELD BETWEEN BUT000 & CVI_CUST_LINK IS “PARTNER_GUID” i.e. Business partner GUID.

Step 1: Extract Account Groups from KNA1 Table for Migration

To get the account groups that are actively in use (not all available account groups), follow these steps once Activation is done.

Go to SE16 → KNA1 → execute → Select Account group → Filter → F4 → get all the account group → Paste in Excel

For Account group number of entries (customers ) are 4 in the table.

Step 2: Document in Excel

CAG- Customer account group; NI- Number range interval

Now we need to create BP configurations to fill up the excel for BP information as shown.

Step 3: Configure BP in ECC System

BP Roles

SPRO → Cross application components → SAP Business Partner → Basic Setting → Business Partner Roles → Define BP roles

Standard BP Roles are :

FLCU00 - Company Code data. FLVN00- Vendor FI

FLCU01- Sales Area data. FLVN01 - Vendor Purchase

 Number Ranges & BP Groupings

SPRO → Cross application components → SAP Business Partner → Basic Setting → Number ranges & groupings → Define number ranges →
Intervals

Note : Validate customer number range to make similar entry and make BP as external number range to have same Customer and BP number.

Define groupings and number assignment

SAP Business Partner → Basic Setting → Filed groupings → Configure filed attribute for BP role → Configure filed attribute for each role
category

Control files in BP as mandatory or optional or suppress if required.

CVI mapping (Direction customer to BP)

SPRO → Cross application components → master data synchronization → Customer vendor integration → BP settings → Settings for
customer → integration →

BP grouping ZD01 created for Customer account group- JD02.

For accounted account group JD02 we have 4 entries. As of now BP has not been created so no entry in table- BUT000.
Execute Upgradation Check Report for Customer BP and CVI Configuration

To check for errors related to Customer BP Configuration or CVI Configuration, follow these steps:

1. Execute the Upgradation Check Report:

Go to Transaction SE38 or SA38 (ABAP Program Execution).

Enter the program name: /SDF/RC_START_CHECK (for the Upgradation Check Report).

2. Run the Report:

Execute the report. This will perform checks across various configurations and highlight any issues related to Customer to BP
migration or CVI configuration.

3. Review the Errors:

The report will display errors and inconsistencies that need to be resolved before migration. Pay particular attention to issues with
Customer to BP mapping and CVI Configuration.
We are getting some error related to Customer BP configuration or CVI configuration.
Analyze the Error:

Trying to execute Simplification Item Check report.

Report shows an error indicating that the BP role direction needs to be configured from Customer to BP.

Follow these steps to resolve it:

SPRO → Cross Application Components → Master data synchronization → Customer-Vendor Integration → Business Partner settings →
Settings for Customer Integration → Define BP role for direction Customer to BP
Assign account group to BP group.

SPRO → Cross Application Components → Master data synchronization → Customer-Vendor Integration → Business Partner settings →
Settings for Customer Integration → field assignment for customer integration → assign keys → Define number assignment for direction
Customer to BP

Re-run the check report, and if no issues are found, proceed with the migration steps.

Steps to Migrate Customer to Business Partner in Migration Cockpit

Access Migration Cockpit:

Go to Migration Cockpit (Transaction: MDS_LOAD_COCKPIT).

Select “customer – Business Partner” combination → right side → mention account group in “field name”, I in “Include”, EQ in “Option” account
group in “Lower limit” → Execute
Click on “Monitor” Queue → Register & activate queue → refresh it → get the status

Check the BUT000 table for BP group ZD01 and verify if there are 4 entries, matching the number of entries in KNA1.

Steps for Post Migration Configurations (S4 Hana Server)

1. Activate creation of Post processing orders

2. maintain synchronization object

3. Activate PPO request for platform object in dialog box

 4. Activate synchronization options

5. Activate contact person

6. Configure BP attributes

7. Go to customer number ranges and make it external.

i) Go to NT status and make current status blank. Further make number range as external

OR

ii) Close the existing number range with cutest NR status number range and create a new number range with remaining number range

example- 01 000001 100000 500 internal

01 000001 000500 500 internal

02 000501 100000 blank external

8. Go to BP number ranges (BUCF) and make this internal

9. BP configuration for direction BP to Customer

SPRO → Cross application component → master data synchronization → Customer vendor integration → BP Setting → Setting for customer
integration → Set BP role → Category direction BP to Customer → new entry → BP Roles

10. Number range assignment for Direction BP to Customer

SPRO → Cross application component → master data synchronization → Customer vendor integration → BP Setting → Setting for customer
integration → filed assignment for customer integration → Assign keys → define number assignment for direction BP to customer

Labels:

SAP Sales and Distribution

Tags:

Migration Process

Comments

‎2025 Jan 20 3:01 AM

Vignesh_Kumar_RV Explorer

Well compiled. Thanks @Kaushik_Samanta

 ‎2025 Jan 20 10:23 AM
Ishan1 Newcomer

CVI_Cockpit is missing. Cockpit is one stop shop for everything. Great efforts for writing document though.

‎2025 Jan 22 4:59 AM

sanju5016 Explorer

Great Compilation. Kudos.

‎2025 Jan 28 3:00 AM

Khasim_Sharief Discoverer

Great job, Kaushik! Well compiled

‎2025 Jan 28 1:14 PM

VyomakeshRacherla Newcomer

Informative !!Thank you

BR

Vyomakesh Racherla

‎2025 Mar 18 5:04 PM

bradybragg Product and Topic Expert

For an SAP customer using ECC as their HR system of record, is there direction to move to Cloud Employee Central as well as S4 Hana?
 3 weeks ago
pavankumar1127 Discoverer

Very informative and useful information !!Thank you.

Pavan Kumar M