October 2014August 2000
EnglishEnglish
SAP Fiori Apps for SAP ERP - Human Capital Management (HCM) (MEY)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Test Script
© SAP SE Public Page 4 of 33
SAP Best Practices SAP Fiori Apps for SAP ERP - Human Capital Management (HCM) (MEY): Test Script
Icons
Icon / Meaning/ Caution
/ Note
Typographic Conventions
Icon / MeaningExample text / Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Example text / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> / Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
Copyright
© 2014 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/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 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 SE’s 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.
Contents
1 Purpose 5
2 Prerequisites 5
3 My Leave Requests 6
4 My Timesheet 11
5 My Paystubs 16
6 My Benefits 20
7 Approve Leave Request 24
8 Approve Timesheets 29
SAP Fiori Apps for SAP ERP - Human Capital Management (HCM)
1 Purpose
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 (i.e. test steps) in a table view.
The following SAP Fiori apps are described in this document:
SAP Fiori app / Business Role /My Leave Requests / Employee
My Timesheet / Employee
My Paystubs / Employee
My Benefits / Employee
Approve Leave Request / Manager
Approve Timesheets / Manager
2 Prerequisites
· Before using SAP Fiori applications, you must install the prerequisite building blocks.
· Users must be assigned to the predefined Launchpad role for your SAP Fiori application.
For launching the home page, use the appropriate URL.
http://<Gatewayhost>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html
3 My Leave Requests
3.1 Purpose
The purpose of this app is to describe the process for employees to manage their leave requests.
3.2 Process Overview Table
Process Step / Business Condition / Business Role / Expected Results /Launch Home page / Employee / The Home page with all the applications the user has assigned is displayed in a tiled layout.
Launch App My Leave Request / Employee / The submenus Request Leave, History and Leave Overview are shown
Create New Leave Request / Employee / A new leave request is submitted.
Manage Existing Leave Request / Employee / You have viewed, edited or withdrawn an existing leave request.
Check Leave Balance / Employee / You have accessed the account balance
3.3 Testing the Process Steps in the SAP Fiori App
This section describes test procedures in the frontend for each process step that belongs to this scope item.
Test Step # / Test Step Name / Instruction / User Entries:Field Name: Value / Expected Result / Pass / Fail / Comment /
1 / Add-on verification / Check backend ERP and Gateway system and determine if the required add-ons and SAP notes are installed. / UIHCM002 100 (UI Component); GBHCM002 (ABAP Gateway Component + SAP Notes)
2 / Launch Home Page / Launch the SAP Fiori home page via the appropriate URL (https://> >…) and logon with the appropriate user and password. / Home Page is displayed.
3 / Launch My Leave Requests application / Touch "My Leave Requests" tile on the home page. / Further options: Request Leave, History, and Leave Overview are shown.
4 / Create a new leave request / 1. Touch "Request Leave" tile.
2. Select a leave type from the drop-down box. The information of the
related time quota with used and available days is displayed.
3. Choose a day or period of time in the calendar view.
4. Enter additional details like start and end time if the leave type
requires this.
5. Add a comment for example for the approver in the Note field.
6. Choose "Send". The request will be validated.
7. On the dialog popup choose "Send" to confirm the request.
Note: If any approval is required the request is also sent to the manager and will be shown in the corresponding app Approve Leave Requests. / Leave Request is created.
5 / View an existing leave request / 1. Choose "Home page" again. On History tile the number of
pending requests is shown.
2. Touch "History" tile to view the already created requests.
3. The list shows the approved and pending leave requests
with leave type, time frame and duration.
Note: Leave requests in status Approved can only be withdrawn, the requests in status Sent can be also changed. / Leave Request details are displayed.
6 / Edit an existing leave request / 1. Choose one of the sent leave requests from the list.
Additional information are displayed.
2. Choose "Change" and adapt the any data like date/time period.
3. Choose "Send". The request will be validated.
4. On the dialog pop-up choose "Send" to confirm the request.
Note: If any approval is required the request is also sent to the manager again and will be shown in the corresponding app Approve Leave Requests. / Leave Request is edited.
7 / Withdrawn an existing leave request / 1. Choose one of the listed leave requests, status "Sent"
or "Approved".
2. Choose "Withdraw".
3. On the dialog popup choose "Withdraw" again to confirm.
/ Leave Request is withdrawn.
8 / Check Leave Balance / 1. Choose Home Page again. On "Leave Overview" tile
the available days of the default leave quota are shown.
2. Touch "Leave Overview" tile to check the current leave balance. The list provides the following information:
-Leave quota type
-Available hours/days
-Entitlement in hours/days.
/ Time account balance is displayed.
3.4 Testing the Process Steps in the Backend
This section describes the underlying SAP backend process. It describes the source of the data for the app. In addition, it is a way to check if the app is properly connected by changing data in the SAP system and checking if these changes are subsequently displayed by the app.
Test Step # / Test Step Name / Instruction / User Entries:Field Name: Value / Expected Result / Pass / Fail / Comment /
1 / Check new leave request / 1. Execute transaction PTARQ.
2. Type in a personnel number.
3. Choose Test Application.
4. On the Test Report for the UIA Interface for Leave Requests
screen, choose Display List of Requests.
5. Choose Execute (F8).
6. Search for the new created entry based on start/end date.
7. Choose "Details".
/ The new leave request is displayed.
2 / Display existing leave requests / 1. Execute transaction PTARQ.
2. Type in a personnel number.
3. Choose Test Application.
4. On the Test Report for the UIA Interface for Leave Requests
screen, choose Display List of Requests.
5. Choose Execute. / The list of employee's leave requests is displayed.
3 / Display edited leave request / 1. Execute transaction PTARQ.
2. Type in a personnel number.
3. Choose Test Application.
4. On the Test Report for the UIA Interface for Leave Requests
screen, choose Display List of Requests.
5. Choose Execute.
/ The existing leave request is modified.
4 / Recall a leave request / 1. Execute transaction PTARQ.
2. Type in a personnel number.
3. Choose Test Application.
4. On the Test Report for the UIA Interface for Leave Requests
screen, choose Display List of Requests.
5. Choose Execute. / The existing leave request is recalled.
5 / Display Leave Balance / 1. Select Back.
2. On the Test Report for the UIA Interface for Leave Requests screen, choose Time Accounts.
3. Select "Display All Data".
4. Choose Execute. / The list of employee's time accounts is displayed.
4 My Timesheet
4.1 Purpose
The purpose of this app is to describe the process for employees to manage time entry data.
4.2 Prerequisites
My Timesheet uses the Data Entry Profile to determine the usage and behavior for the client. The Data Entry Profile must be maintained for each user in the CVR parameter.
To set the Data Entry Profile, from the SAP GUI, go to System ® User Profile ® Own Data.
4.3 Process Overview Table
Process Step / Business Condition / Business Role / Expected Results /Launch Home page / Employee / The Home page with all the applications the user has assigned is displayed in a tiled layout.
On My Timesheet tile the number of days without time recording is shown.
Launch App My Timesheet / Employee / The My Timesheet page is displayed with a calendar view.
Check Missing Time Recordings / Employee / The calendar is checked for missing entries.
Create, Modify or Delete Time Recordings manually / Employee / You have created, modified, or deleted time recordings.
Create New Time Recordings with Auto Entry / Employee / You have created time recordings with auto-fill.
4.4 Testing the Process Steps in the SAP Fiori App
This section describes test procedures in the frontend for each process step that belongs to this scope item.
Test Step # / Test Step Name / Instruction / User Entries:Field Name: Value / Expected Result / Pass / Fail / Comment /
1 / Add-on verification / Check backend ERP and Gateway system and determine if the required add-on is installed. / UISRA002 100 (UI Component); SRA002 600 (ABAP Gateway component)
2 / Launch Home Page / Launch the SAP Fiori home page via the appropriate URL (https://> >…) and logon with the appropriate user and password. / Home Page is displayed. On "My Timesheet" tile the number of missing days, days without time recording, is shown.
3 / Launch My Timesheet application / 1. Touch "My Timesheet" tile on the home page.
The My Timesheet page is displayed with a calendar view. The calendar view highlights for example:
- Days with time recording (Done)
- Days without time recording where action is required (Your Action Needed)
- Days with time recording for approval (Approver Action Needed)
Today is selected.
Note: To view your assigned data entry profile, choose the Gearwheel icon at the bottom of the page. In the dialog box, select Settings. The data entry profile is displayed.
Choose Auto Suggest if you like to get automatically suggested time entries per week based on the previous filled week. This helps employees with recurring times to have a starting point rather than start from a blank screen. / Calendar screen is displayed. The time recording status for a day is displayed by color.
4 / Check existing time recordings / 1. Click one a specific week/day in the calendar or choose Manual Entry to enter time data.
2. Choose an listed entry.
3. Note the following data:
-Cost Assignment (for example: attendance/absence type,
activity type, receiver WBS, and so on )
-Duration
-Note
/ The overview of time recordings per week is displayed in the calendar.
5 / Create a new time recording / 1. Click one a specific week/day in the calendar.
2. Choose the "Plus" icon in the header or New Entry below
the corresponding date to add an entry.
3. Add the entry and hit submit.
4. Note the following data:
-Cost Assignment (that is:. attendance/absence type,
activity type, receiver WBS, and so in )
-Duration (the planned hours are suggested)
-Note
/ A new time recording is created in the backend.
6 / Modify a time recording / 1. Click one a specific week/day in the calendar
where already entries exist.
2. Choose one of the existing entries. Adapt the values.
3. Hit "Submit".
4. Note the following data:
-Cost Assignment (that is: attendance/absence type,
activity type, receiver WBS, and so in )
-Duration
-Note
/ The time recording is modified in the backend
7 / Delete a time recording / 1. Click one a specific week/day in the calendar
where already entries exist.
2. Choose one of the existing entries.
3. On the Entry Details dialog popup the details
are displayed.
4. Choose "Delete" to remove the entry.
5. Choose "Submit" to save.
/ The time recording is deleted in the backend
8 / Create time recordings using auto entry / 1. On the My Timesheet page choose "Auto Entry".
2. The default cost assignment and the sum of
all missing time (in hours based on the planned time) are
shown.
3. Choose "Submit" to create the missing recordings in one step.
/ All missing time recordings are created in the backend.
4.5 Testing the Process Steps in the Backend
This section describes the underlying SAP backend process. It describes the source of the data for the app. In addition, it is a way to check if the app is properly connected by changing data in the SAP system and checking if these changes are subsequently displayed by the app.