SAP Community - SAP S/4HANA migration cockpit

SAP FIORI - MIGRATION COCKPIT - BOM -Item status not supported

2025-11-19T18:54:26.174000+01:00

HI,

I am using the SAP Fiori Migration Cockpit to upload BOMs. I am getting the error message "Item status not supported" (see attached screenshot). How can I solve this issue? When I create the BOM manually via CS01, everything works correctly. Could you please help me?

Value Mappings Not Applied During Simulation (LTMOM) - Direct Transfer ECC to S/4HANA

2025-11-23T15:39:15.122000+01:00

Problem Description: I'm working on a Direct Transfer scenario from SAP ECC to S/4HANA 2023 using Migration Cockpit with a custom migration object, but the value mappings are not being applied during simulation.

Environment Setup:

Source: SAP ECC
Target: S/4HANA 2023
DMIS component installed and RFC connection configured between systems
Custom migration object created using LTMOM with custom function module for data creation

Issue Details:
I have created value mappings for three fields to transform values between source and target systems:

Company Code (BUKRS) - Mapping: Z_MAP_BUKRS
House Bank (HBKID) - Mapping: Z_MAP_HBKID
Bank Account (HKTID) - Mapping: Z_MAP_HKTID

Current Configuration:

All three value mappings are properly defined in the migration object structure
Field mappings are configured with option "Fill field using a mapping, fixed value or source code rule"
Importing parameters are assigned correctly (e.g., IV_HBKID filled with source value)
The mappings appear in the "Using this API automatically fills these mapping value rules" section
Mapping tasks are successfully generated and show as "Done: 3" in the Migration Cockpit

Problem: During simulation, the migration object processes records using the original source values instead of the mapped target values.

For example:

Source company code: 0001
Mapped target company code: 1000
Expected behavior: Simulation should use company code 1000
Actual behavior: Simulation uses company code 0001

Screenshots Attached:

Migration object structure showing value mappings (Z_MAP_BUKRS, Z_MAP_HBKID, Z_MAP_HKTID)
Field mapping configuration for HBKID with importing parameter IV_HBKID
Target API settings showing Z_MAP_BUKRS in automatic mapping rules
Migration Cockpit monitoring showing mapping tasks completed but simulation errors

Question: What configuration am I missing to ensure value mappings are applied during the simulation phase in a custom migration object with Direct Transfer? Are there additional settings required in the custom function module or transfer step configuration?

Any guidance would be greatly appreciated!

Bulgaria EUR Transition_Material inventory balance Migration from old company code BG10 to new BG20

2025-11-24T14:17:59.571000+01:00

Hi All,

We are currently preparing for the Bulgaria EUR Transition and starting Mock 1 activities in our SAP S/4HANA Public Cloud Test System. As part of this exercise, we need to migrate the Material Inventory Balance from the source company code BG10 to the target company code BG20.

We request SAP’s official and detailed documentation/steps for performing the Material Inventory Balance migration using the SAP Data Migration Cockpit (Migrate Data Using Staging Tables).

Specifically, we need clarification on the following:

Step-by-step procedure to migrate Material Inventory Balance using the “Material Inventory Balance” migration object in Public Cloud.
Whether SAP provides any standard extract for inventory value (quantity + valuation amount) for Public Cloud.
Instructions for correctly populating the following staging templates delivered by SAP:
- S_MARA#FreeText_Mandatory.csv
- S_MARD#FreeText_Mandatory.csv
  Do these files need to be uploaded in sequence?
Any SAP-provided Bulgaria EUR Transition–specific migration guidelines for material stock.
Given the criticality of the EUR transition timeline, we request urgent guidance and the official SAP steps or documentation to ensure we follow the correct procedure.
Thank you for your support.
Adyasha Patra

How to populated the VAT registration number for Business Partner correctly?

2025-11-29T10:21:52.910000+01:00

Hello dear SAP S/4HANA experts,

As part of an SAP S/4HANA migration project, I am responsible for data migration. I am currently attempting to migrate customer master data as business partners into SAP S/4HANA using the Migration Cockpit (version 12.2.24) and the migration object “Customer.”

Unfortunately, I am unable to successfully migrate the VAT registration number.

After the migration of the customer master data, the Migration Cockpit displays the warning message: Customer ##1 is from an EU country/region; enter a VAT registration number and VAT Registration No.: Plausibility check failed.

