Академический Документы
Профессиональный Документы
Культура Документы
CUSTOMER
Table of Contents
1
Test Description
2
2.1
2.2
2.3
2.4
Prerequisites 5
Association to Sales Order Processing: Sell from Stock (109)
System Access and Roles
5
Master Data, Organizational Data, and Other Data
6
Business Conditions 7
Overview Table
4
4.1
4.2
5
5.1
Test Procedures
10
Test Generic Example Flavors 10
4.1.1
Start Sales Order Processing Landing Page
10
4.1.2
Create Sales Order with Generic Example Flavor
11
4.1.3
Create Delivery with Generic Example Flavor
12
4.1.4
Check Batches with Generic Example Flavor
13
4.1.5
Assign Serial Numbers with Generic Example Flavor
15
4.1.6
Post Goods Issue with Generic Example Flavor 16
4.1.7
Create Billing with Generic Example Flavor
17
Test Fiori Flavors
18
4.2.1
Start Sales Order Processing Launchpad19
4.2.2
Create Sales Order with Fiori Flavor
20
4.2.3
Create Delivery with Fiori Flavor 21
4.2.4
Check Batches and Assign Serial Numbers with Fiori Flavor
4.2.5
Assign Serial Numbers with Fiori Flavor 23
4.2.6
Post Goods Issue with Fiori Flavor
25
4.2.7
Create Billing with Fiori Flavor 26
Appendix
28
Process Integration
28
22
5.1.1
Preceding Processes
28
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Document History
Revision
Change Date
Description
June 8, 2015
Published version
Note for the customer project team: Instructions for the customer project team are highlighted in yellow and should be removed before hand -over to project
testers. The appendix is included for internal reference, in particular to support A2O, and should also be deleted before hand-over to the customer, unless
deemed helpful to explain the larger context.
If there are any special requirements that do not fit into the template, add instructions to the appendix.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Test Description
This scope item provides example SAP Screen Personas flavors for transactions to process a standard sales order for a customer. The example flavors are
provided in two different design versions:
Fiori Flavors
This document provides a detailed procedure for testing the scope item Sales Order Processing with SAP Screen Personas 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.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
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
Scope item Sales Order Processing with SAP Screen Personas (UP1) reflects the mandatory process steps of the business process included in Sales Order
Processing: Sell from stock (109) configured using SAP Screen Personas 3.0. Therefore in order to fully utilize the process steps in this scope item, it is
recommended that you are familiar with the scope item Sales Order Processing: Sell from stock (109) and follow the prerequisites for that scenario.
2.2
Details
SAP ERP
Use the following standard test users or assign roles to testers, respectively:
Business Role
Business Role ID
Log On
SAP_NBPR_EMPLOYEE_S
/PERSONAS/CONSUMER_ROLE
Sales Administrator
Password: <password>
Test user: <userid>
Password: <password>
SAP_NBPR_SALESPERSON_S
Warehouse Clerk
SAP_NBPR_WAREHOUSECLERK_S
Billing Administrator
Sales Order Processing with SAP Screen Personas
Appendix
SAP_NBPR_BILLING_S
Business Role
Business Role ID
Log On
Password: <password>
2.3
The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the
structure of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your
company.
Use your own master data to go through the test procedure. If you have installed an SAP Best Practices baseline package, you can use the following baseline
package sample data:
Note
The master data used is the same as for the scenario Sales Order Processing: Sell from stock (109).
If you are using these master data, ensure that you carry out the activities listed in Preliminary Steps in the document Sales Order Processing: Sell
from stock (109).
Data
Sample Value
Details
Material
H11
Comments
H12
Material
H20
Example
You have activated the building block
Serial Number Management (126).
Material
H21
Example
You have activated the building block
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Data
Sample Value
Details
Comments
H22
Example
You have activated the building block
F29
Example
You have activated the building block
F126
Example
You have activated the building block
Serial Number Management (126).
Sold-to party
493000
Customer Company 02
Ship-to party
493000
Customer Company 02
Payer
493000
Customer Company 02
Plant
1000 (1100)
Shipping Point
1000 (1100)
Sales organization
1000
Distribution channel
10
Division
10
2.4
Business Conditions
Before this scope item can be tested, the following business conditions must be met.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Condition
1
Comment
Relevant SAP Screen Personas flavors have been created for all
transactions in the business process.
Note
The scenario Sales Order Processing: Sell from stock (109) contains several business conditions that are prerequisites for that scenario. These steps
are not provided with example SAP Screen Personas flavors, nor do they form part of the solution for SAP Screen Personas.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Overview Table
The scope item Sales Order Processing with SAP Screen Personas consists of several process steps, provided in the table below.
Process Step
Business Role
Transaction
Expected Results
Employee
(Professional User)
SMEN
Sales Administrator
VA01
Warehouse Clerk
VL10, VL01N
Warehouse Clerk
VL02N
Warehouse Clerk
VL06O
Billing Administrator
VF04, VF01
Employee
(Professional User)
SMEN
Sales Administrator
VA01
Warehouse Clerk
VL10, VL01N
Warehouse Clerk
VL02N
Warehouse Clerk
VL06O
Billing Administrator
VF04, VF01
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
The test should take around 60 minutes.
4.1
This process exclusively uses the generic example flavors for Sales Order Processing.
The test should take around 30 minutes.
4.1.1
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Responsibility
Testing Date
Duration
5 minutes
Purpose
In this process step you access the Sales Order Processing Landing Page in the Web browser. This is the starting point to access each of the transactions in
the process.
Note
Each business role uses the landing page to access the transactions for which they are responsible.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
10
Procedure
Test Step #
Instruction
Expected Result
1.
2.
4.1.2
Pass / Fail /
Comment
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Sales Administrator
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you enter a sales order.
Procedure
Test Step
#
Instruction
Expected Result
1.
Pass / Fail /
Comment
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
11
Test Step
#
Instruction
Expected Result
transaction
2.
Enter customer
3.
4.
Example
Pass / Fail /
Comment
Example
Enter H11 or H20 (for serial number assignment)
or F29 (for batch assignment) in Material;
Enter 5 in Order Quantity.
6.
Save order
Choose Save.
Note
Make a note of the sales order
number:
_______________.
4.1.3
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Business Roles
Warehouse Clerk
Tester Name
Testing Date
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
12
Responsibility
Duration
5 Minutes
Purpose
In this process step you create the delivery.
Prerequisites
Sufficient quantities of the materials are available for delivery. You can maintain this in Goods Receipt Other (transaction MIGO).
Note
For further information on this process, refer to section Preliminary Steps in Sales Order Processing: Sale from Stock (109).
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Create delivery
3.
4.
5.
Save Delivery
Choose Save.
Pass / Fail /
Comment
Note
Make a note of the delivery
Sales Order Processing with SAP Screen Personas
Appendix
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
13
Test Step
#
Instruction
Expected Result
Pass / Fail /
Comment
number:
_______________.
4.1.4
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you check batches for the materials in the delivery document.
Prerequisites
Use this step if batch management is activated.
You can only execute this step for a material with batches.
Example
Material F29.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
14
Procedure
Test Step
#
Instruction
Expected Result
Pass / Fail /
Comment
1.
Start Check
Batches/Assign Serial
Numbers transaction
2.
3.
Note
The batch split indicator is represented by an
icon in the Batch Split Indicator column.
4.
5.
6.
Choose Save.
4.1.5
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Business Roles
Warehouse Clerk
Responsibility
Tester Name
Testing Date
Duration
5 Minutes
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
15
Purpose
In this process step you carry out serial number assignment for the materials in the delivery document.
Prerequisites
You can only execute this step for a material with serial number assignment.
Example
Material H20.
Procedure
Test Step
#
Instruction
Expected Result
1.
Start Check
Batches/Assign Serial
Numbers transaction
2.
3.
Pass / Fail /
Comment
Example
Material H20.
4.
5.
6.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
16
4.1.6
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you post the goods issue.
Prerequisites
In order to render the ABAP List Viewer (ALV) screen in an SAP Screen Personas flavor, the list type must be set to Grid Control.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Example
Enter 1000 for Shipping Point/Receiving Point.
3.
Pass / Fail /
Comment
Caution
The list is displayed in ALV
format.
17
Test Step
#
Instruction
Expected Result
4.
4.1.7
Pass / Fail /
Comment
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Billing Administrator
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you handle the billing for the order.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Pass / Fail /
Comment
Example
Enter dates in Billing Date From and to in order
Sales Order Processing with SAP Screen Personas
Appendix
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
18
Test Step
#
Instruction
Expected Result
Pass / Fail /
Comment
4.
Create Invoice
Note
The status of the document is
displayed as OK (icon with
green tick).
5.
4.2
Leave Billing
This process exclusively uses the Fiori flavors for Sales Order Processing.
The test should take around 30 minutes.
4.2.1
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Business Roles
Responsibility
Tester Name
Testing Date
Duration
5 minutes
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
19
Purpose
In this process step you access the Sales Order Processing Launchpad in the Web browser. This is the starting point to access each of the transactions in the
process.
Note
Each business role uses the Launchpad to access the transactions for which they are responsible.
Procedure
Test Step #
Instruction
Expected Result
1.
2.
Navigate to Launchpad
4.2.2
Pass / Fail /
Comment
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Sales Administrator
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you enter a sales order.
Sales Order Processing with SAP Screen Personas
Appendix
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
20
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Enter customer
3.
4.
Example
Pass / Fail /
Comment
Example
Enter H11 or H20 (for serial number assignment)
or F29 (for batch assignment) in Material;
Enter 5 in Order Quantity.
6.
Save order
Choose Save.
Note
Make a note of the sales order
number:
_______________.
4.2.3
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Sales Order Processing with SAP Screen Personas
Appendix
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
21
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you create the delivery.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Create delivery
3.
4.
5.
Save Delivery
Pass / Fail /
Comment
Note
Make a note of the delivery
number:
_______________.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
22
4.2.4
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you check batches for the materials in the delivery document.
Prerequisites
Use this step if batch management is activated.
You can only execute this step for a material with batches.
Example
Material F29.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Pass / Fail /
Comment
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
23
Test Step
#
Instruction
Expected Result
Pass / Fail /
Comment
Note
The batch split indicator is represented by an
icon in the Batch Split Indicator column.
4.
5.
6.
Choose Save.
4.2.5
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you carry out serial number assignment for the materials in the delivery document.
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
24
Prerequisites
You can only execute this step for a material with serial number assignment.
Example
Material H20.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
3.
Pass / Fail /
Comment
Example
Material H20.
4.
5.
Note
The item with the batch number has batch
number displayed in Batch column.
6.
Create Serial
Assignments
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
25
4.2.6
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date
Duration
25 Minutes
Purpose
In this process step you post the goods issue.
Prerequisites
In order to render the ABAP List Viewer (ALV) screen in an SAP Screen Personas flavor, the list type must be set to Grid Control.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Example
Enter 1000 for Shipping Point/Receiving Point.
3.
Pass / Fail /
Comment
Caution
The list is displayed in ALV
format.
26
Test Step
#
Instruction
Expected Result
4.
4.2.7
Pass / Fail /
Comment
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Billing Administrator
Responsibility
Testing Date
Duration
5 Minutes
Purpose
In this process step you handle the billing for the order.
Procedure
Test Step
#
Instruction
Expected Result
1.
2.
Pass / Fail /
Comment
Example
Enter dates in Billing Date From and to in order
Sales Order Processing with SAP Screen Personas
Appendix
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
27
Test Step
#
Instruction
Expected Result
Pass / Fail /
Comment
4.
Create Invoice
Note
The status of the document is
displayed as OK (icon with
green tick).
5.
Leave Billing
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
28
Appendix
5.1
Process Integration
The process to be tested in this test script is part of a chain of integrated processes.
5.1.1
Preceding Processes
You may first have completed the following processes and conditions before you start with the test steps:
Process
Business Condition
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
29
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
30
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
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
CUSTOMER
2015 SAP SE or an SAP affiliate company. All rights reserved.
31
www.sap.com/contactsap