SAP Knowledge Base Article - Public

2405802 - Date Format Error during Foudation Data Import

Symptom

We have a large number of import jobs scheduled to run daily that are of the type "Foundation Data Import".

A lot of records now fail in these jobs. The error messages are  of this type:

"Effective start date cannot be null.,effectiveStartDate: 22/10/2014 is not a valid date value.","".

I suspect that something has changed so that dates  are now expected to be of a different format than the one we have used so far (dd/mm/yyyy).

(Nothing has changed in the way the data files, that come from different sources, are sent to Employee Central.)

 

Reproducing the Issue

> Schedule Jobs 

> go to Monitor Job for error reports

2016-12-16_12-00-29.jpg

Cause

For any Foundation Object that is on MDF, the only date format that is accept on import is MM/DD/YYYY.

MDF import does not currently support the logged in users locale, it will Always operate on US date format- This is expected behaviour.

 For any Foundation Object that is not on MDF, it will respect the logged in user locales date format.

 

Resolution

Make sure to use the US date format i.e.  MM/DD/YYYY

See Also

1935476 - Date format does not match selected Locale

Keywords

Date Format User Locale Effective start date cannot be null , KBA , LOD-SF-EC-FOO , Foundation Objects - MDF & Legacy , Problem

Product

SAP SuccessFactors HCM Core 1611