1. Home
  2. S/4HANA
  3. Migration Cockpit

SAP S/4HANA Migration Cockpit: moving FI data in without losing a cent

The tool every new SAP S/4HANA system uses for its first data load, with a complete FI cut-over you can run and balance yourself.

Read as

By · Updated

Overview

What the Migration Cockpit is, if you have never used it

A new SAP S/4HANA system starts empty. Before go-live someone has to load what the old system holds on the cut-over date: customers, suppliers, G/L accounts, unpaid invoices, fixed assets, stock and balances. The SAP S/4HANA Migration Cockpit is the tool SAP ships inside SAP S/4HANA for that first load. It offers a predefined migration object for each kind of data, a template or a direct connection to fill it, and the same checks the system runs when someone types the data in by hand.

This page walks through the cockpit’s process in the Migrate Your Data app, then follows a complete Financial Accounting (FI) cut-over, object by object. You can load one company yourself and prove that the books still balance, and the page ends with the transactions and apps, the errors people meet most and the questions they ask.

Runs on
  • SAP S/4HANA
  • SAP S/4HANA Cloud Private Edition
  • SAP S/4HANA Cloud Public Edition
Main codesF3473LTMOMFINS_MIG_CTRL_1

Use the User | Consultant switch at the top of the page to show or hide the technical layer: the settings, programs and tables behind each step.

Six things happen to every migration object

Whether the object is a bank or a fixed asset, the cockpit takes it through the same steps. Nothing reaches SAP S/4HANA before the last one.

  • 01 · F3473SelectPick the migration object: Customer, Fixed asset, FI - Accounts receivable open item.
  • 02 · XML · CSVFillUpload a template or select from SAP ERP; the data waits in the cockpit.
  • 03 · PreparePrepareThe cockpit reads the staging tables and raises the mapping tasks.
  • 04 · Value mappingMapOld values become new ones: company codes, payment terms, accounts.
  • 05 · SimulateSimulateThe standard checks run on every record, and errors come back per record.
  • 06 · MigrateMigrateBackground jobs create the data through SAP’s standard APIs.

  • Staging tables

    From any source

    Migrate Data Using Staging Tables. The cockpit creates staging tables for each object; you fill them from SAP’s XML or CSV templates or with your own tools, and the cockpit migrates them. Since SAP S/4HANA 2020 the old file approach lives inside this one.

    Source: SAP blog, Migrate Your Data part 1

  • Direct transfer

    From SAP ERP

    Migrate Data Directly from SAP System. Since release 1909 the cockpit can read an SAP ERP 6.0 system over an RFC connection, with the DMIS add-on installed in the source, and select the data by company code.

    Source: SAP product management, migration cockpit 1909

  • LTMC

    The old way

    Transaction LTMC was the Web Dynpro version of the cockpit, with its own file approach. It is deprecated: projects created in it stay in it, and new migrations run in the Migrate Your Data app.

    Source: SAP KBA 2988692, the two versions of the cockpit

Who does what in a migration

  • FI key usersOwn the numbersPrepare open items and balances from the old system and sign off the reconciliation.
  • ConsultantsSettings and mappingMigration key date, offset accounts, value mappings, simulation errors.
  • Data teamExtract, cleanse, fillTemplates or staging tables filled by tools; LTMOM changes.
  • BasisThe plumbingRFC and DMIS for direct transfer, background jobs, SAP Notes.
  • Master dataCustomers and suppliersTax numbers, bank details, payment terms, reconciliation accounts.
  • ControllersThe proofTrial balance against trial balance, clearing accounts at zero.

This page uses one example

Company code 1000 goes live on SAP S/4HANA on 1 January 2027

A soft-drink maker in São Paulo, the one that makes FG-500 lemon soda on the SAP PP page. Migration key date 31.12.2026. A year-end cut-over: the 2026 profit is already closed into equity in the old system, so only balance sheet values move. Amounts in BRL, examples only.

The process

From an empty project to data you can sign off

Nine steps in the Migrate Your Data app. Pick a step to see what happens, how it differs between staging tables and a direct transfer, and what it hands to the next step. The Consultant view adds what sits under the hood.

Step 1 of 9 · What happens

Create a migration project and choose the approach

In the Migrate Your Data app you create a project and decide where the data comes from: staging tables, which you fill from templates or your own tools, or a direct connection to an SAP ERP system. Typically the first project is built in a test system that is a copy of production, and the production project comes last.

Who: The data migration lead, with Basis for the connections.

Under the hood

Every project carries a mass transfer ID of three characters. Quality and production receive a project’s content only through a project with the same ID, and after an upgrade to SAP S/4HANA 2020 SAP requires the ID to start with X, Y or Z. Before the first project, the note analyzer CNV_NOTE_ANALYZER_MC_EXT brings in the latest cockpit corrections.

  • Mass transfer ID
  • CNV_NOTE_ANALYZER_MC_EXT
  • SAP_BR_CONFIG_EXPERT_DATA_MIG

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Choose Migrate Data Using Staging Tables. The staging tables are created in the local SAP S/4HANA database, or in a remote SAP HANA schema whose database connection exists before the project.

  • Local schema
  • Remote SAP HANA

With a direct transfer

Choose Migrate Data Directly from SAP System and the RFC connection to the source. When the DMIS add-on in the source answers, the cockpit lists its company codes for you to pick.

  • RFC
  • DMIS_2011_1

NextAn empty project with its approach fixed. Next, the migration objects.

Sources: SAP blog, Migrate Your Data part 1; SAP KBA 3081146; SAP blog, implementing the latest corrections; SAP Community, tips for the direct transfer.

Step 2 of 9 · What happens

Pick the migration objects the project needs

A migration object is SAP’s predefined package for one kind of data, such as Customer, G/L account or FI - Accounts receivable open item. Each one documents what is in scope, which objects must come before it and which app checks the result. In the cloud, the objects on offer follow the business processes active in the system.

Who: Functional consultants, each for their own area.

Under the hood

The cockpit uses the same APIs and validation checks as the standard applications, so a user needs authorization for Migrate Your Data and for the data itself. Objects with the suffix deprecated stay for old projects only; SAP KBA 2698032 explains the suffix.

  • SIF_OPEN_ITEM_AR
  • SIF_GL_BALANCE
  • SIF_FIXED_ASSET

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Opening an object creates its staging tables automatically, one for each source structure of the object.

  • /1LT/ tables

With a direct transfer

Objects select by the unit SAP defines for the scenario, for SAP ERP to SAP S/4HANA the company code. A finer selection is set in LTMOM.

  • Company code
  • LTMOM

NextA list of objects with their predecessors. Load them in that order.

Sources: SAP Learning, introducing the migration cockpit and migrating data; SAP blog, staging tables; SAP Community, migration cockpit FAQ.

Step 3 of 9 · What happens

Get the legacy data into the cockpit

With staging tables you download the object’s template, fill it and upload it, or load the staging tables straight from your extraction tools. With a direct transfer the cockpit reads the SAP ERP system itself. Either way, nothing has reached SAP S/4HANA yet.

Who: Data owners and the data migration team.

Under the hood

An XML or CSV file, and a zip of several files, may be up to 100 MB; on-premise the parameter icm/HTTP/max_request_size_KB raises the limit per XML file to 160 MB. A CSV file is one worksheet of the XML template. The table /1LT/DS_MAPPING tells you which staging table belongs to which source structure, useful for scripts that fill them.

  • /1LT/DS_MAPPING
  • icm/HTTP/max_request_size_KB

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Download the XML or CSV template, fill it and upload it, or fill the staging tables with SAP’s or third-party ETL tools. Paste values only: formatting and formulas can corrupt the XML structure.

  • XML
  • CSV

With a direct transfer

Start the selection: the cockpit reads the data of the chosen company codes over RFC. The selection can be repeated, and single items can be skipped.

  • Start selection

NextData sitting in the cockpit, untouched by SAP S/4HANA.

