Migration Cockpit: Direct Transfer & Performance

You need to migrate from a non-SAP legacy database. Why can't you use direct transfer, and what can?

Your legacy SAP ERP source is still non-Unicode. Does that block direct transfer, and what happens to the data on the way in?

On-premise, users hit the 100 MB ceiling uploading a large staging file. Which parameter raises it, and why is cranking it up risky?

A stakeholder wants to reuse direct transfer to keep the old ERP and new S/4HANA continuously in sync. Which SAP products are actually meant for that?

Before scoping a direct transfer, how do the minimum source releases differ across the supported scenarios?

You installed the DMIS add-on in the source but the migration still isn't recognized. Beyond installing it, what must match your target release, and who pays for it?

How do you confirm every required DMIS add-on and S/4HANA component note is implemented before creating a migration project, instead of finding out mid-load?

Migration objects that worked last quarter are missing after a support package update. What step must be repeated?

Before the very first migration test in direct transfer, what must already exist in the target — and why isn't the migrated data enough on its own?

A consultant sets up only target-side roles for the migration user and selection fails. Which roles does direct transfer require, and where?

A migration step dies on a missing authorization but the message is vague. Which transaction pinpoints the failed check?

You're migrating two source systems into one S/4HANA target. Why can't a single migration project cover both, and how many objects should a project hold?

At project creation you're forced to assign a development package even though you never plan to transport it. What do you assign, and what becomes irreversible?

You transport a direct-transfer project to production and the mapping values don't come across. Is that a defect?

You added a migration object by mistake and want it gone. When is deletion even allowed, and what's the workaround if it isn't clean?

During the Check step a popup offers to add predecessor objects like CO - Secondary Cost Element. Must you accept?

Right after creating a project, its objects show Not Ready for Processing. Is the project broken?

A TCI note ships a content update for a migration object you already have in your project. How do you actually apply it?

In direct transfer, why does the Migration Object view never warn about custom (Z) fields in your S/4HANA target?

You selected company code 0001 and the CO - Activity Type object, but activity types aren't stored by company code. How does the cockpit still find the right records?

Source records changed after your first selection. What do you pick on re-selection, and what's the cost of getting it wrong?

You only want to migrate a handful of business-critical records first, not the whole selected set. How?

Where must you deduplicate and clean legacy data in a direct transfer, and why not in the cockpit?

Since release 2021 there's a separate Prepare Mapping Tasks step that used to be part of Select Data. What does it do, and when can you skip it to save downtime?

You download a mapping template to edit values offline. What sheets does it contain, and how do you control whether an upload replaces or adds values?

In direct transfer you confirmed mapping values but no validation ran. Is that expected, and how do you actually check them?

Two legacy cost centers should collapse into one target cost center A1. Why does the second record error out, and what tooling won't help you?

What exactly does Simulate do to your instances before you commit to Migrate, and how much can you simulate at once?

After a simulation you want to see, for one error message, every instance it hit. Which of the three message views gives you that?

A simulation error clearly comes from an SAP application check, not from the tooling. What are your realistic ways to resolve it?

Technically, what's the only difference between Migrate and Simulate, and how do you avoid migrating known-bad records?

After migrating, how do you review what landed and jump straight to the created records?

The Customer object migrated through more than one path while most objects used just one. Where do you see and control that?

You want to parallelize simulation harder than selection. Can you, and what ultimately caps the number of parallel jobs?

You have budget to add either RAM or CPUs to speed the live migration. Which usually helps more?

Two migration objects hold identical row counts, yet one loads far slower in a direct transfer. Beyond parallel jobs and hardware, which two direct-transfer-specific factors explain the gap?

Throughput during a migration is stalling even though the system has spare dialog capacity. Why can switching off unrelated standard background jobs and limiting logins actually speed the load up?

Across the SAP migration tools, which can pull data out of a source system on their own, and how does the cockpit's direct transfer do the extraction?

For the migration cockpit, when do you actually have to write development code for extraction — and how does direct transfer differ from the file/staging approach here?

In direct-transfer object modeling, what can you change on-premise that you simply cannot change in S/4HANA Cloud?

A customer wants direct transfer but is on older SAP releases. What is the minimum source release for each supported source scenario?

You're about to transfer balances and open items into S/4HANA. Why must a migration key date be set first, and where is it no longer allowed to be maintained?

A financial-object data transfer fails with CNV_DMC_SIN 441 or FINS_MIG_HIST_BAL_023. What's the root cause, and which company-code status must you reach before it will run?

