BG5 Application Conversion Guide

SAP S/4HANA May 2016 English

System Conversion for SAP S/4HANA (Application Conversion) (BG5) Building Block Configuration Guide

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

System Conversion for SAP S/4HANA (Application) (BG5):

Copyright © 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE

Public

Page 2 of 112

SAP Best Practices


Icons Icon

Meaning Caution Example Note Recommendation Syntax

Typographic Conventions Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE

Public

Page 3 of 112

SAP Best Practices


Contents 1 2 3 4

5

6

7

8

Purpose .............................................................................................................................. 9 Conversion Scenarios ........................................................................................................ 9 General Remarks ............................................................................................................... 9 Application Preparation Activities in Business Uptime: Logistics ..................................... 10 4.1 Master Data ............................................................................................................ 10 Business Partner ................................................................................................ 10 Material Master .................................................................................................. 16 Material Number Field Length Extension ...................................................... 16 Simplification of Parameter Effectivity ........................................................... 19 4.2 Sales and Distribution ............................................................................................ 19 Foreign Trade .................................................................................................... 19 Revenue Recognition......................................................................................... 20 4.3 Sales and Distribution - Data Model Changes in SD Pricing ................................. 20 4.4 Materials Management - Data Model Changes in Inventory Management ........... 20 4.5 Production Planning - Storage Location MRP ....................................................... 21 4.6 Environment, Health and Safety ............................................................................ 22 Conversion from Component Extension for SAP EH&S Management (Incident Management/ Risk Assessment) ..................................................................................... 22 Conversion from EH&S Management as Part of SAP ERP .............................. 22 EH&S - Product Safety and Stewardship for Process Industries ...................... 23 4.7 Ariba Network Integration ....................................................................................... 23 Application Preparation Activities in Business Uptime: Finance ...................................... 23 5.1 General Prerequisites ............................................................................................ 23 5.2 Prerequisite Check ................................................................................................. 24 Check Prerequisites for New Assets Accounting .............................................. 24 Prepare for New Depreciation Calculation Activation ........................................ 25 Check Currency Settings and CO Configuration ............................................... 26 5.3 Consistency Checks before Conversion and Migration ......................................... 26 5.4 Handling Customer-Defined Fields and Interfaces ................................................ 28 Application Preparation Activities in Business Downtime: Logistics ................................ 29 6.1 Master Data ............................................................................................................ 29 Business Partner ................................................................................................ 29 Material Master - Run Pre-Check for ALE Change Pointers and MFLE ........... 30 6.2 Production Planning - Storage Location MRP ....................................................... 33 Application Preparation Activities in Business Downtime: Finance ................................. 33 7.1 Post or Delete all Held Documents ........................................................................ 33 7.2 Period-End Closing and Prepare for Cut-Over ...................................................... 34 7.3 Reconcile and Compare Data – Before System Conversion ................................. 35 Application Follow-Up Activities in Business Downtime: Logistics ................................... 38 8.1 Master Data - Material Number Field Length Extension ........................................ 38 8.2 Sales & Distribution ................................................................................................ 39 Data Model Changes in SD Pricing ................................................................... 39 SD Rebate Processing replaced by Settlement Management .......................... 40 Optimization of SD Rebate Processing for Trade Promotion Management ...... 41 8.3 Output Management .............................................................................................. 42 8.4 Ariba Network Integration ....................................................................................... 43

© SAP SE

Public

Page 4 of 112

SAP Best Practices


8.5

Environment, Health and Safety ............................................................................ 44 Activities after Conversion to Incident Management ......................................... 44 Conversion from Component Extension 1.0 for SAP EHS Management ..... 44 Conversion from Component Extension 2.0 for SAP EHS Management ..... 46 Conversion from Component Extension 3.0 for SAP EHS Management ..... 48 Conversion from Component Extension 4.0 for SAP EHS Management ..... 49 Conversion from Component Extension 5.0 for SAP EHS Management ..... 50 Conversion from Component Extension 6.0 for SAP EHS Management ..... 50 Conversion from EHS Management as part of SAP ERP ............................. 51 Activities after Conversion to Health and Safety Management ......................... 52 Conversion from Component Extension 2.0 for SAP EHS Management ..... 52 Conversion from Component Extension 3.0 for SAP EHS Management ..... 53 Conversion from Component Extension 4.0 for SAP EHS Management ..... 55 Conversion from Component Extension 5.0 for SAP EHS Management ..... 57 8.5.2.4.1 Conversion from SP00 of Component Extension 5.0 for SAP EHS Management .......................................................................................................... 57 8.5.2.4.2 Conversion from FP01 of Component Extension 5.0 for SAP EHS Management .......................................................................................................... 59 Conversion from Component Extension 6.0 for SAP EHS Management ..... 61 Conversion from EHS Management as part of SAP ERP ............................. 61 Activation of WebDynpro Services ................................................................ 62 Activities after Conversion to Product Safety and Stewardship ........................ 63 Conversion of Product Compliance from Component Extension 3.0 for SAP EHS Management ........................................................................................................ 63 Conversion of Product Compliance from Component Extension 4.0 for SAP EHS Management ........................................................................................................ 66 Conversion of Product Compliance from Component Extension 5.0 for SAP EHS Management ........................................................................................................ 68 Conversion of Product Compliance from Component Extension 6.0 for SAP EHS Management ........................................................................................................ 70 Conversion of Product Safety and Stewardship for Process Industries ........ 70 9 Application Follow-Up Activities in Business Downtime: Finance .................................... 70 9.1 Deactivate Asset Accounting ................................................................................. 71 9.2 Preparation and Migration of Customizing ............................................................. 71 Check Customizing Settings Prior to Migration ................................................. 71 Define Message Type for Posting Before and During Migration ....................... 72 Preparation and Migration of Customizing for General Ledger ......................... 72 Activate SAP Reference IMG for Financial Accounting (New) ...................... 73 Check and Adopt Fiscal Year Variants .......................................................... 73 Migrate General Ledger Customizing ............................................................ 74 Define Settings for Ledgers and Currency Types ......................................... 74 Define Ledger for CO Version ....................................................................... 75 Define Document Types for Postings in Controlling ...................................... 75 Define Document Type Mapping Variants for CO Business Transactions ... 75 Check and Define Default Values for Postings in Controlling ....................... 76 Define Offsetting Account Determination Type ............................................. 76 Define Currency Settings for Migration ......................................................... 76 Define Source Ledger for Migration of Balances........................................... 77

© SAP SE

Public

Page 5 of 112

SAP Best Practices


Execute Consistency Check of General Ledger Settings ............................. 77 Activate Business Functions ......................................................................... 78 Preparations and Migration of Customizing for Asset Accounting - from Classic Asset Accounting .............................................................................................................. 78 Prepare New Asset Accounting ..................................................................... 78 Migrate Charts of Depreciation ...................................................................... 79 Display Migration Log .................................................................................... 79 Perform Additional Manual Activities ............................................................. 79 Check Prerequisites for Activating Asset Accounting (New) ......................... 80 Activate Asset Accounting (New) .................................................................. 80 Preparations and Migration of Customizing for Asset Accounting - from New Asset Accounting .............................................................................................................. 80 Info: Adjustments in New Asset Accounting .................................................. 80 Adjust Parameters in Chart of Depreciation .................................................. 81 Display Migration Log .................................................................................... 81 Preparations and Migration of Customizing for Controlling ............................... 82 Execute BW-Delta Extraction for Account-Based CO-PA ............................. 82 Adapt Settings for Profitability Segment Characteristics ............................... 82 Maintain Operating Concern.......................................................................... 82 Maintain Operating Concern for Banking Add-On ......................................... 83 Activate Account-Based Profitability Analysis ............................................... 83 Transport Operating Concern ........................................................................ 83 Preparations and Migration of Customizing for Material Ledger ....................... 84 Preparations and Migration of House Bank Accounts ....................................... 84 Define Number Ranges for Bank Account Technical IDs ............................. 85 Define Number Ranges for Change Requests .............................................. 85 Define Settings for Bank Account Master Data ............................................. 85 Preparatory Activities and Migration of Customizing for Credit Management ... 86 Migrate Credit Management Customizing ..................................................... 86 Define Credit Analyst Group as Business Partner Group ............................. 86 Define Credit Representative Group as Business Partner Relationship ....... 87 Define Customer Credit Group ...................................................................... 87 Assign Credit Management Group to Customer Credit Group ...................... 88 Assign Credit Management Processor to Credit Analyst Group ................... 88 Check and Define Credit Management Customizing .................................... 88 Define Settings for Credit Management Migration ........................................ 89 Check Customizing Settings ......................................................................... 89 9.3 Migration................................................................................................................. 90 Partitioning of Universal Journal Entry Line Items Table ................................... 90 Regenerate CDS Views and Field Mapping ...................................................... 90 Migration of Cost Elements ................................................................................ 91 Check Consistency of G/L Accounts and Cost Elements ............................. 91 Migration of Secondary Cost Elements to Chart of Accounts ....................... 91 Display Status of Migration of Cost Elements ............................................... 91 Migrate Default Account Assignments .......................................................... 92 Display Status of Migration of Default Account Assignments ....................... 92 Adopt Authorizations ..................................................................................... 92 Define Authorizations and Profiles ................................................................ 93

© SAP SE

Public

Page 6 of 112

SAP Best Practices

9.4

© SAP SE


Technical Check of Transaction Data ................................................................ 93 Analyze Transactional Data........................................................................... 93 Display Status of Analysis of Transaction Data............................................. 93 Reconcile Transactional Data ....................................................................... 94 Display Status of Technical Reconciliation of Transactional ......................... 94 Material Ledger Migration .................................................................................. 94 Migrate Material Ledger ................................................................................. 94 Display Status of Material Ledger Migration .................................................. 95 Check Migration of Material Ledger .............................................................. 95 Display Status of Material Ledger Migration Check ...................................... 96 Migration – Enrichment of Data ......................................................................... 96 Enrich Transactional Data ............................................................................. 96 Display Status of Enrichment of Transactional Data ..................................... 96 Check of Migrated Documents ...................................................................... 97 Display Status of Check of Migrated Documents .......................................... 97 Migration of Line Items into New Data Structure ............................................... 97 Migrate Accounting Documents to Universal Journal Entry Structure .......... 97 Display Status of Document Migration to Universal Journal Entry ................ 98 Check Migration of Accounting Documents to Universal Journal Entry ........ 98 Display Status of Check of Accounting Document Migration ........................ 99 Migrate General Ledger Allocations .............................................................. 99 Check Migrated General Ledger Allocations ................................................. 99 Migration of Balance ........................................................................................ 100 Migrate Balances ......................................................................................... 100 Display Status of Migration of Balances ...................................................... 100 Check Migration of Balances ....................................................................... 101 Display Status of Check of Migration of Balances ...................................... 101 Migration - Calculation of Depreciation and Total Values................................ 101 Calculate Initial Depreciation Values ........................................................... 101 Display Status of "Calculate Initial Depreciation Values" ............................ 102 Check Initial Depreciation Values and Total Values ................................... 102 Display Status of "Check Initial Depreciation Values and Total Values" ..... 103 Migration of House Banks Accounts ................................................................ 103 Credit Management Migration ......................................................................... 104 Migrate Credit Management Master Data ................................................... 104 Display Status of Migration of Credit Management Master Data ................ 105 Migrate Credit Management Exposure ........................................................ 105 Display Status of Credit Management Exposure Migration ......................... 106 Initialize Documented Credit Decision ......................................................... 106 Display Status of Initialization of Documented Credit Decisions ................. 106 Reconcile Documented Credit Decisions .................................................... 107 Complete Migration .......................................................................................... 107 Reconcile and Compare Data - After System Conversion .......................... 107 Set Migration to Completed ......................................................................... 107 Activities after Migration ....................................................................................... 108 Transfer Application Indexes ........................................................................... 108 Display Status of Transfer of Application Indexes ........................................... 108

Public

Page 7 of 112

SAP Best Practices

9.5

© SAP SE


Fill Due Dates in FI Documents ....................................................................... 109 Display Status of Filling in Due Dates into FI Documents ............................... 109 Fill the Offsetting Account in FI Documents..................................................... 109 Display Status of Filling the Offsetting Account in FI Documents ................... 110 Convert to SAP Cash Management ................................................................. 110 Migrate House Bank Accounts .................................................................... 110 Activate Business Functions FIN_FSCM_CLM ........................................... 111 Necessary Configurations - Migrate from the Classic SAP Liquidity Planner 111 SAP BPC for SAP S/4HANA Finance .................................................................. 112 Reactivate Classic Planning Transactions ...................................................... 112 Set-Up SAP BPC for SAP S/4HANA ............................................................... 112

Public

Page 8 of 112

SAP Best Practices


System Conversion for SAP S/4HANA (Application Conversion): Configuration Guide 1

Purpose

This Configuration Guide is part of the Master Configuration Guide (BG4_S4HANAXV1_BB_ConfigGuide_EN_XX.docx) with focus on tasks for the financial and logistics applications. The purpose of this document is to describe the necessary activities in SAP S/4HANA Finance and SAP S/4HANA Logistics applications as part of SAP S/4HANA conversion procedure.

2

Conversion Scenarios

The SAP Best Practices for SAP S/4HANA System Conversion covers the following conversion scenarios: Scenario 1: Conversion of SAP ERP on AnyDB to SAP S/4HANA Enterprise Management Scenario 2: Conversion of SAP ERP on SAP HANA to SAP S/4HANA Enterprise Management Scenario 3: Conversion of SAP ERP with SAP S/4HANA Finance on SAP HANA to SAP S/4HANA Enterprise Management

3

General Remarks

The Master Configuration Guide (BG4_S4HANAXV1_BB_ConfigGuide_EN_XX.docx) guides you through the technical conversion procedure and lists all relevant steps in the right sequence. The Master Configuration Guide cross references to this Application-Specific Configuration Guide (BG5_S4HANAXV1_BB_ConfigGuide_EN_XX.docx) describing the application relevant steps. How to convert financial and logistic applications to the SAP S/4HANA 1511 FPS01 is described in the Conversion Guide and Simplification List: 

Conversion Guide for SAP S/4HANA 1511 FPS01



Simplification List for SAP S/4HANA 1511 FPS01

Please check these documentations for updated information.

Financial Applications All the financial activities are valid for scenarios 1 and 2. However, for scenario 3, only several activities are valid. SAP S/4HANA Finance is based on new General Ledger Accounting (FI-GL (New)) and has functions such as parallel ledgers and the document splitting. If you have been using classic General Ledger Accounting, you can convert to SAP S/4HANA Finance by following this Configuration Guide. However, none of the functions of new General Ledger Accounting, such as parallel ledgers and document splitting can be implemented during this conversion. In case you want parallel ledgers and document splitting functions, you must first do a New General Ledger migration, and then SAP S/4HANA system conversion. If you have been

© SAP SE

Public

Page 9 of 112

SAP Best Practices


using the New General Ledger, you can convert to SAP S/4HANA Finance too by following this Configuration Guide. Currently it is not possible to subsequently add additional ledgers or to subsequently activate document splitting during conversion even if you have been using New General Ledger. SAP S/4HANA Finance is based on new Asset Accounting. Different activities are required depending on whether you have been using classic Asset Accounting or new Asset Accounting. We recommend you to execute the mentioned steps also in clients with no transactional data so that the migration programs can set the status of this client to Finished.

Logistic Applications All activities listed for the logistic applications are valid for all scenarios.

4

Application Preparation Activities in Business Uptime: Logistics

4.1 Master Data Business Partner Use In SAP S/4HANA the use of the Customer/Vendor Integration (CVI) is mandatory. This means that the formerly used transactions for maintaining customers and vendors are no longer used. For maintaining customer and vendor master data, the new Business Partner functionality will be used. To convert the actual customer and vendor master data into business partners, the described steps are mandatory:

Procedure This step of the procedure is to check the actual Number Assignment for Customers and Vendors. Customers 1. Access the Customizing activity using one of the following navigation options Transaction Code

SPRO

IMG Menu

Logistics → General → Business Partner → Customers → Control → Define and Assign Customer Number Ranges

2. In the Choose Activity dialog box, select Assign Number Ranges to Account Groups. 3. On the Assign Customer Acct Groups -> Number Range: Overview screen, check the number ranges which are currently assigned to your customer account groups. 4. Choose Back. 5. In the Choose Activity dialog box, select Define Number Ranges for Customer Master. 6. On the Range Maintenance: Customer screen, choose Display Intervals and check the actual intervals of the used number ranges. 7. Choose Back twice.

© SAP SE

Public

Page 10 of 112

SAP Best Practices


Vendors 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Logistics - General → Business Partner → Vendors → Control → Define Number Ranges for Vendor Master Records

2. On the Vendor Number Ranges screen, choose Number range. 3. On the Assign Vendor Account Groups -> Number Range: Overview screen, check the number ranges which are currently assigned to your vendor account groups. 4. Choose Back. 5. On the Vendor Number Ranges screen, choose Intervals. 6. On the Maintain Intervals: Vendor screen, check the actual intervals of the used number ranges. 7. Choose Back twice. Define Number Ranges for Business Partners 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges

2. If your actually used number ranges for customers and vendors are disjoint, the business partner number range should be defined as a mirror image of the customer/vendor number ranges. 3. If your actually used number ranges for customers and vendors are not disjoint, the business partner number range should be defined in such a way that most numbers from customer/vendor can be reused. 4. To allow the customer/vendor numeric numbers to be taken over to the business partner, you must select the checkbox External Assignment for the numeric intervals of the business partner number ranges.

For at least one number range which you are using for customers, the External Assignment checkbox may not be selected as this Customizing view requires one number range as the standard range for internal number assignment and one as the standard range for external number assignment. Otherwise the BP will not be created. This means that you have to define at least 2 number ranges, if you want to take over the actual customer numbers to business partner numbers: one where the External Assignment checkbox is not selected and another one where the checkbox is selected.

© SAP SE

Public

Page 11 of 112

SAP Best Practices


Define Groupings and Assign Number Ranges Each business partner has to be assigned to a grouping. It determines how an entry is made in the Business Partner Number field. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and assign Number Ranges

2. On the BP Groupings: Overview screen, you define the groupings you will use in the system. If you want to take over the numbers of your customers from your current system, you have to define at least 2 groupings: 

For the 1st grouping, the Internal Standard Grouping radio button has to be selected.



For the 2nd grouping the External Standard Grouping radio button must be selected. To this grouping, you have to assign the number range which you are using for your actual customer numbers (which is actually assigned to the customer account group).

Customer/Vendor Integration This step of the procedure is to define the BP Role for Direction Customer to BP. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Define BP Role for Direction Customer to BP

2. On the “Role Assignment for Customer According to BP”: Overview screen, you have to assign a business partner role to the account group for the customer master record in which the business partner will be created. The system creates a business partner with the relevant account group in the BP roles that are assigned to this account group. This step of the procedure is to define the Number Assignment for Direction Customer to BP. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignments for Customer Integration → Assign Keys → Define Number Assignments for Direction Customer to BP

2. On the Number Assignment for Direction Customer to BP: Overview screen, you have to assign the business partner groupings to the account groups of the customer master records to ensure that when you process customers as part of customer integration the system also updates the business partner at the same time. 3. Select Same No if you want to use the same number which is used for creating business partners as for the customer/vendor.

The same settings described above, which you have performed for customers, you have to perform for vendors as well. The relevant Customizing settings

© SAP SE

Public

Page 12 of 112

SAP Best Practices


therefore you find in the same Customizing tree, but under Settings for Vendor Integration. Contact Person (only relevant for customer integration) This step of the procedure is to activate the Assignment of Contact Persons. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person → Activate Assignment of Contact Persons

2. On the Assign Contact Person: Details screen select Cntct Person Active. This step of the procedure is to Assign Department Numbers for Contact Persons. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person → Assign Department Number for Contact Person

2. On the Assign Department Numbers for Contact Person: Overview screen you assign the department numbers for the business partner to the department numbers for the contact person in the current customer master record. This step of the procedure is to Assign Functions of Contact Person. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person→ Assign Function of Contact Person

2. On the Assign Functions of Contact Person: Overview screen you assign the functions for the business partner to the contact person functions in the current customer master record. This step of the procedure is to Assign Authority of Contact Person. 1. Access the Customizing activity using one of the following navigation options:

© SAP SE

Public

Page 13 of 112

SAP Best Practices


Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person→ Assign Function of Contact Person

2. On the Assign Authority of Contact Person: Overview screen you assign the partner's authority for the business partner to the partner's authority for the contact person in the current customer master record. This step of the procedure is to Assign VIP Indicator for Contact Person. 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person→ Assign VIP Indicator for Contact Person

2. On the Assign VIP Indicator for Contact Person: Overview screen you assign the VIP Indicator for the business partner to the VIP Indicator for the contact person in the current customer master record. Master Data Synchronization Synchronization Objects 1. Access the customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Synchronization Objects

The following entry must be available: Syn. Object

Sync. Mode

Extractor Class

Description

Platform

Block Size

BP

For Synchronous Comparison and Mass Data Loads

CVI_BP_EXTR ACTOR

Business Partner

Select checkbox

e.g. 50

2. Activate PPO Requests for Platform Objects in the Dialog You have to define for which platform objects a post-processing order should be written in the event of a synchronization error. Access the customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate PPO Requests for Platform Objects in the Dialog

The following entry must be available: Synchronization Object

© SAP SE

PPO-Active

Public

Page 14 of 112

SAP Best Practices


BP

Select checkbox