Sources: SAP blog, overcoming the file size limit; SAP KBAs 3691273, 3210687 and 2620588; SAP Community, migration cockpit FAQ.

Step 4 of 9 · What happens

Prepare: the cockpit reads what you loaded

For staging tables, Prepare reads the data you loaded and gets the object ready to run; it is where the mapping tasks first appear. Prepare and Simulate stay greyed out when the data never reached the staging tables.

Who: The data migration team.

Under the hood

Migration programs are generated automatically: nobody writes code for a standard object. SAP has a KBA on new mapping tasks that appear only during simulation, in which case Prepare runs again.

  • Prepare
  • CNV_DMC_SIN 331

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Run Prepare after each upload or after the tools have filled the tables.

  • Prepare

With a direct transfer

After the selection the data is already in the cockpit; the next step is the mapping tasks.

  • Selection done

NextData the cockpit can read, and mapping tasks waiting.

Sources: SAP blog, staging tables; SAP KBAs 3076466 and 3301684; Consilio, data migration with the cockpit.

Step 5 of 9 · What happens

Map the old values to SAP S/4HANA values

Mapping tasks translate the values of the old system into the ones the new system knows: company codes, payment terms, tax number categories, G/L accounts. Some are proposed and only need confirming; fixed values and control parameters need a decision.

Who: Functional consultants, with the data owners.

Under the hood

A target value that does not exist stops the mapping. “Mapping of Tax Number Category contains invalid values” means the category is missing in the system; SAP Note 775919 lists the standard ones.

  • Fixed value
  • Control parameter

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

The values to map come from the data loaded into the staging tables.

  • Mapping tasks

With a direct transfer

Value mapping works on the values selected from SAP ERP; one company code to one company code is the simplest case.

  • Value mapping

NextEvery mapping task confirmed, so the cockpit can call the SAP S/4HANA APIs.

Sources: SAP KBAs 3076466 and 3340256; SAP Community, tips for the direct transfer.

Step 6 of 9 · What happens

Simulate: the business checks without the load

Simulation runs the data through the standard checks of the business applications, so missing settings, blocked accounts and wrong values show up per record before the real load. When it ends with errors, you correct them and simulate again only the records that failed.

Who: Functional consultants and key users.

Under the hood

Simulation is not free of side effects in every object: SAP has a KBA where it consumes number ranges for Measuring Point. For FI, simulation is where a missing migration key date, a posting block or a tax error usually shows first.

  • All Instances with Errors
  • CNV_DMC_SIN 441
  • FF707

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Correct the data in the template or the staging table, prepare again, simulate again.

  • Simulate

With a direct transfer

Correct the data in the source system or the mapping, select again or simulate again.

  • Simulate

NextA list of records that will pass; the rest go back to their owners.

Sources: SAP KBAs 3783355, 3555410, 2768330 and 2883454; SAP blog, direct transfer top 5 FAQs.

Step 7 of 9 · What happens

Migrate: background jobs create the data

The migration creates master data and posts journal entries through SAP’s standard APIs, in background jobs. More data transfer jobs make large objects faster, but SAP warns against running several projects and objects in parallel when the jobs exceed what the system has.

Who: The data migration team, with Basis watching the jobs.

Under the hood

The G/L balance and open item objects post with BAPI_ACC_DOCUMENT_POST. In the public cloud a project has 8 background jobs by default and each migration object starts with 1; Job Management in the app changes both.

  • BAPI_ACC_DOCUMENT_POST
  • Job Management
  • SM37

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Data transfer jobs move the records from the staging tables into SAP S/4HANA; Job Management sets how many run for each object.

  • Job Management

With a direct transfer

SAP’s content maps the classic SAP ERP tables to the new model, BSEG to ACDOCA for example, which is why a direct transfer is meant for SAP ERP sources only.

  • BSEG → ACDOCA

NextData in SAP S/4HANA. Now prove it is right.

Sources: SAP KBAs 3580792, 3580750 and 2883454; SAP Community, migration cockpit FAQ.

Step 8 of 9 · What happens

Monitor, correct and run the failures again

Each object shows its records with their messages. Records in error are corrected and migrated again; records already migrated stay as they are, because the cockpit cannot delete or reverse what it migrated.

Who: The data migration team and the key users.

Under the hood

Undoing a load happens in the business applications: an FI journal entry is reversed like any other, a business partner is handled in the business partner apps. The application log keeps the detail behind a message.

  • FB08
  • F.80
  • SLG1

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Correct the data in the template or the staging table, then simulate and migrate the records with errors.

  • Correct

With a direct transfer

Correct the data in the source system or in the mapping, select again and migrate the records with errors.

  • Select again

NextEvery record either migrated or explained.

Source: SAP KBA 3686263, reversing migrated data.

Step 9 of 9 · What happens

Validate against the old system and close the door

Each object’s documentation names the transactions to check the result. For FI that means displaying the journal entries, comparing customer, supplier, asset, stock and G/L balances with the old system on the key date, and checking that the migration clearing accounts add up to zero. Then the legacy data transfer status goes to Completed.

Who: FI key users, controllers and auditors.

Under the hood

SAP’s post-processing lists FB01, FB02 and FB03 for open items and G/L balances; MMBE, MB5L, MB51 and MB52 for stock; FAGLB03 and S_PL0_86000030 for historical balances; DEFTAX_ITEM and RFUMSV50 for deferred tax.

  • FINS_MIG_CTRL_1
  • FAGLB03
  • MB5L

Programs, tables and the settings behind this step are in the Consultant view.

With staging tables

Both approaches end the same way: the proof is in the business apps, not in the cockpit.

  • FB03
  • F0996A

With a direct transfer

Both approaches end the same way: the proof is in the business apps, not in the cockpit.

  • FB03
  • F0996A

NextGo-live: the first real posting in SAP S/4HANA can happen.

Sources: SAP Help, migration objects for SAP S/4HANA; ERPlingo, message CNV_DMC_SIN 484.

Two approaches, side by side

The second half of both paths is the same: map, simulate, migrate through SAP’s standard APIs. What differs is how the data gets into the cockpit. Staging tables work for any source; a direct transfer only for an SAP ERP source.

Migrate Data Using Staging Tables

  1. XML · CSVSAP’s templates, or your own extraction and ETL tools
  2. /1LT/ tablesStaging tables, one per source structure, local or in a remote SAP HANA schema
  3. PrepareReads the staging tables and raises the mapping tasks
  4. MappingOld values to SAP S/4HANA values
  5. SimulateThe standard checks, without the load
  6. MigrateStandard APIs create the data, in background jobs

Migrate Data Directly from SAP System

  1. DMISAdd-on DMIS 2011 SP17 or higher in SAP ERP 6.0 or later
  2. RFCConnection from SAP S/4HANA to the source system
  3. SelectBy company code; a finer selection is set in LTMOM
  4. MappingValue mapping on the selected data
  5. SimulateThe standard checks, without the load
  6. MigrateStandard APIs create the data, in background jobs

Sources: SAP blogs, Migrate Your Data part 1 and staging tables; SAP product management, migration cockpit 1909; SAP Community, migration cockpit FAQ; SAP KBA 3580792.

FI cut-over

The FI cut-over, in the order that keeps the books balanced

Every FI object posts a real journal entry, and every one of them puts its other side on a migration clearing account. Load the subledgers first, the G/L balances last, and those clearing accounts tell you whether anything went missing. Pick a phase.

Phase 0 of 6

Settings that must exist before the first FI object

Set the migration key date of each company code in FINS_MIG_CTRL_1 and its status to Ongoing; without it the FI objects stop with CNV_DMC_SIN 441. Asset Accounting has its own legacy data transfer date and offsetting account, and that date must not be before the G/L migration date. Open the periods of the key date and make sure the offset accounts accept postings.

Migration objects and settings

  • FINS_MIG_CTRL_1
  • Define Transfer Date and Additional Parameters
  • Define Offsetting Account for Legacy Data Transfer

What it posts in company code 1000

Nothing is posted yet. These settings decide which date, which status and which offset account every later posting gets.

