This blog compiles frequently asked questions from SAP SuccessFactors Knowledge Base Articles (KBAs), focusing on Employee Central, Job Information, Compensation, and Position Management. Each question is answered in a simple, step-by-step format to help functional consultants, admins, and support teams quickly resolve common issues and configuration scenarios.
How to configure the Event Reason field in Job Information?
Answer:
Option 1: Manage Business Configuration
1. Go to Admin Center → Manage Business Configuration
2. Navigate to jobInfo (HRIS Elements)
3. Add field event-reason
4. Set:
– Label = Event Reason
– Enabled = Yes
– Mandatory = Yes
– Visibility = Edit
5. Save
Option 2: Succession Data Model
1. Export Succession Data Model
2. Add <hris-field id=”event-reason”> under jobInfo
3. Import updated model
Note:
- Defining the field in SDM allows translations and onChange business rules.
- If not defined, the system uses a hard-coded field with no change in UI behavior.
What happens if Event Reason is NOT defined in the Data Model?
Answer:
1. System still shows hardcoded permission
2. No UI change
3. Field behaves as standard
What happens if Event Reason IS defined in the Data Model?
Answer:
1. Hardcoded permission disappears
2. Custom field appears in permissions
3. No UI change
How to sync Compensation Info to Job Info and Position?
Answer:
1. Create Business Rule (Base: Compensation Info)
2. Assign rule as onSave
3. Create Event Reason with Follow-up Activity = Position Reclassification
4. Maintain fallback event reason
5. Update Job Info → Position Sync Rule
6. Add required logic to rule
Note:
- Ensure rule logic includes the new pay component mapping for synchronization.
How to undo an accidental employee termination?
Answer:
1. Go to Employee → Job Information
2. Locate termination record
3. Delete the termination record
If still incorrect:
4. Perform Full Purge Job Info Import (without termination)
Post-check:
5. Validate position status
6. Validate reporting relationships
Note:
- Check position status, reporting relationships, and manager hierarchy after correction.
How to configure Off-Cycle Event Batch for future-dated scenarios?
Answer:
Step 1: Create Job
1. Go to Scheduled Job Manager
2. Create job → Offcycle Event Batch Processing
3. Set schedule (daily recommended)
Step 2: Create Rule
4. Create rule (Base: Job Info)
5. Configure PM form trigger logic
Step 3: Configure Batch
6. Go to Manage Data → OffCycleEventBatch
7. Assign rule
8. Define filters (e.g., Hire Date ≥ today)
9. Save
Note:
- Business rules cannot launch forms for terminated employees.
- Ensure job runs after HRIS Sync job.
How to sync Employee Status from Job Info to Employee Profile?
Answer:
1. Create custom field in Employee Profile
2. Grant RBP View permission
3. Add field to People Profile
4. Add mapping in Data Model:
– emplStatus → custom field
5. Run Full HRIS Sync Job
6. Validate results
Note:
- Source field is emplStatus from Corporate Data Model.
How to hide “Changes Pending Approval” in Job Information?
Answer:
1. Go to Manage Permission Roles
2. Navigate to User Permissions → Employee Data
3. Disable Transactions Pending Approval
Note:
- This controls visibility across multiple portlets including Job Info and Compensation.
How to fix JobInfoInconsistentEndDateCheckerror?
Answer:
1. Go to Admin Center → Check Tool
2. Run JobInfoInconsistentEndDateCheck
3. Click Quick Fix
4. Select correction
5. Approve and run
Note:
- Ensure only one record has end date 12/31/9999.
How is FTE calculated in Job Information?
Answer:
1. FTE is derived from Standard Weekly Hours
2. System auto-calculates if:
– FTE is NOT editable
– Standard Hours exist
Auto-calculation will NOT work if:
– FTE is editable
– No standard hours exist
– Rule overrides FTE
Note:
- FTE is derived from Standard Weekly Hours, not manually controlled.
Can I calculate Standard Hours from FTE?
Answer:
Yes (custom setup):
1. Configure Propagation XML
2. Create Business Rule (onChange on FTE)
3. Assign rule to jobInfo → fte field
How to change the label of Job Information section?
Answer:
1. Export Succession Data Model
2. Update <hris-section id=”jobFieldsList“>
3. Change label (e.g., “Job Details”)
4. Import updated model
Note:
- Label change is controlled via XML translation tags.
Why does Job History show a specific time zone?
Answer:
1. Time zone comes from logged-in user profile
2. Not from employee data
To change:
3. Update user time zone in profile
How to trigger business rules during Job Info import?
Answer:
1. Go to Manage Permission Roles
2. Enable Employee Central Import Entities
3. Ensure:
– Fields are blank in import
– No overwrite flags
Note:
- Rules only populate fields if they are blank in import file.
How to correct Job Information using Full Purge import?
Answer:
1. Extract current data via Adhoc Report
2. Download Job History template
3. Prepare clean data:
– No end dates
– Correct sequence
4. Go to Import Employee Data
5. Select Full Purge
6. Upload and validate
Note:
- Full purge replaces all existing records with imported data.
How can I update Job Info based on seniority?
Answer:
1. Create OffCycleEventBatch
2. Define filter (e.g., service years ≥ X)
3. Create rule to update Job Info field
4. Schedule BizXDailyRulesProcessingJob
5. System updates records automatically
Note:
- Only one entity type can be modified per rule.
How to calculate FTE based on workdays?
Answer:
1. Create Business Rule
2. Use functions:
– Get Number of Calendar Days
– Get Number of Days in Year
3. Apply rule to Job Info
Note:
- This is a custom solution; standard system calculates FTE from hours.
How is Job History Audit Trail Time Zone Determined?
Answer:
- Navigate to Job Information > History
- Check “Last Updated By” section
- Verify user’s time zone in UDF
- Update time zone in Job Info if needed
- Sync changes
Note:
- Time zone is based on logged-in user, not employee.
This FAQ blog is designed for quick troubleshooting and configuration guidance in SAP SuccessFactors Employee Central, helping teams reduce resolution time and improve system understanding. For more Information checkout our 3Core Systems AMS.