Asset accounting doesn't call it the migration key date. What is it called, which objects need it, and how does Universal Parallel Accounting change the object set?

You already ran one asset data transfer and now need a second at a later date. Why can't you just overwrite the transfer date, and which extra status do assets have that GL accounting does not?

Which app lets you review, evaluate, and download the message log of migration runs per object — and what surprising limitation did it originally have about which approach it covered?

On-premise a colleague can open the Data Migration Status app but can't approve audited records. Which role distinction explains that?

From the Data Migration Status app you want to jump straight to an imported record's maintenance app. How does that navigation work, and why do a few objects refuse to navigate?

Beyond the Imported/Failed counts, what does the Data Migration Status app's audit function add, and what are its three states?

You have to audit thousands of imported records without opening each one. What selection and offline options does the Data Migration Status app give you?

After an on-premise migration you open Extended Statistics for per-structure record counts and see nothing. Which default bit you, and when must you flip it?

You scope a direct transfer to company code 0001, but a table like CSLA has no company-code field. How does the cockpit still select the right records?

In direct-transfer object modeling, what exactly is a 'filter,' why can't you invent your own, and how does the company-code filter differ from the other nine in the SAP ERP scenario?

If direct transfer reads live SAP tables, why can't it just copy rows across — why is a migration object required at all?

In the file/staging approach you attach rules to events; in direct transfer that option is gone. So when do direct-transfer rules actually run?

You need to narrow which source rows a direct-transfer object reads. On which tables can you even add selection criteria, and what responsibility shifts to you once you do?

For a source table at level ≥2, what's the practical difference between 'Selection Affects the Entire Migration Object Instance' and 'Only This Table and Subordinate Elements'?

Filters and simple selection criteria can't express the extraction rule you need. What escape hatch did S/4HANA 2021 add, and where does that code run?

A source SAP standard table carries custom Z fields. Which cockpit approach even notices them, and what decides whether they can actually be migrated?

Debugging a direct-transfer simulation, how do you inspect an instance both as it was read from the source and after your mapping rules have transformed it?

Why do you tune the number of parallel jobs during test runs rather than discovering the right value on the production load itself?

For direct transfer to S/4HANA, where must the DMIS add-on be installed, and what breaks if it's on the wrong system?

In a direct transfer, which direction does the RFC connection run, and which side initiates the data movement?

When must you NOT use direct transfer, even though it can read an SAP source over RFC?

Why can an on-premise system be parallelized more aggressively for migration than an S/4HANA Cloud system?

Before you can use SAP's delivered migration objects for direct transfer, what must you run, and why isn't the working client enough on its own?

What does direct transfer eliminate compared with the file/staging approaches of the migration cockpit?

Migration throughput is poor even after tuning jobs and resources. What non-load factor should you check next?

Which transfer method gives the best migration performance, and what single thing most determines an object's throughput?

Beyond technical tuning, which organizational measures in the SOURCE improve transfer performance, and which one is easy to forget?

Which SAP source scenarios are supported for direct transfer to S/4HANA?

How do migration objects stay current in S/4HANA Cloud versus on-premise staging, and what do you NOT get on-premise?

In direct transfer, how do you scope which source data is selected, and what scoping freedom do you NOT have?

Which system resources gate migration throughput, and why is checking only RAM a mistake?

Since which release is direct transfer available for S/4HANA Cloud, public edition — and what's the catch at that release?

At what granularity is parallelization set in the migration cockpit, and what ultimately caps it?

Where do you find which BAPI a migration object posts through and how to verify its results, before you run it?

The Data Migration Status app shows object names like 'BANK_2' instead of 'BANK'. What harmless action caused the app to display these technical names?

Why should you avoid scheduling a data transfer during an S/4HANA Cloud maintenance window?

Where do you maintain the GL migration key date on-premise, and which authorization gates it that a cloud user doesn't need to think about?

In direct transfer, the predefined organizational unit you first select depends on the scenario. What's the mapping for each source system?

You want a second migration project just like an existing one. What does Copy carry over, and what will you have to redo?

Direct transfer's headline benefit is a direct connection to an SAP source — but what single protocol limitation constrains it today?

Which SAP systems can NOT serve as a source for direct transfer to S/4HANA?

Your team keeps opening Transaction LTMC to run a direct-transfer migration and it's gone. Since which release did direct transfer arrive on-premise, and what launches it now?