When defining the Age of the Job Requisition as "Posting Start Date", the system always considers the Start Date from the latest Posting change.
For example: The Job Requisition is posted for the first on 01/01/2023 (Jan 1st, 2023) and the gets unposted after some days. The Posting Start Date on that moment is 01/01/2023. The Job Requisition is then re-posted on 10/01/2023 (Jan 10th, 2023). The Posting Start Date now is 10/01/2023 and no longer the first Posting Start Date 01/01/2023.
Would this be an expected behavior?
"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 Recruiting Management
This is an expected behavior.
The system considers the Posting Start Date from the latest posting.
As workaround, if you have a business requirement to set the first Posting Start Date as Job Requisition Age, you can create a Business Rule to automatically populate any of the available fields in Start Date picklist with the first Posting Start Date date and use this field as the aging date.
The Business Rules will be structured as the following:
The <selected field> must be NULL to trigger the rule. If the <selected field> already has a value, the process won't be required.
Then, set the <selected field> to be equal to Last Modified Date from the Job Posting (select the type of posting).
Based on that, the Business Rule will trigger for the first time the Job Requisition is posted and won't trigger again as the <selected field> is already filled.
Save the Business Rule on Manage Rules in Recruiting as OnSave.
Please refer to the list of date fields that can be used as option:
- Date Created
- Approved Date
- Closed Date
- External Posting Start Date
- External Posting End Date
- Internal Posting Start Date
- Internal Posting End Date
- Latest Hold Removal Date
- Job Start Date
- Due Date
- Actual Start Date
posting, start, date, age, workaround , KBA , LOD-SF-RCM , Recruiting Management , Problem