SAP Knowledge Base Article - Public

2729221 - Integration Center: Non-Effective Dated to Effective Dated Entity Navigation


You are creating an integration using Integration Center

You add a new field to the Integration Center Preview and you are propmted with the below message:

"You have used one to many field navigation while adding this field. You have used default field filter with value <first> or not used any field filter.

Do you want to add this field?"

[Yes / No]



  • BizX
  • SuccessFactors
  • Integration Center

Reproducing the Issue

Using Employment Information (EmpEmployment) and Job Information (EmpJob) as an example use case:

  1. Create an simple outbound integration in Integration Center
  2. Choose a non-effective dated starting entity (EmpEmployment)
  3. Add a new simple associated field
  4. Navigate to an effective-dated entity (EmpJob) and choose a field from this entity

Once you add this field from EmpJob entity, you will see the below prompt / alert:



This message is displayed due to the one-to-many relationship between the chosen entities that you have navigated to / from:

For example:

  • A one-to-many relationship exists between entities Employment Information (EmpEmployment) --> Job Information (EmpJob)
  • Such relationships usually involve non-effective dated (one) and effective dated (many) entities:
  • In the image below, the one to many relationship between EmpEmployment and EmpJob, is displayed 
  • User ID is the business key used to maintain the relationship between entities



There is no resolution needed for this message, this message is in place to inform you that:

  • As you have chosen to pull a field from an effective dated entity, by default, Integration Center will return the latest record available for the chosen field.
  • i.e. For one EmpEmployment record, there can be Many EmpJob records (one-to-many relationship)
  • This message simply states, that for the chosen field from EmpJob, the latest / most recent value maintained will be returned, unless otherwise specified

If your requirement is to choose a value that is not the latest value contained in the field

You can do so via Choose Association > Field Filters > Choose the desired value from the dropdown shown below.




Navigations to effective dated entities are shown in the below manner:

The multiple boxes located to the left of the navigation field (shown below) symbolises the navigation to an Effective Dated entity:



To provide a visual example of what the above mentioned selection actually does, see below:

  • If we have a data change (job title) in an employee's job information and now a new job information record exists for this employee.
  • If this employee's job title has changed from Retail Associate --> Administrative Assistant, as shown in the below screen shot:



Leaving the filter as default <first> the job title - 'Administrative Assistant' will be returned, as this is the latest / most recent job title for employee:



If we choose <2nd> this will return the previous job title of - 'Retail Associate' will be returned, as this is the second entry, relative to the most recent job title that is maintained in the system currently.




  • You may have to implement the 'Effective From' & 'Effective To' Time-Based Filters, as you are pulling data from an effective dated entity
  • This is because only the active / latest record will be returned from an effective-dated entity, unless fromDate & toDate parameters are used


See Also

Integration Center Guide


  • One-to-many
  • Non-Effective Dated
  • Effective Dated
  • EmpJob
  • EmpEmployment
  • Navigation
  • <first>
  • <2nd>
, KBA , LOD-SF-INT-INC , Integration Center , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , LOD-SF-INT-ODATA , OData API Framework , How To


SAP SuccessFactors HCM Core all versions