SAP Knowledge Base Article - Public

3063678 - Entry Date Field Logic via Centralized Services


When carrying out Job Infomration Update using; Job History imports/API, JobHistory UI or MSS when Centralized Services is enabled, a different logic from the prior release is being applied to the calculation of Entry Date fields:

The Entry Date Fields are as below:

  • Job Entry Date
  • Position Entry Date
  • Company Entry Date
  • Location Entry Date
  • Department Entry Date
  • Pay Scale Level Entry Date

Please Note: this is also applicable to features which update Job Information using the import framework, such as Position to Job Information synchronization or Leave of Absence Record Creation.


SAP SuccessFactors Employee Central


  • This is caused by improved logic added via Centralized Services Imports for Job Information
  • These fields are system calculated when Job Classification, Position, Company, Location, Department or Pay Scale Level are changed as detailed in the following handbook page:
    SAP SuccessFactors Data Model Reference Guide: Entry Dates and TimeIn Calculation for Job Information
  • Via the UI you could not manually manipulate these field values or use a rule to set them.
  • A functional gap existed, where you could set the value manually on import and overwrite the system logic.
  • This functional gap was closed in the 1H 2021 release with the introduction of Centralized Services for Job Information.
    Via import, when Centralized Services for Job Information is enabled, these fields can no longer be manually set.
    The system logic is used on import.


  • If your business need requires an Entry Date field, whose calculation deviates from the system logic, a custom date field can be used for this purpose.

Please note:

  • Position to Job Information Sync: Unless a workflow is involved pos2jobinfo sync is always using Centralized Services. When a workflow is triggered Centralized Services is not used. 
    This does not depend on the setting in Company System and Logo settings.
  • Leave of Absence: Job Information updates via Leave of Absence (LOA) always uses Centralized Services. This does not depend on the setting in Company System and Logo settings.
  • Off Cycle Event Batch: Updates to Job Information via Off Cycle Event Batch always uses Centralized Services. This does not depend on the setting in Company System and Logo settings.

Adding a custom date field: 

  1. Adding a custom date field can be done via Manage Business Configuration or a Data Model upload;
  2. Custom-date1–50 can be used for Job Information;
  3. Once the field is added, permissions must be provided for the field;
  4. You can then decide to manually enter dates for the field or use a rule. If the rule option is chosen, it can be added at this stage.
  5. The data needs to be added to this field for users, and it can be done in various ways: via incremental import, full purge import or via the Mass Change tool. 
    Please see the below mentioned KBAs for more details. 

Custom Entry Date Values Allowed for Job Information in Migration Scenarios:

For customers migrating data using imports and APIs, it is now possible to edit entry date fields in Job Information. Entry dates are generally calculated by the system. However, they can now be manually updated in the following cases:

  • Records for the very first record of the history (this is typically the hire record)

  • Records for which the base field changes compared to the previous record

If no entry date is provided, the system calculated one is saved.

For more information on how Custom Entry Date Values are allowed for Job Information in Migration Scenarios, please review the following links:

See Also


jobEntryDate, positionEntryDate, companyEntryDate, locationEntryDate, departmentEntryDate, payScaleLevelEntryDate, Pay Scale Level Entry Date, Department Entry Date, Location Entry Date, Company Entry Date,Position Entry Date, import, api, upsert, ECT-127956, ECT-153911, 1H 2021, 2105, b2105, pos2job, loa, leave of absence, position to job information, ECT-202301,  Custom Entry Date Values Allowed for Job Information in Migration Scenarios, Custom Entry Date,  Migration Scenarios, Migration, cutover, cut over, , KBA , LOD-SF-EC-JOB , Job Information , LOD-SF-INT , Integrations , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , Problem


SAP SuccessFactors Employee Central all versions