close

Вход

Забыли?

вход по аккаунту

Business Process Procedures

код для вставкиСкачать
EHP7 for SAP ERP 6.0
August 2014
English
Take Action: Promotion/Demotion (FJ2)
Test Case
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Icons
Icon
Meaning
Caution
Note
Recommendation
External Process
Typographic Conventions
Icon
Meaning
Example 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.
© SAP AG
Page 2 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
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.
© SAP AG
Page 3 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Content
1
2
Purpose ................................................................................................................................................................................................................... 5
1.1
Purpose of the Document ................................................................................................................................................................................ 5
1.2
Purpose of Take Action: Promotion/Demotion ................................................................................................................................................ 5
Prerequisites ........................................................................................................................................................................................................... 5
2.1
Configuration ................................................................................................................................................................................................... 5
2.2
System Access ................................................................................................................................................................................................ 6
2.3
Roles ................................................................................................................................................................................................................ 6
2.4
Master Data, Organizational Data, and Other Data ........................................................................................................................................ 6
2.5
Business Conditions ........................................................................................................................................................................................ 6
3
Overview Table ....................................................................................................................................................................................................... 7
4
Testing the Process Steps ...................................................................................................................................................................................... 8
4.1
Logging on, Searching and Selecting Employee ............................................................................................................................................. 8
4.2
Entering Promotion Data ................................................................................................................................................................................. 9
4.3
Entering Demotion Data ................................................................................................................................................................................ 12
4.3.1
4.4
5
Updating Employee Master Data Record in EC Payroll ......................................................................................................................... 15
Viewing Personnel Master Data .................................................................................................................................................................... 15
Follow-Up Process: Payroll and Post-Payroll Processing .................................................................................................................................... 17
© SAP AG
Page 4 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Take Action: Promotion/Demotion
1 Purpose
1.1 Purpose of the Document
This document provides a detailed procedure for testing the scope item Take Action: Promotion/Demotion 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. Steps that are not in scope of the process but are needed for testing are marked accordingly (see column Test Step). Customer-projectspecific steps must be added.
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.
1.2 Purpose of Take Action: Promotion/Demotion
This document describes the use of the actions Promotion or Demotion which can be executed as an event for an employee within an
organization. In the SuccessFactors system the button Take Action is used to navigate to the drop down menu to select Change Job and
Compensation Information for employees. The Job Information is used for these events.
An HR manager with the adequate permissions will be able to enter a Promotion or a Demotion for an employee within an organization. And
depending on the configuration there may be an approval workflow that is triggered.
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 Configuration
© SAP AG
Page 5 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Please ensure to follow the correct installation sequence of building blocks as specified in the Prerequisite Matrix.
2.2 System Access
The test should be conducted with the following system and users:
Type of Data
Details
System
SuccessFactors EC
<Provide details on how to access system, e.g. system client or URL>
Standard User
HR Manager
<Provide Standard User Id and Password for test, if applicable>
System
EC Payroll
<Provide details on how to access system, e.g. system client or URL>
Standard User
HR Administrator
<Provide Standard User Id and Password for test, if applicable>
2.3 Roles
For non-standard users, the following roles must be assigned in SuccessFactors to the system user(s) testing this scenario. The permission roles
are predelivered.
Business Role
Permission Role
Process Step
Sample data
HR Manager
Super_Admin
Refer to chapter 3 Overview Table
Provide Best practice Standard User Id and Password
for test, if applicable
2.4 Master Data, Organizational Data, and Other Data
The organizational structure and master data of your company has been created in your system during implementation. The organizational
structure reflects the structure of your company and includes the company, cost center and location in the system. It is part of the corporate data
model and is predelivered as a starting point in Employee Central.
2.5 Business Conditions
Before this scope item can be tested, the following business conditions must be met.
1
Business Condition
Comment
Employees must have been hired and already exist in the system.
Refer to scope item Add New Employee (FJ0)
© SAP AG
Page 6 of 17
SAP Best Practices
2
Take Action: Promotion/Demotion (FJ2): Test Case
Business Condition
Comment
One administrator user with the complete access to all employee
views and fields must exist.
Permission Role Super_Admin can be used as reference.
3 Overview Table
The scope item Take Action: Promotion/Demotion consists of several process steps provided in the table below.
Process Step
UI Type
Business Condition
Business
Role
Enter
Promotion
Data
Success
Factors
An employee is promoted.
HR Manager
Update
Employee
Master Data
Record in EC
Payroll
Background
View Personnel
Master Data
EC
Payroll
Master data of the employee has
been transferred successfully to EC
Payroll.
HR
Administrator
Enter
Demotion Data
Success
Factors
An employee is demoted.
HR Manager
Update
Employee
Master Data
Record in EC
Background
© SAP AG
Transaction
Code /
Program /
Job
Expected Results
The promotion data for an employee has
been entered into the system. The
updates to the employee are done
immediately and the change is reflected in
the system.
After the changes have taken affect, the
master data record of the employee has
been updated automatically in EC Payroll.
PA20
The updated master data record of the
employee is viewed.
The demotion data for an employee has
been entered into the system. The update
to the employee is done immediately and
the change is reflected in the system.
After the changes have taken affect, the
master data record of the employee has
been updated automatically in EC Payroll.
Page 7 of 17
SAP Best Practices
Process Step
Take Action: Promotion/Demotion (FJ2): Test Case
UI Type
Business Condition
Business
Role
Transaction
Code /
Program /
Job
Expected Results
EC
Payroll
Master data of the employee has
been transferred successfully to EC
Payroll.
HR
Administrator
PA20
The updated master data record of the
employee is viewed.
Payroll
View Personnel
Master Data
4 Testing the Process Steps
This section describes test procedures for each process step that belongs to this scope item.
The test should take 1 hour.
4.1 Logging on, Searching and Selecting Employee
Purpose
In the SuccessFactors system, the HR manager will need to log on to the system. Once in the system, he or she can search and select the
appropriate employee.
The Take Action: Promotion/Demotion processes covered in this document will refer to the navigation steps included in this section.
Procedure
Depending on the configuration, there may be several ways to search and select an employee as well as how to access the Take Action
pushbutton. In this guide we are covering two of these options, accessing it via the People Search box and via the My Employee File in the Links
section on the Home page.
Test
Step
#
Test Step
Name
© SAP AG
Instruction
Additional
information
Expected Result
Pass / Fail /
Comment
Page 8 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Test
Step
#
Test Step
Name
Instruction
1
Log on
Log on to SuccessFactors as an HR
manager.
The Home page is
displayed.
2
Search for
Employee
Option 1: In the People Search box, enter
the name of the employee.
The system proposes the
employees matching the
search criteria.
Option 2: From the Home drop down select
the My Employee File.
The Employee Files for
<HR manager user> is
displayed
Option 1: In the search results, using the
mouse hover over the name.
The employee’s business
card is displayed.
Option 2: On the My Employee File: <HR
manager user> screen select the drop down
arrow: In the Search box enter the name of
the employee and select the employee.
The Employees Files for
the employee is displayed.
3
4
Select
Employee
Select Take
Action
Pushbutton
Option 1: In the employee’s business card
select the Take Action drop down menu.
Option 2: In the My Employee File for
employee, select the Take Action
Pushbutton.
Additional
information
To continue the
process, please see
the section Enter
Promotion or Enter
Demotion.
Expected Result
Pass / Fail /
Comment
The Take Action menu is
displayed.
4.2 Entering Promotion Data
Purpose
It is time for an employee to be promoted within an organization. The reasons for an employee’s promotion can be due to a normal career
progression, due to outstanding performance, or for other reasons. The HR manager enters the corresponding data for the promotion.
© SAP AG
Page 9 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Procedure
In the following we mention the mandatory fields as well as some filled typical in a promotion. The mandatory fields to be filled (they are marked
with a red asterisk on the screen) and those optional fields which need to be filled in order to achieve a meaningful employee master data record.
Depending on the configuration, there are several ways to navigate to the Take Action pushbutton. In the following business process we start the
Promotion event from the Take Action pushbutton by selecting the Change Job and Compensation Info. For logging on to the system, searching
and selecting an employee please see the previous section.
Additionally, only the mandatory fields to be filled (they are marked with a red asterisk on the screen) and those optional fields which may need to
be entered in order to achieve a meaningful employee master data record listed below.
Test
Step
#
Test Step
Name
Instruction
1
At the Take
Action
Pushbutton
2
Enter the Type
of Change Job
and
Compensation
Info for
Employee
© SAP AG
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected
Result
From the Take
Action drop
down menu and
from the value
list select
Change Job and
Compensation
Info.
The Take Action
button is located on
the very right of the
screen.
The type of
Change Job
and
Compensation
Info can be
selected.
Option 1: Select
the option Job
Information.
The Job
Information portlet
is displayed.
When do you
want your
changes to
take
effect/Event
and the
Compensation
Information is
displayed.
Option 2: Select
the option
Compensation
Info.
The Compensation
Information portlet
is displayed.
When do you
want your
changes to
take
effect/Event
Pass / Fail /
Comment
Page 10 of 17
SAP Best Practices
Test
Step
#
Test Step
Name
Take Action: Promotion/Demotion (FJ2): Test Case
Instruction
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected
Result
Pass / Fail /
Comment
and the
Compensation
Information is
displayed.
3
4
Enter When Do
You Want The
Changes to
Take Effect and
Select Event
Enter
Compensation
Info
In the
Compensation
Info portlet enter
the required
fields that are
needed to track.
When do you
want your
changes to take
effect:
Select a value from
the calendar help.
*Event:
Select Promotion
from drop-down list.
*Event Reason:
Select the reason
for the Promotion
from the drop-down
list. For example
Promotion - Pay
Change
(PROPWP).
Example fields
could include:
Pay Group
Amount
Today’s date is
default date or
enter the date in
mm/dd/yyyy or
select the calendar
to select month,
day and year.
The effective
date is set.
The Event
type
Promotion is
selected.
The possible values
for Event Reason
are dependent on
the Event type
defined in the
system for
Promotion.
The Event
Reason is
selected for
the Promotion.
After entering the
new values, the old
values are
displayed crossed
out.
You are ready
to submit the
Promotion for
the employee.
Currency
Frequency
© SAP AG
Page 11 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Test
Step
#
Test Step
Name
Instruction
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected
Result
5
Submit Data
Choose the
Submit
pushbutton.
You are
proceeded to
the
Compensation
Information tab
in the Take
Action:
Promotion
screen.
6
Check My
Employee File
Job
Information
Portlet
In the Job
Information
portlet, check
that the changes
are displayed.
Check that the
new values
are now
effective for
the employee.
Pass / Fail /
Comment
4.3 Entering Demotion Data
Purpose
A demotion for an employee may be for unsatisfactory performance, lack of skills or other reasons. This may or may not affect the pay or grade of
the employee. An employee’s demotion is entered by the HR Manager.
If a workflow is configured in the system for a promotion or demotion, an approval request will be triggered upon submitting the promotion or
demotion for an employee.
Procedure
In the following we mention the mandatory fields as well as some filled typical in a promotion. The mandatory fields to be filled (they are marked
with a red asterisk) and those optional fields which need to be filled in order to achieve a meaningful employee master data record.
Depending on the configuration, there are several ways to navigate to the Take Action pushbutton. In the following business process we start the
Demotion event from the Take Action pushbutton by selecting the Change Job and Compensation Info. For logging on to the system, searching
and selecting an employee please see the previous section.
© SAP AG
Page 12 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Additionally, only the mandatory fields to be filled (they are marked with a red asterisk on the screen) and those optional fields which may need to
be entered in order to achieve a meaningful employee master data record listed below.
Test
Step
#
Test Step Name
Instruction
1
At the Take
Action
Pushbutton
From the Take
Action drop down
menu and from the
value list select
Change Job and
Compensation Info.
2
Enter the Type
of Change Job
and
Compensation
Info for
Employee
Option 1: Select the
option Job
Information.
The Job
Information portlet
is displayed.
The portlets
When do you
want your
changes to take
effect/Event and
the
Compensation
Information is
displayed.
Option 2: Select the
option
Compensation Info.
The Compensation
Information portlet
is displayed.
The portlets
When do you
want your
changes to take
effect/Event and
the
Compensation
Information is
displayed.
Today’s date is
default date or
enter the date in
mm/dd/yyyy or
select the calendar
to select month,
The effective
date is set.
3
4
Enter When Do
You Want The
Changes to
Take Effect and
Select Event
© SAP AG
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected Result
Pass / Fail /
Comment
The type of
Change Job and
Compensation
Info can be
selected.
When do you
want your
changes to
take effect:
Select a value from
the calendar help.
Page 13 of 17
SAP Best Practices
Test
Step
#
Test Step Name
Take Action: Promotion/Demotion (FJ2): Test Case
Instruction
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected Result
Pass / Fail /
Comment
day and year.
5
Enter
Compensation
Info
In the
Compensation Info
portlet enter the
required fields that
are needed to
track.
*Event:
Select Demotion
from drop-down list.
*Event
Reason:
Select the reason
for the Demotion
from the drop-down
list. For example
Demotion –
Unsatisfactory
Performance
(DEMOPERF).
Example
fields could
include:
Pay Group
The Event type
Demotion is
selected.
The possible values
for Event Reason
are dependent on
the Event type
defined in the
system for
Demotion.
The Event
Reason is
selected for the
Demotion.
After entering the
new values, the old
values are
displayed crossed
out.
You are ready to
submit the
Demotion for the
employee.
Amount
Currency
Frequency
6
Submit Data
© SAP AG
Choose the Submit
pushbutton.
You are
proceeded to the
Compensation
Information tab in
the Take Action:
Demotion screen.
Page 14 of 17
SAP Best Practices
Take Action: Promotion/Demotion (FJ2): Test Case
Test
Step
#
Test Step Name
Instruction
7
Check My
Employee File
Job Information
Portlet
In the Job
Information portlet,
check that the
changes are
displayed.
4.3.1
Field Name:
Description
User Entries:
Field Name: User
Action and Value
Additional
information
Expected Result
Pass / Fail /
Comment
Check that the
new values are
now effective for
the employee.
Updating Employee Master Data Record in EC Payroll
Purpose
A batch job is scheduled in BOOMI on a regular basis that replicates the employee’s changed master data from SuccessFactors EC to EC Payroll.
The employee’s master data record is updated automatically in EC Payroll and can be viewed by the HR Administrator.
4.4 Viewing Personnel Master Data
Purpose
The HR administrator (PA) views the updated master data of the employee as it is transferred from SuccessFactors EC. For this he or she uses
the Display or Overview function.
Before displaying the data, the HR Administrator specifies which infotype is to be viewed for which employee.
Procedure
Test
Step
#
Test Step
Name
Instruction
1
Log on
Log on to EC Payroll as HR
Administrator and enter
transaction code PA20.
The Display HR Master Data
screen is displayed.
2
Search
Employee
On the Display HR Master Data
screen, in the Personnel no. field
select the value help on the right
The system proposes a list of
employees matching your search
© SAP AG
Additional Information
Expected Result
Pass / Fail /
Comment
Page 15 of 17
SAP Best Practices
Test
Step
#
3
Test Step
Name
Select
Employee
Take Action: Promotion/Demotion (FJ2): Test Case
Instruction
Additional Information
Expected Result
hand side of this field to search
for the appropriate employee by
first/last name. Press ENTER.
criteria.
Click in the list of employees the
appropriate employee.
The personnel number of the
employee is taken over in the
Personnel No. field. Press ENTER.
Pass / Fail /
Comment
A short profile of the employee is
displayed, containing name,
employee group/subgroup,
personnel area and cost center.
On the Display HR Master Data
screen, the infotypes in the
different tabs for which data is
stored in the system are marked
with a green check mark.
4
Select
Infotype
Enter the name or number of the
infotype in the Infotype field
located in the Direct selection part
on the screen.
You can also use the value help
next to the Infotype and STy fields
located in the Direct selection part
on the screen.
Relevant infotyes are:
 Actions (IT0000)
 Organizational Assignment
