Вы находитесь на странице: 1из 130

Capgemini

Migration of Simple
Finance and Logistics
After S4 HANA 1610 upgrade
Solution Centre

This document outlines the steps involved in migrating Simple finance and Logistics after the system is upgraded
to S4 HANA 1610. It is a compilation of the steps that were executed in system for migration of Simple Finance
and Simple Logistics by members of Solution Centre.
TABLE OF CONTENTS
Table of Contents............................................................................................................................................................2
Authors............................................................................................................................................................................5
1. Introduction............................................................................................................................................................6
2. Scope.......................................................................................................................................................................7
3. Activity Overview Table..........................................................................................................................................8
4. Checklist (attachment)..........................................................................................................................................24
5. Steps in Simple Finance........................................................................................................................................25
5.1. Prerequisite steps - Preparation activities before the installation of the SAP Simple Finance add-on......25
5.1.1. Check if business function EA-FIN is active.............................................................................................25
5.1.2. Check if prior migration check screen is available or not.......................................................................25
5.2. Preparation and Migration customizing for General Ledger......................................................................28
5.2.1. Activate SAP Reference IMG for Financial Accounting (New)................................................................28
5.2.2. Check and Adopt fiscal year variant.......................................................................................................28
5.2.3. Migrate General ledger customizing......................................................................................................29
5.2.4. Define settings for ledgers and currency types......................................................................................30
5.2.5. Define ledger for CO version...................................................................................................................32
5.2.6. Define Document types for posting in Controlling.................................................................................33
5.2.7. Define document type mapping to CO business transactions...............................................................34
5.2.8. Check and define default values for postings in controlling..................................................................35
5.2.9. Define offsetting account determination type.......................................................................................37
5.2.10. Define Source ledger for migration of balances.................................................................................38
5.2.11. Execute consistency check of General Ledger Settings......................................................................40
5.2.12. Activate business functions................................................................................................................42
5.3. Preparation and migration customizing for Asset Accounting...................................................................43
5.3.1. Migrate chart of Depreciation................................................................................................................43
5.3.2. Display Migration Log.............................................................................................................................44
5.3.3. Perform additional manual activities......................................................................................................45
5.3.4. Check prerequisites for activating Asset accounting..............................................................................47
5.3.5. Activate Asset Accounting......................................................................................................................50
5.4. Preparation and migration of customizing for controlling.........................................................................52
5.4.1. Execute BW data extraction for Account based COPA...........................................................................52
5.4.2. Adapt settings for the change of profitability segment characteristics.................................................53

2
5.4.3. Maintain operating concern...................................................................................................................53
5.4.4. Activate Account based profitability analysis.........................................................................................54
5.5. Migration.....................................................................................................................................................55
5.5.1. Partitioning of Universal Journal Entry Line Items Table........................................................................56
5.5.2. Regenerate CDS views and field mapping..............................................................................................56
5.6. Migration of Cost elements and customizing – Not Applicable for S4 HANA 1610....................................57
5.6.1. Check consistency of GL accounts and cost elements (for 1511)...........................................................58
5.6.2. Migrate secondary cost elements to GL accounts (for 1511)................................................................59
5.6.3. Display status of Migration cost elements (for 1511)............................................................................60
5.6.4. Migrate default account assignments....................................................................................................60
5.6.5. Display status of Default account assignments (for 1511).....................................................................61
5.6.6. Adapt Authorizations (for 1511).............................................................................................................61
5.7. Technical check of transactional data – not applicable for S4 HANA 1610................................................61
5.7.1. Analyze transactional data (for 1511)....................................................................................................62
5.7.2. Display status of Analyze transactional data (for 1511).........................................................................63
5.7.3. Reconcile Transactional data (1511).......................................................................................................63
5.7.4. Display status of Reconcile transactional data (for 1511)......................................................................64
5.8. Migration Enrichment of data – not applicable for S4 HANA 1610............................................................65
5.8.1. Enrich Transactional data (for 1511)......................................................................................................66
5.8.2. Display status of migration enrichment data (for 1511)........................................................................66
5.8.3. Check of migrated documents (for 1511)...............................................................................................67
5.8.4. Display status of check migrated documents (for 1511)........................................................................67
5.9. Migration of line items into new data structure – not applicable for S4 HANA 1610................................68
5.9.1. Migrate accounting documents to universal journal entry structure (for 1511)...................................68
5.9.2. Display status of documents to universal journal entry (for 1511)........................................................69
5.9.3. Check migration of Accounting documents to Universal journal entry (for 1511)................................70
5.9.4. Display status of check accounting documents migration (for 1511)....................................................71
5.9.5. Migrate General Ledger allocations (for 1511)......................................................................................71
5.10. Migration of Balances – not applicable for S4 HANA 1610.........................................................................72
5.10.1. Migrate balances (for 1511)...............................................................................................................73
5.10.2. Display status of Migrate balances (for 1511)...................................................................................73
5.10.3. Calculate initial depreciation values (for 1511)..................................................................................74
5.10.4. Check migration of balances (for 1511).............................................................................................74
5.10.5. Display status check of migration balances (for 1511)......................................................................75

3
5.11. Complete Migration....................................................................................................................................75
5.11.1. Convert Held Documents (for 1511, not applicable for S4 HANA 1610)...........................................75
5.11.2. Reconcile and Compare Migrated Data (for 1511, not applicable for S4 HANA 1610).....................76
5.11.3. Set migration completed....................................................................................................................77
5.12. Activities after migration.............................................................................................................................78
5.12.1. Transfer application indexes..............................................................................................................78
5.12.2. Display status of Transfer application indexes...................................................................................79
5.12.3. Fill due dates in FI documents............................................................................................................80
5.12.4. Display status of fill due dates in FI documents.................................................................................81
5.12.5. Fill offsetting account in FI documents...............................................................................................82
5.12.6. Display status of fill offsetting account in FI documents....................................................................83
5.13. Migrate House bank Accounts....................................................................................................................84
5.13.1. Prerequisites.......................................................................................................................................84
5.13.2. Migrate house bank accounts............................................................................................................85
5.13.3. Classify FI document types for Document splitting............................................................................87
6. Steps in Migration of Simple Logistics..................................................................................................................89
6.1. For Credit Management..............................................................................................................................89
6.1.1. Preparatory Activities and Migration of Customizing for Credit Management.....................................89
6.1.2. Credit Management Migration...............................................................................................................97
6.1.3. Transporting changes and re-execution for Credit Management........................................................103
6.2. For Manufacturing activities.....................................................................................................................105
6.2.1. Report Execution for MRP Record creation..........................................................................................105
6.2.2. Correct the Secondary Persistence of Sales Documents Relevant to ATP – Execute report
ATP_VBBE_CONSISTENCY...................................................................................................................................105
6.2.3. Preparations and Migration of Customizing for MRP activation..........................................................105
6.2.4. Activation of MRP Live on HANA Procedures.......................................................................................110
6.2.5. Checking active dependents while MRP on SAP HANA is being activated on a live system................111
6.2.6. Planning File Entries Conversion...........................................................................................................111
6.2.7. Steps before MRP RUN in MRP Live.....................................................................................................112
7. Customer-Vendor integration.............................................................................................................................113
7.1. Steps for Customer-Vendor Integration from reference documents.......................................................113
7.2. Vendor Integration....................................................................................................................................113
7.2.1. Initial Settings for Vendor - ERP C/V Account Group Settings..............................................................113
7.2.2. Vendor Integration process..................................................................................................................127

4
AUTHORS

Inputs based on  Mallikarjuna Tummala (Simple Finance)


migration work  Ajit Jaiswal (Simple Logistics - Credit Management & Customer Vendor Integration)
done  Vamsi A (CVI – Vendor Integration)
 Amit Chintalwar (Simple Logistics - Manufacturing activities)
Compiled By  Jenamani Priyadarshi
Reviewed By  Chirdeep Rastogi
 Manoj Nile

5
1. INTRODUCTION
With the advent of S4 HANA which brings super speed due to in-memory computing, existing ERP systems may
upgrade to harness the benefits of the new technology that comes through SAP Business Suite powered by SAP
HANA which is simple yet fast, and with options to go for easy-to-use, ergonomic and graphic user experience
provided by the FIORI user interface.

Simple Finance (sFin) and Simple Logistics are add-ons for the SAP Business Suite powered by SAP HANA which
come with simpler data models and replace the classical financial applications available in ERP systems. A user can
have finance in FIORI with sFin.

One can have Simple Finance with and without migration. However, in case of an existing ERP system, migration is
the mandated way forward. This is unlike new ERP systems where the financial applications can be updated along
with the new ERP system with S4 update, although table migration would still be required.

S4 HANA database being a prerequisite for Simple Finance, once S4 HANA 1610 upgrade is done on the system,
migration of Simple Finance and Simple Logistics is to be initiated in that order.

This broadly involves the steps involving configurations to be done and migration steps to be carried out as
detailed in the document further.

6
1. SCOPE
The scope of the document is restricted to the migration activities carried out by the Solution Centre Team (Value
Streams of Finance-to-Manage, Order-to-Cash, Procure-to-Pay, and Demand-to-Supply and the Basis team) of
Capgemini Technology Services India Limited, after S4 HANA 1610 upgrade has been done.

This document will go through the overall steps for Simple Finance configuration and migration first, and this will
be followed by similar steps for Simple Logistics, including Customer-Vendor Integration.

7
2. ACTIVITY OVERVIEW TABLE
This table summarizes the processes or activities involved in the migration processes and can be used as a quick
reference guide.

S.N
Phase Activity Expectation
o
Steps in Simple
   
Finance
Business function EA-FIN should be
1.1. Check if business function EA-FIN active in Transaction SFW5
is active.

Report RASFIN_MIGR_PRECHECK runs


1.2. Check if the report and checks the customizing settings in
RASFIN_MIGR_PRECHECK is available the customizing-, test- and productive
in your SAP ERP system or implement system
note 1939592 (it contains the report).
Run report RASFIN_MIGR_PRECHECK
in all your system

1.3. Check and activate the business Business functions


functions FIN_AA_PARALLEL_VAL and FIN_AA_PARALLEL_VAL and
FIN_AA_CI_1. FIN_AA_CI_1 should be active
The report
Preparation
ZFINS_MIG_PRECHCK_CUST_SETTNGS
activities is executed in the customizing-, test-
before the
and productive system.
installation of
1 Example of 2 error messages:
the SAP
- For some company codes, currencies
Simple were assigned to non-leading ledger
Finance add-
1.4. Run the report but not to the leading ledger - it is
on ZFINS_MIG_PRECHCK_CUST_SETTNGS necessary to correct the currency
in all your SAP ERP systems (this report assignment for all company codes,
is contained in SAP note 2129306) even if they are not actively used;
- The fiscal year variant assigned to the
company code CN01 was different
from the one assigned to the
controlling area - the fiscal year variant
in FI and CO must be the same.
The report was executed again and
finished with status check passed.
1.5.Check whether the customizing of The SAP Best Practices Baseline
the depreciation areas has been package does not have depreciation
defined correctly in case of parallel areas in a parallel currency. No action
currencies. required.
1.6. If you are already using account- The SAP Best Practices Baseline

