Migration Object Modeler

You're on on-premise SAP S/4HANA and need to open the modeling environment to adapt a delivered migration object, but LTMOM won't launch for a colleague. What are the two prerequisites, and what's the entry point?

In LTMOM you know the object exists but not which project it lives in. The default Object Browser assumes you already know the project — what's the other view, and what can it search that the browser can't?

For the staging-table approach, the modeler's full feature set is huge. Which three application cases does SAP frame as the common reasons you'd actually reach for it?

You need a migration object to do something the delivered template can't. Before you sink time into building rules in LTMOM, what determines whether your enhancement is even possible?

A colleague says LTMOM is only for staging-table migrations, so direct-transfer projects can't customize objects. Right or wrong?

Are SAP's delivered standard migration objects fixed reference data you must clone before touching, or something you can work on in place?

Which two kinds of migration interface can the migration object modeler build objects on?

Same migration object, on-premise vs S/4HANA Cloud public edition: why can you customize it more deeply on-premise — and what does that imply for planning the cloud project?

Your source data needs a conversion the delivered rules don't cover. What's the right move in LTMOM, and why not just patch each field inline?

You're migrating from SAP ERP and the business relies on custom/extension fields. What happens to those fields if you just run the standard migration object — and what's the fix?

The delivered object isn't doing the job. How do you decide between extending the existing one and building a brand-new custom migration object?

Six months after go-live SAP ships a correction to a delivered migration object. Your copied (not template-based) object — does it pick up the fix? How would you tell at a glance?

You're adding a migration object to a project in LTMOM. The two ways differ in one property that decides everything downstream — what is it?

SAP releases a new version of a delivered object your template-based object is built on. Will it silently overwrite your object — and what's the catch if you do nothing?

You copy a migration object from one LTMOM project into another. After the copy, are the two objects still tied together?

You need to change a field's length on a delivered migration object, which a template-based object won't allow. Copying gives you that freedom — what's the asymmetric cost you're accepting?

You created the object 'from a delivered template' and now must change a delivered field's length. What can't you do, and why does the template route forbid it?

You copy a migration object specifically to fully decouple it from SAP updates. What extra step do people skip — and where must the result live?

You need to migrate a handful of extension/custom fields the delivered object doesn't cover. Must you build a whole new migration object?

You need to know exactly which import structure fields a delivered BAPI expects before you extend its migration object. Where does that field-level documentation live?

A staging-table migration project built on SAP S/4HANA 2020 works in the development client but a consultant can't open it in another client. Why — and did this apply to older LTMC projects?

You write a transfer rule at project level expecting to edit it, but the modeler shows it as read-only. What determines where a rule can live and whether you can change it?

When you open a single migration object in LTMOM, the navigation tree exposes five nodes. What are they, and roughly in what order do you work through them?

The object browser groups everything you can build in a migration object into four kinds of transfer rule. What are the four, at a glance?

You want to hardcode a controlling area onto a target field, and separately map a translation object to another field. Neither can be attached to the target field directly — what's the shared workaround?

The 'Rules' category splits into three subtypes. How do event-based, field-based, and internal rules differ in when and how they fire?

You need a value computed in a start-of-loop event rule to be reused by several later field rules in the same migration object. What construct carries it across?

You finish mapping new source fields but the migration cockpit still won't process them. What technical step did you skip, and what does it actually rebuild?

SAP ships a correction to a delivered object you've heavily customized. You run the update to pick up the fix — what happens to your custom rules, and how could you have permanently opted out instead?

Two naming conventions signal how a migration object was created: what prefix marks a custom object ID, and what suffix appears when an object is copied?

Before extending a delivered migration object, you open its Global Data node. What reference information does the delivered header documentation give you there?

You set a field's migration-template visibility to Not Visible, but your custom changes don't show up in the cockpit at all. What are the three visibility values, and what one switch did you forget to flip?

In the Target Structures node you see the function module (e.g., BAPI_BANK_CREATE) plus four processing settings. What do those settings control, and what does 'Value for Writing Data = X' mean?

In the Structure Mapping area, what does the '<<' notation after a target structure tell you, and how can an expert catch a mapping error before running any data?

Event rules can fire at 'processing times', but the available times differ between structure mapping and field mapping. What are the two sets, and why does the distinction matter?

You drag a source field onto a target field and the modeler silently creates a MOVE rule. When is that exactly what you want, and when will it quietly break the load?

You're mapping an object with hundreds of target fields and want the system to do the tedious work and let you find what's still unmapped. Which field-mapping functions help?

You want to base a custom migration object on your own function module. What must that FM satisfy to qualify as a migration API, and what's the escape hatch if it can't — or if it's actually a class method?

When creating a user-defined migration object whose target is a function module, which three settings must you supply in the input dialog, and what are the typical values?