Check it with

  • FINS_MIG_CTRL_1
  • FAA_CMP_LDT
  • OB52
  • FS00

Sources: SAP Help, migration objects for SAP S/4HANA; SAP KBAs 2768330 and 3228609; SAP blog, fixed asset legacy data migration.

Phase 1 of 6

Exchange rates, accounts and the CO objects first

The open item objects list their predecessors: G/L account, supplier or customer, cost center, profit center and exchange rate. So the chart of accounts, the exchange rates of the key date and the CO objects the balances will carry come before any posting.

Migration objects and settings

  • Exchange rate
  • Bank
  • G/L account
  • Cost center
  • Profit center

What it posts in company code 1000

Master data only. A wrong reconciliation account set here will move every open item later.

Check it with

  • OB08
  • FS00
  • KS03
  • KE53

Sources: SAP Help, FI - Accounts payable open item; SAP KBA 2848568.

Phase 2 of 6

Customers and suppliers, as business partners

Customers and suppliers are business partners in SAP S/4HANA, created by the Customer and Supplier objects together with their company code data: reconciliation account, payment terms, tax numbers. The open items can only point to partners that already exist.

Migration objects and settings

  • Customer
  • Supplier

What it posts in company code 1000

Master data only. The tax number category mapping task is where Brazilian CNPJ and CPF categories must already exist.

Check it with

  • BP
  • SIF_CUSTOMER_2
  • SIF_VENDOR_2

Sources: SAP KBAs 2848224 and 3340256; SAP blog, loading customers with the cockpit.

Phase 3 of 6

Open items: one line per document

The cockpit posts the customer or supplier item and generates the offsetting line on an initial offset account. The sign at the start of the amount decides debit or credit. Open tax items must be settled before migration, deferred tax aside, and special G/L type W and noted items are out of scope.

Migration objects and settings

  • FI - Accounts receivable open item
  • FI - Accounts payable open item

What it posts in company code 1000

DebitCreditBRL
Customers (reconciliation)39914000 Initial FI-AR offset420,000.00
39915000 Initial FI-AP offsetSuppliers (reconciliation)310,000.00

Check it with

  • F0711
  • F0712
  • FBL5N
  • FBL1N
  • FB03

Sources: SAP Help, FI - Accounts receivable and payable open item; SAP KBA 2911854.

Phase 4 of 6

Fixed assets and stock, through their own subledgers

Fixed assets come in with acquisition value and accumulated depreciation, posted in Asset Accounting and the general ledger together, against the legacy data transfer offsetting account. Stock comes in with movement type 561, valued at the material master price, against the account for initial entry of stock balances.

Migration objects and settings

  • Fixed asset (incl. balances and transactions)
  • Fixed asset - Master data and Postings
  • Material inventory balance

What it posts in company code 1000

DebitCreditBRL
Fixed assets, acquisition valueAsset legacy offset1,500,000.00
Asset legacy offsetAccumulated depreciation600,000.00
Stock (BSX)Initial stock entry (GBB-BSA)260,000.00

Check it with

  • AW01N
  • S_ALR_87011990
  • MB52
  • MB5L

Sources: SAPinsider, asset migration; SAP Help, Material inventory balance and GBB account groupings; SAP KBA 2827574.

Phase 5 of 6

G/L balances: what no subledger carries

Bank, loans, equity and accruals go in with FI - G/L account balance and open/line item, one line per account and assignment, offset on 39916000. Fixed asset balances do not belong in this file. In the 1909 documentation open-item-managed accounts are out of scope for this object, so check your release: SAP also lists 39917000 as the offset for open item G/L postings.

Migration objects and settings

  • FI - G/L account balance and open/line item

What it posts in company code 1000

DebitCreditBRL
Bank39916000 Initial other GL offset180,000.00
39916000 Initial other GL offsetBank loan450,000.00
39916000 Initial other GL offsetEquity1,000,000.00

Check it with

  • F0707
  • FAGLB03
  • OKB9
  • FB03

Source: SAP Help, FI - G/L account balance and open/line item.

Phase 6 of 6

Reconcile, then set the status to Completed

The total of all migration clearing accounts must be zero, while each one keeps its own balance until it is cleared. Then compare the trial balance with the old one account by account, check customer, supplier, asset and stock totals, and set the status in FINS_MIG_CTRL_1 to Completed, which stops further transactional migration.

Migration objects and settings

  • Trial balance
  • Migration clearing accounts
  • Status Completed

What it posts in company code 1000

In company code 1000: 39914000 420,000.00 Cr, 39915000 310,000.00 Dr, 39916000 1,270,000.00 Dr, asset offset 900,000.00 Cr, stock offset 260,000.00 Cr. Total 0.00.

Check it with

  • F0996A
  • F0703
  • F0701
  • FINS_MIG_CTRL_1

Sources: SAP Help, FI - Accounts payable open item; SAP KBA 3757771; ERPlingo, message CNV_DMC_SIN 484.

Where each FI object posts

One line in a template becomes one journal entry: the item you loaded, and an offsetting line the cockpit generates. The offset account numbers are SAP’s best-practice ones; your chart of accounts may use its own.

Migration objectPosts toOffset account
FI - Accounts receivable open itemThe customer, on its reconciliation account39914000 Initial FI-AR offset
FI - Accounts payable open itemThe supplier, on its reconciliation account39915000 Initial FI-AP offset
FI - G/L account balance and open/line itemThe G/L account in the line39916000 Initial other GL offset39917000 for open item G/L postings
Fixed asset objectsAcquisition value and accumulated depreciation, in Asset Accounting and the G/L The account in Define Offsetting Account for Legacy Data Transfer
Material inventory balanceThe stock account (BSX), movement type 561 GBB with account grouping BSA, initial entry of stock balances
FI - Historical balanceClosed periods before the key date, for reporting only A dummy offset account kept for this purpose

Sources: SAP Help, migration objects for SAP S/4HANA (open items, G/L balances, historical balance, inventory); SAPinsider, asset migration with SAP S/4HANA Finance; SAP Help, GBB account groupings; SAP guide, FI historical balances.

Σ = 0

The total of all migration clearing accounts must be zero. That sentence sits in the post-processing of SAP’s open item objects, together with the instruction to balance them with the G/L balance object. Each offset account keeps its own balance; only their total must vanish, and SAP has a KBA about clearing them after the migration. Source: SAP KBA 3757771, clearing the initial offset accounts

Try it: the FI cut-over

Load company 1000 yourself and get the clearing accounts to zero

Five migration objects carry the 31.12.2026 trial balance into SAP S/4HANA. Switch them off and on to see what each one posts on the offset accounts; with all five in, the total must be zero. Then switch on the classic mistakes and see which ones the zero check catches, and which one it does not.

Five objects, one trial balance

Example: all five objects loaded, stock valued at a master price equal to the legacy value, no mistakes in the files.

Examples only. One company code, one ledger, local currency only, no taxes in the open items.

The facts behind it

  • Legacy trial balance on 31.12.2026: debits and credits of 2,360,000.00 each.
  • Customers 420,000.00 in three customers. Suppliers 310,000.00: invoices of 330,000.00 less a credit memo of 20,000.00.
  • Fixed assets 1,500,000.00 at acquisition value, 600,000.00 depreciated. Stock 260,000.00 of cans, cartons and FG-500 packs.
  • Bank 180,000.00, bank loan 450,000.00, equity 1,000,000.00, loaded with the G/L balance object.

The trial balance, old system against SAP S/4HANA

AccountLegacySAP S/4HANADifference
BankG/L balances180,000.00 Dr180,000.00 Dr0.00
CustomersAR open items420,000.00 Dr420,000.00 Dr0.00
StockInventory260,000.00 Dr260,000.00 Dr0.00
Fixed assets, acquisition valueFixed assets1,500,000.00 Dr1,500,000.00 Dr0.00
Accumulated depreciationFixed assets600,000.00 Cr600,000.00 Cr0.00
SuppliersAP open items310,000.00 Cr310,000.00 Cr0.00
Bank loanG/L balances450,000.00 Cr450,000.00 Cr0.00
EquityG/L balances1,000,000.00 Cr1,000,000.00 Cr0.00