3. Activate Synchronization Options Access the customizing activity using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Cross –Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate Synchronization Options

The following entries must be available: Source Object

Target Object

Active Indicator for Synchronization Options

BP

Customer

Select checkbox

BP

Vendor

Select checkbox

Customer

BP

Select checkbox

Vendor

BP

Select checkbox

Check Settings for CVI 1. Access the transaction using the following navigation option: Transaction Code

CVI_FS_CHECK_CUST

The transaction verifies the CVI Customizing settings. 2. On the CVI Customizing - Check Report screen you can select the settings to be checked. To execute the report choose Check and Display Results. 3. Result Screen for selection General Settings: The screen is divided into 4 areas. Choose Display text in each area to get more information about the displayed results. From here you can also directly access the relevant Customizing settings. 

Synchronization Direction



Connection to PPO



Registered Function Modules

 Log. You have to make sure that no messages are displayed in this area. Result Screen for selection Customer Settings:

© SAP SE

Public

Page 15 of 112

SAP Best Practices


Three areas are displayed: 1. Direction: BP -> Customer Area: Display Settings for Business Partner Roles In this area the defined business partner roles are displayed. Area: Display Settings for Business Partner Groupings The defined Business Partner Groupings and their assignment to customer account groups are displayed. 2. Direction: Customer -> BP Area: Display Settings for Business Partner Roles The defined business partner roles and their assigned customer account groups are displayed. Area: Display Settings for Business Partner Groupings The defined Business Partner Groupings and their assigned customer account groups are displayed. 3. LOG In this area inconsistencies are listed which must be corrected. For more information choose Long Txt. Result Screen for selecting Vendor Settings The same Result screen as for customers is displayed for vendors. Verifying Results 1. Access the Customizing activity using one of the following navigation options: Transaction Code

SE38

SAP Menu

Tools → ABAP Workbench → Development → ABAP Editor

2. To verify the results, execute the PRECHECK_UPGRADATION_REPORT report. 3. On the Pre-Upgrade Checks screen, select the checkboxes for the checks you want to perform. 4. Choose Execute. 5. On the Display IMG screen in the area Precheck Status Results double click the red or yellow lights which are displayed. 6. On the Error Messages screen, all detected error messages concerning the selected pre-check activity are listed. You can access the relevant Customizing by double clicking the corresponding line. 7. Leave the report by choosing Back twice. There remain still some further activities concerning the Customer/Vendor Integration, which need to be performed before the conversion, but during business downtime. These activities are described in Application Preparation Activities in Business Downtime: Logistics - Master Data - Business Partner.

Material Master Material Number Field Length Extension Use This check is relevant for the extended material number handling. It is mandatory to run this check program in your systems before starting the conversion. Your data will be analyzed to make sure that all framework data is converted to the new structure. Customer defined tables and customer defined BOR types are also checked. The data in your system will not be

© SAP SE

Public

Page 16 of 112

SAP Best Practices


changed. You will get a structured and classified result list which indicates whether you need to take action.

Procedure This step of the procedure is to search for BOR types. The report will look for all BOR types that have an extended field in the key. For the found BOR types, the report will search for the usage in tables that can also have a BOR key. Known tables that are not relevant are excluded by a false positive list. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the MFLE_CLS4H_CHECKS_CC report. 3. On the Report MFLE_CLS4H_CHECKS_CC screen select Search for BOR types. 4. In the menu bar, choose Program and then Execute in background from the dropdown list. 5. In the Background Print Parameter dialog box, choose Continue. 6. In the Start Time dialog box, choose Immediate and then Check input. 7. Choose Save. 8. Depending on your personal settings (SAP GUI Options → Interaction Design → Notifications → Messages), the system will display the Background job was scheduled for program MFLE_CLS4H_CHECKS_CC message either in the status bar or in a separate message window. 9. To retrieve the results of this report, choose System from the menu bar and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this specific report shows the text MFLE_CLS4H_CHECKS_CC in the JobName column. If the Status field in this line contains the text Active, the job is still running. 10. To update the status of your job, choose Refresh from the application toolbar. 11. Once the Status field for your job in this list changes to Finished, you can evaluate any messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. 12. The Output controller: List of Spool Requests screen is displayed. Select the checkbox at the beginning of the line for your spool and choose Display contents. 13. The Graphical display of spool request screen in the system is displayed. It contains a list of messages produced by the report. 14. The result list of the report is structured as follows: There will be 1 line per table/field/BOR type, which provides the following information: Classification "A: customer (BOR)" / "A: customer (table)" / "A: customer (table/BOR)" => Customer extensions that require action: either the table, the field or the BOR type is a customer extension. In this case the conversion needs to be done by the customer. "B: SAP (BOR)” / "B: SAP (table)” / "B: SAP (table/BOR)” => No conversion planned: Either the table or the BOR type is not planned to be converted. In this case, please get in contact with SAP. "C: check okay" => these objects are either converted by SAP or no conversion is necessary.

© SAP SE

Public

Page 17 of 112

SAP Best Practices


This step of the procedure is to search for the Material Number. The program searches for significant material numbers and where they are used. "Significant" here refers to materials that have a high number of entries in material documents (table MSEG), and that have a recognizable "number" to reduce the amount of false positive findings. For example, purely numeric values will only be selected if there is no other (alphabetic) material available. This search will only be performed for a selected number of materials and will therefore provide an estimate. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the MFLE_CLS4H_CHECKS_CC Report. 3. On the Report MFLE_CLS4H_CHECKS_CC screen select Search for Material Number. 4. Additional selection fields will now be available on the screen. 5. Minimum Field Length Parameter Only fields of this length or longer will be checked.

It is recommended to enter at least 19 as minimum field length, because the report should mainly look for concatenated fields that have a material number. This way, the Standard Material Number fields would not be checked (because they do not need to be converted). 6. Amount of Materials Parameter The amount defines the number of materials that can be used. It is not possible to use all materials for this check, because the run time would be too long. A good starting point would be a range between 100 and 1000 materials. 7. Specific Materials Parameter Specific material numbers that are to be used for this check, can be entered here. These could be e.g. material numbers that are often used in the system or that are used in specific scenarios that are to be checked. 8. In the menu bar, choose Program and then Execute in background from the dropdown list. 9. In the Background Print Parameter dialog box, choose Continue. 10. In the Start Time dialog box, choose Immediate and then Check input. 11. Choose Save. 12. Depending on your personal settings (SAP GUI Options → Interaction Design → Notifications → Messages), the system will display the message Background job was scheduled for program MFLE_CLS4H_CHECKS_CC either in the status bar or in a separate message window. 13. To retrieve the results of this report, choose System from the menu bar and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this specific report shows the text MFLE_CLS4H_CHECKS_CC in the JobName column. If the Status field in this line contains the text Active, the job is still running. 14. To update the status of your job, choose Refresh from the application toolbar. 15. Once the Status field for your job in this list changes to Finished, you can evaluate any messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. 16. The Output controller: List of Spool Requests screen is displayed. Select here the checkbox at the beginning of the line for your spool and choose Display contents.

© SAP SE

Public

Page 18 of 112

SAP Best Practices


17. The Graphical display of spool request screen in the system is displayed. It contains a list of messages produced by the report.

Simplification of Parameter Effectivity Use In SAP S/4HANA 1511, the field KZEFF in table MARA is no more available. The current setting KZEFF is such that the field will be hidden only from the UI, but still continue to be available in the database. However, Assign effectivity parameter values/ override change numbers (KZEFF) impacts the parameter effectivity in BOM maintenance. Hence, the value of this field needs to be reset from ‘X’ to space to avoid adverse side effects. If the pre-check report R_S4_PRE_TRANSITION_CHECKS found MARA entries with field KZEFF set to X instead of space, the following message appeared in the results of this report (among others): Action required: Table MARA has field KZEFF marked as 'X' for some of the rows. This should be set to space. Please see SAP Note 2207188.

Procedure 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the ZLIST_MARA_KZEFF report to check if there are material master records with KZEFF field marked as ‘X’. 3. Execute the ZLIST_MARA_KZEFF2 report to set this field to blank.

4.2 Sales and Distribution Foreign Trade Use The foreign trade functionality of SAP SD is replaced in SAP S/4HANA 1511 release onwards by SAP Global Trade Services (GTS). It may be possible that you are currently using functionalities, which cannot be used as such with SAP S/4HANA.

Procedure You need to analyze all foreign trade processes currently in use. You can connect SAP Global Trade Services (SAP GTS) to SAP S/4HANA to run the respective foreign trade processes. These steps are only necessary, if you still have not switch to SAP GTS before starting the conversion to SAP S/4HANA. Download the following data from table MARC, which can no more be maintained after the conversion: MOWNR EU product list no. MOGRU CAP prod. Group PREFE Preference status PRENE Vendor decl. status PRENC Exemption Certificate PRENO Exemption Cert. No. PREND Iss.date of ex.cert.

© SAP SE

Public

Page 19 of 112

SAP Best Practices

ITARK


Military Goods

Revenue Recognition The SD-Revenue Recognition functionality is replaced by the new application SAP Revenue Accounting and Reporting. Before upgrading your system to SAP S/4HANA, a migration to “SAP Revenue Accounting and Reporting” needs to be done. Please refer to SAP Note 2225170 SAP S/4HANA SDRevenue Recognition.

4.3 Sales and Distribution - Data Model Changes in SD Pricing Use This step of the procedure is to evaluate the Check Results of Custom Code Check.

Procedure 1. If there is a reference to SAP Note 2220005 S/4 HANA: Data Model Changes in Pricing and Condition Technique, execute required custom code changes. The SAP Note lists a complete cookbook how to adapt custom code to resolve incompatibility with the new data model in Pricing and Condition Technique. 2. WEGXX and STUFE fields might be filled in the pricing table. If WEGXX and STUFE fields are filled and the data is still needed, SAP must add them to PRCD_ELEMENTS before migrating the data and update the migration code accordingly. According to SAP Note 2188695 WEGXX and STUFE fields are probably filled in the pricing table KONV, create a ticket to contact SAP (Note: use component SD-BF-PR). 3. Pricing table KONV has been enhanced with customer-specific fields. If you have added an append structure to database table KONV in the source release, you also need to add an append structure with the same fields (same field names, same data types) to the new database tables PRCD_ELEMENTS and PRCD_ELEM_DRAFT. You need to add the append structure to PRCD_ELEMENTS during the SPDD phase of the conversion process on the shadow instance.

4.4 Materials Management - Data Model Changes in Inventory Management This step is executed on the shadow instance of the conversion process.

Use The MM-IM data model in SAP Business Suite composed by the two document tables MKPF and MSEG has been changed in SAP S/4HANA to a new model consisting of a single denormalized table with name MATDOC. Also the actual stock quantity data will not be stored anymore in the material master aggregate tables but calculated on-the-fly from MATDOC. For more information, see the following SAP Notes: 

2206980 Material Inventory Management: change of data model in S/4HANA



2242679 Redirect inconsistency - Proxy Substitution

© SAP SE

Public

Page 20 of 112

SAP Best Practices




2238690 S/4HANA MM-IM migration by SUM

Procedure Manually add customer include CI_COBL structure NSDM_S_ITEM, so it will become part of the new table MATDOC (to be done during SPDD phase). 1. Logon to the shadow instance of the conversion process. 2. Access the transaction using the following navigation option: Transaction Code

SE11

3. On the ABAP Dictionary: Initial screen select Data Type and enter NSDM_S_ITEM. 4. Choose Change. 5. On the Dictionary: Change Structure screen navigate to the last field of the structure and set the cursor after this field. 6. In the menu bar, choose Edit, Include and then Insert. 7. On the Insert Include screen, enter CI_COBL in the Structure field. 8. Choose Continue. 9. On the Dictionary: Change Structure screen choose Activate from the application toolbar. 10. As NSDM_S_ITEM is one of the structures of which MATDOC is composed, now CI_COBL is part of table MATDOC and hence fields of this customer include will be set during conversion as well.

4.5 Production Planning - Storage Location MRP Use The SAP S/4HANA MRP only plans on plant and MRP area level. Planning on storage location level is not available in SAP S/4HANA 1511. Instead, planning on MRP area level has to be used. Materials with MRP-area-specific MRP type 'ND' (no MRP) can be used instead of materials with a storage location excluded from MRP. Materials with MRP-area specific MRP type 'VB' (reorder point planning) can be used instead of materials with separately planned storage locations. For more information, see the following SAP Notes 2216528 Pre-upgrade check for storage location migration report and 2227579 SAP S/4HANA Simplification Item: Logistics_PP-MRP Storage Location MRP.

Procedure If the pre-checks detect that storage location MRP is used, run the following report: 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the MRP_AREA_STORAGE_LOC_MIGRATION report.

© SAP SE

Public

Page 21 of 112

SAP Best Practices


3. The report first checks some prerequisites like MRP types, lot-sizing procedures, and MRP areas in customizing. If the required customizing entries are missing, you have to create them manually. 4. Follow the instructions provided by the report.

Result If all prerequisites of the report are fulfilled then report will proceed in the business downtime phase (see Application Preparation Activities in Business Downtime: Logistics - Production Planning - Storage Location MRP).

4.6 Environment, Health and Safety Conversion from Component Extension for SAP EH&S Management (Incident Management/ Risk Assessment) If you have installed the component extension for SAP EHS Management and the check result list of custom code check lists any ABAP development objects that are no longer supported in the EHS Management area, either adapt custom code to no longer use these objects or copy these objects into the customer namespace and adapt custom code to use those copied versions instead. With the component extension for SAP EHS Management, you can use the Incident Management (EHS-MGM-INC) and Risk Assessment (EHS-MGM-RAS) functions. Both functions are included in SAP S/4HANA but some of their features are no longer supported. The following features are affected: 1. Analytical reporting for EHS using SAP NetWeaver Business Intelligence (BI). 2. Data extraction into SAP NetWeaver business intelligence (BI) for risks, chemicals and incidents.

Conversion from EH&S Management as Part of SAP ERP If you have installed the component extension for SAP EHS Management and the check result list of custom code check lists any ABAP development objects that are no longer supported in the EHS Management area, either adapt custom code to no longer use these objects or copy these objects into the customer namespace and adapt custom code to use those copied versions instead. See the following SAP Notes for required activities to adapt custom coding: 1. for Industrial Hygiene and Safety (EHS-IHS): SAP Note 2217206 SAP S/4 HANA Simplification Item: Industrial Hygiene and Safety (EHS-IHS) and SAP Environmental Compliance (EC) interfaces 2. for Occupational Health (EHS-HEA): SAP Note 2217205 SAP S/4 HANA Simplification Item: Occupational Health (EHS-HEA) 3. for Waste Management (EHS-WA): SAP Note 2217202 SAP S/4 HANA Simplification Item: Waste Management (EHS-WA) Export data that are still required, but stored in tables which are not supported by SAP S/4HANA 1511.

© SAP SE

Public

Page 22 of 112

SAP Best Practices


EH&S - Product Safety and Stewardship for Process Industries You have installed the SAP Product and REACH Compliance add-on which supports Process Industry (PI) and Discrete Industry (DI) manufacturers. Discrete Industry The Product and REACH Compliance for the discrete industry has its origin in the TechniData Compliance for Products CFP solution. Product Compliance Management of SAP Environment, Health and Safety Management Extension EHSM is a successor for the discrete industry. If you use the discrete industry solution of SPRC or CFP, you are able to migrate to Product Compliance Management. Process Industry If you use the process industry solution of SPRC, you have to de-install SPRC since no successor exists.

4.7 Ariba Network Integration This step is only relevant if you use SAP ERP add-on Ariba Network Integration for SAP Business Suite.

Use The Supplier Workplace (SWP) as an E-commerce platform is no more available with SAP S/4HANA 1511. With Ariba Network a successor commerce platform is available. When preparing the conversion from the SAP ERP add-on Ariba Network Integration for SAP Business Suite to SAP S/4HANA, you have to perform the activities described below.

Procedure 1. Unschedule all reports that you have been using in the add-on Ariba Network Integration for SAP Business Suite. 2. Record all settings that exist in Customizing for SAP Business Suite Integration Component for Ariba. This allows you to compare the settings after the conversion and make adaptations, if necessary.

5

Application Preparation Activities in Business Uptime: Finance

5.1 General Prerequisites Before you start to conduct SAP Financials application related activities, make sure your system meet the following prerequisites. 3. The Customer/Vendor Integration for the Business Partner has been completed. Please refer to chapter Application Preparation Activities in Business Uptime: Logistics - Master Data - Business Partner. 4. You understand SAP Cash Management is the only compatible cash management product to SAP S/4HANA Finance. Classic SAP Cash and Liquidity Management are not officially supported in SAP S/4HANA Finance. You accept the functions describe

© SAP SE

Public

Page 23 of 112

SAP Best Practices


