3256303 - Report on skippedStatus and statusComments Fields in Recruiting JobApplicationStatusAudit OData API - Recruiting Management

Since 2H 2022 release, you can now create a report on the skippedStatus and statusComments fields in the Recruiting JobApplicationStatusAudit OData API.

The enhancement allows users to extract information about all statuses (Skipped and Not Skipped) and comment on any status change, in an application. This update is from Customer Community Idea 233587, Customer Community Idea 200165, and Customer Community Idea 252122.

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

Behaviors in API (differences from the Recruiting V2 Report fields)

The behaviors of skippedStatus & statusComments in API are approximately the same as the Recruiting V2 Report fields 'Skipped Status' & 'Status Comment' besides the followings:

statusComments

1. statusComments cannot be set as a filter as it is filterable="false" in API.
2. If there are multiple lines, in JSON API responses, a newline character "\n" is inserted between lines, e.g., Line1\nLine2\nLine3.
   
   • This is an expected behavior because the status comment is a plain text-area field and "\n" represents a new line in JSON string.
   • Note: In the case of CSV File Output Integration, new line characters "\n" can split the text into different rows. To accommodate new lines, you can select "True CSV" as the Output File Type (see KBA 2621968).

skippedStatus

1. skippedStatus cannot be set as a filter as it is filterable="false" in API.
2. skippedStatus has only status codes (0,1,2) and there is no label in the API.

          Status codes in API vs. Labels in Recruiting V2 Report:

          0 - Not Skipped
          1 - Skipped by user
          2 - Skipped as user does not have permission

Using Integration Centre to create a report starting from JobApplicationStatusAuditTrail entity

Please grant API permissions as per the User Assistance Guide - JobApplicationStatusAuditTrail.

1. Go to Admin Center > Integration Center > My Integrations
2. Click '+Create' button and select an output integration type
3. Search for 'JobApplicationStatusAuditTrail' entity
4. Select fields as needed

The example below is 'Scheduled Simple File Output Integration'. Note: revType is not selectable as per the current design.

Assigning custom labels to skippedStatus codes (0,1,2) using Value Lookup Table

1. Right click on the column header 'Skipped Status'
2. Select Value Lookup Table
3. Click '+ New' to create a lookup table

4. Name the lookup table
5. Click '+' button to add rows (We need to add three rows as there are three status codes)
6. Edit the data

• Input Code: Enter the status code (0,1,2)
• Output Code: Assign a label to the status code
• Description: (optional) Enter a description

7. Click 'Save' button
8. Click 'OK' button and it is done

• User Assistance Guide - JobApplicationStatusAuditTrail
• KBA 2594749 - How to use Value Lookup Table in Integration Center

RCM-67305, 2H 2022 release, b2211, OData, API, skippedStatus, statusComments, JobApplicationStatusAudit, OData API Application Audit Export, Integration Center, permission, [COE0020]OData API Application Audit Export permission in Admin Center is not enabled , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-APP , Applicants and Job Applications , How To