3800533 - Two Different Approved Dates for a job requisition in Ad Hoc Reports - Recruiting Management

When an adhoc report is run,  two Different Approved Dates in Ad Hoc Reports for the same job requisition.

• The root cause is that the Route Map is configured with a collaborative step and no exit user is specified for that step.
• When a collaborative step is configured in the Route Map without a defined exit user, the system treats the moment the first step owner opens the form and sends it to the next step as an approved record. This intermediate date is captured in the report alongside the final approval date (when the form is fully approved).
• This is considered expected system behavior for this type of route map configuration.

• Option 1 – Route Map Configuration Fix: Review the collaborative step in the Route Map and define an exit user for that step. This prevents the intermediate step action from being recorded as an approval event, ensuring only the final approval date is captured. 

• Option 2 – Custom Field Workaround: Create a custom date field in the Job Requisition template and configure an OnSave Business Rule to automatically populate this field when the requisition moves from Pre-Approved to Approved status. The rule should include an "IF null" condition on the custom field so it is populated only once and not overwritten on subsequent saves.

         This custom field will then be available in Ad Hoc reports and reflects a single, reliable approved date.

• Job Requisition Pre-Approval Change History - Recruiting Management (Note 2835473)
• How to populate Approved Date on Job Requisition via Business Rule (KBA 2957351)
• Approved date in Job Requisition - Recruiting Management

approved date, job requisition, reports, adhoc report, multiple approved dates, Job Requisition Status Audit,  , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem