OBIA Notes

1. To setup the source system and target system configurations, login to BIACM using a user that has Admin privileges (in this case, BIAppsAdmin). Logging in with normal user like weblogic will not allow doing the system setup.
2. On change of source connection details, suggested option is to edit the connection details of the existing source system setup and not to create a new source connection setup. The editing of the source connection is to be done from ODI studio.
3. The target data warehouse connection is setup between the BIACM and the warehouse by updating the DataSource Number of the Target Datawarehouse to 999 from ODI Studio. This results in the Target Datawarehouse connection details to show automatically in the system setup tab in BIACM.
4. Do Provide correct path for Source Files either from CM or ODI Studio(Under Topology Tab>>File)
5. Datasource Number being provided while creating the source system setup is very crucial and is referenced throughout.
6. Domain and Domain member mappings are similar to the csv setups being done in earlier versions of BI Apps (like 7964). Do update Domain Member Mappings Information. This information is explained in Detail in the later sections.
7. To view runtime values of parameters or session values, pick the session ID from the load run.  Login to ODI Console -> Sessions -> Search for the session ID and then look for parameter values. OR in the ODI studio open the session and find the values in general tab 

8. To view the SQL involved in any mapping, go to Design view, identify the mapping -> package -> scenario. Right-click the package and click on execute. In the pop-up dialog, check the “Simulation” checkbox and click OK. This will generate the SQL associated with the mapping.
9. To reset the datawarehouse and load fresh data altogether, there is an option available called ‘Reset Datawarehouse Scenario’. This can be used to do a fresh data load by truncating all existing data in the datawarehouse. This scenario works by actually truncating the W_ETL_LOAD_DATES table and running the load in full mode. 
10. In case of marking a step that has an error as complete, an entry for this step will not be put into the W_ETL_LOAD_DATES table. (Every successfully completed step will have an entry in the W_ETL_LOAD_DATES table with the run date and other details)
11. Incremental Run logic

The W_ETL_LOAD_DATES table has a record for each of the steps executed in the load plan. In case of successful execution of a step in the load plan, an entry for that step will be made in this table.

     When the load is re-run, at each step, it will look for an entry in the W_ETL_LOAD_DATES table for that step. If an entry is present, it will go in incremental load, or it will go in full mode.

     Example query that checks the incremental mode:

SELECT    IF(COUNT(*)>0,'Y','N')
FROM     QUALIFY_DS(W_ETL_LOAD_DATES)
WHERE   PACKAGE_NAME = 'GET_CONTAINER_NAME()'
AND        (DATASOURCE_NUM_ID=#DATASOURCE_NUM_ID
OR           DATASOURCE_NUM_ID=#WH_DATASOURCE_NUM_ID)
AND        ETL_USAGE_CODE = '#ETL_USAGE_CODE'
AND        COMMITTED='1'

12. In an incremental load, to override and run a particular step in full mode, following options can be used,

●        Delete the entry for that step in the W_ETL_LOAD_DATES table

●        Update the “committed” column to 0(zero) in the W_ETL_LOAD_DATES table for the particular step.