Publishing Data to SAP SuccessFactors Employee Central

Once the compensation planning is completed, it is time to publish the final compensation results back to Employee Central. To publish the results to Employee Central, mapping must be defined between the source field in Compensation and the target field in Employee Central.

The code element, comp-ect-out-component, is used for publishing back to Employee Central. Currently, publishing is limited to the following Employee Central entities:

• payComponentRecurring
• payComponentNonRecurring
• JobInfo

It is important to define the target Employee Central entity, component code, event reason, and effective date to create the new compensation record in Employee Central.

Mapping attributes include:

• componentType: Specifies the type of pay component to publish to in Employee Central - payComponentRecurring or payComponentNonRecurring. JobInfo is only used for publishing promotions.
• componentCode: Specifies the code of the pay component. This is optional for recurring pay components. When not specified, the amount will be published to the pay component that has the attribute UsedforCompPlanning set to COMP or BOTH as seen in the figure, Recurring Pay Component.
• eventReason: Specifies the reason for the payout. This is optional for non-recurring pay components. The event reason can be changed in the user interface. When event reason is configured at the employee level (for example, by use of a lookup table), it will take precedence over the default value.
• : Specifies the default start-date for recurring pay components and the pay-date for non-recurring pay components. If a date is specified for the hris-field, that date takes precedence. Dates can be edited in the user interface.
• comp-hris-field-map: Specifies the names of the field in Compensation (comp-field-id) and Employee Central (hris-field-id).

Source fields that can be used for publishing include the following:

• Standard and custom compensation fields of the type string, amount, percent, money, and date can be published to Employee Central.

Target fields that can be used for publishing include the following:

• For recurring pay components, all Employee Central standard fields except pay-component- code, pay-component-type, is-target, and tax-treatment.
• All custom fields except fields that are of the data type long. This is because all custom fields in Compensation are of the data type double.
• If the compensation template is functional currency centric, money-formatted fields are converted to the employee’s local currency at the time of publishing.

For all recurring pay components, it is assumed that the recurring pay component is associated with its parent Employee Central compensation data. A recurring pay component can be published multiple times:

• The first time a component is published, a new pay component is created under the new parent compInfo.
• Subsequent publishing updates the pay components already created.

Pay components with different effective dates will be stored as different compensation data. Pay components in the base (not the template) will be carried over to the next compensation data.

For all non-recurring pay components, it is assumed that the pay component is a stand-alone pay component that is not connected to the Employee Central compensation data.

Multiple non-recurring pay components can be published:

• New pay component is created from scratch with foundation object values populated.
• Field values are set based on the comp-hris-field-map.

The same component can be published multiple times:

• First publishing creates a new pay component.
• Subsequent publishing updates pay components published from the same template and creates new ones.

Make sure there is only one non-recurring pay component with the same pay component code and same pay-date for the same compensation template.

If nonRecurringPayComponents for values such as Lumpsum were not part of the initial Employee Central implementation, the nonRecurringPayComponents element will need to be added, and the specific code created.

1. Navigate to Compensation Home → Select the comp template → Complete Compensation Cycle → Publish Data. You can select the population that can be published back to Employee Central. Publishing in multiple batches improves the overall performance of the publishing process.
   1. Use Publish in Employee Central to bulk publish records from all completed forms. Processing time depends on number of records.
   2. Use Publish Selected Worksheets in Employee Central to batch process records for select completed worksheets.
   3. Use Publish Selected Employees in Employee Central to batch process records for select employees from completed forms. Employees can be entered one at a time or can be imported using a CSV template. User filter option is based on chosen custom field setup in Employee Central Settings. Blanks is the filter value to match users with blank fields on the worksheet.
   4. Use Publish selected employees in the Metadata Framework (MDF) to publish data to MDF-based objects, which eliminates additional manual work. This is useful if you will be publishing custom MDF objects for compensation planning data. Please note it requires an XML code update to the compensation plan template, outlined in the Key Points about Publishing section.
