Up1 Scrp30 BPD en XX

Test Script
SAP Screen Personas 3.0

June 2015
English
CUSTOMER
Sales Order Processing with SAP Screen

Personas
UP1
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
Sales Order Processing with SAP Screen Personas

Typographic Conventions
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.

Appendix
CUSTOMER
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:
Generic Example Flavors
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.

Appendix
CUSTOMER
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
Association to Sales Order Processing: Sell from Stock (109)
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
System Access and Roles
The test is conducted in the following systems:

System
Details
SAP ERP
<Provide details on how to access system, e.g. system client or URL>
Use the following standard test users or assign roles to testers, respectively:
Business Role
Business Role Description
Business Role ID
Log On
Employee (Professional User)
Assignment of this role is necessary

for basic functionality.
SAP_NBPR_EMPLOYEE_S
Test user: <userid>
Assignment of this role is necessary

to use SAP Screen Personas to
execute the transactions in the
business process
/PERSONAS/CONSUMER_ROLE
SAP Screen Personas standard

user
Sales Administrator
Password: <password>
Test user: <userid>
SAP_NBPR_SALESPERSON_S
Test user: <salesperson_userid>

Warehouse Clerk
SAP_NBPR_WAREHOUSECLERK_S
Test user: <warehouse_clerk_userid>

Billing Administrator
Appendix
SAP_NBPR_BILLING_S
Test user: <billing_userid>

CUSTOMER
Business Role
Business Role Description
Business Role ID
Log On
2.3
Master Data, Organizational Data, and Other Data
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
Trading Good for Reg. Trading (MRP

planning)
Comments
no Serial no.; no batch

Material
H12
Trading Good for Reg. Trading

(reorder point planning)
no Serial no.; no batch
Material
H20

with serial numbers, no batch
You must have activated Serial Number

Management.
Example
You have activated the building block
Serial Number Management (126).
Material
H21

no Serial no.; batch controlled
(Exp. Date)

Appendix
You must have activated Batch Management.
Example
CUSTOMER
Data
Sample Value
Details
Comments
Batch Management (117).

Material
H22

no Serial no.; batch controlled
(FIFO strategy)
Example

Material
F29
Finished Good MTS for Process

Industry (PD planning)
no Serial no.; with batch (Exp.
Date)
Example

Material
F126
Finished Good MTS for Discrete

Industry (PD planning)
with Serial no.; with / w/o batch
(FIFO strategy)
You must have activated Serial Number

Management.
Example
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
You can test the scope item using another

customer.
Business Conditions
Before this scope item can be tested, the following business conditions must be met.

Appendix
CUSTOMER
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.

Appendix
CUSTOMER
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
Start Sales Order Processing Landing

Page
Employee
(Professional User)
SMEN
Create Sales Order with Generic Example

Flavor
Sales Administrator
VA01
Sales Order is created.
Create Delivery with Generic Example

Flavor
Warehouse Clerk
VL10, VL01N
Delivery is created. The Warehouse Transfer Order is

created.
Check Batches and Assign Serial

Numbers with Generic Example Flavor
Warehouse Clerk
VL02N
Post Goods Issue with Generic Example

Flavor
Warehouse Clerk
VL06O
The goods issue is posted.
Create Billing with Generic Example

Flavor
VF04, VF01
Billing is carried out.
Start Sales Order Processing Launchpad
Employee
(Professional User)
SMEN
Sales Administrator
VA01
Sales Order is created.
Create Delivery with Fiori Flavor
Warehouse Clerk
VL10, VL01N
Delivery is created. The Warehouse Transfer Order is

created.
Check Batches and Assign Serial

Numbers with Fiori Flavor
Warehouse Clerk
VL02N
Warehouse Clerk
VL06O
The goods issue is posted.
Create Billing with Fiori Flavor
VF04, VF01
Billing is carried out.

