Symptom
A status change performed on a candidate application is visible in Change History but is not recorded in the Application Status Audit Trail.
As a result, status transitions may appear in Change History while being unavailable in:
- The Application Status Audit Trail user interface
- The JobApplicationStatusAuditTrail OData entity
This can lead to differences between reports generated from the Application Status Audit Trail and the status information available in Change History.
Environment
SAP SuccessFactors Recruiting Management
Cause
This behavior is expected by design.
The Application Status Audit Trail is designed to record committed status changes. When application statuses are updated as part of an on-save rule execution process, intermediate status transitions are not recorded in the Application Status Audit Trail.
As a result, the audit process responsible for creating Application Status Audit Trail records is not triggered for all status transitions occurring during the on-save rule execution path.
Resolution
The Application Status Audit Trail is not intended to serve as a complete history of all status transitions that occur during application processing.
For scenarios where application statuses are modified through business rules, the Change History should be used as the authoritative source for reviewing the full sequence of status changes. Change History records rule-driven status updates that may not be reflected in the Application Status Audit Trail.
Therefore, discrepancies between the Application Status Audit Trail and the Change History are expected in cases where status changes occur during on-save rule execution. This behavior is aligned with the current product design.
Keywords
application, status, audit, trail, change, history, recruiting, candidate, requisition, rule, onsave, transition, odata, jobapplicationstatusaudittrail, reporting, discrepancy, visibility, tracking, commit , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem
SAP Knowledge Base Article - Public