Custom Fields in Migration Cockpit

[SAPSupport]

How to add custom fields to the standard template of a Migration object? Should it be done via "Custom Fields" app? LTMOM? Both?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[steven_k]

I have a follow-up question.

The 2 goals listed above do not cover our current situation. Our situation is as follows:

We have existing custom fields in our MARA table. They are critical, mandatory fields for our business. These fields are not currently available in LTMOM to map. We do NOT wish to create new custom fields via "Custom Fields". We have been unable to find a suitable solution for making existing custom fields available for migration via "Migrate Your Data". (We were successful using LTMC, but as this tool is no longer available, we are at a loss).

Is there a documented method for achieving our goal?

[former_member708504]

I have the same issue.If we insert the custom field manually in LTMOM,it is not appear in target structure.If we add via ' Custom field ' ,the field name is start with prefix ZZ1_* which cannot do the field mapping to existing Z-field .Any recommendation ?

[FrankFinkbohner]

Hi,

the Data Migration Framework only supports new key user extensibility. The classic ERP extensibility model is not supported out of the box. Most of the APIs used to migrate data are also only supporting the new key user extensibility. Using key user extensibility, you don't need to take care for the sender structure and field mapping. You create the custom fields via Custom Fields app and within migration cockpit you choose the button check for custom fields. Then the fields are automatically being added to the staging tables/Template. For the on-premises and Private Cloud releases you can check the https:\\help.sap.com\s4_op_mo web page that shows you the objects per release that support custom fields by key user extensibility.
The LTMC uses the same migration framework as the Migration Cockpit Fiori-based app. Even with the LTMC it was not possible to use other extensibility then key user extensibility out of the box. When you are saying that it was possible with the LTMC transaction to use the Material object and then add old classic extensibility fields to the object via LTMOM, then this is correct. But that was not an advantage of the LTMC. At the time of LTMC, the migration object Material was build using the old ERP BAPI BAPI_MATERIALSAVE_REPLICA. The new Product object replacing the old Material object uses the Universal Product API build for SAP S/4HANA and supports multiple additional functionalities that are missing in the old ERP BAPI, as for example, internal numbering, key user extensibility support, additional industries... Old ERP BAPIs are getting more and more replaced by new APIs build for SAP S/4HANA. Using the old classic ERP extensibility is not recommended as it has a lot of limitations within SAP S/4HANA.

BR

Frank

See also the SAP Help Portal: Overview | SAP Help Portal (Support of Custom Fields – SAP S/4HANA Migration Cockpit)