S/4 HANA T.

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

Controlling Classic G/L sFIN

Add Base Planning Object KKE1 CKUC
Compare Base Object - Unit Cost Est KKEC CKUC
PCA Line Item Browser KE5Z KE5ZH
Cost Centers: Actual Line Items KSB1 KSB1N
Orders: Actual Line Items KOB1 KOB1N
Controlling Documents: Actual KSB5 KSB5N
Project Selection for CJ8GH CJ8V CJ8VH
Generate Settmt Rule: Coll.Proc. CJB1 CJB1H
Actual Settlement: Projects/Networks CJ8G CJ8GH
Act. Settlment: Int.-/Maint. Orders KO8G KO8GH
Actual Settlement: Sales Orders VA88 VA88H
AC: Accrual Posting ZC_VA88 ZC_VA88H
 Functionality Old T-Code / New Tcode

Settlement-Order & Project VA88 / VA88H (Order)- the one ending with H is optimized for
HANA and is new tcod
CJ8G / CJ8GH (Project)

Result Analysis KKAK / KKAKH

WIP Calculation KKAO / KKAOH

Variance Calculation for Cost KSS1 / KSS1H

Center

SAP HANA T-codes

T-codes Description
CJB1H Generate Sttlmt Rule: HANA Optimized

FINS_MIG_MONITOR AC on HANA: Data Migration Monitor

FINS_MIG_MONITOR_UJ AC on HANA: Migration Monitor UJ

FINS_MIG_REGENERATE SAP AC on HANA: Regenerate Views

FINS_MIG_UJ SAP AC on HANA: Data Migration UJ

FLQAH Assignment from Document Chain(HANA)

MDC_BP_IMHANA_BC01 Import BC Set for IM in Hana

MDC_HDB_MTC_DEL Delete generated Hana artefacts

T-codes Description
MDG_GEN_HBA_CR Generate MDG HANA based CR content

MDG_GEN_HBA_CR_EXT Generate MDG HANA based CR content

MDG_HDB_GEN_UI HANA View Generator

RS2HANA_ADMIN Administration ext. SAP HANA views

RS2HANA_CHECK SAP HANA Model Generation Check

RS2HANA_GEN Replicate Authorizations to SAP HANA

RS2HANA_VIEW Settings for SAP HANA Views

RSDHAAP SAP HANA Analysis Process Designer

RSDHAAP_MONITOR SAP HANA Analysis Process Monitor

RSDHATR SAP HANA Transformation

RSDSHANA Manage SAP HANA Remote Subscriptions

RSDSHANAS Overview Realtime Repl. (SAP HANA)

RSOSM BW Search on SAP HANA Maintenance

SEPMH_DG_AIS_SOCC EPM HANA DG 'AIS Soccer'

SEPMH_DG_PAL EPM Data Generator for HANA based PAL

UJHANAMDX BPC HANA MDX Test

UKM_MIG_FINISH Finish FSCM CM migration to S/4 HANA

RSDD_HM_PUBLISH Publish SAP Hana Model

T-codes Description
FOLK FVVI Pop-up for addit.letter print.

DECK Cash Holding Years

SINA SAP BPT: Maintaining Standard Configuration

IMDB App.req: Execute report in background

HDS Initial Screen - HDS

ENGR Periodic Declarations

FWIW Securities information

AIAZ Display Dist. Rule Allocation

LVSM Landscape Verification for SolMan

AD21 Matchcode maintenance (for IMG)

SPRO Customizing - Edit Project

SE11 ABAP Dictionary Maintenance

SE38 ABAP Editor

SM59 RFC Destinations (Display/Maintain)

SE16 Data Browser

SU01 User Maintenance

SE37 ABAP Function Modules

SE80 Object Navigator

SICF Maintaining HTTP Service Hierarchy

T-codes Description
SE71 SapScript form

/BGLOCS/FI_DISTX Assign Output Tax Code:Cash Discount

