Setting Up FTI KPI Targets

[samuellevin_mavenwire]

All
We are doing some testing in OTM on FTI and I am trying to get my targets to show up. I have gone into Power Data and Setup my KPI Target Value Stage which I would think would then show up. I also created my own Adhoc Query which would display my targets and nothing shows up. Is there anything more that needs to be configured to get the KPO Target to display? Unfortunetly help does not help in this regard. I apprecaite any help you can give!

[cool_brat]

Re: Setting Up FTI KPI Targets

Hello Sam,

I have not checked any adhoc query option but for standard target values if set in power data at target value stage should reflect in dash board, However for certain targets like % On time pickup / Delivery these values are not reflecting. I had raised an SR on these values and got the confirmation as a bug for these two targets.

And the target will reflect after the Data is transferred from OTM To ROD to HD-Database so check your job scheduling with sysadmin and see if targets reflect after the scheduling job is completed.


Regards
Vipin

[kkchopra]

Re: Setting Up FTI KPI Targets

Hi All,

Can you guys share some docs on creating new KPIs in the FTI ?

[jdavis425]

Re: Setting Up FTI KPI Targets

This is what you do:

Adding Custom Key Performance Indicators (KPIs)
To add new KPIs to the Fusion Transportation Intelligence solution follow the steps below:
KPI Definition in Oracle Transportation Management
1. Use the KPI page (available via Transportation Intelligence > Power Data > Transportation Intelligent > KPI) to create your new KPI definition.
2. Now, use the KPI Target Value Type page (available via Transportation Intelligence > Power Data > Transportation Intelligence > KPI Target Value Type) to define the target value for your new KPI.
Extending ETL for KPI Load Logic
1. Log into the HDOWNER schema of the historical database.
2. Modify the load_KPI_Targets.pkg package available here to extend the ETL load logic for the new KPI.
3. Compile the package.
Extending Fusion Transportation Intelligence Metadata
1. Stop the OBI EE services and edit the advanced_analytics.rpd metadata file.
2. Extend the Targets folder in the logical layer of the Fusion Transportation Intelligence metadata to add the new KPI column and provide the appropriate the logical level mappings for the new KPI.
3. Extend the Presentation layer to add the new KPI column to the relevant folders.
4. Verify your metadata changes for errors.
5. Restart the OBI EE services to now host the modified Fusion Transportation Intelligence metadata.
Extending Dashboard Reports
1. Finally, extend the relevant dashboard report(s) to include the new KPI column.
2. Refresh the Webfolders in OBI EE.
3. Run the ETL to load the new KPI data.
4. Log into Fusion Transportation Intelligence to view your reports with the new KPI data.
Creating Custom Business Intelligence Roles
You can create your own business intelligence (BI) roles in addition to the standard roles that ship with FTI.
Note: You cannot change the pre-defined business intelligence roles that ship with Fusion Transportation Intelligence or are used by Fusion Transportation Intelligence. Any changes to these existing roles are not supported. The ability to create new BI roles or editing existing BI roles has been removed from the Oracle Transportation Management user interface in version 6.3 and later.
In order to create your own custom BI Roles, you must add the roles to Oracle Transportation Management via CSV files as detailed below:
1. Add your customized BI roles to the BI_ROLE.csv file.
2. Login to Oracle Transportation Management as DBA.ADMIN.
3. Go to Business Process Automation > Integration > Integration Manager.
4. Click Upload an XML/CSV Transmission.
5. Click Browse next to the ‘What XML/CSV file do you want to upload?’ field and select the BI_ROLE.csv file that you want to upload.
6. After selecting the file, click on Upload. The Launch Integration page appears.
7. In the Command list, select the transaction code as i.
8. The Data Directory field defaults to a temporary folder on the server where your CSV file is uploaded to prior to updating the database. You should leave this field as is.
9. The Data File Name field contains the name of the file that you recently selected to upload in the Upload XML/CSV Transmission page. Unless you selected the wrong file name during that step, you should leave this field as is. Since BI_ROLE.csv is the file selected this field should contain the name as BI_ROLE.csv.
10. The Run SQL Loader field is a drop-down list containing two values. One value is - runsqlloader, the second is the option to leave this field blank. The default value is to leave this field blank, and it should be left as is.
11. The XValidate drop-down list allows you to turn on or off verbose diagnostic messaging. To leave messaging on, the value in the drop-down list should be Y, which is the default. To turn it off, select N.
12. In the Encoding list, select the appropriate encoding type for your CSV file. If your file contains standard ASCII characters, then it can be encoded as ISO-8859-1. If it contains non-standard, international characters, then it should be encoded as UTF-8.
13. Click on Run. The new BI_ROLE.csv file gets processed. The new roles will now be available under Business Intelligence Roles.
14. Create identical application roles in WebLogic. The process listed above only creates the roles on the FTI side. You need an identical application role in WebLogic. Refer to the following documentation to create new application roles in OBIEE: “Oracle® Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) chapter 2 Managing Security Using the Default Security Configuration > 2.4 Managing Application Roles and Application Policies Using Fusion Middleware Control > 2.4.2 Creating Application Roles Using Fusion Middleware Control > 2.4.2.2 Creating an Application Role”.
For more details on using the Upload an XML/CSV Transmission page, refer to the Oracle Transportation Management online help.