BH5_S4HANA1611_BPD_EN_XX.docx

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

Test Script SAP S/4HANA - 22-06-17

CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved.

CUSTOMER

1

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

Table of Contents 1

Purpose

3

2

Prerequisites

4

2.1

System Access

4

2.2

Roles

4

2.2.1

Technical Roles

4

2.2.2

Business Roles

5

2.3

Migration Object

6

2.4

Business Conditions

7

2.5

Adding Roles to the Data Migration User

8

2.5.1

Add Catalog Roles

8

2.5.2

Add Business Roles

9

3

Overview Table

10

4

Test Procedures

11

4.1

Download Migration Template

11

4.2

Prepare Test Data

12

4.3

Transfer Migration Template Data

14

4.4

Confirm Imported Data in the SAP S/4HANA System

18

5

Appendix

20

5.1

General Topics and Limitations

20

5.1.1

When to create a new project?

20

5.1.2

Units of Measure

20

5.1.3

Currencies

20

5.2

Financials - General Topics

21

5.2.1

Document Types for Data Migration

21

5.2.2

Document Date

21

5.2.3

Posting Date

21

5.2.4

Value Date

21

5.2.5

Transferring Booking Account

21



2

1 Purpose New SAP customers can take advantage of a template-based migration approach built into SAP S/4HANA with the SAP S/4HANA Migration Cockpit. The SAP S/4HANA cloud packages support a limited set of data migration objects, with support for additional objects planned for later inclusion, following a similar methodology to the available migration to SAP S/4HANA. This document provides a detailed procedure for testing the scope item after solution deployment, reflecting the predefined scope of the solution. Each process step is covered in its own section, providing the system interactions (that is, test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly (see the Test Step column). Customer-project-specific steps must be added.



3

2 Prerequisites This section summarizes all prerequisites to conducting the test in terms of systems, users, master data, organizational data, and other test data and business conditions. Following prerequisites need to be fulfilled and available: ● Access to the SAP S/4HANA on-premise edition system

2.1 System Access The test should be conducted with the following system: System

Details

SAP S/4HANA System

Your system administrator provides you with the system ID and users to access the system.

2.2 Roles 2.2.1 Technical Roles Ask your System Administrator to copy the SAP role templates into your customer’s namespace and assign it to a user that will migrate the data. Purpose

Role

SAP S/4HANA Migration Cockpit

SAP_CA_DMC_MC_USER

SAP S/4HANA Migration Object Modeler

SAP_CA_DMC_MC_DEVELOPER

Name

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

PFCG

SAP Menu

Tools -> Administration -> User Maintenance -> Role Administration -> Roles

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


4

1. In the Role field, enter the name of the role to copy: SAP_CA_DMC_MC_USER. 2. Choose menu path Role -> Copy. 3. In the appearing dialog box Query , enter the name of the role according to your company’s naming convention, for exampleZ_DMC_MC_USERin field to role. 4. Choose tab Copy All. 5. Choose Change 6. Enter the description Role to migrate data using the migration cockpitin the description field. 7. Choose tab Authorizations. 8. Choose Propose Profile Names in section Information About Authorization Profile to generate a profile. Note To do this you need to have sufficient authorization to create a profile: Authorization object: S_USER_PROF Authorization values: ACTVT = 01, 06 1. Choose Change Authorization Data in section Edit Authorization data and Generate Profiles. 2. In the appearing dialog box Save the role , choose Yes to save the role. 3. Read the information box Important and choose ENTER. 4. Choose Save to save the role. 5. Choose menu Authorizations -> Generate to generate the role. Result You have created the role to use the SAP S/4HANA Migration Cockpit.

2.2.2 Business Roles In order to be able to migrate specific business objects, you need to create a data migration user and assign the required technical and business roles to this user. For the required business roles, ask your functional consultant or your system administrator. Procedure 1. Access the transaction Users using one of the following navigation options: Transaction Code

SU01

SAP Menu

Tools -> Administration -> User Maintenance -> Users

1. Enter the name of the User to migrate your data in field User, for example MIGUSER. 2. Choose menu path Users -> Create to create the user. 3. Enter Migration user in field Last name of tab Address. 4. Choose Logon data tab. 5. Select Dialog in the User Type field. Data Migration to S/4HANA from File (BH5) Prerequisites


5

6. Enter the initial password in the field New Password and repeat the password in the field Repeat Password. 7. Choose Roles tab. 8. Enter the name of the role you have created in the previous section Technical Roles , for example Z_DMC_MC_USER. 9. Choose ENTER. 10. Enter the name of the role for your business object in a separate line. 11. Choose ENTER. 12. Choose Save. 13. Log off your system and logon again user the new data migration user and the initial password created in step 7. Result The user to migrate your Business Object is created and has the required authorizations assigned.

2.3 Migration Object The following Migration Objects will be tested using Microsoft Excel XML Spreadsheet 2003. Business Object Name

Area

Business Object Type

Migration Cockpit Object Name

Technical Object Name

Activity Types

CO

Master data

Migration of Activity types (FILE2S4)

SIF_LSTAR_CREATE

Cost Center

CO

Master data

Migration of Cost centers (FILE2S4)

SIF_KOSTL_MASTER

Activity Price

CO

Master data

Migration of Activity prices (FILE2S4)

SIF_ACT_PRICE

Internal Order

CO

Transactional data

Migration of Activity prices (FILE2S4)

SIF_INTORDER

Profit Center

FI

Master data

Migration of Profit centers (FILE2S4)

SIF_PRCTR_MASTER

Bank Master Data

FI

Master data

Migration of Banks (FILE2S4)

SIF_BANK_MASTER

Customer Master

FI, SD

Master data

Migration of Customer (FILE2S4)

SIF_CUSTOMER

Vendor Master

FI, MM-PUR

Master data

Migration of Vendor (FILE2S4)

SIF_VENDOR

Customer Open Items

FI

Transactional data

Migration of Customer open items (FILE2S4)

SIF_AR_OPEN_ITEM

Vendor Open Items

FI

Transactional data

Migration of Vendor open items (FILE2S4)

SIF_AP_OPEN_ITEM

Fixed Asset incl. Balances

FI-AA

Master data + Transactional data

Migration of Fixed assets (FILE2S4)

SIF_FIXED_ASSET

G/L Account Balances

FI

Transactional data

Migration of G/L balances (FILE2S4)

SIF_GL_BALANCES



6

Business Object Name

Area

Business Object Type

Migration Cockpit Object Name

Technical Object Name

G/L Account Open Items

FI

Transactional data

Migration of G/L open items (FILE2S4)

SIF_GL_OPEN_ITEM

Exchange Rate

FI

Master data

Migration of Exchange rates (FILE2S4)

SIF_EXCH_RATE

Inventory Balances

MM-IM

Transactional data

Migration of Material inventory balances (FILE2S4)

SIF_INVENTORYBAL

Material Master

LO-MD

Master data

Migration of Materials (FILE2S4)

SIF_MATERIAL

Material Master

LO-MD

Master data

Migration of Material long texts (FILE2S4)

SIF_MAT_LONGTEXT

Material Master

LO-MD

Master data

Migration of Consumptions (FILE2S4)

SIF_MAT_CONSUMP

Purchasing Info Record

MM-PUR

Master data

Migration of Purchasing info records (FILE2S4)

SIF_PURCH_INFREC

Purchase Order

MM-PUR

Transactional data

Migration of Purchase orders (only open) (FILE2S4)

SIF_PURCH_ORDER

Contracts (Purchasing)

MM-PUR

Transactional data

Migration of Purchasing contracts (FILE2S4)

SIF_CONTRACTS

Source List

MM-PUR

Transactional data

Migration of Source lists (FILE2S4)

SIF_SOURCE_LIST

Sales Order

SD

Transactional data

Migration of sales orders (only open) (FILE2S4)

SIF_SALES_ORDER

Batches

QM, SD, PP-PI

Master data

Migration of Batches (FILE2S4)

SIF_BATCHES

Bill of Material (BOM)

PP

Master data

Migration of Bill of materials (FILE2S4)

SIF_BOM

Work Center

PP, QM

Master data

Migration of Work centers (FILE2S4)

SIF_WORK_CNTR

Routing

PP

Master data

Migration of Routings (FILES4)

SIF_ROUTING

Equipment

PM

Master data

Migration of Equipments (FILE2S4)

SIF_EQUIPMENT

Equipment Task List

PM

Master data

Migration of Equipment task list (FILE2S4)

SIF_EAM_TASKLIST

Functional Location

PM

Master data

Migration of Functional locations (FILE2S4)

SIF_FUNC_LOC

Characteristics

CA

Master data

Migration of Characteristics (FILE2S4)

SIF_CHARACT

Classes

CA

Master data

Migration of Classes (FILE2S4)

SIF_CLASS

2.4 Business Conditions Before this scope item can be tested, the following business conditions must be met: Data Migration to S/4HANA from File (BH5) Prerequisites


7

Business Condition

Comment

1

Best practices content is activated or relevant customizing is finalized your system.

2

Org. structures and additional settings are made on top of the Best Practices content

2.5 Adding Roles to the Data Migration User Use In this step, you set up user settings that are necessary for migrating your data.

2.5.1 Add Catalog Roles Procedure 1. Access the SAP S/4HANA cloud edition Fiori screen. 2. On the Home screen, choose tile Maintain Business Users. 3. Choose the Catalog Role to assign to your data migration user 4. Choose Edit. 5. On the Catalog role details choose, Add User. 6. Enter the User name given by your System Administrator. Field Name

Description

User Action and Values

User Name

Name of the Data Migration user

User name

Comment

7. Choose Go. 8. Select the User in the Users list Choose OK. . 9. Choose Save . 10. Go back to the Previous Screen 11. Repeat steps 3 to 9 per catalog role you need. 12. Go back to the SAP Home screen. Result You have created and added the necessary roles for the specific Data Migration object to load. Data Migration to S/4HANA from File (BH5) Prerequisites


8

2.5.2 Add Business Roles Procedure 1. Access the SAP S/4HANA cloud edition Fiori screen 2. On the Home screen, choose tile Maintain Business Users: 3. Enter the User name given by your System Administrator Field Name

Description

User Action and Values

User Name

Name of the Data Migration user

User name

Comment

4. Choose Go 5. Select the User in the Users list 6. Choose Edit 7. Choose Add Business Roles 8. On Add Business Roles list, fill the needed Business role into the Search field and choose Enter 9. Select the needed Business role(s) and choose OK 10. Choose Save 11. Go back to the SAP Home screen. Result You have created added the necessary roles for the specific Data Migration object to load.



9

3 Overview Table The scope item Data Migration to S/4HANA from File consists of several process steps provided in the table below. Process Step, Report or Item

UI Type

Business Condition

Expected Results

Download Migration Template

Migration Cockpit (Web Dynpro via SAP Fiori launchpad)

This activity is to download a Migration Template to facilitate the data transfer from Microsoft Excel Spreadsheet Templates to SAP S/4HANA.

The Microsoft Excel XML spreadsheet 2003 template has been downloaded.

Prepare Test Data

Microsoft Excel

This activity is to enter the test data to be migrated.

Test data has been entered into Microsoft Excel XML Spreadsheet 2003 template.

Transfer Migration Template Data

Migration Cockpit (Web Dynpro via SAP Fiori launchpad)

This activity is to run the Data Migration in Update Mode with database updates in SAP S/4HANA target system.

The data has been transferred from the Microsoft Excel XML spreadsheet 2003 template to the SAP S/4HANA system.

Confirm Imported Data in the SAP S/4HANA System

SAP

This activity is to check completeness of the migrated data in the target SAP S/4HANA system using corresponding business functions.

All data from the Microsoft Excel XML spreadsheet 2003 template can be found in the corresponding SAP S/4HANA business functions.

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

Fiori launchpad


10

4 Test Procedures This section describes test procedures for each process step that belongs to this scope item. The test should take around 4 hours.

4.1 Download Migration Template Test Administration Customer project: Fill in the project-specific parts.

Test Case ID

Tester Name

Testing Date Enter a test date.

Business Role(s) Responsibility

Duration

Enter a duration.

Purpose In this process step, you download a Migration Template to facilitate the data transfer from Microsoft Excel XML Spreadsheet 2003 templates to SAP S/4HANA. Procedure Test Step #

Test Step Name

Instruction

1

Log on

Log on to your SAP S/4HANA back-end system and start the SAP S/4HANA Migration Cockpit using transaction LTMC

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

User Entries: Field name: Value

Expected Result

Pass / Fail / Comment

The SAP S/4HANA Migration Cockpit appears


11

Test Step #

Test Step Name

Instruction

2

Create Migration Project

Choose Create

3

Add Name

Make the required entry in Create Migration Project dialog window and choose Create.

4

Select Migration Object

On the Migration Objects tab, select the table row containing your Migration Object and choose Open.

Download Template

Choose Download Template. Once the Download dialog appears, choose Save to store the Migration Template on your local PC.

5


Expected Result


The Create Migration Project dialog window appears.

Once the confirm dialog window appears, choose OK to copy the selected Migration Object to your project.

Name: Name of your migration project.

You have created a migration project. The project including all active migration objects is displayed on the screen. The Migration Object has been copied and the Migration Object Details screen appears.

The Migration Template is downloaded and saved on your local PC.

Note Dependent on your Internet Browser and Version a Download dialog appears. If it appears, choose Save to store the Migration Template on your local PC. If it doesn't appear, the Migration Template is automatically stored in your default Download folder. Note Dependent on your internet browser you will have to add the extension .xml to your downloaded file.

4.2 Prepare Test Data Test Administration Customer project: Fill in the project-specific parts.

Test Case ID

Tester Name


Business Role(s) Data Migration to S/4HANA from File (BH5) Test Procedures


12

Responsibility

Duration

Enter a duration.

Purpose With this activity, you enter the test data for migration to SAP S/4HANA into the Migration Template.

Procedure Test Step #

Test Step Name

Instruction

1

Open downloaded Migration Template

Select the Migration Template on your local PC and open it using Microsoft Excel.

2

Enter test data in mandatory sheets manually

Enter your test data in all mandatory sheets of your Migration Template. Fill all mandatory columns at least


Expected Result


Microsoft Excel displays the Migration Template. Caution When copying data into the Migration template, please always use the Paste Option: Values (V). Avoid to paste data including formatting and formulas into the template, this will lead to a corrupted XML file.

The Migration Template contains the data of the mandatory sheets.

Note For more information on field level increase line 8 of the Migration Template to make the additional field description visible.

The Migration Template contains data of sheets, which are not mandatory.

Note For more information on field level increase line 8 of the Migration Template to make the additional field description visible.

Note Mandatory columns are marked with '*'. For further details, read the Appendix below. 3

Enter test data in optional sheets manually

Enter your test data in sheets of your Migration Template, which are not mandatory. Fill all mandatory columns at least Note Mandatory columns are marked with '*'

4

Save

To save the data on your local PC choose Save in the Microsoft Excel application.


The Migration Template containing test data is saved on your local PC. CUSTOMER © 2017 SAP SE or an SAP affiliate company. All rights reserved.

13

Test Step #

Test Step Name

Instruction


5

Close

Choose Close in the Microsoft Excel application.

Expected Result


The Microsoft Excel application is closed.

4.3 Transfer Migration Template Data Test Administration Customer project: Fill in the project-specific parts.

Test Case ID

Tester Name



Duration

Enter a duration.

Purpose In this activity, you will import the data from your Migration Template into the SAP S/4HANA target system.



14


Test Step Name

Instruction


1

Log on

Log on to your SAP S/4HANA back-end system and start the SAP S/4HANA Migration Cockpit using transaction LTMC

The SAP S/4HANA Migration Cockpit page appears.

2

Open Migration Project

Select the table row containing your project in the Available Migration Projects table and choose Open.

The Migration Project Details screen appears.

3

Select Migration Object

Switch to the Migration Objects tab and select the table row containing your Migration Object. Choose Open.

The Migration Object Details screen appears.

4

Upload Migration Template

Choose Upload File.

The File Upload dialog window appears.

5

Open File Browser of your local PC

Choose Browse to select the corresponding Migration Template from your local PC.

The file browser of your local PC appears in a dialog window.

6

Select File

Select your Migration Template from the list and choose Open.

7

Upload

Choose Upload to transfer the data to the Migrate Your Data Web Application.

File Path: path of your migration template on local PC.

Expected Result


The file path of your local file is transferred to the File Path of the File Upload dialog window

Your file appears in the overview list of the Files tab.

Caution Dependent on your internet browser and the browser version, it might be that you receive an error message like this: Error when uploading file ….XML : No virus scan provider available for scanner group DE-



15

Test Step #

Test Step Name

Instruction


Expected Result


FAULT . If this message occurs, you will have to try another browser or update your browser to a newer version. 8

9

10

Activate File for Migration

Select your file from the overview list of the Files tab and choose Activate.

Start Transfer

Choose Start Transfer to migrate the data from your file.

1. Validate Data

Choose Close to close the dialog window when the progress reaches 100%

Your file is active and marked with a green status LED.

Note In case that the overview list contains multiple files that have not yet been finished, select the files and choose Deactivate to avoid reprocessing.

Note A Guided Activity controls the migration process. Execute all work steps one after another

Note You can ignore error messages in regards to value mappings. These errors are fixed in the Convert Values step. Correct all other possible errors. In case that data changes in your source file are required to solve the error, select the file, choose Download and save it on your local PC. After changing the data, repeat activity 4.3 Transfer Migration Template Data once again.

The Guided Activity screen appears in a separate browser window and data validation is in progress. The Validate Data screen is displayed, showing the notifications of the validation run.

11

Navigate to Next Work Step

Choose Next to navigate to the next work step.

The Convert Values screen is displayed, showing a list of all your open tasks. Open tasks are marked with a red LED.

12

2. Convert Values

Select each table row one by another and choose Process Task to maintain your Migration settings.

The maintenance screen of the selected item appears.

13

Provide Values

Enter a new value or confirm the already existing values by choosing the Confirm Value (green hook). Choose Save to continue.

All migration settings are maintained and marked with a green LED. Depending on the Filter set-


Note The applied combination of translation has status AUTO . This message means that the uploaded file contains source data values in fields where a value mapping (translation) rule is assigned. These values are automatically added as new source data values to the translation rule and must be assigned to a correct target value in the Convert Values step.


16

Test Step #

14

Test Step Name

Navigate to next work step

Instruction


Expected Result

Valid / confirmed values are marked with a green LED. Enter a customizing value for Fixed Values and Control Parameters. If available, use Value Help for value selection

tings of the screen, they may disappear. By setting filter to All, all the migration settings are listed again.


The Simulate Import screen is displayed, showing the dialog window with the progress bar of the current-ly active simulation run.


Note In case that the selected migration object does not support simulation run, the Execute Import screen is displayed instead. 15

3. Simulate Report

Choose Close to close the dialog window when the progress reaches 100%. Note Correct all possible errors and choose Repeat Simulation to execute the simulation again. Repeat this process until you solved all errors. In case that data changes in your source file are required to solve the error, select the file, choose Download and save it on your local PC. After changing the data, repeat activity 4.3 Transfer Migration Template Data once again.

The simulation of the data import finished successfully without errors..

16

Navigate to Next work step


The Execute Import screen is displayed, showing the dialog window with the progress bar of the currently active import run

17

4. Execute Import

Choose Close to close the dialog window when the progress reaches 100%.

The data import finished successfully without errors..

Note Correct all possible errors and choose Repeat Import to execute the import again. Repeat this process until you solved all errors.



17

Test Step #

Test Step Name

Instruction


18

Complete the Process

Choose Finish to complete the currently active Guided Activity. Note In case that a new Delta File has been created which needs to be changed, select the file, choose Download and save it on your local PC. After changing the data, repeat activity 4.3 Transfer Migration Template Data once again.

Expected Result


The browser window of the Guided Activity is closed. The Migration Object Details screen appears

4.4 Confirm Imported Data in the SAP S/4HANA System Test Administration Customer project: Fill in the project-specific parts.

Test Case ID

Tester Name



Duration

Enter a duration.

Purpose The purpose of this activity is to check completeness of the migrated data in the target SAP S/4HANA system using corresponding business functions.



18


Test Step Name

Instruction

1

Access corresponding Business Function

Call the corresponding business functioning the SAP S/4HANA system and check completeness of the imported data.



Expected Result


All data from the Microsoft Excel Spreadsheet 2003 Template is displayed in the corresponding SAP S/4HANA transactions.

Note Check the Migration Object documentation for the transaction to validate the data in the system.


19

5 Appendix 5.1 General Topics and Limitations 5.1.1 When to create a new project? We recommend that you create a new project if you encounter one of the following situations: ● You load data for an object from different systems with different value mappings ● You have different files to load for one object with different org. structures For example: Assets that belong to different charts of depreciation cannot be migrated with a single upload file, if the depreciation areas differ. You will have to double-check the mapping of the depreciation areas if the uploaded assets belong to a different chart of depreciation than the one used in the previous upload. This limitation will not be relevant, if you create separate migration projects by company code.

5.1.2 Units of Measure Units of measure must be filled into the Microsoft Excel XML Spreadsheet 2003 in ISO format.

5.1.3 Currencies Currencies must be filled into the Microsoft Excel XML spreadsheet 2003 in ISO format.

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


20

5.2 Financials - General Topics 5.2.1 Document Types for Data Migration The document type for all Open items and Open balances migration objects is UE Data Transfer.

5.2.2 Document Date The document date must be the same date as in the original data record.

5.2.3 Posting Date For all Open items migration objects the posting date should be set to the last day of the previous period.

5.2.4 Value Date The value date must be the same date as in the original data record.

5.2.5 Transferring Booking Account The transfer booking accounts to be used in the Open items and Open balances migration objects are as follows: Account

Description

Migration Object

39913000

Initial FI-AM offset

Fixed Asset

39914000

Initial FI-AR offset

Customer Open Items

39915000

Initial FI-AP offset

Vendor Open Items



21

Account

Description

Migration Object

39916000

Initial other GL offset

G/L account balances

39917000

Initial other Open Item GL offset

G/L account open items



22

Typographic Conventions Type Style

Description

Example

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents.

Example

Emphasized words or expressions.

EXAMPLE

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example

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

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE

Keys on the keyboard, for example, F 2 or E N T E R .



23

www.sap.com/contactsap

© 2017 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.

BH5_S4HANA1611_BPD_EN_XX.docx

Recommend Documents