Currently, substitution variables can be used effectively in parameters and expressions across various components in Oracle Data Integrations. However, there is no support for using substitution variables directly within Target Mappings.
Enabling substitution variable support in Target Mappings would greatly enhance flexibility and reusability, especially in dynamic or parameter-driven data pipelines.
Use Case and Business Need (Required):
In our scenario, the budget year is a key element in the target data structure and needs to change based on the selected year (e.g., Actuals, Budget, Forecast). Users define the target year using a substitution variable. However, because substitution variables aren't supported in the target mapping, we are forced to manually update the mapping each time the year changes.
This becomes tedious and error-prone when working across multiple data flows or environments. If substitution variables were supported in the target definition, we could simply reference something like &BUDGET_YEAR to dynamically determine the correct target — without having to redesign or modify the mappings.
Alternate Solution 1: https://lnkd.in/gHUthBu5