3087941 - One-to-many behavior in Integration Center

Integration Center was designed to support simpler integration scenarios and the challenge with one-to-many relationships is a known limitation of the tool and has existed since its introduction.

For scenarios that require greater flexibility, the recommended approach is to use the OData API together with middleware such as CPI. That route gives you much more control over the data structure.

This KBA will cover the following topics:

1. What is a one-to-many navigation?
2. How to identify a one-to-many navigation?
3. One-to-many behavior in Integration Center
4. How to handle one-to-many behavior
5. Issues when using <First> or other order-related Field Filters

"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 HCM Suite
  
  • Integration Center

order, guaranteed, 1:M, one to many, one-to-many, many, navigations, navigation, wrong results, undesired results, unexpected, predictable, first, field filters, IC, integration center, integration centre, sf, successfactors , KBA , LOD-SF-INT-INC , Integration Center , How To