Migration to S4HANA Finance

Additional Information for Migration

Logic to SAP S/4HANA FinanceNovember 2015Product Version / LoB:

SAP S/4HANA, on-premise edition 1511 / LoB Finance

E2E Solution/Solution Capability:

Financial Accounting and Close

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2CustomerEarly Knowledge Transfer

Objectives

At the end of this lesson, you will be able to:

• To understand the migration logic for archived documents or line

items

• To analyze migrated items and judge their correctness

• To explain why material ledger needs to be active and how to

transfer data into the inventory valuation data model


Agenda

Logic of Migration of Line items and Balances

Criteria to identify migrated Line Items

Material Ledger Changes in Data Model and Migration with SAP S/4HANA On

Premise


Example of Migration – CO Data Only

Table AccountAccount assignment Amount

COEP – CO items 600000 CC100 100 €

COSP – CO Total 600000 CC100 100 €

Compatibility Reporting GL

Cost Center 100

Account 600000 100 €


BSEG – GL line item 0

GLT0 – GL total 0

Table Account

Account

Assignment Amount Source of document

ACDOCA – line item 600000 CC100 100 € Migrated CO Line item

600000 -100 € GL Balance Correction

Compatibility Reporting CO

Before Simple Finance Migration:

After Simple Finance Migration:


Example of Migration - CO and GL Line Items


COEP – CO items 800000 WBS element 100 €

COEP – CO items 800000 WBS element 100 €

COSP – CO Total 800000 WBS element 200 €

Account 800000 200 €

GL Compatibility Reporting

WBS element:

Account 800000 200 €


BSEG – GL line item 800000 100 €


GLT0 – GL total 800000 200 €

Table AccountAccount Assignment Amount Source of document

ACDOCA – line item 800000 WBS element 100 € Migrated CO/GL line item

ACDOCA – line item 800000 WBS element 100 € Migrated CO/GL line item

CO Compatibility Reporting

FI document items and CO line items before Simple Finance Migration:



Example of Migration - CO and GL Line Items Not Linked


COEP – CO items 400000 CC100 120 €

COEP – CO items 400000 CC200 180 €

COSP – CO Total 400000 CC100 300 €

Account 400000 300 €

GL Compatibility Reporting

Cost Center 100:

Account 400000 120 €




GLT0 – GL total 400000 300 €

Table AccountAccount Assignment Amount Source of document

ACDOCA – line item 400000 CC100 120 € Migrated CO item

ACDOCA – line item 400000 CC200 180 € Migrated CO item

ACDOCA – line item 400000 150 € Migrated GL item

ACDOCA – line item 400000 150 € Migrated GL item

CO Compatibility Reporting

FI document items and CO line items before Simple Finance Migration:


Cost Center 200:

Account 400000 180 €


Why Do we Need the Migration of Balances?

Published financial statements had been based on total reporting in the

past (EHP7 / without Simple Finance)

Reporting based on ACDOCA has to bring up the same results as the old

total based reporting

Migration of Balances ensures that the aggregation on ACDOCA

shows the same results as the old totals

In case of any differences the migration creates correction items in

ACDOCA

Differences arise if line items are archived or line items resulting from the

same business transaction cannot be linked


Example – Archived GL Line Items and Totals

Table AccountAccount

Assignment AmountCOEP 400000 CC100 100 CO line itemCOSP 400000 CC100 100 CO totals

BSEG 400000 100 Archived GL line itemGLT0 400000 100 Archived GL total

ACDOCA 400000 CC100 100 Migrated CO line itemACDOCA 400000 -100 GL Correction item

CostCenter100

Account 400000 100 €Account 400000 0 €

GL Reporting on ACDOCA CO Reporting on ACDOCA


Example – GL only postings and Archived GL line Item


Assignment Amount

COEP CO line Item

COSP CO Total

BSEG 400000 100 GL line item

BSEG 400000 200 Archived GL Line Item

GLT0 400000 300 GL total (including archived items)

ACDOCA 400000 100 Migrated GL Line item

ACDOCA 400000 200 Correction entry for GL balances

Account 400000 300 €



Example – CO only posting with archived CO Line Items


Assignment AmountCOEP 900000 CC100 -100 Archived CO line item COEP 900000 OR200 100 CO line itemCOSP 900000 CC100 -100 CO totalCOSP 900000 OR200 100 CO total