During the validation or simulation of the customer master data, however, no warning message appears.

The most recent XML template contains four separate sheets related to VAT information.

I have tried various combinations that came to mind, but unfortunately without success. I would greatly appreciate any further suggestions.

My question is:

How exactly must the fields be populated so that the VAT registration number is migrated correctly?

Additionally:

Is there a way to deactivate the validation rule for "VAT registration no. plausibility check" either in Customizing or in the Migration Object Modeler (LTMOM)?

Data Migration Cockpit - VC Material variant

2025-12-04T10:51:32.438000+01:00

We are currently using the SAP Data Migration Cockpit (DMC) in S/4HANA to migrate Material Master data, including Variant Configuration (VC) for configurable materials.

We have encountered an issue when attempting to migrate Classic Variant Configuration (i.e., configurations that are not Advanced Variant Configuration - AVC).

The Technical Observation

Upon tracing the migration process, it appears the DMC migration object invokes the Function Module VCH_MATERIAL_CONFIG_CREATE. Inside this FM, we identified a hard-coded check or logic related to the processing mode:

The code seems to include a check that only permits the execution when the process mode (PROC_MODE) is set to 'A' (Advanced Configuration).

This effectively prevents the migration of any data related to Classic Variant Configuration (proc_mode = ' ') via the standard migration object, as the system seems to be designed to only allow AVC.

The Question for the Community

Has anyone else experienced this specific limitation when migrating materials with Classic VC using the standard SAP DMC migration object (e.g., Product or similar)?
What was your workaround or solution?
- Did you have to customize the migration object in LTMOM?
- Did you switch to a different loading technique (e.g., using a custom BAPI/FM that supports VCH)?
- Is there a specific SAP Note (KBA) that addresses the use of Classic VC within the DMC?

Any insights or recommended approaches from the community would be highly appreciated!

Thanks Giuseppe!

#Variant Configuration #Data Miration Cockpit #Classic VC

SAP DMC - Data Migration object becomes unusable to load in development system after TR release

2025-12-05T18:16:06.673000+01:00

Hi, In the SAP Data Migration Cockpit, a project is created with its migration objects, assigned to a package and transport, and then moved to Quality. However, once the transport is released, I am no longer able to use the migration object for loading data in the Development system. Is this expected behaviour? I would assume not.

In our current S/4HANA 2023 system, while the object remains in change mode and is assigned to an open transport, it is available for data loading in the Fiori Migrate Your Data app. But after the transport is released, the object status changes to Not Ready for Processing and all load-related options become greyed out.

This raises a concern — how are we expected to perform test loads in Development (for new requirements or on-demand testing) if the object becomes unusable after a transport release? These projects and objects were already created and moved to Quality before I joined, but the process of creating a project, adding objects, and assigning transports should behave consistently across environments.

Could you please advise what might be missing in our setup, or whether there is a configuration aspect we need to review? Any guidance would be much appreciated.

How to analyze error message inconsistent amounts F5 704 in Migration Cockpit?

2025-12-13T08:56:03.038000+01:00

Dear SAP S/4HANA Experts,

during the migration of customer open items using the migration object “FI – Accounts receivable open item”, one open item is not being migrated. Instead, the following error messages occur:

“Inconsistent amounts”
“Error in document: BKPFF $ CDACLNT275”

When I analyze the relevant open items in the SAP ERP source system using transaction FBL5N (Customer Line Items), document 6293930 contains two line items:

one line item with H Debit/Credit Ind. and a negative amount of -1,065.07 EUR
another line item with S Debit/Credit Ind. and a positive amount of 57.55 EUR

Both line items are listed identically in the XML template file as well as in the staging table.

However, only the line item with S Debit/Credit Ind. and the positive amount of 57.55 EUR is migrated into the SAP S/4HANA test system.

The source structure of the migration object “FI – Accounts receivable open item” does not contain a field for the Debit/Credit Ind.. Therefore, I assume that the Migration Cockpit derives the Debit/Credit Ind. of an open item solely based on the sign of the value in the field “Amount in doc curr.”. We are migrating the customer open items into an SAP S/4HANA test system in which no user exits, such as EXIT_SAPLV60B_002, EXIT_SAPLV60B_008, or similar enhancements, have been implemented.

At present, I am unable to clearly interpret the cause of these error messages from a functional perspective.

