Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
1 Purpose 2
2 Prerequisites 3
2.1 System Access 3
2.2 Roles 3
2.3 Master Data, Organizational Data, and Other Data 3
2.4 Preliminary Steps 4
3 Overview Table 5
4 Test Procedures 6
4.1 Create Purchasing Categories 6
4.2 Manage Purchasing Categories 8
1 Purpose
This scope item helps you gain a portfolio-level view of your supplier relationships. It also gives you the transparency to continuously determine the right mix of suppliers, serve your business
objectives optimally, and to reduce your overall supply risk. You can classify and segment your suppliers by multiple criteria. This enables you to identify suppliers in a flexible manner, as well as to
define and monitor sourcing strategies.
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.
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.
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 role is provided as an example role from SAP. You can use these as templates for your own roles.
For more information on creating master data objects, see the following Master Data Scripts (MDS)
Supplier Classification and Segmentation (19E_US) PUBLIC
Prerequisites © 2018 SAP SE or an SAP affiliate company. All rights reserved. 3
Table 1: Master Data Script Reference
Master Data ID Description
BNE Create Supplier Master
The Subcontracting test script consists of several process steps provided in the following table.
Manage Purchasing Categories Strategic Manage Purchasing Categories Purchasing category is maintained, including assigning Suppliers, Team Employees and
[page ] 8 Buyer (F0337) Material Groups to it.
This section describes test procedures for each process step that belongs to this scope item.
Test Administration
Test Case ID <X.XX> Tester Name Testing Date Enter a test date.
Business Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
In this activity, a purchasing category is created and a purchaser responsible for the purchasing category is assigned. Suppliers, team employees, and material groups are also assigned to it.
Procedure
1 Logon Logon to the SAP Fiori launchpad as a Strategic Buyer. The SAP Fiori launchpad displays.
2 Open Manage Purchasing Open Manage Purchasing Categories (F0337) . The Manage Purchasing Categories (Original)
Categories screen displays.
4 Enter Purchasing Category In the General section, make the following entries: All data is entered, no error or warning
data Name : <enter a name for the purchasing category, e.g. messages exist.
Test_PurchasingCategory>
Purchaser Responsible : Buyer
(leave it as default value)
Choose Enter.
5 Assign Suppliers In the Suppliers section, choose Add Line, and enter following data : The assignment of suppliers to the purchasing
ID: 17300001. category is done.
Choose Enter.
6 Assign Team Employees In the Team section, Choose Add Employee, The assignment of team members to the
In the search help Add Employee, choose Go. purchasing category is done.
In the search result list, select an employee and choose OK. Check that the is Member.
7 Add Purchasing Category In the Languages for Purchasing Category Description section, make the following The assignment of description and available
Description and Languages entries: languages of the purchasing category is done.
Purchasing Category Description : <enter a description of the
purchasing category, e.g. Test_PurchasingCategory>
Choose Add Language, enter following data:
Language: Choose a language for translation from the dropdown list
Status of Translation: To Be Translated
Choose Enter.
8 Assign Material Groups In the Material Groups section, choose Add Material Groups and enter following The material group is assigned to the
data in the dialogue box : purchasing category.
Material Group ID: L001
Choose GO button.
In the search resulst list select the entry of L001 and choose OK.
Result
The system generates a purchasing category.
Test Administration
Test Case ID <X.XX> Tester Name Testing Date Enter a test date.
Business Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
This activity displays and edits the purchasing category created in the previous step.
Procedure
3 Search Purchasing In the Search field, enter a part of the purchasing category name entered in test The search result list is displayed.
Category step 4 of Create Purchasing Categories [page ] 6.
Choose Go.
4 Display Purchasing Click on e.g. name of the requested Purchasing Category. The Purchasing Category screen displays.
Category On the screen Purchasing Category, check the details of the purchasing The details of the purchasing category is
category. displayed correctly.
5 Edit Purchasing Category Choose Back. The screen Purchasing Category: <name of
On the search result list, select the requested purchasing category by choosing purchasing category> displays.
the radio button.
Choose Edit.
6 Add Planned Spend On section Planned Spend, choose Add Line and enter following data: The purchasing category is changed and saved.
From: <select a start date>
To: <select an end date>
Amount: For example, 10
Currency: USD
Choose Save.
Result
The Purchasing Category displays and changes.
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 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.