When executing an interface and using a filter to define subsets of data for intergration, we would like to ensure that the integration interface does not execute the IKM ( and associated TRUNCATE target step) when no records are loaded in the source data stores.
The simplest way of achieving this is to separate the logic into a set of package steps including an ODI variable to store the number of records transferred and to serve as an evaluation step.
The package contains the following steps:
1. Declare ODI variable step
2. an integration interface which transfers source records into a temporary table.
3. A refresh variable step using a sql statement which counts the number of records that have been transferred to the temporary table
4. Evaluate the variable and if no records the package will terminate. other wise the package will execute the following step.
5. Execute an integration interface to load data from the temporary table to the ultimate target table.
Conditionaly replace data in a target data store
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Note: only a member of this blog may post a comment.