Appendix
CUSTOMER
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
Test Generic Example Flavors
This process exclusively uses the generic example flavors for Sales Order Processing.
4.1.1
Start Sales Order Processing Landing Page
Test Administration
Customer project: Fill in the project-specific parts (highlighted).
Test Case ID
<X.XX>
Tester Name
Business Roles
Responsibility
<State Service Provider, Customer, or Joint Service Provider and Customer>
Testing Date
Click here to enter a

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.

Appendix
CUSTOMER
10
Procedure
Test Step #
Test Step Name
Instruction
Expected Result
1.
Log on using Web browser
You log on to the system using a Web

browser with the correct URL address
You have logged on to the system and the

initial transaction is displayed in the Web
browser session.
2.
Navigate to landing page
Navigate to the transaction for the landing

page.
The landing page for Sales Order Processing

is displayed
4.1.2
Pass / Fail /
Comment
Create Sales Order with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Sales Administrator
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you enter a sales order.
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Create Sales Order
In the landing page for Sales Order Processing, choose
You are directed to the overview screen

Appendix
Pass / Fail /
Comment
CUSTOMER
11
Test Step
#
Test Step Name
Instruction
Expected Result
transaction
Enter button below the text Create Sales Order.
for the transaction Create Sales Order.
2.
Enter customer
In the Sold-To-Party field, enter the customer number

<Sold-To-Party>.
The customer number is displayed in

Sold-To-Party
3.
Enter purchase order

number
Enter a customer purchase order number as a reference
The Customer purchase order number

is displayed.
4.
Enter payment terms
In the Payment terms field, enter the payment terms.
The Terms of Payment Key and the

Description of terms of payment are
displayed.
Example
Pass / Fail /
Comment
0003 14 days 3%, 20/2%, 30 net

5.
Enter material and order

quantity
Enter <Material> in Material, and <Quantity>.
The material id, order quantity, and

unit are displayed in the order item
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.
You have saved the sales order.
Note
Make a note of the sales order
number:
_______________.
4.1.3
Create Delivery with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Business Roles
Warehouse Clerk

Appendix
Tester Name
Testing Date

date.
CUSTOMER
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
#
Test Step Name
Instruction
Expected Result
1.
Start Create Delivery

transaction

the Enter button below the text Create Delivery.
You are directed to the initial screen for

the transaction Create Delivery.
2.
Create delivery
In the Sales Document field, enter the <Sales Order

Number> and choose Execute.

of the order.
3.
Choose Activities Due for

Shipping
Select the sales order document in the list Activities Due

for Shipping: Sales Order and choose Execute in Dialog.
You have selected the sales order to

create a delivery.
4.
Enter Delivery Quantity
If necessary, in the Create Outbound Delivery screen, in

the Deliv. Qty column, enter the delivery quantity for
each item in the outbound delivery.
5.
Save Delivery
Choose Save.
Pass / Fail /
Comment
You have saved the delivery document.
Note
Make a note of the delivery
Appendix
CUSTOMER
13
Test Step
#
Test Step Name
Instruction
Expected Result
Pass / Fail /
Comment
number:
_______________.
4.1.4
Check Batches with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

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.

Appendix
CUSTOMER
14
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
Pass / Fail /
Comment
1.
Start Check
Batches/Assign Serial
Numbers transaction

the Enter button below the text Check Batches Assign
Serial Numbers.
You are directed to the initial screen to

check batches and assign serial
numbers.
2.
Enter Outbound Delivery

Number
In the Outbound Delivery field, enter the <Outbound

Delivery Number> and choose Enter.

of the delivery.
3.
Select an Item with a

Batch Split
Select an item for which a batch split exists.
You have selected an item with a batch

split.
Note
The batch split indicator is represented by an
icon in the Batch Split Indicator column.
4.
Display Batch Split
Choose Batch Split.

of the batch split.
5.
Check Batch Number

Assignment
In Batch split items, check the batch number

assignment in the Batch field.
You have checked the batch

assignment.
6.
Save Batch Number

Assignment
Choose Save.
You have saved the batch assignment.
4.1.5
Assign Serial Numbers with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Business Roles
Warehouse Clerk
Responsibility

