ODI Commit of Headers only when Lines data is loaded successfully

Question

We have a requirement where in we have two interfaces ( headers & lines).
We have to commit data in Headars table only if the lines table gets successfully polulated.We have customized the KM's to remove commit from the headers interface and removed the ddl statements from IKM and LKM which usually do autocommit.We tried commiting the data after the lines interface execution , but that's not working. Though in ODI it displays single session for all executions(header and line), internally it is creating sub sessions.
We are using IKM Oracle Incremental Update-Merge knowledge module.
Execution steps are Procedure 1 --> Procedure 2 --> Headers Interface --> Lines Interface --> Procedure 3 --> Procedure 4.
Kindly provide your inputs.Looking forward to your suggestions.

Answer 1

Anand,
My approach would be different. Essentially your requirement indicates that you need to run DML on header and details table within same transaction cycle. Because for each interface execution, agent makes a separate connection, it is hard to design that into two different interfaces. My approach would be to accommodate both targets into single interface using a special LKM. Below is the procedure in short:
1. Create a data model by adding columns on header table and details table together.
2. Design an interface and put this model as target.
3. Bring the usual sources in the source pain and establish joins
4. Create the mapping for header table and mark them as UD1 in addition to mark them as INSERT or UPDATE as required.
5. Create the mapping for header table and mark them as UD2 (not UD1) in addition to mark them as INSERT or UPDATE as required.
6. All mapping are to be executed in staging.
7. Create a special IKM to include two I$ tables (I$_target_table_1 and I$_target_table_2) using the columns used for UD1 and UD2 mapping respectively. Populate them. To know how to use UD1 and UD2 mappings, look at manual for the documentation of odiRef.getColumnList api.
8. Add two options in the IKM where header and detail table names can be specified.
9. In a trasaction cycle (say, transaction1), insert into header table. In the next step into details table. Commit in the next step. In that way, if insert to details was not successful, job will fail and ODI would terminate the connection without a commit.
If you want to use two interface still, you have to find a way to run both interfaces asynchronously and then the IKM used in the interface for header table should be modified in such a way that after insert it must wait for some kind of communication (in the form of table data or temporary file) to mark the commit. My best guess would be to use jython in the IKM to check for the file. Off course interface writing to detail tables must be sending similar communications at the end of a successful write. If you do not want to use Jython, my advise would be to use PL/SQL procedure (try looking into DBMS_PIPE or DBMS_ALERT, I do not have ready code) to arrange for such a notification. But this is one hell of an extra work and the logic has multiple points of failure that requires still extra work.