Dr is debit, Cr is credit. Accounts not yet loaded show 0.00 in SAP S/4HANA.

Migration clearing accounts

39914000 Initial FI-AR offset420,000.00 Cr

39915000 Initial FI-AP offset310,000.00 Dr

39916000 Initial other GL offset1,270,000.00 Dr

AA Asset legacy offset900,000.00 Cr

BSA Initial stock entry260,000.00 Cr

Σ Total0.00

Zero, and every account matchesThe trial balance equals the old one and the offsets net to zero. Time to clear the offset accounts against each other and set the legacy data transfer status to Completed.

Journal entries the cockpit posted

ObjectDebitCreditBRL
FI - Accounts receivable open itemCustomers39914000420,000.00
FI - Accounts payable open item39915000Suppliers, two invoices330,000.00
FI - Accounts payable open itemSuppliers, credit memo3991500020,000.00
Fixed asset objectsFixed assets, acquisition valueAsset legacy offset1,500,000.00
Fixed asset objectsAsset legacy offsetAccumulated depreciation600,000.00
Material inventory balance (561)StockInitial stock entry (GBB-BSA)260,000.00
FI - G/L account balanceBank39916000180,000.00
FI - G/L account balance39916000Bank loan450,000.00
FI - G/L account balance39916000Equity1,000,000.00

Simplified: one line per account or partner, no CO assignments, no currencies besides BRL. The offsets follow SAP’s documented logic: the cockpit generates the offsetting line of each open item and G/L balance, assets post against the legacy data transfer offsetting account, stock posts with movement type 561 and is valued at the material master price. Sources: SAP Help, migration objects for SAP S/4HANA; SAPinsider, asset migration; SAP KBA 3757771.

Quick test

Which migration object carries it?

Choosing the wrong object is the quietest way to unbalance a migration. Guess the object, then open the card to check. Two of the answers surprise most FI people.

  • Invoices your customers have not paid yetShow the object
    FI - Accounts receivable open item

    One line per invoice. The cockpit posts the customer item and the offset on 39914000; it does not derive the payment terms from the customer master, so they belong in the file.

    Source: SAP KBA 3385525, payment terms in open items
  • Supplier invoices due next month, and one credit memoShow the object
    FI - Accounts payable open item

    The credit memo is an open item too, with the opposite sign. The API sets the invoice reference to V for credit memo lines.

    Source: SAP Help, migration objects for SAP S/4HANA
  • The bank account balance on 31 DecemberShow the object
    FI - G/L account balance and open/line item

    Surprise number one: the Bank account balance object only feeds Cash Management. It posts no journal entry, and the G/L reports will not show it.

    Source: SAP KBA 2804858, bank account balance and the G/L
  • Filling machines with five years of depreciationShow the object
    Fixed asset (incl. balances and transactions)

    Or, on-premise and private cloud from 2022, the pair Fixed asset - Master data and Fixed asset - Postings. Either way the values post in Asset Accounting and the G/L together.

    Source: SAP KBA 2827574, fixed asset migration objects
  • Cans, cartons and FG-500 packs in the warehouseShow the object
    Material inventory balance

    Movement type 561. Surprise number two: the stock is valued at the material master price, not at the value you type, unless you give an external amount for a standard-price material.

    Source: SAP Help, migration objects for SAP S/4HANA
  • Monthly balances of 2024 and 2025 for comparative reportsShow the object
    FI - Historical balance

    Closed periods before the migration key date, for reporting only: the documents cannot be displayed one by one.

    Source: SAP Help, migration objects for SAP S/4HANA
  • A receivable carried as a bill of exchangeShow the object
    None: post it manually

    Special G/L transactions of type W are not supported for mass migration, and SAP points to posting them in the app.

    Source: SAP KBA 2944536, special G/L type W
  • Exchange rates valid on the key dateShow the object
    Exchange rate

    A predecessor of the open item objects, so it loads before them.

    Source: SAP Help, migration objects for SAP S/4HANA
  • A supplier registered in August 2026 with letters in its CNPJShow the object
    Supplier, once the BR1 checks accept letters

    SAP Note 3583627 adjusts the BR1 checks for the alphanumeric CNPJ; without it the tax number field takes digits only and raises AR104.

    Source: SAP KBA 3756985, CNPJ accepts only numbers
  • Share capital and retained earningsShow the object
    FI - G/L account balance and open/line item

    No subledger carries equity, so it goes in as a G/L balance with its offset on 39916000.

    Source: SAP Help, migration objects for SAP S/4HANA
  • Purchase orders sent but not yet deliveredShow the object
    Purchase order (only open PO)

    An MM object, not an FI one: the open order is created, and its goods receipt and invoice happen in SAP S/4HANA.

    Source: SAP KBA 3833244, open purchase order object
  • Customer master data with CNPJ, address and payment termsShow the object
    Customer

    It creates the business partner with the customer role. Its Tax Number Category mapping task only accepts categories that exist in the system.

    Source: SAP KBA 3340256, Tax Number Category mapping

Load errors

Why did my load fail?

Each one has an SAP knowledge base article behind it. Guess the cause, then open the card to check.

  • Setup
  • Tax
  • Accounts
  • Open items and partners
  • Template
  • Direct transfer
  • CNV_DMC_SIN 441Missing settings of migration key date for company codeShow the cause
    Setup

    The FI posting objects need a migration key date for each company code, maintained in FINS_MIG_CTRL_1, Define Settings for Legacy Data Transfer.

    Source: SAP KBA 2768330, migration key date errors
  • In PreparationMigration key date still has status In PreparationShow the cause
    Setup

    In Preparation means the key date is still being clarified, and transactional data cannot be migrated. The initial load needs the status Ongoing.

    Source: ERPlingo, message CNV_DMC_SIN 484
  • FAA_CMP 061Legacy data transfer date must not be before G/L migration dateShow the cause
    Setup

    The Asset Accounting transfer date cannot be earlier than the migration key date of the general ledger. Align the two dates before the asset objects.

    Source: SAP KBA 3228609, FAA_CMP 061 transfer date
  • FF707Tax entered incorrect in a G/L balance lineShow the cause
    Tax

    The G/L balance object neither calculates nor migrates tax, so a tax code on a balance line runs into the tax check. Tax codes are not needed for this object.

    Source: SAP KBA 2883454, FF707 in G/L balances
  • Tax accountsDirect postings to tax accounts are not permittedShow the cause
    Tax

    Tax codes are not supported in the G/L balance object, and SAP’s KBA links this message to the rule that VAT line items cannot be migrated.

    Source: SAP KBA 3455154, direct postings to tax accounts
  • FINS_ACDOC_POST 105G/L account blocked for posting in company codeShow the cause
    Accounts

    The account carries a posting block in that company code. Offset accounts and balance accounts must accept postings while the load runs.

    Source: SAP KBA 3360397, FINS_ACDOC_POST 105
  • FINS_ACDOC_POST 133House bank is not assigned to G/L accountShow the cause
    Accounts

    A bank G/L account line in the balance file needs the house bank the account belongs to.

    Source: SAP KBA 3592867, house bank in G/L balances
  • Type WSpecial G/L transactions of type W are not supportedShow the cause
    Open items and partners

    Bills of exchange cannot be mass-migrated with the open item objects; they are posted manually.

    Source: SAP KBA 2944536, special G/L type W
  • FF805Tax statement item missing for tax codeShow the cause
    Open items and partners

    Raised for open items with a special G/L indicator, such as down payments, that carry a tax code.

    Source: SAP KBA 3413446, FF805 with special G/L
  • 100 MBUpload canceled. Make sure each file is smaller than 100 megabytesShow the cause
    Template

    The default limit per XML file. Split the file or zip several; in the public cloud from 2602 each XML inside a zip may reach 400 MB, with the zip itself at 100 MB.

    Source: SAP KBA 3691273, file size limits, public cloud
  • CNV_PE_GET_T001_INFOFailed to read company codes from source systemShow the cause
    Direct transfer

    The function module the cockpit calls in the SAP ERP source is missing: the DMIS add-on is not installed or not current there.

    Source: SAP KBA 3142703, reading source company codes
  • MappingMapping of Tax Number Category contains invalid valuesShow the cause
    Open items and partners

    The customer or supplier file uses a tax number category the system does not have. SAP Note 775919 lists the standard categories to add.

    Source: SAP KBA 3340256, Tax Number Category mapping

