Symptom
An Inbound Integration Center job (writing data into SuccessFactors via OData) returns a message such as:
Warning or Error: "Mandatory value missing"
Example: "User: Mandatory value is missing for gender for record userId …"
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Environment
SAP SuccessFactors HCM Suite
Cause
This behavior is driven by OData API metadata for the target entity/field. Fields marked as required OR not nullable in metadata cannot be NULL or blank, and this configuration cannot be changed in Integration Center.
Scenario 1 – Warning (job completes)
A warning is shown, but the job still completes.
- The target field is not required and not nullable in OData metadata: Required = FALSE & Nullable = FALSE
- Meaning: The field must contain a value (cannot be NULL/blank).
- Check in: Admin Center > OData API Data Dictionary > [Entity] > Nullable
Scenario 2 – Error (job fails / record rejected)
An error is shown and the job fails.
- The target field is required in OData metadata: Required = TRUE
- Meaning: The field must contain a value (cannot be NULL/blank).
- Check in: Admin Center > OData API Data Dictionary > [Entity] > Required
Resolution
Scenario 1 (Warning only)
- This is expected system behavior.
- Ignore the warning. The job can still complete;
Scenario 2 (Error / mandatory field)
You must ensure mandatory fields always receive a value:
- Map the affected field in Integration Center (target entity field).
- Provide a value for all records, for example by:
- Mapping from a source field that is always populated
- Setting a default/fallback value when the source is blank
- Filtering out records where the required value is missing (if appropriate)
See Also
Keywords
OData, Integration Center, User Entity, Gender Field, Mandatory, User: Mandatory value is missing for gender for record userId, gender. , KBA , LOD-SF-INT-INC , Integration Center , Problem
SAP Knowledge Base Article - Public