(IT0001)
 Planned Working Time
(IT0007)
 Basic Pay (IT0008)
5
View
Infotype
Record
Choose the Display button to view
the infotype record. Choose Next
record pushbutton to proceed to
the next record of this infotype.
Choose Previous record
pushbutton to go back.
If no subsequent record for
the chosen infotype exists,
the system message “No
subsequent record for
current selection criteria” is
generated.
6
View List
Alternatively, you can display a
Check that in the newest
© SAP AG
Page 16 of 17
SAP Best Practices
Test
Step
#
Take Action: Promotion/Demotion (FJ2): Test Case
Test Step
Name
Instruction
Additional Information
of all Valid
Records
for an
infotype
and its
Subtypes
list of all valid records for an
infotype and its subtypes. For this,
choose the Overview button on
the Display HR Master Data
screen. A list of all valid records
for this infotype is displayed. If
you want to display one of the
available records in this list, select
the record of interest and choose
the Choose button.
record of the relevant
infotypes the data changes
made are reflected.
Expected Result
Pass / Fail /
Comment
5 Follow-Up Process: Payroll and Post-Payroll Processing
External Process
Using the data transferred from SuccessFactors EC, payroll and post payroll processing can take place in EC Payroll.
© SAP AG
Page 17 of 17
1/--страниц
Пожаловаться на содержимое документа