Study guide

13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions

SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations

1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources

2 Chapter 2: Security, Proxy, and System Administration

2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager

3 Chapter 3: User Experience Configuration

3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations

4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework

4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security

5 Chapter 5: Business Rules

5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices

6 Chapter 6: Foundation Objects and Corporate Data Models

6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects

7 Chapter 7: Employee Data Structures and Permissions

7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators

8 Chapter 8: Employee Transactions and Data Maintenance

8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions

9 Chapter 9: Workflows, Alerts, and Event Reasons

9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

10 Chapter 10: Optional Employee Central Configurations

10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central

11 Chapter 11: Position Management Setup

11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

12 Chapter 12: Position Management in the Employee Lifecycle

12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows

13 Chapter 13: Position Management Rules, Integrations, and Company Structure

13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview

13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions

Key Takeaways Explain This Topic AI

Automatic position codes need a sequence, a Rules for MDF Based Objects rule under Save Rules, a read-only code field, and the onSave code-generation setting set to Yes.

Position workflows use a Rules for MDF Based Objects rule with purpose Workflow, assigned as an onSave (Save) rule, plus Pending Data = Yes.

Workflows on positions run only after all Save and Validate rules, so the code-generation rule runs first.

Advanced To-do Key Details can show up to four position fields, and only one instance is allowed per company.

Position rule functions include Get Incumbent By Position, Get Next Available Manager By Position, and Get Pay Range By Position.

Last updated: September 2026

13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions

Quick Answer: Generate position codes from MDF sequences with a Rules for MDF Based Objects rule under the Position object's Save Rules , and set Position External Code Generation by onSave rule = Yes . Protect position changes with workflow rules (purpose Workflow , assigned onSave , with Pending Data = Yes ). Register right to return rules in PM Settings. Use PM rule functions such as Get Incumbent By Position in conditions.

Generating Position Codes Automatically

Automatic codes keep codes consistent and avoid entry errors. They can vary by attribute, for example by the country of the position's company (US_POS10, DEU_POS25…).

Create sequences in Manage Sequence , Manage Data, or Import and Export Data. Each has a start value and a step. THR79's example uses PTSeqPos starting at 1000 with step 125 for Portugal, and another starting at 106 with step 10 for others. The current value is transient.

Create the rule: Rules for MDF Based Objects , Base Object Position , Purpose Evaluate . The THEN sets the code from a format template and a sequence. Formats use Java format string syntax . For example, 1%07d gives an 8-digit number starting with 1. SAP's example uses PTPosID_%d for Portugal and PosID%d otherwise.

Assign the rule under Save Rules in the Position object.

Set the code field (externalCode) to Read Only.

Position Management Settings > General > Position External Code Generation by onSave rule = Yes.

Creating a position in Manage Positions now shows a read-only code that is generated on save (PosID_1, PosID_2…). The Check Tool flags inconsistencies, such as the setting being Yes while the code is editable or no rule is assigned.

Workflows for Position Creation and Changes

Managers may be allowed to create positions for their teams. Even with fine-grained RBP, approval is often required.

Create the workflow record(s) in Manage Organization, Pay and Job Structures with approvers, contributors, and CC roles.

Create the rule: Rules for MDF Based Objects , Base Object Position , Purpose Workflow . IF or ELSE IF define when. THEN sets the wfConfig field ( Workflow Context.Workflow Configuration ).

Assign it as an onSave rule (under Save Rules ) in Configure Object Definitions > Position .

Set Pending Data = Yes on the Position object, so records are not visible until approved. This is a prerequisite for position workflows.

For the latest home page, the To Do Category is Generic Object Change Requests (read-only).

Unless you use position types , you cannot run a workflow on Job Information changes if position changes must sync to incumbents.

Order of execution: workflows trigger only after all MDF Save and Validate rules have run , so the code-generation rule runs first . To target only new positions, test Original Record.Position Code is equal to Null .

Worked Example (THR79)

  • Workflow Steps
  • NewPositionUS Dynamic Role Finance Controller (Context Source) → Dynamic Role HR Approval

NewPosWFNonUS Dynamic Group Talent Approval → Position Relationship Parent Parent Position (Context Target , Relationship to Approver Position ) → Dynamic Role HR Approval

Rule New_Position_WFL : IF Original Record.Position Code = Null and Position.Company.Country = USA → wfConfig = NewPositionUS; ELSE IF … Country ≠ USA → NewPosWFNonUS . Assign it under Save Rules , then test by adding a US position and a non-US lower-level position.

Managing Position Workflow Requests

Approvers act from Home Page engagement cards: quick approval with or without comments, drill-down, update transaction , post a comment, send back , and assign to me for group approvers. View Pending Workflows leads to My Workflow Requests , which requires Manage Workflows > Professional Edition Manage Workflow Requests .

Advanced To-do Key Details customizes the Key Details column for position requests. In Manage Data > Create New > Advanced To-do Key Details , choose the Position object and up to four fields , for example externalName, company, businessUnit, and jobCode. Only the Position object supports this , and each company can have only one instance . Edit it, or delete and recreate it.

Right to Return Setup

In Position Management Settings > Right to Return (global assignment example):

  • Setting Value
  • Unassign from Position Rule from Unassigned Incumbent from Position for Right to Return
  • Create Right to Return Rule from Create Right to Return for Incumbent
  • Event Reason for unassigned Position Away on Global Assignment (AGA)
  • Event Reason for assign Position Back from Global Assignment (BGA)

THR79's test adds a long-term global assignment to Ace Germany on the Sales Director, Europe position, with a workflow approved by a Talent Approval member. The host position shows the Global Assignment icon and becomes fully staffed. The home position shows Away on Global Assignment . After the planned end date, the host position returns to TBH and the icon disappears.

Rule Functions for Position Management

  • Function Returns Inputs
  • Get Incumbent By Position The incumbent's user ID; only one if several Position code and start date

Get Next Available Manager By Position The next available manager in the position hierarchy Position code and start date

Get Matrix Position Code By Type The matrix position of a given type Position code, date, matrix relationship type

Get Number of Child Positions The count of child positions Position code, date, include inactive?

  • Get Pay Range By Position The pay range for a position Position data
  • Get Pay Range Attributes Minimum, maximum, midpoint, currency, frequency Pay range, field, date

Is Position Below User's Position in Hierarchy (New Version) Whether a position is in and below the user's hierarchy Can be used for new positions