Test Script SAP S/4HANA April 2016 English SAP S/4 HANA, cloud marketing edition - ERP Data Integration ID: 19Y Table of Contents 1 Test Description 3 2 Prerequisites 4 2.1 System Access 4 2.2 Roles 4 2.3 System Setup 4 2.4 Data 5 3 Test Procedures 6 3.1 Business Partner Fact Sheet 6
Document History Revision Change Date Description 0 2016-03-11 Document creation Test Description 2015 SAP SE or an SAP affiliate company. All rights reserved. 2
1 Test Description In this integration package, a marketing expert wants to have actual and committed spend from SAP ERP visible in marketing planning of SAP S/4HANA, cloud marketing edition. This document provides a detailed procedure for testing the integration package SAP S/4HANA, cloud marketing edition - ERP Data Integration. Each process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be added Test Description 2015 SAP SE or an SAP affiliate company. All rights reserved. 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. 2.1 System Access Systems SAP ERP 6.0 EhP 4 system or higher SAP S/4HANA, cloud marketing edition Details Transaction SE38 ABAP report CUAN_ERP_MSM_EXTRACT_ACTUAL Fiori Launchpad Tile My Marketing Spend - Details 2.2 Roles For details about the business role content, refer to the section Maintenance of Fiori Artefacts for SAP S/4HANA in the configuration guide Check S/4HANA Technical Settings (BG0). Use the following standard test users or assign roles to testers, respectively: SAP S/4HANA, cloud marketing edition: Business Catalog Role Name Business Catalog Role ID Log On Marketing- Spend Management SAP_BCR_CEC_MKT_SMP_PC Suggested sample user MARKETING_EXPERT representing the business role Marketing Expert 2.3 System Setup To test this integration package, you must have configured the scenario defined in https://help.sap.com/s4hana -> SAP S/4HANA Cloud 1605 > Product Assistance > Cloud Editions > SAP S/4HANA Marketing Cloud > Business Administration Tasks > Export of Data > Exporting Spend Data to SAP ERP. Prerequisites 2015 SAP SE or an SAP affiliate company. All rights reserved. 4
2.4 Data To test this integration package, you must have done the following - Create a campaign in My Marketing Spend - Detail app and add at least spend types with planned spend. - Release the campaign which will have created a project and WBS elements for this campaign in SAP ERP. - Create a Purchase Order for each WBS element. - Create a good receipt for the Purchase Order for one of the WBS elements to get actual spend. - Keep one of Purchase Order without a good receipt to get committed spend Prerequisites 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
3 Test Procedures This section describes test procedures for each process step that belongs to this scope item. 3.1 Business Partner Fact Sheet Test Administration Customer project: Fill in the project-specific parts (highlighted). Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date. Business Role(s) Marketing Expert Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration <Enter a duration, e.g. 60 minutes> Purpose The marketing expert is interested to understand the process of his campaign spend, both the actual and committed spend, in My Marketing Spend - Detail. Test Procedures 2015 SAP SE or an SAP affiliate company. All rights reserved. 6
Procedure - SAP Fiori This procedure expects that you have done all the prerequisites. Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment 1. Logon to SAP ERP system as an administrator Log on to SAP ERP backend (SAPGUI) 2. Run transaction SA38 Run ABAP report CUAN_ERP_MSM_EXTRACT_ACTUAL IDoc is created based on the selection criteria. Please refer to the documentation before running it 3. Type in the Project Prefix e.g. 1_CUAN_MSM_ 4. Select Posting Date e.g. 01.01.2016 to 23.03.2016 5. Select Update Mode Mark the Send All Actual and Committed Spend radio button 6. Run the report Click on the Execute button (F8) Report run successfully and IDoc was posted. 7. Log on to Fiori Launchpad as Marketing Expert 8. Access My Marketing Spend - Detail 9. Select a campaign that is released Log on to the Fiori Launch Pad as a Marketing Expert. Open tile My Marketing Spend - Detail Choose a campaign from the master list which is released, has 2 spend types, and that was sent to SAP ERP and has actual and committed spend associated to it. Ensure that you have created a campaign with all the related steps as described in the prerequisites The Fiori Launchpad opened. The system displays a list of available campaigns in a master list. The campaign spend is shown on the detail page 3 tiles are shown: KPI comparison mini-chart showing data at the program level, to which the campaign is assigned Actual amount for this campaign Committed amount for this campaign Test Procedures 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description 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. Emphasized words or expressions. 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. 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. 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. Keys on the keyboard, for example,f2 or ENTER. Test Procedures 2015 SAP SE or an SAP affiliate company. All rights reserved. 8
www.sap.com/contactsap 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporateen/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.