Migration Cockpit: Concept & Staging Tables

In the migration cockpit, what does one "instance" of a migration object represent?

You load customer records but skip maintaining mapping values for the legacy plant/region codes. What happens at migration time?

A 2020-era runbook tells you to start the migration cockpit with transaction LTMC. On SAP S/4HANA 2021, what's wrong with that?

In what file formats can you download a migration template, and what do you get when you select several objects at once?

A stakeholder hears "the migration cockpit automates the load" and assumes the transfer is push-button. Why does SAP explicitly warn against this?

In the staging-tables approach, what does the migration cockpit actually read as its source — and why does that matter for how you can feed data in?

Which technical product version underlies SAP S/4HANA Cloud public edition versus on-premise / Cloud private edition?

You open a migration template workbook and see an Introduction sheet plus many spreadsheets. How do you know which ones you must actually fill?

Since which releases has the staging-tables approach been supported (on-premise and Cloud)?

The migration cockpit offers two data-transfer approaches. What are they, and what fundamentally distinguishes them?

Why does the migration cockpit carry far more weight for an S/4HANA Cloud project than for on-premise?

You have in-flight projects in the old LTMC cockpit and are moving to the new Migrate Your Data app. Can you carry those projects over?

You loaded customers, then corrected some attributes in your source and want to push the changes. Why can't you just re-run the migration object?

After a migration, 200 of 50,000 records failed. What's the right way to fix and reload them, and why not just reload everything?

What does the Simulate step actually do before the real migration — and what does it NOT do?

Your upload is rejected on a current system even though the data looks correct. Why does SAP insist you download templates from the latest release?

What is the SAP S/4HANA migration cockpit, and what is it scoped for?

After you upload filled templates, where does the data physically reside — and what does that let you do within one migration project?

What does a migration project in the cockpit actually hold — the loaded business data, or something else?

What are the two ways to populate the staging tables, and when would you choose the non-file route?

A simulation has been running for an hour and you suspect it's stuck. What does the Monitoring view let you do about it?

Should you work directly in the underlying "migration workbench" to customize delivered objects and rules?

After you upload a migration file, which two activities run, and where do they leave the data?

Why can writing directly into the staging tables be faster than the template-file route — and what's the trade-off?

Once staging data is loaded for an object, what's the correct order of actions — and which step is easy to skip?

An upload ends in "Validation Completed with Warning" or "Check failed." What's the most likely root cause, and what do you check first?

What happens technically the moment you create a customer migration project in the cockpit?

In SAP S/4HANA Cloud, can you write the local database-schema staging tables directly from an external tool?

To get direct external read/write into the remote SAP HANA staging schema, where must it live and how is it connected?

What does the Prepare action check, and how is it different from Simulate?

In the staging approach, how do a template's spreadsheets map to staging tables?

Beyond 'staging lands data first, direct transfer pulls from the source,' what technically distinguishes the cockpit's two approaches, and since when is direct transfer even available?

Browsing the object list you see one object tagged (deprecated) and another tagged (restricted). What does each addition tell you?

Before scoping a migration you need to know which objects your release actually supports and what changed since the previous release. Where do you look?

A migration user gets 'no authorization' launching the cockpit, and later again when connecting to a remote HANA schema. Which roles cover each case?

On an on-premise SAP S/4HANA system, where can the staging-table schema live, and what one-time table entry does a remote HANA schema require?

Staging tables temporarily hold real business data (customers, banks) in plain tables. What data-protection step does that call for, and why?

Do you have to create the staging tables yourself before loading data, or does something create them for you?

After the Migrate step posts data to the target, how do you validate the result, and which tool is the stronger choice?

You try to create a migration project directly in production and can't. Where must projects be built, how do they reach production, and what surprisingly does NOT travel with them?

When creating a project you're handed a 'Mass Transfer ID.' What constrains its value, and what is it actually used for?

The same migration object shows different fields for two colleagues. What controls which structures and fields appear, and what's the default on-premise versus cloud?

Since SAP S/4HANA 2022 you can upload CSV instead of XML. What do you gain, and what's the catch for a multi-structure object like Customer?

A CSV template that loaded fine in the US fails when a German colleague re-exports the same data. What CSV setting most likely bit you?

You split a large migration across several projects. Later, asset postings can't find the new internal keys of the assets you already loaded. What went wrong?

You added custom fields to a business object via in-app extensibility. Do you have to hand-add them to the migration template?

An object's Dependencies section lists Bank as a predecessor of Customer. Does that mean you must always load Bank first?

With 250+ migration objects and no single dependency chart, what ordering principles keep a load from failing on missing prerequisites?

Before loading an unfamiliar migration object, what does its SAP Help Portal documentation tell you that the template alone won't?

Several background activities finished with errors and the header now hides its buttons behind a menu icon. After you've corrected the underlying data, how do you clear the error state?

On S/4HANA Cloud you want to watch a migration simulation job — why can't you just open transaction SM37 the way you would on-premise?

You download a template for one migration object as XML and get a single file, but downloading it as CSV hands you a ZIP even though it's the same one object. Why?

Opening an XML template you see only a few labelled columns, but the book says the real technical field names are there too — where are they hidden and why do you need them?

You fill a Purchase Order template's item rows but not the header, and separately a Customer template's General Data. Which upload fails, and what's the underlying rule?

A colleague copies a column of dates from another spreadsheet into a migration template with plain Ctrl+V, and later the upload complains about data types. What went wrong?

Two uploads finish with warnings: one about a decimal like 0.57 being truncated, one about missing fields/structures. Which warnings can you safely ignore and which must you fix?

An upload lands in "Check failed" (not just a warning). What kinds of hard errors cause that status, and how is it different from a warning?