Could this be a misunderstanding on my side, or is this a limitation or issue within the Migration Cockpit?
What solution or recommended approach would you suggest in this case?

Kind regards,
Emal Rahman

Missing December Month P&L Data in Report app

2025-12-14T12:43:39.099000+01:00

Hi community,
I am facing very weird thing in my system; I migrated almost 20 company codes data in my QA system but now when I am trying to see that data in Balance Sheet/Income statement app I cannot see December month data of Income statement. I migrated 2023 and 2024 Historical data, but 2024 December data is not showing, but in migration project it can be seen that data is migrated.
Can anyone help me to rectify in this error/issue.

LTMOM - Debug "Select Data" Step for a Mig Object

2025-12-16T18:04:08.051000+01:00

I am using the Mig Object Fixed Asset (Incl. Balances). While I select the Data using Direct Transfer method from my source ECC system, it selects only 50% of the records out of 16600+ records in ANLA table.

SAP help says all ANLA records that dont have a Deactivation Date in them are automatically selected. however, I dont see that happening in my case. It seems to ignore a lot more than that. Any idea how I can debug the data selection step and find out what logic it is applying to filter out half of the records. While I see the option to debug in Simulation step, there is no way I could see to debug the earlier steps.

Note that the App Analyze Your Selection Process does not support the Fixed Asset Mig. Object.

Any pointers, please ?

Regards

@HenrikeGrtecke @Chris1973 @DonWilliams @N1kh1l

SAP S/4HANA Migration Cockpit What’s New in 2025?

2025-12-18T17:44:20.812000+01:00

SAP S/4HANA Migration Cockpit What’s New in 2025? Sequence Information View

Recommendation - Project Setup

Note: Please touch base with Basis or Development team to implement all required SAP correction notes prior to using the DMC tool for avoiding lot of errors and related to performance issues.

You can use the SAP Note Analyzer (transaction CNV_NA_MC) to check whether all the necessary SAP Notes for
SAP S/4HANA migration cockpit are installed. For more information, see SAP Note 3016862

How to implement the latest corrections released for Migration cockpit

SAP Fiori must be set up as prerequisite for the data migration approaches. For more information about the
SAP Fiori app Migrate Your Data, see:

SAP Fiori Apps Reference Library and search for the SAP Fiori app Migrate Your Data
• SAP Note 3039598

SAP Fiori Apps Reference Library

App ID: F3473 - Migrate Your Data - Migration Cockpit

App ID: F3280 - Data Migration Status

App ID: 7829 - Analyze Your Selection Process (This app is only relevant for the migration approach Migrate Data Directly from SAP System.)

Migration Cockpit (Transaction LTMC) - Deprecated

The app Migrate Your Data - Migration Cockpit is the successor of the Migration Cockpit (Transaction LTMC) app. The Migration Cockpit (transaction LTMC) app is deprecated and can no longer be used to migrate data to SAP S/4HANA. However, you can still view any projects that you created when using this app.

Refer the below links for more details

3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/SAP S/4HANA) - SAP for Me

INST_OP2023.pdf

SAP S/4HANA migration cockpit - Cookbook - Private Edition - 2023

INST_OP2025.pdf

SAP S/4HANA Migration Cockpit - Migrate your Data to SAP S/4HANA -2025

SAP S/4HANA Migration Cockpit - Migrate Your Data to SAP S/4HANA Cloud Public Edition

Latest Features in the SAP S/4HANA Migration Cockpit, released with 2025 FPS0

Migration Objects For a complete list of migration objects, see https://help.sap.com/S4_OP_MO

Situation Handling for Data Migration | SAP Help Portal

Video Library for Data Migration | SAP Help Portal

Available Migration Objects | SAP Help Portal

Data Migration Status | SAP Help Portal

Data Migration | SAP Help Portal

Migration of Open Items with VAT Codes into SAP S/4HANA with Migration Cockpit

2025-12-20T12:16:47.476000+01:00

Current Situation

As part of an SAP migration project from SAP ERP to SAP S/4HANA, open items for customers (AR), vendors (AP), and G/L accounts (balance sheet and P&L) are migrated using the Migration Cockpit with the staging table approach and XML template files.

During this process, it becomes apparent that some open items in the SAP ERP source system contain a VAT (tax) code. However, the migration of these VAT codes is technically limited or problematic, especially when no corresponding tax-relevant G/L line item exists.

