At times, the source system for BIAPPS might have additional tables that you want to extract the data from and get into BIAPPS. This blog specifies the steps on how to import a source table that is there in Source system but not present in the BIAPPS ODI repository.
It is assumed that the user has already registered the Source system before attempting any of the steps in this document. Please refer to the BIAPPS documentation incase you need help with the Source Registration.
First step is to identify the model in the BIAPPS repository corresponding to the source system in question. For the purpose of the blog, we will assume there is a EBS table CST_ITEM_COST_DETAILS that we want to import from EBS 12.2 Source system. The models are visible under Model tab in the Designer window of ODI studio. Select the right model corresponding to the Source System Version and then double click on the model in ODI studio. Below screenshot shows the EBS 12.2 model opened.
Once you have the model open in ODI Studio, select the Reverse Engineer tab and click on Customized. This will allow the user to select the BIAPPS RKM. Ensure that the RKM relevant for the Source System is selected. In the above example, the RKM ought to be RKM BIAPPS E-Business Suite(Oracle).BI Apps Project. Specify the table you want to import using the LIST_OF_TABLES option. You can leave the other parameters as defaults. In the example above, the LIST_OF_TABLES would be set to CST_ITEM_COST_DETAILS to import a table called CST_ITEM_COST_DETAILS in the source table.
Once the appropriate RKM is selected and the required table specified in the RKM options, click on Reverse Engineer on the top to start the process
Once you start the reverse engineer process, it will start a session that is visible from Operator just like any other scenario session. Monitor that session to check if the process completed. If the session failed, then view the session log to see the reasons for failure. Screenshot below show the session in progress as visible from Operator.
Once the run completes successfully, you should be able to see the desired table in the ODI repository. The table would normally get placed in the appropriate sub-model. Certain RKMs (like the one for BIAPPS warehouse) would place it in a sub-model like others. If you are not able to locate the newly imported table (as there are many sub-models), you can run a backend query against the ODI repository to identify the sub-model it got imported under.
select m.mod_name,s.smod_name, t.res_name table_name
from snp_table t
inner join snp_model m on
inner join snp_sub_model s on
t.i_sub_model = s.i_smod
Some of the common mistakes that should be avoided are listed below:
a)Open the model
b)Go to Reverse Engineer Tab
d)Provide the table name in the mask field
e)Click on Reverse Engineer
f)The table should then get imported directly under the model (not under any sub model). Now move the table to the desired sub model.
Refer to ODI standard documentation for more details