Appendix
Tester Name
Testing Date

date.
Duration
5 Minutes
CUSTOMER
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
#
Test Step Name
Instruction
Expected Result
1.
Start Check
Batches/Assign Serial
Numbers transaction

Enter in the button below the text Check Batches Assign
Serial Numbers.

numbers.
2.

Number


of the delivery.
3.
Select an Item with

Serial Numbers
Select an item for which a serial number is maintained.
You have selected an item with serial

numbers.
Pass / Fail /
Comment
Example
Material H20.
4.
Choose Serial Numbers
Choose Serial Numbers.
The Maintain Serial Numbers dialog box

is displayed.
5.
Create Serial Numbers

Automatically
Choose Cre (Create serial number automatically

Create serial numbers automatically)
You have created serial numbers for the

selected item of the delivery order.
6.
Assign Numbers and

Save
Choose Continue and Save
The serial numbers are assigned to the

item. Save the delivery order to persist
your changes.

Appendix
CUSTOMER
16
4.1.6
Post Goods Issue with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

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
#
Test Step Name
Instruction
Expected Result
1.
Start Post Goods Issue

transaction

the Enter button below the text Post Goods Issue.

posting goods issue.
2.
Enter Shipping Point
In Shipping Point/Receiving Point, enter the value for

<Shipping Point> and choose Execute.
The list of outbound deliveries to be

posted is displayed.
Example
Enter 1000 for Shipping Point/Receiving Point.
3.
Select Order for Goods

Issue

Appendix
Pass / Fail /
Comment
Caution
The list is displayed in ALV
format.
Select the delivery order and choose Post Goods Issue.

CUSTOMER
17
Test Step
#
Test Step Name
Instruction
Expected Result
4.
Specify Actual Goods

Issue Date
Choose todays date in the dialog box and choose

Continue.
You have posted the goods issue for the

outbound delivery.
4.1.7
Pass / Fail /
Comment
Create Billing with Generic Example Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you handle the billing for the order.
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Create Billing

transaction

the Enter button below the text Create Billing.

billing.
2.
Search for Billing

Documents
Enter the relevant search criteria and choose Display Bill

List.
The Maintain Billing Due List is

displayed.
Pass / Fail /
Comment
Example
Enter dates in Billing Date From and to in order
Appendix
CUSTOMER
18
Test Step
#
Test Step Name
Instruction
Expected Result
Pass / Fail /
Comment
to search for documents according to date.

3.
Create Individual Billing

Document
Select the respective billing document and choose

Individual Billing.
The Create Invoice screen is displayed.
4.
Create Invoice
In Create Invoice: Overview of Billing Items, choose

Save.

displayed.
Note
The status of the document is
displayed as OK (icon with
green tick).
5.
4.2
Leave Billing
Choose Back twice to return to the landing page.
You have created an invoice for the

order.
Test Fiori Flavors
This process exclusively uses the Fiori flavors for Sales Order Processing.
4.2.1
Start Sales Order Processing Launchpad
Test Administration
Test Case ID
<X.XX>
Business Roles
Responsibility

Appendix
Tester Name
Testing Date

date.
Duration
5 minutes
CUSTOMER
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 #
Test Step Name
Instruction
Expected Result
1.
Log on using Web browser
You log on to the system using a Web

browser with the correct URL address
You have logged on to the system and the

initial transaction is displayed in the Web
browser session.
2.
Navigate to Launchpad
Navigate to the transaction for the

Launchpad.
The Launchpad for Sales Order Processing is

displayed
4.2.2
Pass / Fail /
Comment
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Sales Administrator
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you enter a sales order.
Appendix
CUSTOMER
20
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Create Sales Order

transaction
In the Sales Order Processing Launchpad, choose the tile

Create Sales Order.

the transaction Create Sales Order.
2.
Enter customer
In the field Sold-To-Party, enter the customer number

<Sold-To-Party>.
The customer number is displayed in

