Setting Up Propagation Rules

Pay-Related Objects A-Z

8 Creating Rules

8.1 Setting Up Propagation Rules

Prerequisites

You must have configured the fields you are going to reference in your propagation rules before in the Corporate Data Model and the Succession Data Model. If you are referring to country-specific fields, you must have set the fields in the country-specific data models accordingly.

Note

The field of the HRIS element in the Succession Data Model you are referencing in your propagation rules must be visible. If you have hidden the field, that is, if you have set the attribute value to visibility=“none”, propagation will fail.

Context

What Are Propagation Rules?

You define propagation rules to have the system automatically fill in fields in employment data. For example, if the user selects a certain location in Job Information, the time zone for that location can be filled automatically. Or if the user selects a job code, the job title to it will automatically be displayed in the job title field. This way, you reduce the amount of data the user has to enter manually, and it improves the consistency of data, which is vital for accurate reporting. Propagation is only possible from certain foundation objects to certain employment objects. Below, in step 2.b, you find a table from which foundation objects you can propagate to which employment objects.

Procedure

1. Download the XML file for propagation rules.

○ If you're setting up propagation rules the first time for a company, download the most current version from this link:

https://mysp.successfactors.com/productcentral/Pages/display/prodinfo/data+models+and +picklists/default.aspx .

Partners use this link: https://partners.successfactors.com/productcentral/Pages/display/prodinfo/

data+models+and+picklists/default.aspx

○ If you're changing already uploaded propagation rules, download the XML file from Provisioning under Succession Management Import/Export HRIS Propagation Configuration XML .

2. Open the file in an XML editor and adjust it according to the company's requirements.

a. Insert a propagation rule by copying an existing rule from the standard XML file and adjusting the following:

○ foundation-element-id: This is the HRIS-element ID of the foundation object. You find the correct ID either in the XML file for the Corporate Data Model, or in the Foundation object tables.

Note

For the CostCenter GO, the foundation-element-id must be set to "CostCenter".

○ field id: This is the HRIS-field ID of the field that belongs to the HRIS element and which contains the values you want to propagate.

Note

For cost center field id, refer to the CostCenter Data Object table.

○ destination hris-element-id: This is the HRIS-element ID of the employment object. You find the correct ID you need to enter here either in the XML file for the Succession Data Model, or in the Employment Object Tables.

○ field-id: This is the HRIS-field ID of the field that belongs to the HRIS element and to which you want propagate the values from the foundation object field.

If you are referencing a country-specific field, you have to insert the country code as follows:

</field>

You must have defined the country-specific Corporate Data Model and the country-specific Succession Data Model before, as this is where you define the field IDs you are referencing. In this example, custom-string2 is a field defined in the country-specific Corporate Data Model for USA, under HRIS element jobClassLocal. eeo1–job-category is a country-specific field you have set up before in the country-specific Succession Data Model, where it has been defined for country USA for the HRIS element jobInfo.

Consider another example where you want to reference a country specific field of legal entity, you will have to add code as follows:

</field>

In this example, LegalEntityUSA is the country-specific object id defined in the Configure Object Definition page for the country USA.

b. Map the foundation objects to the corresponding employment objects by inserting propagation mapping at the end of the XML file.

You have to set up a propagation mapping for every combination of foundation object to employment object. You always map from the external code of the foundation object to a specific field of the employment object in the following format:

<propagation-mapping foundation-field=”company.externalCode” hris-field=”jobInfo.company” />

○ foundation-field: This consists of the HRIS-element ID of the foundation object (company) and the HRIS-field ID of the external code (externalCode).

○ hris-field: This consists of the HRIS-element ID of the employment object (jobInfo) and the HRIS-field ID of the field that is connected to the external code of the foundation object field (company). To find out which field ID you have to enter here, refer to the table below.

In this table, you find the correct employment object field ID. Look for the foundation object from which you are propagating, then for the employment object you are propagating to. In the same row of the table, you find the correct employment object field you need to map the propagation with. This is always the same field, no matter which field of that employment object you are actually using in the propagation rules.

Let's say you want to propagate the field values from the timezone field of the location to the timezone field in the job information portlet as in this example:

<hris-propagations>

</field>

</propagate>

...

</hris-propagations>

To have the system execute this propagation rule, you need to insert a mapping from the location foundation object to the jobInfo employment object. If such a propagation mapping already exists in the XML file, you do not have to add it again. But if it is not there yet in the XML file, add the following propagation mapping at the end of the XML file:

<propagation—mapping foundation-field=”location.externalCode” hris-field=”jobInfo.location” />

3. Upload the propagation rules in Provisioning under Succession Management Import/Export HRIS Propagation Configuration XML .

Related Information

Foundation Object Tables [page 384]

Employment Object Tables [page 472]

In document EC Implementation Guide (Page 193-196)