Professional Documents
Culture Documents
Employee Central
Employee Central
18/06/2019
My Employee Profile:
Only admin and consultant have the administrative rights to configure the settings
In portlets
Profile indicator is is nothing but the amount of information filled in the profile …its not seen by others
apart from user
They are 7 data models and we mainly use 5 data models
You can set up various data models in Employee central . You need to login to provisioning
under the succession management you can find 7 Data models .
You need download these data models and create a back up folder and edit these data models as
per your requirement and re - import it in provisioning. So that these changes will reflect in your
instance
a. A DTD is a document type definition that defines the document structure and elements of
your XML. For example, if a new hris-element is introduced in a new release and the
DTD does not contain that element or any related attributes you will receive errors that
you cannot move past.
What do I have to do after I have defined the customer’s requirements in the data
model?
a. In Provisioning upload the data models to your customer’s instance. Any errors that may
not have been caught by the XML parser will be caught here so don’t be alarmed if you
see errors here.
b. The most frequent mistake is trying to upload a data model through the wrong link in
Provisioning. Unfortunately currently you don’t see an error but the processing will
happen endlessly before you wake up and realize your mistake.
Now that you know all that you need to know about data models and DTDs let us cruise through
the 4 main data models used in Employee Central. There are 3 others used for workflow, rules,
and Propagation.Propagation is the feature in Employee Central that allows for foundation data
to be automatically populated on the HR data objects. For e.g. if you stored the time zone on the
location foundation object, you can build a propagation such that the time zone is automatically
changed on employee data based on the value of location selected.
a. You define the country specific features for elements already defined in the
corporate Data model
b. This data model comes with some standard delivered localization elements like
National ID etc.
c. You have to define a hris-element in the Corporate data model in order to specify
the country specific behavior for that element
d. Below is an example of the country Specific Corporate Data model showing a few
countries and delivered hris-elements. You can add any hris-element defined in
the Corporate data model to add country specific requirements. The following is
the grid view in the Oxygen XML editor.
a. You define the HR data (Person and Employment) in this data model. This data
model is called “data model” in Provisioning
b. With the rapid advancement of the Meta data framework customers can configure
most of the elements on the OneAdmin UI
c. Below is an example of the personalInfo hris-element in XML
a. The country specific succession data model is used to define country specific
requirements for elements defined in the succession data model
b. For example, if you want to define US specific fields to store Global Info you will
do that in the Country Specific (CSF) succession data model, similar to the CSF
Corporate data model
You will be working most frequently on the standard hris-elements hence selecting them for
discussion. There are a number of things you can do with the background elements in the
Succession Data model, such as create custom views for the client and it is synced with the
Employee profile and other integrated products of the BizX suite.
Errors will occur when the XML is either not “well-formed” (missing syntax, e.g. not closing a tag) or
not “valid” (not confirming to the DTD)
SAP Successfactors Assignment for EC
Employee Central’s mobile functionality is extremely sophisticated and has excellent usability. It
covers the crucial components of the HR software solution such as time off requests/approvals,
workflow approvals and employee/manager self-service. In addition, it utilizes the useful
organizational chart search feature which allows employees to instantly locate any user contact
info, job title, picture etc..
Robust Data Management – An intuitive user interface powered by effective dating, auditing
capabilities and a rules-based workflow make it easy for you to securely manage current,
historical or future-looking workforce and organization data.
1. You define the country specific features for elements already defined in the
corporate Data model
2. This data model comes with some standard delivered localization elements like
National ID etc.
3. You have to define a hris-element in the Corporate data model in order to specify
the country specific behavior for that element
4. Below is an example of the country Specific Corporate Data model showing a few
countries and delivered hris-elements. You can add any hris-element defined in
the Corporate data model to add country specific requirements. The following is
the grid view in the Oxygen XML editor.
1. You define the HR data (Person and Employment) in this data model. This data
model is called “data model” in Provisioning
2. With the rapid advancement of the Meta data framework customers can configure
most of the elements on the OneAdmin UI
3. Below is an example of thepersonalInfohris-element in XML
1. The same element can be configured in the Metadata Framework via OneAdminUI by
going to Manage Business Configuration
2. Country Specific (CSF) Succession Data model
1. The country specific succession data model is used to define country specific
requirements for elements defined in the succession data model
2. For example, if you want to define US specific fields to store Global Info you will
do that in the Country Specific (CSF) succession data model, similar to the CSF
Corporate data model
Propagation is the feature in Employee Central that allows for foundation data to be
automatically populated on the HR data objects. For e.g. if you stored the time zone on the
location foundation object, you can build a propagation such that the time zone is automatically
changed on employee data based on the value of location selected.
You can define rules that automatically determine the right workflow when the manager or
employee changes employee data. To achieve this, you create a workflow foundation object and
assign it to the rule in the Rules Engine U
7. Event Reason Derivation Data models: Specifies what data changes should trigger a
specific event reason for eg:Determinesweather a new job code is job change event or
promotion event.
For each of the data models above describe the role of them in building EC foundation.
2.Country Specific (CSF) Corporate Data model: Configures country specific fields, sets
international standards like address format, national id format.
3. Succession Data model: HR data (Person and Employment) is defined in this data
model. This data model is called “data model” in Provisioning
4.Country Specific (CSF) Succession Data model:Used todefine country specific requirements
for elements defined in the succession data model.
6. Workflow rules Data model: Define rules that automatically determine the right
workflow when the manager or employee changes employee data.
7. Event Reason Derivation Data models:Specifies what data changes should trigger a
specific event reason for eg:Determines whether a new job code is job change event or
promotion event.
8. What are foundation objects?
By using foundation objects you set up data that can be shared across the entire company such as
Organization, Pay and Job Structure Details – in Successfactors terminology this is called
Foundation Objects. Foundation objects are created in the CorporateData Model
Personal and Employment Objects :Employee Details – This covers Personal and Employment
Details for Employees, known as Personal and Employment Objects respectively.
The MDF is a UI-based configuration and extension framework that provides creation,
modification, maintenance, and deletion of custom objects (called Metadata Objects) within the
SuccessFactors HCM suite. It replaces XML-based configuration and the need to import Master
Data via CSV/Excel files.
At its core the MDF provides one generic set of the components that are re-used by all objects.
This is because each object’s data is Metadata – nothing is hard-coded within the SuccessFactors
system.
When standard delivered Foundation Objects are not sufficient to meet customer requirements,
there is another category of Objects, which were added recently to provide flexibility in a
scenario. These are known as Generic or Custom Foundation Objects, e.g. Positions for Position
Management. As per their current status, generic objects are not “Integration ready” i.e. it’s not
possible to import or export generic objects in an automatic manner.Generic objects are created
in the Succession Data model.
2. Download the Succession Data Model from Provisioning and open it in an XML editor.
add the typeattribute referencing the external code of the generic object, as in this
example:
<hris-element id=”jobInfo”>
<label>Job Information</label>
type=”GO_Building”>
<label>Building</label>
</hris-field>
Use only a custom-stringas customer-specific field when you use the typeattribute with generic
objects.
4. Save your changes and upload the Succession Data Model in Provisioning.
5.Assign role-based permissions for the custom field you have added.
Describe a scenario to get approval for an employee to grant FMLA leave and describe
how to build a workflow solution for this.
1.Log in to SuccessFactors, and select Admin from the Welcome drop-down menu.
Remind in days:
Is delegate supported: Yes
Alternative Workflow
Step 1
Approver Type Approver Role Context
Role Employee HR Source
Step 2
Approver Type Approver Role Context
Role Employee Manager Manager Source
Workflow Contributor
Contributor Type Contributor Context
CC Role
CC Role Type CC Role Context
Role Employee Manager Target
Note: There is always an additional step with the employee in the approver role.
7. Select Save.
Rules are configured in the XML model for Workflow Derivation. This model is available
from Provisioning. Rules contain 5 pieces:
Rule Id – ex: <rule id=“rule-1”/>
This event id should match the id you created in the workflow creation step
Conditions
1.In Provisioning, under Succession Management, click Import/Export Rules XML for
Workflow Derivation.
<rule id=”rule-1″>
<trueoutput>FMLA</trueoutput>
<conditions>
<and>
<equal id=”Name of event.event” value=”8” compareToNew= “true” />
</and>
</conditions>
</rule>
Import/export foundation data: Download .csv file, key in the data and import it back.
Download these data models and create a backup folder and edit these data models as per
company/client requirements and re – import it in provisioning, So that these changes will be
reflected in company/client instance.