8
based profitability analysis, perform a package does not have account-based
delta upload to SAP BW for all profitability analysis. No action
account-based CO-PA DataSources for required.
which you use the delta method.
All posting periods are locked for FI
1.7.Lock postings periods in FI.
postings
1.8.Lock posting periods in CO for All posting periods are locked for CO
Plan/Actual postings (transaction postings
OKP1).
1.9.Run the report The report shall not show any error
RASFIN_MIGR_PRECHECK again to message.
make sure that the prerequisites for
the Asset Accounting are met
1.10.Block all users who have no tasks Only users involved in the migration
in the migration project. project have access to the system
1.11.Backup the system before System backup done.
installing the add-on.
2 Preparations Not required, IMG menu is already
and Migration 2.1.Activate SAP Reference IMG for available.
of Financial Accounting (New)
Customizing No activity required, since the SAP Best
for the 2.2.Check and Adopt Fiscal Year Practices Baseline packages use the
General Variants variant K4 for both the controlling
Ledger area, and all company codes.
The following settings are migrated:
- Company code assignments
- Currency settings
2.3.Migrate General Ledger
- Fiscal year variant
Customizing*
- Open period variant
- Settings for real-time integration of
CO-FI
In case of multiple accounting
principles, e.g. IFRS and GAAP are
2.4.Define Settings for Journal Entry assigned to the ledger 0L, the flag
Ledger Parallel accounting using additional
G/L accounts will be by default
selected
Leading ledger 0L has been assigned to
2.5.Define Ledger for CO Version
the CO version 0 (Plan/actual version).
2.6.Define Document Types for CO as the document type has been
Postings in Controlling defined to be used for CO postings
2.7.Define Document Type Mapping Document Type Mapping Variant for
Variants for CO Business Transactions CO transaction is made
2.8.Check and Define Default Values If you do not enter a default ledger
for Postings in Controlling group, all CO postings will be done to
all G/L ledgers.

9
The recommended option As case 2,
2.9.Define Offsetting Account
but including line items generated
Determination Type
automatically has been selected.
Since New G/L Accounting was already
2.10.Define Source Ledger for active in the baseline ERP system, the
Migration of Balances ledger 0L has been selected as source
ledger for the migration of balances
The consistency check has run and no
errors should be reported.

2.11.Execute Consistency Check of


General Ledger Settings

The activation of the business


functions is mandatory for the SAP
Simple Finance add-on.
Following business functions have
2.12.Activate Business Functions
been activated:
- FIN_GL_CI_1
- FIN_GL_CI_2
- FIN_GL_CI_3
3 Preparations The chart of depreciation, which is
and Migration 3.1.Migrate Charts of Depreciation used in the SAP Best Practices Baseline
of package, is migrated
Customizing If the migration log displays error
for Asset messages, you should analyze them
Accounting and take consequent actions.
Example: If the error message No
accounting principle found for chart of
deprec. 10US/deprec. area 01 is
displayed, you should correct the
depreciation areas in the chart of
depreciation by assigning the
3.2.Display Migration Log respective accounting principles.
3.3.Perform Additional Manual Here you should at least perform the
Activities mandatory activity Define Technical
Clearing Account for Integrated Asset
Acquisition.
Additionally, in baseline the accounting
principle (local GAAP) is assigned to all

10
depreciation areas
The prerequisites for the activation of
the New Asset Accounting have been
checked with
transaction.FAA_CHECK_ACTIVATION.
3.4.Check Prerequisites for Activating
If you encounter any error, you need
Asset Accounting (New)
to correct it and then run this check
report again until it ends with the
message No error found and all traffic
lights are green
The New Asset Accounting has been
3.5.Activate Asset Accounting (New) activated with transaction
FAA_DO_ACTIVATION.
Because the baseline used only the
4.1.Execute BW-Delta Extraction for cost-object based profitability analysis
Account-Based CO-PA prior the migration, this step is not
required.
All the settings for profitability
segment characteristics (segment
4.2.Delete Settings for the Change of
level) made in transaction KEQ3 have
Profitability Segment Characteristics
been deleted by running the report
FCO_MIGRATION_COPA
The report
Preparations FCO_ADD_COPA_FIELD_TO_ACDOCA
and Migration 4.3. Maintain Operating Concern is started in background and activates
of the operating concern for account-
Customizing based Profitability Analysis
for The account-based Profitability
Controlling Analysis is now active for your
concern.
*Since the cost-based CO-PA has been
used before the SAP Simple Finance
4.4. Activate Account-Based add-on, after the activation of account-
Profitability Analysis based CO-PA, both approaches exist
and work correctly in the baseline
landscape.
The recommended approach by SAP is
the Account - Based Profitability
4 Analysis.
5.1.Partitioning of Universal Journal
5 Migration
Entry Line Items Table No action required.

11
5.2.Regenerate CDS Views and Field
Mapping Execute in background the program
FGL_MIG_REGENERATE_CDS and
check the progress in the transaction
SLG1 with sub- object FINS_GENERATE.
6 Migration of An inconsistency could be that no G/L
Cost Elements accounts exist for a primary cost
and element. Here is an example of an
Customizing error found in SAP Best Practices
(For 1511, Not Baseline packages for China:
for S4 HANA Error message:
1610) Primary cost element 41010100/CN01
(type 1) not found in chart of accts
CACN
6.1.Check Consistency of G/L Accounts
Solution:
and Cost Elements
Create the missing G/L account with
account type primary cost element for
CN client. Take a similar account as
template for setting up the G/L
account characteristics.
After all corrections, G/L accounts and
cost elements are consistent with each
other and G/L account master records
have the right account types
6.2.Migrate Secondary Cost Elements All secondary cost elements, as well as
to Chart of Accounts (transaction the primary cost elements, are
FINS_MIG_GCM) represented as G/L accounts
With this transaction, you can monitor
the status of the merge of G/L
accounts and cost elements.
6.3.Display Status of Migration of Cost
In the baseline both company codes
Elements (transaction
1000 and 1010 use the same chart of
FINS_MIG_MONITOR_GCM)
accounts. The chart of accounts tables
are updated when report is executed
for the first company code
6.4.Migrate Default Account The default assignments are
Assignments (transaction transferred from the master data table
FINS_MIG_DAA) CSKB to the Customizing table TKA3A.
6.5.Display Status of Migration of With this transaction, you can check
Default Account Assignments the status of the transfer of default
(transaction account assignments. After the
FINS_MIG_MONITOR_DAA) migration, the default account
assignments are accessible via
transaction OKB9.

12
Because G/L accounts and cost
elements are in the same table in
Simple Finance 2.0 system, you need
6.6.Adopt Authorizations
to adapt the authorization roles for
creating/changing G/L accounts and
cost elements.
The report runs and checks whether all
7.1.Analyze Transactional Data
transactional data are complete and
(transaction FINS_RECON_RCO)
correct.
7.2.Display Status of Analysis of
Technical Transaction Data (transaction You use this report to check the status
Check of FINS_MIG_MONITOR_RCO) of the transactional data analysis.
Transaction The report checks whether all FI
7 Data (For 7.3.Reconcile Transactional Data documents are consistent and ready to
1511, Not for (transaction FINS_RECON_RC1) be migrated. It checks prerequisites for
S4 HANA the migration.
1610)
7.4.Display Status of Technical
Reconciliation of Transactional Data
(transaction You use this report to check the status
FINS_MIG_MONITOR_RC1) of the transactional data
reconciliation.
The report enriches transactional data
8.1.Enrich Transactional Data and documents and then migrates
(transaction FINS_MIGRATION) them to SAP Accounting powered by
SAP HANA.
8.2.Display Status of Enrichment of You use this report to check the status
Migration - Transactional Data (transaction of the transactional data enrichment
Enrichment of FINS_MIG_MONITOR) and migration.
Data (For This report checks the result of the
8
1511, Not for 8.3.Check of Migrated Documents previous step of the migration. It
S4 HANA (transaction FINS_RECON_RC2) checks document fields that are used
1610) in the following migration steps.
You use this report to check the status
8.4.Display Status of Check of Migrated of the previous step.
Documents (transaction All checks from the last migration step
FINS_MIG_MONITOR_RC2) should end with status green (no
issues).
All accounting documents are migrated
Migration of to the Unified Journal Entry structure
Line Items and are enriched with COPA
into New information.
9.1.Migrate Accounting Documents to
Data SAP recommends that you execute this
9 Universal Journal Entry Structure
Structure (For migration step in all clients, also in
(transaction FIND_MIG_UJ)
1511, Not for clients where there are no
S4 HANA transactional data. This is required so
1610) that the migration status for the client
can be set to finished.

13
9.2.Display Status of Document You can use this report to monitor the
Migration to Universal Journal Entry status of the previous step.
(transaction FINS_MIG_MONITOR_UJ) All data packages are displayed with
status green (no issues).

9.3.Check Migration of Accounting This report performs several checks to


Documents to Universal Journal Entry the migrated documents.
(transaction FINS_RECON_RC3) You must perform this step before
migrating the account balances.
9.4.Display Status of Check of You can use this report to monitor the
Accounting Document Migration status of the previous step.
(transaction All checks from the last migration step
FINS_MIG_MONITOR_RC3) ended with status green (no issues).
All allocations have been migrated to
9.5.Migrate General Ledger Allocations
the new Unified Journal Entry
(transaction FINS_MIG_GL_ALLOC)
structure and no errors are displayed.
10 Migration of
Balances (For
1511, Not for
S4 HANA
1610) All G/L account balances are migrated.
10.1.Migrate Balances (transaction SAP recommends that you execute this
FINS_MIG_DLT) migration step in all clients, also in
clients where there are no
transactional data. This is required so
that the migration status for the client
can be set to finished.

10.2.Display Status of Migration of


Balances (transaction
FINS_MIG_MONITOR_DLT)
You can use this report to monitor the
status of the previous step.
All data packages are displayed with
status green (no issues).
10.3.Calculate Initial Depreciation The migration from the classical to the
Values (transaction AFAR) New Asset Accounting is one
precondition for migrating to Simple
Finance. Now, after completing the
migration of transactional data and
account balances, you need to
recalculate the planned depreciation
values for the Asset Accounting.
After running this report, the initial
planned depreciation values have been

14
calculated and stored in the respective
database tables.
This report checks the result of the
previous step of the migration.
If you find errors, you need to make
the respective corrections and run the
10.4.Check Migration of Balances
migration again. Should you need to
(transaction FINS_RECON_RC4)
repeat the migration, please read the
SAP note 2138644 first. This SAP note
advices on how to reset the migration
in case you need to repeat it.

10.5.Monitor Check of Balances


