This document discusses using the transaction LTMOM to migrate data to SAP S/4HANA and provides tips to overcome challenges. It outlines an agenda including examples of customer master data loads and debugging LTMC and LTMOM. Specific issues covered include loading credit management roles, extending organizations, and material master issues. The discussion emphasizes the importance of practicing migrations and having programs to reset or delete data when needed.

1. LTMOM TO MOVE TO SAP
S/4HANA
GAIN TIPS ON HOW TO MANAGE CHALLENGES IN USING THE
TRANSACTION LTMOM TO MOVE TO SAP S/4HANA. PLEASE BRING
YOUR OWN ISSUES, OR BE READY TO LISTEN TO OTHERS’
CHALLENGES. THIS IS NOT A TRAINING ON HOW TO USE THE
PRODUCT BUT A DISCUSSION ON OVERCOMING OBSTACLES.

2. SHORT INTRO
• Name
• Company
• System HANA 1709, Netweaver 7.5
• The Rules – open conversations, interrupt and share your own
experiences throughout, Relax this one is all about you

3. AGENDA
• Example of Customer Master load
• Examples Running LTMC script multiple times
• Debugging
• LTMC vs LTMOM
• Mapping

4. CHALLENGE – BP CREDIT MANAGEMENT
• Move XD03 customers to BP. Add the BP role UKM000 Credit
Management
• Create LTMC load the data
• Data is easily loaded with only a few or constant changes

5. LTMC – CUSTOMER LOAD
• Added customer load – general information is loaded
• First issue tried to load all the roles at once
• Next issue was loading texts
• Credit Role
• Cross Reference table – new numbers made on our new system

6. BREAKDOWN
• Customer load
• General Data
• Company Data
• Customer Account Management
• Dunning
• General Data
• Industry

7. CUSTOMER MASTER
• Webdynpro – Recomplile on each client
• XD02 to BP
• Customer Credit - UKM_DB_UKMBP_CMS_EXECUTE
• Added BAPI_BUPA_ROLE_EXIST_CHECK_2
and BAPI_BUPA_ROLE_ADD_2

8. GENERAL - EXAMPLE

9. CUSTOMER CREDIT ROLE NOT FOUND
• Could not get this one to work at all in LTMC
• Extend the new orgs

10. EXTEND ORG

11. THE FUNCTION MODULE FOR ADDING
CREDIT ROLE
• Z_UKM_DB_UKMBP_CMS_EXECUTE – wrapped
UKM_DB_UKMBP_CMS_EXECUTE
• Quick and dirty

12. data: ls_crd type ukm_s_bp_cms_upd,
lt_crd type standard table of ukm_s_bp_cms_upd.
clear: ls_crd,
lt_crd.
data: numc10(10) type n.
if partner co '0123456789 '.
numc10 = partner.
clear partner.
partner = numc10.
endif.
* Move to table for SAP FM
ls_crd-client = sy-mandt.
ls_crd-partner = partner.
ls_crd-check_rule = check_rule.
ls_crd-risk_class = risk_class.
ls_crd-credit_group = credit_group.
ls_crd-limit_rule = 'STANDARD'.
ls_crd-change_id = 'I'. "change_id'.
append ls_crd to lt_crd.
loop at n_ukmbp_cms_sgm.
clear n_ukmbp_cms_sgm-partner.
n_ukmbp_cms_sgm-partner = partner.
n_ukmbp_cms_sgm-change_id = 'I'.
modify n_ukmbp_cms_sgm index sy-tabix.
endloop.
* Run the function module - no return value
call function 'UKM_DB_UKMBP_CMS_EXECUTE'
tables
n_ukmbp_cms = lt_crd
n_ukmbp_cms_sgm = n_ukmbp_cms_sgm[].
commit work.

13. PROBLEMS
• Need the role before can add to it

14. data: lt_ret type standard table of bapiret2,
lv_error(1),
bpartner type bapibus1006_head-bpartner,
partnrole type bapibus1006_bproles-partnerrole,
numc10(10) type n.
field-symbols: <fs_mes> type bapiret2.
data: ls_crd type ukm_s_bp_cms_upd,
lt_crd type standard table of ukm_s_bp_cms_upd.
clear: ls_crd,
lt_crd.
bpartner = bp.
if bp_role is initial.
partnrole = 'UKM000'.
else.
partnrole = bp_role.
endif.
if bpartner co '0123456789 '.
clear numc10.
numc10 = bpartner.
clear bpartner.
bpartner = numc10.
endif.
call function 'BAPI_BUPA_ROLE_EXIST_CHECK_2'
exporting
businesspartner = bpartner
businesspartnerrole = partnrole
tables
return = lt_ret[].
loop at lt_ret assigning <fs_mes>.
if <fs_mes>-type = 'E'.
lv_error = 'X'.
exit.
endif.
endloop.
.
if lv_error = abap_true.
clear lt_ret.
call function 'BAPI_BUPA_ROLE_ADD_2'
exporting
businesspartner = bpartner
businesspartnerrole = partnrole
tables
return = lt_ret.
clear lv_error.
loop at lt_ret assigning <fs_mes>.
if <fs_mes>-type = 'E'.
lv_error = 'X'.
move-corresponding <fs_mes> to ct_return2.
append ct_return2 to ct_return2.
endif.
endloop.
endif.
if lv_error <> abap_true and
bp_sim <> abap_true.
call function 'BAPI_TRANSACTION_COMMIT'.
endif.

15. PROBLEMS - DEBUG
• Your FM works fine
• Your LTMOM works fine
• Run LTMC and it doesn’t work

16. GENERATE THE LTMOM

17. Debug

18. MATERIAL MASTER ISSUE
• Material view will be used in the Basic Data as Material views

19. MATERIAL MASTER – BIG NOTE

20. REMINDER
• Generate in each Client
• Be ready to create your own programs to delete data. Or have
some clients where you can just reset.
• Practice as many times as you can
• Never worry about small amount of data for manually
uploading

21. PROBLEMS
• Re-run even if there were errors – run DMC_FM_RESTART and
DMC_FM_RESTART_COPY_DELETE

22. LESSONS LEARNED
• It’s hard finding information. Many blogs and many questions
were out there
• Can’t practice enough
• Some cross-reference programs had to be written. We did
change some data before the move. Some was done in
previous system and some was done in LTMC. It would have
been easier to have it all done in LTMC. (Or more than we did)

23. LINKS
• Open SAP Course - https://open.sap.com/courses/s4h8
• Blog by Praful Jain – SAP S/4 HANA Migration Cockpit Step by Step -
https://blogs.sap.com/2018/01/07/sap-s4hana-migration-cockpit-step-by-
step-process/
• Blog and interactive demo by Jorg Knaus -
https://blogs.sap.com/2017/02/28/getting-started-with-the-s4hana-
migration-cockpit-onpremise/
• Blog for starting to use LTMC by Ramkumar RV
https://blogs.sap.com/2019/05/13/sap-s4-hana-migration-cockpit-ltmc-
activity-type-master-data-upload-step-by-step-process/
• My Blog – Stumbling through Data Migration with HANA -
https://blogs.sap.com/2018/07/05/stumbling-through-data-migration-with-
hana-data-migration-ltmc-and-ltmom/