Speak migration

The codes and numbers you will see on the way

The numbers and codes that come up in every migration meeting, from the offset accounts to the limits that end up in the cut-over plan.

SAP’s best-practice numbers; your chart of accounts may use its own. What never changes: after the last object their total must be zero.

The cockpit picks them from the sign at the start of the amount; you do not type them.

Set per company code in FINS_MIG_CTRL_1 together with the migration key date. SAP documents it for all financial posting objects except the fixed asset object, which follows Asset Accounting’s own transfer date.

The IDs you meet in SAP KBAs and logs; the app shows the object names.

Closed periods before the migration key date, posted for reporting. Its own numbers and its own limits.

The numbers that end up in cut-over plans.

  • 39914000Initial FI-AR offsetThe other side of every customer open item.
  • 39915000Initial FI-AP offsetThe other side of every supplier open item.
  • 39916000Initial other GL offsetThe other side of the G/L balances.
  • 39917000Initial other open item GL offsetThe other side of open item G/L postings.
  • AAAsset legacy offsetSet in Define Offsetting Account for Legacy Data Transfer; a balance sheet account kept for this purpose.
  • BSAInitial entry of stockGBB with account grouping BSA, the offset of movement type 561.
  • 31 · 40Supplier, negative amountCredit on the supplier with key 31, debit on the offset with 40: an invoice.
  • 21 · 50Supplier, positive amountDebit on the supplier with 21, credit on the offset with 50: a credit memo.
  • 40 · 50G/L, positive amountDebit on the G/L account with 40, credit on the offset with 50.
  • 50 · 40G/L, negative amountCredit on the G/L account with 50, debit on the offset with 40.
  • 1In PreparationThe key date is still being clarified; transactional data cannot be migrated.
  • 2OngoingRequired for the initial data transfer.
  • 3CompletedThe transfer is over; no more transactional migration.
  • SIF_OPEN_ITEM_ARFI - Accounts receivable open itemOlder releases: SIF_AR_OPEN_ITEM.
  • SIF_OPEN_ITEM_APFI - Accounts payable open itemOlder releases: SIF_AP_OPEN_ITEM.
  • SIF_GL_BALANCEFI - G/L account balance and open/line itemOlder releases: SIF_GL_BALANCES.
  • SIF_FI_HIST_BAL3FI - Historical balanceEarlier versions SIF_HIST_BALANCE and SIF_FI_HIST_BAL2.
  • SIF_FIXED_ASSETFixed asset (incl. balances)On-premise since 1610.
  • SIF_FIXED_ASST_MFixed asset - Master dataOn-premise and private cloud from 2022.
  • SIF_FIXED_ASS_P2Fixed asset - PostingsOn-premise and private cloud from 2022.
  • SIF_CUSTOMER_2CustomerBusiness partner with the customer role.
  • SIF_VENDOR_2SupplierBusiness partner with the supplier role.
  • SIF_GL_ACCOUNT_3G/L accountEarlier versions SIF_GL_ACCOUNT and SIF_GL_ACCOUNT_2.
  • BCFBalance carry forwardOne of the two upload styles.
  • NPRNext period reverseThe other style: each period is reversed automatically in the next.
  • DHGDocument numbersInternal numbers follow the pattern DHG0000001.
  • DHRReversal numbersThe automatic reversals follow DHR0000001.
  • 9Years of period movementThe import method Period movement reaches 9 years back; for older years, use Period balance.
  • 100MB per filePer XML or CSV file, and per zip file.
  • 160MB on-premisePer XML file after raising icm/HTTP/max_request_size_KB.
  • 400MB inside a zipPer XML file in a zip, public cloud from 2602.
  • XYZMass transfer IDMust start with X, Y or Z in SAP S/4HANA 2020 and later.
  • 8Jobs per projectDefault in the public cloud.
  • 1Job per objectDefault for each migration object until you raise it.

Sources: SAP Help, migration objects for SAP S/4HANA; SAPinsider, asset migration; SAP Help, GBB account groupings.

Sources: SAP Help, FI - Accounts payable open item and FI - G/L account balance; SAP KBA 3388709.

Sources: SAP Help, FI - Accounts payable open item; ERPlingo, message CNV_DMC_SIN 484.

Sources: SAP KBAs 2853964, 2827574, 2848224 and 2848568; SAP blog, getting started on-premise.

Sources: SAP Help, FI - Historical balance; SAP KBA 3026368.

Sources: SAP KBAs 3691273, 3081146 and 3580792; SAP blog, overcoming the file size limit.

LTMC · F3473 · LTMOM

Three names, three jobs. LTMC is the old Web Dynpro cockpit, kept for the projects created in it. F3473, Migrate Your Data, is where migrations run since SAP S/4HANA 2020 and SAP S/4HANA Cloud 2008. LTMOM, the migration object modeler, is where you change the objects themselves: extra fields, rules and the selection. Source: SAP KBA 2988692, the two versions of the cockpit

Reference

The transactions, apps and tables of a migration, by module

The cockpit itself, the settings FI needs before the load and the apps that prove the result afterwards. Filter by module, then by audience; Start here shows the ones worth bookmarking. The last column says where each one runs. Type a code or a word to search all of them.

