2541688 - Odata - How to Update and Use the Standard Field Status from JobApplication Entity as Filter - RCM

SAP Knowledge Base Article - Public

2541688 - Odata - How to Update and Use the Standard Field Status from JobApplication Entity as Filter - RCM

Symptom

This articile explains how to update the standard field status and also how to use this field as a filter on a query over JobApplication entity.

Here is the field declaration from the Odata Data Dictionary:

field declaration.png

Environment

SuccessFactors Recruiting Management (RCM) - All versions

Resolution

The standard field status is a string field. However, when using the field as a filter in a query call or even when updating this field, there are some values acceptable by the system. Not all values are accepted for this field.

Here is an example of some data retrieved from the instance. This screen is from the integration center and contains just a few fields from jobApplication entity to illustrate how the field status is retrieved in a query:

call on the field.png

As shown above, when querying over jobApplication, the value for this field is stored as a string, e.g. Open, however, when using this field as a filter or updating it, the call/payload has to be built using the associated code for the correspondent status.

Here is the acceptable status and the linked codes:

This numerical value...

is mapped to...

0

"Open"

1

"Disqualified"

2

"Closed"

3

"Withdraw"

4

"Saved"

5

"Non Applied"

6

"Draft Application"

In order to use this field as a filter, you have to filter by the code mapped to the status. Here is an example:

<HOST URL>/odata/v2/JobApplication?$format=json&$filter=status eq 4

This is also valid when updating the jobApplication:

Sample Code


../odata/v2/Upsert

[{
"__metadata":{
"type":"SFOData.JobApplication",
"uri":"JobApplication"
},
"candidateId": "1001",
"jobReqId": "902",
"applicationTemplateId": "792",
"appStatusSetItemId": "21",
"status": "0",
"countryCode": "BR",
"questionResponse": "[]",
"faxNumber": "01",
"convictedYes": "Yes",
"zip": null,
"nonApplicantStatus": "0",
"source": "1",
"rating": "0",
"candidateSource": { "id": "1516"},
"convicted": { "id": "381"},
"relativesEmployed": { "id": "381"}
}

Keywords

jobApplication Entity; Odata; status; upsert; insert; update; , KBA , LOD-SF-RCM , Recruiting Management , How To

Product

SAP SuccessFactors Recruiting all versions