Skip to Content

Hello S/4HANA migration cockpit users,

in this blog we would like to share some best practices, either in documents or short videos.

OpenSAP Course on Data Migration with deep-dive into the SAP S/4HANA migration cockpit and the migration object modeler for self-studying here


Migration Objects Overview

  • Find an overview on pre-delivered content for 1709/1802 here

MOM: New migration object – Create own function module:

  • In general the API must be a function module (FM) – RFC capability is not required.
  • OData and other techniques are currently not supported by the SAP S/4HANA migration cockpit.
  • The pre-requisites are quite the same as the BAPI definitions in the BAPI Programming Guide
  • The API must not execute ‘COMMIT WORK’ commands. The COMMIT control is handled by the Migration Tool
  • Error Handling: All messages must be returned in a BAPIRET2 formatted table or structure.
  • API should provide a test run flag to simulate the data creation
    • Internal Buffers must be refreshed in case the API is called in test run mode to prevent buffer overflows and performance issues when calling in a loop
  • Consistency Check: Write-enabled API methods must make all the necessary consistency checks to ensure that the modified or newly created instance is consistent.
  • Plausibility Checks: All necessary plausibility checks must be done within the API
  • If some of the prerequisites are not met, you can develop a wrapper (e.g. for old IDocs).

Find more details in SAP Note 2590165

MOM: Which function modules to use with newly created migration objects

  • Only function modules that are released shall be used
  • If a function module is released to be used by customers can be checked easily in SE37 -> „Attributes“ and “Released on” field.
  • Example for a released FM:


  • Example for a FM that is not released:

  • You should also check the SAP Notes for the FMs they want to use to get more information and also error corrections, e.g. RFC_CVI_EI_INBOUND_MAIN: 2506041 – S4TWL – API RFC_CVI_EI_INBOUND_MAIN is obsolete in SAP S/4HANA; 2387032 – Maintain the Task field in the communication segment in RFC_CVI_EI_INBOUND_MAIN; 2518068 – Load Credit Management Data with RFC_CVI_EI_INBOUND_MAIN





  • If you use SAPGUI 7.50 we recommand to unflag “SAP Fiori visual theme”




To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Federica Quaranta

    Dear Sybille,

    we are trying to use LTMOM with function module UKM_DB_UKMBP_CMS_EXECUTE in a SAP S/4 HANA 1709 system. Our aim is to create the role UKM000 for existing BP.

    We are unable to upload the data in LTMC because of the error:

    Furthermore, in SE37 this function module is “not released”:

    Can you help us?

    Thank you,



    1. Sybille Lackermeier Post author

      Hello Frederica,

      as this post is quite old – I suppose you did open a SAP incident.

      For your specific question on this role: You can use bapi BAPI_BUPA_ROLE_ADD_2 to maintain role UKM000.

      best regards, sybille



Leave a Reply