Code or appModuleWhat it doesWho opens itWhere it runs
F3473Cockpit · CA-LT-MCMigrate Your Data: create projects, upload or select data, map, simulate, migrate and monitor.Fiori appS/4HANA
LTMCCockpit · CA-LT-MCThe Web Dynpro cockpit used up to SAP S/4HANA 2020; its projects open only there.UserUp to S/4HANA 2020
LTMOMCockpit · CA-LT-MCMigration object modeler: add fields, change rules and the selection, create your own objects.ConsultantS/4HANA
Model Your Migration ObjectsCockpit · CA-LT-MCThe object modeler as an app, for staging tables in the public cloud.Fiori appPublic Cloud
CNV_NOTE_ANALYZER_MC_EXTCockpit · CA-LTNote analyzer: finds and implements the latest cockpit corrections (SAP Note 3016862).ProgramS/4HANA
CNV_NA_MCCockpit · CA-LTTransaction that starts the same note analyzer.ConsultantS/4HANA
/LTB/MC_PROJ_Q2PCockpit · CA-LT-MCExports and imports a staging project between systems by mass transfer ID.ProgramS/4HANA
/1LT/DS_MAPPINGCockpit · CA-LT-MCWhich staging table belongs to which object and source structure, since 1809 FPS0.TableS/4HANA
/LTB/MIG_MC_ODATA_SRVCockpit · CA-LT-MCOData service behind the Migrate Your Data app, activated in the gateway.ConsultantS/4HANA
SAP_BR_CONFIG_EXPERT_DATA_MIGCockpit · RolesBusiness role for the Migrate Your Data app.ConsultantS/4HANA
SAP_CA_DMC_MC_DEVELOPERCockpit · RolesRole for the migration object modeler, LTMOM.ConsultantS/4HANA
SAP_CA_DMC_MC_USERCockpit · RolesRole to transfer data with the cockpit, from the LTMC days.ConsultantUp to S/4HANA 2020
LSMWCockpit · BC-SRV-DXLegacy System Migration Workbench: on the simplification list for SAP S/4HANA (SAP Note 2287723).ConsultantECC and S/4HANA
SLG1Basis · BC-SRVApplication log: the detail behind a cockpit message.ConsultantECC and S/4HANA
SM37Basis · BC-CCMJob overview: the data transfer jobs of a running migration.ConsultantECC and S/4HANA
STMSBasis · BC-CTSTransports: staging projects and LTMOM changes move by transport from SAP S/4HANA 2021.ConsultantECC and S/4HANA
SE16NBasis · BC-DWBTable display: staging tables, FQM_FLOW and the like.ConsultantECC and S/4HANA
DMIS_2011_1Basis · Source systemAdd-on in the SAP ERP source for direct transfer, SP17 or higher.BasisSource SAP ERP
SAP_DMIS_OBT_MASTERBasis · Source systemRole for the RFC user in the source system.BasisSource SAP ERP
CNV_PE_GET_T001_INFOBasis · Source systemFunction module the cockpit calls to read the source company codes.BasisSource SAP ERP
FINS_MIG_CTRL_1FI-GL · Legacy data transferDefine Settings for Legacy Data Transfer: migration key date and status per company code.ConsultantS/4HANA
OB52FI-GL · PeriodsOpen the posting periods of the migration key date.ConsultantECC and S/4HANA
FS00FI-GL · Master dataG/L account master: reconciliation accounts, posting blocks, open item management.ConsultantECC and S/4HANA
OKB9FI-GL · CO assignmentDefault account assignment the G/L balance object can take its CO fields from.ConsultantECC and S/4HANA
OB08FI-GL · CurrenciesExchange rates: check what the Exchange rate object loaded.UserECC and S/4HANA
FB03FI-GL · DocumentsDisplay a migrated journal entry; part of SAP’s post-processing for the FI objects.UserECC and S/4HANA
FB02FI-GL · DocumentsChange a migrated document, also in SAP’s post-processing list.UserECC and S/4HANA
FB08FI-GL · DocumentsReverse one wrongly migrated document.UserECC and S/4HANA
F.80FI-GL · DocumentsMass reversal of documents.UserECC and S/4HANA
FAGLB03FI-GL · BalancesG/L balances per period; also SAP’s check for historical balances.UserECC and S/4HANA
F0707FI-GL · BalancesDisplay G/L Account Balances, the app for FAGLB03 and FS10N.Fiori appS/4HANA
F0996AFI-GL · BalancesTrial Balance: compare it with the old trial balance.Fiori appS/4HANA
F0706FI-GL · Line itemsDisplay G/L Account Line Items.Fiori appS/4HANA
FBL3NFI-GL · Line itemsG/L account line items in SAP GUI.UserECC and S/4HANA
S_PL0_86000030FI-GL · ReportsFinancial statement report SAP names to check FI - Historical balance.UserS/4HANA
RFUMSV50FI-GL · TaxDeferred tax transfer; SAP’s check after migrating deferred tax.ProgramECC and S/4HANA
DEFTAX_ITEMFI-GL · TaxDeferred tax items written by the open item objects.TableECC and S/4HANA
ACDOCAFI-GL · Universal JournalWhere every migrated journal entry lands.TableS/4HANA
BAPI_ACC_DOCUMENT_POSTFI-GL · APIThe posting API behind the G/L balance and open item objects.ConsultantECC and S/4HANA
FQM_FLOWFI-GL · Cash managementCash flows: SAP’s check for the Bank account balance object.TableS/4HANA
FCLM_BAM_AMDFI-GL · Cash managementBank account master data, with the technical ID the bank balance template asks for.TableS/4HANA
F0711FI-AR/AP · FI-ARManage Customer Line Items: the migrated customer items.Fiori appS/4HANA
F0712FI-AR/AP · FI-APManage Supplier Line Items: the migrated supplier items.Fiori appS/4HANA
F0703FI-AR/AP · FI-ARDisplay Customer Balances.Fiori appS/4HANA
F0701FI-AR/AP · FI-APDisplay Supplier Balances.Fiori appS/4HANA
FBL5NFI-AR/AP · FI-ARCustomer line items in SAP GUI.UserECC and S/4HANA
FBL1NFI-AR/AP · FI-APSupplier line items in SAP GUI.UserECC and S/4HANA
FD10NFI-AR/AP · FI-ARCustomer balances in SAP GUI.UserECC and S/4HANA
FK10NFI-AR/AP · FI-APSupplier balances in SAP GUI.UserECC and S/4HANA
BPMaster data · LO-MD-BPBusiness partner: customers and suppliers after the load.UserS/4HANA
OY17Master data · Country checksCountry-specific checks for tax numbers, relevant for the alphanumeric CNPJ.ConsultantECC and S/4HANA
KS03Master data · CO-OMDisplay a migrated cost center.UserECC and S/4HANA
KE53Master data · EC-PCADisplay a migrated profit center.UserECC and S/4HANA
FI03Master data · BanksDisplay a migrated bank.UserECC and S/4HANA
FAA_CMP_LDTFI-AA · Legacy data transferLegacy data transfer settings in Asset Accounting: transfer date and segment.ConsultantS/4HANA
AS91FI-AA · Legacy data transferCreate a legacy asset by hand.UserECC and S/4HANA
ABLDTFI-AA · Legacy data transferEnter legacy transfer values; posts to Asset Accounting and the G/L at the same time.UserS/4HANA
AS100FI-AA · Legacy data transferLegacy asset transfer from a spreadsheet, still available.UserECC and S/4HANA
AW01NFI-AA · ReportsAsset Explorer: values per asset and depreciation area after the load.UserECC and S/4HANA
S_ALR_87011990FI-AA · ReportsAsset history sheet: compare it with the legacy asset register.UserECC and S/4HANA
AR01FI-AA · ReportsAsset balances.UserECC and S/4HANA
MMBEMM · MM-IMStock overview after Material inventory balance.UserECC and S/4HANA
MB52MM · MM-IMWarehouse stocks.UserECC and S/4HANA
MB51MM · MM-IMMaterial document list: the 561 documents of the load.UserECC and S/4HANA
MB5LMM · MM-IMStock values and balances: compare with the G/L stock accounts.UserECC and S/4HANA
OBYCMM · MM-IVAccount determination: GBB with grouping BSA is the offset of movement type 561.ConsultantECC and S/4HANA

Cross-checked with SAP Help’s migration object documentation, SAP KBAs and SAP blogs; Fiori app IDs from SAP KBAs, Michael Management and SAPSTACK. Projects can hide transactions or rename apps, so check your own system before writing them into a cut-over plan.

Then and now

What changed since the first Migration Cockpit