(transaction
FINS_MIG_MONITOR_RC4) This report helps you monitoring the
previous step.
All checks from the last migration step
should end with status green (no
issues).
You need to convert previously held
11.1.Convert Held Documents documents, before you can create new
(transaction FINS_RFTMPBLU (For ones or processing existing ones.
1511, Not for S4 HANA 1610) As a result, all held documents are
converted or deleted.
All financial data should be correct and
11.2.Reconcile and Compare Migrated corresponds to the figures prior to the
Data (For 1511, Not for S4 HANA 1610) migration in case there was
- Reconcile ledger 0 with ledger 0L transactional data. Otherwise, this step
(transaction GCAC). is not mandatory.
-Compare the company's key figure
Complete
with the ones prior to the migration:
Migration
- The financial statements (program
11 (Single Step in
RFBILA00)
S4 HANA
- The asset history sheet (program
1610)
RAGITT_ALV01)
- The depreciation run for the planned
depreciations (program
RAHAFA_ALV01)
- The totals report for cost centers
(transaction S_ALR_87013611)
- Sales order selection (program
RKKBSELL)
- The G/L account balance list
(program RFSSLD00)
- The general ledger line items list

15
(program RFSOPO00)
The compact document journal
(program RFBELJ00)
-The vendor sales (program
RFKUML00)
- The vendor open item list (program
RFKEPL00)
- The customer sales (program
RFKUML00)
- The customer open item list (program
RFDEPL00)
- The customer recurring entry original
documents (program RFDAUB00)
- The cost centers:
actual/plan/variance (transaction
GR55 with report group 1SIP)
Once you set the migration status to
11.3.Set Migration to Completed
complete, users are allowed to make
(single Step in S4 HANA 1610)
postings again in the system.
12 Activities In this Customizing activity, application
after indexes are transferred to the cold
Migration partition of the database in order to
12.1.Transfer Application Indexes reduce main memory consumption.
(transaction FINS_MIG_INIT_COLD) For this you use Data Aging, therefore
it is required to activate the business
function DAAG_DATA_AGING in your
system.

12.2.Display Status of Transfer of You can use this report to monitor the
Application Indexes (transaction status of the previous step.
FINS_MIG_MONITOR_CLD) All data packages should be displayed
with status green (no issues).
In this Customizing activity, due date
fields are filled in the FI line items for
12.3.Fill Due Dates in FI Documents
customers and vendors and for G/L
(transaction FIN_MIG_DUE)
account line items that have a base
line date.

12.4.Display Status of Filling in Due You can use this report to monitor the
Dates into FI Documents (transaction status of the previous step.
FIN_MIG_MONITOR_DUE) All data packages should be displayed
with status green (no issues).
12.5.Fill the Offsetting Account in FI The offsetting account is filled in the FI
Documents (transaction documents.
FIN_MIG_GKONT) Precondition for this activity is that you
have defined an offsetting account
determination type in the Customizing
activity Define Offsetting Account
Determination Type.

16
12.6.Display Status of Filling the You can use this report to monitor the
Offsetting Account in FI Documents status of the previous step.
(transaction FIN_MIG_MONITOR_GKO) All data packages should be displayed
with status green (no issues).
The house bank accounts are
migrated.
12.7.Migrate House Bank accounts
* You need to perform customizing for
(transaction FCLM_BAM_MIGRATION)
Bank Account Management first and
then run the transaction
Steps in Simple Logistics - Credit Management  
13.1 Preparatory Activities and
Migration of Customizing for Credit
Management  
13.1.1 Migrate Credit Management
Customizing  
13.1.2 Define Credit Representative
Group as Business Partner
Relationship:  
13.1.3 Assign Credit Representative
Group to Credit Analyst Group  
13.1.4 Define Customer Credit Group  
13.1.5 Assign Credit Management
Migration of Group to Customer Credit Group  
Simple 13.1.6 Assign Credit Management
13 Logistics - Processor to Credit Analyst Group  
Credit 13.1.7 Check Customizing Settings  
Management 13.2 Credit Management Migration  
13.2.1 Migrate Credit Management
Master Data  
13.2.2 Display Status of Migration of
Credit Management Master Data  
13.2.3 Migrate Credit Management
Exposure  
13.2.4 Display Status of Credit
Management Exposure Migration  
13.2.5 Initialize Documented Credit
Decisions  
13.2.6 Display Status of Initialization of
Documented Credit Decisions  
Steps in Simple Logistics - Manufacturing  

17
Use this report to create MRP records
that are to be used for operative
planning.
Execute report
PPH_SETUP_MRPRECORDS

REPORT
EXECUTION
1 FOR MRP
Use this report to create MRP records
RECORD
that are to be used for operative
CREATION
planning. If you want to create MRP
Report records to be used for simulative
PPH_SETUP_MRPRECORDS_SIMU. planning (long-term planning), a
second report is available:

This report reads all the sales orders


and deliveries with open quantities
Correct the
and compares this information with
Secondary
the available entries on the database.
Persistence of
Execute report By selecting the Simulation Mode
2 Sales
ATP_VBBE_CONSISTENCY checkbox, you can perform this report
Documents
in simulation. If you do not start the
Relevant to
report in simulation mode, all
ATP
inconsistencies found will be corrected
automatically.
3 Preparations In order to activate MRP on SAP HANA
and Migration Configuration - Overall Maintenance of you cannot have total requirements
of Repetitive Manufacuring Profile - for sales orders or for dependent
Customizing In change view of Overall Maintenance requirements. Aggregate requirements
for MRP of Repetitive Manufacturing Profile, are no longer supported by SAP HANA,
activation select REM profile as shown and click as they can now be aggregated at
on details (lens icon) runtime. Therefore, before proceeding
Maintain parameters and values as: with the business function activation,
Field Aggregate Reqmts in tab Control you must make sure that there is no
data 2 – Mandatory to Tick as shown in material with total requirements.
second screenshot from here.

Availability checking group in the This setting can be generally found in


material master In MRP 3 view, field the MRP3 tab of the material master
Availability Check to be 02 (Transaction MM02). The available-to-
promise (ATP) checking group
(Availability Check) is the standard
checking group delivered by SAP with
total records.

18
have a custom checking group with
total requirements

Configuration - Define Checking group


- T Code OVZ2 -
You must check the entries in the
customizing activity Define Checking
Groups any checking group with the
option B - Totals records per day. You
should replace this value with A -
Single records

It is necessary to create a new interval


with the key PP for each one of these
elements. The following rules must be
considered:
Setup Number range for MRP Live -
»It must be a numeric interval, which
it is necessary to set up this
means that we cannot use letters.
interval for planned orders (object
»This interval must not overlap with
PLAF), reservations/dependent
any other interval for this object.
requirements (object RESB) and
»This interval should be used for MRP
purchase requisitions (object BANF).
Live only, so you cannot use it for
T Code - SNRO
any other purpose.
The procedure to create a new interval
for object BANF must be repeated for
objects PLAF and RESB
SAP Note 1907934: MRP Live on Hana Before running MRP on SAP HANA, we
procedures activation, provides a list must ensure that all of the SAP
of the SAP HANA Transport Containers HANA delivery units were successfully
(HTCs) that should be activated for deployed, otherwise errors and
each release and support package. For short dumps may be observed in MRP
example, our system is running on EHP Live, or in any transactions that
7 with Support Package 9. access the MRP on SAP HANA
Activation of SAP Note 1907934 provides the procedures.
MRP Live on following list of HTCs:
4
HANA »HCO_ERP_SAPPL_PPH_V04_SGT
Procedures »HCO_ERP_SAPPL_PPH_V04_MRP
»HCO_ERP_SAPPL_PPH_V05_READ
HCO_ERP_SAPPL_PPH_V05_MRP
»HCO_ERP_SAPPL_PPH_V05_SGT
Post Processing for HANA Transport  
Container Correction Report Execution
in SE38 SNHI_NHDU_POST_PROCESS

19
This report checks the existence of
MRP on SAP HANA is being activated
MRP on SAP active dependent requirements for
on a live system, where dependent
HANA is being materials with simple discontinuation
5 requirements already exist, we
activated on a and checks the discontinuation flag
recommend that you execute report
live system, (KZAUS) in table RESB for those
PPH_ADAPT_RESB_DISCONT.
requirements.
If you are still using the old planning
file table MDVM, or if you are
upgrading to SAP S/4HANA, it is
necessary to convert the planning file
Planning File entries. In this section, we will discuss
Run t code OM0F or execute report
6 Entries this process for both SAP ERP and SAP
RMDBVM00 in SE38
Conversion S/4HANA.
After the report has executed, all
planning file entries will be copied to
table DBVM and deleted from table
MDVM.
The SAP S/4HANA release, a new
planning file table called PPH_DBVM
If you are upgrading an older system to was created. This table is even faster
SAP S/4HANA, report and is optimized for the SAP HANA
PPH_SETUP_MRPRECORDS must be database.
executed in order to convert the This report is used to create the
planning file entries to this new table. planning file entries in table
PPH_DBVM and also as a consistency
check for existing planning file entries.
In order to help you to identify which
materials are using a setting not
supported by MRP Live, SAP has also
Before MRP developed a new report to check the
7 RUN in MRP master data.
Live With this report, you can evaluate all
Check master data report
of your materials and identify which
PPH_CHECK_MRP_
ones can be planned by MRP Live, and
ON_HANA
which ones should be planned by the
classic MRP transactions. The fact that
this report is available for other
releases is interesting, because you
can review all of your master data
even before an upgrade.
After running the report in actual
Production Versions Created by Report mode, we can see the proposal of new
CS_BOM_PRODVER_MIGRATION production versions that will be
created by MRP
Steps in Customer-Vendor Integration  
14.1 Steps for Customer-Vendor Customer Vendor Integration is
14 CVI
Integration from reference required for business partners in order

20
to use Financial Accounting (FI) and
SAP Business partner in parallel.
Financial Accounting uses its own
customer/vendor master records
which are integrated in all accounting
transactions, instead of relying on SAP
Business Partner. Accounts
Receivables and Accounts Payable
subledgers are used to manage
accounting data of customers and
vendors in FI.
documents:
Customer and Vendor integration can
1. S4HANA CVI Customer Care
be used independent of each other
Presentation 20160905.pdf
and there are applications that use
2.
only customer integration or vendor
J61_S4HANAX_BB_ConfigGuide_EN_X
integration. CVI is intended as one
X.docx
system/one client solution.

As complete implementation of this


feature is yet to be done by our team,
CVI can be performed as per the steps
detailed in the attached documents.
1. S4HANA CVI Customer Care
Presentation 20160905.pdf
2.
J61_S4HANAX_BB_ConfigGuide_EN_X
X.docx
14.2 Vendor Integration The purpose of this document is to
14.2.1 Initial Settings describe the general configuration
ERP Partner Functions / Partner steps required to manually set up the
Determination configuration within the system
Set Up Partner Functions landscape that has already been
ERP C/V Account Group Settings installed using the corresponding
installation or configuration guides for
Create Number Ranges for Vendor
installation.
Accounts
If you do not want to configure
Define Account Groups with Screen
manually and prefer an automated
Layout (Vendors)
installation process using BC Sets and
Assign Number Ranges to Vendor other tools, refer to the Configuration
Account Groups Guide – Getting Started of your SAP
Define Permissible Partner Roles per rapid-deployment solution that is
Account Group attached to the SAP Note.
Define Partner Schemas This document supplements the
Assign Partner Schemas to Account existing Customizing documentation in
Groups the Implementation Guide (IMG) and
Vendor Integration Process Steps provides additional information where

21
14.5.2.1 Define Number Assignment
for Direction BP to Vendor
14.5.2.2 Set BP Role Category for
Direction BP to Vendor
14.5.2.1 Define Number Assignment required
for Direction BP to Vendor
14.5.2.2 Set BP Role Category for
Direction BP to Vendor

22
3. CHECKLIST (ATTACHMENT)
The activities listed earlier are listed in form of a template as migration checklist.

Migration of Simple
Finance and Logistics_Checklist_v3.xlsx

23
4. STEPS IN SIMPLE FINANCE

4.1. PREREQUISITE STEPS - PREPARATION ACTIVITIES BEFORE THE INSTALLATION OF


THE SAP S IMPLE FINANCE ADD-ON
4.1.1. C HECK IF BUSINESS FUNCTION EA-FIN IS ACTIVE

U SE
With this activities, you can prepare for the installation of sFin by checking for EA-FIN business as active or not.

P ROCEDURE
Tcode SWF5

Steps: Check if business function EA-FIN is active

R ESULT
Business function is active

4.1.2. C HECK IF PRIOR MIGRATION CHECK SCREEN IS AVAILABLE OR NOT

U SE
This activity checks for customizing settings prior to migration.

P ROCEDURE
Tcode FINS_MIG_PRECHECK
IMG Menu details in screenshot.

Steps:

1. Execute and resolve errors to proceed further as seen.

24
2. Execute

3. Resolve the errors as in preceding screenshot to proceed further

4. Blocking posting periods for variant “UPPP”

25
R ESULT
Customizing settings are checked.

26
4.2. PREPARATION AND MIGRATION CUSTOMIZING FOR GENERAL LEDGER
4.2.1. ACTIVATE SAP REFERENCE IMG FOR FINANCIAL ACCOUNTING (N EW)

N OTE
This step will NOT be required as IMG menu would already be available in the system

U SE
In this Customizing activity, the SAP reference IMG structure for Financial Accounting (New) and the menu is
activated.

P ROCEDURE
1. To activate the SAP reference IMG structure do the following:

a) Select transaction se38.