Reasons for Not Migrating VAT Codes

The VAT code is currently not migrated for the following reasons:

Closed VAT reporting period in the source system
The VAT return for the closed period 12/20XX must be executed in the SAP ERP system, as only there all tax-relevant document line items for the final reporting period are fully available.
Technical restrictions of the Migration Cockpit
The Migration Cockpit (staging table approach) does not appear to support a consistent migration of VAT codes for open items when no tax-relevant G/L line item is transferred together with the customer or vendor line.

Error Message During Migration

When attempting to migrate open items with a VAT code, the following system message occurs:

“Tax code XX is not contained in any G/L account line item”
Message class: FF
Message number: 753

System Diagnosis

The document contains a customer or vendor line item with a VAT code, but no corresponding tax-relevant G/L line item.
Since tax line items are derived from the accounting document, the system considers this an inconsistent posting.

SAP further explains that such postings may lead to:

Cash discount bases being set to zero if not entered manually
Incorrect or incomplete tax recalculation during cash discount clearing
Tax reporting inconsistencies in the target system

Current Technical Workaround

By changing the message control in transaction OBA5, the error can be downgraded to a warning, allowing the open items to be migrated despite the inconsistency.

Open Question and Business Risk

This leads to the central question:

Can automatic tax correction during payment runs (including cash discount calculation) still be performed correctly in SAP S/4HANA if open items are migrated without a tax-relevant G/L line item or without the original VAT code?

If the VAT code is not migrated, this may cause functional limitations in SAP S/4HANA, especially in:

Payment runs for customers and vendors
Cash discount processing
Automatic tax corrections and tax reporting

Key Questions

What are the technically and functionally correct approaches to migrate open items with VAT codes from SAP ERP to SAP S/4HANA?
What options does the Migration Cockpit (staging table approach) offer for transferring VAT codes in open items?
What are the advantages and disadvantages of each approach
(e.g. migrating VAT codes vs. deliberately omitting them)?
What are the impacts on downstream processes, especially payment runs, cash discount handling, and tax adjustments in SAP S/4HANA?

Objective

The objective is to identify a technically sound, audit-compliant, and process-stable solution for migrating open items with VAT codes that ensures correct financial processing and tax handling in SAP S/4HANA.

Migrate Commodity Codes from ECC to S/4 Hana

2025-12-22T13:00:14.950000+01:00

Hello,

I need to migrate the commodity codes from the ECC system to S/4 Hana. Based on SAP Help page, it must be done via XPRA. So, we have imported the object V_T604 in a Transport Of Copies (ToC) and including the XPRA object in the ToC.

Data Migration in International Trade | SAP Help Portal

The Log for the importing is just with warnings, indicating that the object is redirected to CDS CLS_V_T604, but entries created in tables T604 and T604T. This is what I want, and, as far I know, the the program /SAPSLL/XPRA_1610_/MARC_STAWN will convert the data to the new tables /SAPSLL/CLSNR and /SAPSLL/CLSNRT.

But when I look for the entries in table T604 they are not created.

Why is this happening? What is wrong in the importing.

On the other hand, what is the other solution to migrate massively the commodity codes (near by 30 thousand), impossible to do it manually.

Thanks

How to Change the CSV Field Delimiter for a Migration Project?

2026-01-01T08:07:47.079000+01:00

Dear SAP S/4HANA-Experts,

When attempting to change the field delimiter in the Migration Cockpit under Project Settings → CSV File Options, the Migration Cockpit becomes unresponsive and the changes are not saved.

This may indicate a software bug; alternatively, there may be system settings that need to be configured and are currently unknown to me.

How can the field delimiter for a migration project be changed correctly in SAP S/4HANA, either via the Migration Cockpit or the Migration Object Modeler?

Is it possible to change the field delimiter for a migration project using the Migration Object Modeler?

with kind regards

replacement for TDMS

2026-01-25T08:28:13.890000+01:00

Hello Guru's

We migrated to S/4 HANA 2023. TDMS does not work anymore with S/4 HANA.

We are looking for an easy tool which can copy data from Production to non production systems.

Not entire data, only selective modules like SD or MM or FI.. especially Master data.

does the SAP migration cockpit is a good approach?. any one has implemented this?.

what other alternate tools available either from SAP or from 3rd party?.

