Global User Functions Are Not Replaced With Their Code When Used in ODI 12c Datastore Constraints
(Doc ID 1662756.1)
Last updated on JUNE 16, 2022
Applies to:Oracle Data Integrator - Version 18.104.22.168.0 to 22.214.171.124.1 [Release 12c]
Information in this document applies to any platform.
In Oracle Data Integrator (ODI) 12c, the Global User Functions - i.e. "f_is_null($(p_string))" - are not replaced by the stored implementation within the scope of ODI code generation when used in Datastore Constraints. When checking the Datastore Constraints with either static control (at Datastore/Model level), or Flow Control (at Mapping execution), "f_is_null($(p_string))" will be used in the generated code instead of the expected implementation - i.e. "isnull(mycolumn)".
Using these Functions in Mappings, as Filter or target expression, a code replacement is executed without problems.
The problem only occurs if these Functions are used in the scope of Constraints.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document