For the Customer object, when would you reach for CSV files instead of the XML template, and what extra rule governs the CSV file names?

The street field in a migration template is 60 characters but the SAP customer table KNA1 only has 35. Is the template wrong, and what does it tell you about where to extract data?

A field wasn't flagged mandatory in the template, yet the load complains it's required. How can a field be "conditionally" mandatory, and when does that surface?

You skip the template files and write straight into the staging tables from an ETL tool. What extra responsibility does that put on you for data types?

When you populate staging tables directly at the database level, the consistency check behaves differently than for file uploads. What's the rule — and why not just always leave it on?

You already loaded some customers, then upload another file that includes a few of the same customer numbers. What does the cockpit do, and what are your options?

A CSV file validated successfully in the cockpit. Is its data now in the staging tables?

Working with CSV templates feels fussier than XML. What extra handling does CSV require before validation can even start?

You uploaded a CSV file and now it has vanished from the Upload Files list. What's happening and how do you get it back?

You delete an uploaded file from the cockpit to "undo" a load. Did that remove the data from the staging tables?

A background job was cancelled and now the staging tables appear locked, and separately a table shows status "Adjustment Required." Which maintenance actions fix each, and what do they touch?

Mapping tasks come in three types. What distinguishes them, and why do object-ID tasks like customer numbers behave differently?

During Prepare a mapping task goes to Error status, e.g. a plant value that's longer than four digits. What did the cockpit do with that value, and what must you do?

Why does the migration cockpit's value mapping reward you for sourcing most of your data from a single legacy system?

You want subject-matter experts to maintain value mappings offline in a spreadsheet. How do you export a mapping task, and where in the file does the target value actually go?

You confirmed all mapping tasks and ran Simulate — and now new, unconfirmed mapping tasks have appeared. Bug, or expected? And how do you clear them?

You have hundreds of thousands of instances and don't want to trial-run all of them at once. What scoping options does the Simulate action give you?

A simulation finished with errors. How do you spot the failed object, get to the messages, and read what kind of component actually raised the error?

Before simulating a huge object, why is it smart to simulate just a handful of instances first — and how do you know when an object is ready to migrate?

In S/4HANA Cloud, how do you find out a long migration run has finished without watching the screen, and what does the notification take you to?

The Migration Results function gives you clickable links into a validation app. When should you not rely on it, and why might a link simply not work?

A migration object finished with status Completed — no errors. Why should you still open the message log, and what trick finds a systematic problem fast?

You need to hand migration error details to a functional team for troubleshooting. What are the two export formats, and how do they differ?

After go-live you set a migration project to Finished. Does that delete the data you loaded, and what is the Data Retention Period actually releasing?

Loading staging tables throws "will be truncated during transfer" (DMC_MD_INTERPRETER 037). What's actually happening and the usual cause?

When you run Migrate, which option is the recommended one, and what practice does it enforce?

You upgraded to SAP S/4HANA 2021 and can still open the old migration cockpit, but a colleague says the migration project you started there won't run. What state is the old cockpit in?

A stakeholder worries the migration cockpit can't handle their billions of records. Is there a hard cap on how much data you can load through it?

The book insists you always inspect data in the cockpit after an upload, even a clean one. What specifically can silently go wrong that you should check for?

After staging data is loaded, you need to act on just a handful of specific records rather than the whole object. Which view lets you do that, and what can it show and do?

Beyond a consistency check, what does the Prepare action do to your value mappings — and why must you still review before confirming them in bulk?

For the Customer object, mapping tasks appear the moment you add it, and the book says to do them before Prepare. Why does ordering matter here?

You only want to simulate or migrate a targeted subset of instances (say, all customers whose name starts with A). How does Custom Selection let you do that?

Migration finished with errors and you've fixed the bad rows in the correction file. What one step is easy to skip that will otherwise break the re-upload?

Is running one clean sample load in QA enough sign-off to load production?

Your migration file is larger than the upload will accept. What are the size ceilings, and how do you split without breaking the data?

You Select All on the mapping-task list and download values, but the file is missing most of your mappings. What did the list quietly do?

In S/4HANA Cloud (and S/4HANA 2022 FPS01+) you can wipe a whole mapping task with Delete Values. Why is that riskier than it looks?

You re-import maintained mapping XML files via Upload Values. What must finish before the tasks even appear, and which two option axes control the load?

While reviewing a value mapping you need to confirm some target values and pick valid ones for others. What does per-value maintenance give you beyond bulk confirm?

The old file-based cockpit parallelized by the number of files. In the staging-based cockpit, what drives parallelism instead, and what's the minimum job footprint per object?

You crank the job count way up in S/4HANA Cloud to speed the load, and even spin up a second migration project. Why does neither help?

After a release upgrade the cockpit flags many objects as "Update Required." What does that mean and how do you act on it?

Why does keeping migration objects current feel automatic in S/4HANA Cloud but require deliberate work on-premise — and what report helps on-premise?

Why does the number of available migration objects differ between SAP S/4HANA Cloud and on-premise, and how do new objects reach each edition between releases?

You're installing a fresh SAP S/4HANA 2022 FPS0 system for a migration. Why might some migration objects be broken out of the box, and what must you do before loading?

Your on-premise migration playbook leans on LSMW and SAP Data Services. Why does that plan fall apart when the target is SAP S/4HANA Cloud?

Why does the migration cockpit force you to map units of measure and currencies to ISO codes as the target value?

After a release upgrade, how do you tell whether a migration object has a newer version you should pull in?

Before creating a migration project (or opening a support ticket for a suspected bug), how can you confirm your source and target systems have all the required SAP Notes and TCIs?