Sold-To-Party
3.
Enter purchase order

number
Enter a customer purchase order number as a reference
The Customer purchase order number

is displayed.
4.
Enter payment terms
In the Payment terms field, enter the payment terms.
The Terms of Payment Key and the

Description of terms of payment are
displayed.
Example
Pass / Fail /
Comment
0003 14 days 3%, 20/2%, 30 net

5.
Enter material and order

quantity
Enter <Material> in Material, and <Quantity>.
The material id, order quantity, and

unit are displayed in the order item
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.
You have saved the sales order.
Note
Make a note of the sales order
number:
_______________.
4.2.3
Create Delivery with Fiori Flavor
Test Administration
Appendix
CUSTOMER
21
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you create the delivery.
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Create Delivery

transaction

Create Delivery.

the transaction Create Delivery.
2.
Create delivery
In the Sales Document field, enter the <Sales Order

Number> and choose Execute.

of the order.
3.
Choose Activities Due for

Shipping
Select the sales order document in the list Activities Due

for Shipping: Sales Order, Fast Display and choose
Execute in Dialog.
You have selected the sales order to

create a delivery.
4.
Enter Delivery Quantity
If necessary, in the Create Outbound Delivery screen, in

the Deliv. Qty column, enter the delivery quantity for
each item in the outbound delivery.
5.
Save Delivery
In the Create Outbound Delivery screen, choose Save.
Pass / Fail /
Comment
You have saved the delivery document.
Note
Make a note of the delivery
number:
_______________.

Appendix
CUSTOMER
22
4.2.4
Check Batches with Fiori Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

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
#
Test Step Name
Instruction
Expected Result
1.
Start Assign Serial

Numbers transaction

Check Batches Assign Serial Numbers.

numbers.
2.

Number

of the delivery.

Appendix
Pass / Fail /
Comment
CUSTOMER
23
Test Step
#
Test Step Name
Instruction
Expected Result
Pass / Fail /
Comment

3.

Batch Split
Select an item for which a batch split exists.

split.
Note
The batch split indicator is represented by an
icon in the Batch Split Indicator column.
4.
Display Batch Split
Choose Batch Split.

of the batch split.
5.
Check Batch Number

Assignment
In Batch split items, check the batch number

assignment in the Batch field.
You have checked the batch

assignment.
6.
Save Batch Number

Assignment
Choose Save.
You have saved the batch assignment.
4.2.5
Assign Serial Numbers with Fiori Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you carry out serial number assignment for the materials in the delivery document.

Appendix
CUSTOMER
24
Prerequisites
You can only execute this step for a material with serial number assignment.
Example
Material H20.
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Check Batches

Assign Serial Numbers
transaction

Check Batches Assign Serial Numbers.

numbers.
2.

Number


of the delivery.
3.

Batch Split
Select an item for which a serial number is maintained.

split.
Pass / Fail /
Comment
Example
Material H20.
4.
Display Batch Split
Choose Batch Split.

of the batch split.
5.
Select Item for Batch

Assignment
In Batch Structure for Item <item number>, choose the

item for the batch assignment.
You have selected the batch for serial

assignment.
Note
The item with the batch number has batch
number displayed in Batch column.
6.
Create Serial
Assignments

Appendix
Choose Create Serial Assignments.
You have created serial assignments for

the delivery order.
CUSTOMER
25
4.2.6
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Warehouse Clerk
Responsibility
Testing Date

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
#
Test Step Name
Instruction
Expected Result
1.
Start Post Goods Issue

transaction

Post Goods Issue.

posting goods issue.
2.
Enter Shipping Point
In Shipping Point/Receiving Point, enter the value for

<Shipping Point> and choose Execute.
The list of outbound deliveries to be

posted is displayed.
Example
Enter 1000 for Shipping Point/Receiving Point.
3.
Select Order for Goods

Issue

Appendix
Pass / Fail /
Comment
Caution
The list is displayed in ALV
format.
Select the delivery order and choose Post Goods Issue.