in SAP Note 2243327 Release Scope Information: SAP Cash Management (SAP S/4HANA, On-Premise Edition 1511. 5. You understand CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for SAP S/4HANA Finance. You accept the functions describe in SAP Note 2127742 Release Information Note: Controller Apps / SAP BPC for SAP S/4HANA Finance (Alias: SAP Integrated Business Planning for Finance) for SAP Simple Finance 1503 and 2203831 Release Information Note: Controller Apps / SAP BPC for SAP S/4HANA Finance (Alias: SAP Integrated Business Planning for Finance) - SAP Simple Finance, on-premise edition 1511. 6. You have finished the blueprint for any functions that you want to change or to implement during the system conversion. Including: a. New Asset Accounting b. SAP Credit Management (in case you have been using FI-AR-CR) c. SAP Cash Management (in case you have been using Classic Cash and Liquidity Management FIN-FSCM-CM and FIN-FSCM-LP) 7. The following functionalities are encouraged to be implement in a follow-up project after the SAP S/4HANA system conversion. a. Account-based CO-PA b. Extension ledger c. BPC for SAP S/4HANA

5.2 Prerequisite Check All the following checks should be done before you have decided for SAP S/4HANA system conversion, to understand the gap and prepare for blueprinting, business process changes, and test cases. However, since to fulfill the prerequisite is essential, the following check report must be executed again before the SAP S/4HANA technical conversion.

Check Prerequisites for New Assets Accounting Use In this activity you check whether the prerequisites for new Asset Accounting have been met. The program checks: 1. Compatibility with other components and functions; 2. Whether the periodic APC (Acquisition and Production costs) postings are complete for all company codes; 3. Consistency between the company codes and chart of depreciation: Company codes, to which different ledgers are assigned, must also have different charts of depreciation assigned. 4. Ledgers assigned to the company code and the ledgers that are to be posted to via the chart of depreciation must be identical. SAP Note 2147666 Assigned ledgers in FI-GL and FI-AA are inconsistent explains the cases and offers possible solutions. 5. The company codes that are assigned to the same chart of depreciation are not allowed to be different in number and type to the local currencies used in General Ledger Accounting. 6. Whether the fiscal year is already closed for all depreciation areas before the migration. The company codes or the depreciation areas defined in the assigned charts of depreciation are allowed only one open fiscal year before the conversion. 7. The clearing accounts for the integrated asset acquisition that you have defined in Customizing under Asset Accounting → Integration with the General Ledger are not allowed to be open-item-managed. 8. Those company codes that only allow subsequent reporting must be completely archived before the migration. 9. Start and end of the fiscal year for the representative ledger of the assigned ledger groups must be identical. SAP Note 2220152 Ledger approach and Asset Accounting (new): Non-calendar fiscal year variant for parallel valuation explains in detail the

© SAP SE

Public

Page 24 of 112

SAP Best Practices


problem and proposed solution. In case you are in this situation, activation of New AA and the solution based on creation and migration of a new ledger have to be executed before the S4H system conversion project.

Procedure 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RASFIN_MIGR_PRECHECK

2. Execute the program. 3. Select Target Release in Simple Finance depending upon the system which needs to be migrated to Simple Finance. Select the option Simple Finance add-on or on premise edition.

Result You should now see The prerequisites for New Asset Accounting are met message. All the packages should be in green and no messages in red (errors).

Prepare for New Depreciation Calculation Activation Use In this activity you check whether the new depreciation calculation is active, and if not, you should prepare for this.

Procedure 1. Access the business function activation by: Transaction Code

SFW5

2. Choose Continue. 3. Open the ENTERPRISE_EXTENSIONS folder. 4. Search for EA-FIN, check whether it is activated. If yes, stop here. If not, continue with the following steps. 5. Check SAP Note 965032 Differences between old and new depreciation calculation to understand the differences if you activated the new depreciation calculation. Consider these changes into blueprinting, configuration, business process changes, and testing. 6. Check SAP Note 1498047 Changeover from old to new depreciation calculation. Here the steps to activate new depreciation calculation are proposed; beginning of year is recommended as ideal activation date. However, conversion to SAP S/4HANA can be executed in any period. 7. If EA-FIN is not activated yet, Activate the business functions by: Transaction Code

SFW5

8. 9. 10. 11. 12. 13. 14. 15.

Choose Continue. Open the ENTERPRISE_EXTENSIONS folder. Search for EA-FIN. Check on select the checkbox to activate the business function. Choose Activate changes. Choose EA-FIN under Business functions to be switched on. Again, choose Activate changes. You should now see an information Job SFW_ACTIVATE_SF0X was started in the background. 16. Choose OK.

© SAP SE

Public

Page 25 of 112

SAP Best Practices


Result Business function EA-FIN is activated. You have understand the differences between old and new depreciation calculation and prepared for this.

Check Currency Settings and CO Configuration Use The FINS_MIG_PRECHECK_CUST_SETTNGS program checks the consistency of your ledger, company code and controlling area settings to determine if a conversion to SAP S/4HANA Finance is possible. The FINS_PRE_CHECK_SFIN_1503 program does the following: 

Collect general information of system usage



Check functional restrictions / differences compared to ERP 6.0 EhP7, i.e. classic Financials



Check the compatibility of installed components



Check write accesses to the affected tables exist in the customer namespace



Collect general information of system usage


SE38

Report

FINS_MIG_PRECHECK_CUST_SETTNGS

Report

FINS_PRE_CHECK_SFIN_1503 (If not a NEW INSTALL customer)

2. Execute the program FINS_MIG_PRECHECK_CUST_SETTNGS. Refer to SAP Note 2129306 Check Customizing Settings Prior to Upgrade to Simple Finance (sFIN 2.0) for additional information. 3. If it is not a new install customer, then you need to also execute the program FINS_PRE_CHECK_SFIN_1503 to check the compatibility of installed components. Refer to SAP Note 2176077 Check report for Simple Finance on-premise edition 1503 for additional information.

Result You should now see a Check passed message in the job log for both programs.

5.3 Consistency Checks before Conversion and Migration Use FI Consistency Check (RFINDEX_NACC) - You use this program to check the consistency of the document views (BSIS, BSAS, BSID, BSAD, BSIK, and BSAK) with the line items in table BSEG. Comparison Document/transaction figures (TFC_COMPARE_VZ) if you are using new General Ledger; or SAPF190 if you are using classic General Ledger - This report compares the transaction figures with the total of the single documents. RAABST01 to analyze reconciliation problems between the value update in Asset Accounting and the account update in the general ledger (with reference to a certain account). RAABST02 selects the asset totals records (ANLC), summarizes the values at G/L account

© SAP SE

Public

Page 26 of 112

SAP Best Practices


level and the business area level and writes these totaled values to the EWUFIAASUM table. This table is read and the values are reconciled with the general ledger accounts. Ledger Comparison (RGUCOMP4) - You can use this program to compare local ledgers, global ledgers, and ledgers with varying fiscal year variants and charts of accounts to each other. List of Stock Values (RM07MBST) - The report List of Stock Values: Balances is used to display the total quantity and value of the stock of one or more materials at plant and storage location level. MM/FI Balance Comparison (RM07MMFI) - This report compares the totals of the values from the material masters with the balances of the assigned stock accounts. The inconsistencies should be cleaned up or documented before the technical conversion.

Procedure 1. Access the transaction using: Transaction Code

SE38

Report

RFINDEX_NACC

2. Using the checkbox for starting RFINDEX_NACC, you can schedule the RFINDEX_NACC check report as a background job, either for a specific company code or for all company codes (the job is executed directly) The report is called with the following parameterization: - Documents vs Indexes - Indexes vs Documents - Documents - Transaction Figures - Indexes - Transaction Figures The system always considers all fiscal years in the system. 3. Check Documents - Transaction Figures for all fiscal years, in which archiving has not yet taken place. If you can’t perform consistency checks of documents against transaction figures using report RFINDEX_NACC due to runtime issues, perform the consistency checks after the installation instead. To do so, in customizing choose Migration from SAP ERP to S/4HANA Financials → Migration → Technical Check of Transaction Data → Analyze Transactional Data. Check the result in the Display Status of Analysis of Transaction Data Customizing activity. Then carry out the Reconcile Transactional Data activity and check the result in the Display Status of Technical Reconciliation of Transactional Data activity. All these activities are available in your test system after you have installed SAP S/4HANA. 4. Reconciliation for the General Ledger and the Sub-ledgers: If you are using classical General Ledger, the above process in 1.a, 1.b and 1.c will provide you the reconciliation between General Ledger and sub-ledgers, so you can move to next step. If you are using new General Ledger, use: Transaction Code

SE38

Report

TFC_COMPARE_VZ Alternatively this can be executed with transaction code FAGLF03

5. Reconciliation for the General Ledger and the Assets Accounting for leading valuation and parallel valuation. If you are using classical Assets Accounting, use:

© SAP SE

Public

Page 27 of 112

SAP Best Practices


Transaction Code

SE38

Report

RAABST01 Consistency Check for FI-AA (New) and FI-GL (New)

If you are using classical and new Assets Accounting, use: Transaction Code

SE38

Report

RAABST02 Reconciliation Program FI-AA <-> General Ledger: List with Difference Accounts

6. Compare ledgers, if you use new General Ledger Accounting Transaction Code

SE38

Report

RGUCOMP4 Alternatively, this can be performed with transaction code GCAC

7. Reconcile MM-IM with General Ledger, if you use classical or new General Ledger Accounting. Transaction Code

SE38

Report

RM07MBST

Report

RM07MMFI

Execute RM07MBST report to list stock values as of the current period. This list output of the report is required to be stored and compared with the output after migration. Schedule report RM07MMFI with the function MM-FI Perform Balance Comparison for the current period. Select Save Results of This Run. Check if there are any inconsistencies and correct the inconsistencies.

Result You should have cleaned up all the inconsistencies before SAP S/4HANA system conversion. It is almost impossible to be fix the inconsistencies once they are carried over to SAP S/4HANA. You may consider archive the data or at least document the inconsistencies in case they are not cleared up.

5.4 Handling Customer-Defined Fields and Interfaces Use Customer-defined field must be generated to the compatibility views in an appropriate way.

Procedure 1. If you are using new General Ledger Accounting and using customer-defined fields, these fields are generated to the appropriate compatibility views. 2. For customer fields in BSEG and the index tables, note the following for the creation of the views with the same names 

If a customer field exists in both BSEG and in the indexes, it is automatically generated into the view with the same name.



If the customer field only exists in the index, it is not transferred into a view with the same name. In this case the field must first be included in the BSEG and filled using a customer program. 3. If you transferred data from your Z tables to new General Ledger Accounting during the migration to the Financial Accounting add-on 1.0, you have to delete the data of these Z tables before the conversion. If you do not delete the data, the data of the Z

© SAP SE

Public

Page 28 of 112

SAP Best Practices


tables is migrated again and transferred to the new table structure. The values would then be duplicated. 4. If you have used interfaces to connect your system to external systems that make postings to General Ledger Accounting (in real time or subsequently), check whether adjustments need to be made to the interfaces. For more information, see SAP Help Portal → Product Assistance → Cross Components → Business Functions → Business Functions → Enterprise Business Functions → Accounting → Finance → General Ledger Accounting (FI-GL) (New → FI-GL (New) Transfer of Totals and Single Documents in Distributed Systems 5. ALE scenarios are only partially supported. A SAP S/4HANA system cannot serve as an ALE receiver for CO line items. The reason is that FI and CO line items use the same persistence table. Therefore, the CO line items cannot be posted alone without the FI line items they belong to. SAP does not provide a check to determine if this scenario is used in the system. You have to check this manually. ALE scenarios for the distribution of CO Master Data, such as cost centers, continue to be supported.

Result Your customer-defined fields and interfaces have been adapted to SAP S/4HANA.

6

Application Preparation Activities in Business Downtime: Logistics

6.1 Master Data Business Partner Use Here the above mentioned further activities concerning the Customer/Vendor Integration (see chapter Application Preparation Activities in Business Uptime: Logistics - Master Data Business Partner), which have to be performed during business downtime, are described.

Procedure Data Synchronization using the Synchronization Cockpit Once all Customizing settings concerning the Business Partner Customizing are done, you can use the synchronization cockpit to carry out necessary steps for master data synchronization. Access the transaction using one of the following navigation options: Transaction Code

MDS_LOAD_COCKPIT

IMG Menu

Cross –Application Components → Master Data Synchronization → Synchronization of Mass Data → Execute Synchronization Cockpit

It is divided into 3 work areas: 1. Synchronization Process This work area in the top left part of the screen contains a list of the synchronization processes. The list displays either the active synchronization processes or all the synchronization processes. You can change between the two views at any time choosing Show/Hide Inactive. 2. Customizing Synchronization This work area in the bottom left part of the screen contains an overview of the 4 separate reports that you can use for the customizing synchronization. 3. Synchronization

© SAP SE

Public

Page 29 of 112

SAP Best Practices


This work area in the right part of the screen contains the Processing and Monitor tab pages, which are used to prepare or to monitor synchronization runs. To transfer customer master data into business partners, perform the following steps: a. In the Synchronization Process area, select the entry with Source Object Customer and Target Object Business Partner by double clicking the corresponding line. b. In the Synchronization area choose the tab page Processing. Enter your selection criteria in the area Selection Criteria for Source Object. c. Choose Start Synchronization. d. You can check the result of the synchronization run by choosing the tab page Monitor. e. Select a line and choose Appl. Log. To transfer vendor master data into business partners, perform the same steps by selecting the line with Source Object Vendor and Target Object Business Partner by double clicking the corresponding line in the area Synchronization Process. Postprocessing Master Data Synchronization errors After having executed the above steps, you should check if there have been postprocessing orders created, which should be processed. Access the transaction using one of the following navigation options: Transaction Code

MDS_PPO2

1. On the Postprocessing Desktop – Edit Order: Initial screen make your selections to restrict the results. 2. Choose Execute. 3. On the Postprocessing Desktop – Edit Order: Overview screen you get the error messages which occurred during the master data synchronization run. 4. Select a main object in the Main Object / Key column and choose Expand subtree from the application toolbar to get detailed information about all the problems which occurred during synchronization run for this main object. 5. Analyze the errors which occurred and adapt the Customizing or your customer/vendor master data accordingly. 6. Choose Back twice.

After the successful initial load, the numeric intervals of the business partner must be changed back to internal. Additionally the customer/vendor numeric number ranges must be set to external to allow identical numbers for customer/vendor and business partner (see step 3 Application Preparation Activities in Business Uptime: Logistics - Master Data - Business Partner). You should change the number range in such a way that new identical numbers are created for business partner and customers/vendors by defining new ranges for business partner and customer/vendors.

Material Master - Run Pre-Check for ALE Change Pointers and MFLE Use Before all XPRAS are started to change the material number field length extension (MFLE) from 18 to 40 digits, some checks have to be performed. One of these checks establishes whether there are any open ALE Change Pointers. This process must be completed manually before the system is migrated.

© SAP SE

Public

Page 30 of 112

SAP Best Practices


Some ALE message types handle a material number. In most cases, the material number is in a concatenated field. Transforming these millions of entries would extend the downtime dramatically. How to process the open ALE change pointers depends on the message type. Using RBDCPCLR report, you can delete all obsolete change pointers. Using RBDMIDOC report, you can process valid ALE change pointers.

Procedure This step of the procedure is to delete obsolete ALE Change Pointers. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the RBDCPCLR report to delete change pointer entries from database tables. 3. On the Delete Change Pointers screen select the Test Run checkbox, if you only want to perform a simulation. In this simulation mode, no changes on the database are done. 4. Select the Scan Tables checkbox only if you have changed the number range for the change pointers manually or if you have reset the state of the number range. This also applies if the number range has been exhausted and starts again from the beginning, or if the data in the change pointer table is inconsistent. In these cases, the change pointer tables need to be scanned so that all change pointers are included in the reorganization.

Remember that no new change pointers can be generated while the change pointer tables are being scanned. 5. In the Obsolete Change Pointers area, choose the Obsolete Change Pointers checkbox to reorganize the change pointers no matter whether they have been processed or not. Restrict your selection by choosing the relevant message types which you want to process. Furthermore you can restrict the selection of the relevant change pointers by entering Date and Time of creation. 6. In the Processed Change Pointers area, choose the Processed Change Pointers checkbox to reorganize the processed change pointers. Restrict your selection by choosing the relevant message types which you want to process. Furthermore you can restrict the selection of the relevant change pointers by entering a Created on and Created at range of the creation. 7. The report outputs the number of deleted entries. In test mode, the selected change pointer entries are displayed. 8. In the menu bar, choose Program and then Execute in background from the dropdown list. In the Background Print Parameter dialog box, choose Continue. 9. In the Start Time dialog box, choose Immediate and then Check input. 10. Choose Save. 11. Depending on your personal settings (SAP GUI Options → Interaction Design → Notifications → Messages), the system will display the message Background job was scheduled for program RBDCPCLR either in the status bar or in a separate message window. 12. To retrieve the results of this report, choose System from the menu bar and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this

© SAP SE

Public

Page 31 of 112

SAP Best Practices


specific report shows the text RBDCPCLR in the JobName column. If the Status field in this line contains the text Active, the job is still running. 13. To update the status of your job, choose Refresh from the application toolbar. 14. Once the Status field for your job in this list changes to Finished, you can evaluate any messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. 15. The Output controller: List of Spool Requests screen is displayed. Select here the checkbox at the beginning of the line for your spool and choose Display contents. 16. The Graphical display of spool request screen in system is displayed. It contains a list of messages produced by the report. 17. Choose Back several times to go back to the SAP Easy Access Menu. This step of the procedure is to valid ALE Change Pointers. This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the RBDMIDOC Report, to process valid change pointers. 3. It needs to be run per single message type. To determine the relevant message types, access the transaction: Transaction Code

TAANA

4. On the Table Analysis: Administration screen select the row BDCP or BDCP2 depending on your used SAP Release in the area Table/Analysis/Field list. 5. In the toolbar choose Start table analysis. 6. On the Start Table Analysis screen, enter BDCPV or BDCP2 depending on your used SAP Release in the Table Name field. 7. Select an Analysis Variant by choosing the button right of the input field. 8. On the upcoming Analysis Variants: Selection screen select the Default Variant in the Table/analysis variant area. 9. Choose Continue. 10. On the Start Table Analysis screen in the Processing Options area select In the Background. 11. Choose Continue. 12. On the Start Time screen choose the relevant button to schedule the job. 13. Choose Save. 14. To retrieve the results of this report, choose System from the menu bar and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this specific report shows the text TAB_ANA_FOR_BDCP2_DEFAULT in the JobName column. If the Status field in this line contains the text Active, the job is still running. 15. To update the status of your job, choose Refresh from the application toolbar. 16. Once the Status field for your job in this list changes to Finished, you can evaluate any messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. 17. The Output controller: List of Spool Requests screen is displayed. Select here the checkbox at the beginning of the line for your spool and choose Display contents. 18. The Graphical display of spool request screen in system is displayed. It contains the output produced by the report. The output are

© SAP SE

Public

Page 32 of 112

SAP Best Practices

19. 20.

21. 22. 23.


information about the number of master data IDocs and communication IDocs created. Choose Back several times to go back to the SAP Easy Access Menu. On the Creating IDoc Type from Change Pointers screen enter a message type from the previous report result list with Processing Indicator equal Blanks. Only these are potential IDocs to be processed. Choose Execute to start the report. The report outputs information about the number of master IDocs and communication IDocs created. Choose Back several times.

6.2 Production Planning - Storage Location MRP Use This step refers to chapter Application Preparation Activities in Business Uptime: Logistics Production Planning - Storage Location MRP after the missing Customizing entries are created.

Procedure 1. Proceed to execute the MRP_AREA_STORAGE_LOC_MIGRATION report after the instructions and issues are fixed. 2. The report generates material master records for planning on MRP area level using the storage location material records.

Result Planning is now done on MRP area level.

7

Application Preparation Activities in Business Downtime: Finance

If you are using classic Asset Accounting, new Asset Accounting or the Simple Finance addon 1.0, make sure that you have performed the following activities. If you are using SAP S/4HANA Finance beside of a few exceptions (RMMMPERI, RAPERB2000, FAGLGVTR, RAJABS00, SAPL0F00, SAPMKCSP), most of the steps explained under chapter Post or Delete all Held Documents, Period-End Closing and Prepare for Cut-Over, Reconcile and Compare Data – Before System Conversion are not necessary for conversion scenario 3. For all the check jobs, if you see errors or warnings, check and change the corresponding configurations, or correct the transaction data. Run the check job again, until check passed.

7.1 Post or Delete all Held Documents These activities are relevant for all conversion scenarios 1 and 2 covered by this Best Practices package. Held documents must be cleaned up before SAP S/4HANA system conversion.

Procedure Access the transaction using one of the following navigation options:

© SAP SE

Public

Page 33 of 112

SAP Best Practices


1. Check held documents in: Transaction Code

FBV3

2. a. If you want to post held document, choose: Transaction Code

FB50 → Edit → Select Held Document

b. If you want to delete held document individually, choose: Transaction Code

FB50 → Edit → Delete Held Document

Result You should not see any held documents in transaction code FBV3 after the posting or deletion.

Make sure that you have all documents posted or deleted all not-needed held documents.

7.2 Period-End Closing and Prepare for Cut-Over If is it not mentioned extra, these activities are relevant for all 3 conversion scenarios covered by this Best Practices package. You should perform your normal period-end closing activities and document the results. The following activates must be considered. Some activates are relevant to cut-over, they are mentioned in the step description.

Procedure 1. Close the current and previous periods in Material Management Transaction Code

SE38

Report

RMMMPERI

Or Transaction Code

MMPV

2. For Assets Accounting Close periodic asset posting Transaction Code

SE38

Report

RAPERB2000

Execute periodic depreciation posting run.

These activities are relevant for all conversion scenarios 1 and 2 covered by this Best Practices package. Transaction Code

SE38

Report

RAPOST2000

Close previous fiscal year and keep the current fiscal year open. Transaction Code

SE38

Report

RAJABS00

© SAP SE

Public

Page 34 of 112

SAP Best Practices


3. Carry forward balances Transaction Code

FAGLGVTR (if new General Ledger Accounting is used)

These activities are relevant for all conversion scenarios 1 and 2 covered by this Best Practices package. Transaction Code

F.16 (if classical General Ledger Accounting is used)

Transaction Code

AJRW (Assets Accounting)

Transaction Code

F.07 (Accounts Payables and Accounts Receivables)

4. Lock Accounting and Controlling periods. Transaction Code

OB52 (Accounting)

Transaction Code

OKP1 (Controlling)

5. Relevant to cut-over. If you are already using Account-based profitability analysis, perform a delta upload to SAP BW for all account-based CO-PA data sources for which you use the delta method. Relevant to cut-over. Transaction Code

RSA7

6. Relevant to cut-over. If you are using classical General Ledger Accounting and using Foreign Currency Valuation with function Valuation for Balance Sheet Preparation, then you need to reset the valuation difference in the open items to zero. In other words, field BSEG_BDIFF in open items has to be empty over all years. If not, create a new valuation method in the Customizing path of the classic GL and reset valuation before the SAP S/4HANA software is installed. The new foreign currency valuation run after migration has to be in the same reporting period. Transaction Code

SE38

Report

SAPF100

7. Relevant to cut-over. Execute all scheduled job and do not schedule any new job. Transaction Code

SM37

8. Relevant to cut-over. Lock users Transaction Code

SU10

7.3 Reconcile and Compare Data – Before System Conversion You should document important reports before technical conversion. Later on, you can compare the reports result after application is converted into SAP S/4HANA Finance.

Procedure SAP recommends you to run the following reports. You should consider the reports that is important to you. Document cost centers: Actual/Plan/Variance 1. Access the transaction using the following navigation option: Transaction Code

S_ALR_87013611

2. Execute the transaction with report group 1SIP 3. Save the results.

© SAP SE

Public

Page 35 of 112

SAP Best Practices


Document Order: Actual/Plan/Variance 1. Access the transaction using the following navigation option: Transaction Code

S_ALR_87012993

2. Execute the transaction for all the years for which the data has not been archived. 3. Save the results. Document Financial Statements 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFBILA00

2. Execute the transaction for all the years for which the data has not been archived. 3. Save the results Document sales order selection 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RKKBSELL

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document G/L account balance list 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFSSLD00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document General ledger line items list 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFSOPO00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document Compact document journal 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFBELJ00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document Asset history sheet 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RAGITT_ALV01

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document Depreciation run for planned depreciation

© SAP SE

Public

Page 36 of 112

SAP Best Practices


1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RAHAFA_ALV01

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document vendor business 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFKUML00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document vendor open item list 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFKEPL00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document customer sales 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFDUML00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document customer open item list 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFDEPL00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results. Document customer recurring entry original documents 1. Access the transaction using the following navigation option: Transaction Code

SE38

Report

RFDAUB00

2. Execute the report for all the years for which the data has not been archived. 3. Save the results.

Result You have documented the most important financial statements, to be compared with the same financial statements after the system conversion.

© SAP SE

Public

Page 37 of 112

SAP Best Practices

8


Application Follow-Up Activities in Business Downtime: Logistics

8.1 Master Data - Material Number Field Length Extension Use To ensure that any selection variants for programs created before the conversion are still available after the conversion, a functionality called ASU variant restorer is executed during the technical upgrade. It is recommended to use this functionality especially to check if selection variants affected by the Material Number Field Length Extension are successfully restored or if there are additional steps required to make them fully available again after the conversion. The ASU variant restorer works as follows: The program RASUVAR1 (or RASUVAR_START) imports the parameters of the selection screen for all programs that have at least one variant and stores this information in the table TASUVAR1. In RASUVAR_START, the system variants (&SAP...) can also be evaluated. This is not required in the case of an upgrade because these variants are always delivered new for it and therefore do not have to be converted. The program RASUVAR2 (or RASUVAR_FINISH) reads all reports from the table TASUVAR1 and then tries to import all existing variants for these reports. If an error occurs for a variant, the parameters are imported individually for this variant - if a parameter cannot be imported, the information for this parameter is used to generate ABAP from the table TASUVAR1 and this is used to read the data. The imported value is then transferred to the current structure. When all parameters are processed, the data of the variant in the current structure is exported to the database again. This ensures that this variant can be imported without errors in the future. The logs of the programs RASUVAR1 and RASUVAR2 are stored as a file with the upgrade logs on the application server. You can usually view the log files in the relevant directory using transaction AL11. The name is the name of the program (that is, RASUVAR1 or RASUVAR2) followed by a dot and the system name. For the programs RASUVAR_START and RASUVAR_FINISH, the logs can additionally be printed as a list in the spool. To check the results after the conversion of the variants using the programs RASUVAR1 and RASUVAR2 (or RASUVAR_START and RASUVAR_FINISH), the program RASUVAR_DETECT (see SAP Note 1384051 ASU variant restorer: Consistency check after upgrade) is available in addition to the log files. SAP Note 1384051 also contains a detailed documentation for the program RASUVAR_DETECT. With this, it should be relatively easy to determine which variants still require manual post-implementation steps after the conversion. For more information, see SAP Notes 1696821 Technical documentation: ASU variant restorer functionality, 1160685 Using the ASU variant restorer outside of the technical upgrade and 1384051 ASU variant restorer: Consistency check after upgrade.


SE38

SAP Menu


2. Execute the RASUVAR_DETECT report. 3. Optional: On the ASU Variants: detect variants that might be changed during the upgrade screen, you could limit the scope of the check report to specific reports. If you wish to do this, enter the respective report name(s) in the Reportname (optional)

© SAP SE

Public

Page 38 of 112

SAP Best Practices

4. 5. 6. 7. 8. 9. 10. 11.

12.

13. 14.

15. 16.


field. We recommend to leave these fields empty in order to have all relevant reports checked. On the same screen, deselect the Variants used in jobs only radio button. Select the Check all variants radio button. Select the Display errors/warnings only checkbox. In the menu bar, choose Program and then Execute in background from the dropdown list. In the Background Print Parameter dialog box, choose Continue. In the Start Time dialog box, choose Immediate and then Check input. Choose Save. Depending on your personal settings (SAP GUI Options → Interaction Design → Notifications → Messages), the system will display the message Background job was scheduled for program RASUVAR_DETECT either in the status bar or in a separate message window. To retrieve the results of this report, choose System from the menu bar, and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this specific report shows the text RASUVAR_DETECT in the JobName column. If the Status field in this line contains the text Active, the job is still running. To update the status of your job, choose Refresh from the application toolbar. Once the Status field for your job in this list changes to Finished, you can evaluate any error or warning messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. The Output controller: List of Spool Requests screen is displayed. Select the checkbox at the beginning of the line for your spool and choose Display contents. The Graphical display of spool request screen in system is displayed. It contains a list of messages produced by the report.

Result You have executed the RASUVAR_DETECT report and evaluated its results to identify any errors or warnings.

8.2 Sales & Distribution Data Model Changes in SD Pricing Use Business documents within the SAP Business Suite such as the sales order or the purchase order used to store the pricing result in the KONV database table. In SAP S/4HANA, table KONV has been replaced in its data persistency role by the new table PRCD_ELEMENTS. However, KONV is and can still be used for data declaration purposes. It still defines the structure of the pricing result within the application coding. The content of KONV is transferred to PRCD_ELEMENTS when moving to SAP S/4HANA. SAP provides migration reports centrally to migrate data from the old database table KONV to the new database table PRCD_ELEMENTS. However, the WAERK document currency field of table PRCD_ELEMENTS needs to be filled with the currency of the related document header. To reduce downtime, it was decided to move this step to the post-processing. Within migration, the currency is filled with the technical currency '2' allowing the system to correctly convert PRCD_ELEMENT to KONV format and vice versa. However, to fill the currency consistently in accordance with the related document, SAP recommends that you run the post-processing PRC_MIG_POST_PROCESSING report as soon as possible.

© SAP SE

Public

Page 39 of 112

SAP Best Practices



SE38

SAP Menu


2. Execute the PRC_MIG_POST_PROCESSING report. 3. Optional: On the Post-processing report for pricing migration KONV -> PRCD_ELEMENTS screen, select the Test mode checkbox. Make sure you repeat the following step with this checkbox deselected. 4. In the menu bar, choose Program and then Execute in background from the dropdown list. 5. In the Background Print Parameter dialog box, choose Continue. 6. In the Start Time dialog box, choose Immediate and then Check input. 7. Choose Save. 8. Depending on your personal settings (SAP GUI Options → Interaction Design → Notifications → Messages), the system will display the message Background job was scheduled for program PRC_MIG_POST_PROCESSING either in the status bar or in a separate message window. 9. To retrieve the results of this report, choose System from the menu bar, and then Own jobs from the dropdown list. In the list of your jobs, the line containing the job for this specific report shows the text PRC_MIG_POST_PROCESSING in the JobName column. If the Status field in this line contains the text Active, the job is still running. 10. To update the status of your job, choose Refresh from the application toolbar. 11. Once the Status field for your job in this list changes to Finished, you can evaluate any error or warning messages issued by the report if you select the checkbox at the beginning of the line with your job and then choose Display spool list from the application toolbar. 12. The Output controller: List of Spool Requests screen is displayed. Select here the checkbox at the beginning of the line for your spool and choose Display contents. 13. The Graphical display of spool request screen in system is displayed. It contains a list of messages produced by the report.

Result You have executed the PRC_MIG_POST_PROCESSING report and evaluated its results to identify any errors or warnings.

SD Rebate Processing replaced by Settlement Management Use In general, SD Rebate Processing is not available in SAP S/4HANA 1511. The successor of SD Rebate Processing is Settlement Management. However, there is one exception: SAP CRM Trade Promotion Management (TPM) customers can still use SD Rebate Processing for their business processes, but have to adapt to an SAP S/4HANA-optimized solution. For more information, see Optimization of SD Rebate Processing for Trade Promotion Management. Nevertheless, you need to make sure that custom code referring to this topic is adapted where necessary.

Prerequisites To ensure that your custom code works with SAP S/4HANA, SAP has provided the simplification list concept to check your custom code against a set of SAP S/4HANA simplifications (for more information, see Configuration guide - Getting Started (Quick Guide) (BP_BSCON_S4HANAXV1_Quick_Guide_EN_XX.docx). This has to be done before

© SAP SE

Public

Page 40 of 112

SAP Best Practices


the technical preparation for the upgrade-like conversion to SAP S/4HANA is started. Results of the custom code check need to be properly evaluated and processed (that is, suggested changes are to be done wherever possible before the actual conversion; other changes might have to be completed after the technical part of the conversion). After the conversion, you can access the results of the custom code check on the system where you executed the check, following the steps listed below.


SE38

SAP Menu


2. Execute the SYCM_DISPLAY_SIMPLIFICATIONS report. 3. On the Display simplifications that affect custom code objects screen, insert the ID of your recently upgraded system in the System ID field. Optional: Define additional selection criteria. 4. Choose Execute. 5. On the Objects affected by simplifications screen, select the header of the Note column and choose Set filter… 6. In the Determine Values for Filter Criteria dialog box, insert the value 2226380 in the Note field and choose Execute. 7. If the (now filtered) list contains a reference to SAP Note 2226380 S/4HANA: Deprecation of SD Rebate Processing, adapt custom code according to the guidance given in the SAP Note.

Result You have evaluated the results of the custom code check for any reference to change requirements with regards to the simplification in the field of SD Rebate Processing / Settlement Management.

Optimization of SD Rebate Processing for Trade Promotion Management Use Customers who will integrate their existing CRM TPM scenario with SAP S/4HANA, still have to use SD Rebate Processing, even though a successor is already being provided by Settlement Management. For more information, see SD Rebate Processing replaced by Settlement Management. For those customers, the existing SD Rebate functionality is optimized with regard to the database footprint. For this purpose, from a technical standpoint, the rebate index table VBOX is no longer used. Please note that TPM customers are also not able to create new rebate agreements in SAP S/4HANA or extend existing ones. However, this is not necessary for the TPM process, since rebate agreements are created by CRM TPM for this business process. Nevertheless, you need to make sure that custom code referring to this topic is adapted where necessary. In addition to this, a rebuild of the content of table S469 is required after the conversion if you use extended SD rebate processing, and you have to maintain new Customizing settings. For more information, see SAP Note 2200691 SD rebate: Simplifications in SAP S/4HANA.

Prerequisites To ensure that your custom code works with SAP S/4HANA, SAP has provided the simplification list concept to check your custom code against a set of SAP S/4HANA simplifications (for more information, see Configuration Guide - Getting Started (Quick

© SAP SE

Public

Page 41 of 112

SAP Best Practices


Guide) (BP_BSCON_S4HANAXV1_Quick_Guide_EN_XX.docx). This has to be done before the technical preparation for the upgrade-like conversion to SAP S/4HANA is started. Results of the custom code check need to be properly evaluated and processed (that is, suggested changes are to be done wherever possible before the actual conversion; other changes might have to be completed after the technical part of the conversion). After the conversion, you can access the results of the custom code check on the system where you executed the check, following the steps listed below.


SE38

SAP Menu


2. Execute the SYCM_DISPLAY_SIMPLIFICATIONS report. 3. On the Display simplifications that affect custom code objects screen, insert the ID of your recently upgraded system in the System ID field. Optional: Define additional selection criteria. 4. Choose Execute. 5. On the Objects affected by simplifications screen, select the header of the Note column and choose Set filter… 6. In the Determine Values for Filter Criteria dialog box, insert the value 2200691 in the Note field and choose Execute. 7. If the (now filtered) list contains a reference to SAP Note 2200691 SD rebate: Simplifications in SAP S/4HANA, perform the additional activities as per this SAP Note. Among others, adapt custom code according to the detailed guidance given in this SAP Note. Building blocks are: a. Table VBOX: If customer-defined reports read from this table, they need to be adapted to use FM SD_REBATES_GET_INVOICES_IM to read the relevant billing documents directly from application tables instead. b. Communication Structure KOMG: If User-Exits, Business Add-Ins (BAdIs) or Modifications were used to fill KOMG before the conversion, Customizing Table TREB_CUST_MAP_IM is to be used in order to establish the correlation of KOMG with the original document data; if the customer-specific logic is too complex for direct mapping, BAdI SD_REBATES_IM can be used. c. Enhanced Rebate: If this functionality was used before the conversion, a onetime setup of the data in table S469 is required after the conversion (report: ENH_REBATE_S469RB) as this table is cleared during conversion; see SAP Note 1060629 SDS060RB/ENH_REBATE_S469RB:Reorg. of data relevant to rebate for a detailed description of the report

Result You have evaluated the results of the custom code check for any reference to change requirements with regards to the optimization of SD Rebate Processing for customers using the CRM functionality Trade Promotion Management (TPM).

8.3 Output Management Use With SAP S/4HANA, a new output management approach is in place. The new architecture is based on Adobe Document Server and Adobe Forms only. For all billing documents and all purchase orders created in SAP S/4HANA, the new output management is used.

© SAP SE

Public

Page 42 of 112

SAP Best Practices


Procedure Billing documents and purchase orders that were created in SAP ERP are still processed using the NAST-based output control after the conversion. For new billing documents and purchase orders that were created after the conversion, you have to customize the new output management. For more information, see SAP Notes 2228611 Output Management in SAP S/4HANA and 2292539 SAP S/4HANA output control configuration.

8.4 Ariba Network Integration This step is only relevant if you have converted SAP ERP add-on Ariba Network Integration for SAP Business Suite to SAP S/4HANA.

Use After converting from the SAP ERP add-on Ariba Network Integration for SAP Business Suite to SAP S/4HANA, you have to perform the activities described below.

Procedure Polling Agent Scheduling 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the ARBFND_FETCH_CXML_MESSAGES_NEW report. If it is not available in your system, please implement SAP Note 2267601 Polling report does not allow the selection of multiple cXML message types. 3. Access the transaction using one of the following navigation options: Transaction Code

SPRO

IMG Menu

Integration with Other SAP Components → Integration Component for Ariba Network → Framework Settings → Define Basic Message Settings

4. Deselect the Active checkbox for the following entry: Application Component ID

Object Type

cXML Message Type

BNS-ARI-SE-ERP

BUS2081

STAT

5. 6. 7. 8.

Choose Save. Select the Active checkbox for this entry again and choose Save. Choose Back several times. Use the Schedule Supplier Invoice Jobs app to transfer invoice status update messages to the Ariba Network. In this app, select the job template Schedule Supplier Invoice Output. For transferring new purchasing documents to the Ariba Network, you have to perform the following settings: 1. Access the transaction using one of the following navigation options:

© SAP SE

Transaction Code

SPRO

IMG Menu

Integration with Other SAP Components → Integration Component for Ariba Network → Application-Specific Settings → Define Message Output Control

Public

Page 43 of 112

SAP Best Practices


2. Here the following activities are relevant: a) Define Business Rules for Output Determination b) Map Application and Output Type to cXML Message (Output Management) c) Activate Business Transaction Event to Trigger Invoice Status Message

8.5 Environment, Health and Safety Depending on the version of EH&S which is in place, there are different steps to be executed for the conversion to SAP S/4HANA. Therefore the following chapters describe the necessary steps depending on the version of EH&S which is in place. The illustration shows the transition of former components to the new components including the change of scope.

Activities after Conversion to Incident Management Conversion from Component Extension 1.0 for SAP EHS Management Use If you convert Incident Management from Component Extension 1.0 for SAP EHS Management to Environment, Health and Safety, carry out the following activities:

Procedure Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for Personal Object Worklists (POWLs). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown.

© SAP SE

Public

Page 44 of 112

SAP Best Practices


7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The report R_EHFND_LHR_BUILD_PATH will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. 4. Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 5. Choose Execute. 6. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). 7. If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. 8. Adjust all Customizing settings under the IMG node EHS-Foundation and classes for field control from client 000. Using old Customizing settings or classes can lead to short dumps. 9. The authorization object EHHSS_INC1 (access to incidents) has an additional activity C5 (Reopen). If you have already been granted authorizations to your roles/profiles using this authorization object, you may need to check whether it is also necessary to grant this new activity for reopening closed incidents. The following new authorization objects are available: EHHSS_INC2 EHHSS_INC3 EHHSS_INC5 You should additionally configure these authorization objects. If authorization objects EHHSS_INC3 and EHHSS_INC5 are not applicable for your use case, you can deactivate the objects by deactivating the corresponding BAdI in Customizing. Therefore: Access the Customizing activity using the following navigation option: IMG Menu

