0% found this document useful (0 votes)
342 views67 pages

Confiion - Workbook - EC - Employee - Data - ECM - v4

This document provides guidance for completing a SuccessFactors configuration workbook. It explains that the workbook will be used to document configuration decisions for an implementation project. The customer is responsible for filling out the workbook sections and signing off on iterations. The consultant will then configure SuccessFactors based on the approved workbook. Key elements of the workbook like configuration items, customer input fields, and a sample data field table are described.

Uploaded by

Gunjan Shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
342 views67 pages

Confiion - Workbook - EC - Employee - Data - ECM - v4

This document provides guidance for completing a SuccessFactors configuration workbook. It explains that the workbook will be used to document configuration decisions for an implementation project. The customer is responsible for filling out the workbook sections and signing off on iterations. The consultant will then configure SuccessFactors based on the approved workbook. Key elements of the workbook like configuration items, customer input fields, and a sample data field table are described.

Uploaded by

Gunjan Shah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 67

Employee Central Employee Data Configur

Workbook

ACME Wheelies Corp.

Global Headquarters Contact Us


Toll Free: (800) 809
1500 Fashion Island Blvd. Suite 300 Phone: (650) 645-2
San Mateo, CA 94404 USA Fax: (650)645-209
www.successfactors.com
ta Configuration

Corp.

Contact Us
Toll Free: (800) 809-9920(800) 809-9920
Phone: (650) 645-2000(650) 645-2000
Fax: (650)645-2099(650) 645-2099
Table of Contents

Introduction Introduction
General Info General Info
Links Links
Configuration Decisions Jump to Tab…

General Settings General RBP Settings


Data Group
Biographical Info Biographical Info
Personal Info Personal Info
National ID National ID
Home Address Home Address
Employment Info - At Hire Employment Info - At Hire
Job Info Job Info
Roles and Groups Roles and Groups
Signoffs
Document Signoffs for each iteration Sign-Off
Appendices
LaVRePrS alizeprunchfys

Tasks
JUMP BACK TO TOC
Introduction

BizXpert Methodology Map (Overview)


Phase

Tasks

Lead determination Project Team Orientation Config / Req Refinement Integration Testing
Set Scope & Pricing Internal Kick-off Data Migration User Acceptance Testing
SOW Process – Functional Project Planning & Resource Extensions / Technical Go-Live Training
and Technical scope booking developments
Transition from Sales to PS Kickoff Meeting Data imports/exports
Provisioning Requirements Gathering [integrations]
Workshops Unit Testing / Config
Verification

Checkpoints [Checkpoints are milestones where all stakeholders of the implementation project agree that specific d
requirements and consequently that the project can continue.]

Sales to PS Configuration Integration Testin


Scope & Project
Transition Acceptance Acceptance
Readiness

Working with Your SuccessFactors Consultant

Together with your Professional Services Consultant you will explore and discuss each of the decision points described thro

Your SuccessFactors Professional Services Consultant is ready to guide you through the completion of this workbook. You
complete the workbook on your own or without our guidance. While you own the maintenance of the document so that y
the document together.

Once you have identified and recorded the configuration options that meet your needs we will ask you to sign-off on this c
of describing how you would like to see SuccessFactors configured by your Professional Services Consultant. Upon receipt
SuccessFactors to match your requests.

The SuccessFactors Empower methodology calls for three cycles, or iterations, where you can complete the workbook to d

You will use the workbook to record the configuration you have requested. Note that the signoff for configuration “receiv
final signoff of “production readiness”.
SuccessFactors Consultant Responsibilities
Explain the options available in the Configuration Workbook
Provide feedback and suggestions on the best ways to utilize SuccessFactors to accomplish the customer’s business objecti
Configure the SuccessFactors system to match the customer requests documented in the Configuration Workbook after si

[CUSTOMER] Responsibilities
Own the Configuration Workbook document
Complete the Configuration Workbook with guidance and explanation from the Consultant, filling in the pale yellow sectio
Sign the workbook before the Consultant makes any configuration changes

Note: The Configuration Workbook represents what you are requesting to see in the next iteration of the system. The syst
workbook and configures the system to match it.
Keys to using the Configuration Workbook

The workbook contains the following elements:

• Configuration Item Discussion – Wording following each section heading describing the configuration item and possible c
• Customer Input/Decision: . Individual choices are colored with a pale yellow background.
• General Requirements: Area where you may record other comments, requests, or choices relating to configuration
• Business Drivers: Area where you may record business decisions and logic about the configuration element
• Iteration Configuration Modifications: During iterations 2 and 3, this is an area where you may record modifications or c
General Notes

