SAP Knowledge Base Article - Public

3090729 - Error - Property applicationId is invalid - Insert using Odata - Recruiting Management


When running an insert call to create an offer letter, Odata returns the following error message:

"error": {
"message": {
"lang": "en-US",
"value": "Property applicationId is invalid"

Above error message is seen on Odata Audit logs or as a return in the solution used to run the API calls. 

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Successfactors - Recruiting Management

Reproducing the Issue

Run an insert operation on OfferLetter entity

System returns the error message "Property applicationId is invalid"


The error happens if the status of the applicant you are trying to create the offer letter is not categorized as Offer. The Odata infrastructure will always validate the status category once creating an offer thru this method. 

You can check the status category by navigating to admin center > Edit Applicant Status configuration > Select the correct status set > Verify status category:


In order to resolve this issue there are two main options:

1 . Non Configuration Required

Move the candidate to a status with the category set as offer. This approach does not require any configuration change. 

2 . Configuration Change Required

The second option requires a configuration change. For example, if you are trying to create an offer for the status 29 (Background as shown on example above), the system will return the error. If you want to make this status valid for odata, the status need to be changed from Screening to Offer. 

In order to make the status category you need either provisioning (back-end) access or contact a partner for this change.

  1. Go to provisioning
  2. Manage Recruiting 
  3. Applicant status configuration
  4. Edit Base
  5. Select the desired status and hit Take Action
  6. On the pop up, change de status category as necessary
  7. Hit Save
  8. I'm Done

Note: The change seems simple, however, every change brings impacts to the system. For this reason, this change needs to be conducted by a partner so the impact can be evaluated and change performed if possible. 

See Also

SAP SuccessFactors HXM Suite OData API: Reference Guide


KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem


SAP SuccessFactors Recruiting all versions


Pasted image.png