The idea never changed: predefined objects, standard APIs, simulate before you load. Almost everything around it did, from the screen you work in to how a project reaches production. Many blog posts and templates on the internet still describe the old way.

  • The screen you work in

    BeforeLTMC, a Web Dynpro application.

    NowThe Fiori app Migrate Your Data (F3473), from SAP S/4HANA 2020 and SAP S/4HANA Cloud 2008.

    Projects created in LTMC cannot be opened in the new app; LTMC itself is deprecated for new migrations.

    Source: SAP blog, LTMC decommissioned or replaced

  • Files

    BeforeA file approach of its own, next to staging tables.

    NowFiles are one way to fill staging tables, and one project can combine both.

    Each source structure of an object has its own staging table.

    Source: SAP blog, Migrate Your Data part 1

  • Staging tables

    BeforeAdded in on-premise 1709 FPS02 and SAP S/4HANA Cloud 1905.

    NowThe standard approach for any source, in the local database or a remote SAP HANA schema.

    Besides the templates, SAP’s or third-party ETL tools can fill the tables directly (SAP KBA 3210687).

    Source: SAP PRESS, data migration to SAP S/4HANA (sample)

  • SAP ERP as a source

    BeforeExtract to files, then upload.

    NowDirect transfer over RFC since 1909, from SAP ERP 6.0 with the DMIS add-on; in the public cloud since 2402.

    Not meant for SAP S/4HANA to SAP S/4HANA: mappings such as BSEG to ACDOCA do not apply there.

    Source: SAP Community, migration cockpit FAQ

  • CSV templates

    BeforeXML templates in Excel’s XML spreadsheet format.

    NowCSV files as well, each one a worksheet of the XML template.

    The same 100 MB limit applies.

    Source: SAP KBA 3210687, CSV templates

  • Getting a project to production

    BeforeExport and import between systems, matched by mass transfer ID.

    NowTransport of staging projects and LTMOM changes from SAP S/4HANA 2021, on-premise.

    Quality and production only execute projects. The public cloud has no transport for staging projects: the project is created again.

    Source: SAP Community, the transport concept

  • Fixed assets

    BeforeOne object, Fixed asset (incl. balances), on-premise since 1610.

    NowSeparate objects for master data and postings, on-premise and private cloud from 2022.

    With universal parallel accounting, asset postings are ledger-specific.

    Source: SAP KBA 2827574, fixed asset migration objects

  • Asset values and the G/L

    BeforeIn SAP ERP, AS91 wrote values to the subledger tables and the G/L was posted separately.

    NowTakeover values are posted against a transfer G/L account, as one document for both.

    The account comes from Define Offsetting Account for Legacy Data Transfer.

    Source: SAPinsider, asset migration with SAP S/4HANA Finance

  • Changing objects

    BeforeLTMOM, on-premise only.

    NowLTMOM on-premise and private cloud; Model Your Migration Objects in the public cloud.

    Custom fields from in-app extensibility appear in the templates automatically for objects that support them.

    Source: SAP Learning, extending migration objects

  • LSMW

    BeforeThe classic tool for legacy data, with recordings that could create and change data.

    NowStill in the system, and on the simplification list for SAP S/4HANA.

    SAP’s comparison of migration tools refers to SAP Note 2287723 for LSMW in SAP S/4HANA.

    Source: SAP, data migration tools compared

  • File size

    Before100 MB per XML file and per zip.

    NowPublic cloud 2602: up to 400 MB per XML inside a zip; the zip stays at 100 MB.

    On-premise, 160 MB per file with icm/HTTP/max_request_size_KB.

    Source: SAP KBA 3691273, file size limits, public cloud

  • Changing data after go-live

    BeforeLSMW could also change existing data, through recordings.

    NowThe cockpit is for the initial load; changes go to the maintenance and mass processing apps.

    “Extend” objects add new organizational levels to existing records, such as a customer in a new company code.

    Source: SAP Community, migration cockpit FAQ

Brazil

Going live in Brazil on 1 January 2027

A cut-over on 31 December 2026 lands on two changes at once: the new CNPJ format, already in use, and the first day of CBS. Neither changes how the cockpit works, but both change what has to be ready before the first load.

  • CNPJ · BR1

    Suppliers with letters in their CNPJ

    The Receita Federal issued the first alphanumeric CNPJ on 31 July 2026, for new registrations only; old numbers stay valid. A supplier opened since then can fail the Supplier object with AR104, the tax number accepting digits only, until SAP Note 3583627 adjusts the BR1 checks.

    Source: SAP KBAs 3736153 and 3756985Source: Barbieri Advogados, alphanumeric CNPJ
  • PIS · COFINS · CBS

    Taxes travel as balances, not as lines

    The cockpit does not migrate VAT line items: open tax items must be settled before the load, deferred tax aside. Recoverable and payable PIS, Cofins, ICMS and IPI on 31.12.2026 therefore move as balances, never as tax lines, and the first CBS document of 2027 is posted in SAP S/4HANA, not migrated.

    Source: SAP KBA 2911854, VAT line itemsSource: Mattos Filho, CBS in 2027
  • IRRF · CSRF · ISS

    Withholding tax rides along with the open item

    Withholding tax items are among the supported features of the payables and receivables open item objects, next to the header, the partner item and the currency item. A Brazilian supplier invoice with tax still to be withheld at payment can migrate with its withholding data instead of losing it.

    Source: SAP Help, FI - Accounts payable open item

Documented, but little known

18 tips most people learn too late

Each tip comes from SAP Help, an SAP KBA, an SAP blog or the SAP Community, linked under the tip.

  • 01Key users

    Paste values only

    Paste into the template with Values only: formatting and formulas can corrupt the XML structure and break the import. And read the template’s Introduction sheet first; SAP puts its instructions there.

    • XML
    • Introduction
    Source: SAP KBA 2620588, using the migration templates
  • 02Key users

    One line per document

    The open item objects take one partner line per document and generate the offset themselves; several supplier lines in one document are out of scope.

    • SIF_OPEN_ITEM_AP
    Source: SAP KBA 3544356, out of scope in AP open items
  • 03Key users

    The sign is the posting key

    A minus at the start of the amount makes a supplier item a credit with key 31, a plus makes it a debit with key 21. A credit memo typed with the wrong sign doubles the error.

    • 31
    • 21
    Source: SAP Help, migration objects for SAP S/4HANA
  • 04Key users

    Fill in the payment terms

    The open item objects do not take the payment terms from the customer or supplier master, so an empty field means no terms on the item.

    • ZTERM
    Source: SAP KBA 3385525, payment terms in open items
  • 05Key users

    A payment block can appear on its own

    A default payment block on the payment term reaches the migrated item even if the template leaves the field empty.

    • ZLSPR
    Source: SAP Help, migration objects for SAP S/4HANA
  • 06Key users

    Let the system translate currencies

    Leave the second local currency and the group currency empty and the system calculates them; the date of the rate follows the company code’s foreign currency translation setting.

    • OB08
    Source: SAP Help, migration objects for SAP S/4HANA
  • 07Key users

    Clear before you migrate

    SAP’s documentation of the G/L balance object recommends clearing as many open items as possible before the migration: fewer items, fewer chances to be wrong.

    • F-03
    Source: SAP Help, migration objects for SAP S/4HANA
  • 08Consultants

    Ongoing for the load, Completed after

    FINS_MIG_CTRL_1 holds the migration key date and the status. In Preparation blocks transactional data, Ongoing lets it in, Completed closes the door.

    • FINS_MIG_CTRL_1
    Source: ERPlingo, message CNV_DMC_SIN 484
  • 09Consultants

    Align the asset date with the G/L date

    The Asset Accounting transfer date may not be before the G/L migration key date; set both together.

    • FAA_CMP_LDT
    • FAA_CMP 061
    Source: SAP KBA 3228609, FAA_CMP 061 transfer date
  • 10Consultants

    OKB9 can fill the CO fields

    CO assignments of G/L balance lines can come from the template or from the default account assignment.

    • OKB9
    Source: SAP Help, migration objects for SAP S/4HANA
  • 11Consultants

    Know the duplicate check

    G/L balances are checked for duplicates on company code, ledger group, reference document number, line item number and G/L account; open items on company code, reference, line item and partner.

    • XBLNR
    Source: SAP Help, migration objects for SAP S/4HANA
  • 12Consultants

    Deferred tax has its own rules

    Deferred tax migrates only for invoices, debit memos and credit memos, with tax signs opposite to the partner item. Check it in DEFTAX_ITEM and with RFUMSV50.

    • DEFTAX_ITEM
    • RFUMSV50
    Source: SAP Help, migration objects for SAP S/4HANA
  • 13Consultants

    Run the note analyzer first

    SAP keeps the cockpit corrections behind SAP Note 3016862 and the report CNV_NOTE_ANALYZER_MC_EXT; run it before the first mock load and again before the cut-over.

    • CNV_NOTE_ANALYZER_MC_EXT
    Source: SAP blog, implementing the latest corrections
  • 14Other teams

    Find staging tables by name

    The table /1LT/DS_MAPPING lists each object, its source structure and its staging table. Synonyms keep scripts working when the names change between systems.

    • /1LT/DS_MAPPING
    Source: SAP Community, migration cockpit FAQ
  • 15Other teams

    Direct transfer needs DMIS in the source

    SAP ERP 6.0 or later with the add-on DMIS 2011 SP17 or higher, included in the SAP S/4HANA license; without it the cockpit cannot even read the company codes.

    • DMIS_2011_1
    Source: SAP product management, migration cockpit 1909
  • 16Other teams

    Give big objects more jobs

    Each migration object starts with one data transfer job. Raise it for high volumes in Job Management, within what the system can run.

    • Job Management
    Source: SAP KBA 3580792, data transfer jobs
  • 17Other teams

    Stock takes the master price

    Material inventory balance values stock at the material master price. For standard-price materials an external amount posts the difference to a price difference account; for moving-average materials it changes the price.

    • 561
    • MB5L
    Source: SAP Help, migration objects for SAP S/4HANA
  • 18Other teams

    Bigger files on-premise

    The 100 MB limit per XML file can be raised to 160 MB on-premise with icm/HTTP/max_request_size_KB; beyond that, split or use the staging tables directly.

    • icm/HTTP/max_request_size_KB
    Source: SAP blog, overcoming the file size limit

