Академический Документы
Профессиональный Документы
Культура Документы
Code
Asset Accounting: Classic G/L sFIN
Process / Transaction Name
Asset history sheet Pr.: RAGITT01 S_ALR_87011990
Asset reconciliation ABST ABSTL
Create asset transaction AB01 AB01L
Unplanned Depreciation ABAA ABAAL
Last Retirement on Group Asset ABAKN ABAKNL
Asset Sales Without Customer ABAO ABAOL
Asset Retirement By Scrapping ABAV ABAVL
Balance Sheet Revaluation ABAW ABAWL
Adjustment Posting To Areas ABCO ABCOL
Credit Memo In Year After Invoice ABGF ABGFL
Enter Credit Memo In Year Of Invoice ABGL ABGLL
Investment Support ABIF ABIFL
Manual Depreciation ABMA ABMAL
Manual Transfer Of Reserves ABMR ABMRL
Post-Capitalization ABNA ABNAL
Subsequent Revenue ABNE ABNEL
Subsequent Costs ABNK ABNKL
Miscellaneous Transactions ABSO ABSOL
Transfer From Initial Screen ABUM ABUML
Acquisition From In-House Production ABZE ABZEL
Asset Acquisition Auto. Offset. Posting ABZO ABZOL (sFIN)
Acquisition From Affiliated Company ABZP ABZPL
WRITE-UP ABZU ABZUL
R2R:
Replacements by new GL
New G/L/
Process / Transaction Name Classic G/L SFIN
Tr.: F.01 Tr.: FAGLF03
Pr:
Comparison: Documents/ transaction figures Pr.: SAPF190 TFC_COMPARE_VZ
G/L account balances display Tr.: FS10N Tr.: FAGLB03
Line item display G/L Tr.: FBL3N Tr.: FAGLL03
Tr.: FAGLL03H
Line item display GL – HANA optimized N/A Optional!
CFR:
Replacements by new GL
New G/L/
Process / Transaction Name Classic G/L SFIN
Tr.: FAGLGVTR
Balance carry forward Tr.: F.16 Pr: SAPFGVTR
Tr.: FAGL_FCV
Foreign currency valuation Tr.: F04N Pr.: FAGL_FCV
Pr.: SAPF100
Tr.: FAGLF101
Regrouping Tr.: F101 Tr.: FAGLF101
N/A FGI3 reports
Note: classic
RFBILA00 can still
be used under
Financial Statement NEWGL and SFIN Optional!
GCO:
New transactions by sFIN
Process / Transaction Name Classic G/L SFIN
N/A FBL5H
Customer line items
Settlement-Order & Project VA88 / VA88H (Order)- the one ending with H is optimized for
HANA and is new tcod
CJ8G / CJ8GH (Project)
Center
COAT COAT
Below you can find an overview about replaced, changed and new transactions in SAP S/4HANA
FINANCE.
Please note: all other transactions didn’t change, e.g. FBL1N, FBL5N, AS01, AS02 etc. Here just the
changes are mentioned (replacements or new transactions that are available with new GL or sFIN).
FAGLL03H
Note: classic FBL3N can still be used under new GL and sFIN but just for entry view not for GL view!
FBL1H
Note: classic FBL1N can still be used under new GL and sFIN. FBL1H is optional.
FBL5H
Note: classic FBL5N can still be used under new GL and sFIN. FBL5H is optional.
FGI3
Note: classic RFBILA00 can still be used under newGL and sFIN. FGI3 is optional, several reports are
available with this transaction.
Changed transactions in CO
Add Base Planning Object KKE1 CKUC used only as embedded Function in Product cost for Sales order
Compare Base Object - Unit Cost Est KKEC CKUC used only as embedded Function in Product cost for
Sales order
PCA Line Item Browser KE5Z KE5ZH Wave 0 use KE5Z; further investigation in next waves
Cost Centers: Actual Line Items KSB1 KSB1N Wave 0 use KSB1; further investigation in next waves
Orders: Actual Line Items KOB1 KOB1N Wave 0 use KOB1; further investigation in next waves
Controlling Documents: Actual KSB5 KSB5N Wave 0 use KSB5; further investigation in next waves
Act. Settlment: Int.-/Maint. Orders KO8G KO8GH Ko8GH recommended to use in Wave 0
Actual Settlement: Sales Orders VA88 VA88H VA88H recommended to use in Wave 0
Actual Results Analysis: Sales Ordrs KKAK KKAKH use transaction KKAK; KKAKH do not cover the
whole functionality
SAP-ECC → is —ERP Central Component— Solution from SAP. It is part of older SAP Business
Suite (consists of ERP/CRM/SRM/PLM) from SAP. The latest version from SAP is ECC 6.0 (EHP7).
ECC 6.0 could be installed on any RDBMS (ORACLE/DB2/DB6/MSSQL etc.)
SAP-HANA →is SAP’s In-Memory Solution based on Proprietary Database. It is supposed to give
high performance since the DB is In-memory
S/4HANA → Is the new 4th generation Business Suite offered by SAP only on HANA Database. It is
optimized to take benefit from HANA Platform and provide simplification across processes.
“S” stands for “Simplification” and “4” stands for 4th generation or “next” generation. S/4HANA is
available in On-Premise and Cloud. It also offers SAP-FIORI as SAP Mobility Option for end users
front-end.
S/4 HANA is the latest version of the SAP enterprise software where SAP has moved away
from primarily on-premise based ECC version . The difference between both the versions are :
ECC version has a choice of database of Oracle, SQL server or SAP ‘s HANA but for S/4 HANA , the
underlying DB can only be SAP’s HANA DB
S4HANA versions for Finanace & logistics have much lesser tables than ECC So, it ‘s about making
the product more compact & easier & faster to implement .
S4HANA is SAP’s answer to various best of the breed cloud-based products and taking the product to
more SMB companies . ECC version was more of an on-premise product which SAP was trying to
adapt to today’s mobile first, cloud first environment . S4HANA is a radically different product to
adapt to this new paradigm shift.
https://www.youtube.com/watch?v=PEPDh4bwGLs&feature=youtu.be
SAP S/4HANA Migration Cockpit Step by Step process
Hello All,
With my recent experience in SAP S/4 HANA Migration cockpit in my role as SAP Finance
consultant, where we migrated Asset balances,Exchange rates and GL balances with LTMC XML
template, i would like to explain the step by step process of using LTMC Tcode.
There have been many blogs explaining the usage of Migration cockpit of SAP. In this blog, i am
trying to explain the step by step process of how to use the transaction code LTMC.
The use of LSMW for data load to SAP S/4HANA is not recommended, hence an SAP Migration
cockpit has to be used for migrations.
By end of this blog you will be able to browse through the LTMC tcode and understand the process
and functions of Migration Cockpit.
2)User friendly and predefined process, with validation and simulation in place .
3)Useful for Master Data Migrations,open item migration, balance migrations,Asset migrations,etc.
Steps:
Creation of project Name
All the available objects are copied automatically as per below screenshot.
For the purpose of Demo i have selected migration of GL balances .
Click on download template and the template will look like below
Once you fill the template, please upload the same using upload icon.
To correct the errors you to click on each error item on the name field
Update the required document type in the customizing and click on save
Similarly clear all the error by selecting each line and saving the same.
Click on Next
Click on Next for update run
In My next blog i would try to give some Insights on new functionalities of S/4 HANA around the
transaction Code SE16H ,Use of Worklist in Assets and CO-PA Realignment.
Getting started with the S/4Hana Migration Cockpit
(OnPremise)
Overview
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
https://blogs.sap.com/2017/06/20/discover-the-s4hana-migration-cockpit-migration-object-modeler-
onpremise-nltmom/
Update 28.9.2017: Added 1709 Standard Content Migration Object List
SAP Notes:
Check CA-GTF-MIG / SV-CLD-MIG for predefined content problem, check CA-LT-MC
for toolsproblem.
use the expert search https://launchpad.support.sap.com/#/mynotes?tab=Search\
Existing Documentation
Added 6.7.2017:
https://cp.hana.ondemand.com/dps/d/preview/76a9ec56a9eb6138e10000000a44147b/1610%20001
/en-US/ab242557ea516359e10000000a44147b/content.htm
SAP Help
https://help.sap.com/doc/PRODUCTION/bf1d5c82ea1c45ba8f1d7d1f7757f04d/1610%20001/en-
US/frameset.htm?8f97f0b407024465a283809f0bbe000c.html
https://help.sap.com/doc/PRODUCTION/bf1d5c82ea1c45ba8f1d7d1f7757f04d/1610%20001/en-
US/frameset.htm?9a02076c76354f6a93aefc9bdf943e68.html
Best Practice Explorer S/4Hana OnPremise, Data Management:
Name Name
(FILE2S4)
(FILE2S4)
Business Object Area Business Object Type Migration Cockpit Object Name Technical Object
Name Name
(FILE2S4)
(FILE2S4)
Vendor Master FI, MM-PUR Master data Migration of Vendor (FILE2S4) SIF_VENDOR
Items (FILE2S4)
Vendor Open Items FI Transactional data Migration of Vendor open items SIF_AP_OPEN_ITEM
(FILE2S4)
Fixed Asset incl. FI-AA Master data + Migration of Fixed assets (FILE2S4) SIF_FIXED_ASSET
Balances
G/L Account Open FI Transactional data Migration of G/L open items SIF_GL_OPEN_ITEM
Items (FILE2S4)
Business Object Area Business Object Type Migration Cockpit Object Name Technical Object
Name Name
(FILE2S4)
balances (FILE2S4)
Material Long texts LO-MD Master data Migration of Material long texts SIF_MAT_LONGTEXT
(FILE2S4)
Consumptions (FILE2S4)
Purchase Order MM-PUR Transactional data Migration of Purchase orders (only SIF_PURCH_ORDER
open) (FILE2S4)
Pricing Conditions SD, CO, Master data Migration of Pricing conditions SIF_CONDITIONS
(FILE2S4)
MM-PUR
(Currently Cloud Only)
(Purchasing) (FILE2S4)
Business Object Area Business Object Type Migration Cockpit Object Name Technical Object
Name Name
Source List MM-PUR Transactional data Migration of Source lists (FILE2S4) SIF_SOURCE_LIST
open) (FILE2S4)
Batches QM, SD, PP- Master data Migration of Batches (FILE2S4) SIF_BATCHES
PI
(BOM) (FILE2S4)
(FILE2S4)
Equipment Task List PM Master data Migration of Equipment task lists SIF_EAM_TASKLIST
(FILE2S4)
(FILE2S4)
(FILE2S4)
Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object
Name
PUR
Supplier FI, MM- Master data Supplier – extend existing record SIF_VEND_EXTEND
Name
Fixed Asset FI-AA Master data + Fixed asset incl. balances SIF_FIXED_ASSET
Transactional data
Item
Name
Purchasing Info Record MM-PUR Master data Purchasing info record with SIF_PURCH_INF_V2
conditions
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
MM-PUR
Sales Order SD Transactional data Sales order (only open SO) SIF_SALES_ORDER
Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object
Name
Batch QM, SD, Master data Batch (if Batch is unique at SIF_BATCHES
Maintenance Task List PM Master data Functional location task list SIF_FLOC_TL
Name
Management (CPM)
characteristic
group/code
contract
TRM – Financial FI-FSCM- Transactional data TRM – Foreign exchange swap – SIF_TR_FX_SWAP
TRM – Financial FI-FSCM- Transactional data TRM – Interest rate instrument SIF_TR_IR_INSTR
Transaction TRM-TM
Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object
Name
TRM – Financial FI-FSCM- Transactional data TRM – Interest rate swap SIF_TR_IRDE_SWAP
Transaction TRM-TM
New 04/12/2017:
Nice: Sample Migration Templates (Excel Examples)
https://launchpad.support.sap.com/#/notes/2470789
(currently for S/4HANA Cloud only but still helpful)
Migration Process
In the first Screen you can create or open a Migration Project.
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.
Excel Format
The Excel Templates are in XML Format
it looks like this
<?xml version=”1.0″?>
<?mso-application progid=”Excel.Sheet”?>
<Workbook xmlns=”urn:schemas-microsoft-com:office:spreadsheet”
xmlns:o=”urn:schemas-microsoft-com:office:office”
xmlns:x=”urn:schemas-microsoft-com:office:excel”
xmlns:dt=”uuid:C2F41010-65B3-11d1-A29F-00AA00C14882″
xmlns:ss=”urn:schemas-microsoft-com:office:spreadsheet”
xmlns:html=”http://www.w3.org/TR/REC-html40″>
<DocumentProperties xmlns=”urn:schemas-microsoft-com:office:office”>
<Title>MATERIAL</Title>
<Author>HHE</Author>
<LastAuthor>Heiko Herrmann</LastAuthor>
<Created>2017-01-03T00:00:00Z</Created>
<LastSaved>2017-02-08T14:11:35Z</LastSaved>
<Company>HHE</Company>
<Version>16.00</Version>
</DocumentProperties>
<CustomDocumentProperties xmlns=”urn:schemas-microsoft-com:office:office”>
<APPLICATION dt:dt=”string”>SLO</APPLICATION>
<OBJECT_NAME dt:dt=”string”>MATERIAL</OBJECT_NAME>
<LANGUAGE dt:dt=”string”>D</LANGUAGE>
</CustomDocumentProperties>
<OfficeDocumentSettings xmlns=”urn:schemas-microsoft-com:office:office”>
<AllowPNG/>
<Colors>
<Row ss:AutoFitHeight=”0″>
<Cell ss:StyleID=”s79″><Data ss:Type=”String”>D1-100011-02</Data></Cell>
Import Processing
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?)
Fugr /1LT/S4H500000000000003
INCLUDE /1LT/LS4H500000000000003U01.
“/1LT/S4HIL_500000000000003
INCLUDE /1LT/LS4H500000000000003U02.
“/1LT/S4HOLC_500000000000003
INCLUDE /1LT/LS4H500000000000003U03.
“/1LT/S4HOLO_500000000000003
INCLUDE /1LT/LS4H500000000000003U04.
“/1LT/S4HACS_500000000000003
FUNCTION /1LT/S4HIL_500000000000003.
*”——————————————————————–
*”*”Lokale Schnittstelle:
*” IMPORTING
*” 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
*” EXCEPTIONS
*” INSERT_IT_ERROR
*” LOG_ERROR
*” STOPPED_BY_RULE
*”——————————————————————–
* 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
CLEAR _WA_HEADER.
LOOP AT _IT_S_MARA
INTO _WA_S_MARA
.
CLEAR _actual.
_actual-sstruct1 = ‘S_MARA’.
_actual-sddicname = ”.
* CONVERSION: Init receiver work area
CLEAR _WA_HEADER .
CLEAR l_mapping_error.
* 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.
…
ENDIF.
* CONVERSION: call BEGIN OF RECORD routine
PERFORM _BEGIN_OF_RECORD_0001_.
* CONVERSION: call field processing routine
IF _FLG_SKIP_REC_ = FALSE.
PERFORM _CONVERT_0001_.
ENDIF.
* BWP: Increment record count
HEADER_NO = HEADER_NO + 1.
IF _FLG_SKIP_REC_ = FALSE.
FORM _CONVERT_0002_.
*— RECEIVER: NOAPPLLOG
PERFORM _RULE_MOVE_OP
USING
_WA_VI0001_NOAPPLLOG-NOAPPLLOG
‘X’.
ENDFORM.
FORM _CONVERT_0003_.
*— RECEIVER: FUNCTION
PERFORM _RULE_MOVE_OP
USING
_WA_T01_HEADDATA-FUNCTION
‘INS’.
*— RECEIVER: IND_SECTOR
PERFORM _RULE_CVT_MBRSH_S
USING
_WA_T01_HEADDATA-IND_SECTOR
_WA_S_MARA-MBRSH.
*— RECEIVER: MATL_TYPE
PERFORM _RULE_CVT_MTART_S
USING
_WA_T01_HEADDATA-MATL_TYPE
_WA_S_MARA-MTART.
*— RECEIVER: BASIC_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-BASIC_VIEW
_WA_S_MARA_CUST-INDICATOR_K.
*— RECEIVER: SALES_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-SALES_VIEW
_WA_S_MARA_CUST-INDICATOR_V.
*— RECEIVER: PURCHASE_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-PURCHASE_VIEW
_WA_S_MARA_CUST-INDICATOR_E.
*— RECEIVER: MRP_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-MRP_VIEW
_WA_S_MARA_CUST-INDICATOR_D.
*— RECEIVER: FORECAST_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-FORECAST_VIEW
_WA_S_MARA_CUST-INDICATOR_P.
*— RECEIVER: WORK_SCHED_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
USING
_WA_T01_HEADDATA-WORK_SCHED_VIEW
_WA_S_MARA_CUST-INDICATOR_A.
*— RECEIVER: PRT_VIEW
PERFORM _RULE_SET_X_IF_NOT_INIT_S
FUNCTION /1LT/S4HOLO_500000000000003.
*”——————————————————————–
*”*”Lokale Schnittstelle:
*” IMPORTING
*” VALUE(IM_TEST_MODE) LIKE EDITSTRUC-CHANGED OPTIONAL
*” VALUE(IM_BEHAVIOUR) TYPE NUM1 DEFAULT 1
*” EXPORTING
*” VALUE(ET_MESSAGES) TYPE DMC_FM_MESSAGES_T
*” CHANGING
*” VALUE(CT_PAYLOAD) TYPE DMC_PAYLOAD_TAB
*” VALUE(XT_RUN_STAT) TYPE DMC_T_RUN_STAT OPTIONAL
*” EXCEPTIONS
*” COMMUNICATION_FAILURE
*” SYSTEM_FAILURE
*” NO_AUTHORIZATION
*”——————————————————————–
* 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
further Tips
Structure XXXX: Number of recipient records generated 0000000000 (or less than in input file)
reason:
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
Open Items
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?
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)
strangely i could not find any oss notes, nor any blogs, is nobody using the tool yet?
With my recent experience in SAP S/4 HANA Migration cockpit in my role as SAP Finance
consultant, where we migrated Asset balances,Exchange rates and GL balances with
LTMC XML template, i would like to explain the step by step process of using LTMC Tcode.
There have been many blogs explaining the usage of Migration cockpit of SAP. In this blog,
i am trying to explain the step by step process of how to use the transaction code LTMC.
The use of LSMW for data load to SAP S/4HANA is not recommended, hence an SAP
Migration cockpit has to be used for migrations.
By end of this blog you will be able to browse through the LTMC tcode and understand the
process and functions of Migration Cockpit.
Prerequisite: Web service has to be activated by using T-code SICF
High level Usages and advantages:
1) Standard XML template provided by SAP for each migration object and can be
customized according to requirements.
2) User friendly and predefined process, with validation and simulation in place .
3) Useful for Master Data Migrations,open item migration, balance migrations,Asset
migrations,etc.
4) Preconfigured Business Objects
4) Errors can be corrected on the fly.
Steps:
Creation of project Name
All the available objects are copied automatically as per below screenshot.
For the purpose of Demo i have selected migration of GL balances .
Click on download template and the template will look like below
Once you fill the template, please upload the same using upload icon.
It can be seen that data will first get validated and then converted.
To correct the errors you to click on each error item on the name field
Update the required document type in the customizing and click on save
Similarly clear all the error by selecting each line and saving the same.
Click on Next
SAP S/4HANA Technical. Part 5. Data Migration in S/4HANA via Migration Cockpit
SAP S/4HANA, is SAP Business Suit 4 which is specially designed for HANA
platform. SAP S/4HANA was released in 2015. Earlier versions of SAP business
suits like ERP, CRM, SRM can also run on HANA platform. Now the question
comes, what is need of SAP S/4HANA?
SAP wants to design a simplified business suit that will combine all functionality
of ERP, CRM, SRM, and others into a single HANA system and replacing the
earlier generation of ERP System.
Thus we can say, SAP Business Suite 4 SAP HANA (or SAP S/4HANA) is
a business suite that is built on SAP’s proprietary Operational Database
System and in-memory computing platform called SAP HANA.
DID YOU KNOW, SAP NOW DOES NOT CONSIDER HANA AS JUST AN APPLIANCE, BUT IT IS NOW A PLATFORM TOO?
S/4HANA Editions
1. S/4HANA on Premises
2. S/4HANA on Cloud
SAP S/4HANA, cloud edition covers specific business scenarios for the marketing
line of business and for the professional services industry as well as the most
essential scenarios to run an entire enterprise in the cloud with a digital
core, which includes: finance, accounting, controlling, procurement, sales,
manufacturing, plant maintenance, project system, and product lifecycle
management, plus integration with SAP SuccessFactors Employee Central, SAP
Ariba Network, SAP Hybris Marketing, SAP Fieldglass and SAP JAM.
S/4HANA Implementation
There are 3 different scenarios for how the customer wants to implement
S/4HANA.
In this scenario, the SAP S/4HANA system is implemented, and master and
transactional data are migrated from the legacy system. Depending on the SAP
S/4HANA edition and detailed customer requirements, SAP Landscape
Transformation (SAP SLT) or SAP Data Services Technology is used for the
required data migration.
Following are different options available for data migration in SAP S/4HANA
on premises:
Here we will discuss only S/4HANA Migration Cockpit. For other option, we
will talk in subsequent articles.
S/4HANA migration cockpit is a new migration tool which was initially designed
for S/4HANA cloud edition but now it is also available for 1610 S/4HANA on
premises and later versions.
The migration project is always associated with ‘Transfer ID’. This transfer id is
a unique identifier which facilitates the transfer of projects between different
systems of the landscape. For example, if we transfer migration project from
quality to production system then project transfer id should be same in both
system.
Press create.
For our example, we select Material Migration Object and the following screens
would appear:
After selecting migration object we need to execute the below steps.
Once the template is copied into the project, then any changes to the template
by SAP does not reflect in that project’s template. Here is a sample of the
template file.
Here we can see one file is in orange (yellowish) color, it means this is
a mandatory sheet in which we have to provide data. Others sheets are
optional.
2. Upload file – We can fill legacy data into the downloaded template and then
can upload .XML file in MC for migration. More than one file can also be
uploaded.
3. View and Edit– Once the file has uploaded, we can view data by clicking on
the name of the file and if required we can edit data in the file by clicking on
edit button.
4. Activate – To take the file into next step i.e. start transfer we need to select
that file and click on activate button.
6. Start Transfer – We can start data transfer for active files by clicking on
button ‘start transfer’.
Below screen would appear after start transferring where we need to perform 4
steps
i. Data Validation– Data stored in the staging area is checked against the
mandatory field, type, length.
ii. Value Conversion– Mapping rules can be defined between source to the
target system. For example country code ‘USA’ is set in source system but in
the target system, it should be mapped to ‘US’.
iii. Simulation– Data stored in the staging area is processed by actual BAPIs
but commit is not performed (after all it is simulation/test run). Here we can
find warning and error messages.
iv. Execution/Finish– In this step data is actually posted to SAP HANA system
using relevant BAPI.
After executing all above steps, press FINISH button to commit changes to the
database.
We can validate the output of our load file by going to t-code MM03 (as we
uploaded the material master). Please check the input file and the material data
in S/4HANA matches.
This is how we make use of Migration Cockpit. We can leverage the same steps
for other business objects (viz Business Partners, Cost Center, etc)
migration. The templates would be different, but the fundamentals remain the
same.
This is my first article and I would be excited to read your feedback. Please
write your thoughts in the comment section below. Also, suggest, what would
you like to read more on S/4HANA. I will try to prepare my next article as per
the demand.
SAP S/4HANA Migration Cockpit – tips&tricks
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 Cockpit – Staging Tables
Learn how to personalize your view (e.g. to create an “active view” for your migration
objects): Personalize View
Cloud here
on-premise here
On the right top corner you can access a crop-down list to choose the release you are working on.
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).
MOM: Which function modules to use with newly created migration objects
Notes:
SAP Note 2470789 – “SAP S/4HANA Migration Cockpit – Cloud data migration template
samples”
Videos:
How to: Assign Foreign Key for nested structure (Migration Object Modeler)
UI:
If you use SAPGUI 7.50 we recommand to unflag “SAP Fiori visual theme”
MOM: testing a migration object
When you created your own migraton object using a XML template, you may want to run a
simulation/test. This report for kind of debugging funciontality is availabe from 1709 FPS01.