b) Enter the program RFAGL_SWAP_IMG_NEW.

c) Select Execute.

d) On the screen Activate/Deactivate New Implementation Guide select Activate New IMG and choose
Execute.

In the SAP Reference IMG the structure for Financial Accounting (New) is visible and can be used.

2. To activate the menu do the following:

a) Select transaction se38.

b) Enter the program RFAGL_SWAP_MENU_NEW.

c) On the screen Activate/Deactivate New Implementation Guide select Activate New MENU and choose
Execute.

In the menu the relevant structure is visible and can be used

R ESULT
SAP reference IMG structure will be activated.

4.2.2. C HECK AND ADOPT FISCAL YEAR VARIANT

U SE
In this Customizing activity, you compare the fiscal year variants between controlling areas and their assigned
company codes. Once you execute this system will check fiscal year variant of your company code and the
controlling area, and both should match otherwise system will throw error.

P ROCEDURE
Tcode FINS_MIG_FYV

27
IMG Menu details in screenshot.

R ESULT
No activity is required though, since the SAP Best Practices Baseline packages use the variant K4 for both the
controlling area, and all company codes.

4.2.3. MIGRATE GENERAL LEDGER CUSTOMIZING

U SE
In this activity, you migrate all new G/L ledgers to the new configuration.

The following settings are migrated:

 Company code assignments


 Currency settings
 Fiscal year variant
 Open period variant
 Settings for real-time integration of CO-FI

P ROCEDURE
Tcode FINS_MIG_LEDGER_CUST

28
IMG Menu details in screenshot.

R ESULT
General Ledger migration is achieved

4.2.4. D EFINE SETTINGS FOR LEDGERS AND CURRENCY TYPES

U SE
Here you edit the currency types and currency conversion settings that you use in Accounting. You also define the
corresponding ledger settings and assign accounting principles for ledgers and company codes

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

29
Execute the step and ensure the following:

 Since we have only one accounting principle assigned to ledger 0L, no action required in this step.
 In case of multiple accounting principles, e.g. IFRS and GAAP are assigned to the ledger 0L, the flag Parallel
accounting using additional G/L accounts will be by default selected

R ESULT
Parallel accounting for GL accounts check box is selected

30
4.2.5. D EFINE LEDGER FOR CO VERSION

U SE
In this activity, you assign G/L ledgers to controlling (CO) versions. This means that controlling will then read the
actual data (postings) from the G/L ledgers that you specify here.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

R ESULT
Leading ledger 0L has been assigned to the CO Version 0 (Plan/actual version)

31
4.2.6. D EFINE DOCUMENT TYPES FOR POSTING IN CONTROLLING

U SE
In this activity, you can create new document types for postings in Controlling, for example you can create a
document type that you can use for the manual reposting of primary costs.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

Execute and follow the screenshot

32
R ESULT
CO as the document type has been defined to be used for CO postings

Document type "CO" is created in OBA7

4.2.7. D EFINE DOCUMENT TYPE MAPPING TO CO BUSINESS TRANSACTIONS

U SE
In this activity you define a mapping variant that maps CO business transactions to document types. This mapping
must be done for all CO business transactions that do actual postings.

Note that for actual settlement of internal orders with a settlement rule that specifies settlement to a G/L account,
the mapping defined in this activity is overridden by the Document type setting in the Maintain Settlement Profiles
activity. You can find this activity under Controlling -> Internal Orders -> Actual Postings -> Settlement.

Upgrades: The migration of the ledger Customizing generates a default mapping variant in which all CO business
transactions are mapped to the document type that was entered in the variant for real-time CO-FI integration.

It is important to note that each company code that contains CO documents must be assigned to a mapping
variant. This means that if no mapping variant exists yet, you need to manually create one and enter a document
type for all CO business transactions.

In the Mapping of CO Bus. Transactions to Document Types view, you have to manually create an entry for each
value that is shown in the value help of the CO business transaction field and to enter a document type.

The reason for this is that the Migrate Accounting Documents to Universal Journal Entry Structure activity requires
a document type for each CO document.

Here we can define Document Type Mapping Variants for CO Business Transactions

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

33
Execute

R ESULT
The document type mapping for CO Business Transactions is defined

4.2.8. C HECK AND DEFINE DEFAULT VALUES FOR POSTINGS IN CONTROLLING

34
U SE
In this activity, you define default values for use in CO business transactions whose user interfaces do not allow
you to enter a document type or a ledger group for posting purposes.

If you do not enter a default ledger group, all CO postings will be done to all G/L ledgers.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

Execute and check

R ESULT
Ledger group "0L" is assigned to Company code 1000

35
4.2.9. D EFINE OFFSETTING ACCOUNT DETERMINATION TYPE

U SE
In this customizing activity you define how the system calculates the offsetting account in all applications.

You have to carry out this activity before you perform any migration activities that affect the offsetting account.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

Execute, click on new entries and select the recommended option is “As case 2, but including line items generated
automatically”

36
R ESULT
The offsetting account determination type is defined.

4.2.10. DEFINE SOURCE LEDGER FOR MIGRATION OF BALANCES

U SE
In this activity you define the source ledger (and eventually the source database table) of the balances for general
ledger accounting using the following:

• Target Ledger
• Company Code (you can specify * to apply the settings to all company codes)
• Starting Fiscal Year (by specifying year 0001 you apply the settings for all fiscal years)

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

37
Execute

Since New G/L Accounting was already active in the baseline ERP system, the ledger 0L has been selected as source
ledger for the migration of balances

R ESULT
The source ledger is defined for migration of balances.

38
4.2.11. EXECUTE CONSISTENCY CHECK OF GENERAL LEDGER SETTINGS

U SE
In this activity, the Customizing settings for the ledgers are checked. This check must run without error messages
before you continue, for example with the migration of transaction data or any other activities.

P ROCEDURE
Tcode FINS_CUST_CONS_CHK
IMG Menu details in screenshot.

The consistency check has to run and no errors should be reported.

39
Executed program “FINS_INS_TKA09_FR01” in SE38 to generate missing of version “0” to controlling area FR01, as
SAP suggested in note “2191912”

Assigned version to company code FR01 in configuration to resolve the above issue.

T ROUBLESHOOTING
You might encounter 2 errors:

40
1. Fiscal year variant is not maintained for company MX03: Fiscal year variant is assigned for company code MX03
as in screenshot

2. Version "0" is not maintained in controlling: Follow instruction as mentioned in SAP NOTE "2191912"

R ESULT
Consistency check of General Ledger settings is executed

4.2.12. ACTIVATE BUSINESS FUNCTIONS .

U SE
In this activity you activate the business functions that are necessary for migrating to SAP S/4HANA.

P ROCEDURE
The activation of the business functions is mandatory for the SAP Simple Finance add-on.

Following business functions have been activated:

- FIN_GL_CI_1

- FIN_GL_CI_2

- FIN_GL_CI_3

Go to Transaction code SFW5 and check below business functions are active or not.

Tcode SFW5

R ESULT
Business functions activated

41
4.3. PREPARATION AND MIGRATION CUSTOMIZING FOR ASSET ACCOUNTING
4.3.1. MIGRATE CHART OF DEPRECIATION

U SE
If you are already using classic Asset Accounting and want to migrate to new Asset Accounting, you have to
migrate the charts of depreciation from classic Asset Accounting. This activity supports you in this migration.

Using this activity, you can (among other things) assign depreciation areas to an accounting principle.

P ROCEDURE
Tcode FAA_CHECK_MIG2SFIN
IMG Menu details in screenshot.

R ESULT

42
The chart of depreciation, which is used in the SAP Best Practices Baseline package, is migrated

4.3.2. D ISPLAY MIGRATION LOG

U SE
You can use this activity to display the logs of the migration of charts of depreciation during either the test run or
the update run.

P ROCEDURE
Tcode FAA_SHOWLOG_MIG2SFIN
IMG Menu details in screenshot.

If the migration log displays error messages, you should analyze them and take consequent actions.

Example: If the error message No accounting principle found for chart of depreciation 10US/depreciation area 01 is
displayed, you should correct the depreciation areas in the chart of depreciation by assigning the respective
accounting principles.

43
R ESULT
The migration log is displayed and checked for errors

4.3.3. P ERFORM ADDITIONAL MANUAL ACTIVITIES

U SE
After the migration of the charts of depreciation, you have to make more Customizing settings before you can
check and activate new Asset Accounting.

Here you should at least perform the mandatory activity Define Technical Clearing Account for Integrated Asset
Acquisition. Plus, in baseline the accounting principle (local GAAP) is assigned to all depreciation areas.