• This Configuration Workbook may make reference to products or services which are not part of your SuccessFactors agre
to you and what is not.
• This Configuration Workbook does not contain every possible configuration option. If it did, it would be 50 times bigger
frequently used features of SuccessFactors if they are a fit for your organization.
Description of Headings
Each foundation object consists of one or more fields. This column lists the technical IDs o
System Field Id
This is the text that appears in the user interface (UI). If you require an alternative label pl
SF Label
Fields can handle data of various types. The options are:

BIGDECIMAL and DECIMAL - Fields with these data types can handle mathematical opera
BOOLEAN - Fields like this can handle two options. On the UI, the most common options f
DATE - You can enter dates in fields of this type.
DOUBLE - Fields with this data type can handle decimal numbers.
Type LONG - Fields with this data type can only contain integers.
STRING - You can enter a string of characters in fields with this data type. Where there is a
characters allowed is shown in the Max Length column.

Max Length
Some fields with data type “String” have a limit on the number of characters you can ente
Used Do you want to see this field - values are Yes (means visibility = both), No (means visibility
Customer Label Alternative label to be displayed in place of SF Label
Required
(Mandatory) Whether it is mandatory to enter data into the field, i.e. it cannot be left blank.
List of Values Typical values - can be a picklist, system defined, foundation object, user list, etc
Decimal Precision If the field is a decimal, please specify a precision i.e. number of decimal places
ACME Requested
Change Whether ACME would like to change this field.
Comments Explantory comment about purpose of the field

Example
Customer Label (specify
Iteration 2 Change

Iteration 3 Change

Biogra

System Field Id SF Label Type

date-of-birth Date of Birth DATE


country-of-birth Country of COUNTRY
Birth

custom-string1 Custom String STRING


1

Region of
region-of-birth STRING
Birth
Description of Headings
This column lists the technical IDs of the fields. You cannot change this ID.

If you require an alternative label please specify this in "Customer Label"

e:

pes can handle mathematical operations.


the UI, the most common options for such fields are “Yes” and “No”.

al numbers.
gers.
with this data type. Where there is a limit on the number of characters in fields like this, the maximum number of
n.

number of characters you can enter in the string. Where this is the case, this column shows the relevant maximum.
visibility = both), No (means visibility = none)

e. it cannot be left blank.


dation object, user list, etc
number of decimal places

Customer Label (specify alternative label to "Biographical Information" if required)

Biographical Information (Person Information)

Max Length Used Customer Required List of Decimal ACME Requested


Label (Mandatory) Values Precision Change

Yes Yes Yes


100 Yes Birth location Yes

Additional
256 Yes Location of Yes
Residency

100

Orange field indicates change requested by customer

White field indicates values cannot be changed

Yellow field indicates values can be specfied/changed


Comments

Standard field used


changed
Standard field used with
new label specified and
set as mandatory

Illustration of how to
specify the use of a
custom field

Standard field used


unchanged
JUMP BACK TO TOC
Customer Label (specify alternative lab
Iteration 2 Change
Iteration 3 Change
Biographical Informa

System Field Id SF Label Type Max Length Used

date-of-birth Date of Birth DATE Yes

User Name in Add N


Iteration 2

Iteration 3

System Field Id SF Label Type Max Length Used

user-name User Name STRING Yes


mer Label (specify alternative label to "Biographical Information" if required)
Biographical Information (Person Information)

ACME
Customer Label Required List of Values Decimal Requested
(Mandatory) Precision
Change

Yes Yes

User Name in Add New Employee - Identity

ACME
Required Decimal
Customer Label (Mandatory) List of Values Requested
Precision
Change
Learn More about this functionality:
The Person Information portlet defines the basic biograp
the Employee as well as the ID used by the client interna
Comments

Comments

Note this field only appears in the Add New Employee


wizard. Thereafter, it appears in the Employee Profile
only.
s functionality:
n portlet defines the basic biographic information for
as the ID used by the client internally to the Company
JUMP BACK TO TOC
Customer Label (specify alternati
Iteration 2 Change
Iteration 3 Change

Per

System Field Id SF Label Type Max Length Used

salutation Salutation STRING 128 Yes

suffix Suffix STRING 128 No

gender Gender STRING 2 Yes

custom-string2 Custom String 2 STRING 256 Yes


custom-string2-20 Custom String XX STRING 256
custom-date1-10 Custom Date XX DATE
custom-long1-20 Custom Long XX LONG
custom-double1-20 Custom Double XX DOUBLE
mer Label (specify alternative label to "Personal Information" if required)
Personal Information

Required Decimal ACME Requested


Customer Label List of Values
(Mandatory) Precision Change

No Picklist: salutation Yes

No Picklist: namesuffix Yes

Yes System Yes

Citizenship No picklist Citizenship Yes


Learn More about this functionality:
Personal Information stores information about an Employee's Name as
demographic information.
Comments NB: Alternate Name fields are used for non-standard character sets.
NB: This portlet also contains the Global Information included for the
Employee

This portlet includes effective dated history.


predefined picklist salutation and contains
the following standard fields:
● Mr
● Mrs
● Ms

You can enter a name suffix, such as Jr, Sr,


PhD, and so on. The list of values comes from
the predefined picklist namesuffix.

The list of values is system-defined. Do not


configure this as a picklist. Possible values
are Male and Female.
ut an Employee's Name as well as

tandard character sets.


rmation included for the
JUMP BACK TO TOC
Customer Label (specify alte
Iteration 2 Change
Iteration 3 Change

Hom

System Field Id SF Label Type Max Length Used

address1 Address 1 STRING 256 Yes


address2 Address 2 STRING 256 Yes
address3 Address 3 STRING 256 No
custom-string1 Address 4 STRING 256 No
city City STRING 256 Yes
county County STRING 256 No
state State STRING 256 Yes
zip-code Zip Code STRING 256 Yes
province Province STRING 256 Yes
Iteration 2 Change
Iteration 3 Change

Home Ad

System Field Id SF Label Type Max Length Used

address1 Address 1 STRING 256 Yes


address2 Address 2 STRING 256 Yes
address3 Address 3 STRING 256 No
custom-string1 Address 4 STRING 256 No
city City STRING 256 Yes
county County STRING 256 No
province Province STRING 256 No
state State STRING 256 Yes
zip-code Zip Code STRING 256 Yes
country Country STRING 256 Yes
Iteration 2 Change
Iteration 3 Change

Home

System Field Id SF Label Type Max Length Used

address1 Address 1 STRING 256 Yes


zip-code Zip Code STRING 256 Yes
address2 Address 2 STRING 256 No
address3 Address 3 STRING 256 No
custom-string1 Custom String 1 STRING 256 No
city City STRING 256 Yes
custom-string2 Custom String 2 STRING 256 No
province Province STRING 256 No
county County STRING 256 No
state State STRING 256 No
country Country STRING 256 Yes
Customer Label (specify alternative label to "Home Address" if required)
Home Address - Default

Required Decimal ACME Requested


Customer Label List of Values
(Mandatory) Precision Change

Yes
Yes
Yes
Yes
Yes
Yes
Picklist STATE_USA Yes
Yes
Yes

Home Address - United States (USA)

Customer Label Required List of Values Decimal ACME Requested


(Mandatory) Precision Change

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes List of Countries Yes

Home Address - France (FRA)

Required Decimal ACME Requested


Customer Label List of Values
(Mandatory) Precision Change

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes List of Countries Yes
Learn More about this functionality:
Home Address allows the Employee to enter multiple ad
Each Country can define a specific address format using
Comments The alternate fields available are used for those Countrie
standard character sets

This portlet includes effective dated history.

used to handle counrty specific address lines

Comments

Comments
s functionality:
the Employee to enter multiple addresses.
ne a specific address format using the available fields.
ailable are used for those Countries that use non-
s

ffective dated history.


JUMP BACK TO TOC
Customer Label
Iteration 2 Change
Iteration 3 Change

System Field Id SF Label Type Max Length

country Country STRING 100


card-type National ID Card Type STRING 256
national-id National ID STRING 256
isPrimary Primary BOOLEAN 1
custom-string1-20 Custom String XX STRING 256
custom-date1-10 Custom Date XX DATE
custom-long1-20 Custom Long XX LONG
custom-double1-20 Custom Double XX DOUBLE
Iteration 2 Change
Iteration 3 Change

Country National ID Type National ID Description

USA ssn Social Security Number


FRA INSEE INSEE - INSEE code
MEX PR CURP-Clave Única de Registro de Población
Customer Label (specify alternative label to "National ID Information" if required)
National ID Information

Required Decimal
Used Customer Label List of Values pii
(Mandatory) Precision

Yes Yes Configured Countries


Yes Yes Configured Types
Yes Yes Yes
Yes Yes Boolean: True/False

Supplied National ID Formats (note they can be reconfigured if required)

Display Format Regular Expression

XXX-XX-XXXX [\d]{3}-[\d]{2}-[\d]{4}
XXXXXXAXXXXXX XX [\d]{6}[A-Z\d][\d]{6} [\d]{2}
ro de Población XXXXXXXXXXXXXXXXXX [\d]{18}
Learn More about this functio
National ID Information is used
ACME that identifies them through th
Requested Comments National ID per Type per Count
Change
The system won't accept havin
Type and Country
Yes National ID is also used as part
Yes within the New Hire process
Yes
Yes

onfigured if required)

ar Expression ACME Requested Customer Label Display Format Requested Regular Exp
Change

[\d]{2}-[\d]{4} Yes 999-99-9999 [\d]{3}-[\d]{2


Z\d][\d]{6} [\d]{2} Yes INSEE Code 999999X999999 99 [\d]{6}[A-Z\d][\d
[\d]{18} Yes CURP AAAA999999AAAAAA99 [a-zA-Z]{4}[\d]{6}[a-
Learn More about this functionality:
National ID Information is used to capture an Employee's Tax based number
that identifies them through their local government. An Employee can have a
National ID per Type per Country.

The system won't accept having two Employees with the same National ID,
Type and Country
National ID is also used as part of the system lookup for an existing Employee
within the New Hire process

Learn More about this functionality:

Regular Expression

[\d]{3}-[\d]{2}-[\d]{4}
[\d]{6}[A-Z\d][\d]{6} [\d]{2}
[a-zA-Z]{4}[\d]{6}[a-zA-Z]{6}[\d]{2}
JUMP BACK TO TOC
Customer Label (spe
Iteration 2 Change
Iteration 3 Change

System Field Id SF Label Type Max Length

benefits-eligibility-start-date Benefits Eligibility Start Date DATE


professionalServiceDate Professional Service Date DATE
initialStockGrant Initial Stock Grant LONG
Iteration 2 Change
Iteration 3 Change

Employm

System Field Id SF Label Type Max Length

custom-string1 Custom String 1 STRING 256


custom-date1 Custom Date 1 DATE
Iteration 2 Change
Iteration 3 Change

Emplo

System Field Id SF Label Type Max Length

custom-string2 Custom String 2 STRING 256


custom-date2 Custom Date 2 DATE
Customer Label (specify alternative label to "Employment Details" if required)
Employment Details

Mandatory
Used Customer Label (Required by the List of Values Decimal
Precision
system)

Yes
No
Yes

Employment Information - At Hire - United States (USA)

Required Decimal
Used Customer Label List of Values
(Mandatory) Precision

Yes Probation Waived Picklist yesno


Yes End of Probation

Employment Information - At Hire - France (FRA)

Required Decimal
Used Customer Label List of Values
(Mandatory) Precision

Yes Hiring Initiative Picklist HiringInit


Yes Previous Service From
Learn More about this functionality:
Employment Information defines the engageme
Employee that outlines the Employee's most rec
ACME Requested Comments eligibilities around Stock and Benefits at the Emp
Change
NB: Employment Information is split into two se
- Hire
This is the start date from which the - Termination
Yes employee is eligible for benefits. They are grouped in the same section within the
Yes functionality but the fields for Termination will o
is Terminated. This also means the Custom fields
Yes sections as noted.

This is a Country Specific portlet and fields can b


Country

ACME Requested
Comments
Change

Yes
Yes

ACME Requested
Comments
Change

Yes, visible
Yes, visible
s functionality:
tion defines the engagement level information for an
s the Employee's most recent Hire information as well as
ck and Benefits at the Employment level.

mation is split into two sections:

he same section within the UI and the portlet


elds for Termination will only show when the Employee
o means the Custom fields are split between the two

fic portlet and fields can be configured individually by


JUMP BACK TO TOC
Iteration 2 Change
Iteration 3 Change

System Field Id SF Label Type

company Legal Entity INTEGER


timezone Timezone STRING
business-unit Business Unit INTEGER
division Division STRING
department Department STRING
location Location STRING
cost-center Cost Center Account INTEGER
manager-id Supervisor HRIS_FINDUSER
job-code Job Code STRING
job-title Job Title STRING
local-job-title Local Job Title STRING
standard-hours Standard Hours DOUBLE
fte FTE DOUBLE
is-fulltime-employee Full/Part-Time BOOLEAN
notes Notes STRING
shift-rate Shift Rate DOUBLE
shift-factor Shift Factor DOUBLE
supervisor-level Supervisor Level STRING
is-cross-border-worker Cross Border Worker BOOLEAN
eeo-class EEO Class STRING
custom-string1 Custom String 1 STRING
Iteration 2 Change
Iteration 3 Change

System Field Id SF Label Type

flsa-status FLSA Status STRING


eeo-class EEO Job Group STRING
eeo1-job-category EEO Category 1 STRING
eeo5-job-category EEO Category 5 STRING
eeo6-job-category EEO Category 6 STRING
Customer Label (specify alternative label to "Job Information" if required)
Job Information

Max Length Used Customer Label Required (Mandatory)

Yes Wheel Yes


Yes
Yes Hub Yes
128 Yes Spoke Yes
128 No
128 Yes
Yes Yes
384 Yes Yes
128 Yes No
256 Yes Yes
256 No
Yes
No
Yes Full Time Yes
4000 No
No
No
256 Yes Hierarchy
No
256 Yes
256 Yes Contract Type Yes

Job Information - United States (USA)

Max Length Used Customer Label Required (Mandatory)

256 Yes
256 Yes
256 Yes
256 No
256 No
e label to "Job Information" if required)
formation

List of Values Propagation Decimal ACME Requested


Precision Change

Foundation Object Yes


System Yes, from location Yes
Foundation Object Yes
Foundation Object Yes
Foundation Object Yes
Foundation Object Yes
Foundation Object Yes
User List Yes
Foundation Object Yes
Yes
Yes
Yes, from company Yes
Yes
Boolean: True/False Yes
Yes
Yes
Yes
picklist supervisor-level Yes, from job classification Yes
Boolean: True/False Yes
picklist eeo-class Yes
picklist ContractType Yes

- United States (USA)

Decimal ACME Requested


List of Values Propagation
Precision Change

Picklist: FLSASTATUS_USA
Picklist: eeo-class Yes
Picklist: EEO1CODE_USA
Picklist: EEO5CODE_USA Yes
Picklist: EEO6CODE_USA Yes
Learn More about this functionality:
Job Information is the main job based portlet that is recorded for the
Employee. This portlet records all of the individual attributes of the
Comments Employee's current Job posting.

NB: FTE is a calculated field and is based off Job Information.Standar


Company.Standard Hours
NB: Employment Status is a floating field that is derived from the cha
made to an Employee through transactions. The status is non-config

This is a Country Specific portlet and fields can be configured individu


Country
This portlet includes effective dated history.

Appears in your instance as EEO Job Group

Comments
that is recorded for the
vidual attributes of the

ob Information.Standard Hours /

is derived from the changes


The status is non-configurable.

n be configured individually by
JUMP BACK TO TOC
Iteration 2 Change
Iteration 3 Change

Customer Role Permission

System Admin ALL

Employees Business Email

Employees Citizenship

Personal Information Fields


Employees Except Citizenship

Employees Scorecard

Employees Update Employee Records / Take


Action

Update Employee Records / Take


Employees
Action

Employees planLeaveOfAbsenceAction

Employees planLeaveOfAbsenceAction

Employees Permission to Create Notes

Employees Permission to Create Notes

Managers Business Email


Managers Personal Information Fields

Managers Employee Views

Managers Plan Leave of Absence

Managers Return from Leave of Absence

Managers Hire
Managers Rehire

Managers Permission to Create Notes

Power User ALL

Power User ALL

Power User ALL

Power User ALL

Power User ALL

Power User ALL


General RBP Settings

Permission Type Permission Roles Permission Section

View/Edit System Adminstrators ALL

View Employee Self-Service Employee Data

Employee Central
View Current/View History Employee Self-Service
Effective Dated Entities

Employee Central
View Current/View History/ Edit Employee Self-Service Effective Dated Entities

None Employee Self-Service Employee Views

None Employee Self-Service Employee Data

Employee Login and Basic


None Employee Data
Access

None Employee Self-Service Employee Data

Employee Login and Basic


None Employee Data
Access

None Employee Self-Service General User Permission

Employee Login and Basic


None General User Permission
Access

View Manager Role Employee Data


Employee Central
View Current / View History Manager Role
Effective Dated Entities

ALL Manager Role Employee Views

View/Edit Manager Role Employee Data

View/Edit Manager Role Employee Data

None Manager Role Employee Data


None Manager Role Employee Data

None Manager Role General User Permission

View/Edit Power User Edit Employee Data

Employee Central
View/Edit Power User Edit
Effective Dated Entities

View/Edit Power User Edit Employee Views

View Only Power User View Employee Data

Employee Central
View Only Power User View
Effective Dated Entities

View Only Power User View Employee Views


Permission
Sub Section

ALL

HR Information

Personal Information

Personal Information

HR Actions

HR Actions

HR Actions

HR Actions

HR Information
Personal Information

HR Actions

HR Actions

HR Actions
HR Actions

ALL

ALL

ALL

ALL
Learn More about this fu
This section outlines eac
data or portlets within th
permissions are split by R
Comments

Make sure that the System Administrator has access to all fields including the custom
fields you added as part of the case study.

Can View but not edit the Business E-mail address

Can View but not edit the Personal Information field Citizenship

Can View Current, View Historical and Edit Personal Information fields. This does not
include the Citizenship field.

Remove permission to see scorecard

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

Can View but not edit the Business E-mail address


Can View Current and View Historical Personal Information fields. This includes the
Citizenship field.

Allows manager to see all pages of the employee file

Allows managers to plan leave of absence requests

Allows managers to plan leave of absence requests

Remove the permission for a manager to add employees


Remove the permission for a manager to rehire employees
Remove any permissions for this item. This controls whether the 'Update Employee
Records' button is viewable

User can access and edit all fields

User can access and edit all fields

User can access and edit all fields

User can view all fields.

User can view all fields.

User can view all fields.


Learn More about this functionality:
This section outlines each of the permissions that do not pertain to individual
data or portlets within the Employee Central system. Each of these
permissions are split by Role
JUMP BACK TO TOC
Iteration 2 Change
Iteration 3 Change

Iteration 2 Change
Iteration 3 Change
RBP Granted Groups and Target Groups

Group Name Group Definition

System Administrators User List: superacme, etc.


Select one user from the system
Power User FRA with no direct reports
Select another user from the system
Power User USA with no direct reports
Permission Group 1
Permission Group 2
RBP Roles to Groups

Granted Population Role

Employees Employee Self-Service

Employees Employee Login and Basic Access

Managers Manager Role


Administrators System Admin
Power User FRA Power User Edit
Power User USA Power User Edit
Power User FRA Power User View
Power User USA Power User View
Groups Learn More about this functionality:
Once Roles are defined within the system, the Users that the Role is g
as well as the Target Population need to be defined. Within each Role
Target Population multiple groups can be defined to determine both populations

NB: There are a number of combinations that can define these popula
- Default Relationships (Manager, Employee etc.)
- Target Groups (defining specific populations)
Self - Combination of Default Relationships and Target Groups (USA Ma
etc.)
All

All Direct Reports - All Levels Down


All
Employees in France
Employees in USA
ALL Employees
ALL Employees
e Users that the Role is granted to
efined. Within each Role,
both populations

t can define these populations:


e etc.)
ons)
Target Groups (USA Managers
JUMP BACK TO TOC
Configuration Workbook Sign-Off
The intent of this sign-off is to close the requirements gathering phase.

The <CUSTOMER> team has reviewed this configuration workbook and agreed to the following:

The configuration workbook accurately reflects <CUSTOMER>’s requirements as they relate to <MODULE> and the asso
The SuccessFactors proposed solution addresses these requirements as they are understood by the project team
By moving forward with these requirements, <CUSTOMER> understands that any requests for future edits and changes

Throughout a project, new information may surface that may necessitate a change in business requirements or a change
scope and therefore estimated level of effort, project timeline or solution features. Change Orders may result in adjustm

SuccessFactors acknowledges that after scoping the reporting requirements, additional review of this design document m
be initiated by either a <CUSTOMER> or SuccessFactors team member. Due to the complexity of some change orders, Suc
the requested change. SuccessFactors will inform <CUSTOMER> of the estimate if a charge will apply.

Iteration 1

Signed <CUSTOMER>: Date:

___________________________________________________________

Iteration 2

Signed <CUSTOMER>: Date:

___________________________________________________________

Iteration 3

Signed <CUSTOMER>: Date:

___________________________________________________________
elate to <MODULE> and the associated processes
tood by the project team
sts for future edits and changes could impact the project start date

iness requirements or a change in the technical environment. These changes may result in a change in project
ge Orders may result in adjustments to this estimate and an increase in the estimated costs.

view of this design document may be necessary. Any changes to scope will require a Change Order, which may
xity of some change orders, SuccessFactors may bill <CUSTOMER> for the time required to scope and estimate
e will apply.

You might also like