Thanks Guru's

Sap upgrade

2026-01-28T17:46:07.586000+01:00

Hi everyone,

We are currently planning an SAP system upgrade and are discussing the landscape sequence. I have two specific questions regarding the methodology:

• System Independence: While I understand that DEV, QA, and PRD are upgraded individually, is it technically feasible (or advisable) to run them as completely independent projects with significant time gaps between them?

• Reverse Sequence Risks: What are the specific technical consequences if we were to upgrade the Development (DEV) system last? Specifically, I am concerned about:

• Handling SPDD/SPAU adjustments and how those would be transported if PRD is already upgraded.

• The impact on the transport directory and version mismatch errors (RC=8/12) when moving emergency fixes from a lower-version DEV to a higher-version PRD.

• Maintenance of custom code (Z-programs) during the "split-version" period.

Has anyone ever been forced into this "Reverse Sequence" due to business constraints? If so, how did you manage the landscape synchronization, or did you ultimately decide it was too high-risk?

Looking forward to your insights and any "lessons learned" from the field.

Following messages raised while executing migration of Fixed Assets - Postings

2026-02-06T14:13:42.158000+01:00

Following messages raised while executing migration of Fixed Assets - Postings

Error: Inform your system administrator (system error) (AA 481)
Warning: Sheet Cumulative Values; Crcy type 10: Specify the historical foreign currency values (FAA_POST 510)
Warning: Sheet Posted Values; Crcy type 10: Specify the historical foreign currency values (FAA_POST 510)
Warning: Sheet Cumulative Values; Crcy type 30: Specify the historical foreign currency values (FAA_POST 510)
Warning: Sheet Posted Values; Crcy type 30: Specify the historical foreign currency values (FAA_POST 510)
The same does not occur while simulating the migration.

Following messages raised while executing migration of Fixed Assets - Postings

2026-02-06T14:23:57.935000+01:00

Dear colleagues,

Following messages raised while executing migration of Fixed Assets - Postings

What is the practical use of Data controller tab in Supplier and Customer LTMC template?

2026-02-19T09:36:11.031000+01:00

In SAP Cloud Private edition - Migrate your data

What is the practical use of Data controller tab in Supplier and Customer LTMC template? In earlier version we did not have this tab

Mapping Tasks Button Disabled in S/4HANA Migration Cockpit

2026-02-20T11:10:14.285000+01:00

Dear Experts,

We are currently in the testing phase of our S/4HANA data migration using the Migration Cockpit.

In one of our projects, the “Mapping Tasks” button is enabled and working as expected. However, when we create a new project with same migration object and complete the “Prepare Mapping Tasks” step, the “Mapping Tasks” button becomes disabled afterward. Due to this, we are unable to access the mapping screen again to review or confirm the mapping values.

This behavior is not consistent across projects, as the button remains enabled in another testing project under similar conditions.

Could you please advise:

Under what conditions does the “Mapping Tasks” button become disabled?
Is there a configuration, status setting, or authorization that controls this?
How can we re-enable the button to review and confirm the mapping values?

Your guidance would be highly appreciated.

Fixed asset migration for French company

2026-03-03T11:02:12.439000+01:00

Hi All,

I would like to ask for support regarding fixed asset migration into SAP S4HANA cloud public edition via migration cockpit for a French company.

We are migrating an asset which was acquired in February 2020, depreciation start date is 01/02/2020.

Useful life 4 years:

Just to mention, we have 2 ledgers (0L as operational ledger and 2L as local ledger).

The master data was properly migrated. However we are having issues with the second part of migration - the fixed asset postings. In template for fixed asset-postings we have the posting key tab fulfilled as follows:

And the cumulative values tab:

With this file being simulated, we are receiving an error messages for 2L ledger (0L is successfully simulated):

-depreciation area 93 does not manage APC values

-acquisition value will become negative in depreciation area 93

I do not understand, how could the acquisition value become negative, if the acquisition cost is 848,00 and depreciation 847,99. There should be 1 cent left.

This is the fixed asset in system:

Legacy data transfer settings:

And migration key date is 31.12.2025

The 92 and 93 depreciation areas are specific for companies operating in FR. Is there something wrong with the set-up? What should we change to be able to migrate the asset?

Is there anyone who has experience with FR fixed asset migration?

Thanks in advance

Zuzana Gersiova