How to configure the DAC for BI Apps 7.9.6.

2
General configuration for all areas.
1. Launch the DAC Client, Go to File >New Source System Container 2. Enter the new container id and name 3. Select Create as a copy of existing container and select the required container to copy. 4. Once the copy has completed (takes a few minutes) ensure that your new container is selected in the drop-down box to the right of the Execute button. 5. Click on the Source System Parameters tab and locate the $$INITIAL_EXTRACT_DATE parameter. 6. Change the date in the Value field to suit requirements. 7. Click on the Source System Parameters tab and locate the *GLOBAL*CURR_CODE parameters (three should be returned) 8. Change the currency code in the Value field to suit requirements. 9. Click on the Source System Parameters tab and locate the *RATE* parameters. 10. Change the exchange rate name in the Value field to suit requirements. 11. A prerequisite for all calendars is to setup the Gregorian calendar, to do this click on the Tasks tab and locate SIL_DayDimension 12. Select the Parameters tab in the lower pane. 13. Change the date in the Value field as required for both $$END_DATE and $$START_DATE 14. To configure the Enterprise calendar navigate to Design -> Source System Parameters. 15. Change the Value for $$GBL_CALENDAR_ID to the result in the GL_PERIOD_SETS.PERIOD_SET_NAME GL_PERIOD_TYPES.PERIOD_TYPE in the format Period Set Name~Period Type i.e. Accounting13~21 16. Change the Value for $$GBL_DATASOURCE_NUM_ID by entering the appropriate values from the Configuration Guide for Informatica PowerCenter Users i.e. 27 17. Two workflows (SDE_ORA_Stage_Reverse_ARTransactionFact_DiffManDerive and

SDE_ORA_Stage_Reverse_GLRevenueFact_DiffManDerive) will fail in the vanilla

install of BI Apps if a connection pool is not created in Informatica with the name PARAM_OLTP_ORA11I

Configuration for Procurement and Spend.

