3676085 - SF Odata API: FOCompany entity property name discrepancy (effectiveStartDate OR startDate)

SF Odata API: FOCompany entity property name discrepancy (effectiveStartDate OR startDate)

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

• SAP SuccessFactors HXM suite
  
  • Integrations 
    
    • FOCompany entity

1. Navigate to the API Odata API Data Dictionary.
2. The field is named "effectiveStartDate" in Instance A and "startDate" in Instance B.

This property names depend on the configuration for "Manage Data - Element Type Map for EC Migration: LegalEntity (company)":

1. If the configuration entry of "LegalEntity (company)" doesn't exists, system will use default property names. The property name of start date will be "startDate"
2. If the configuration entry of "LegalEntity (company)" exists, but the field mapping of effectiveStartDate is not configured, the property name of start date will be "effectiveStartDate".

If you want to use "startDate" under FOCompany:

1. Please help to add a new line under "Element Field Map for EC Migration".
2. Fill the value "HRIS Field Name"=startDate, "GO Field Name"=effectiveStartDate.
3. Execution SF Odata Metadata refresh: 2171588 - OData API Metadata Refresh and Export in SuccessFactors Cloud - SAP for Me 
4. Then the property name will be changed into "startDate".

Similar other fields in FOCompany:
effectiveStatus -> status
effectiveEndDate -> endDate
effectiveStartDate -> startDate
countryOfRegistration -> country
standardWeeklyHours -> standardHours

effectiveStartDate, startDate, metadata refresh, mdf object definition, element type map, field mapping, inconsistency, property name discrepancy, FOCompany startDate, FOCompany effectiveStartDate, , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , Problem