Environment, Health and Safety → Incident Management → Business Add-Ins → Business Add-Ins for Authorization → BAdI: Extended Authorization Checks

See SAP Note 1970106 Fatality check box in Injuries/Illnesses table is no longer in use for details regarding the changed usages of the fatality flag.

© SAP SE

Public

Page 45 of 112

SAP Best Practices


See SAP Note 1970313 Deleted objects for details regarding the deletion of class CL_EHHSS_INC_INV_DET_UI_FRM and component configuration EHHSS_INC_REC_OIF_V3_INVDETA_FRM. The database table EHHSSD_INC_LINKI was enhanced with an additional field LINK_CATEGORY that specifies whether a link links to a risk assessment or an incident. The report R_EHHSS_INC_ADJUST_LNK_TBL fills the table with default values (specifying the link as a link to an incident). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_INC_ADJUST_LNK_TBL report. There is no dedicated selection screen so the report starts right away. 3. On the Program R_EHHSS_INC_ADJUST_LNK_TBL screen, a confirmation or warning / error messages are displayed if applicable. 4. Add Personnel Number field to customer-specific versions of offline forms for initial near miss and safety observation. The forms in the standard system are delivered with the new field for the personnel number. If you copied this form in an earlier release, you may want to add this new field and its logic to the copy. 5. Select the attached document, the Notice of Violation (NOV), in existing incident records.

In the previous version, you could indicate that the NOV was attached. Now, you can also choose which of the attached documents the NOV is. It appears linked on the tab for Notice of violations in Incident Management.

Conversion from Component Extension 2.0 for SAP EHS Management Use If you convert Incident Management from Component Extension 2.0 for SAP EHS Management to Environment, Health and Safety, carry out the following activities:


SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown.

© SAP SE

Public

Page 46 of 112

SAP Best Practices


7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The report R_EHFND_LHR_BUILD_PATH will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute. 5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). 6. If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. 7. Adjust all Customizing settings under the IMG node EHS-Foundation and classes for field control from client 000. Using old Customizing settings or classes can lead to short dumps. 8. The authorization object EHHSS_INC1 (access to incidents) has an additional activity C5 (Reopen). If you have already been granted authorizations to your roles/profiles using this authorization object, you may need to check whether it is also necessary to grant this new activity for reopening closed incidents. The following new authorization objects are available: EHHSS_INC2 EHHSS_INC3 EHHSS_INC5 You should additionally configure these authorization objects. If authorization objects EHHSS_INC3 and EHHSS_INC5 are not applicable for your use case, you can deactivate the objects by deactivating the corresponding BAdI in Customizing. Therefore: Access the Customizing activity using the following navigation option: IMG Menu

Environment, Health and Safety → Incident Management → Business Add-Ins → Business Add-Ins for Authorization → BAdI: Extended Authorization Checks

See SAP Note 1970106 Fatality check box in Injuries/Illnesses table is no longer in use for details regarding the changed usages of the fatality flag.

© SAP SE

Public

Page 47 of 112

SAP Best Practices


See SAP Note 1970313 Deleted objects for details regarding the deletion of class CL_EHHSS_INC_INV_DET_UI_FRM and component configuration EHHSS_INC_REC_OIF_V3_INVDETA_FRM.



SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The report R_EHFND_LHR_BUILD_PATH will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. Optional: Normally it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute.

© SAP SE

Public

Page 48 of 112

SAP Best Practices


5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. Adjust all Customizing settings under the IMG node EHS-Foundation and classes for field control from client 000. Using old Customizing settings or classes can lead to short dumps.


Procedure Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for personal object worklists (POWLs). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The report R_EHFND_LHR_BUILD_PATH will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program.

© SAP SE

Public

Page 49 of 112

SAP Best Practices


Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute. 5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles.



SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown.

Conversion from Component Extension 6.0 for SAP EHS Management If you convert Incident Management from Component Extension 6.0 for SAP EHS Management to Environment, Health and Safety, no further activities are required.

© SAP SE

Public

Page 50 of 112

SAP Best Practices


Conversion from EHS Management as part of SAP ERP Use If you convert Industrial Hygiene and Safety (EHS-IHS) of EHS Management as part of SAP ERP to Incident Management of Environment, Health and Safety, carry out the following activities:

Procedure Activate WebDynpro Services. 1. Access the transaction using one of the following navigation options: Transaction Code

SICF

SAP Menu

Tools → Administration → Administration → Network → HTTP Service Hierarchy Maintenance

2. On the Define Services screen, make the following entries: Field Name

Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/bc/nwbc

Service Name

NWBC

3. Choose Execute. 4. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node sap. 5. In the menu bar, choose Service/Host and then Activate from the dropdown list. 6. In the Activation of ICF Services dialog box, choose Yes. 7. Choose Back. 8. On the Define Services screen, make the following entries: Field Name

Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/bc/ui5_ui5

9. Choose Execute. 10. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node ui5. 11. In the menu bar, choose Service/Host and then Activate from the dropdown list. 12. In the Activation of ICF Services dialog box, choose Yes. 13. Choose Back. 14. On the Define Services screen, make the following entries: Field Name

Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/public/bc/ui5_ui5

15. Choose Execute.

© SAP SE

Public

Page 51 of 112

SAP Best Practices


16. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node ILMRWC. 17. In the menu bar, choose Service/Host and then Activate from the dropdown list. 18. In the Activation of ICF Services dialog box, choose Yes. Copy the delivery Customizing from client 000 from Incident Management sub tree and also from Foundation for EHS sub tree into your other clients. Make the relevant settings in the Customizing activities for Environment, Health, and Safety under Foundation for EHS and under Incident Management. Import the data that you have exported before the conversion into your SAP S/4HANA system and carry out the necessary activities as described in the data migration information in SAP Note 2198406 Pre-Transition Checks for software component EA-APPL (attached to SAP Note as file S4HANA_EHS_Data_Migration_(003).pdf).

Activities after Conversion to Health and Safety Management Conversion from Component Extension 2.0 for SAP EHS Management Use If you convert Risk Assessment from Component Extension 2.0 for SAP EHS Management to Health and Safety Management of Environment, Health and Safety, carry out the following activities:


SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The report R_EHFND_LHR_BUILD_PATH will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. © SAP SE

Public

Page 52 of 112

SAP Best Practices


1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute. 5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. In Health and Safety Management, you can use a workplace sampling process. This process supports the gathering of workplace sampling data that replaces the amounts of data series. For more information, see SAP Note 2065178 Deprecation of data series and amounts as of component extension 5.0 for SAP EHS Management Feature Package 1. With workplace sampling data, the Amounts menu item and the corresponding service Create Data Series is no longer required. For this reason, remove the menu items for Amounts and Data Series from your PFCG roles and replace them with the corresponding menu entries for workplace sampling. Note that the delivered PFCG roles (for example SAP_EHSM_MASTER) contain the corresponding menu entries and services for workplace sampling under Health and Safety → Overview → Workplace Sampling. With workplace sampling, the feature to request amounts as a separate step in the risk assessment has been replaced. For this reason, the Specify Assessment Steps and Analysis Methods Customizing activity under Environment, Health and Safety → Health and Safety Management → Risks Analysis no longer contains step EHHSS_RAS_STEP15. If you included this step in your Customizing, remove it for each risk assessment type in the Customizing view Assign Assessment Steps. If you have used agents for risk assessment in Component Extension 2.0 for SAP EHS Management to store rudimentary data for chemicals you may need to manually move the data into the chemical business object.

