Confiion - Workbook - EC - Employee - Data - ECM - v4
Confiion - Workbook - EC - Employee - Data - ECM - v4
Workbook
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…
Tasks
JUMP BACK TO TOC
Introduction
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.]
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
• 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
Region of
region-of-birth STRING
Birth
Description of Headings
This column lists the technical IDs of the fields. You cannot change this ID.
e:
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)
Additional
256 Yes Location of Yes
Residency
100
Illustration of how to
specify the use of a
custom field
Iteration 3
ACME
Customer Label Required List of Values Decimal Requested
(Mandatory) Precision
Change
Yes Yes
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
Per
Hom
Home Ad
Home
Yes
Yes
Yes
Yes
Yes
Yes
Picklist STATE_USA Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes List of Countries Yes
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
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
Required Decimal
Used Customer Label List of Values pii
(Mandatory) Precision
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
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
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
Employm
Emplo
Mandatory
Used Customer Label (Required by the List of Values Decimal
Precision
system)
Yes
No
Yes
Required Decimal
Used Customer Label List of Values
(Mandatory) Precision
Required Decimal
Used Customer Label List of Values
(Mandatory) Precision
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.
256 Yes
256 Yes
256 Yes
256 No
256 No
e label to "Job Information" if required)
formation
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.
Comments
that is recorded for the
vidual attributes of the
ob Information.Standard Hours /
n be configured individually by
JUMP BACK TO TOC
Iteration 2 Change
Iteration 3 Change
Employees Citizenship
Employees Scorecard
Employees planLeaveOfAbsenceAction
Employees planLeaveOfAbsenceAction
Managers Hire
Managers Rehire
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
Employee Central
View/Edit Power User Edit
Effective Dated Entities
Employee Central
View Only Power User View
Effective Dated Entities
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 Personal Information field Citizenship
Can View Current, View Historical and Edit Personal Information fields. This does not
include the Citizenship field.
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
Iteration 2 Change
Iteration 3 Change
RBP Granted Groups and Target Groups
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
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
___________________________________________________________
Iteration 2
___________________________________________________________
Iteration 3
___________________________________________________________
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.