Evaluating Position Management Business Rule Scenarios

Business Rules are used to add application logic to determine the outcome of a change made to particular data in the system. Business Rules follow the logic "IF this data is changed in a certain way, THEN the system reacts in this way".

Business Rules are highly configurable and not delivered "out of the box", since the requirements vary from customer to customer.

In the business rule, you define which actions the system performs when specific conditions are met.

• In the IF section of a rule, you define which conditions need to be met. Please note that some rules don't require conditions, be it for application-specific reasons or because the rule is defined as "always true"
• In the THEN section of a rule, you define how the system reacts when the conditions are met. Please note that some application-specific rules don't require THEN statements.
• Sometimes, rules have alternative scenarios when another set of different conditions and statements would make the rule trigger ELSE IF / THEN or even "Catch All" scenarios, when any of the conditions or statements already define on the rule are not met, but we still want the rule to trigger ELSE. The typical example of using ELSE is for the Event Reason Derivation rules in Employee Central.
• The rule is assigned wherever applicable (e.g. a rule to propagate data to the Position record based on selection of Job Classification will be assigned at the jobCode field in the Position object definition).
• Definition of the event that triggers the rule. Using the same example, the rule will trigger when the jobCode field changes, and before you save the Position changes (onChange trigger event).

In Position Management, the following scenarios are available to configure Business Rules

• Synchronize Position Changes to Incumbents. You can use this scenario to synchronize changes of a position to the incumbents. You must first register the rule in Position Management Settings → Synchronization → Rule for Synchronizing Position to Job Information. The rule should also be triggered if the position field is changed in job information.
• Map Fields from Position to External Job Requisition in Fieldglass Integration. You can use this scenario to define the field mapping between a position and the external job requisition to be created in Fieldglass. You must first register the rule in Position Management Settings, in the Rule for Mapping Fields between Position and Fieldglass field.
  Note

  This business rule scenario requires to set up the integration with SAP Fieldglass, which is not in scope for this training. For more information, you can check the following resource in the SAP Help Portal:Integrating Employee Central with SAP Fieldglass

• Synchronize Incumbent's Changes to Position. You can use this scenario to synchronize changes in an incumbent's job information to the assigned position. You must first register the rule in Position Management Settings → Synchronization → Rule for Synchronizing Job Information to Position.
• Default Position Attributes in Position Organization Chart. You can use this scenario to default values if a new position is created in the position organization chart using the Add Lower-Level Position or the Create Same-Level Position actions. You must first register the rule in Position Management Settings → UI Customizing → Rule for Defining Copy-Relevant Position Fields.
• Update Rule for Mass Change Run. You can use this scenario in a mass change run to define the target criteria of objects to be updated, as well as the updated values. You can register the rule in your Position Mass Change Run requests in Manage Mass Changes for Metadata Objects tool.
• Unassigned Incumbent from Position for Right to Return. You can use this scenario to decide whether an incumbent should be unassigned from the position in a Right to Return scenario or not. You must first register the rule in Position Management Settings → Right to Return → Unassign from Position.
• Create Right to Return for Incumbent. You can use this scenario to decide whether a right to return should be created in the incumbent's position in a Right to Return scenario or not. You must first register the rule inPosition Management Settings → Right to Return → Create Right to Return.
• Derive Job Requisition Template in Recruiting Integration. You can use this scenario to derive the job requisition template ID that should be used for the job requisition. You must first register the rule in Position Management Settings → Integration → Rule for Deriving Job Requisition Template ID.
• Map Fields from Position to Job Requisition in Recruiting Integration. You can use this scenario to define the field mapping between the position and the job requisition to be created. You must first register the rule in Position Management Settings → Integration → Field Mapping Rule to Create Job Requisition from Position.
  Note

  The rules for Recruiting Integration will be discussed further in the Unit 5 - Lesson 1 Integrating SAP SuccessFactors Employee Central Position Management with SAP SuccessFactors Recruiting.

Besides the specific scenarios for Position Management in Configure Business Rules, you can use the Rules for MDF Based Objects in the Metadata Framework rule scenario to:

• Generate Position Code Automatically based on a sequence.
• Default Values when a new position is created.
• Trigger Workflows when a new Position is created and/or changed.
• Configure EC Alerts and Notifications