2. Select Submit when ready to publish.
3. Track the status of your request with Monitor Compensation Jobs.

Key points about publishing are as follows:

• Employee’s base compInfo record in Employee Compensation (for example, the compInfo record that is effective as of the publish date) is the basis from which a new compInfo record is created. The new compInfo record copies info from the base record, modifying it according to the publishing configurations in the compensation template and user data in the compensation form.
• There can be only one base compInfo record for each publishing event.
• Current salary is stored in the compensation form and is retrieved from compInfo effective on plan date (for most cases, it will be the base compInfo during publish). Final salary, merit, promotion, and adjustment are stored in the compensation form and updated in the compensation cycle. They are published to the recurring pay components associated with this compInfo at the end of the compensation cycle.
• Lump sum is stored and edited in the form, and because it is a one-time payout, it is published as a non-recurring pay component. Non-recurring pay components are not associated with any compInfo.
• Compensation forms need to be completed.
• There are some business rules that can hinder publishing, such as a business rule to trigger additional workflow for any increase more than five percent. To override these rules, you can enable Do not trigger EC rules when publishing from the Compensation to Employee Central setting in Advanced Settings.
• Use the Enable forward propagation when publishing from the Compensation to Employee Centralsetting in Advanced Settings to ensure forward propagation for users with post-dated transactions.
• Ensure that pay components that are to be published are uniquely named.
• The publish date cannot be earlier than the plan date, that is, the effective date configured oncomp-config.
• A transaction is specific to a compensation user entry. In case multiple recurring or non-recurring pay components have to be updated, and even one fails, nothing will be updated in Employee Central for that record.
• The publishing order is based on the effective date of the component and event reason code.
• If more than one compInfo is getting published, the publish date must have the same effectivecompInfo. Otherwise, publishing will fail.
• Cannot publish for users without a base compInfo, that is, compInfo effective as of the publish date.
• A new pay component, with the same effective date as that of a pay component already published, cannot be added once data from that template has been published.
• The effective date of a pay component in the template can’t be changed once published.
• A published pay component cannot be deleted from the template; however, you can delete the entry from Compensation (History → Take Action → Permanently Delete Entry).
• Publish will not happen in Compensation for ineligible employees.
• For recurring pay components, publish will not happen if there is no new pay component to add or if there is no change to the value of an existing pay component.
• If canOverride is set to false, and you try to publish a value different from what is already on the foundation object, publishing will fail.
• Multiple pay components for the same date with the usedForCompPlanning attribute set to COMP or BOTH will cause publishing to fail. You may specify to publish job Information prior to publishing compensation Information. This will help with simplifying business rules that first rely on the new jobInfo, as well as with making the publishing job a two part process (more efficient if large amounts of data are being transferred). You do this by enabling Publish Job Information before Compensation Information found in Plan Setup → Settings → Advanced Settings.
• Up to five custom fields may be published to support scenarios where admins must publish only for select business units, countries, or regions. For a field to be publishable it must be marked as Reportable in the Column Designer.

To publish data to custom MDF objects, for the purposes of updating compensation planning data, you will need to do a few modifications.

• Ensure you have the appropriate role-based permissions by selecting Administrator → Manage Compensation → Store Compensation in MDF.
• Add the componentType to map comp-field-id to a comp-mdf-field. You can then map the various comp fields to their MDF-based objects. In the figure, ComponentCode: Custom Equity Retention Bonus, the cust_equity_retention_bonus componentCode was taken out and three comp fields have been mapped to their MDF-based equivalents.
• You can now publish data back to the MDF object by using the Publish Data tool.

Once data publishing has been activated, a background job runs to submit the information back to Employee Central. When the status of the job is completed, you may run the Employee Central Publish Report. This report will help identify overall issues or individual users with problems for troubleshooting.

To run and view the report, you must have role-based permissions. Click Administrator → Manage Compensation → View Employee Central Publish Report.

Once permissioned, you may submit the report by navigating to Compensation Template → Complete Compensation Cycle → Publish Data → Employee Central Publish Report.