Getting started with the S/4Hana Migration Cockpit (OnPremise)
The S/4HANA Migration Cockpit is available from S/4HANA Release 1610 in the OnPremise Version.
As it is the first Version, i don’t have too much expectations, but i am sure we will see very interesting updates in the future.
Basically, it is a Web Based Tools to migrate Legacy Data into S/4HANA. It allows to Download predefined Excel Sheet-Templates, so you can “easily” extract legacy data into this format and upload in S/4HANA by using the Migration Cockpit. Basic Mapping Functionality is provided (e.g. Map Unit of Measure Codes and so on) but don’t expect too much here yet.
Target group seems to be smaller and medium businesses (SMB). The handling of the Import Process and Validations are made very easy (“cloud style”)
To Import the Data, the SAP Standard BAPIs are used. There is an error Log provided with information on Warnings or Errors.
As there is already a number of Standard Objects Available (see below)
for the creation of additional Migration Objects see also my Blog
Update 28.9.2017: Added 1709 Standard Content Migration Object List
Update 13.3.2018: Working with Staging Tables see Blog https://blogs.sap.com/2018/03/13/working-with-staging-tables-in-s4hana-migration-cockpit-onpremise/
Update 27.9.2018: https://blogs.sap.com/2018/09/27/s4hana-1809-migration-cockpit-release-news-a-few-other-hints/
Update 12.02.2019: 02/2019: Updated Newsletter with best practices on S/4HANA Migration Cockpit
LTMC Migration Cockpit
LTMOM Migration Object Modeler
url for migration cockpit:
Check CA-GTF-MIG / SV-CLD-MIG for predefined content problem, check CA-LT-MC for tools problem.
use the expert search https://launchpad.support.sap.com/#/mynotes?tab=Search
Overview Presentation: SAP S/4HANA Migration Cockpit
Interactive Click Demo:
Best Practice Explorer S/4Hana OnPremise, Data Management:
Data Migration to S/4HANA from File (BH5)
Data Migration to S/4HANA Enhancements (BH4)
02/2019: Updated Newsletter with best practices on S/4HANA Migration Cockpit:
Update 30.1.2018: check out new note 2596400 – Which Migration Object is available in the Migration Cockpit currently https://launchpad.support.sap.com/#/notes/2596400
|Business Object Name||Area||Business Object Type||Migration Cockpit Object Name||Technical Object Name|
|Activity Types||CO||Master data||Migration of Activity types (FILE2S4)||SIF_LSTAR_CREATE|
|Cost Center||CO||Master data||Migration of Cost centers (FILE2S4)||SIF_KOSTL_MASTER|
|Activity Price||CO||Master data||Migration of Activity prices (FILE2S4)||SIF_ACT_PRICE|
|Internal Order||CO||Transactional data||Migration of Activity prices (FILE2S4)||SIF_INTORDER|
|Profit Center||FI||Master data||Migration of Profit centers (FILE2S4)||SIF_PRCTR_MASTER|
|Bank Master Data||FI||Master data||Migration of Banks (FILE2S4)||SIF_BANK_MASTER|
|Customer Master||FI, SD||Master data||Migration of Customer (FILE2S4)||SIF_CUSTOMER|
|Vendor Master||FI, MM-PUR||Master data||Migration of Vendor (FILE2S4)||SIF_VENDOR|
|Customer Open Items||FI||Transactional data||Migration of Customer open items (FILE2S4)||SIF_AR_OPEN_ITEM|
|Vendor Open Items||FI||Transactional data||Migration of Vendor open items (FILE2S4)||SIF_AP_OPEN_ITEM|
|Fixed Asset incl. Balances||FI-AA||Master data + Transactional data||Migration of Fixed assets (FILE2S4)||SIF_FIXED_ASSET|
|G/L Account Balances||FI||Transactional data||Migration of G/L balances (FILE2S4)||SIF_GL_OPEN_ITEM|
|G/L Account Open Items||FI||Transactional data||Migration of G/L open items (FILE2S4)||SIF_GL_OPEN_ITEM|
|Exchange Rate||FI||Master data||Migration of Exchange rates (FILE2S4)||SIF_EXCH_RATE|
|Inventory Balances||MM-IM||Transactional data||Migration of Material inventory balances (FILE2S4)||SIF_INVENTORYBAL|
|Material Master||LO-MD||Master data||Migration of Materials (FILE2S4)||SIF_MATERIAL|
|Material Long texts||LO-MD||Master data||Migration of Material long texts (FILE2S4)||SIF_MAT_LONGTEXT|
|Material Consumptions||LO-MD||Master data||Migration of Consumptions (FILE2S4)||SIF_MAT_CONSUMP|
|Purchasing Info Record||MM-PUR||Master data||Migration of Purchasing info records (FILE2S4)||SIF_PURCH_INFREC|
|Purchase Order||MM-PUR||Transactional data||Migration of Purchase orders (only open) (FILE2S4)||SIF_PURCH_ORDER|
|Pricing Conditions||SD, CO, MM-PUR||Master data||
Migration of Pricing conditions (FILE2S4)
(Currently Cloud Only)
|Contracts (Purchasing)||MM-PUR||Transactional data||Migration of Purchasing contracts (FILE2S4)||SIF_CONTRACTS|
|Source List||MM-PUR||Transactional data||Migration of Source lists (FILE2S4)||SIF_SOURCE_LIST|
|Sales Order||SD||Transactional data||Migration of sales orders (only open) (FILE2S4)||SIF_SALES_ORDER|
|Batches||QM, SD, PP-PI||Master data||Migration of Batches (FILE2S4)||SIF_BATCHES|
|Bill of Material (BOM)||PP||Master data||Migration of Bill of materials (FILE2S4)||SIF_BOM|
|Work Center||PP, QM||Master data||Migration of Work centers (FILE2S4)||SIF_WORK_CNTR|
|Equipment||PM||Master data||Migration of Equipment (FILE2S4)||SIF_EQUIPMENT|
|Equipment Task List||PM||Master data||Migration of Equipment task lists (FILE2S4)||SIF_EAM_TASKLIST|
|Functional Location||PM||Master data||Migration of Functional locations (FILE2S4)||SIF_FUNC_LOC|
|Characteristics||CA||Master data||Migration of Characteristics (FILE2S4)||SIF_CHARACT|
|Classes||CA||Master data||Migration of Classes (FILE2S4)||SIF_CLASS|
Object List in 1709:
|Business Object Name||Area||Business Object Type||Migration Cockpit Object Name||Technical Object Name|
|Activity Type||CO||Master data||Activity type||SIF_LSTAR_CREATE|
|Cost Center||CO||Master data||Cost center||SIF_KOSTL_MASTER|
|Activity Price||CO||Master data||Activity price||SIF_ACT_PRICE|
|Internal Order||CO||Transactional data||Internal order||SIF_INTORDER|
|Profit Center||FI||Master data||Activity price||SIF_PRCTR_MASTER|
|Bank Master Data||FI||Master data||Bank||SIF_BANK_MASTER|
|Customer||FI, SD||Master data||Customer||SIF_CUSTOMER|
|Customer||FI, SD||Master data||Customer – extend existing record by new organizational levels||SIF_CUST_EXTEND|
|Supplier||FI, MM-PUR||Master data||Supplier||SIF_VENDOR|
|Supplier||FI, MM-PUR||Master data||Supplier – extend existing record by new organizational levels||SIF_VEND_EXTEND|
|Accounts Receivable (Customer) Open Item||FI||Transactional data||Accounts receivable (Customer) open item||SIF_AR_OPEN_ITEM|
|Accounts Payable (Vendor) Open Item||FI||Transactional data||Accounts payable (Vendor) open item||SIF_AP_OPEN_ITEM|
|Fixed Asset||FI-AA||Master data + Transactional data||Fixed asset incl. balances||SIF_FIXED_ASSET|
|G/L Account Balance||FI||Transactional data||G/L balance||SIF_GL_BALANCES|
|G/L Account Open/Line Item||FI||Transactional data||G/L open/line item||SIF_GL_OPEN_ITEM|
|Exchange Rate||FI||Master data||Exchange rate||SIF_EXCH_RATE|
|Inventory Balance||MM-IM||Transactional data||Material inventory balance||SIF_INVENTORYBAL|
|Material Master||LO-MD||Master data||Material||SIF_MATERIAL|
|Material Master||LO-MD||Master data||Material long text||SIF_MAT_LONGTEXT|
|Material Master||LO-MD||Master data||Material consumption||SIF_MAT_CONSUMP|
|Material Master||CO||Master data||Exceptional case: Material Price Chng for global currencies||SIF_MATPRICE_CHG|
|Material Master||MD||Master data||Material – extend existing record by new organizational levels||SIF_MAT_EXTEND|
|Material Master||CA-CLF||Master data||Material classification||SIF_CLF_MAT|
|Material Master||QM||Master data||Material inspection type *||SIF_INSP_TYPE|
|Material Master||SLL-LEG||Master data||Material – Commodity code||SIF_MAT_COMMCODE|
|Purchasing Info Record||MM-PUR||Master data||Purchasing info record with conditions||SIF_PURCH_INF_V2|
|Purchasing Info Record||MM-PUR||Master data||Purchasing info record||SIF_PURCH_INFREC|
|Purchase Order||MM-PUR||Transactional data||Purchase order (only open PO)||SIF_PURCH_ORDER|
|Pricing Condition||SD, CO, MM-PUR||Master data||Pricing condition||SIF_CONDITIONS|
|Contracts (Purchasing)||MM-PUR||Transactional data||Purchasing contract||SIF_CONTRACTS|
|Scheduling Agreement||MM-PUR||Transactional data||Scheduling Agreement||SIF_SCHED_AGRMNT|
|Source List||MM-PUR||Transactional data||Source list||SIF_SOURCE_LIST|
|Sales Order||SD||Transactional data||Sales order (only open SO)||SIF_SALES_ORDER|
|Sales Contract||SD||Transactional data||Sales contract||SIF_SD_CONTRACT|
|Batch||QM, SD, PP-PI||Master data||Batch (if Batch is unique at material level)||SIF_BATCHES|
|Bill of Material (BOM)||PP||Master data||Bill of material||SIF_BOM|
|Work Center||PP, QM||Master data||Work center||SIF_WORK_CNTR|
|Functional Location||PM||Master data||Functional location||SIF_FUNC_LOC|
|Maintenance Task List||PM||Master data||Equipment task list||SIF_EQUI_TL|
|Maintenance Task List||PM||Master data||Functional location task list||SIF_FLOC_TL|
|Maintenance Task List||PM||Master data||General task list||SIF_GENMT_TL|
|Maintenance Plan||PM||Master data||Maintenance plan||SIF_MAINT_PLAN_2|
|Commercial Project Management (CPM)||CA-CPD||Master data||CPM project||SIF_PROJECT|
|Inspection method||QM||Master data||Inspection method||SIF_INSP_METHOD|
|Master inspection characteristic||QM||Master data||Master inspection characteristic||SIF_MSTR_CHAR|
|QM catalog code group/code||QM||Master data||QM catalog code group/code||SIF_QM_CATALOG|
|Inspection Plan||QM||Master data||Inspection plan||SIF_INSP_PLAN|
|QM selected set||QM||Master data||QM selected set||SIF_SELECTED_SET|
|QM selected set code||QM||Master data||QM selected set code||SIF_SELSET_CODE|
|TRM – Financial Transaction||FI-FSCM-TRM-TM||Transactional data||TRM – Foreign exchange spot/forward transaction – contract||SIF_TR_FX_TR|
|TRM – Financial Transaction||FI-FSCM-TRM-TM||Transactional data||TRM – Foreign exchange swap – contract||SIF_TR_FX_SWAP|
|TRM – Financial Transaction||FI-FSCM-TRM-TM||Transactional data||TRM – Interest rate instrument||SIF_TR_IR_INSTR|
|TRM – Financial Transaction||FI-FSCM-TRM-TM||Transactional data||TRM – Interest rate swap||SIF_TR_IRDE_SWAP|
Nice: Sample Migration Templates (Excel Examples)
(currently for S/4HANA Cloud only but still helpful)
FAQ Note on Migration Cockpit
In the first Screen you can create or open a Migration Project.
then you can activate one or multiple migration objects
Now Open the Migration Object
you can look at the documentation of the migration object
you can Download an Excel Template.
Now fill the Excel with you data
and Upload into the Migration Cockpit
select and activate the File
now start Transfer (migrate to S/4 Hana):
First the Data is validated
when finished 100 %, click on close
now you can see the notifications (warnings/error messages):
Choose next to perform the Value Mappings (Convert Values)
if a value from the excel sheet is found for the first time, you have to confirm or add a value mapping:
enter a new Value (EV_xxx) and/or click on confirm
now click on next for the simulation and then next for the import (same procedure as validation)
all actions are performed in background (as a batch-job/SM37), but you can wait until process is finished 100 % and then immediately see the results or let it run in background and come back later.
The Excel Templates are in XML Format
it looks like this
<VERSION dt:dt=”string”>S4CORE 101 – 06.01.2017</VERSION>
<SYSTEM dt:dt=”string”>EAD / 700</SYSTEM>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>D1-100011-02</Data></Cell>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>EN</Data></Cell>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>ASF1400</Data></Cell>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>E</Data></Cell>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>9999</Data></Cell>
<Cell ss:Index=”7″ ss:StyleID=”s79″><Data ss:Type=”String”>X</Data></Cell>
<Cell ss:Index=”9″ ss:StyleID=”s79″><Data ss:Type=”String”>98</Data></Cell>
<Cell ss:Index=”11″><Data ss:Type=”String”>01</Data></Cell>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>PCE</Data></Cell>
<Cell ss:Index=”14″ ss:StyleID=”s79″><Data ss:Type=”String”>10</Data></Cell>
you can find several documentations in the internet:
i faced problems with ‘SPACE’ for empty columns, they should be <null> otherwise the ss:Index gets confused and the Values are linked to the wrong columns when importing into the migration cockpit, even if they are in correct order
It helps if you are familiar with the Standard BAPI Structures and SAP Input Data (for example how to create a material master)
Abap Skills are not required, but ABAP Debugging skills are useful for the Root Cause Analysis in cases where the Error Log isn’t enough.
The BAPI used for the Data Inport can be found in Transaction LTMOM
you can also see how the input fields are mapped.
currently i was not able to change the standard mappings, i can only add customer fields.
you can set an external Breakpoint (external as the import is always performed by a batch job)
here you can also save the data (after mapping/conversion) as testdata for SE37 (right click on toolbox) if you need to do some troubleshooting
in some cases i added an ‘implicit enhancement’ at begin of function (ABAP Enhancement Concept) in the importing BAPI to change the conversion.
(quick and dirty?)
Generated ABAP Objects
The Migration Cockpit generates ABAP Function Modules for the Conversion and the Import.
These can be Debugged (or maybe even “enhanced”?)
if you come from LSMW or other ABAP Migration Tools you will find yourself familiar shortly.
*” VALUE(IM_ALLOG) TYPE DMC_ALLOG OPTIONAL
*” VALUE(IM_DEBUG) TYPE BOOLEAN OPTIONAL
*” VALUE(IM_DEBUG_LEVEL) TYPE CHAR1 OPTIONAL
*” VALUE(IM_TEST_MODE) TYPE BOOLEAN OPTIONAL
*” VALUE(IM_ROLLBACK) TYPE BOOLEAN OPTIONAL
*” VALUE(IM_VALIDATE) TYPE BOOLEAN OPTIONAL
* Project : ZSIN_MIG_001
* Subproject : ZSIN_MIG_001
* Migration Object : Z_MATERIAL_001
* Layer : Conversion layer
* Generated : 13.02.2017 07:53:07 by SENS_MM
* Generate time related processing = X
* Generate interlinkage processing = –
* Generate IMPORT FROM MEMORY = –
* Generate EXPORT TO MEMORY = –
* Generate LDU initialize = X
* Generate Call next function module = –
*** <__UNIT_0001__> ************************************
*** Targetstructure : HEADER
*** Primary relation source : S_MARA
*** Primary relation type : 1:1
*** Primary relation number : 0001
* CONVERSION: call BEGIN OF LOOP routine
* CONVERSION: Primary relation read
” init receiver work area
LOOP AT _IT_S_MARA
_actual-sstruct1 = ‘S_MARA’.
_actual-sddicname = ”.
* CONVERSION: Init receiver work area
CLEAR _WA_HEADER .
* CONVERSION: Init SKIP_TRANSACTION
_FLG_SKIP_TNX_ = FALSE.
* CONVERSION: Increment transaction count
<TNX_COUNT> = <TNX_COUNT> + 1.
* CONVERSION: init SKIP_RECORD flag
_FLG_SKIP_REC_ = FALSE.
* CONVERSION: call BEGIN OF RECORD routine
* CONVERSION: call field processing routine
IF _FLG_SKIP_REC_ = FALSE.
* BWP: Increment record count
HEADER_NO = HEADER_NO + 1.
IF _FLG_SKIP_REC_ = FALSE.
*— RECEIVER: NOAPPLLOG
*— RECEIVER: FUNCTION
*— RECEIVER: IND_SECTOR
*— RECEIVER: MATL_TYPE
*— RECEIVER: BASIC_VIEW
*— RECEIVER: SALES_VIEW
*— RECEIVER: PURCHASE_VIEW
*— RECEIVER: MRP_VIEW
*— RECEIVER: FORECAST_VIEW
*— RECEIVER: WORK_SCHED_VIEW
*— RECEIVER: PRT_VIEW
*” VALUE(IM_TEST_MODE) LIKE EDITSTRUC-CHANGED OPTIONAL
*” VALUE(IM_BEHAVIOUR) TYPE NUM1 DEFAULT 1
*” VALUE(ET_MESSAGES) TYPE DMC_FM_MESSAGES_T
*” VALUE(CT_PAYLOAD) TYPE DMC_PAYLOAD_TAB
*” VALUE(XT_RUN_STAT) TYPE DMC_T_RUN_STAT OPTIONAL
* Project : ZSIN_MIG_001
* Subproject : ZSIN_MIG_001
* Migration Object : Z_MATERIAL_001
* Layer : Outer layer out (Function Module)
* Generated : 13.02.2017 07:53:34 by SENS_MM
Job-Controller Functions: (for Debugging purposes)
FORM EXECUTE_LOAD SAPLDMC_DTL LDMC_DTLU25
METHOD START_ACTIVITY CL_DMC_WDA_MIG_JOBS===========CP CL_DMC_WDA_MIG_JOBS===========CM003
Structure XXXX: Number of recipient records generated 0000000000 (or less than in input file)
the Migration Cockpit is storing all created objects in Table DMC_FM_RESTART, so if your object number, for example material number, is in this table, it will be skipped and not imported again.
you can delete the entry with transaction code se16
also if a job with the name /1LT/LOAD… is scheduled or already running, the import will not start
(but shows no error message)
verify with SE37
Check from ABAP Coding
START_DATA_LOAD (CL_DMC_WDA_MIG_CONTR) CHECK cl_dmc_act_rec=>get_active_and_scheduled_jobs( iv_ext_id = lv_ext_id
iv_activity_type = cl_dmc_act_rec=>…
for Material Views Check Note
2145027 – FAQ: Maintenance status in data transfer
Export Data from R/3 Source System? in the online help there is a remark: In the ABAP-based SAP source system, you have installed the DMIS add-on. You can download the add-on from the SAP Software Download Center at http://support.sap.com/swdc using the following path: Installations and Upgrades A – Z Index L SAP LT Replication Server SAP LT Replication Server 2.0 .
how can i export the data for the Migration Cockpit?
Best-Practice how to fill the Excel/XML Files with legacy data
The Excel-Templates are very nice, Examples with Best-Practice Data would help understanding how to fill the values.
how to create Additional Mapping Rules like we know this from LSMW?
Create Additional Migration Objects
Create Contact Persons for Customers (i could assign them to the Customer, but i had to to a workaround to create the Contact Person’s Business Partner Number)
Mass/Data, Performance, parallel Processing, memory consumption, limitations…
strangely i could not find any oss notes, nor any blogs, is nobody using the tool yet?
so maybe i will write another Blog…
we are migrating Material Master and getting the error message as :
Duplicate entries for parameter MATERIALDESCRIPTION
Parameter MATERIALDESCRIPTION contains records with a duplicate key.
Delete the records that have a duplicate key in parameter MATERIALDESCRIPTION, then call BAPI_MATERIAL_SAVEREPLICA again.
There are at two places where we update the description one in Basic Data and another in Material Description tab in excel template. Both tabs we have updated the same name of material and getting the above error.
Please could you help to resolve the issue.
You only put material descriptions on the "Material Descriptions" tab that are in a different language than those you put on the "Basic Data" tab. If you're creating materials with only one language you don't need to put anything on the "Material Descriptions" tab.
Is migration cockpit is also available for SAP ECC Data Migration ???
The Migration Cockpit is part of S/4HANA. Hence, you can load data into S/4HANA but not into SAP ECC.
I am using LTMC for Legacy Data Migration but while uploading i am unable to understand what is
the posting logic that the system is using as there is no field of posting key i am unable to identify
the which Gl account is getting debited & which is getting credited. Request you to help on the same
first of all thanks to this exciting BLOG.
We are now building migration scenarios on S/4HANA Release 1610 on premise.
I started with a moigration example on master material.
I could start the MC via LTMC.
Then I created an Project and sub project and used the material master migration object: Migration of Materials (FILE2S4).
I could download the template file and I tried to upload the file wit data for migration an wanted to start migration.
But then something went wrong.
Now I can start the LTMC again, but I always jump into one screen, where I couldn't jump or move to anywhere because of missing dat:
So I can't do anthing. I checked the tables: DMC_FM_RESTART and the jobs with name /1LT/*, but there are no entries.
Could you please help me, because the call of the transaction LTMC leads me to this screen, where I didn't get any clue, what I can do to restart the migration project from the scratch. In LSMW you always could do this without problems.
I stucked on this screen and can't us the cockpit any longer.
Could you please help me ?
Regards Frank Meyer
Hi Frank, The Screenshot looks really very empty, this is not a normal behaviour, what FPS Patch Level is you 1610?
I think you can create a new Migration Project and then it should be filled again (you can upload you template here)
thanks to your fast answer.
I think we are using the Patch Level 01 (01 (02/2017) FP).
My problem is: if start the LTMC, I only see the screen above and I can not move to anywhere else. I am stucked.
Do you have an clue, what I can I do to restart an new migration project ?
Thank you and best regards
log on with an another user and start LTMC. Then proceed with your user - the entry screen should be reset.
thanks a lot for your help.
Yes this has helped.
But I couldn't go on with the original user.
Only with the new user I could start the LTMC in a proper mode.
On the old user the same behaviour remains (??? do you have any reason for this ???)
Thank you and best regards
can you try to delete all history in your browser?
best regards, sybille
please check if there are dumps in S4 system like in oss note 2393469
You could try to delete user parameters in netweaver.
Activate service wd_analyze_config_user in SICF and test it. Select entries for your original not working user id.
If tehre are entries, delete them and try LTMC again.
You can go to personalization and select the Standard view, it will solve your problem for the current user.
We are working on a greenfield migration to S/4HANA, currently focusing on Cost Centers and Profit Centers.
In the Migration Cockpit, the documentation for Cost Centers mentions:
However, I don't see any Migration object for Cost Center Groups or Profit Center Groups.
As Master Data, these are also not available as BC Sets.
What do you recommend for the migration of hierarchies like Cost Center Groups and Profit Center Groups?
Hi Luz Mery,
I had the same problem two weeks ago and i have passed that error by selecting the customer view if i am going to use a customized Migration object (I created it ) and the On Premise when i was using standard Object (Created by SAP) but i am not sure if this is the right procedure.
What i have been unable to find out is where to write a code if i want to get a field from external table for example or take the input and perform on it any kind of Mathematical function , Does anyone have any idea ?
when you download the template where they have provided standard field and if you want more field then there is + icon you can add those and sane need to extend in excel sheet template. then try to upload and share the result with us.
thanks for your answer.
I do not know if it is useful to write the code you need as a conversion rule or to make an enhancement in the standard functions module that maps the data.
Thanks Luz Mery
I was trying to post Customer data into S/4 HANA using Migration cockpit. Whenever i am posting data with "sales data" it is giving an error named "system error occurs while calling functional module in target systems".
Without sales data we are able to post it successfully.
Please help us to solve this.
Can you share the error in more detail or screenshot of the error. Also check the ST22 for any dump.
it was pretty most helpful document to whom which want to be migrated into ECC to S/4HANA 1610 & latest version 1709.
author have explored deep the topic where abap will come into the picture.
what list of objects are including into S/4HANA 1709 Release.
based on instruction given in this blog we have tested the migration scenario ECC to S/4HANA by sandbox system without issue.
so once again want to say its more helpful blog as this is new technology which is in demand as per my information SAP has achieved the milestone as SAP done migration for approx. 1000 customer.
I am creating a migration object using LTMOM (S/4HANA 1709) , I follow all the recommended steps. When assigning the conversion rules, I get an error when entering a standard rule, for example CVT_MATKL.
If I use the search help to select some, the system does not display all the rules, just some
Does anyone have any ideas
Did you check under Rules> Field based rule.
I'd like to comment an issue that I'm facing since yesterday. I created a Migration Object in LTMOM transaction for BAPI: BAPI_QPGR_SAVEREPLICA. I know that already exists one for it, but I wanted to create a new one to understand a little bit more how to map source and target structures.
I stablished a debug to see all the mappings and everything was fine in LTMC for my first load; however if I try to load new data within a new excel template, in debug I see the program is taking the values of the first load and no respect the new ones. What can I do to resolve this? There's something I'm missing in LTMOM?
I also could see that the loop sentence that assign values for BAPI use the sentence IMPORT...FROM DATA BUFFER.
I aprecciate your support.
Were you able to resolve the issue you mentioned? If yes, please suggest. I'm having the same issue.
I was trying to use SIF_BOM object for BOM upload, but every BOM quantity was uploaded w/o decimals (even if there were lines with decimals in uploading file). Data was formatted as text as templete required. Can you please sugest a solution?
What is user id i should use in external debugging?
The same user that initiates LTMC
first of all let me mention we are using several objects in LTMC already and from our pov it seems to be handy whereas the performance of the WD is the most negative experiance we'ld like to share. The open SAP course was very helpful as well as your link collection in here. Thanks for this easy entrance.
We wonder if there are any plans known if the object of "master recipe" / C201 is going to be considered soon? In current 1709 version we could not find any.
The solution of colleagues might have been used LSMW using "BUS1194" shouldn't be appropriated any more and the data model changed in simplification as well (2267863).
So if I did not miss any alternative, you may add it on a OP-List.
I am having problems with loading the Fixed Assets file of the LTMC
I complete the values of Cumulated Acquisition Value and Accumulated Ordinary depreciation as follows:
When I upload the file in the LTMC, I get the following errors:
Correction to ordinary dep. greater than acc. dep. in area 01
Message no. AA634
The line item cannot be posted, since the correction to ordinary depreciation in area 01 exceeds the cumulative ordinary depreciation.
The error can occur during a transfer, a write-up, or post-capitalization.
Correct your entry.
I also get errors in other areas of valuation that were not loaded:
Correction to ordinary dep. greater than acc. dep. in area 31
Message no. AA634
The line item cannot be posted, since the correction to ordinary depreciation in area 31 exceeds the cumulative ordinary depreciation.
Could someone send me an example of asset loading excel?
Depreciation values must be negative values. E.g. -52777,77
Firstly thanks for such an informative blog.
@Jorg and others:
I need your help with migration object:"Material-extend exiting record to new org level".
We are trying to extend the already existing material to sales org views.
We have created the xml file with material number and sales view details.
We get error that"Material does not exist in Sales Org and distribution Channel"
Also we are mantaining the tax classification for both the countries which is required in material master but still it throws error that tax classification is already mantained for one country, when we remove the entry of it from xml file it throws error that tax classification is insufficiently mantianed.
Can you show us an example to extend the material to sales view that ud be helpful with the example xml file.
Thanks for sharing nice blog.
But it seems Customer migration data template does not contains BP Role so that we can create source customer as business partner in S/4HANA.
How this can be achieved?
I try to add the services tables in Migration object PO, But I have a error when I will activate the Object. Someone had the same error?.
This is the errors:
Error while generating runtime objects for Z_PURCH_ORDER_SE_002
Syntax error in function module /1LT/FSQOLC_700000000000030
Error message: A FORM already exists with the name"_CONVERT_0001_".