/BGLOCS/FI_LIABILI Balance Sheet - Liabilities (Bilat.)

/CPD/BILL_PLAN_NO_R Billing Plan Number Range Intervals

/CPD/CHK_ACT_NUM_RNG Number Range for Checklist Items

/CPD/CHK_NUM_RNG Number Range for Checklist Header

/CPD/MC_AUTO_CREATE Automatic Creation of Checklist Item

SWDC Workflow Definition: Administration

PB10 Init.entry of applicant master data

BTREE Overview of BRE Programs

DMC Start DMC Interface

COAT COAT

OPS1 Maintain User Fields

KSI4 Actual Overhead: Cost Centers

CPAS Act. Template Alloc.: Bus. Processes

IMCC IM Summarization: Curr. transl. type

CJO8 Overhead COMM: Projects Ind.Pro.

BD36 Send Business Processes

CAC5 Define Customer Fields

T-codes Description
KSP4 Plan Overhead: Cost Centers

VORP Repairs procedure: Shorttext trans.

OODA Online Process

RSMIGRHANADB Conversion to In-Memory Optimized

/IWBEP/REG_MODEL Maintain Model

/IWBEP/REG_SERVICE Maintain Service

/AIF/CUST_FUNC Define Custom Functions

/AIF/CUST_HINTS Define Custom Hints

/AIF/CUST_LINK Define Custom Data Links

SAP S/4HANA FINANCE New Transaction Codes

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).

Replaced transactions in GL/ AP/ AR

Description OLD NEW Comment

Balance Carry Forward F.16 FAGLGVTR

Foreign Currency valuation F04N/ F.05 FAGL_FCV

Regrouping F101 FAGLF101

Comparison: Documents/ transaction figues

F.01 FAGLF03

G/L account balances display FS10N FAGLB03

Line item display G/L FBL3N

FAGLL03H

Note: classic FBL3N can still be used under new GL and sFIN but just for entry view not for GL view!

New transactions in GL/ AP/ AR

Description OLD NEW Comment

Vendor line items FBL!N

FBL1H

Note: classic FBL1N can still be used under new GL and sFIN. FBL1H is optional.

Customer line items FBL5N

FBL5H

Note: classic FBL5N can still be used under new GL and sFIN. FBL5H is optional.

Transfer CO documents from worklist to FI (Real-time – integration) N/A FAGLCOFIFLUP

Financial Statement N/A

FGI3

Note: classic RFBILA00 can still be used under newGL and sFIN. FGI3 is optional, several reports are
available with this transaction.

Line item display GL – HANA optimized N/A FAGLL03H Note: optional

Changed transactions in CO

Description OLD NEW Comment

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

Project Selection for CJ8GH CJ8V CJ8VH

Generate Settmt Rule: Coll.Proc. CJB1 CJB1H

Actual Settlement: Projects/Networks CJ8G CJ8GH CJ8GH recommended to use in Wave 0

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

AC: Accrual Posting ZC_VA88 ZC_VA88H ZC_VA88H recommended to use in Wave 0

Actual Results Analysis: Sales Ordrs KKAK KKAKH use transaction KKAK; KKAKH do not cover the
whole functionality

Replaced transactions in Asset Accounting

Description OLD NEW

Asset reconciliation ABST ABSTL

Create asset transaction AB01 AB01L

Unplanned depreciation ABAA ABAAL

Last Retirement on Group Asset ABAKN ABAKNL

Asset Sale 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 ABUM ABUML

Acquisition from in-house production ABZE ABZEL

Asset acquis. autom. offset. posting ABZO ABZOL

Acquistion from affiliated company ABZP ABZPL

Write-up ABZU ABZUL

Replaced reports in Asset Accounting

Description OLD NEW

Asset History Sheet Program RAGITT01 Program RAGITT_ALV01

Asset Transactions Program RABEWG01 Program RABEWG_ALV01