Conversion from Component Extension 3.0 for SAP EHS Management Use If you convert Risk Assessment from Component Extension 3.0 for SAP EHS Management to Health and Safety Management of Environment, Health and Safety, carry out the following activities:

Procedure Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for Personal Object Worklists (POWLs). 1. Access the transaction using one of the following navigation options:

© SAP SE

Transaction Code

SE38

SAP Menu


Public

Page 53 of 112

SAP Best Practices


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The R_EHFND_LHR_BUILD_PATH report will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute. 5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. In Health and Safety Management, you can use a workplace sampling process. This process supports the gathering of workplace sampling data that replaces the amounts of data series. For more information, see SAP Note 2065178 Deprecation of data series and amounts as of component extension 5.0 for SAP EHS Management Feature Package 1. With workplace sampling data, the menu item Amounts and the corresponding service Create Data Series is no longer required. For this reason, remove the menu items for Amounts and Data Series from your PFCG roles and replace them with the corresponding menu entries for workplace sampling. Note that the delivered PFCG roles (for example SAP_EHSM_MASTER) contain the corresponding menu entries and services for workplace sampling under Health and Safety → Overview → Workplace Sampling. With workplace sampling, the feature to request amounts as a separate step in the risk assessment has been replaced. For this reason, the Specify Assessment Steps and Analysis Methods Customizing activity under Environment, Health and Safety → Health and Safety Management → Risks Analysis no longer contains step EHHSS_RAS_STEP15. If you included this step in your Customizing, remove it for each risk assessment type in the Customizing view Assign Assessment Steps.

© SAP SE

Public

Page 54 of 112

SAP Best Practices


If you have used chemical agents for risk assessment, run the R_EHFND_MIGRATE_CHM report after the conversion. The business object and database structure of EHFND_CHEMICAL has been changed. This report will update existing chemicals from the old structure to the new structure. If you have extended the Customizing for hazard classification or hazard statements, you will need to make some further adjustments. For more details, see the report documentation. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_MIGRATE_CHM report. 3. On the Program R_EHFND_MIGRATE_CHM screen, deselect the Run in Test Mode checkbox and choose Execute. The Configure Report to Transfer Listed Substances and OELs Customizing activity is obsolete. You can check your entries in the view EHFNDV_REGL_FILL using transaction SM30 (Call View Maintenance). For the new R_EHFND_FILL_REGL_BY_EHS_SUBST report, you have to use BAdI Transfer of Chemicals (BADI_EHFND_CHM_TRANSFER) under Environment, Health and Safety → Health and Safety Management → Master Data Configuration → Chemicals → Data Transfer from EHS Specification Database. For more details, see the BAdI documentation.

Conversion from Component Extension 4.0 for SAP EHS Management Use If you convert Risk Assessment from Component Extension 4.0 for SAP EHS Management to Health and Safety Management of Environment, Health and Safety, carry out the following activities:


SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute.

© SAP SE

Public

Page 55 of 112

SAP Best Practices


12. Once finished, the Display logs screen is shown. The BO and database structure of EHFND_LOCATION_STRUCTURE has been extended. The R_EHFND_LHR_BUILD_PATH report will initialize the new path node. If you do not run this report, some CHIPs on the home pages and side panels will not work. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_LHR_BUILD_PATH report. 3. On the Builds the path node of the location structure screen, select Execute program. Optional: Under normal circumstances, it should be sufficient to initialize the current revision only. However, if you have already defined a location structure revision for a future date, you will need to create the path for all revisions. In order to do so, select Create data for all revisions. 4. Choose Execute. 5. Once finished, the screen shows a log with a confirmation (Data for all revisions created or Data for current revision created). If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. In Health and Safety Management, you can use a workplace sampling process. This process supports the gathering of workplace sampling data that replaces the amounts of data series. For more information, see SAP Note 2065178 Deprecation of data series and amounts as of component extension 5.0 for SAP EHS Management Feature Package 1. With workplace sampling data, the menu item Amounts and the corresponding service Create Data Series is no longer required. For this reason, remove the menu items for Amounts and Data Series from your PFCG roles and replace them with the corresponding menu entries for workplace sampling. Note that the delivered PFCG roles (for example SAP_EHSM_MASTER) contain the corresponding menu entries and services for workplace sampling under Health and Safety → Overview → Workplace Sampling. With workplace sampling, the feature to request amounts as a separate step in the risk assessment has been replaced. For this reason, the Specify Assessment Steps and Analysis Methods Customizing activity under Environment, Health and Safety → Health and Safety Management → Risks Analysis no longer contains step EHHSS_RAS_STEP15. If you included this step in your Customizing, remove it for each risk assessment type in the Customizing view Assign Assessment Steps. Run the R_EHHSS_RAS_FIX_CHM_KEY_REF report after the conversion. The report corrects keys for chemical revisions (CHM_REV_KEY) in table EHHSSD_RSK_REV. If you do not run this report, you may have inconsistent data. For more information, see SAP Note 2076880 Risk Assessment Follow Up: chemical revision key is not copied into the new risk revision. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_RAS_FIX_CHM_KEY_REF report. 3. On the Correction of Keys for Chemical Revisions screen, deselect the Test Mode checkbox and choose Execute.

© SAP SE

Public

Page 56 of 112

SAP Best Practices


Run the R_EHFND_CHM_UPGRADE_WPCP report after the conversion. The business object and database structure of EHFND_CHEMICAL has been changed. This report will remove duplicate entries in the list of workplace control parameters. If you do not run this report, existing chemicals can show duplicate entries. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_CHM_UPGRADE_WPCP report. 3. On the Cleanup of Components with Workplace Control Parameters screen, deselect the Run in Test Mode checkbox. Optional: Enter a specific chemical in the Chemical field to perform the cleanup for this chemical only. If you do not enter a chemical, all chemicals in the system are processed. 4. Choose Execute. In Health and Safety Management, you can use quantitative exposure assessments. The changes in the data model for the quantitative exposure assessment affects the triggering criteria of Health Surveillance Protocols (HSP). Due to the change, some triggering criteria that were created in the component extension for SAP EHS Management that contain exposure ratings could now be inconsistent. For more information, see SAP Note 2095991 Adaption of Health Surveillance Protocols Triggering Criteria.

Conversion from Component Extension 5.0 for SAP EHS Management Use If you convert Risk Assessment from component extension 5.0 for SAP EHS Management to Health and Safety Management of Environment, Health and Safety, there are two different sets of activities to be performed depending on the exact release of this Component Extension (SP00, FP01).

8.5.2.4.1 Conversion from SP00 of Component Extension 5.0 for SAP EHS Management Use If you convert Risk Assessment from Component Extension 5.0 for SAP EHS Management (SP00) to Health and Safety Management of Environment, Health and Safety, carry out the following activities:

Procedure If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for Personal Object Worklists (POWLs). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the POWL_D04 report.

© SAP SE

Public

Page 57 of 112

SAP Best Practices


3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. In Health and Safety Management, you can use a workplace sampling process. This process supports the gathering of workplace sampling data that replaces the amounts of data series. For more information, see SAP Note 2065178 Deprecation of data series and amounts as of component extension 5.0 for SAP EHS Management Feature Package 1. With workplace sampling data, the menu item Amounts and the corresponding service Create Data Series is no longer required. For this reason, remove the menu items for Amounts and Data Series from your PFCG roles and replace them with the corresponding menu entries for workplace sampling. Note that the delivered PFCG roles (for example SAP_EHSM_MASTER) contain the corresponding menu entries and services for workplace sampling under Health and Safety → Overview → Workplace Sampling. With workplace sampling, the feature to request amounts as a separate step in the risk assessment has been replaced. For this reason, the Specify Assessment Steps and Analysis Methods Customizing activity under Environment, Health and Safety → Health and Safety Management → Risks Analysis no longer contains step EHHSS_RAS_STEP15. If you included this step in your Customizing, remove it for each risk assessment type in the Customizing view Assign Assessment Steps. Run the R_EHHSS_RAS_FIX_CHM_KEY_REF report after the conversion. The report corrects keys for chemical revisions (CHM_REV_KEY) in table EHHSSD_RSK_REV. If you do not run this report, you may have inconsistent data. For more information, see SAP Note 2076880 Risk Assessment Follow Up: chemical revision key is not copied into the new risk revision. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_RAS_FIX_CHM_KEY_REF report. 3. On the Correction of Keys for Chemical Revisions screen, deselect the Test Mode checkbox and choose Execute. Run the R_EHFND_CHM_UPGRADE_WPCP report after the conversion. The business object and database structure of EHFND_CHEMICAL has been changed. This report will remove duplicate entries in the list of workplace control parameters. If you do not run this report, existing chemicals can show duplicate entries. 1. Access the transaction using one of the following navigation options:

© SAP SE

Transaction Code

SE38

SAP Menu


Public

Page 58 of 112

SAP Best Practices


2. Execute the R_EHFND_CHM_UPGRADE_WPCP report. 3. On the Cleanup of Components with Workplace Control Parameters screen, deselect the Run in Test Mode checkbox. Optional: Enter a specific chemical in the Chemical field to perform the cleanup for this chemical only. If you do not enter a chemical, all chemicals in the system are processed. 4. Choose Execute. In Health and Safety Management, you can use quantitative exposure assessments. The changes in the data model for the quantitative exposure assessment affects the triggering criteria of Health Surveillance Protocols (HSP). Due to the change, some triggering criteria that were created in the component extension for SAP EHS Management that contain exposure ratings could now be inconsistent. For more information, see SAP Note 2095991 Adaption of Health Surveillance Protocols Triggering Criteria.

8.5.2.4.2 Conversion from FP01 of Component Extension 5.0 for SAP EHS Management Use If you convert Risk Assessment from Feature Package 01 of Component Extension 5.0 for SAP EHS Management to Health and Safety Management of Environment, Health and Safety, carry out the following activities:


SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. Run the R_EHHSS_RAS_FIX_CHM_KEY_REF report after the conversion. The report corrects keys for chemical revisions (CHM_REV_KEY) in table EHHSSD_RSK_REV. If you do not run this report, you may have inconsistent data.

© SAP SE

Public

Page 59 of 112

SAP Best Practices


For more information, see SAP Note 2076880 Risk Assessment Follow Up: chemical revision key is not copied into the new risk revision. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_RAS_FIX_CHM_KEY_REF report. 3. On the Correction of Keys for Chemical Revisions screen, deselect the Test Mode checkbox and choose Execute. Run the R_EHFND_CHM_UPGRADE_WPCP report after the conversion. The business object and database structure of EHFND_CHEMICAL has been changed. This report will remove duplicate entries in the list of workplace control parameters. If you do not run this report, existing chemicals can show duplicate entries. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHFND_CHM_UPGRADE_WPCP report. 3. On the Cleanup of Components with Workplace Control Parameters screen, deselect the Run in Test Mode checkbox. Optional: Enter a specific chemical in the Chemical field to perform the cleanup for this chemical only. If you do not enter a chemical, all chemicals in the system are processed. 4. Choose Execute. Run the R_EHHSS_RAS_FIX_ABAGT_KEY_REF report after the conversion. The report corrects keys for airborne agent revisions (ABAGT_REV_KEY) in table EHHSSD_RSK_REV. If you do not run this report, you may have inconsistent data. For more information, see SAP Note 2077301 Risk Assessment Follow Up: airborne agent revision key is not copied into the new risk revision. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_RAS_FIX_ABAGT_KEY_REF report. 3. On the Correction of Keys for Airborne Agent Revisions screen, deselect the Test Mode checkbox. 4. Choose Execute. Run the R_EHHSS_SPLCP_INITIALIZE_ATF report after the conversion. The sampling campaign business object has been extended. This report will initialize the attachment folders for existing sampling campaigns. 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the R_EHHSS_SPLCP_INITIALIZE_ATF report. 3. On the Initialization of Attachment Folders for Sampling Campaigns screen, deselect the Run in Test Mode checkbox. 4. Choose Execute. Run the R_EHFND_SPLMT_UPGRADE_TYPE report after the conversion. The EHFNDC_SPLMT configuration table has been extended. This report will initialize the new EHSM_COMPONENT field. If you do not run this report, some previously created sampling methods will not be visible.

© SAP SE

Public

Page 60 of 112

SAP Best Practices



SE38

SAP Menu


2. Execute the R_EHFND_SPLMT_UPGRADE_TYPE report.

Conversion from Component Extension 6.0 for SAP EHS Management If you convert Risk Assessment from Component Extension 6.0 for SAP EHS Management to Health and Safety Management of Environment, Health, and Safety, no further activities are required.

Conversion from EHS Management as part of SAP ERP Use If you convert Industrial Hygiene and Safety (EHS-IHS) of EHS Management as part of SAP ERP to Health and Safety Management of Environment, Health, and Safety, carry out the following activities:

Procedure Activate WebDynpro Services 1. Access the transaction using one of the following navigation options: Transaction Code

SICF

SAP Menu



Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/bc/nwbc

Service Name

NWBC

3. Choose Execute. 4. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node sap. 5. In the menu bar, choose Service/Host and then Activate from the dropdown list. 6. In the Activation of ICF Services dialog box, choose Yes. 7. Choose Back. 8. On the Define Services screen, make the following entries: Field Name

Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/bc/ui5_ui5

9. Choose Execute.

© SAP SE

Public

Page 61 of 112

SAP Best Practices


10. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node ui5. 11. In the menu bar, choose Service/Host and then Activate from the dropdown list. 12. In the Activation of ICF Services dialog box, choose Yes. 13. Choose Back. 14. On the Define Services screen, make the following entries: Field Name

Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/public/bc/ui5_ui5

15. Choose Execute. 16. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node ILMRWC. 17. In the menu bar, choose Service/Host and then Activate from the dropdown list. 18. In the Activation of ICF Services dialog box, choose Yes. Copy the delivery Customizing from client 000 from the Incident Management sub tree and also from the Foundation for EHS sub tree into your other clients. Make the relevant settings in the Customizing activities for Environment, Health, and Safety under Foundation for EHS and under Incident Management. Import the data that you have exported before the conversion into your SAP S/4HANA system and carry out the necessary activities as described in the data migration information in SAP Note 2198406 Pre-Transition Checks for software component EA-APPL (attached to SAP Note as file S4HANA_EHS_Data_Migration_(003).pdf).

Activation of WebDynpro Services Use After having performed the above described activities, you have to carry out the following steps to activate the new WebDynpro Services.

Procedure Activate WebDynpro Services 1. Access the transaction using one of the following navigation options: Transaction Code

SICF

SAP Menu



Entry Value

Hierarchy Type

SERVICE

Virtual Host

DEFAULT_HOST

Service Path

/sap/bc/webdynpro/sap/

Service Name

EHFND*

3. Choose Execute. 4. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node sap.

© SAP SE

Public

Page 62 of 112

SAP Best Practices


5. In the menu bar, choose Service/Host and then Activate from the dropdown list. 6. In the Activation of ICF Services dialog box, choose Yes. The dialog box may appear repeatedly for the different services. 7. Choose Back. 8. On the Define Services screen, change the entry in the Service Name field to EHHSS* and choose Execute. 9. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node sap. 10. In the menu bar, choose Service/Host and then Activate from the dropdown list. 11. In the Activation of ICF Services dialog box, choose Yes. The dialog box may appear repeatedly for the different services. 12. Choose Back. 13. On the Define Services screen, change the entry in the Service Name field to POWL and choose Execute. 14. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node POWL. 15. In the menu bar, choose Service/Host and then Activate from the dropdown list. 16. In the Activation of ICF Services dialog box, choose Yes. 17. Choose Back. 18. On the Define Services screen, change the entry in the Service Name field to IBO_WDA_INBOX and choose Execute. 19. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node IBO_WDA_INBOX. 20. In the menu bar, choose Service/Host and then Activate from the dropdown list. 21. In the Activation of ICF Services dialog box, choose Yes. 22. Choose Back. 23. On the Define Services screen, change the entry in the Service Name field to WDR_CHIP_PAGE and choose Execute. 24. On the Define Services screen (in the screen area Virtual Hosts/Services), select the node WDR_CHIP_PAGE. 25. In the menu bar, choose Service/Host and then Activate from the dropdown list. 26. In the Activation of ICF Services dialog box, choose Yes. 27. Choose Back.

Activities after Conversion to Product Safety and Stewardship Conversion of Product Compliance from Component Extension 3.0 for SAP EHS Management Use If you convert Product Compliance from Component Extension 3.0 for SAP EHS Management to Product Compliance for Discrete Industries, carry out the following activities:

Procedure General Activities Verify the Customizing as described in the Installation Guide for SAP S/4HANA 1511 FPS01 under the Follow-Up Activities for Product Compliance chapter. Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for Personal Object Worklists (POWLs).

© SAP SE

Public

Page 63 of 112

SAP Best Practices



SE38

SAP Menu


3. Execute the POWL_D04 report. 4. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 5. Choose Execute. 6. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 7. Repeat this step until the Display logs screen is shown. 8. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 9. Choose Back twice. 10. Execute the POWL_D01 report. 11. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 12. Choose Execute. 13. Once finished, the Display logs screen is shown. Run the R_EHPRC_REV_PROC_STATUS_INIT report after the conversion. A new field processing status has been introduced in the ROOT node of the business object EHPRC_COMPLIANCE_DATA: This report will update existing compliance data objects and fill the correct processing status value. Since the migration is client-dependent, you must execute the report in all clients that contain compliance data. Make sure that the user account that is used for executing the report has sufficient authorizations to modify compliance data. As the report can run into errors (for example, locking errors), we recommend you to run the report at a time when the system is not used by end users. The report can be re-executed any number of times and will try to migrate only these records which have not been migrated yet. 1. a. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


b. Execute the R_EHPRC_REV_PROC_STATUS_INIT report. If you have created customer roles, check if the provided template roles contain new menu entries needed to be integrated into your customer roles. After integration, regenerate the corresponding authorization profiles. Follow-Up Activities for Simplified Import of Material Declarations Product Compliance for Discrete Industries contains a simplified import of material declarations. With this import, you can import the IPC 1752-A Class C XML files in an alternative way. If you want to use the simplified import of material declarations as the default import for IPC XML files, you have to remove the old Template and Documents Customizing for the template IPC_XML_C and replace them with the new Template and Documents Customizing for the new template IPC_XML that is covered by the BC sets. Carry out the Customizing activity Specify Outgoing and Incoming Templates 1. Access the Customizing activity using the following navigation option: IMG Menu

© SAP SE

Product Safety and Stewardship → Product Compliance for Discrete Industries → General Configuration → Data Exchange → Specify Outgoing and Incoming Templates

Public

Page 64 of 112

SAP Best Practices


2. The old template ID IPC_XML_C is no longer used, but you should not delete the template definition because the template name is still used for existing documents. As an option, you can change the name of the template. The new template IPC_XML from the BC set must be available. Carry out the Customizing activity Specify Incoming Templates. 1. Access the Customizing activity using the following navigation option: IMG Menu

Product Safety and Stewardship → Product Compliance for Discrete Industries → General Configuration → Data Exchange → Specify Incoming Templates

2. To replace the old IPC 1752-A Class C import with the simplified import of material declarations, you have to remove the old IPC_XML_C template from the incoming templates, including all entries in the sub structure. The new template IPC_XML from the BC set must be available. Carry out the Customizing activity Specify Outgoing Templates. 1. Access the Customizing activity using the following navigation option: IMG Menu

Product Safety and Stewardship → Product Compliance for Discrete Industries → General Configuration → Data Exchange → Specify Outgoing Templates

2. New generated IPC XML files should also use the new template IPC_XML. Therefore you have to remove the old template IPC_XML_C from the outgoing templates. The new template IPC_XML from the BC set must be available and all values must be identical between the two templates before you remove the old template. Carry out the Customizing activity Define Templates for the Compliance Object. 1. Access the Customizing activity using the following navigation option: IMG Menu

Product Safety and Stewardship → Product Compliance for Discrete Industries → General Configuration → Compliance Object → Define Templates for the Compliance Object

2. To import the compliance documents in the Compliance Workbench with the simplified Import for Material Declarations, you have to remove the old document settings based on the template IPC_XML_C in the sub dialog structures Define Incoming Documents and Define Outgoing Documents. The new document settings based on the new template IPC_XML from the BC set must be available and all values must be identical between the two documents before you remove the old document settings. Carry out the Specify Checks for Compliance Requirement and Check Criteria Customizing activity. 1. Access the Customizing activity using the following navigation option: IMG Menu

Product Safety and Stewardship → Product Compliance for Discrete Industries → General Configuration → Regulations and Compliance Requirements → Specify Checks for Compliance Requirement and Check Criteria

To import the compliance requirement revision documents in the Compliance Workbench with the simplified Import for Material Declarations, copy the settings for the old document settings based on the template IPC_XML_C in the sub dialog structures Define Incoming Documents and Define Outgoing Documents to the new document settings of the template IPC_XML for all relevant compliance requirements. When the new document settings of the template IPC_XML exist, remove the old document settings based on the template IPC_XML_C. The new document settings based on the new template IPC_XML from the BC set or depending

© SAP SE

Public

Page 65 of 112

SAP Best Practices


on manual entries must be available and all values must be identical between the two documents before you remove the old document settings. Only the document settings for the compliance requirements ROHS, CHINA-ROHS, JIG and REACH_SVHC are available in the BC set. For all other compliance requirements, you have to create the settings manually.

