Symptom
- Integration Center issues with associating the first calculated field in a second calculated field.
- Cannot reference the first calculated field when creating a second calculated field.
- Issue occurs in the Integration Center UI.
- The calculated field does not appear in the associate/search results even when using the IF condition.
- No error message displayed.
Environment
- Product: SAP SuccessFactors Platform
- Integration Center
Reproducing the Issue
- Create a calculated field in Integration Center.
- Create a second calculated field in the same Integration Center integration.
- Attempt to reference the first calculated field inside the second calculated field (for example, as an operand or within an IF condition).
- Observe that the first calculated field is not available in the field search/associate results.
Cause
- By design, Integration Center calculated fields cannot reference other calculated fields. Calculated fields can only reference fields exposed by the OData API.
Resolution
It's not possible to refer a calculated field inside another calculated field. Calculated fields can only refer fields from OData API. So the workaround is to create the first calculated field and its logic via a business rule in the metadata, then refer to it in the subsequent calculated field. We won't be able to help with that configuration, though, as it's a consulting matter.
See Also
Keywords
integration center, calculated field, nested calculated field, reference calculated field, associate field search, field not found, if condition, odata api, metadata business rule, field not available, by design, ui, search results, successfactors integration, integration limitation , KBA , LOD-SF-INT-INC , Integration Center , Problem
SAP Knowledge Base Article - Public