P ROCEDURE

T ECHNICAL CLEARING ACCOUNT FOR A SSET A CQUISITION


Tcode SPRO
IMG Menu details in screenshot.

Create one Asset recon account under balance sheet and assign it in below configuration

44
Ignore warning message and proceed further

A. Define depreciation area for accounting principle GAAP.

45
R ESULT
The additional activities are performed successfully

4.3.4. C HECK PREREQUISITES FOR ACTIVATING ASSET ACCOUNTING

U SE
In order to be able to use new Asset Accounting as an application in SAP Accounting powered by SAP HANA, you
must execute the following steps as in the procedure

P ROCEDURE
Tcode FAA_CHECK_ACTIVATION
IMG Menu details in screenshot.

If you encounter any error, you need to correct it and then run this check report again until it ends with the
message. No error should be found and all traffic lights are to be green.

46
T ROUBLESHOOTING
We have to resolve all above errors to proceed further

Remove Chart of depreciation to company code assignments for not actively using company codes, and assign
chart of depreciation assignment to company code only COD which we are migrating

Tcode OAOB

After maintaining above configuration we are left with below errors which needs to be resolved before activating
Asset Accounting

47
Since the above company codes are not available in system, but system is able to find this company codes in some
table, it is very difficult to identify those tables and remove entries, so instead of deleting we have to create those
company codes in system and then issue gets resolved.

Next issue:

Screen shot of Depreciation area 03

Depreciation area 03 is not fully posted for Periodic postings so we need to run periodic posting program to update
these values, but as part of Simple finance migration sap has removed periodic posting program, in simple finance
it is not needed, because of the above reason we have deleted depreciation area 03 to proceed further.

48
R ESULT
After doing above changes now all errors resolved, Asset accounting can be activated now

4.3.5. ACTIVATE ASSET ACCOUNTING

U SE
In order to be able to use new Asset Accounting in SAP Accounting powered by SAP HANA, you must execute the
following steps as in Procedure.

P ROCEDURE
Tcode FAA_DO_ACTIVATION
IMG Menu details in screenshot.

49
50
Ignore all warning messages press “Enter” to activate.

R ESULT
Now new asset accounting is activated.

4.4. PREPARATION AND MIGRATION OF CUSTOMIZING FOR CONTROLLING


4.4.1. EXECUTE BW DATA EXTRACTION FOR ACCOUNT BASED COPA

U SE
Execute a delta extraction in SAP Business Information Warehouse for those account-based CO-PA data sources for
which you use the delta procedure. This is necessary because otherwise account-based CO-PA line items that are
not extracted before the migration may be ignored after the migration when the next delta is loaded.

P ROCEDURE
Since we are following Costing based CO-PA, there is no need to execute these steps. Because the baseline used
only the cost-object based profitability analysis prior the migration, this step is not required.

51
4.4.2. ADAPT SETTINGS FOR THE CHANGE OF PROFITABILITY SEGMENT CHARACTERISTICS

U SE
In this activity, you adapt the settings for profitability segment characteristics (segment level characteristics) made
in classic CO-PA with transaction KEQ3 (SAP Customizing Implementation Guide -> Controlling -> Profitability
Analysis -> Structures -> Define Profitability Segment Characteristics (Segment-Level Characteristics)), since this
summarization function is no longer available in SAP Accounting powered by SAP HANA.

Tcode FCO_MIGRATION_COPA
IMG Menu details in screenshot.

P ROCEDURE
All the settings for profitability segment characteristics (segment level) made in transaction KEQ3 have been
deleted by running the report FCO_MIGRATION_COPA

R ESULT
Settings adapted.

4.4.3. MAINTAIN OPERATING CONCERN

U SE
In this activity, you activate your operating concerns for account-based profitability analysis. If this setting is not
made, the new profitability reporting will not be available

P ROCEDURE
Tcode KEA0
IMG Menu details in screenshot.

52
The report FCO_ADD_COPA_FIELD_TO_ACDOCA is started in background and activates the operating concern for
account-based Profitability Analysis

NOTE: If we are are not using COPA for our company code (as seen in screenshots for company codes UP02 and
UP03), we skip this step.

4.4.4. ACTIVATE ACCOUNT BASED PROFITABILITY ANALYSIS

U SE
In this activity, you activate account-based profitability analysis for your operating concerns. If this setting is not
made, the new profitability reporting will not be available.

P ROCEDURE

53
Tcode KEKE

The account-based Profitability Analysis is now active for your concern. Since the cost-based CO-PA has been used
before the SAP Simple Finance add-on, after the activation of account-based CO-PA, both approaches exist and
work correctly in the baseline landscape. The recommended approach by SAP is the Account - Based Profitability
Analysis.

NOTE: If we are are not using COPA for our company code (as seen in screenshots for company codes UP02 and
UP03), we skip this step.

4.5. MIGRATION

N OTE
Some of these steps are not applicable for S4 HANA 1610 and are mentioned for 1511 version for information
purpose and are automatically taken care in final step (click here: Set migration completed)

4.5.1. P ARTITIONING OF UNIVERSAL JOURNAL ENTRY LINE ITEMS TABLE

54
U SE
During the migration to SAP S/4HANA Finance, the table ACDOCA (Universal Journal Entry Line Items) is filled from
the areas of G/L, controlling, material ledger, and asset accounting.

Depending on data volume in the respective applications the ACDOCA table can contain a high number of records.
This high number of records can have a negative effect on performance of selects and merge operations.

Consider partitioning the ACDOCA in order to prevent the negative effects listed above. Partitioning splits tables
horizontally into disjunctive sub-tables or partitions. In this way, large tables are broken down into smaller, more
manageable parts. Consult the administration guide for more details.

P ROCEDURE
No action required.

4.5.2. REGENERATE CDS VIEWS AND FIELD MAPPING

U SE
You use this Customizing activity to regenerate the compatibility and data migration views so as to adapt them to
the configuration of customer-specific entities.

P ROCEDURE
Tcode FINS_MIG_REGENERATE
IMG Menu details in screenshot.

Execute in background the program FGL_MIG_REGENERATE_CDS and check the progress in the transaction SLG1
with sub- object FINS_GENERATE.

55
T ROUBLESHOOTING
If one table was not generated because of authorization issue, execute this with ABAP team, and it still doesn’t
work – i.e. if any table generation fails, we can use follow the steps given in note "2182930"

R ESULT
The views and field mappings are regenerated.

4.6. MIGRATION OF COST ELEMENTS AND CUSTOMIZING – NOT APPLICABLE FOR S4


HANA 1610

NOTE
The below steps are for HANA 1511 and are not applicable for s4 HANA 1610. In the new version, the IMG Menu
contains only documentation for Migration of Cost Elements. One need not try to perform migration steps in this
document which are mentioned for 1511 version.

56
U SE
In SAP S/4HANA, the master data of G/L accounts and cost elements are merged. Cost elements get special G/L
accounts and are maintained in transaction FS00 (Edit G/L Account Centrally).

Before you migrate G/L Accounts and Cost Elements you have to check whether the G/L accounts and cost
elements are consistent. An inconsistency could be, for example, that no G/L account exists for a primary cost
element. You need to correct the indicated inconsistencies before the migration, otherwise the G/L account
master records may have the wrong account types after migration.

After you have checked and corrected all inconsistencies and errors, you can migrate your G/L accounts and cost
elements. The migration merges the cost elements into the G/L account master data.

4.6.1. C HECK CONSISTENCY OF GL ACCOUNTS AND COST ELEMENTS (FOR 1511)

P ROCEDURE
Tcode
IMG Menu details in screenshot.

An inconsistency could be that no G/L accounts exist for a primary cost element. Here is an example of an error
found in SAP Best Practices Baseline packages for China:

Error message: Primary cost element 41010100/CN01 (type 1) not found in chart of accts CACN

Solution: Create the missing G/L account with account type primary cost element for CN client. Take a similar
account as template for setting up the G/L account characteristics.

After all corrections, G/L accounts and cost elements are consistent with each other and G/L account master
records have the right account types

57
4.6.2. MIGRATE SECONDARY COST ELEMENTS TO GL ACCOUNTS (FOR 1511)

P ROCEDURE
Tcode FINS_MIG_GCM

All secondary cost elements, as well as the primary cost elements, are represented as G/L accounts

58
4.6.3. D ISPLAY STATUS OF M IGRATION COST ELEMENTS (FOR 1511)

U SE
With this transaction, you can monitor the status of the merge of G/L accounts and cost elements. In the baseline
both company codes 1000 and 1010 use the same chart of accounts. The chart of accounts tables are updated
when report is executed for the first company code

P ROCEDURE
Tcode FINS_MIG_MONITOR_GCM

4.6.4. MIGRATE DEFAULT ACCOUNT ASSIGNMENTS

P ROCEDURE
Tcode FINS_MIG_DAA

The default assignments are transferred from the master data table CSKB to the Customizing table TKA3A

59
4.6.5. D ISPLAY STATUS OF DEFAULT ACCOUNT ASSIGNMENTS (FOR 1511)

P ROCEDURE
Tcode FINS_MIG_MONITOR_DAA
With this transaction, you can check the status of the transfer of default account assignments.

After the migration, the default account assignments are accessible via transaction OKB9.

4.6.6. ADAPT AUTHORIZATIONS (FOR 1511)

U SE
Because G/L accounts and cost elements are in the same table in Simple Finance 2.0 system, you need to adapt the
authorization roles for creating/changing G/L accounts and cost elements.

P ROCEDURE
Executed but system will ask for role – could be left blank in case those details are not there.

4.7. TECHNICAL CHECK OF TRANSACTIONAL DATA – NOT APPLICABLE FOR S4 HANA


1610

60
NOTE
The below steps are for HANA 1511 and are not applicable for s4 HANA 1610. In the new version, the IMG Menu
contains only documentation for Technical check of transactional data. One need not try to perform migration
steps in this document which are mentioned for 1511 version.

4.7.1. ANALYZE TRANSACTIONAL DATA (FOR 1511)


Use

When you execute the migration in the Customizing activity Start and Monitor Migration, the system analyzes if all
transactional data is complete and correct.

P ROCEDURE
Tcode FINS_RECON_RCO

Run the report.

61
R ESULT
The report runs and checks whether all transactional data are complete and correct

4.7.2. D ISPLAY STATUS OF ANALYZE TRANSACTIONAL DATA (FOR 1511)

U SE
You use this report to check the status of the transactional data analysis.

P ROCEDURE
Tcode FINS_MIG_MONITOR_RCO

R ESULT
Status is displayed

4.7.3. RECONCILE TRANSACTIONAL DATA (1511)

U SE
The report checks whether all FI documents are consistent and ready to be migrated. It checks prerequisites for
the migration.

P ROCEDURE
Tcode FINS_RECON_RC1

62
R ESULT
Prerequisites checked.

4.7.4. D ISPLAY STATUS OF R ECONCILE TRANSACTIONAL DATA (FOR 1511)