Conversion of Product Compliance from Component Extension 4.0 for SAP EHS Management Use If you convert Product Compliance from Component Extension 4.0 for SAP EHS Management to Product Compliance for Discrete Industries, carry out the following activities:

Procedure General Activities Verify the Customizing as described in the Installation Guide for SAP S/4HANA 1511 FPS01 under chapter Follow-Up Activities for Product Compliance. Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for personal object worklists (POWLs). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. Follow-Up Activities for Simplified Import of Material Declarations Product Compliance for Discrete Industries contains a simplified import of material declarations. With this import, you can import the IPC 1752-A Class C XML files in an alternative way. If you want to use the simplified import of material declarations as the default import for IPC XML files, you have to remove the old Template and Documents Customizing for the template IPC_XML_C and replace them with the new Template and Documents Customizing for the new template IPC_XML that is covered by the BC sets. Carry out the Customizing activity Specify Outgoing and Incoming Templates. 1. Access the Customizing activity using the following navigation option:

© SAP SE

Public

Page 66 of 112

SAP Best Practices

IMG Menu



2. The old template ID IPC_XML_C is no longer used, but you should not delete the template definition because the template name is still used for existing documents. As an option, you can change the name of the template. The new template IPC_XML from the BC set must be available. Carry out Customizing activity Specify Incoming Templates. 1. Access the Customizing activity using the following navigation option: IMG Menu


2. To replace the old IPC 1752-A Class C import with the simplified import of material declarations, you have to remove the old IPC_XML_C template from the incoming templates, including all entries in the sub structure. The new template IPC_XML from the BC set must be available. Carry out Customizing activity Specify Outgoing Templates. 1. Access the Customizing activity using the following navigation option: IMG Menu


2. New generated IPC XML files should also use the new template IPC_XML. Therefore you have to remove the old template IPC_XML_C from the outgoing templates. The new template IPC_XML from the BC set must be available and all values must be identical between the two templates before you remove the old template. Carry out Customizing activity Define Templates for the Compliance Object. 1. Access the Customizing activity using the following navigation option: IMG Menu




To import the compliance requirement revision documents in the Compliance Workbench with the simplified Import for Material Declarations, copy the settings for the old document settings based on the template IPC_XML_C in the sub dialog structures Define Incoming Documents and Define Outgoing Documents to the new document settings of the template IPC_XML for all relevant compliance requirements. When the new document settings of the template

© SAP SE

Public

Page 67 of 112

SAP Best Practices


IPC_XML exist, remove the old document settings based on the template IPC_XML_C. The new document settings based on the new template IPC_XML from the BC set or depending on manual entries must be available and all values must be identical between the two documents before you remove the old document settings. Only the document settings for the compliance requirements ROHS, CHINA-ROHS, JIG and REACH_SVHC are available in the BC set. For all other compliance requirements, you have to create the settings manually.

Conversion of Product Compliance from Component Extension 5.0 for SAP EHS Management Use If you convert Product Compliance from Component Extension 5.0 for SAP EHS Management to Product Compliance for Discrete Industries as part of Product Safety and Stewardship, carry out the following activities:

Procedure General Activities Verify the Customizing as described in the Installation Guide for SAP S/4HANA 1511 FPS01 under chapter Follow-Up Activities for Product Compliance. Clear POWL caches according to SAP Note 1916079 EHFNDS_TM_SEARCHFIELDSmax_rows not existing. Therefore, run the following 2 reports in the given order to clear the cache for Personal Object Worklists (POWLs). 1. Access the transaction using one of the following navigation options: Transaction Code

SE38

SAP Menu


2. Execute the POWL_D04 report. 3. On the Delete Cached Selection Criteria for Admin Queries screen, insert EH* in the Query ID field. Optional: Enter additional selection criteria in the POWL Type ID field. 4. Choose Execute. 5. In the Prompt for Customizing request dialog box, enter the number of a valid Customizing request in the Request field and choose Continue. 6. Repeat this step until the Display logs screen is shown. 7. On this screen, a list of messages is displayed with further details on the IDs of the respective admin queries for which cached selection criteria were deleted. 8. Choose Back twice. 9. Execute the POWL_D01 report. 10. On the Delete Queries from Database screen, insert EH* into the APPLID field, clear the User field and deselect the DISPLAY checkbox. Optional: enter additional selection criteria in the User field. 11. Choose Execute. 12. Once finished, the Display logs screen is shown. Follow-Up Activities for Simplified Import of Material Declarations Product Compliance for Discrete Industries contains a simplified import of material declarations. With this import, you can import the IPC 1752-A Class C XML files in an alternative way. If you want to use the simplified import of material declarations as the default import for IPC XML files, you have to remove the old Template and Documents Customizing for the template IPC_XML_C and replace them with the new Template and Documents Customizing for the new template IPC_XML that is covered by the BC sets.

© SAP SE

Public

Page 68 of 112

SAP Best Practices


Carry out the Specify Outgoing and Incoming Templates Customizing activity. 1. Access the Customizing activity using the following navigation option: IMG Menu


2. The old template ID IPC_XML_C is no longer used, but you should not delete the template definition because the template name is still used for existing documents. As an option, you can change the name of the template. The new template IPC_XML from the BC set must be available. Carry out the Specify Incoming Templates Customizing activity. 1. Access the Customizing activity using the following navigation option: IMG Menu


2. To replace the old IPC 1752-A Class C import with the simplified import of material declarations, you have to remove the old IPC_XML_C template from the incoming templates, including all entries in the sub structure. The new template IPC_XML from the BC set must be available. Carry out the Specify Outgoing Templates Customizing activity. 1. Access the Customizing activity using the following navigation option: IMG Menu


2. New generated IPC XML files should also use the new template IPC_XML. Therefore you have to remove the old template IPC_XML_C from the outgoing templates. The new template IPC_XML from the BC set must be available and all values must be identical between the two templates before you remove the old template. Carry out the Define Templates for the Compliance Object Customizing activity. 1. Access the Customizing activity using the following navigation option: IMG Menu




To import the compliance requirement revision documents in the Compliance Workbench with the simplified Import for Material Declarations, copy the settings for the old document settings © SAP SE

Public

Page 69 of 112

SAP Best Practices


based on the template IPC_XML_C in the sub dialog structures Define Incoming Documents and Define Outgoing Documents to the new document settings of the template IPC_XML for all relevant compliance requirements. When the new document settings of the template IPC_XML exist, remove the old document settings based on the template IPC_XML_C. The new document settings based on the new template IPC_XML from the BC set or depending on manual entries must be available and all values must be identical between the two documents before you remove the old document settings. Only the document settings for the compliance requirements ROHS, CHINA-ROHS, JIG and REACH_SVHC are available in the BC set. For all other compliance requirements, you have to create the settings manually.

Conversion of Product Compliance from Component Extension 6.0 for SAP EHS Management If you convert Product Compliance from Component Extension 6.0 for SAP EHS Management to Product Compliance for Discrete Industries, no further activities are required.

Conversion of Product Safety and Stewardship for Process Industries Once you have converted from an SAP ERP system to an SAP S/4HANA system, ensure that you have implemented the most recent versions of Expert / Open Content Connector (OCC) and Windows Wordprocessor Integration (WWI) in your system landscape. For information regarding installation instructions for WWI and Expert / OCC, see SAP Note 568302 Current version of EH&S WWI and EH&S Expert or OCC.

9

Application Follow-Up Activities in Business Downtime: Finance

Once your system is technically converted to SAP S/4HANA, perform the activities for Financials application related migration. Perform these activities in Production system, or any of the systems involved in SAP S/4HANA system conversion. To run the activity in any of following steps, choose the IMG execution button ( ). For the activities without Execution button ( ), choose the Help activity and follow the instructions. Since all the activities are structured in sequence in IMG, no separate IMG path, transaction code or program name are provided in this document. Most of the activities are structured in this way: the first activity is to execute, and the very next one is to monitor the status and display the log. The execution activity has always the same screen. You can see under Mass data run the execution phase. If you have NEVER run the job before, you will see Start firs run; if you have run the job before, get however errors, you will see Complete the first run. Under Batch job control you can define the number of batch jobs. This execution activity parallelizes mass data processing using batch work processes (Type = BTC). The number of batch jobs to be used should be decided based on your system resource, like the total number of batch work processes, size of memory, disc size for spool. You should find the optimal value during rehearsals.

© SAP SE

Public

Page 70 of 112

SAP Best Practices


Next to the execution activity is the monitor activity. These kind of reports displays the application log of the last execution activity. You can also find this log later in transaction Analyze Application Log (transaction code SLG1). The program displays a list of all clients for which data processing is performed. For each client, it includes the processed data packages and their processing status. The data packages are specified using their technical names, which can consist, for example, of a company code, ledger ID, year, and period. If mass data processing has not yet been performed for a client, the processing status of the client is marked with a red traffic light. If a log number is available for a data package, you can display a package-specific log by double-clicking the data package entry. If the log show in errors, you must check and correct the reason for this failure. When you have completed the corrections, you must start the migration again. For all the monitor activities, you must see green light (finished) for all the clients. If any client has yellow light (waiting) or red light (Issues found), you must solve the problems and restart the execution step again. The prerequisite is all the inconsistent documents found in the consistency check section must be corrected or archived.

9.1 Deactivate Asset Accounting Use If you do not want to use Asset Accounting and are also not planning on using it in future, you must deactivate Asset Accounting before the migration.

Procedure 1. Access the transaction: Transaction Code

SM30

2. In theTable/View field enter TRWCA, choose under Restrict Data Range radio button No Restrictions. 3. Choose Maintain. 4. Deactivate component RAIN (Asset Accounting) by unchecking Active.

Result Asset Accounting is deactivated.

9.2 Preparation and Migration of Customizing These activities should be only performed in the Development system, and transported to the downstream systems by transport request.

Check Customizing Settings Prior to Migration Use The program checks whether the Customizing fulfills the requirement of SAP S/4HANA migration.

Procedure Execute the Check Customizing Settings Prior to Migration IMG activity.

© SAP SE

Public

Page 71 of 112

SAP Best Practices


Result You should now see a Check passed message in the job log if the configurations are right. This program has the same function as FINS_MIG_PRECHECK_CUST_SETTNGS provided by SAP Note 2129306 Check Customizing Settings Prior to Upgrade to Simple Finance (sFIN 2.0), which should have been executed before the technical conversion. Run it after the technical conversion as a double check.

Define Message Type for Posting Before and During Migration Use In this Customizing activity you define that users are informed by a message when they want to post in the system although the migration has not been set to finish. By default, before finalizing the migration an error will occur in case of attempted posting: FINS_FI_MIG 150 Data migration is not yet finished: Posting of documents is not possible. The message can be switched from error to information in the test environment.

Procedure 1. 2. 3. 4. 5. 6. 7. 8. 9.

Enter the FINS_FI_MIG work area. Select Continue. If there is no entry for message 150 yet, create it by choosing New Entries. In the MsgNo field enter 150, and choose Enter. Enter in User Name field the user ID if the message applies to a specific user. Leave the User Name field empty if the message applies to all users. In the Online field and Batch define if the message is should be shown as Error (E), or Warning (W), or Note in window (I), or Note in footer (S). If the message applies to more than one user but not to all users, select New Entries and repeat step 3 to 6. Choose Save. On the Prompt for Customizing request screen choose or create the Customizing request you want to use, and choose

continue (ENTER).

Result You should now see the Data was saved information in the footer. The Data migration is not yet finished: Updating of documents is not possible message will be issued as you configured above before the migration is set to complete.

Preparation and Migration of Customizing for General Ledger These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package. SAP S/4HANA General Ledger is based on new General Ledger. You have to technically migrate to SAP S/4HANA General Ledger, either from classic General Ledger or new General Ledger.

© SAP SE

Public

Page 72 of 112

SAP Best Practices


Activate SAP Reference IMG for Financial Accounting (New) Use In this Customizing activity you activate the SAP reference IMG structure for Financial Accounting (New) and the menu. You do not need do it if you have been using Financial Accounting (New) before.

Procedure To activate the SAP reference IMG structure do the following: 1. Execute transaction code SE38. 2. Enter the program RFAGL_SWAP_IMG_NEW. 3. Choose Execute. 4. On the Activate/Deactivate New Implementation Guide screen select Activate New IMG. 5. Choose Execute. 6. You should now see the Setting was saved message. To activate the menu do the following: 1. Execute SE38 transaction code. 2. Enter the RFAGL_SWAP_MENU_NEW program. 3. On the Activate/Deactivate New Implementation Guide select Activate New MENU screen. 4. Choose Execute.

Result In the SAP Reference IMG the structure for Financial Accounting (New) is now visible and can be used. In the menu, the relevant structure is visible and can be used.

Check and Adopt Fiscal Year Variants Use The migration to the unified journal entry requires a unique fiscal year variant in controlling and financial. In this Customizing activity you compare the fiscal year variants between controlling areas and their assigned company codes. The report reconciles the fiscal year variant of the controlling areas and their assigned company codes. It creates a proposal for the configuration change. This check should be done by the FINS_MIG_PRECHECK_CUST_SETTNGS report in the prerequisite check. Run it again after the technical conversion to cross check.

Procedure 1. Execute the Check and Adopt Fiscal Year Variants IMG activity. 2. Put in all the controlling area existing in the system, e.g. *. 3. The report lists all controlling areas and company codes to be changed. The number of the posting periods and the special periods are listed. The Det. FYV for CoAr column (determined fiscal year variant for controlling area) and Det. FYV for CoCd (determined fiscal year variant for company code) provides the proposal for the configuration change. 4. Differences in the posting periods cannot be changed. In this case, you need to change the fiscal year variant to equalize the posting periods.

© SAP SE

Public

Page 73 of 112

SAP Best Practices


5. Call the configuration transactions from the list if any change is needed.

Result Once you have a unique fiscal year variant in controlling and financial, the report shows No changes required for fiscal year variants.

Migrate General Ledger Customizing Use In this activity you migrate all G/L ledgers configurations to the new configuration view. The following are migrated:     

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

Procedure 1. Execute the Migrate General Ledger Customizing IMG activity. 2. On the Prompt for Customizing request screen choose or create the Customizing request you want to use, and choose

to continue (ENTER).

Result Once you have successfully migrated the general ledger Customizing, the system shows the following messages: Check passed Ledger $ successfully migrated Ledger configuration copied to new Journal Entry Ledger configuration in this client.

Define Settings for Ledgers and Currency Types Use In this Customizing activity you define the ledgers that you use in Accounting. For SAP S/4HANA system conversion, it is not necessary to make changes here. However, it is recommended to check and make changes if the system to be migrated has not consistent setup.

Procedure 1. Execute the Define Settings for Ledgers and Currency Types IMG activity. 2. Choose Save.

Result The settings of ledgers and currency types are saved.

© SAP SE

Public

Page 74 of 112

SAP Best Practices


Define Ledger for CO Version Use In this activity you define a ledger that represents Controlling.

Procedure 1. Execute the Define Ledger for CO Version IMG activity. 2. Assign the version 0 to a ledger. The current restriction is that the version 000 must be assigned to the leading ledger.

Result You assigned the version 000 to the leading ledger for all company codes that are assigned to a Controlling area.

Define Document Types for Postings in Controlling Use In this activity you can create new document types for postings in Controlling.

Procedure 1. Execute the Define Document Types for Postings in Controlling IMG activity. 2. Choose New Entries. 3. Enter Document type, assign Number range, Reverse Document Type, select G/L account as Account types allowed. 4. Choose Save.

Result The document type is created.

Define Document Type Mapping Variants for CO Business Transactions Use 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. The reason for this is that the Migrate Accounting Documents to Universal Journal Entry Structure activity requires a document type for each CO document.

Procedure 1. Execute the Define Document Type Mapping Variants for CO Business Transactions IMG activity. 2. The migration of the ledger Customizing generates a default mapping variant 0000000001. Copy from the mapping variant 0000000001 to your own mapping variant. 3. In the Mapping of CO Bus. Transactions to Document Types view, you can change the document type for each CO business transaction.

Result Each CO business transaction has been assigned with the document type you want.

© SAP SE

Public

Page 75 of 112

SAP Best Practices


Check and Define Default Values for Postings in Controlling Use In this activity, you define default values for CO business transactions when user interfaces do not allow you to enter a document type or a ledger group for posting purposes.

Procedure 1. Execute the Check and Define Default Values for Postings in Controlling IMG activity. 2. You have defined a document type mapping variant that maps CO business transactions to document types. Please see step Define Document Type Mapping Variants for CO Business Transactions in this document. Assign it to each company code by entering it in field Document Type Mapping Variants. 3. If you do not enter a default ledger group, all CO postings will be done to all G/L ledgers. 4. Choose Save. 5. Choose New Entries if your company code does not appear in the list, and repeat step 2 to 4.

Result You have defined the Default Ledger Group and the Document Type mapping variant for all the company codes.

Define Offsetting Account Determination Type Use In this activity you define how the system calculates the offsetting account in all applications. This activity is a prerequisite for the activity Fill the Offsetting Account in FI Documents.

Procedure 1. Execute the Define Offsetting Account Determination Type IMG activity. 2. You might see the No entries exist, double-click for long text message. Choose New Entries in this case. 3. In the Define Offsetting Account Determination screen, SAP recommends to choose the option As case 2, but including lime items generated automatically. 4. Choose Save.

Result You have defined the Define Offsetting Account Determination Type.

Define Currency Settings for Migration Use In this activity you maintain exchange rate types for SAP S/4HANA migration. SAP S/4HANA migration has to fill the amount in company code currency for all items of the universal journal. In case amounts are available in other currencies only, e.g. for purely statistical items in table COEP, the company code currency is translated from another amount. The rate used this currency translation is determined by the posting date and the exchange rate type provided here.

Procedure 1. Choose New Entries.

© SAP SE

Public

Page 76 of 112

SAP Best Practices


2. Put in the exchange rate type you would like to use for SAP S/4HANA migration. 3. Choose Save.

Result You have maintained the exchange rate types for SAP S/4HANA migration.

Define Source Ledger for Migration of Balances Use In this Customizing activity you define the source ledger (and by doing so the source database table) of the balances for General Ledger Accounting.

Procedure 1. Execute the Define Source Ledger for Migration of Balances IMG activity. 2. Choose New Entries. Customers using new GL can specify one entry per ledger, where source and target ledger are equal. a. Customers using classic GL can specify one entry, where the source ledger is 00, and the leading ledger (usually 0L) is used as the target ledger. b. Customers who have migrated to new GL, can migrate their new GL balance for the fiscal years after migration and classic GL balance for the fiscal years prior to the new GL migration. This requires two entries with different source ledger and starting year. The following example lists two entries if you have migrated from classic to new GL in 2010: Entry 1:  Target Ledger: 0L  Company Code: 0001  From Year: 0001  Source Ledger: 00 Entry 2:  Target Ledger: 0L  Company Code: 0001  From Year: 2010  Source Ledger: 0L 3. Choose Save.

Result You have maintained the Source Ledger for Migration of Balances.

Execute Consistency Check of General Ledger Settings Use In this activity, the Customizing settings for the ledgers are checked.

Procedure Execute the Execute Consistency Check of General Ledger Settings IMG activity.

© SAP SE

Public

Page 77 of 112

SAP Best Practices


Result You should now see Currency conversion settings for ledger / company assignment checked in this client Check passed in the job log.

Activate Business Functions Use In this Customizing activity you activate the business functions that are necessary for migrating to SAP S/4HANA.

Procedure 1. Access the transaction using the following navigation option in order to activate the business functions: Transaction Code

SFW5

2. Choose Continue. 3. Open the ENTERPRISE_BUSINESS_FUNCTIONS folder. 4. Search for   

FIN_GL_CI_1 FIN_GL_CI_2 FIN_GL_CI_3

5. Check Select the checkbox to activate the business function. 6. Choose Activate changes. 7. Choose FIN_GL_CI_1, FIN_GL_CI_2, FIN_GL_CI_3 under Business functions to be switched on. 8. Choose Activate changes. 9. You should see an information Job SFW_ACTIVATE_SF0X was started in the background. 10. Choose OK.

Result Check FIN_GL_CI_1, FIN_GL_CI_2 and FIN_GL_CI_3 in the same session, it should be activated now.

Preparations and Migration of Customizing for Asset Accounting - from Classic Asset Accounting These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package. You follow this chapter if you have been using classic Asset Accounting. If you have been using new Asset Accounting, please follow the next chapter Preparations and Migration of Customizing for Asset Accounting - from New Asset Accounting.

Prepare New Asset Accounting Use These following activates support you in migrating Customizing data; once you have completed these activities, you can activate New Asset Accounting. Migrating transaction data is not possible until activating Asset Accounting is finished; however, the migration of

© SAP SE

Public

Page 78 of 112

SAP Best Practices


transaction data is not a part of these IMG activities. The documents from Asset Accounting are migrated as part of the migration of documents from the general ledger. You must then build the depreciation values of your fixed assets as initial.

Procedure Read the instructions in IMG activity help Prepare New Asset Accounting to get an overview and a comprehensive understanding about the whole new Asset Accounting process.

Migrate Charts of Depreciation Use This activity helps you to migrate the charts of depreciation from classic Asset Accounting to new Asset Accounting.

Procedure 1. 2. 3. 4. 5.