1. To implement Spend Classification (an additional license that complements Procurement and Spend, open up the OBIEE repository and copy from the presentation layer under the subject area Procurement and Spend Invoice Lines the following:a. Data Classification b. Auto UNSPSC c. Auto Purchasing Category d. Auto Custom Category 1 2. Copy the above presentation tables into the following subject areas:a. Procurement and Spend Purchase Orders

b. Procurement and Spend Purchase Requisitions 3. Save and check in the repository 4. Within the DAC click on the Design button 5. Click on the Tasks tab and query for SIL_PurchaseCycleLinesFact 6. In the lower pane click on the Parameters tab and for the $$ORA_DATASOURCE_NUM_ID_LIST enter the appropriate value(s) i.e. 27 7. Return to the Tasks tab and query for SIL_PurchaseCycleLinesFact_Extract 8. In the lower pane click on the Parameters tab and for the $$ORA_DATASOURCE_NUM_ID_LIST enter the appropriate value(s) i.e. 27 9. Locate the file file_ap_invoice_config_spend_ora12.csv in the directory infa_shared/LkpFiles/LkpFiles and make the required changes to reflect the Invoice Types values stored in EBS. (Section 4.2.2.3 in the Configuration Guide)

Customisation
1. Login to the Informatica Repository Manager and connect to the repository 2. Click on the Folder menu item and click Create 3. Create your custom folder i.e. Custom_SDE_ORA1212_Adaptor 4. Login to the Informatica Designer and connect to the repository 5. Right click on your new folder and click Open this should highlight the folder in bold. 6. Navigate to the vanilla folder that contains the mapping that you wish to modify 7. Locate the relevant mapping and right click on it and select Export Objects 8. Save the Metadata file out to disk. 9. Ensuring that your custom folder is still open (in bold) select the Repository menu item. 10. Select Import Objects from the resulting dropdown. 11. Locate the relevant Metadata file and work your way through the popup wizard. 12. Click on the Repository menu item and select Save 13. Login to the Informatica Workflow Manager and connect to the repository. 14. Right click on your new folder and click Open this should highlight the folder in bold. 15. Navigate to the vanilla folder that contains the workflow that you wish to modify. 16. Locate the relevant workflow and right click on it and select Export Objects 17. Save the Metadata file out to disk. 18. Ensuring that your custom folder is still open (in bold) select the Repository menu item. 19. Select Import Objects from the resulting dropdown. 20. Locate the relevant Metadata file and work your way through the popup wizard. 21. Click on the Repository menu item and select Save 22. Open the Data Warehouse Administration Console (DAC) client. 23. In your custom Source System Container click on the Tools menu item. 24. From the dropdown select Seed Data 25. From that resulting dropdown select Task Physical Folders 26. From the resulting pop-up click on the New menu item and enter the name of your custom folder exactly as displayed in Informatica. 27. Click on the Save menu item 28. Click on Close

29. In your custom Source System Container click on the Tools menu item. 30. From the dropdown select Seed Data 31. From that resulting dropdown select Task Logical Folders 32. From the resulting pop-up click on the New menu item and enter a logical name for your custom folder exactly. 33. Click on the Save menu item 34. Click on Close 35. In your custom Source System Container click on the Source System Folders tab. 36. Click on the New menu item. 37. Select your new logical folder into the Logical Folder column and associate your new physical folder into the Physical Folder column. 38. Click on the Save button. 39. In your custom Source System Container click on the Tasks tab. 40. Select a task and you should now be able to select the new logical folder from the Folder Name dropdown. 41. Right click on the updated task and from the resulting menu items select Synchronise Tasks 42. In your custom Source System Container click on the Subject Areas tab. 43. Click on the Assemble menu item follow the prompts and wait for it to complete. a. Im not sure if this needs to be done if you update a small detail for an existing Task 44. Click on the Execute menu item 45. Select your relevant Execution Plan from the Execution Plans tab. 46. Click on the Parameters sub-tab and click on the Generate menu item.

Configure Currencies for OBIEE Display

1. Navigate to OracleBI\Web\Config and locate the file Currencies.XML 2. Open in Notepad having backed up the file first. 3. Log into OBIEE and locate a report that displays a currency value within a table. 4. Navigate to the underlying Answers report and click on the Advanced tab.

Configure Relational Connections in Informatica

The DAC ETL process will fail unless three Relational Connections have been setup within the Informatica environment. 1. Open Informatica Workflow Manager and click on the Create / Edit Relational Connection button. 2. Click on the New button from the resulting pop-up 3. Enter the Name as PARAM_OLTP_ORA11I This needs to be done because of a known Oracle bug which will cause the ETL to fail without this connection. The remaining details for this entry should reflect the setup for the OLTP database. 4. Create an OLTP connection that matches the OLTP connection name within the DAC 5. Create an OLAP connection that matches the OLAP connection name within the DAC

General Configuration if the Projects Module is Available

1. Log into the Data Administration Console (DAC) 2. Ensure that you have your custom Container selected within the Design view. 3. Select Subject Areas 4. Select Configuration Tags from the lower sub-menu pane. 5. For each relevant subject area clear the Inactive flag from the Enable Project Dimensions tag. a. Financials Revenue b. Financials Receivables c. Financials Payables d. Financials Cost of Goods Sold 6. Save the record and Assemble the subject area. 7. Project Templates cannot be used for Billing, Costing, or Revenue.All analysis in pre-built reports is based on Project Operating Unit, which is the operating unit of a project. To allow templates to be brought through the following filter needs to be removed :a. PA_PROJECTS_ALL.TEMPLATE_FLAG = N

General Configuration If the Financials Module Is Available

Navigate to the Design view within the DAC client Click on the Source System Parameters tab. Query for the entry $$FILTER_BY_LEDGER_ID In the Value field enter Y (the single quotes are important) and save. Query for the entry $$LEDGER_ID_LIST In the Value field enter the EBS Ids of the relevant Ledgers. Navigate to the Execute view within the DAC client. Select the relevant Execution Plan and select the Subject Areas sub tab. Remove from the list of Subject Areas the 'Financials - Group Account Number Clean Up' entry. This entry if left will cause the DAC to fail. This Subject Area is only run on special 'one-off' occasions when customers have made a mistake with a Group Account and have a mismatch of data in their Data Warehouse. Ensure that for an initial load the following files are configured, they are located in the SrcFiles directory within the Informatica. o o o file_group_acct_names.csv file_group_acct_codes_ora.csv file_grpact_fstmt.csv

If new Group Account Numbers are added to the above files then the values will also need to be exposed within the OBIEE repository. To set up hierarchies with FSG Report Definition configure the file file_gl_hierarchy_assignment_ora.csv to specify the hierarchies you want to reference for each CHART_OF_ACCOUNTS (Page 73 of the setup document)

Navigate to the Informatica SrcFiles directory. Open the file file_gl_hierarchy_assignment_ora.csv Specify the segments you want to analyze.

In the DAC, do the following go to the Design view, and select your custom container from the drop-down list. Display the Subject Areas tab, and query for 'Financials General Ledger'. In the Configuration Tags subtab, do the following: o o Query for the tag 'Oracle Extract FSG Hierarchies', and make sure that the Inactive check box is not selected. Query for the tag 'Oracle Extract Value Set Hierarchies', and make sure that the Inactive check box is selected.

Execution Plan
Navigate to the Execute view. Click on the New button and enter a name for the execution plan. Click on the Subject Areas sub-tab and add in the required entries. Click on the Parameters sub-tab and click on Generate o Once this has completed you will find a number of entries have been added, ensure that the Value field for each entry is correct. Select the appropriate value from the drop-down selection.

Troubleshooting
If you have problems with unique index keys when using FSG hierarchies, then you may well need to add a truncate table action to the SDE_ORA_GLAccountDimension_HierarchyDerive task. This is described in the Oracle support document 967547.1 With Financials you need to configure the file_gl_hierarchy_assignment_ora.csv file with the AXIS_SET_ID and the Chart of Accounts ID. Both of these can be found by querying RG_REPORT_AXIS_SETS for the relevant AXIS_SET_ID and STRUCTURE_ID.

To work out the reasons why W_HIERARCHY_DS is empty run through the following steps.
o o o

This appears to because W_ORA_GL_HIER_DERIVE_DH_TMP is also empty. This is because W_ORA_GL_HIER_RPT_CALC_DH_TMP is empty. W_ORA_GL_HIER_RPT_CALC_DH_TMP is loaded from a query on RG_REPORT_CALCULATIONS and RG_REPORT_AXIS_SETS in mapping: SDE_ORA_Stage_GLHierarchy_Extract

o o

The records are looked up against W_ORA_GL_HIER_FSG_ASGN_DH_TMP W_ORA_GL_HIER_FSG_ASGN_DH_TMP holds the contents of the config file which has a chart_of_accounts_id

There is an issue with the mapping SDE_ORA_APInvoiceDistributionFact_Full whereby the out of the box mapping points to the SrcFiles directory but the relevant file is held in the LkpFiles directory. To correct this do the following :o o Open the SDE_ORA_APInvoiceDistributionFact_Full in workflow manager. Select the Mapping Tab

o o

Under the Transformations heading select mplt_SA_ORA_APInvoiceDistributionFact.LKP_CONFIG_SPEND_FILE In the associate Properties view on the right change the attribute Lookup source file directory to point at $PMSourceFileDir\