Saving a new source structure fails with a 'maximum key field length exceeded' error. What's the hard limit, and what's automatically set on a brand-new object's key fields?

You map several source structures to their target structures but no data records get processed on the load. What's the classic omission, and what else about the mapping matters?

Mapping the COSTCENTER target field, a single source field for the cost center isn't enough and the value won't resolve. Why, and what must you supply instead?

For cost-center migration on SAP S/4HANA 2022+, which delivered rule determines the target cost center, and what do you feed it to select determination by controlling area?

Instead of assigning a rule to every field by hand, the modeler can propose rules automatically. Since which release, and how does it decide what to propose?

Reading the rule-proposal overview, what do a yellow triangle, the flags (S)/(M), and a question mark after a rule each tell you?

You've finished all field mapping for a new migration object. What's the mandatory last step before any data can be transferred, and where does the object show up afterward?

Debugging a generated migration object's function group, which two INCLUDEs matter — one holding the processing function modules, the other calling the migration API?

You built a translation object to convert source values. Why can't you drop it straight onto the target field, and where should you create it so the whole project can reuse it?

You're naming a new custom migration object, rule, or translation object. What naming constraint does SAP S/4HANA enforce, and since when?

When you define a translation object's export parameter, how can you restrict it to a valid value range — and which choices also let the system validate the value?

In a translation object, what do 'Do Not Convert if Field Contains Initial Value', 'Insert Missing Record into Conversion Table', and the 'First Import Parameter' error option each do?

A field-based rule can change a target value during migration. What three things can it be based on, and what appears in the migration cockpit once you assign it to a field?

Before a real load you want to test how source fields get transferred. What does the modeler's Simulation give you, which records does it touch, and how do you break into the flow?

On an older SAP S/4HANA release without in-modeler simulation, and when you need to re-run records you've already migrated — what tools handle each case?

Two ways to create a direct-transfer migration object — one starting from SAP's delivered content, one from scratch. What menu path does each take?

For direct-transfer objects, why can you only copy a migration object within the same project, and what do you run when the underlying ABAP Dictionary tables or function modules change?

As of SAP S/4HANA 2020, which three transformation rule types can you create, and what distinguishes a value mapping from a fixed value?

When you create a user-defined rule in direct transfer, what does creating it at project level versus object level change, and what two statuses does every rule carry?

Rule handling in the modeler shifted release by release. What changed for source-code rules, for copy/delete/transport of rules, and for downloading/uploading mappings?

How are migration projects moved between systems on modern SAP S/4HANA, what must you set up at project creation, and what was different back in 1909?

You add a migration project to a transport request. What travels with it, and what silently stays behind?

You use Goto > Use Project in Different Client to make a project available in another client. What's the trap about mapping values, and how do you avoid losing them?

Migration projects can't be edited directly in production, and a freshly transported project won't just open. What's the workflow, and what one-time step does the target system demand?

In direct transfer, trace the path from raw source tables to a posted record: what does the data model define, and what happens in the Simulate versus Migration steps?

Some target fields — dates, names, descriptions — need no conversion at all. Which rule handles them, and what does it actually do?

SAP ships an updated migration object via an SP or TCI note, but your project still behaves as before. Why, and what must you run — mandatory since which release?

Your migration project won't reach a consistent status until certain function modules are created or an SAP Note correction is made effective. What are these units of work called, when must you create them, and what blocks their creation?

You're on SAP S/4HANA Cloud public edition and want to extend a migration object yourself. Is the migration object modeler even available to you, how far can you actually take it, and which role unlocks it?

Simulation of a staging migration object refuses to run. Which four prerequisites must all hold — including one about the staging tables that surprises people?

In SAP S/4HANA Cloud, public edition, what is the scope of the migration object modeler, and what should you NOT assume from that limit?

You heavily adapt a delivered migration object and later hit a runtime error. Before opening a support ticket, what's the limit on the help SAP will give you?

You want to reuse a migration object that lives in a different client, and another one from a legacy project. Can the copy function reach across those boundaries?

You need cost center names in several languages, but the delivered cost center migration object only writes one. Why, and what's the standard way around it?

Besides classic function modules, the migration object modeler can build objects on a second, newer kind of interface. What is it, since when, and what technology does it come from?

A team member proposes using the Legacy System Migration Workbench (LSMW) for a fresh SAP S/4HANA data load. Why is that the wrong default now, and where is that decision documented?

You try to delete a migration object in LTMOM but the system won't let you. What's the likely blocker, and how do you clear it?

SAP Best Practices only exposes a subset of an object's fields, but you know the API carries more. Where do you add the missing ones, and how does the tool tag what you add?

You add a new substructure to a migration object and it never receives data. What structural link did you fail to establish, and how are structures tied together in general?