Sie sind auf Seite 1von 14

Test Script CUSTOMER

SAP S/4HANA - 06-09-16

Emergency Maintenance (BH2_US)

Table of Contents

1 Purpose 3

2 Prerequisites 4
2.1 System Access 4
2.2 Roles 4
2.3 Master Data, Organizational Data, and Other Data 4
2.4 Business Conditions 5
2.5 Preliminary Steps 6
2.5.1 Initial Material Stock 6

3 Overview Table 7

4 Test Procedures 8
4.1 Confirm Unplanned Job 8
4.2 Technically Complete Maintenance Order 10

5 Appendix 12
5.1 Process Integration 12
5.1.1 Preceding Processes 12
5.1.2 Succeeding Processes 12
Emergency Maintenance (BH2_US) CUSTOMER
Purpose © 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
1 Purpose

The Emergency Maintenance scope item uses order recording after an event to log unforeseen and urgent maintenance work by creating and confirming an order in the same work step. The
technician can identify an issue affecting a piece of equipment, immediately fix the issue, and later reports the time spent and the material consumed. The technician enters the required data
quickly. The data can then be used for the planning objects (such as maintenance orders) and for actual recording (order confirmation, notification data, and goods movements). The planned
data does not differ from the actual data, that is the work recorded on an operation corresponds to the confirmed actual work.
The order is created, released, and if required, technically completed. In addition, you can install, dismantle, or replace pieces of equipment.
This document provides a detailed procedure for testing the scope item after solution deployment, reflecting the predefined scope of the solution. Each process step is covered in its own section,
providing the system interactions (that is, test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly (see the Test Step column).
Customer-project-specific steps must be added.

Emergency Maintenance (BH2_US) CUSTOMER


Purpose © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
2 Prerequisites

This section summarizes all prerequisites needed to conduct the test in terms of system, user, master data, organizational data, and other test data and business conditions.

2.1 System Access


The test should be conducted with the following system:

System Details

System Accessible via the 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.
The following roles are provided as example roles from SAP. You can use these as templates for your own roles.

Business Role Business Catalog Role ID Log On

Maintenance Planner SAP_BR_MAINTENANCE_PLANNER

Maintenance Technician SAP_BR_MAINTENANCE_TECHNICIAN

Warehouse Clerk SAP_BR_WAREHOUSE_CLERK

For more information about business roles, refer to Assigning business roles to a user in the Administration Guide for the Implementation of SAP S/4HANA.

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:

Emergency Maintenance (BH2_US) CUSTOMER


Prerequisites © 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Data Sample Value Details Comments
Equipment 217100091 Cooling Water Circulation Pump

Spare Parts Material SP001 Bearing

Spare Parts Material SP002 Coupling

Spare Parts Material SP003 Shaft

Spare Parts Material SP004 Gaskets 1mm

Spare Parts Material SP005 Mechanical Seal

Spare Parts Material SP006 Spur gear IS651

Plant 1710 Plant 1 US

Storage Location 171B Std. storage 2

2.4 Business Conditions


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

Business Condition Comment

To complete this scope item, the materials must be available in


stock

BNZ Open New MM Period You have completed the step described in the Open New MM Period(BNZ) master data script. Posting Period is up to
date.

Emergency Maintenance (BH2_US) CUSTOMER


Prerequisites © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
2.5 Preliminary Steps

2.5.1 Initial Material Stock

Procedure

In a real business case, the materials are usually purchased from external vendors that can be covered by the standard purchasing processing or subcontracting processing. Here we post initial
stock directly to the storage locations.

Test Test Step Name Instruction Expected Result Pass / Fail /


Step # Comment
1 Log onto SAP Fiori Log onto the SAP Fiori Launchpad as a The SAP Fiori Launchpad displays.
Launchpad Warehouse Clerk.

2 Access the App Open Post Goods Movement. The Post Goods Movement screen displays.

3 Choose Goods Re- Choose Goods Receipt-Other, set the


ceipt-Other movement type as 561

4 Specify Material Enter the material number For a detailed materials list, refer to Master Data, Organizational Data, and Other Data [page ]
4, except for Equipment 217100091, the other materials need to conduct initial stock.

5 Specify Quantity Enter the quantity

6 Specify Plant and Specify the plant 1710 and storage lo-
Storage Location cation 171B for all of materials.

7 Check Click Check. Document is OK.

8 Post Click Post. Material document XXX posted.


Materials are available in stock.

Emergency Maintenance (BH2_US) CUSTOMER


Prerequisites © 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
3 Overview Table

The scope item Emergency Maintenance consists of several process steps provided in the table below.

Process Step, Report or Item Business Role Transaction/App Name Expected Results
Confirm Unplanned Job [page ] 8 Maintenance Techni- Confirm Jobs Unplanned job is confirmed incl. time recording, confirming ma-
cian terial used.

Technically Complete Maintenance Order Maintenance Planner Manage Orders and Notifications in Information Maintenance Order is technically completed
[page ] 10 Center

Emergency Maintenance (BH2_US) CUSTOMER


Overview Table © 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
4 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

4.1 Confirm Unplanned Job

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.

Purpose

After Event recording or confirm unplanned job suites the purpose that an event has occurred which requires quick and immediate intervention from the maintenance technician. In such an
emergency, the maintenance technician performs the required maintenance activity to restore the condition of the equipment. Maintenance technician identifies an issue at a piece of equip-
ment, immediately fixes the issue and reports later the time spent and the material consumed. Very often he is not able to identify the equipment number and searches along the hierarchy of the
Functional Location.

Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1. Log onto SAP Fiori Log onto the SAP Fiori Launchpad as a Maintenance Technician. The SAP Fiori Launchpad displays.
Launchpad

Emergency Maintenance (BH2_US) CUSTOMER


Test Procedures © 2016 SAP SE or an SAP affiliate company. All rights reserved. 8
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
2. Access the App Open Confirm Jobs. The Confirmation screen displays.

Enter Technical Object On the Confirmation screen. In the Confirm Unplanned Job area, make the
following entries:
Order Type: YBA1, Maintenance Order
Tech. Object: 217100091
Choose Create.

3. Confirm the times On the Confirm Unplanned Job screen. Go to the Confirmation Data tab.
In the Operation Data area, go to Confirmation Data tab.
In the Confirmation of Time Data area, make the following entries:
● Actual work: For example: 5 (5 hours)
● Start Date: <Date>
● Start Time: <Time>
● End Date: <Date>
● End Time: <Time>
● No Remaining Work: flag set

4. Confirmation of Material In the Confirmation of Material Used area, make the following entries:
used ● Material: SP001
● Quantity: For example: 1
● Plant: 1710
● Storage Location: 171B

5. Check Entries Choose Check Entries. Entries have been checked.

6. Save Choose Save. Order 4XXXXXX saved with notification


1XXXXXXX.

Emergency Maintenance (BH2_US) CUSTOMER


Test Procedures © 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
4.2 Technically Complete Maintenance Order

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.

Purpose

Both the maintenance notification and the maintenance order are settled after the required maintenance work has been performed. There are two related completion phases:
Technical completion
Business completion
The technical completion reduces all the purchase requisitions, open reservations, and capacities still outstanding for the maintenance order.
Nevertheless, the order can still continue to receive costs, for example, through invoice receipts for delivered and used materials, however it is blocked for all changes in the processing.
The order settlement transfers the costs incurred that were temporarily collected for the maintenance order, to the recipient, for example, to the cost center for the maintained object.
The business completion signifies that the order is completed in accounting terms. It cannot receive any further postings.
In our example, the order costs are settled to the assigned Workshop/Maintenance cost center using an all-inclusive cost element.An executed order must be completed in the system, to show
that the order has been processed. In the PM module, there are two types of completion, technical completion and business completion.
Technical completion shows that an order was technically successful or it can be viewed as technically completed by Plant Maintenance.
The following shows how technical completion works.

Emergency Maintenance (BH2_US) CUSTOMER


Test Procedures © 2016 SAP SE or an SAP affiliate company. All rights reserved. 10
Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

1. Log onto SAP Fiori Log onto the SAP Fiori Launchpad as a Maintenance Plan- The SAP Fiori Launchpad displays.
Launchpad ner.

2. Access the App Open Manage Orders and Notifications in Information Cen- The Order and Notification Information Center screen dis-
ter plays.

3. Get an overview of all Order In the Lists area, choose Maintenance Orders Order List-
Default (X)
Choose Refresh.

4. Choose order number Choose line of Maintenance Order number from the previ-
ous section.

5. Set Complete (Technically) Choose Set Order Status Complete Technically


status.

6. Save the Order On the Complete(Technically) screen, make the following The Complete (Technically) status for the maintenance or-
entries: der is done.
● Reference Date: <Date>
● Reference Time: <Time>
● Complete assigned Notification: flag set
Choose OK.

Emergency Maintenance (BH2_US) CUSTOMER


Test Procedures © 2016 SAP SE or an SAP affiliate company. All rights reserved. 11
5 Appendix

5.1 Process Integration

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


MDS: Open New MM Period ScopeItem_BusinessCondition

5.1.2 Succeeding Processes


After completing the activities in this test script, you can continue testing the following business processes:

Process Business Condition


Period-End Closing - Maintenance Orders A maintenance order technically completed as part of Emergency Maintenance

Emergency Maintenance (BH2_US) CUSTOMER


Appendix © 2016 SAP SE or an SAP affiliate company. All rights reserved. 12
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 .

Emergency Maintenance (BH2_US) CUSTOMER


Appendix © 2016 SAP SE or an SAP affiliate company. All rights reserved. 13
www.sap.com/contactsap

© 2016 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.