Execute the Migrate Charts of Depreciation IMG activity. Enter all the Chart of Depreciation in the Chart of dep., e.g. * field. Execute the program in a test run. Check the log by choosing Job Log. Correct the errors if there are any, re-run the program as a test run until the log shows no errors. 6. Perform the program in an update run.

Result You should see a Migration is ended for client XXX; for details see job log message. You can also check the job log in the next step Display migration Log.

Display Migration Log Use You can use this activity to display the logs of Migrate Charts of Depreciation during either the test run or the update run.

Procedure Execute Display Migration Log

Result You have checked the log.

Perform Additional Manual Activities Use After the migration of the charts of depreciation, you have to make some additional Customizing settings before you can check and activate new Asset Accounting.

Procedure Please follow the instructions in the IMG activity help Perform Additional Manual Activities to perform the additional manual activities.

Result Finish all the mandatory manual activities before you proceed.

© SAP SE

Public

Page 79 of 112

SAP Best Practices


Check Prerequisites for Activating Asset Accounting (New) Use If the check is positive, activate new Asset Accounting in the next activity Activate New Asset Accounting (New).

Procedure 1. Execute the Check Prerequisites for Activating Asset Accounting (New) IMG activity 2. On the Check of Prerequisites for Parallel Valuation in FI-AA (New) screen, select the check before import Activation Check Before Import of Customizing Switch, and execute.

Result The system log should show the Check passed message.

Activate Asset Accounting (New) Use In this activity you activate new Asset Accounting.

Procedure 1. Execute Activate Asset Accounting (New) 2. In the Change View New Asset Accounting: Activation Details screen, choose Activate. 3. Choose Save.

Result You should see the Data was saved message.

Preparations and Migration of Customizing for Asset Accounting - from New Asset Accounting These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package. You follow this chapter if you have been using new Asset Accounting. If you have been using classic Asset Accounting, please follow the chapter Preparations and Migration of Customizing for Asset Accounting from Classic Asset Accounting.

Info: Adjustments in New Asset Accounting Use The following activities are relevant for you if you are already using new Asset Accounting. One of the following scenarios is applicable: 

You are using new Asset Accounting.



You are already using SAP Simple Finance, on-premise edition 1503 with new Asset Accounting.

© SAP SE

Public

Page 80 of 112

SAP Best Practices


Procedure Read the IMG activity help Info: Adjustments in New Asset Accounting to get informed about the new Asset Accounting adjustment.

Adjust Parameters in Chart of Depreciation Use This activity supports you in adjusting the parameters for charts of depreciation.

Procedure 1. 2. 3. 4. 5.

Execute the Adjust Parameters in Chart of Depreciation IMG activity. Enter all the Chart of Depreciation in the Chart of dep., e.g. * field. Execute the program in a test run. Check the log by choosing Job Log. Correct the errors if there is any, re-run the program as a test run until the log shows no errors. 6. Perform the program in an update run. You have to adjust the charts of depreciation manually in the following cases: 

The parameters of your chart of depreciation could not be adjusted automatically because the starting situation defined in your system is not recognized by the program.



You have charts of depreciation in your system that are assigned to a deactivated company code. This means they are assigned to a company code that only allows subsequent reporting. The data of this deactivated company code is still not archived; it must be migrated with the document migration. You must therefore definitely migrate this chart of depreciation manually.

Result Use the next activity Display Migration Log to check the log.

Display Migration Log Use You can use this activity to display the logs of the Adjust Parameters in Chart of Depreciation during either the test run or the update run.

Procedure Execute Display Migration Log.

Result You have checked the log.

© SAP SE

Public

Page 81 of 112

SAP Best Practices


Preparations and Migration of Customizing for Controlling These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Execute BW-Delta Extraction for Account-Based COPA Use You should have done it in Period-end closing and prepare for cut-over. Execute a delta extraction in SAP Business Information Warehouse for those account-based CO-PA data sources for which you use the delta procedure.


RSA7

2. Check the BW Delta Queue Maintenance screen in the ERP system and/ or BW system. In case there are entries in the delta queue, execute the respective InfoPackages and upload the data into the BW system until there are no entries in the delta queue.

Result The BW-Delta Extraction must be finished before you proceed.

Adapt Settings for Profitability Segment Characteristics Use In this activity you adapt the settings for profitability segment characteristics made in classic CO-PA with transaction KEQ3. In SAP S/4HANA Financials each profitability segment contains all available characteristics by default, the summarization function is no longer valid/available in SAP S/4HANA Financials.

Procedure 1. 2. 3. 4.

Execute the Adapt Settings for Profitability Segment Characteristics IMG activity. Execute the program in Test Run. You should not see errors in the log. Execute the program in update run.

Result You should see in job logs only information (in green) and no errors (in red).

Maintain Operating Concern Use In this activity you can activate your operating concerns for account-based profitability analysis. You need to activate the data structures and generate the environment even if you continue using only costing-based CO-PA.

© SAP SE

Public

Page 82 of 112

SAP Best Practices


If you have banking add-on, execute Maintain Operating Concern for Banking Add-On instead.

Procedure 1. Execute the Maintain Operating Concern IMG activity. 2. Enter your operating concern. 3. On the Data Structure tab, select Account-based, if you want to activate the Accountbased CO-PA. Otherwise do not change anything. 4. On the Environment tab, activate the operating concern for the Cross-client part and the Client-specific part.

Result You must activate all the operating concerns before you proceed.

Maintain Operating Concern for Banking Add-On Use In this activity you maintain your operating concerns for the banking add-on. If you do NOT have banking add-on, execute the Maintain Operating Concern IMG activity instead.

Procedure 1. Execute the Maintain Operating Concern for Banking Add-on IMG activity. 2. Enter your operating concern. 3. On the Data Structure tab, select Account-based, if you want to activate the Accountbased CO-PA. Otherwise do not change anything. 4. On the Environment tab, activate the operating concern for the Cross-client part and the Client-specific part.


Activate Account-Based Profitability Analysis Use In this activity you activate account-based profitability analysis for your operating concerns.

Procedure 1. Execute the Activate Account-Based Profitability Analysis IMG activity. 2. Select for each controlling area in field Active Status the type of CO-PA you want to activate. 3. Choose Save.


Transport Operating Concern Use In this activity you transport the definition of your operating concerns. This is only relevant when you want to transport e.g. from Development System to Quality Assurance System. The configurations from the last step Maintain Operating Concern or Maintain Operating Concern for Banking Add-On will be transported to the downstream system. © SAP SE

Public

Page 83 of 112

SAP Best Practices



Execute the Transport Operating Concern IMG activity. Choose Operating concern. Choose Execute. Choose Customizing Request and Workbench Request

5. 6. 7. 8.

Choose continue (ENTER). In Select Object window, click on the line you want to transport Choose Execute in Backgroud. In the Choose Dependent Object Classes pop-up window, select all the lines, then choose , (ENTER). 9. In the Start Time pop-up window, choose Immediate. 10.

Save your entry.

Result You have transported the changes to operating concern to the downstream systems.

Preparations and Migration of Customizing for Material Ledger These activities are relevant for all 3 conversion scenarios covered by this Best Practices package.

Use In this Customizing activity, you migrate the Customizing settings pertaining to the Material Ledger. Perform this activity after the following IMG activities under Migration from SAP ERP to SAP Accounting powered by SAP HANA - Preparations and Migration of Customizing have been successfully completed: • Check Customizing Settings Prior to Migration • Define Message Types for Posting Before and During Migration • Preparations and Migration of Customizing for General Ledger • Preparations and Migration of Customizing for Asset Accounting • Preparations and Migration of Customizing for Controlling


Execute the Migrate Material Ledger Customizing IMG activity. First execute the program as a test run (select Test mode). Correct the errors before continuing. Execute in update mode (deselect Test mode).


Preparations and Migration of House Bank Accounts These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

© SAP SE

Public

Page 84 of 112

SAP Best Practices


Define Number Ranges for Bank Account Technical IDs Use In this Customizing activity you create number range intervals for bank account technical IDs.

Procedure 1. 2. 3. 4. 5.

Execute the Define Number Ranges for Bank Account Technical IDs IMG activity. Choose Intervals. On the Maintain Intervals: Account ID screen, choose Insert Line (F6). Enter a number for the interval and specify a number range. Choose Save.

6. Read the information on the pop-up window, and choose

.

Result You should now see a message telling you the changes were saved.

Define Number Ranges for Change Requests Use In this Customizing activity you create number range intervals for change requests used in Bank Account Management.

Procedure 1. 2. 3. 4. 5.

Execute the Define Number Ranges for Change Requests IMG activity. Choose Intervals. In the Maintain Intervals: Account ID screen, choose Insert Line (or F6). Enter a number for the interval and specify a number range. Choose Save.

6. Read the information on the pop-up window, and choose

.

Result You should now see a message telling you the changes were saved.

Define Settings for Bank Account Master Data Use In this Customizing activity you define the basic settings for the bank account master data. Define different types of accounts to suit different business purposes. Account types can be used as an analysis dimension in reporting and planning. This setting is required for the migration of house bank accounts.

Procedure 1. Execute the Define Settings for Bank Account Master Data IMG activity. 2. Double click on folder Bank Account Master Data Setting. a. In the Bank Account Master Data window, assign a number range interval to field Req. No. Range as Number Range of Workflow Change Requests b. Assign a number range interval to field Tech. ID No. Range as Number Range of Bank Account Technical IDs

© SAP SE

Public

Page 85 of 112

SAP Best Practices


3. Double click on folder Account Type Definition. To add a new bank account type, choose New Entries and then specify the following: a. Account Type: Enter a unique type ID no longer than 10 characters. b. Description: Enter a short description for the account type c. Direction: Specify whether the cash flow direction is inflow only, outflow only, or inflow and outflow. d. Attribute: Specifies whether the bank account is an Operating account or a Functional account. Operating accounts are bank accounts that are used for daily business transactions, such as receiving incoming payments and issuing outgoing payments. Functional accounts are bank accounts that are used in other financial activities, such as loan, investment, and fund raising. 4. Double click on Define import methods for bank statements. To add a new import methods for bank statements, choose New Entries and then specify the Import Method ID and Description. 5. Choose Save.


Preparatory Activities and Migration of Customizing for Credit Management This migration step is necessary only if FI-AR-CR Credit Management has been used, as it is not available with SAP S/4HANA. The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).

These activities are relevant for all 3 conversion scenarios covered by this Best Practices package.

Migrate Credit Management Customizing Use In this Customizing activity, you migrate the Customizing settings pertaining to the credit management to the new configuration of credit management.

Procedure Execute the Migrate Credit Management Customizing IMG activity.

Result You should see Credit Management Customizing migrated in the job log.

Define Credit Analyst Group as Business Partner Group Use In this Customizing activity you define a credit analyst group as business partner of the type group.

Procedure 1. Execute the Define Credit Analyst Group as Business Partner Group IMG activity. 2. Choose Create Group to create the Credit Analyst Group. 3. You can enter an ID in the Business Partner field.

© SAP SE

Public

Page 86 of 112

SAP Best Practices


4. Select Grouping for External Number Assignment or Internal Number Assignment. 5. Select the business partner role to be Business Partner (Gen). 6. Enter the corresponding information in the Name, Search Terms, Standard Address, Communication, etc. sindow 7. Choose Save.

Result You should see the Business Partner $ created message.

Define Credit Representative Group as Business Partner Relationship Use In this Customizing activity you define a credit representative group and assign the credit Analyst Group created above to it. The credit Representative group is assigned to each customer in the Business Partner (customer) master record.

Procedure 1. Execute the IMG activity Define Credit Representative Group as Business Partner Relationship. 2. Choose New Entries to create the Credit Representative Group. 3. In the Cred. rep. field enter an up-to-3-digits ID for credit representative group. 4. Enter a credit control Area if needed in field CCAr and the description in field Credit rep. group. Also enter the Credit Analyst Group created in the field Group. 5. Choose Save.


Define Customer Credit Group Use In this Customizing activity you define a customer credit group. The customer credit group is used to classify a customer on the basis of different credit groups. It is assigned to each customer in the Business Partner (customer) master record.

Procedure 1. Execute the Define Customer Credit Group IMG activity. 2. Choose New Entries to create the Customer Credit Group. 3. Enter an up-to-4-digits number as the customer credit group ID in the Credit Group field. Enter the description in the Name of Credit Group field.


© SAP SE

Public

Page 87 of 112

SAP Best Practices


Assign Credit Management Group to Customer Credit Group Use In this step, you define groups per credit control area depending on your requirements and then you assign each customer to one of these groups in the application menu for the credit management master data.

Procedure 1. Execute the Assign Credit Management Group to Customer Credit Group IMG activity. 2. Choose New Entries to create the credit management group. 3. Enter an up-to-4-digits ID for credit management group in the Cred field. 4. Enter the credit control Area if needed in the CCAr field, and the description for the credit management Group in the Group field. 5. Enter the Customer Credit Group in the Cr. Group field. 6. Choose Save.

Result You should now see the Data was saved message.

Assign Credit Management Processor to Credit Analyst Group Use In this step, you assign employees to a credit analyst group.

Procedure 1. Execute the Assign Credit Management Processor to Credit Analyst Group IMG activity. 2. Enter the relationship category UKMSBG and execute. 3. Enter in field Partner 1 the Business Partner of the Credit Analyst Group and in the Partner 2 field the Business Partner of the employees of the credit analyst group. 4. Choose Save.

Result You should see the Relationships were created message.

Check and Define Credit Management Customizing Use In this activity you check and define the necessary settings in Credit Management Customizing. When SAP Credit Management is active, Value 'A', 'B' and 'C' to define the credit limit check for sales document types is not supported: 'A' (execute credit limit check and warning) 'B' (execute credit limit check and error) 'C' (execute credit limit check and delivery block) Change these values to value 'D' (Credit Management: Automatic credit control) and assign a credit group accordingly.

© SAP SE

Public

Page 88 of 112

SAP Best Practices


Procedure 1. In the SAP Reference IMG (transaction SPRO), choose Financial Supply Chain Management → Credit Management →Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Sales Documents and Delivery Documents. 2. Select Credit limit check for order types. a. Identify the sales document type for which the credit check is required. b. Replace value A, B, or C with D or BLANK if applicable, or enter value D in the Check Credit field. c. Update Credit group with the wished value. d. Choose Save. 3. Select Credit limit check for Delivery types. a. Identify the delivery type for which the credit check is required. b. Choose the wished Delivery Credit Group in the Dlv. credit group field. c. Choose the wished Goods issue credit group in the GI credit group field. d. Choose Save.


Define Settings for Credit Management Migration Use In this activity, you define target values for credit management that are customer-specific. These are, for example, the business partner role or the credit limit rule. The settings you make here are needed for the migration of the credit management master data.

Procedure 1. Execute the Define Settings for Credit Management Migration Access IMG activity to create the variant. 2. Leave the following values as default: BP Role as UKM000 SAP Credit Management, Rules as MIG Migration, Credit check Rule as 01 Default, Text Object as UKM_01 Texts for Credit Management, Commitment types of FI/AR as 200 Open Invoices and Commitment types of SD as 100 Open Orders. 3. Choose Back. 4. In the Maint. Variant MIGRATION pop-up window, choose Yes to confirm Leave value maintenance: Save values? 5. In the Variant Attributes screen, enter a description. 6. Choose Save.

Result You should see the Variant $ saved message in the footnote.

Check Customizing Settings Use When you execute this activity, it checks, whether the credit management Customizing is set up correctly for the migration.

© SAP SE

Public

Page 89 of 112

SAP Best Practices


Procedure Execute the Check Customizing Settings IMG activity.


9.3 Migration Partitioning of Universal Journal Entry Line Items Table Use 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.

Procedure 1. Run a test SAP S/4HANA system conversion on a copy of the productive system in order to determine the resulting number of records in the ACDOCA table. 2. Partition ACDOCA only if you expect more than 500m records. You must partition the table if you expect to reach 2bn records. SAP recommends 300m to 500m records as partition size. Consult the administration guide for more details. 3. For HDB versions lower than SPS09 only hash partitioning is available for ACDOCA (range partitioning is already used up by aging). Use the field BELNR (Document Number) as a partitioning criterion. 4. Starting with SPS09 a range-range partitioning is available, which allows for a range partitioning for example by company code (field RBUKRS). The proper selection of the right partitioning field largely depends on the data distribution and on the patterns of frequent selects, which are highly individual.

Regenerate CDS Views and Field Mapping Use You use this Customizing activity to do the following: 

Regenerate the compatibility and data migration views to adapt them to the configuration of customer-specific entities.



Generate the redirection of SELECT-statements from the concerned data base tables to the corresponding compatibility views.



Regenerate the mapping of customer-specific fields in the data migration procedure.

Procedure 1. Execute the Regenerate CDS Views and Field Mapping IMG activity. 2. Choose Display Options, check the documentation of each option by F1 help, and check the wished options if needed. 3. Choose Execute.

Result To check the progress of the program, use transaction SLG1 with sub- object FINS_GENERATE. You should see in job logs only information (in green) and no errors (in red).

© SAP SE

Public

Page 90 of 112

SAP Best Practices


Migration of Cost Elements These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Check Consistency of G/L Accounts and Cost Elements Use In this Customizing activity you check whether the G/L accounts and cost elements are consistent with each other.

Procedure Execute Check Consistency of G/L Accounts and Cost Elements.

Result You should see the Check passed message in green and no messages in red (errors).

Migration of Secondary Cost Elements to Chart of Accounts Use In this Customizing activity you migrate secondary Cost Elements to G/L accounts with account type Secondary Costs.

Procedure 1. Execute the Migrate Secondary Cost Elements to Chart of Accounts IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or Complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Account/Cost Element Merge job FINS_GCM-@date-@Time-@ Number message of Batch Jobs scheduled for immediate execution. Check result in the Display Status of Migration of Cost Elements activity.

Display Status of Migration of Cost Elements Use In this Customizing activity you check the status of the Migration of Secondary Cost Elements to Chart of Accounts.

Procedure 1. Execute Display Status of Migration of Cost Elements. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat the Migration of Cost Elements.

© SAP SE

Public

Page 91 of 112

SAP Best Practices


Result You have finished the Migration of Cost Elements.

Migrate Default Account Assignments Use In this activity you transfer the default assignments from the master data table CSKB to the Customizing table TKA3A. After the migration the results can be checked via transaction OKB9.

Procedure 1. Execute the Migrate Default Account Assignments IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or Complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Default Acc. Assignment job FINS_DAA-@date-@Time-@ Number of Batch Jobs message scheduled for immediate execution Check result in activity Display Status of Migration of Default Account Assignments.

Display Status of Migration of Default Account Assignments Use In this Customizing activity you check the status of Migrate Default Account Assignments.

Procedure 1. Execute the Display Status of Migration of Default Account Assignments IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat the Default Account Assignments.

Result You have finished the Default Account Assignments.

Adopt Authorizations Use In this activity you can adopt authorization to create or change cost element master data or an authorization to create or change G/L accounts.

Procedure To check or change the authorizations, use transaction PFCG.

Result The authorization has been adopted according to your business operation needs.

© SAP SE

Public

Page 92 of 112

SAP Best Practices


Define Authorizations and Profiles Use In this Customizing activity you can create activity groups.

Procedure 1. Execute the Define Authorizations and Profiles IMG activity. 2. Enter the name of the role to be created e.g. ZSAP_AP Supervisor etc. and choose Single Role to create it. 3. In the Description field, enter a description of the function the activity group is to perform. 4. On the Menu tab, assign transactions to the activity group. 5. On the Authorizations tab, choose Change authorization data. 6. On the User tab, assign users to the activity group. 7. If you want to transport the activity group into another system, you now need to enter the activity group in a transport request. To do so, choose Activity group → Transport. You can now specify whether the user assignment should also be transported.

Result The roles are successfully created and transported.

Technical Check of Transaction Data These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Analyze Transactional Data Use In this Customizing activity you analyze if all transactional data is complete and correct.

Procedure 1. Execute the Analyze Transactional Data IMG activity 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or Complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should now see the Analysis job FINS_R20-@Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status of the analysis in the Display Status of Analysis of Transaction Data activity.

Display Status of Analysis of Transaction Data Use In this Customizing activity you display the status of the Analyze transactional data.

© SAP SE

Public

Page 93 of 112

SAP Best Practices


Procedure 1. Execute Display Status of Analysis of Transaction Data. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Analysis of Transaction Data.

Result You have finished the Analysis of Transaction Data.

Reconcile Transactional Data Use In this Customizing activity of the migration to the SAP S/4HANA Finance you check that the FI documents are consistent and ready to be migrated.

Procedure 1. Execute the Reconcile Transactional Data IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Reconciliation job FINS_R21@Date- @Time --- @Number of Batch scheduled for immediate execution message. Check the status in the Display Status of Technical Reconciliation of Transactional Data Customizing activity.

Display Status of Technical Reconciliation of Transactional Use In this Customizing activity you display the status of the technical reconciliation of transactional data.

Procedure 1. Execute the Status of Technical Reconciliation of Transactional IMG activity Display. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Technical Reconciliation of Transactional.

Result You have finished Technical Reconciliation of Transactional.

Material Ledger Migration Migrate Material Ledger Use This activity activates the material ledger for all valuation areas. This creates material ledger master data and converts inventory values and material prices into the material ledger

© SAP SE

Public

Page 94 of 112

SAP Best Practices


currencies (local, group, and an additional currency). In addition, production and purchase order history entries are converted into group currency and an additional currency. If the material ledger is already active in the source system for all valuation areas, postmigration takes place. In post-migration, missing history table entries (tables: EBEWH, MBEWH, QBEWH and OBEWH) are migrated to the material ledger, and any material ledger inconsistencies are resolved.