CUSTOMER
26
Test Step
#
Test Step Name
Instruction
Expected Result
4.
Specify Actual Goods

Issue Date
Choose todays date in the dialog box and choose

Continue.
You have posted the goods issue for the

outbound delivery.
4.2.7
Pass / Fail /
Comment
Create Billing with Fiori Flavor
Test Administration
Test Case ID
<X.XX>
Tester Name
Business Roles
Responsibility
Testing Date

date.
Duration
5 Minutes
Purpose
In this process step you handle the billing for the order.
Procedure
Test Step
#
Test Step Name
Instruction
Expected Result
1.
Start Create Billing

transaction

Create Billing.

billing.
2.
Search for Billing

Documents
Enter the relevant search criteria and choose Display

billing list.

displayed.
Pass / Fail /
Comment
Example
Enter dates in Billing Date From and to in order
Appendix
CUSTOMER
27
Test Step
#
Test Step Name
Instruction
Expected Result
Pass / Fail /
Comment
to search for documents according to date.

3.
Create Individual Billing

Document
Select the respective billing document and choose

Individual billing.
The Create Invoice screen is displayed.
4.
Create Invoice
In Create Invoice: Overview of Billing Items, choose

Save.

displayed.
Note
The status of the document is
displayed as OK (icon with
green tick).
5.
Leave Billing

Appendix
Choose Back twice to return to the landing page.
You have created an invoice for the

order.
CUSTOMER
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
Best Practices for SAP Screen

Personas Development (UP0)
Development of SAP Screen Personas flavors.

Appendix
CUSTOMER
29

Appendix
CUSTOMER
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
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 .

Appendix
CUSTOMER
31
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 SEs 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.

Up1 Scrp30 BPD en XX

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Up1 Scrp30 BPD en XX

Hochgeladen von

Copyright:

Verfügbare Formate

Test Script

SAP Screen Personas 3.0

Sales Order Processing with SAP Screen

Sales Order Processing with SAP Screen Personas

Sales Order Processing with SAP Screen Personas

Generic Example Flavors

Sales Order Processing with SAP Screen Personas

Association to Sales Order Processing: Sell from Stock (109)

System Access and Roles

The test is conducted in the following systems:

<Provide details on how to access system, e.g. system client or URL>

Business Role Description

Employee (Professional User)

Assignment of this role is necessary

Test user: <userid>

Assignment of this role is necessary

SAP Screen Personas standard

Test user: <salesperson_userid>

Test user: <warehouse_clerk_userid>

Test user: <billing_userid>

Business Role Description

Master Data, Organizational Data, and Other Data

Trading Good for Reg. Trading (MRP

no Serial no.; no batch

Trading Good for Reg. Trading

Trading Good for Reg. Trading

You must have activated Serial Number

Trading Good for Reg. Trading

Sales Order Processing with SAP Screen Personas

You must have activated Batch Management.

Batch Management (117).

Trading Good for Reg. Trading

You must have activated Batch Management.

Batch Management (117).

Finished Good MTS for Process

You must have activated Batch Management.

Batch Management (117).

Finished Good MTS for Discrete

You must have activated Serial Number

You can test the scope item using another

Sales Order Processing with SAP Screen Personas

Sales Order Processing with SAP Screen Personas

Start Sales Order Processing Landing

Create Sales Order with Generic Example

Sales Order is created.

Create Delivery with Generic Example

Delivery is created. The Warehouse Transfer Order is

Check Batches and Assign Serial

Post Goods Issue with Generic Example

The goods issue is posted.

Create Billing with Generic Example

Billing is carried out.

Start Sales Order Processing Launchpad

Create Sales Order with Fiori Flavor

Sales Order is created.

Create Delivery with Fiori Flavor

Delivery is created. The Warehouse Transfer Order is

Check Batches and Assign Serial

Post Goods Issue with Fiori Flavor

The goods issue is posted.

Create Billing with Fiori Flavor

Billing is carried out.

Sales Order Processing with SAP Screen Personas