How to load multiple target tables simultaneously in single interface?

Question

I have a requirement where I have to load data into two target tables in single interface simultaneously. Reason is to populate parent-child relationship on target side as it is coming from the source side.
For eg: I have 2 headers and 10 corresponding lines in source. Now I want load 2 headers into T1 and 10 lines into T2 simultaneously.
Eg. SOURCE_TABLE
HeaderId HeaderDesc LineId LineDesc
1 AAA 10 QQQ
1 AAA 20 WWW
2 BBB 30 ZZZ
2 BBB 10 XXX
TARGET_TABLES:
TARGET_HEADER
HeaderId HeaderDesc
1 AAA
2 BBB
TARGET_LINE
HeaderId LineId LineDesc
1 10 QQQ
1 20 WWW
2 30 ZZZ
2 10 XXX
I would appreciate if anyone can provide solution in this scenario.
Thanks in advance.
Giri
Edited by: user10993896 on Apr 13, 2009 2:56 PM
Edited by: GiriM on Apr 14, 2009 10:47 AM

Answer 1

Hi Giri,
Let me try to build an example... If I misunderstood your requirement please, let me know!
1) Source table Tab_S
create table Tab_S as (cs1 number, cs2 varchar2(10))
2) Table Parent (P)
create table Tab_P as (cp1 number, cp2 varchar2(10))
3) Table Child (C)
create table Tab_C as (cc1 number, cc2 varchar2(10), cp1 number)
4) Function F$_Tab_C (create it in a ODI procedure)
4.1 - step 1
Create or Replace
Function F$_Tab_C (p_cp2 varchar2, p_cc1 number,p_cc2 varchar2, cp_cp1 number) return varchar2 as
begin
insert into Tab_C (cc1, cc2, cp1)
values (p_cc1, p_cc2, p_cp1);
return p_cp2;
end;
associate this step to an procedure option like "Create_Function"
4.2 - step 1
Drop Function F$_Tab_C
associate this step to an procedure option like "Drop_Function"
4.3 - Step 2
Disable the FK constraint and parent and child
associate this step to an procedure option like "Disable_Constraint"
4.4 - Step 3
Enable the FK constraint
associate this step to an procedure option like "Enable_Constraint"
5) ODI interface:
Source: Tab_S
Target: Tab_P
Mapping:
cp1 ---> cs1
cp2 ---> F$_Tab_C(cs2, 123, 'abc', cp1)
6) ODI Package with all flow:
6.1 - Drag and drop the procedure and put the options:
"Create_Function" yes
"Disable_Constraint" yes
"Drop_Function" no
"Enable_Constraint" no
6.2 - Drag and drop the interface
6.3 - Drag and drop the procedure (again) and put the options:
"Create_Function" no
"Disable_Constraint" no
"Drop_Function" yes (optional, can let as NO if you wish)
"Enable_Constraint" yes
These are the necessary steps.... Maybe there is some syntax error because I build all in a notepad and do not compiled it in the DB. It is just to show you the general idea.
Maybe you can be a little afraid about disable the FK but it is OK because you can guarantee the relationship by logic (funcion).
The only point is that you must be the only one working at the target tables during the process.
Make any sense in your case?