Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.

Purpose © 2018 SAP SE or an SAP affiliate company. All rights reserved. 1

Test Script PUBLIC
SAP S/4HANA - 16-04-18

Purchase Order Visibility and Procurement Spend

(2QU)

Table of Contents

1 Purpose 2

2 Prerequisites 3
2.1 System Access 3
2.2 Roles 3

3 Overview Table 4

4 Test Procedures 5
4.1 Display CDS Queries for Procurement Scenario 5
4.2 Show Content of CDS Queries for Procurement Scenario 6
4.3 Create Application based on CDS Queries 7
1 Purpose

This scope item provides a prebuilt set of Key Performance Indicators for the procurement scenario, allowing analytics that include information from the SAP S/4HANA Cloud system. Business
leaders and decision makers can monitor, simulate, and drive change that show overview and line-item details and provide business context at the same time to uncover hidden insights. These
KPIs can be used in different scenarios such as Two Tier and SAC stories.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. 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.

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Purpose © 2018 SAP SE or an SAP affiliate company. All rights reserved. 2
2 Prerequisites

This section summarizes all prerequisites to conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.

2.1 System Access

System Details

System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles
Assign the following business roles to your individual test users.
Note The following roles are provided as example roles from SAP. You can use these as templates to create your own roles.

Business Role Business Role ID as Delivered by SAP Log On

BUYER SAP_BR_BUYER

ANALYTICS_SPECIALIST SAP_BR_ANALYTICS_SPECIALIST

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Prerequisites © 2018 SAP SE or an SAP affiliate company. All rights reserved. 3
3 Overview Table

This scope item consists of several process steps provided in the table below.

Process Step Business Role Transaction/App Expected Results

Display CDS Queries for Procurement Scenario [page ] 5 SAP_BR_BUYER View Browser
SAP_BR_ANALYTICS_SPECIALIST

Show Content of CDS Queries for Procurement Scenario [page ] 6 SAP_BR_BUYER View Browser
SAP_BR_ANALYTICS_SPECIALIST

Create Application based on CDS Queries [page ] 7 SAP_BR_BUYER View Browser

SAP_BR_ANALYTICS_SPECIALIST

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Overview Table © 2018 SAP SE or an SAP affiliate company. All rights reserved. 4
4 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.
There are several prebuilt CDS Queries for procure scenario. In the following test procedures, we use only C_PurchaseOrderValueQuery as an example. However, if you would like to analyze
other Key Performance Indicators, you can refer to the table below and choose the corresponding CDS Queries.

CDS Queries Description

C_PurgSpendOffContract Evaluating/analyzing the spend incurred for Off Contract during the procurement/ sourcing event for the purpose of reducing the overall procurement cost

C_PurchaseOrderValueQuery Evaluating/analyzing the spend incurred for PO orders during the procurement/ sourcing event for the purpose of reducing the overall procurement cost

4.1 Display CDS Queries for Procurement Scenario

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

You want to display CDS queries of Procurement Scenario.

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Test Procedures © 2018 SAP SE or an SAP affiliate company. All rights reserved. 5
Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1 Log On Log on to the SAP Fiori launchpad. The SAP Fiori launchpad is dis-
played.

2 Access the App Open View Browser in business group Query Design. The app is launched successfully.

3 Search the CDS Enter the query name C_PurchaseOrderValueQuery in the search bar. Choose The CDS view is displayed.
Query Search.

4.2 Show Content of CDS Queries for Procurement Scenario

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

You want to preview data in CDS queries of Procurement Scenario.

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Test Procedures © 2018 SAP SE or an SAP affiliate company. All rights reserved. 6
Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1 Choose the CDS Query Choose the selection box of the CDS Query in View Browser (C_Pur- The CDS query is selected in the list.
chaseOrderValueQuery).

2 Show Content for the CDS Choose Show Content. The prompt window is displayed.
Query

3 Enter Prompt Value Enter values for prompt Display Currency and Rel Date Function. Choose The dimensions and measure are displayed on
OK. the left panel.

4 Navigate the CDS Query Drag and drop dimensions to theROWS panel. The data preview of the analytical query is dis-
For example: played.

Calendar Year
Calendar Month
Purch. Org. Name
Material Group

Note If you have any issues with the View Browser application in the test procedures, refer to the following document about View Browser. Navigate to English > Generic Information > Analyt-
ics > View Browser .

4.3 Create Application based on CDS Queries

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Test Procedures © 2018 SAP SE or an SAP affiliate company. All rights reserved. 7
Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

You want to create and publish a tile to the catalog for analytical queries for Procurement Scenario.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Choose the CDS Choose the selection box of the CDS Query in View Browser. The CDS query is selected in the list.
Query

2 Create Application for Choose Create Application. The dialog box is displayed.
the CDS Query

3 Enter Value for Title Enter a title and a subtitle for the application. For example, en- An app ID is generated and is available in the Application ID column.
and Subtitle ter Purchase Order Value Analysis. Choose OK. You can publish the application via the Custom Catalog Extension app.

Before creating the application, make sure that for this particular query, no application already exists or delete the outdated application.
If you encounter any issues when publishing the application via the Custom Catalog Extension app in the test procedures, please refer to the following document about Extensibility and
Custom Catalog Extensions. Navigate to English > General Functions for the Key User > Extensibility > Custom Catalog Extensions .

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Test Procedures © 2018 SAP SE or an SAP affiliate company. All rights reserved. 8
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.

<Example> 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 .

Purchase Order Visibility and Procurement Spend (2QU) Error! Reference source not found.
Test Procedures © 2018 SAP SE or an SAP affiliate company. All rights reserved. 9
www.sap.com/contactsap

© 2018 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 affili-
ate 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 in-
formational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omis-
sions 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 ac-
companying 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 presenta-
tion, or to develop or release any functionality mentioned therein. This doc-
ument, or any related presentation, and SAP SE’s or its affiliated compa-
nies’ 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 no-
tice. The information in this document is not a commitment, promise, or le-
gal 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 cau-
tioned 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.