U SE
You use this report to check the status of the transactional data reconciliation

P ROCEDURE
Tcode FINS_MIG_MONITOR_RC1

T ROUBLESHOOTING
If you get errors for data mismatch between tables BSID/BSAD/BSIS/BSAS, apply OSS note "2248211"

63
Solution: Implement note 2248211 to resolve the above issue.

4.8. MIGRATION ENRICHMENT OF DATA – NOT APPLICABLE FOR S4 HANA 1610

NOTE
The below steps are for HANA 1511 and are not applicable for s4 HANA 1610. In the new version, the IMG Menu
contains only documentation for ENRICHMENT OF DATA. One need not try to perform migration steps in this
document which are mentioned for 1511 version.

64
4.8.1. ENRICH TRANSACTIONAL DATA (FOR 1511)

U SE
The report enriches transactional data and documents and then migrates them to SAP Accounting powered by SAP
HANA.

P ROCEDURE
Tcode FINS_MIGRATION

4.8.2. D ISPLAY STATUS OF MIGRATION ENRICHMENT DATA (FOR 1511)

U SE
You use this report to check the status of the transactional data enrichment and migration.

65
P ROCEDURE
Tcode FINS_MIG_MONITOR

4.8.3. C HECK OF MIGRATED DOCUMENTS (FOR 1511)

U SE
This report checks the result of the previous step of the migration. It checks document fields that are used in the
following migration steps.

P ROCEDURE
Tcode FINS_RECON_RC2

4.8.4. D ISPLAY STATUS OF CHECK MIGRATED DOCUMENTS (FOR 1511)

U SE
You use this report to check the status of the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_RC2

All checks from the last migration step should end with status green (no issues).

66
4.9. MIGRATION OF LINE ITEMS INTO NEW DATA STRUCTURE – NOT APPLICABLE FOR
S4 HANA 1610

NOTE
The below steps are for HANA 1511 and are not applicable for S4 HANA 1610. In the new version, the IMG Menu
contains only documentation for MIGRATION OF LINE ITEMS. One need not try to perform migration steps in this
document which are mentioned for 1511 version.

4.9.1. MIGRATE ACCOUNTING DOCUMENTS TO UNIVERSAL JOURNAL ENTRY STRUCTURE (FOR 1511)

U SE

67
All accounting documents are migrated to the Unified Journal Entry structure and are enriched with COPA
information.

SAP recommends that you execute this migration step in all clients, also in clients where there are no transactional
data. This is required so that the migration status for the client can be set to ‘finished’.

P ROCEDURE
Tcode FIND_MIG_UJ

4.9.2. D ISPLAY STATUS OF DOCUMENTS TO UNIVERSAL JOURNAL ENTRY (FOR 1511)

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_UJ

All data packages are to be displayed with status green (no issues).

Once you complete this step you can see values in ACDOCA table

68
R ESULT
The status is displayed.

4.9.3. C HECK MIGRATION OF ACCOUNTING DOCUMENTS TO UNIVERSAL JOURNAL ENTRY (FOR 1511)

U SE
This report performs several checks to the migrated documents.

You must perform this step before migrating the account balances.

P ROCEDURE
Tcode FINS_RECON_RC3

69
4.9.4. D ISPLAY STATUS OF CHECK ACCOUNTING DOCUMENTS MIGRATION (FOR 1511)

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_RC3

All checks from the last migration step should be ended with status green (no issues).

R ESULT
Status is displayed.

4.9.5. MIGRATE GENERAL LEDGER ALLOCATIONS (FOR 1511)

U SE
In this activity, you change existing G/L allocation cycles for actual values to new journal entry database tables.

P ROCEDURE
Tcode FINS_MIG_GL_ALLOC

All allocations have been migrated to the new Unified Journal Entry structure and no errors are displayed.

70
4.10. MIGRATION OF BALANCES – NOT APPLICABLE FOR S4 HANA 1610

NOTE
The below steps are for HANA 1511 and are not applicable for S4 HANA 1610. In the new version, the IMG Menu
contains only documentation for MIGRATION OF BALANCES. One need not try to perform migration steps in this
document which are mentioned for 1511 version.

71
4.10.1. MIGRATE BALANCES (FOR 1511)

U SE
The "Migration of Balances" step ensures that, after migration of the documents, the aggregated view to the
Universal Journal delivers the same results as the previous totals-based reporting.

SAP recommends that you execute this migration step in all clients, also in clients where there are no transactional
data. This is required so that the migration status for the client can be set to ‘finished’.

P ROCEDURE
Tcode FINS_MIG_DLT

All G/L account balances are migrated.

4.10.2. DISPLAY STATUS OF M IGRATE BALANCES (FOR 1511)

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_DLT

All data packages are to be displayed with status green (no issues).

R ESULT

72
Status is displayed.

4.10.3. CALCULATE INITIAL DEPRECIATION VALUES (FOR 1511)

U SE
The migration from the classical to the New Asset Accounting is one precondition for migrating to Simple Finance.

P ROCEDURE
Tcode AFAR

After completing the migration of transactional data and account balances, you need to recalculate the planned
depreciation values for the Asset Accounting.

After running this report, the initial planned depreciation values have been calculated and stored in the respective
database tables.

R ESULT
Initial values calculated.

4.10.4. CHECK MIGRATION OF BALANCES (FOR 1511)

U SE
This report checks the result of the previous step of the migration.

P ROCEDURE
Tcode FINS_RECON_RC4

If you find errors, you need to make the respective corrections and run the migration again. If you need to repeat
the migration, please read the SAP note 2138644 first. This SAP note advices on how to reset the migration in case
you need to repeat it.

73
4.10.5. DISPLAY STATUS CHECK OF MIGRATION BALANCES (FOR 1511)

U SE
This report helps you monitoring the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_RC4

All checks from the last migration step should end with status green (no issues).

R ESULT
Status is displayed.

4.11. COMPLETE MIGRATION

N OTE
This is a single step in S4 HANA 1610 (refer Set migration completed) as mentioned in for complete migration
which will take care of all the steps which will automatically take care of all the steps mentioned in this document
for 1511 version (and hence eliminating any manual work to perform those steps for 1511). One need not try to
perform migration steps in this document which are mentioned for 1511 version.

4.11.1. CONVERT HELD DOCUMENTS (FOR 1511, NOT APPLICABLE FOR S4 HANA 1610)

74
P ROCEDURE
Tcode FINS_RFTMPBLU

You need to convert previously held documents, before you can create new ones or processing existing ones.

R ESULT
As a result, all held documents are converted or deleted.

4.11.2. RECONCILE AND COMPARE M IGRATED DATA (FOR 1511, NOT APPLICABLE FOR S4 HANA
1610)

N OTE
Only display documentation is available for this step in S4 HANA 1610 as seen in screenshot.

P ROCEDURE
 Reconcile ledger 0 with ledger 0L (transaction GCAC).
 -Compare the company's key figure with the ones prior to the migration:
 The financial statements (program RFBILA00)
 The asset history sheet (program RAGITT_ALV01)
 The depreciation run for the planned depreciations (program RAHAFA_ALV01)
 The totals report for cost centers (transaction S_ALR_87013611)
 Sales order selection (program RKKBSELL)
 The G/L account balance list (program RFSSLD00)
 The general ledger line items list (program RFSOPO00)

75
 The compact document journal (program RFBELJ00)
 The vendor sales (program RFKUML00)
 The vendor open item list (program RFKEPL00)
 The customer sales (program RFKUML00)
 The customer open item list (program RFDEPL00)
 The customer recurring entry original documents (program RFDAUB00)
 The cost centers: actual/plan/variance (transaction GR55 with report group 1SIP)

4.11.3. SET MIGRATION COMPLETED

U SE
This is the final and single step in S4 HANA 1610 migration which will automatically take care of all the steps
mentioned in this document for 1511 version (and hence eliminating any manual work to perform those steps for
1511)

P ROCEDURE
Tcode FINS_MIG_FINISH
IMG Menu details in screenshot.

After executing checks, set migration completed.

76
R ESULT
Data migration is set to status ‘Finished’

4.12. ACTIVITIES AFTER MIGRATION


4.12.1. TRANSFER APPLICATION INDEXES

U SE
In this Customizing activity, application indexes are transferred to the cold partition of the database in order to
reduce main memory consumption.

For this you use Data Aging, therefore it is required to activate the business function DAAG_DATA_AGING in your
system.

P ROCEDURE
Tcode FINS_MIG_INIT_COLD
IMG Menu details in screenshot.

77
4.12.2. DISPLAY STATUS OF TRANSFER APPLICATION INDEXES

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FINS_MIG_MONITOR_CLD
IMG Menu details in screenshot.

All data packages should be displayed with status green (no issues).

R ESULT
Status displayed in Green

78
4.12.3. FILL DUE DATES IN FI DOCUMENTS

U SE
In this Customizing activity, due date fields are filled in the FI line items for customers and vendors and for G/L
account line items that have a base line date.

P ROCEDURE
Tcode FIN_MIG_DUE
IMG Menu details in screenshot.

79
R ESULT
Due dates are filled as seen in screenshot.

4.12.4. DISPLAY STATUS OF FILL DUE DATES IN FI DOCUMENTS

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FIN_MIG_MONITOR_DUE
IMG Menu details in screenshot.

All data packages should be displayed with status green (no issues).

80
R ESULT
Status is displayed.

4.12.5. FILL OFFSETTING ACCOUNT IN FI DOCUMENTS

U SE
During data migration, you transfer FI documents to SAP Accounting powered by SAP HANA. As part of this process
you use this Customizing activity to fill the offsetting account in FI documents.

P ROCEDURE
Tcode FIN_MIG_GKONT
IMG Menu details in screenshot.

The offsetting account is filled in the FI documents.

Precondition for this activity is that you have defined an offsetting account determination type in the Customizing
activity Define Offsetting Account Determination Type.

81
4.12.6. DISPLAY STATUS OF FILL OFFSETTING ACCOUNT IN FI DOCUMENTS

U SE
You can use this report to monitor the status of the previous step.

P ROCEDURE
Tcode FIN_MIG_MONITOR_GKO
IMG Menu details in screenshot

All data packages should be displayed with status green (no issues).

82
R ESULT
Status is displayed.

4.13. MIGRATE HOUSE BANK ACCOUNTS

U SE
In this Customizing activity you migrate house bank accounts. For more information, see Migrate House Bank
Accounts.

4.13.1. P REREQUISITES
You need to perform customizing for Bank Account Management first and then run the transaction

D EFINE NUMBER RANGES FOR BANK ACCOUNT TECHNICAL ID ’ S

83
D EFINE N UMBER R ANGES FOR C HANGE R EQUESTS

D EFINE SETTINGS FOR B ANK ACCOUNT MASTER DATA

4.13.2. MIGRATE HOUSE BANK ACCOUNTS

U SE

84
In this Customizing activity you migrate house bank accounts. For more information, see Migrate House Bank
Accounts.

P ROCEDURE
Tcode FCLM_BAM_MIGRATION
IMG Menu details in screenshot.