BSEG 900000 0 GL line itemGLT0 900000 0 GL total

ACDOCA 900000 OR200 100 Migrated CO line itemACDOCA 900000 CC100 -100 CO Balance Correction

CostCenter100

Account 900000 -100 €Account 900000 0 €

Order 200

Account 900000 100 €



Example - CO and GL Line Items - Mixture


Assignment AmountCOEP 400000 CC100 100 Archived CO line item COEP 400000 CC100 100 CO line itemCOSP 400000 CC100 200 CO total

BSEG 400000 100 GL line itemBSEG 400000 100 Archived GL line item GLT0 400000 200 GL total

ACDOCA 400000 CC100 100 Migrated CO/GL line item400000 CC100 100 CO Correction (C)400000 100 GL Correction (F)400000 -100 GL Correction (U)

CostCenter 100

Account 400000 200 €Account 400000 200 €



Agenda




Premise


Identification of Migrated Line Items

During the migration of data into ACDOCA it is necessary to store the type and

the origin of the entry for reconciliation purposes.

The following two attributes have been introduced for additional identification of line

items:

Status of line item (BSTAT):

• Space and ‘L‘: Line Items and ledger

specific line items

• ‚C‘: balance carry forward items or

entries from balance migration

Source of migrated line item

(MIG_SOURCE):

• Space: item created after migration

• F, G, C, M, A: Line items or balance

information originating from classic

GL, New GL, CO, ML or AA

• R: Correction item on document level

• S, U: Correction item on balance

level based on GL or CO

Examples:• Space / Space: Line item posted after migration

• Space / G: Line item migrated from NewGL line item (and potentially CO)

• ‚C‘ / ‚C‘: Correction of balance in CO to compensate for archived CO line items


Agenda




Premise


Material Ledger - What has been changed? (1)

Material Ledger, as a pure inventory sub-ledger, is become obligatorily active.Remark: Actual Costing is still an optional business feature.

See also Material Ledger Obligatory for Material Valuation WIKI

Separate currency customizing of Material Ledger is become obsolete,

instead Material Ledger is acting on the currencies defined for the leading

ledger in Financials.

There are the changes in the data model for Material Ledger documents:

For materials that are not relevant for actual costing (xBEW-MLAST = '2') no ML update

documents (MLHD-VGART = 'UP') are persisted anymore in the ML document tables MLHD,

MLIT, MLPP, MLCR and MLCD. Instead those update document data are being reconstructed

by read access compatibility views based on ACDOCA. Hence attributes from ML data model,

relevant for a pure inventory sub-ledger functionality, are part of table ACDOCA.

Remarks:

• Due to the complexity of application Actual Costing, all data for actual costing relevant materials (xBEW-

MLAST = '3') are still persisted unchanged in ML document tables. This is also true for update document

items.

• xBEW stands for MBEW, EBEW, QBEW, OBEW

https://wiki.wdf.sap.corp/wiki/pages/viewpage.action?pageId=1744022730#SI3%3ALogistics_MM-IM-MaterialLedgerObligatoryforMaterialValuation%28impactonMBEW%2COBEW%2C...%29-ObsoleteTransactionCodes%28notavailableinSAPS%2F4HANA%29%3A


Material Ledger - What has been changed? (2)

There are changes for application index table CKMI1:

No data records are being persisted anymore in this table.

Instead those data are being reconstructed by read access compatibility views based on

ACDOCA. Hence attributes from table CKMI1 are part of table ACDOCA.

Reconstructed result set is restricted to postings that were recorded for inventory accounts

(ACDOCA-KTOSL = ‘BSX’).


Persistency used for non actual costing relevant

materials (xBEW-MLAST = ‘2’).

Persistency used for actual costing relevant materials

(xBEW-MLAST = ‘3’) and historic data before migration

for all materials.

Compatibility views

(read access redirect)

Material Ledger Update Document

HeaderMLHD

MLPP

MLCR

MLHD

MLIT

MLPP

MLPPF

MLCR

MLCRF

Item

Quantity per period

ACT: quantity key

figures per period

Amount per period

and currency type

ACT: amount key

figures per period

and Currency type

ACDOCALine Items

(Universal Journal Entry) MLIT

BKPFHeader

(Universal Journal

entry)

DB Table (Full usage)

