2589696 - Date format changed from "DD/MM/AAAA" to "MM/DD/YYYY" in spanish Mexico

SAP Knowledge Base Article - Public

2589696 - Date format changed from "DD/MM/AAAA" to "MM/DD/YYYY" in spanish Mexico

Symptom

You have noticed that since Jan 13th the date format for Spanish users has changed which is causing some inconsistencies and errors in the instance.

KB1.jpg

KB2.jpg

Jira.jpg

Environment

SAP SuccessFactors Employee Central (EC) - All Versions

Reproducing the Issue

  1. Go to add new employee or any UI where you also need to fill date;
  2. See that the date format has changed 

Resolution

This is a known issue which engineering have fixed with b1802.

There is also a Patch fix targeted for the 27-1-18.

If that changes we will update this KBA.

Workaround until the release:

IMPORTAMT NOTE: The workaround described below will not correct the way the date is displayed (currently MM/DD/YYYY) but it will prevent the error "Object does not exists or you do not have authorization" of happen.

1. Change language toes_ES

2. Use the "Manage Languages" tool from admin center, to restore those values for these 3 languages (esMX, caES and koKR).

ca_ES: "COMMON_DateFormatExample","DD/MM/AAAA"
ko_KR: "COMMON_DateFormatExample","YYYY/MM/DD"

IF YOU ARE APPYING THIS kba FOR SPANISH MEXICO, PLEASE UPDATE THE LIST OF TAGS BELOW:

Key es_MX
COMMON_DateFormatExample DD/MM/AAAA
DATETIMEFORMAT dd/MM/yyyy HH:mm:ss a z
DATEFORMAT_UI $(DATEFORMAT_EXAMPLE)
ADMIN_COMMON_DATE_FORMAT_EXAMPLE DD/MM/AAAA
ADMIN_CPP_dateString DD/MM, HH:mm
ADMIN_CPP_dateOnlyString DD/MM
ANALYTICS_LIST_VIEW_BUILDER_INVALID_DATE_FILTER Introduzca una fecha válida en uno de estos formatos:<br>DD/MM/AAAA,D/M/AAAA,D/MM/AAAA,DD/M/AAAA
COMMON_MONTH_YEAR_DATE_FORMAT_UI (mm/aaaa)
COMMON_DateFormat dd/MM/yyyy
COMMON_TimeFormat HH:mm:ss
COMMON_MEDIUM_DateFormat d MMM yyyy
COMMON_LONG_DateFormat d MMMM yyyy
COMMON_DateTimeFormat d MMM yyyy HH:mm
COMMON_SHORT_DateFormat dd/MM/yy
ECT_PP3_DateFormat dd MMM, aaaa o dd/mm/aa
EMPFILE_EDU_DATEFORMAT dd MMMM yyyy
FB_HIERARCHICAL_REPORTS_MM_YYYY (mm/aaaa)
GOALS_BIZX_TREND_MONTH_DAY_FORMAT dd/MM
RECRUITING_JOB_POSTING_TIME_FORMAT_WITH_ZONE HH:mm z
RECRUITING_JOBREQ_CHANGE_HISTORY_DATEFORMAT dd/MM/yyyy hh:mm
RECRUITING_AUDIT_COMMON_DateFormat dd/MM/yyyy hh:mm:ss
RECRUITING_INT_SCH_AVAIL_TIME_LABEL_FORMAT HH:mm
RECRUITING_INTERVIEW_SCHEDULING_WEEK_COLUMN_FORMAT ddd d/M
RECRUITING_INTERVIEW_SCHEDULING_DAY_COLUMN_FORMAT dddd d/M
TIMEANDLABOR_CALC_BASE_WRONG_EXTERNAL_CODE Utilice el formato IDusuario_AAAA-MM-DD ({0}).
TIMEANDLABOR_TIME_DATEFORMAT_STARTDATE EEEE, d MMMM
TIMEANDLABOR_TIME_DATEFORMAT_ENDDATE EEEE, d MMMM, yyyy
COMMON_THIS_YEAR_FORMATTER MMM d
DEVELOPMENT_Date_Convert_Message DEVELOPMENT_Date_Convert_Message
DEVELOPMENT_Date_Convert_Message_Start Formato no válido de la fecha de inicio. Ejemplo: DD/MM/AAAA
ADMIN_CPP_hourOnlyString HH:mm
RECRUITING_INVALID_DUE_DATE Se necesita la fecha límite (se esperaba DD/MM/AAAA)
DATEFORMAT dd/MM/yyyy
DATEFORMAT_EXAMPLE dd/mm/aaaa
OM_COULD_NOT_PARSE_DATE No se pudo analizar la fecha.  Utilice el formato correcto (DD/MM/AAAA).

EXPLANATION ON HOW TO APPLY THE WORKAROUND:

  1. First identify which language you need to correct esMX, caES or koKR:

If your user is logged in Spanish Mexico for example then you need to correct es_MX and so on, you only need to correct the three languages if in your company you have users using those three languages;

  1. In Admin Center under the Tool Search type "Manage Languages" and this will open a screen as shown below:

KB3.jpg

  1. Search for the language you need to correct in this example es_Mx there pay attention on the box that will show either a "-" signal or a "+" signal and follow the next processes accordingly:

KB4.jpg 

HOW TO PROCEED IF YOU HAVE A "-" SIGNAL:

Note: for this session let's user the language es_ES as example

  1. If you have the "-" signal than you need to add a custom language configuration, for that first you click in "Add" and a pop up will ask you to provide the custom language name for example es_ES_cus:

KB5.jpg

  1. After you do this you'll see that a plus signal will appear for the language you need to correct, now, please follow the steps outlined in the session "HOW TO PROCEED IF YOU HAVE A "+" SIGNAL":

KB6.jpg

HOW TO PROCEED IF YOU HAVE A "+" SIGNAL:

  1. First thing you need to do is to click on the plus signal which will expand to show you the customa language that exists or that you have just created:

KB7.jpg

  1. Mark the checkbox of your custom language:

KB8.jpg

  1. After doing this, scroll to the bottom of the page and in "For Checked Items Above:" choose download, with this a CSV file will be downloaded in your PC:

KB9.jpg

  1.  Now you can open the CSV that you have downloaded and add the tag provided in this KBA and the respective date format, the tag is always COMMON_DateFormatExample and the date format depends on the language for example for es_ES should be DD/MM/AAAA so es_ES_cus will use DD/MM/AAAA:

The CSV will have ony one column called "key" you'll need to add one more with the Locale code for the custom language you have just created for example in this case es_ES.

This is how the CSV must looks like:

KB14.jpg

If you are importing for Spanish Mexico it will be es_MX and for Korean ko_KR.

Important note: if when you open this CSV you see that there are already values maintained there do not erase those values under any circumstances, also if the file alreadu has values you'll see that the second column already exists, in order to be able to import you need to rename that column back to your locale for example es_ES or es_MX or ko_KR see image below:

KB15.jpg

  1. After Adding the tag and the correc value you need to upload the file, for that first refresh the screen, then check the custom language you have created again:

KB8.jpg

  1. Now scroll to the top of your page and in "Import File" chose the file you have just corrected and click in import:

KB11.jpg

  1. After importing, the date format issue should be gone, if you encounter any problem or you don't have access to "Manage Languages", please contact your partner since the same steps can be done under Provisioning>Manage Languages 

Keywords

El objeto no existe o no dispone de autorización , KBA , lang-5170 , LOD-SF-EC-LOC , Localization & Country Specifics , Problem

Product

SAP SuccessFactors HCM Core 1711