Data split / fork concept in ODI

Question

I am using ODI 11g. If somone can guide me on the following:
In an Interface, Staging Table 1 & Staging Table 2 are joined on one attribute (i.e. sub_account) and are populating a Target Table. I need to implement the following logic to do the incremental update on the Target Table:
Records from above joining Staging Table 1 and Staging Table 2 are to be SPLIT/FORK in following two (2) groups:
•     When PRODUCT_ITEM is null, use SUB_ACCOUNT for incremental update.
•     When PRODUCT_ITEM is not null, use PRODUCT_ITEM for incremental update.
Looking for a help on how to implement above.
Thanks
Edited by: 867760 on Jun 22, 2011 1:02 PM
Edited by: 867760 on Jun 22, 2011 1:07 PM
Edited by: 867760 on Jun 22, 2011 1:09 PM

Answer 1

I am have it the same way in both the interfaces.
In the first Interface has a filter "PRODUCT_ITEM is not null" and select PRODUCT_ITEM as PRIMARY KEY Constraint in Data Model. This works just fine.
In the second Interface, I have a FILTER "PRODUCT_ITEM is null" and select SUB_ACCOUNT as KEY in the property inspector, KEY check box checked for Sub_Account.
Both interfaces are using IKM incremental update, but somehow the second interface is not doing successful incremental update.
Your thoughts on un-successful incremental update for the second interface.
Thank you for your valueable thoughts again.
Best!