DB Table (Partly used)

(Compatibility) View

Legend


Persistency used for non actual costing relevant

materials (xBEW-MLAST = ‘2’).

Persistency used for actual costing relevant materials

(xBEW-MLAST = ‘3’) and historic data before migration

for all materials.

Compatibility views


Material Ledger Document Compression Record

MLCDACDOCA MLCD

BKPF




Legend

Header

(Universal Journal

entry)

Line Items

(Universal Journal Entry)


Persistency used for all materials. Persistency used for historic data before migration.Compatibility views


CKMI1 - Index for Accounting Documents for Material

CKMI1ACDOCA CKMI1

BKPF




Legend

Line Items

(Universal Journal Entry)

Header

(Universal Journal

entry)

DB Table (only historic data from before migration,

no new records)


No Obsolete Tables

None of the ML tables is become completely obsolete.

Table content that was persisted before migration is not being migrated to

ACDOCA. Instead data access to those “historic” data is being incorporated

into compatibility views to ensure seamless read access.

Therefore database tables can not be cleaned up after migration.

Instead archiving programs can be used to unload data from database tables.

But, as usual, this will lead to the effect that those data are not available

anymore for reporting or analysis.


Data Conversion Steps for Material Ledger

Prior to installation of S/4HANA

Verify that preconditions have been fulfilled. To do this, customer can create a Z-Report in its

Business Suite system by applying OSS note 2129306

(https://css.wdf.sap.corp/sap/support/notes/2129306). Report will issue error or warning

messages if source system setup does not fit with current sFIN limitations.

In detail the following preconditions have to be fulfilled from ML perspective:

• ML currency setting have to be identical to or a subset of the currencies defined for accounting and

controlling.

• All valuation areas belonging to the same company code have to have the same currency settings.

Data conversion after installation

Material Ledger data conversion is fully embedded into sequence of conversion steps for

SAP S/4HANA Finance.

https://css.wdf.sap.corp/sap/support/notes/2129306


Conversion to the S/4HANA Inventory Valuation Data

Model based on Material Ledger (1)

Scenario 1: All or some valuation areas are not productive with Material Ledger in the source system

Option 1: Set Material Ledger productive during

S/4HANA migration (recommended) Parallelized and re-executable report

S/4HANA 1511: All in downtime

Next releases (planned): Uptime conversion in shadow system with

minimized downtime (based on sMIG approach)

Option 2: Set Material Ledger productive before

S/4HANA migration in the source system Non-parallelized and non-re-executable report

All in downtime

1. Creation of Material Ledger master data and conversion of inventory values and material prices into

Material Ledger currencies (Local, group and another currency)

MBEW MBEWH

EBEW EBEWH

QBEW QBEWH

OBEW OBEWH

CKMLHD CKMLPP CKMLCR CKMLPR

2. Conversion of production order history entries into group and another currency

MLAUF

CRH

MLAUF

CRMLAUF

CRHMLAUF

CR

3. Conversion of purchase order history entries into group and another currency

Migration Activities:

EKBE EKBZ MLWERE MLBE MLBECR

EKBEH EKBZH MLWERE MLBEH MLBECRH


Conversion to the S/4HANA Inventory Valuation Data

Model based on Material Ledger (2)

Scenario 2: All valuation areas are productive with Material Ledger in the source system

Post-migration of missing history table entries and resolving of Material Ledger inconsistencies

during S/4HANA migration S/4HANA 1511: All in downtime

Next releases (planned): Uptime conversion in shadow system with minimized downtime (based on sMIG approach)

1. Post-migration of missing history table entries (For instance, for periods before Material Ledger activation) and resolving of

inconsistencies (For instance, Material Ledger entries do not exist)

MBEW MBEWH

EBEW EBEWH

QBEW QBEWH

OBEW OBEWH

CKMLHD CKMLPP CKMLCR CKMLPR

Migration Activity:


Lesson Summary

You should now be able to

• To understand the migration logic for archived documents or line

items

• To analyze migrated items and judge their correctness

• To explain why material ledger needs to be active and how to

transfer data into the inventory valuation data model


© 2015 SAP SE or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an

SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE

(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional

trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,

and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated

companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be

changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties

that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

Migration to S4HANA Finance

Documents

Transcript of Migration to S4HANA Finance