85
R ESULT
The house bank accounts are migrated.

4.13.3. CLASSIFY FI DOCUMENT TYPES FOR DOCUMENT SPLITTING

U SE
Here we need to map Document type “CO” for document splitting

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

86
R ESULT
The FI Document types for Document splitting are classified.

87
5. STEPS IN MIGRATION OF SIMPLE LOGISTICS

5.1. FOR CREDIT MANAGEMENT


5.1.1. P REPARATORY ACTIVITIES AND MIGRATION OF CUSTOMIZING FOR CREDIT M ANAGEMENT

M IGRATE C REDIT M ANAGEMENT C USTOMIZING

U SE
In this activity, you migrate to the new configuration of credit management. When you execute this activity, the
system also checks whether a migration of Credit Management settings is necessary.

The following settings are migrated and copied to a Customizing transport:


• From credit control areas to credit segments
• From the Customizing table for the risk category to the risk class
Note: As a business partner in FIN-FSCM, the customer has only one risk class for all segments. To ensure that the
correct risk class is migrated, you should have one consistent risk category for the customer in all credit control
areas.
• Necessary Customizing entries for the documented credit decision are made.
• Configuration settings for the automatic credit control are made (transaction OVA8).

P ROCEDURE
Tcode FINS_MIG_CREDIT_CUST
IMG Menu details in screenshot.

Click on Execute as in screenshot below then.

88
D EFINE C REDIT R EPRESENTATIVE G ROUP AS B USINESS P ARTNER R ELATIONSHIP :

U SE
Here one defines the business partner for group and organization with Tcode “BP”.

P ROCEDURE
Tcode BP
IMG Menu details in screenshot.

Click on Execute as shown in screenshot.

89
A SSIGN C REDIT R EPRESENTATIVE G ROUP TO C REDIT A NALYST G ROUP

U SE
Once we have defined a credit representative group as a business partner of group type, we assign this credit
representative group to an accounting clerk group for each credit control area.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

90
D EFINE C USTOMER C REDIT G ROUP

U SE
In this IMG activity you can define the customer credit groups required.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

91
A SSIGN C REDIT M ANAGEMENT G ROUP TO C USTOMER C REDIT G ROUP

U SE
In this step, you define groups per credit control area depending on your requirements. In a second step, you can
assign each customer to one of these groups in the application menu for the credit management master data.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

92
A SSIGN C REDIT M ANAGEMENT P ROCESSOR TO C REDIT A NALYST G ROUP

U SE
In this step, you can assign each customer to one of these groups in the application menu for the credit
management master data.

93
P ROCEDURE
Tcode BUB1
IMG Menu details in screenshot.

Put: Relationship category: UKMSBG and then click on execute

And then add the business partner for Group and Organization.

94
In this case, the following data have been created:

Business partner: 3 (for Group)

Business Partner: 2(For Organization)

C HECK C USTOMIZING S ETTINGS

U SE
When you execute this activity, it checks whether the credit management customizing is set up correctly for the
migration.

The system issues warning or error messages in case of missing or wrong set up of customizing.

P ROCEDURE
Tcode FINS_MIG_CREDIT_CHCK
IMG Menu details in screenshot.

Check customization, status of the customizing which should appear as green.

95
5.1.2. C REDIT MANAGEMENT MIGRATION

M IGRATE C REDIT M ANAGEMENT M ASTER D ATA

U SE
In SAP S/4HANA, the master data from Credit Management in Accounts Receivable (FI-AR) is migrated to SAP
Credit Management in Financial Supply Chain Management (FIN-FSCM-CR).

The master data migration is done per customer and credit control area: the credit limits, the customer credit
groups, the credit representative groups, the text fields, and the risk categories are migrated in accordance with
the assignments made in Customizing.

P ROCEDURE
Tcode FINS_MIG_MK1
IMG Menu details in screenshot.

96
Click on execute

D ISPLAY S TATUS OF M IGRATION OF C REDIT M ANAGEMENT M ASTER D ATA

U SE
In this Customizing activity you check the status of the migration of credit management master data.

P ROCEDURE
Tcode FINS_MIG_MONITOR_MK1
IMG Menu details in screenshot.

97
Status should be green.

M IGRATE C REDIT M ANAGEMENT E XPOSURE

U SE
The migration is executed in two steps:

• Credit values of open orders and deliveries are migrated to the credit exposure.

• Payment behavior data from Credit Management is recalculated based on the data in Accounts Receivable
(FI-AR).

To view the migrated data, you use transaction UKM_BP.

98
P ROCEDURE
Tcode FINS_MIG_MK2
IMG Menu details in screenshot.

Click on execute.

D ISPLAY S TATUS OF C REDIT M ANAGEMENT E XPOSURE M IGRATION

U SE
In this Customizing activity, you check the status of the recalculation of Commitments and Payment Behavior.

P ROCEDURE
Tcode FINS_MIG_MONITOR_MK2

99
IMG Menu details in screenshot.

Status should be green

I NITIALIZE D OCUMENTED C REDIT D ECISIONS

U SE
In SAP S/4HANA, sales and delivery documents blocked by credit management are managed with documented
credit decisions. You use this activity to initialize documented credit decisions in SAP Credit Management.

P ROCEDURE
Tcode FINS_MIG_MK3

100
IMG Menu details in screenshot.

Click on execute.

D ISPLAY S TATUS OF I NITIALIZATION OF D OCUMENTED C REDIT D ECISIONS

U SE
In this Customizing activity, you check the status of the migration of sales and delivery documents blocked by
credit management.

P ROCEDURE
Tcode FINS_MIG_MONITOR_MK3
IMG Menu details in screenshot.

101
Status should be green

5.1.3. TRANSPORTING CHANGES AND RE- EXECUTION FOR CREDIT M ANAGEMENT


Once done in development system then transport the changes to Quality system and re-execute the below process
again.

 Conversion of Accounting to SAP S/4HANA -> Preparations and Migration of Customizing -> Preparatory
Activities and Migration of Customizing for Credit Management
o Assign Credit Management Processor to Credit Analyst Group
 Conversion of Accounting to SAP S/4HANA -> Data Migration -> Credit Management Migration
o Migrate Credit Management Master Data
o Display Status of Migration of Credit Management Master Data
o Migrate Credit Management Exposure

102
o Display Status of Credit Management Exposure Migration
o Initialize Documented Credit Decisions
o Display Status of Initialization of Documented Credit Decisions
 Create a BP for organization and Group.

103
5.2. FOR MANUFACTURING ACTIVITIES
5.2.1. REPORT EXECUTION FOR MRP RECORD CREATION

I. R EPORT PPH_SETUP_MRPRECORDS

U SE
You use this report to create MRP records that are to be used for operative planning.

P REREQUISITES
The materials in the plant must be relevant for MRP. That is, you must have maintained the MRP views in the
material master records of the materials and have set a suitable MRP type.

P ROCEDURE
Tcode SE38
Execute the report PPH_SETUP_MRPRECORDS

II. R EPORT PPH_SETUP_MRPRECORDS_SIMU

U SE
If you want to create MRP records to be used for simulative planning (long-term planning), this second report is
available.

P REREQUISITES
The materials in the plant must be relevant for MRP. That is, you must have maintained the MRP views in the
material master records of the materials and have set a suitable MRP type.

P ROCEDURE
Tcode SE38
Execute the report PPH_SETUP_MRPRECORDS_SIMU

5.2.2. C ORRECT THE S ECONDARY PERSISTENCE OF S ALES DOCUMENTS RELEVANT TO ATP – E XECUTE
REPORT ATP_VBBE_CONSISTENCY

U SE
This report reads all the sales orders and deliveries with open quantities and compares this information with the
available entries on the database. By selecting the Simulation Mode checkbox, you can perform this report in
simulation. If you do not start the report in simulation mode, all inconsistencies found will be corrected
automatically.

P ROCEDURE
Tcode SE38
Execute the report ATP_VBBE_CONSISTENCY

5.2.3. P REPARATIONS AND MIGRATION OF CUSTOMIZING FOR MRP ACTIVATION

I. O VERALL M AINTENANCE OF R EPETITIVE M ANUFACTURING P ROFILE

104
U SE
In order to activate MRP on SAP HANA you cannot have total requirements for sales orders or for dependent
requirements. Aggregate requirements are no longer supported by SAP HANA, as they can now be aggregated at
runtime. Therefore, before proceeding with the business function activation, you must make sure that there is no
material with total requirements.

P ROCEDURE
Tcode OSP2
IMG Menu details in screenshot.

In change view of Overall Maintenance of Repetitive Manufacturing Profile, select REM profile as shown and click
on details (lens icon):

105
Maintain parameters and values as shown.

Field Aggregate Reqmts in tab Control data 2 – Mandatory to Tick as shown in second screenshot from here.

Total dependent requirements are stored on table RQIT. Therefore, you should check if there is any entry in this
table. If you find any entry in this table, it’s because there is a repetitive manufacturing profile (Transaction OSP2)
with the setting Aggregate reqmts (aggregate requirements) in use.

II. A VAILABILITY CHECKING GROUP IN THE MATERIAL MASTER

U SE

106
This setting can be generally found in the MRP3 tab of the material master (Transaction MM02). The available-to-
promise (ATP) checking group (Availability Check) is the standard checking group delivered by SAP with total
records.

P ROCEDURE
Tcode MM02
In MRP 3 view, field Availability Check to be 02

Note: Parallel currencies are not defined for our Best Practices company code.

III. D EFINE C HECKING GROUP

U SE
We need to have a custom checking group with total requirements

P ROCEDURE
Tcode OVZ2
IMG Menu details in screenshot.

107
You must check the entries in the customizing activity Define Checking Groups any checking group with the option
B - Totals records per day. You should replace this value with A - Single records

Tcode SE38

After making sure that the ATP checking group is not used in any material, and that there is no custom checking
group with total records per day, you should execute report SDRQCR21 from within Transaction SE38 in order to
recreate sales orders and delivery requirements. You should not find any records in table VBBS after the report
execution.

108
IV. S ETUP N UMBER RANGE FOR MRP L IVE

U SE
It is necessary to set this up.

P ROCEDURE
Tcode SNRO

Interval for planned orders (object PLAF), reservations/dependent requirements (object RESB) and purchase
requisitions (object BANF).

It is necessary to create a new interval with the key PP for each one of these elements. The following rules must be
considered:

 It must be a numeric interval, which means that we cannot use letters.


 This interval must not overlap with any other interval for this object.
 This interval should be used for MRP Live only, so you cannot use it for any other purpose. The procedure
to create a new interval for object BANF is outlined below, and must be repeated for objects PLAF and
RESB

5.2.4. ACTIVATION OF MRP LIVE ON HANA P ROCEDURES

HANA T RANSPORT C ONTAINERS ACTIVATION FOR MRP L IVE ON HANA

U SE
This step activates MRP Live on HANA Procedures. Once the SAP Note 1907934 is implemented, the HANA
Transport Containers will be activated for each release and support package.