Procedure 1. Execute the Migrate Material Ledger IMG activity. 2. In the S/4HANA Material Ledger Migration Mode&Plant Selection window, select all valuation areas by entering an asterisk (*) in the field Plant. 3. In the Processing Options window, select the options as you wish. 4. For test purposes, you may run the program in test mode by selecting Test run. 5. Choose Execute.

Result You should see in the footnote Plant $ can be set to productive for the material ledger in test mode; or The material ledger can be reconciled with FI in valuation area $ in update mode. You can also see the migration status with the Display Status of Material Ledger Migration activity.

Display Status of Material Ledger Migration Use This activity allows you to check the current status of material ledger migration if you executed the Migrate Material Ledger activity in the background.

Procedure 1. Execute the IMG activity Display Status of material Ledger Migration transaction. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat material Ledger Migration.

Result You have finished material Ledger Migration.

Check Migration of Material Ledger Use This activity checks whether the material ledger is active in all valuation areas and performs various technical checks.

Procedure 1. Execute the Check Migration of Material Ledger IMG activity. 2. Background processing is recommended. Choose Program → Execute in Background.

Result Check the status in the Display Status of Material Ledger Migration Check activity.

© SAP SE

Public

Page 95 of 112

SAP Best Practices


Display Status of Material Ledger Migration Check Use This activity displays the results of the Check Migration of Material Ledger activity.

Procedure 1. Execute the Display Status of Material Ledger Migration Check IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Material Ledger Migration Check.

Result You have finished the Material Ledger Migration Check.

Migration – Enrichment of Data These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Enrich Transactional Data Use In this Customizing activity, you enrich transaction data and documents and migrate them to SAP S/4HANA Financials.

Procedure 1. Execute the Enrich Transactional Data IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see Enrich acc. document job FINS_ENR- @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution. Check the status in the Display Status of Enrichment of Transactional Data activity.

Display Status of Enrichment of Transactional Data Use In this Customizing activity, you can display the status of the enrichment of transactional data for SAP S/4HANA Financials.

Procedure 1. Execute the Display Status of Enrichment of Transactional Data IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Enrichment of Transactional Data.

Result You have finished Enrichment of Transactional Data. © SAP SE

Public

Page 96 of 112

SAP Best Practices


Check of Migrated Documents Use In this Customizing activity you check if all documents are enriched correctly.

Procedure 1. Execute the Check of Migrated Documents IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Reconciliation job FINS_R22 - @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Check of Migrated Documents activity.

Display Status of Check of Migrated Documents Use In this Customizing activity you display the status of the check of the documents migration.

Procedure 1. Execute the Display Status of Check of Migrated Documents IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Check of Migrated Documents.

Result You have finished Check of Migrated Documents.

Migration of Line Items into New Data Structure These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Migrate Accounting Documents to Universal Journal Entry Structure Use In this Customizing activity you migrate accounting documents to the universal journal entry structure. The migration of the transactional data to the SAP S/4HANA Finance is a prerequisite for productive use. It populates the entries in of the universal journal entry (UJE) by combining the transactional data of the applications FI, FI-GL, CO and FI-AA.

© SAP SE

Public

Page 97 of 112

SAP Best Practices


Additionally, the characteristics of account-based CO-PA are added to UJE items which are assigned to a profitability segment.

Procedure 1. Execute the Migrate Accounting Documents to Universal Journal Entry Structure IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see Line Item Migration job - @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution. Check the status in the Display Status of Document Migration to Universal Journal Entry activity.

Display Status of Document Migration to Universal Journal Entry Use In this Customizing activity you display the status of the migration of accounting documents.

Procedure 1. Execute Display Status of Document Migration to Universal Journal Entry. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Check of Migrated Documents.

Result You have finished Check of Migrated Documents.

Check Migration of Accounting Documents to Universal Journal Entry Use In this Customizing activity you check if all accounting documents have been migrated correctly.

Procedure 1. Execute the Check Migration of Accounting Documents to Universal Journal Entry IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

© SAP SE

Public

Page 98 of 112

SAP Best Practices


Result You should see Reconciliation job FINS_R23- @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution Check the status in the Display Status of Check of Accounting Document Migration activity.

Display Status of Check of Accounting Document Migration Use In this Customizing activity you display the status of the migration of accounting documents to universal journal entry.

Procedure 1. Execute the Display Status of Check of Accounting Document Migration IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Check of Accounting Document Migration.

Result You have finished Check of Accounting Document Migration.

Migrate General Ledger Allocations Use In this activity, you change existing G/L allocation cycles for actual values to new journal entry database tables. More specifically, all G/L allocation cycles that refer to the FlexGL sum table FAGLFLEXT are changed to refer to the new ACDOCT view. In addition, all field usage definitions for fields of FAGLFLEXT are copied to new entries for the same fields of ACDOCT.

Procedure 1. Execute the Migrate General Ledger Allocations IMG activity. 2. In the Migration of G/L allocations to journal entry tables window do not change the default variant. If a large number of records are to be migrated, it is advisable to execute the report in the background. You can also restrict the operation to a set of individual ledgers. 3. Choose Execute. 4. Analyze the messages, resolve any errors, and consider the warnings. 5. Once any problems have been resolved, run the program again in update mode (deactivate the test run checkbox).


Check Migrated General Ledger Allocations Use In this activity, you check whether the existing G/L allocation cycles are successfully migrated.

Procedure 1. Access the transaction using the following navigation option:

© SAP SE

Public

Page 99 of 112

SAP Best Practices


Transaction Code

SE38

Report

RGALLOC4

or Transaction Code

GCA9 2. On the Check Customizing settings for the allocation screen, do not change the ACDOCA table name. Select the radio buttons according to your usage. 3. Choose Execute.

Result You should see The Customizing settings for allocation are formally correct message in the footnote.

Migration of Balance These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Migrate Balances Use In this Customizing activity you migrate balances.

Procedure 1. Execute the Migration of Balance IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see Migration (Balances) job FINS_DLT @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution. Check the status in the Display Status of Migration of Balances activity.

Display Status of Migration of Balances Use In this Customizing activity you display the status of the migration of balances.

Procedure 1. Execute the Display Status of Migration of Balances IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Migration of Balances.

Result You have finished Migration of Balances.

© SAP SE 112

Public

Page 100 of

SAP Best Practices


Check Migration of Balances Use In this Customizing activity you check if all balances have been migrated correctly.

Procedure 1. Execute the Check Migration of Balances IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see Reconciliation job FINS_R24-@Date- @Time --- @Number of Batch Jobs scheduled for immediate execution. Check the status in the activity Display Status of Check of Migration of Balances.

Display Status of Check of Migration of Balances Use In this Customizing activity you display the status of the migration of balances.

Procedure 1. Execute Display Status of Check of Migration of Balances. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Migration of Balances.

Result You have finished Migration of Balances.

Migration - Calculation of Depreciation and Total Values These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Calculate Initial Depreciation Values Use The determination of the cumulative depreciation of an asset and the posting of depreciation expense takes place in the system at different points in time: 1. The planned depreciation is determined with each master record change and with each posting on the asset and updated in the database accordingly. 2. The depreciation run adopts the planned asset values and posts them in Financial Accounting. The posting document is updated in Financial Accounting at asset level. You use this activity to initially build the planned depreciation values for Asset Accounting.

© SAP SE 112

Public

Page 101 of

SAP Best Practices


This activity is based on program Calculate Depreciation. You execute this activity after you have migrated the transaction data. However, if you have difficulty to do this during business down time due to time and resource restraints, it is possible to defer the execution of this activity to business uptime after the migration is complete. However you must ensure that the activity has been executed before the first depreciation at the latest.

Procedure 1. Execute the Calculate Initial Depreciation Values IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see Initial Depr. Calc. job FINS_AFA- @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution Check the status in the Display Status of Calculate Initial Depreciation Values activity.

Display Status of "Calculate Initial Depreciation Values" Use With this activity you display the status for the calculation of initial depreciation values.

Procedure 1. Execute Display Status of Calculate Initial Depreciation Values. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Calculate Initial Depreciation Values.

Result You have finished Calculate Initial Depreciation Values.

Check Initial Depreciation Values and Total Values Use In this Customizing activity, you once again reconcile the total values and the depreciation values.

Procedure 1. Execute the Check Initial Depreciation Values and Total Values IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

© SAP SE 112

Public

Page 102 of

SAP Best Practices


Result You should see Reconciliation job FINS_R25- @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution.Check the status in the Display Status of Check Initial Deprec. Values and Total Values activity.

Display Status of "Check Initial Depreciation Values and Total Values" Use With this activity you display the status for the check on the initial depreciation values and total values.

Procedure 1. Execute the Display Status of Check Initial Depreciation Values and Total Values IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Calculate Initial Depreciation Values.

Result You have finished Calculate Initial Depreciation Values.

Migration of House Banks Accounts These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Use In this Customizing activity you migrate existing house bank account data to the bank account master data in Bank Account Management.

Procedure 1. Execute the Migrate House Banks Accounts IMG activity. 2. Specify a date in the Opened On field. 3. Select the house bank accounts that you want to migrate and fill in an account type in field Type for the entry. 4. Click Execute.

Result The system generates bank accounts based on selected house bank accounts. You can check the migration status by checking the status icon displayed at the end of each house bank account entry: 

Green

The house bank account entry is linked to a bank account master record, and the house bank is assigned to the bank account in the master record.

The bank account master records created can be with the status of inactive. This is often caused by issues such as missing bank account numbers or duplicate records. You should always check the generated bank account master records and manually correct the data before you use the accounts in operation activities. © SAP SE 112

Public

Page 103 of

SAP Best Practices




Yellow

The house bank accounts have been migrated to or created in Bank Account Management in an earlier version of SAP Cash Management powered by SAP HANA. You need to execute the program again to update the data. 

Red

The house bank account entry is not yet linked to a bank account master record. If the status of a house bank account remains as red after you have executed the program for it, you can check the migration log for more information. To access the log, in transaction SLG1, specify object BAM_MIGRATE. Migrate House Bank Accounts (Optional) Some information cannot be created by the program automatically, since it is not stored with house bank accounts. Execute the following steps to migrate the wanted information.

Procedure 1. Access the transaction using the following navigation option: Transaction Code NWBC 2. You can manually maintain the following attributes for each bank account individually, or use the Import and Export Bank Accounts tool to massively import data from an XML file:     

General data: unspecified fields, such as bank statement data, payment data, contact persons, and so on. Payment signatories Overdraft limits Additional data Connectivity path: linkages to account records in remote systems

Result You have successfully maintained the additional information for house bank accounts.

Credit Management Migration Migrate Credit Management Master Data Use In this Customizing activity, the master data from Credit Management in Accounts Receivable (FI-AR) are migrated to SAP Credit Management in Financial Supply Chain Management (FIN-FSCM-CR). The credit limit, the credit representative group, the credit customer group and the text fields are migrated.

Procedure 1. Execute the Migrate Credit Management Master Data IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors.

© SAP SE 112

Public

Page 104 of

SAP Best Practices


3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Migration job FINS_MK1 - @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Migration of Credit Management Master Data activity.

Display Status of Migration of Credit Management Master Data Use In this Customizing activity you check the status of the migration of credit management master data.

Procedure 1. Execute the Display Status of Migration of Credit Management Master Data IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Migration of Credit Management Master Data.

Result You have finished Migration of Credit Management Master Data.

Migrate Credit Management Exposure Use In this Customizing activity, the following are migrated.  

Credit values of open orders and deliveries are migrated to the credit exposure. Payment behavior data from credit management in Accounts Receivable (FI-AR) are migrated.

Procedure 1. 2.

Execute the Migrate Credit Management Exposure IMG activity. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Migration job FINS_MK2 - @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Credit Management Exposure Migration activity.

© SAP SE 112

Public

Page 105 of

SAP Best Practices


Display Status of Credit Management Exposure Migration Use In this Customizing activity you check the status of the migration of commitments and payment behavior.

Procedure 1. Execute the Display Status of Credit Management Exposure Migration IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Credit Management Exposure Migration.

Result You have finished Credit Management Exposure Migration.

Initialize Documented Credit Decision Use In SAP Simple Finance, 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.

Procedure 1. 2.

Execute the Initialize Documented Credit Decision IMG activity. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Migration job FINS_MK3 - @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Initialization of Documented Credit Decisions activity.

Display Status of Initialization of Documented Credit Decisions Use In this Customizing activity you check the status of the migration of documents blocked by credit management.

Procedure 1. Execute the Display Status of Initialization of Documented Credit Decisions IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Initialization of Documented Credit Decisions.

© SAP SE 112

Public

Page 106 of

SAP Best Practices


Result You have finished Initialization of Documented Credit Decisions.

Reconcile Documented Credit Decisions Use In this Customizing activity you can reconcile that for each credit blocked document a documented credit decision exists.

Procedure 1. Execute the Reconcile Documented Credit Decisions IMG activity. 2. You can leave the Show missing cases only checkbox selected, or deselect it if wished. 3. Choose Execute.

Result You should see in the job log $ Blocked Documents, which should match with the number of blocked sales documents before migration.

Complete Migration These activities are relevant for all 3 conversion scenarios covered by this Best Practices package.

Reconcile and Compare Data - After System Conversion Use Perform the important reports to compare with the result before the migration. You do it to ensure that the migration has been performed successfully and correctly.

Procedure Perform the reports mentioned in Reconcile and Compare Data - Before System Conversion. Compare the result with the same report performed before system conversion.

Result The same report should show the same result.

Set Migration to Completed Use In this Customizing activity you set the migration to complete. If you do not set the migration to completed users are not able to make postings in the system and receive the message that you defined in the Define Message Types for Posting Before and During Migration Customizing activity. If you set the migration to completed, users are allowed again to make postings in the system.

© SAP SE 112

Public

Page 107 of

SAP Best Practices


Procedure 1. Execute the Set Migration to Completed IMG activity. 2. In the Confirmation Do you really want to set the data migration to status “Completed”? pop-up window, choose Yes.

Result You should see the Data migration has been set to status “Finished” message in the footnote.

9.4 Activities after Migration These activities are relevant for conversion scenarios 1 and 2 covered by this Best Practices package.

Transfer Application Indexes Use In this customizing activity, you can transfer application indexes to the database cold area in order to reduce main memory consumption. The migration step is optional.

Procedure 1. Execute the Transfer Application Indexes IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should now see the Migration job FINS_CLD- @Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Transfer of Application Indexes activity.

Display Status of Transfer of Application Indexes Use In this Customizing activity, you can display the status of the transfer of application indexes to the database cold area.

Procedure 1. Execute Display Status of Transfer of Application Indexes. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Transfer of Application Indexes.

Result You have finished Transfer of Application Indexes. © SAP SE 112

Public

Page 108 of

SAP Best Practices


Fill Due Dates in FI Documents Use You use this Customizing activity to fill the new due date fields in the FI line items for customers and vendors and for G/L account line items that have a base line date.

Procedure 1. Execute the Fill Due Dates in FI Documents IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

Result You should see the Migration job FINS_DUE-@Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Filling in Due Dates into FI Documents activity.

Display Status of Filling in Due Dates into FI Documents Use In this Customizing activity you display the status of filling in the due dates into FI documents.

Procedure 1. Execute the Display Status of Filling in Due Dates into FI Document IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Filling in Due Dates into FI Document.

Result You have finished Filling in Due Dates into FI Document.

Fill the Offsetting Account in FI Documents Use You use this Customizing activity to fill the offsetting account in FI documents.

Procedure 1. Execute the Fill the Offsetting Account in FI Documents IMG activity. 2. In the Mass Data Run window, you see either Start first run, if it the first time you start the job; or you see complete the first run, if you have started the job before, but did not finish without errors. 3. In the Batch Job Control window, fill in a Number of batch jobs considering your system resource. 4. Choose Execute.

© SAP SE 112

Public

Page 109 of

SAP Best Practices


Result You should see the Offsetting Account job FINS_GKO-@Date- @Time --- @Number of Batch Jobs scheduled for immediate execution message. Check the status in the Display Status of Filling the Offsetting Account in FI Documents activity.

Display Status of Filling the Offsetting Account in FI Documents Use In this Customizing activity you display the status of filling in the due dates into FI documents.

Procedure 1. Execute the Display Status of Filling the Offsetting Account in FI Documents IMG activity. 2. You should see all the packages in green and no messages in red (errors). In case of errors (red messages), fix the issue and repeat Filling the Offsetting Account in FI Documents.

Result You have finished Filling the Offsetting Account in FI Documents.

Convert to SAP Cash Management You can only do the activities in this chapter after finishing the SAP S/4HANA Financials conversion. You only need to execute the activities in this chapter if you have been using Classic Cash Management.

Migrate House Bank Accounts Use House bank accounts are completely merged into Bank Account Management (BAM) as master data in SAP Cash Management. Customers who are using SAP S/4HANA Finance (without the SAP Cash Management license) may use Bank Account Management Lite (which does not require separate license) for functions related to house bank and house bank account.

Procedure 1. Migrating existing house bank accounts into BAM accounts has been covered by chapter Migrate House Bank Account. 2. To use Bank Account Management Lite, make sure you have applied the SAP Notes in the Release Information Note 2261518 UDO report for the note 2260584.

Result House bank accounts originally stored in database table T012K are migrated to table FCLM_BAM_ACLINK2. After the migration, you can use the house bank accounts as usual.

© SAP SE 112

Public

Page 110 of

SAP Best Practices


Activate Business Functions FIN_FSCM_CLM Use In this Customizing activity you activate the business function that is necessary for migrating to SAP Cash Management.

Procedure 1. Access the transaction using the following navigation option in order to activate the business functions: Transaction Code

SFW5

2. 3. 4. 5. 6. 7. 8. 9.

Choose Continue. Open the ENTERPRISE_BUSINESS_FUNCTIONS folder. Search for FIN_FSCM_CLM. Check on select the checkbox to activate the business function. Choose Activate changes. Choose FIN_FSCM_CLM under Business functions to be switched on. Choose Activate changes. You should see an information Job SFW_ACTIVATE_SF0X was started in the background. 10. Choose OK.

Result Check FIN_FSCM_CLM in the same transaction, it should be activated now.

Necessary Configurations - Migrate from the Classic SAP Liquidity Planner Use The following should be considered if you migrate from the classic SAP Liquidity Planner to the new SAP Cash Management:    

From actual/info accounts to flow types Liquidity items and Liquidity Item Hierarchies Liquidity item derivation Exit function and other extensions

Procedure Please refer to the following SAP Notes to adapt your current settings:  

2233404 Configuration Guide for SAP Cash Management (SAP S/4HANA, onpremise edition 1511) 2233405 Data Setup Guide for SAP Cash Management (SAP S/4HANA, on-premise edition 1511)

Result You are able to use SAP Cash Management based on SAP S/4HANA.

© SAP SE 112

Public

Page 111 of

SAP Best Practices


9.5 SAP BPC for SAP S/4HANA Finance Reactivate Classic Planning Transactions Use SAP BPC for SAP S/4HANA Finance replaces some planning functions in SAP S/4HANA. If you prefer delaying the activation of SAP BPC for S/4HANA Finance, you can reactivate the classic planning transactions. If you do not want to use SAP BPC for SAP S/4HANA Finance but classic CO-OM planning functions instead, you may apply modifications to reactivate the CO-OM planning transactions. If you cannot immediately convert your entry of G/L planning data and your reporting to BPC for SAP S/4HANA Finance, you can continue to use your G/L planning function for a time in SAP S/4HANA Finance as well via the steps described in SAP Note 2253067 Reactivate G/L planning. The steps also contain modifications. SAP reserves the right to deactivate the old ERP planning function definitively at some point. Additional conditions are: The old G/L planning can really only continue to be used. In other words, planning can be done only for ledgers that already existed in the ERP system (but not, for example, for ledgers that were created after the migration). For example, you can no longer add any new customer fields to your old G/L table. Your existing planned/actual comparisons are restricted to the dimensions that they had before the migration. For instance, they cannot report about dimensions of your choice in the universal journal introduced in SAP S/4HANA Finance. The status is frozen to a certain extent.

Procedure Implement the following SAP Notes to reactivate the classic planning transactions:  2142732 Error messages SFIN_FI 005 and 004: Transactions CJ40, CJ42 cannot be called  2142447 Error message SFIN_FI 005: Transaction KP06, KP07 not usable,  2148356 Error message SFIN_FI 005: Transaction KPF6, KPF7 cannot be used  2135362 Error message SFIN_FI 004: Transactions CJR2 and CJR3 cannot be called. However, please be aware that the former planned integration to P&L planning is not available in SAP S/4HANA 1511.  2253067 Reactivate G/L planning.

Result You can continue using the classic planning transactions to some extent.

Set-Up SAP BPC for SAP S/4HANA Use If SAP BPC for SAP S/4HANA Finance is desired or required (for example, for P&L Planning), then SAP BPC for SAP S/4HANA Finance has to be set up.

Procedure 1.

2.

Refer to SAP Note 1972819 Setup SAP BPC for S/4 HANA Finance and Embedded BW Reporting (aka SAP BPC for S/4 HANA Finance for Finance) to set up SAP BPC for S/4HANA Finance for Finance. Customer roles (menus and authorizations) may need to be adapted.

Result You can use SAP BPC for SAP S/4HANA. © SAP SE 112

Public

Page 112 of

BG5 Application Conversion Guide

Recommend Documents