Myths

Things people get wrong about the Migration Cockpit

  • MythThe Migration Cockpit is only for data from non-SAP systems.

    FactSince 1909 it reads SAP ERP 6.0 directly over RFC, and staging tables take data from any system, SAP or not.

  • MythLTMC still works for a new project.

    FactIt is deprecated: its projects stay in it, and new migrations run in Migrate Your Data (F3473).

  • MythSimulation changes nothing in the system.

    FactIt is meant to find errors before the load, but not every object is free of side effects: SAP has a KBA where simulation uses up number ranges.

  • MythIf the data is wrong, we migrate it again.

    FactThe cockpit is for the initial load and cannot delete or reverse migrated data; corrections happen in the business applications.

  • MythLoad the whole trial balance with the G/L balance object.

    FactCustomers, suppliers, assets and stock come from their own objects, and SAP’s documentation says fixed asset balances must not appear in the G/L file.

  • MythThe Bank account balance object puts the bank balance in the G/L.

    FactIt only feeds Cash Management. The G/L balance of the bank account comes from the G/L balance object.

  • MythEach migration clearing account must be zero.

    FactEach one keeps a balance. Their total must be zero, and the KBA on clearing them exists precisely because they do not vanish one by one.

  • MythA direct transfer can copy one SAP S/4HANA system into another.

    FactNo. It is built for SAP ERP sources; mappings such as BSEG to ACDOCA make no sense between two SAP S/4HANA systems.

Evolution

From a cloud-only file upload to one app for every source

The cockpit started in the cloud, reached on-premise a year later and kept adding ways in. Gold dots mark the Migrate Your Data era.

  1. 1511SAP S/4HANA CloudThe file approach ships with the first, Web Dynpro-based Migration Cockpit.
  2. 1610On-premiseThe cockpit reaches on-premise, with the migration object modeler (LTMOM) beside it.
  3. 1709FPS02Staging tables arrive on-premise; the public cloud gets them in 1905.
  4. 1809FPS0The mapping table /1LT/DS_MAPPING records which staging table belongs to which object.
  5. 1909Direct transferDirect transfer from SAP ERP 6.0 over RFC, with the DMIS add-on in the source, in its own Fiori app.
  6. 2020Migrate Your DataOne Fiori app for staging tables and direct transfer; the file approach becomes part of staging. SAP S/4HANA Cloud gets it in 2008.
  7. 2021TransportTransport for staging projects on-premise; quality and production only execute. SAP had announced LTMC’s retirement for this release.
  8. 2022Fixed assetsFixed asset - Master data and Fixed asset - Postings reach on-premise and private cloud.
  9. 2402Public cloudDirect transfer opens to SAP S/4HANA Cloud Public Edition.
  10. 2602Public cloudEach XML file inside a zip may reach 400 MB.

Three tools compared

LSMWLTMCF3473
ScreenSAP GUIWeb DynproSAP Fiori
ContentBuilt per projectSAP objectsSAP objects
SourcesFilesFiles, stagingStaging, SAP ERP
TodaySimplification listDeprecatedCurrent

Sources: SAP KBA 2988692; SAP, data migration tools compared.

Public cloud against on-premise

Public cloudOn-premise
ModelerModel Your Migration ObjectsLTMOM
StagingScope item 2Q2, by ticketStandard
TransportNone for stagingFrom 2021
From SAP ERPSince 2402Since 1909

Sources: SAP Community, migration cockpit FAQ and product management answer on transports; SAP Learning, extending migration objects.

Sources: SAP PRESS, data migration to SAP S/4HANA; Michael Management, SAP S/4HANA 1709; SAP Community, migration cockpit FAQ; SAP blogs, Migrate Your Data part 1 and the transport concept; SAP KBAs 2827574 and 3691273.

The questions people ask most

Is transaction LTMC still available?

Only for the projects created in it. LTMC is deprecated; from SAP S/4HANA 2020 and SAP S/4HANA Cloud 2008 SAP recommends creating projects in the Fiori app Migrate Your Data (F3473), and LTMC projects cannot be opened there.

Staging tables or direct transfer: which one should I use?

Direct transfer works only when the source is an SAP ERP system (SAP ERP 6.0 or later, with the DMIS add-on) and reads it by company code. Staging tables work for any source, filled from SAP’s templates or from your own tools, and give you a place to cleanse the data before the load.

Can I migrate from one SAP S/4HANA system to another with the cockpit?

Not with the direct transfer: SAP says the cockpit moves data from SAP ERP into SAP S/4HANA and is not meant for loads between SAP S/4HANA systems. Staging tables remain an option, since they accept any source.

What is the file size limit?

100 MB per XML or CSV file and per zip file. On-premise the limit per XML file can be raised to 160 MB with the parameter icm/HTTP/max_request_size_KB; in the public cloud from 2602, each XML inside a zip may reach 400 MB. Filling the staging tables with tools avoids the upload altogether.

Can I add a column to the Excel template?

No. The template itself warns that changes to its sheets corrupt the XML structure. Extra fields are added to the migration object: custom fields from in-app extensibility appear automatically for objects that support them, and LTMOM (or Model Your Migration Objects in the public cloud) adds others.

Can I use the cockpit to update existing data?

It was designed for the initial load, and update objects copied from the standard insert objects are not supported. To add new organizational levels, use the extend objects; to change data, use the maintenance and mass processing apps.

How do I undo a migration?

Not in the cockpit: it cannot delete or reverse migrated data. Use the business application, for FI by reversing the journal entries.

How do I move a project from quality to production?

On-premise from SAP S/4HANA 2021, staging projects and LTMOM changes go by transport; quality and production systems only execute projects. Export and import by mass transfer ID also exist, with the report /LTB/MC_PROJ_Q2P. In the public cloud there is no transport for staging projects, so the project is created again.

Why do my FI open items stop with CNV_DMC_SIN 441?

The company code has no migration key date. Maintain it in FINS_MIG_CTRL_1, Define Settings for Legacy Data Transfer, and set the status to Ongoing for the initial load.

Are taxes migrated with the open items?

VAT line items are not migrated. Open tax items must be settled before the migration; the exception is deferred tax, for invoices, debit memos and credit memos. Tax balances go in as G/L balances.

Do I put customers, suppliers and assets in the G/L balance file?

No. Their reconciliation accounts are posted by the open item and fixed asset objects. SAP’s documentation says fixed asset balances must not be in the G/L file; what the G/L file carries is everything no subledger does.

Why does my bank balance not show in the G/L reports?

Because the Bank account balance object only updates Cash Management. Load the bank G/L account with the G/L balance object; Cash Management then picks up that journal entry.

How do I bring prior-year balances for comparison?

With FI - Historical balance: closed periods before the migration key date, posted for reporting with their own document numbers. The period movement method reaches 9 years back; older years use period balance.

Does the Migration Cockpit cost extra?

The cockpit and its migration objects are included in the SAP S/4HANA and SAP S/4HANA Cloud licenses. SAP notes that staging through a database in the cloud may bring additional license costs.

References

Checked in November 2026. SAP knowledge base articles and SAP Notes need an SAP for Me login. Releases, file limits and object names change; check them in your own system.