P ROCEDURE
SAP Note 1907934: MRP Live on Hana procedures activation, provides a list of the SAP HANA Transport Containers
(HTCs) that should be activated for each release and support package. For example, our system is running on EHP 7
with Support Package 9; SAP Note 1907934 provides the following list of HTCs:

 HCO_ERP_SAPPL_PPH_V04_SGT
 HCO_ERP_SAPPL_PPH_V04_MRP

109
 HCO_ERP_SAPPL_PPH_V05_READ
 HCO_ERP_SAPPL_PPH_V05_MRP
 HCO_ERP_SAPPL_PPH_V05_SGT

Before running MRP on SAP HANA, we must ensure that all of the SAP HANA delivery units were successfully
deployed, otherwise errors and short dumps may be observed in MRP Live, or in any transactions that access the
MRP on SAP HANA procedures.

After finding the correct HTCs, we should run the report SNHI_NHDU_POST_PROCESS with the flag Activate HTC
checked for all of these HTCs

Tcode SE38
Execute report SNHI_NHDU_POST_PROCESS with the flag Activate HTC checked

P OST P ROCESSING FOR HANA T RANSPORT C ONTAINER C ORRECTION


USE
This step is for HANA Transport Container correction

PROCEDURE
Tcode SE38

Execute Report SNHI_NHDU_POST_PROCESS

5.2.5. C HECKING ACTIVE DEPENDENTS WHILE MRP ON SAP HANA IS BEING ACTIVATED ON A LIVE
SYSTEM
Use

This report checks the existence of active dependent requirements for materials with simple discontinuation and
checks the discontinuation flag (KZAUS) in table RESB for those requirements.

Procedure

Tcode SE38
As MRP on SAP HANA is being activated on a live system, where dependent requirements already exist, we
recommend that you execute report PPH_ADAPT_RESB_DISCONT

5.2.6. P LANNING F ILE ENTRIES CONVERSION

U SE
If you are still using the old planning file table MDVM, or if you are upgrading to SAP S/4HANA, it is necessary to
convert the planning file entries using following 2 reports.

 RMDBVM00
 PPH_SETUP_MRPRECORDS

R EPORT RMDBVM00

P ROCEDURE

110
Tcode OM0F or SE38 (for report RMDBVM00)
Run t code OM0F or execute report RMDBVM00

After the report has executed, all planning file entries will be copied to table DBVM and deleted from table MDVM.

R EPORT PPH_SETUP_MRPRECORDS

U SE
The SAP S/4HANA release, a new planning file table called PPH_DBVM was created. This table is even faster and is
optimized for the SAP HANA database. This report is used to create the planning file entries in table PPH_DBVM
and also as a consistency check for existing planning file entries."

If you are upgrading an older system to SAP S/4HANA, report PPH_SETUP_MRPRECORDS must be executed in
order to convert the planning file entries to this new table.

P ROCEDURE
Tcode SE38
Execute PPH_SETUP_MRPRECORDS in SE38

5.2.7. STEPS BEFORE MRP RUN IN MRP LIVE

C HECK MASTER DATA REPORT PPH_CHECK_MRP_ON_HANA


Use

In order to help you to identify which materials are using a setting not supported by MRP Live, SAP has also
developed a new report to check the master data. With this report, you can evaluate all of your materials and
identify which ones can be planned by MRP Live, and which ones should be planned by the classic MRP
transactions. The fact that this report is available for other releases is interesting, because you can review all of
your master data even before an upgrade.

Procedure

Tcode SE38
Execute PPH_CHECK_MRP_ON_HANA in SE38

Note: It is delivered on the standard system by SAP Note 2143063: Evaluating the material masters for MRP live.
This report can be implemented even on older releases not yet enhanced for SAP HANA.

V IEW PRODUCTION VERSIONS THAT WILL BE CREATED BY MRP


Use

After running the report in actual mode, we can see the proposal of new production versions that will be created
by MRP. The productions are created without a routing, even when there is a valid routing for the material.

Procedure

Tcode SE38
Execute report CS_BOM_PRODVER_MIGRATION

111
6. CUSTOMER-VENDOR INTEGRATION

6.1. STEPS FOR CUSTOMER-VENDOR INTEGRATION FROM REFERENCE DOCUMENTS

U SE
Customer Vendor Integration is required for business partners in order to use Financial Accounting (FI) and SAP
Business partner in parallel. Financial Accounting uses its own customer/vendor master records which are
integrated in all accounting transactions, instead of relying on SAP Business Partner. Accounts Receivables and
Accounts Payable sub ledgers are used to manage accounting data of customers and vendors in FI.

Customer and Vendor integration can be used independent of each other and there are applications that use only
customer integration or vendor integration. CVI is intended as one system/one client solution.

P ROCEDURE
As complete implementation of this feature is yet to be done by our team, CVI can be performed as per the steps
detailed in the attached documents.

1. S4HANA CVI Customer Care Presentation 20160905.pdf


2. J61_S4HANAX_BB_ConfigGuide_EN_XX.docx

A TTACHMENTS

S4HANA CVI
Customer Care Presentation 20160905.pdf

J61_S4HANAX_BB_C
onfigGuide_EN_XX.docx

6.2. VENDOR INTEGRATION


For only Vendor integration, please refer to the following steps:

6.2.1. INITIAL SETTINGS FOR V ENDOR - ERP C/V A CCOUNT GROUP S ETTINGS

S ET U P P ARTNER D ETERMINATION FOR C USTOMER M ASTER

U SE
In this activity, you define the rules that should be used to perform automatic partner determination.

P ROCEDURE
IMG Menu Sales and Distribution  Basic Functions  Partner Determination  Set Up Partner
Determination  Set Up Partner Determination for Customer Master

Transaction S_AL0_96000423
Code

112
IMG Menu details in screenshot.

D EFINE A CCOUNT G ROUPS WITH S CREEN L AYOUT (V ENDORS )

113
U SE
In this step you determine the account groups for vendors.

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

114
C REATE N UMBER R ANGES FOR V ENDOR A CCOUNTS

U SE
You create number ranges for Vendor accounts here.

P ROCEDURE
IMG Menu Financial Accounting (New)  Accounts Receivable and Accounts Payable 
Vendor Accounts  Master Data  Preparations for Creating Vendor Master
Data  Create Number Ranges for Vendor Accounts

115
Transaction S_ALR_87003103
Code
IMG Menu details in screenshot.

116
A SSIGN N UMBER R ANGES TO V ENDOR A CCOUNT G ROUPS

U SE
In this step you allocate the number ranges you created in the preceding step to the account groups for vendors.

P ROCEDURE
IMG Menu Financial Accounting (New)  Accounts Receivable and Accounts Payable 
Vendor Accounts  Master Data  Preparations for Creating Vendor Master
Data  Assign Number Ranges to Vendor Account Groups

Transaction S_ALR_87003201
Code
IMG Menu details in screenshot.

117
118
D EFINE P ERMISSIBLE P ARTNER R OLES PER A CCOUNT G ROUP

U SE
In this step, you can specify for each account group of the supplier which roles the supplier may assume.

P ROCEDURE
IMG Menu Materials Management  Purchasing  Partner Determination  Partner
Roles  Define Permissible Partner Roles per Account Group

Transaction S_ALR_87002037
Code
IMG Menu details in screenshot.

119
User Action Funct Name Group Name
Create AD Additionals SUPPL Supplier

Create AZ A.payment recipient SUPPL Supplier

Create OA Supplier SUPPL Supplier

Create VN Supplier SUPPL Supplier

Create PI Invoicing Party SUPPL Supplier

Create CA Contact Address SUPPL Supplier

Create GS Goods Supplier SUPPL Supplier

Create ER Employee respons. SUPPL Supplier

Create AD Additionals CPD One-time Supplier

Create AZ A.payment recipient CPD One-time Supplier

Create OA Supplier CPD One-time Supplier

Create VN Supplier CPD One-time Supplier

Create PI Invoicing Party CPD One-time Supplier

120
User Action Funct Name Group Name

Create CA Contact Address CPD One-time Supplier

Create GS Goods Supplier CPD One-time Supplier

Create ER Employee respons. CPD One-time Supplier

Create AD Additionals EMPL Employee as Supplier

Create AZ A.payment recipient EMPL Employee as Supplier

Create OA Supplier EMPL Employee as Supplier

Create VN Supplier EMPL Employee as Supplier

Create PI Invoicing Party EMPL Employee as Supplier

Create CA Contact Address EMPL Employee as Supplier

Create GS Goods Supplier EMPL Employee as Supplier

121
D EFINE P ARTNER S CHEMAS

U SE
In this step, you define partner determination schemas. Partner schemas allow you to group various partner roles

P ROCEDURE
Tcode SPRO
IMG Menu details in screenshot.

122
123
A SSIGN P ARTNER S CHEMAS TO A CCOUNT G ROUPS U SE
In this step, you assign partner schemas to Account groups. Partner schemas allow you to group various partner
roles

P ROCEDURE

IMG Menu Materials Management  Purchasing  Partner Determination  Partner


Settings in Vendor Master Record  Assign Partner Schemas to Account Groups

Transaction S_ALR_87001648
Code
IMG Menu details in screenshot.

124
125
6.2.2. V ENDOR I NTEGRATION PROCESS

D EFINE N UMBER A SSIGNMENT FOR D IRECTION BP TO V ENDOR

U SE
Here you assign account groups for the vendor master records to the business partner groupings to ensure that
the system updates the vendor at the same time as you process business partners as part of vendor integration.
When you make this assignment, you choose whether the vendor master record is created with an account with
internal or external number assignment or with identical numbers.

P ROCEDURE
IMG Menu Cross-Application Components  Master Data Synchronization 
Customer/Vendor Integration  Business Partner Settings  Settings for Vendor
Integration  Field Assignment for Vendor Integration  Assign Keys  Define
Number Assignment for Direction BP to Vendor

Transaction S_ALN_01002326
Code
IMG Menu details in screenshot.

126
127
S ET BP R OLE C ATEGORY FOR D IRECTION BP TO V ENDOR

U SE
Here you can define which BP role categories enable vendor integration in the direction from the business partner
to the vendor. You can determine how the system creates a corresponding vendor in Financial Accounting when
you process a business partner.

The BP role categories entered in this IMG activity are vendor-based, this means that the system has to consider
vendor integration when it processes business partners with a corresponding BP role. In the IMG activity you can
define whether the business partner role assigned to the BP role category is a mandatory or optional vendor
business partner role.

In the case of mandatory vendor business partner roles the system automatically creates corresponding vendors.
In the case of optional vendor business partner roles you can determine whether you want to create a
corresponding vendor during business partner processing.

P ROCEDURE
IMG Menu Cross-Application Components  Master Data Synchronization 
Customer/Vendor Integration  Business Partner Settings  Settings for Vendor
Integration  Set BP Role Category for Direction BP to Vendor

Transaction S_ALN_01002328
Code
IMG Menu details in screenshot.

128
129
--------End of Document--------

130