2461978 - How To Configure Workflows for Foundation Objects ( FOO)

How to configure workflows for Foundation Objects?

Foundation object: pay range, location

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

• SAP SuccessFactors HXM Suite
• SAP SuccessFactors Employee Central
• Foundation Object
• Workflows

See below for an example to configure a workflow for Location Foundation Object. The workflow will get triggered when a new Location is created or an existing Location is edited.

The workflow used for the foundation object supports only the following approver types:

• For step approvers: Dynamic Group, Position

• For contributors: Dynamic Group, Position

• For CC Role users: Person, External e-mail, Dynamic Group, Position

Step 1:Create a Workflow that should get triggered.

Step 2:Create a Business Rule for triggering the workflow. Please notice the following:

• Base object is the Foundation Object for which a workflow should be triggered
• Parameter Name "FOWorkflow" Code "FOWorkflow" and Object "FO Workflow" should be added

Step 3: Add code in Corporate Data Model (CDM)

The Business Rule should be added as an onSave event to the Foundation Object in Corporate Data Model (CDM).

1. They are defined and configured in the Corporate Data Model. 
2. See Code: <trigger-rule event="onSave" rule="BRLocation"></trigger-rule>

• Access Corporate Data Model  here

Limitations that apply for Workflows for Foundation Objects:

• Foundation objects are one type of Employee Central objects, which are used to set up data across an entire company, such as job codes, or cost centers. They are defined and configured in the Corporate Data Model.

  Here are a few tips on using workflows for foundation objects.

• You can only create workflows for effective-dated foundation objects.
• Workflows are triggered for foundation objects when they're created, changed, and deleted. You cannot define a rule that triggers a workflow only when a foundation object is changed, and not when it's created or deleted.
• The workflow used for the foundation object supports only the following approver types:
• For step approvers: Dynamic Group, Position
• For contributors: Dynamic Group, Position
• For CC Role users: Person, External e-mail, Dynamic Group, Position

Also

• All other approver types are skipped when the workflow is triggered. If the workflow has no valid step approver, the workflow is skipped completely and the changes to the foundation object are saved without triggering the workflow.
• You cannot edit or update workflows for foundation objects on the workflow approval page.
• If you have multiple workflows for creating the same foundation object, and the foundation objects you intend to create have the same effective date, you won't be able to approve the second workflow when the first workflow has already been completed.

Example:

You create a foundation object Location A with an effective date of 01/01/2014, and trigger workflow 1.

• Before workflow 1 is completed, you create a second foundation object Location A, also with an effective date of 01/01/2014, and trigger workflow 2.
• After workflow 1 has been approved and completed, the foundation object Location A (effective on 01/01/2014) is successfully created as a result.
• Now if you try to approve workflow 2, the request will be rejected because the foundation object with the same data already exists.

FAQ - Additional Information

Q) Where can I find the guide documentation on this?

A) Guide:Implementing and Administering Workflows in Employee Central

Chapter: Foundation Objects and Creating Rules that Trigger Workflows for Foundation Objects

Q) Can I use an onChange rule?

A) Not supported:2449503 - onChange rule in Foundation Object

• 3066117 - How to export Data Models?
• 2080139 - How To Import Foundation Objects or Foundation Data - Employee Central
• 2449503 - onChange rule in Foundation Object

CDM, Corporate Data Model, Manage Organization pay and job structures, FOO, foundation object, workflow, corporate data model, location, range, geozone, component, pay grade, frequency, event reason, ECT-123662, ECT-133923, Foundation Objects, location, pay range, ECT-24628 , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , LOD-SF-EC , Employee Central , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , How To