Asset Acquisitions Program RAZUGA01 Program RAZUGA_ALV01

Asset Retirements Program RAABGA01 Program RAABGA_ALV01

Intercompany Asset Transfers Program RAUMBU01 Program RAUMBU_ALV01

Directory of Unposted Assets Program RAANLA01 Program RAANLA_ALV01

Net Worth Valuation Program RAVERM01 Program RAVERM_ALV01

Insurance Values Program RAVERS01 Program RAVERS_ALV01

Depreciation Current Year Program RAHAFA01 Program RAHAFA_ALV01

Replaced Transaction Codes and Programs in FIN
S4HANA Finance - certain transaction codes and programs in the application areas of AC, CO, FI, AA
and FIN - compared to EhP7 for SAP ERP 6.0 - have been replaced with newer transactions, programs, or
WebDynpro applications
Certain Transaction codes and programs have been removed and partially replaced with new
transaction codes and programs in S4HANA Finance.
I have attempted to furnish the maximum information on replaced and Obsolete T codes in the OP
1610. If you find something missing in this list, please comment.
3`
 What is difference between SAP ECC, HANA and S4 HANA?

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.

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.

The task item is created once the upload is done.

Click on Activate icon

Click on Start transfer icon

The below screen will appear once the transfer is successful.

It can be seen that data will first get validated and then converted.

After the successful validation click on next icon.

The below errors have come up in conversion

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

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/
Transaction Codes
LTMC Migration Cockpit
LTMOM Migration Object Modeler

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:

Overview Presentation: SAP S/4HANA Migration Cockpit

Interactive Click Demo:

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:

Data Migration to S/4HANA from File (BH5)

Data Migration to S/4HANA Enhancements (BH4)

https://support.sap.com/content/dam/SAAP/Sol_Pack/BP_OP_ENTPR_S4HANA1611_DEV3/BP_O
P_ENTPR_S4HANA1611_DEV3_Content_Library_EN_DE.htm
Migration Objects
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 Area Business Object Type Migration Cockpit Object Name Technical Object

Name Name

Activity Types CO Master data Migration of Activity types SIF_LSTAR_CREATE

(FILE2S4)

Cost Center CO Master data Migration of Cost centers (FILE2S4) SIF_KOSTL_MASTER

Activity Price CO Master data Migration of Activity prices SIF_ACT_PRICE

(FILE2S4)
Business Object Area Business Object Type Migration Cockpit Object Name Technical Object

Name Name

Internal Order CO Transactional data Migration of Activity prices SIF_INTORDER

(FILE2S4)

Profit Center FI Master data Migration of Profit centers SIF_PRCTR_MASTER

(FILE2S4)

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 FI Transactional data Migration of Customer open items SIF_AR_OPEN_ITEM

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 Transactional data

G/L Account FI Transactional data Migration of G/L balances (FILE2S4) SIF_GL_OPEN_ITEM

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

Exchange Rate FI Master data Migration of Exchange rates SIF_EXCH_RATE

(FILE2S4)

Inventory Balances MM-IM Transactional data Migration of Material inventory SIF_INVENTORYBAL

balances (FILE2S4)

Material Master LO-MD Master data Migration of Materials (FILE2S4) SIF_MATERIAL

Material Long texts LO-MD Master data Migration of Material long texts SIF_MAT_LONGTEXT

(FILE2S4)

Material LO-MD Master data Migration of Consumptions SIF_MAT_CONSUMP

Consumptions (FILE2S4)

Purchasing Info MM-PUR Master data Migration of Purchasing info SIF_PURCH_INFREC

Record records (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)

Contracts MM-PUR Transactional data Migration of Purchasing contracts SIF_CONTRACTS

(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

Sales Order SD Transactional data Migration of sales orders (only SIF_SALES_ORDER

open) (FILE2S4)

Batches QM, SD, PP- Master data Migration of Batches (FILE2S4) SIF_BATCHES

PI

Bill of Material PP Master data Migration of Bill of materials SIF_BOM

(BOM) (FILE2S4)

Work Center PP, QM Master data Migration of Work centers SIF_WORK_CNTR

(FILE2S4)

Equipment PM Master data Migration of Equipment (FILE2S4) SIF_EQUIPMENT

Equipment Task List PM Master data Migration of Equipment task lists SIF_EAM_TASKLIST

(FILE2S4)

Functional Location PM Master data Migration of Functional locations SIF_FUNC_LOC

(FILE2S4)

Characteristics CA Master data Migration of Characteristics SIF_CHARACT

(FILE2S4)

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 SIF_CUST_EXTEND

by new organizational levels

Supplier FI, MM- Master data Supplier SIF_VENDOR

PUR

Supplier FI, MM- Master data Supplier – extend existing record SIF_VEND_EXTEND

PUR by new organizational levels

Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object

Name

Accounts Receivable FI Transactional data Accounts receivable (Customer) SIF_AR_OPEN_ITEM

(Customer) Open Item open item

Accounts Payable FI Transactional data Accounts payable (Vendor) open SIF_AP_OPEN_ITEM

(Vendor) Open Item item

Fixed Asset FI-AA Master data + Fixed asset incl. balances SIF_FIXED_ASSET

Transactional data

G/L Account Balance FI Transactional data G/L balance SIF_GL_BALANCES

G/L Account Open/Line FI Transactional data G/L open/line item SIF_GL_OPEN_ITEM

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 SIF_MATPRICE_CHG

Chng for global currencies

Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object

Name

Material Master MD Master data Material – extend existing record SIF_MAT_EXTEND

by new organizational levels

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 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

Pricing Condition SD, CO, Master data Pricing condition SIF_CONDITIONS

MM-PUR

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
Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object

Name

Sales Contract SD Transactional data Sales contract SIF_SD_CONTRACT

Batch QM, SD, Master data Batch (if Batch is unique at SIF_BATCHES

PP-PI material level)

Bill of Material (BOM) PP Master data Bill of material SIF_BOM

Work Center PP, QM Master data Work center SIF_WORK_CNTR

Routing PP Master data Routing SIF_ROUTING

Equipment PM Master data Equipment SIF_EQUIPMENT

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

Characteristic CA Master data Characteristic SIF_CHARACT

Class CA Master data Class SIF_CLASS

Business Object Name Area Business Object Type Migration Cockpit Object Name Technical Object

Name

Commercial Project CA-CPD Master data CPM project SIF_PROJECT

Management (CPM)

Inspection method QM Master data Inspection method SIF_INSP_METHOD

Master inspection QM Master data Master inspection characteristic SIF_MSTR_CHAR

characteristic

QM catalog code QM Master data QM catalog code group/code SIF_QM_CATALOG

group/code

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 FI-FSCM- Transactional data TRM – Foreign exchange SIF_TR_FX_TR

Transaction TRM-TM spot/forward transaction –

contract

TRM – Financial FI-FSCM- Transactional data TRM – Foreign exchange swap – SIF_TR_FX_SWAP

Transaction TRM-TM contract

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)

FAQ Note on Migration Cockpit

https://launchpad.support.sap.com/#/notes/2537549

Migration Process
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.

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>

<VERSION dt:dt=”string”>S4CORE 101 – 06.01.2017</VERSION>

<SYSTEM dt:dt=”string”>EAD / 700</SYSTEM>

<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>

<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:

https://msdn.microsoft.com/en-us/library/aa140066(v=office.10).aspx
https://wiki.scn.sap.com/wiki/display/Snippets/XML+TAGS+simplifies+Excel+Download
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

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?)

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.

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

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

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?

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…

SAP S/4HANA Migration Cockpit Step by Step process

February 4, 2018 webadmin

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.

The task item is created once the upload is done.

Click on Activate icon

Click on Start transfer icon

The below screen will appear once the transfer is successful.

It can be seen that data will first get validated and then converted.

After the successful validation click on next icon.

The below errors have come up in conversion

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

SAP S/4HANA Technical. Part 5. Data Migration in S/4HANA via Migration Cockpit

Introduction of SAP S/4HANA

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

S/4HANA comes with two choices, S/4HANA on premises and S/4HANA on

cloud. Choice of edition depends on Source system and S/4HANA target edition

1. S/4HANA on Premises

SAP S/4HANA, on-premise edition covers functionality, industries, and

languages that is similar to current SAP Business Suite. For the move to the
SAP S/4HANA, on-premise edition SAP offers a one-step procedure for the
majority of the current SAP Business Suite customer. This one-step procedure
includes the database migration (for those customers not yet on SAP HANA
database) plus the installation of the SAP S/4HANA Core with the
appropriate innovation packages.

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.

Also Read – What is OData?

In this article, we will talk about S/4HANA on-premises edition.

S/4HANA Implementation

There are 3 different scenarios for how the customer wants to implement
S/4HANA.

 New Implementation – In this scenario, new system (Greenfield) will

be implemented in S/4HANA from the legacy system or existing SAP
system. We will cover more of this in this article.
 System Conversion – In this scenario, existing SAP system will move
into S/4HANA system. Please note, SAP does not say it is Upgrade
from ECC to S/4HANA. They call it Conversion.
 Landscape Transformation – In this scenario, system landscape will
transform into S/4HANA for existing SAP business suite.
S/4HANA New Implementation Tool

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:

 S/4HANA Migration Cockpit with Migration Object Modeller

 SAP DATA Services (SAP DS)
 SAP Information Steward
 SAP Rapid Data Migration Content
As per note 2287723 – LSMW in SAP S/4HANA on-premise edition:

LSMW (Legacy system migration workbench) is available in S/4HANA but it

is not recommended to use this tool as it can provide an incorrect interface for
some applications of S/4HANA.

Here we will discuss only S/4HANA Migration Cockpit. For other option, we
will talk in subsequent articles.

S/4HANA Migration Cockpit (MC)

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.

PS: MC = Migration Cockpit in rest of the below content.

MC is browser based (WebDynpro) interface. No additional setup or activation is

required once we setup SAP S/4HANA system.

 To access MC on premises, use transaction LTMC. It will open MC on a

new web browser.
 To access MC on cloud, choose the option ‘Manage your
solutions’ on Launchpad.

Key Features of Migration Cockpit

 This tool is embedded and delivered with S/4HANA system.

 No programming is required by the customer.
 As the name suggests, this tool is used for migrating data from SAP or
Non SAP system to S/4HANA.
  This tool has predefined migration object which contains the mapping
for all master and transactional data. It reduces migration cost and
time.
 Migration activities are predefined and easy to use.

Also Read: SAP Fiori from Space Level

Steps to Migrate Data using MC

Below is an overview of the Migration Cockpit. It shows different element, the

relationship between them and flow of data from the file to the database.

1. Migration Project – First step is to create or open migration project in

MC. Migration project facilitates the transfer of data from source system to
S/4HANA system and monitor migration status.

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.

Below is the screenshot, where we are creating new project Z_NEW_PROJECT

with transfer id 006 and default view, is On Premises.

Press create.

2. Migration Object– Once migration project is created, we need to choose

migration object. Migration Objects are predefined and provided by SAP system.
We need to choose migration objects as per our requirement (The Business
objects like Material, Customer, Cost Center etc are the migration object now).

Below is a screenshot of migration object available on a migration project.

Migration object comes with the following information:

1. Status – Object can be active – available for migration, deactivate –

not available for migration and started – migration has started on this
object.
2. Object name – It is migration object name which is relevant to
customer master or transactional data.
3. Documentation – Once we click on documentation it will open a new
window where we can find all information on migration object like
required structure, fields, uses.
4. Dependent migration object – It shows a list of migration object
that must be loaded first or already present in the system. For
example, before loading material master, profit center object data
must be loaded or exist in the system.

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.

1. Download Template– When we click on download template for the

first time, the system will copy object template into migration project.
This template will provide a list of fields which should be filled for data
transfer. The template is downloaded by default in Excel format. If .xml
is not given then save file with .xml explicitly. We should not change
template fields, type, length and always use paste ‘V’ option for
copying data in the template.

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.

5. Deactivate – In case of multiple files, if the user doesn’t want to transfer

some file then he can choose file and deactivate them. Only the file with active
status will move for transfer.

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

Following steps has to executed after starting the transfer of data:

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.

After execution it shows status as follows:

In case of error records, we need to filter out successful records and then again
run the file for the corrected record only because we cannot upload the same
record. MC supports only INSERT statement. In fact, HANA database is
optimized for INSERT only.

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

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 Cockpit – Staging Tables

 Check backend Transcation DBCO if your database connection is available

 you need to white-list this connection in table DMC_C_WL_DBCO_OP; use SM30

 Naming convention staging tables: /LT1/DS<sys-id><consecutive number>

 due to technical reasons, staging tables are transparent tables – can be seen in SE11 – but
are not used, only tables in HANA schema. To acces them you can use OpenSQL

 NUMC fields must have leading zeros SAP Note260849

 DATE fields are YYYYMMDD

Migration Cockpit – Short Learning Videos

 Learn how to personalize your view (e.g. to create an “active view” for your migration
objects): Personalize View

Migration Cockpit ICF Services

 In the backend system call transaction /nsicf

 Activiate following services:
 /sap/bc/webdynpro/sap/DMC_WDA
 /sap/bc/webdynpro/sap/DMC_WDA_GAF

Migration Objects Overview

Find an overview on pre-delivered content for

 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).

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

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.

Please find the Issue and answers.

1.
Issues:
Client is required P&L ,B/S financial statements for 12+6 months(with considering special period
next 6 months) i.e. 18 months period or any period further after 12 months.
In short the client is required reports for more than 12 months.
Ans:
SAP cannot handle morethan 16 periods (12 + 4 special periods). So you can view P&L & B/S
statements upto 16 periods only.
Some reports having option to view the reports morethan 12 months (from 13 to 16 period) also.
Example: T.code F.01 , selection periods option is available.
2.
Issues:
1) Finished goods stocks and values were being maintained out of system before 1st Jan 2008.
From 1st Jan 2008, the FG stocks have been brought into the system. The client was requested to
update the system on 31st December 2007. But they could not do becos they do not have the right
figures with them. Now, after two months, they are having the figures. Now, how to bring in the
opening balance.
2) We have MTO scenario with configurable material. For every sales order, the system prepares
cost estimate. On the basis of these cost estimate, the Goods Receipts happens. But sometimes,
the Goods receipts happens at a very low price. We found the raw materials requested by the
system is not correct. The sales order costing variant is fine. I am having doubt with variant
configuration. I am not knowledgeable about variant configuration
Ans:
Regarding Q1. You can update the stock with “Posting Date” as 31-12-2007.
Regarding Q2. You have to maintain Variant Condition for Purchasing as well as Sales. You had
already done for Sales. Now you have to do for Purchasing also using the TCODE MEK1 for
condition type PB00. Then you will get total price for base model and characterestics.

these r some real time issues....

Real Time Issue:
Billing Document not released to accounting / Accounts determination:
To resolve the error, you can analyze account determination in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account Determination (first option)
This will list all the condition types in the Billing document & analyze each condition & check for
which G/L accounts is not determined.
Possible errors:
1. VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.
2. Account Assignment of Customer / material not maintained in Customer / Material Master (If
maintained in combination in VKOA).
Solution:
Option 1 (Standard solution):
step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
step 2: Maintain Customer master / Material Master correctly.
step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
Option 2:
Force the Account Assignment Group of Customer / Material through Debug in change mode of
Billing document, which will release Billing Document to Accounting.
3. Account Key not maintained in Pricing Procedure:
Impact: This may create accounting document, but if condition type, which are to be posted to
account, but do not have account key maintained in pricing procedure, it will not be post the relevant
condition type to G/L account.
4. Billing Document not being released to accounting --
In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not
maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few
of course get posted.
Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order &
Create new sales Cycle all over again after rectifying Material master.
Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing
Document with the help of Abaper. But ensure Material master is rectified.
From FI Side, you require to check that all the G/L account has been maintained through T.Code:
FS00. G/L account being Master data has to be created in each client to upload through LSMW /
SCATT / BDC.
In Billing Document in change mode (in the first screen where we enter Billing Document number),
on the top most left hand corner, take a dropdown on Billing Document & select Release to
accounting. Here you can get the under mentioned possible message:
1. G/L account not found
2. Cost Element not maintained for G/L account.
Most of the times we need to transfer stock of material from one plant to another plant or plants. In
SAP R/3 the following type of procedures are available.
Stock Transport Order:
Without Delivery
With Delivery via Shipping
With Delivery and Billing Document/Invoice
Advantages of the Stock Transport Order
It has the following advantages over the transfer of stock without a stock transport order:
A goods receipt can be planned in the receiving plant.
A vendor can be entered in the stock transport order.
Delivery costs can be entered in the stock transport order.
The stock transfer order is part of MRP
The goods issue is possible via a delivery or via Shipping.
The goods receipt can be posted directly to consumption.
The entire process can be monitored via the purchase order history.
Stock Transport Order with Delivery and Billing Document/Invoice
As per Indian Law, if the material is subject to Excise Duty, even moving between plants needs to be
accompanied with Excise Invoice. The following process describes the full cycle of from stock
transport order, goods issue, excise invoice and goods receipt processes.
Create Stock Transport Order
In case of requirement of materials, A Stock Transport Order stating specific quantity of material will
be raised by receiving plant to the supplying plant. For creating Stock transport we can use the
following path:
Logistics> Materials Management> Purchasing> Purchase Order> Create>Vendor/Supplying Plant
Known
T. Code: ME21N or ME27
Creating Outbound Delivery
If the stock of material is available in Supplying Plant then Supplying Plant will create a delivery
against the above Stock Transport Order.
SAP menu> Logistics> Sales and Distribution> Shipping and Transportation> Outbound Delivery>
Create> Collective Processing of Documents Due for Delivery>Purchase Orders
T. Code: VL10B
Changing Outbound Delivery
To Pick the Material and to do the Post Goods Issue supplying plant will change the above outbound
delivery document.
SAP menu> Logistics> Sales and Distribution> Shipping and Transportation> Outbound Delivery>
Change> Single Document
T. Code: VL02N
Creating Billing Document
After PGI, A billing Document known Commercial Invoice is created to update the corresponding GL
Accounts and same is send to receiving plant (Customer).
Logistics> Sales and distribution> Billing>Billing document> Create
T. Code: VF01
Creating Excise Invoice
To meet the legal requirement and to submit it to Excise Authorities the supplying plant will create an
Excise Invoice. It is a legal document and it must accompany the goods when these are being sent
to the Receiving Plant (Customer).
SAP User menu> Indirect Taxes> Sales / Outbound Movements> Excise Invoice> for Sales Order>
Outgoing Excise Invoice Create
T. Code: J1IIN
Goods Receipt for Stock Transport Order
With reference to Stock Transport Order as created above goods are received at the receiving plant.
During entering this goods movement at receiving plant we can capture and post the Part I and Part
II of excise duty. To get Excise Invoice tab at Header Data choose Check icon at third row at the top
of the screen.
Logistics> Materials Management> Inventory Management> Goods Movement> Goods Receipt for
Purchase Order
T. Code: MIGO