OTM Reports FTI Training Manual

OTM Reports & FTI Training Manual
Oracle Transportation Management
OTM BI Reports & FTI Training
OTM Technical
About this training manual:

This workbook is for participants of OTM training. This workbook guides you through a number of scenarios related to
the technical configurations. Each topic has lessons where you will learn all the necessary steps and get the
navigation to go to the respective element. Complete the exercise given in this module to get trained for the role of an
OTM Technical Consultant.
1|Page
Table of Contents
Chapter – 1......................................................................................................................................................................4
Understanding OTM Data Dictionary ..........................................................................................................................4
What is OTM data model? ....................................................................................................................................4
Navigation Steps: ...................................................................................................................................................4
Exercise: ..................................................................................................................................................................4
Chapter – 2......................................................................................................................................................................5
Overview of OTM BI Publisher Reports ......................................................................................................................5
What is Report? ......................................................................................................................................................5
Chapter – 3......................................................................................................................................................................8
Components of OTM Reports ......................................................................................................................................8
Query Template ......................................................................................................................................................8
Format Template ....................................................................................................................................................9
Database Package .............................................................................................................................................. 10
Chapter – 4................................................................................................................................................................... 11
Creating Report in OTM ............................................................................................................................................. 11
Creating Report with single parameter ............................................................................................................ 11
Creating Report with Multiple parameters ....................................................................................................... 15
Exercise: ............................................................................................................................................................... 20
Chapter – 5................................................................................................................................................................... 21
Generating Report in OTM......................................................................................................................................... 21
Chapter – 6................................................................................................................................................................... 23
Scheduling Report in OTM......................................................................................................................................... 23
Chapter – 7................................................................................................................................................................... 25
Overview of Fusion Transportation Intelligence (FTI)............................................................................................ 25
Fusion Transportation Intelligence (FTI) .......................................................................................................... 25
Fusion Transportation Intelligence Architecture ............................................................................................. 30
Exercise: ............................................................................................................................................................... 31
Chapter – 8................................................................................................................................................................... 32
Dashboard Configuration ........................................................................................................................................... 32
Configuring Dashboards: ................................................................................................................................... 32
Exercise: ............................................................................................................................................................... 41
2|Page
Chapter – 9................................................................................................................................................................... 43
IBOTs ............................................................................................................................................................................ 43
Overview ............................................................................................................................................................... 43
Configuring an IBOT ........................................................................................................................................... 43
Exercise: ............................................................................................................................................................... 49
Chapter – 10 ................................................................................................................................................................ 50
Facts and Dimensions table ...................................................................................................................................... 50
Dimension Table.................................................................................................................................................. 50
Fact Table ............................................................................................................................................................. 50
Understanding Existing Schema (HDOWNER) .............................................................................................. 50
Exercise: ............................................................................................................................................................... 51
Chapter – 11 ................................................................................................................................................................ 52
Overview of ODI tool and use of ODI in FTI............................................................................................................ 52
Oracle Data Integrator (ODI) ............................................................................................................................. 52
ODI Interfaces for FTI ......................................................................................................................................... 55
Exercise: ............................................................................................................................................................... 63
Chapter – 12 ................................................................................................................................................................ 64
Overview of OBIEE tool and using OBIEE in FTI ................................................................................................... 64
Oracle Business Intelligence Enterprise Edition (OBIEE) ............................................................................. 64
OBIEE Repository (RPD) ................................................................................................................................... 66
Exercise: ............................................................................................................................................................... 78
3|Page
Chapter – 1
Understanding OTM Data Dictionary
In this lesson, you will learn how to:

 Access the OTM data dictionary
 Navigate the data dictionary
What is OTM data model?
1. OTM data model is basically the data dictionary.

2. It tells how data is stored in the database.
3. It shows the hierarchy and flow of the data in the OTM tables, their primary key and
foreign key relations.
Navigation Steps:
1. The OTM data dictionary can be access by using the url in the browser.
2. URL: https://otm62.kpitcummins.com:8443/GC3/html/data_dict/index.html
Exercise:
1. Find out the relation between shipment and invoice & shipment and bill table.
2. Find 2 ways to relate the order release with shipment.
4|Page
Chapter – 2
Overview of OTM BI Publisher Reports
This Chapter describes how to design and generate reports for Oracle Transportation Management. It is intended for
Report designers and integrators who need to develop reports based on OTM data.
What is Report?
• Reports provide useful information for effective decision-making in the logistics process. They can help
you manage and measure logistics supplier’s performance. Analytical allow you to view detailed analysis
of business processes by various categories to help identify problems, patterns, and areas for
improvement.
• Reporting functionality spans all of OTM, complimenting Shipment Management and Financials.
Reporting consists of a series of pre-defined documents available to generate, view, and print. You can
also schedule reports to run in batch mode and receive them via email messages. The system includes
standard shipping forms as well as performance, capacity, and miscellaneous reports among others.
• Many pre-defined forms and reports are available for use in the Report Manager and other Managers (for
example, Shipment Manager and Payment Invoice Manager). However, you will probably want to create
custom user-defined reports to retrieve and present additional information.
• A user-defined report is any new report, or modified pre-defined report, that is created with an outside
reporting tool and then integrated into the database.
OTM supports two methodologies to generate reports:
External
 Report requests are sent via HTTP to an external report server. The report server may begin an
interactive session with you or simply return report content.
Embedded
 Report requests are routed to an OTM application server. The server uses Oracle’s Business Intelligence
Publisher (BI Publisher) libraries to generate report content.
5|Page
BI Publisher
OTM is tightly integrated with BI Publisher to deliver high quality, multiple format output, translation compliant,
and easily customizable reports which span the entire application. The advantages of BI Publisher include the
reduced cost of report maintenance, a consistent user interface, the ability to generate reports in multiple
output formats, and the ability to use already familiar tools to develop report layouts. BI Publisher enables the
separation of the report data from the report design layout, as well as, report translations. It provides flexibility
in the creation, modification, and maintenance of reports.
Data Generation
6|Page
At its core, BI Publisher takes an XML representation of data and transforms it against a template of the
report layout. The XML can be generated by:
 A SQL Template. BI Publisher executes the SQL statement against a given data source and generates
XML elements for each selected column. Nested elements can be added via cursors. Report parameters
are specified with named bind variables. The use of SQL has the advantage of simplicity, but may restrict
data needed for layout design.
 A Data Template. A data template is a standardized XML document which defines the information needed
to generate data content for the report. It includes a list of report parameters, SQL statements to retrieve
content based on those parameters, and a mapping of resulting SQL columns to XML elements. Creating
a data template requires understanding of the BI Publisher Data Template schema, but provides greater
flexibility by mapping dependent and independent relational data to XML.
 An external XML generator. When using embedded generation, BI Publisher can accept an external XML
for data transformation. This approach minimizes data design but may complicate report layout.
Specifying individual fields within the report can require complex XPath expressions.
Other data models can be used with BI Publisher, but these are not supported by embedded generation.
Transformation
BI Publisher includes a transformation engine that applies XML data against a report layout. The layout
defines the visual structure of the report, including markup tags to populate the report XML from data
generation.
 Placeholders for XML data. For simple XML schemas, the placeholder can simply be the element name.
Complex schemas may require XPath expressions to navigate to the correct data.
 Grouping definitions. Tabular data can be inserted into reports using special markup tags to define the
repeating XML element. Columns are then defined with placeholders relative to the parent element.
 Layout-specific commands.
The output of the transformation engine is a report document. Depending on the layout type, the report user
can select the report format.
7|Page
Chapter – 3
Components of OTM Reports
 There are 3 components of the report:

o Query Template
o Format Template
o Database Package
Query Template
• A query template defines the data that will populate a report. It generates XML data that BI Publisher
uses to transform layout via a format template. Depending on the type of query template, it contains a
SQL query or XML to gather information for generating a report or a document.
Types of query templates:
SQL Template
A SQL template is a single SQL query returning data needed by a report. BI Publisher automatically maps the
result of the XML, based on your column and cursor aliases.
Data Template
A data template is a BI Publisher XML schema that allows multiple queries and processing. It specifies
parameters and queries needed by the report, as well as a mapping of result set data to its XML
representation.
 Parameter specification. Parameters can be typed and explicitly listed
 Data querying. Multiple SQL statements can be specified, allowing independent queries to populate a
report.
 Data mapping. The results of each SQL statement can be combined, nested, or flattened to simplify
the resulting XML, and resulting field specification in the report layout.
There are three primary components of a data template:
 A list of parameters under a <parameters> element. Each parameter is named and typed.
 A list of SQL data queries under a <dataQuery> element. Each SQL query is entered in a
<sqlStatement> element with a distinct name and a valid SQL query embedded in a CDATA section.
Note that parameters are available as named bind variables for each query.
 A tree of XML groups under a <dataStructure> element. Each <group> element defines a list of XML
elements for a particular result set. Each element maps a result set column name or alias to an XML
element name.
Attach is the example for the data template
8|Page
SAMPLE_REPORT.xm
l
Integration Template
 Integration templates are only used for transactional reports that come from integration XML. When
defining this type of template, you do not need to specify a BI Publisher data template in the Upload
field.
Creating Query Template in OTM
Navigation: Go to Business Process Automation > Power Data > Document Generation > Query Template
Click NEW button then open window for creating Query template.
Section - 1: Query Template
1. Enter a Query Template.

2. Select a Domain.
3. Enter a Description.
4. Select a Data Query Type. The data query type is used when creating the integration template type of query
template. It is not used if you are uploading SQL or XML files.
5. Click Upload and browse to select a SQL query or a BI Publisher data template XML file.
Section - 2: XML Information
1. Use this section when defining an integration template type of query template that does not use an uploaded
XML data template or SQL query. Specifying an OUT XML Profile will limit the data that is returned.
2. Enter an Out XML Profile. This profile allows you to filter what Oracle Transportation Management integration
XML is sent to BI Publisher.
3. Click the Generate Sample XML button to generate and export a sample XML file based on the query template
definition.
4. Click Finished.
Format Template
 A format template defines the layout used by BI Publisher to transform data.
Creating Format Template in OTM
Navigation: Go to Business Process Automation > Power Data > Document Generation > Format
Template
click NEW button then open window for creating format template.
Section - 1: Format Template
 Enter a name for the Format Template.

 Select a Domain.
 Enter a Description.
 Select the XSL-FO Template check box if the XML is to be transformed by BI Publisher. Otherwise it is
transformed by XSLT.
 Click Upload and browse to select an RTF, XSL, XSL-FO, eText, or PDF file containing the layout.
Section - 2: Template Details (Optional)
 Select a Data Query Type.
9|Page
 Select the eText Template check box to indicate whether the RTF template is a eText template or ordinary RTF
template. An eText template is an RTF-based template that is used to generate text output for Electronic Funds
Transfer (EFT) and Electronic Data Interchange (EDI). At runtime, XML Publisher applies this template to an
input XML data file to create an output text file that can be transmitted to a bank or other customer. The output
(eText file) is intended only for electronic communication.
 Select the Configure PDF check box if your intended output is a PDF. The PDF sections of the page appear. If
you check the Configure PDF check box then below two sections will open.
o PDF Watermark Configuration
 Select Text or Image from the Use Watermark option buttons.
 If you select a watermark type of Text:
 Enter the Watermark Text. This text will appear in the background of the PDF as a watermark.
Multi-byte characters are not supported for watermark text.
 Select the Font for the watermark text.
 Enter the Font Size in points.
 Enter the Angle at which the text should be tilted.
 Enter the RGB Red, RGB Green, and RGB Blue values to color the text of the watermark.
 Enter the X and Y Coordinates, in pixels, to control where on the page the watermark will
appear.
 If you select a watermark type of Image:
 Enter the X and Y Coordinates for where the image should be placed on the page.
 Click Upload and browse to find the watermark image file.
o PDF Page Configuration
 Enter the page number with which the PDF should start in the Page Number Value Start field.
 Select the Font for the page number.
 Enter the Font Size, in points, for the page number.
 Enter the X and Y Coordinates, in pixels, to control where on the page the page number will
appear.
o Translation Template (Optional)
 Enter a Translation Template.

 Click Save for each translation template you enter.
 Click Finished.
Database Package
 Database Package transforms the input parameters into the sql understandable form and BI publisher attached
those input parameter to where condition of queries defined in query template document.
10 | P a g e
Chapter – 4
Creating Report in OTM
Creating Report with single parameter
If you want to generate a simple report of shipments whose transport mode that you specify. The report
should include SHIPMENT GID, ORDER RELEASE GID, TRANSPORT MODE, SOURCE LOCATION XID
and DESTINATION LOCATION XID.
The basic steps to create an embedded analytical report are:
• create Database Package

• Generate a data model. For this report, we will use a Data Template.
• Create a Query Template record within the system and upload the data model to it.
• Export sample XML data for layout design.
• Design a layout using the XML fields. For this report, you will define an RTF layout using the BI Publisher
Template Builder.
• Create a Format Template record within the system and upload the layout to it.
• Create a Report record within the system, mapping the query template from #2 and the format template
from #5. You will also specify any custom parameters needed by the report and select a Report Manager
UI to hold the report links.
Step 1: Create Database Package and execute in REPORTOWNER schema
We are using standard pre-defined structured database package to manipulate input parameter into
SQL query understandable condition to query the data from glogowner. At the run time, BI publisher will
attach that condition to query.
 Define three variables in the database package specification
 P_L_TRANSPORT_MODE VARCHAR2 (32766) for input parameter
 P_L_TRANSPORT_MODE_WHERE VARCHAR2 (32766) for getting where condition

in db query
 P_H_TRANSPORT_MODE VARCHAR2 (32766) for displaying input parameter in
format template.
 Modify SET_LEXICAL_PARAMETERS procedure in the package with defined input

parameters.
Step 2: Create a Data Template
 Define input parameters in the parameter section of xml data template.
11 | P a g e
<parameters>
<parameter name="P_GL_USER" dataType="character" defaultValue="DBA.ADMIN" />
<parameter name="P_ROLE_ID" dataType="character" defaultValue="ADMIN" />
<parameter name="P_L_TRANSPORT_MODE" dataType="character" defaultValue="1=1" />
</parameters>
 P_GL_USER and P_ROLE_ID are prefined parameters and P_L_TRANSPORT_MODE is

custom parameter.
 Define query for getting data from glogowner in the dataQuery section.
<dataQuery>
<sqlStatement name="Q_1">
<![CDATA[ SELECT OR1.ORDER_RELEASE_GID AS ORDER_ID ,
S.SHIPMENT_GID AS SHIPMENT_ID ,
S.transport_mode_gid AS TRANSPORT_MODE,
OR1.SOURCE_LOCATION_GID AS SOURCE_LOCATION,
OR1.DEST_LOCATION_GID AS DEST_LOCATION
FROM ORDER_RELEASE OR1, VIEW_SHIPMENT_ORDER_RELEASE V,SHIPMENT S
WHERE OR1.ORDER_RELEASE_GID = V.ORDER_RELEASE_GID
AND S.SHIPMENT_GID = V.SHIPMENT_GID
AND S.PERSPECTIVE = 'B'
AND &P_L_TRANSPORT_MODE_WHERE
]]>
</sqlStatement>
</dataQuery>
 Define xml tags to store data in dataStructure
<dataStructure>
<element name="P_L_TRANSPORT_MODE_WHERE" dataType="varchar2"
value="SAMPLE_BI_REPORT.P_L_TRANSPORT_MODE_WHERE" />
<element name="P_H_TRANSPORT_MODE" dataType="varchar2"
value="SAMPLE_BI_REPORT.P_H_TRANSPORT_MODE" />
<group name="G_1" dataType="varchar2" source="Q_1">
<element name="ORDER_ID" dataType="varchar2" value="ORDER_ID"/>
<element name="SHIPMENT_ID" dataType="varchar2" value="SHIPMENT_ID" />
<element name="TRANSPORT_MODE" dataType="varchar2" value="TRANSPORT_MODE" />
<element name="SOURCE_LOCATION" dataType="varchar2" value="SOURCE_LOCATION" />
<element name="DEST_LOCATION" dataType="varchar2" value="DEST_LOCATION" />
</group>
</dataStructure>
 Attach is the sample xml data template.
SAMPLE_BI_REPORT
.xml
Step 3: Create a Query Template
 Log into Oracle Transportation Management and navigate to Business Process Automation >
Power Data > Document Generation > Query Template. Create a new query template and
upload the sql file.
 Select Finished to save the query template.
Step 4: Export Sample XML for Layout Design
12 | P a g e
 Reopen the query template and select Generate Sample XML and click Submit.
 Save the document to a drive accessible by the BI Publisher Template Builder.
Step 5: Design a Layout
 Open up Microsoft Word and Add-Ins tab

 Select Data > Load XML Data from the BI Publisher Template Builder menu and select the
XML file saved in previous Step 4 above. This associates the sample XML which is implicitly
defining an XML schema for the layout.
 Use Insert > Field and Insert > Table Wizard to add ad-hoc and tabular data to the layout.
 Use Preview to test the modified layout with the sample XML.
 Save the modified layout as a Rich Text Format document to a drive accessible by your local
browser.
 Attach is the sample rtf template.
13 | P a g e
SAMPLE_REPORT.rtf
Step 6: Create a Format Template
 Return to OTM and navigate to Business Process Automation > Power Data > Document
Generation > Format Template. Create a new format template and either:
 Upload the RTF file created in step 5
 Select Finished to save the format template.
Step 7: Create a Report
 Navigate to Business Process Automation > Power Data > Document Generation > Reports.
Create a new report as follows:
 Set Report ID to SAMPLE_REPORT_WITH_SINGLE_PARAMETER
 Set Report Display Name to Sample Report with Single Parameter.
 Set Report Description to Sample Report with Single Parameter.
 Set Report Type to SHIPMENT. The report should be available on the Reports menu under
Shipment Management.
 Select the Report Manager Display check box. The report should be available under
Business Process Automation > Reporting > Report Manager.
 Uncheck Use Report Parameters as Bind Values check box.
 Uncheck Run On Third Party Report Server check box.
 Uncheck Run Can Auto Generate check box.
 Select the Select Via UI check box.
 Set Report Group ID to the related report group or create new report if required.
 Set the Query Template to SAMPLE_REPORT_WITH_SINGLE_PARAMETER_QT.
 Set the Format Template to SAMPLE_REPORT_WITH_SINGLE_PARAMETER_FT.
 Add input parameters in the Report Parameters Section: P_L_TRANSPORT_MODE.
The resulting report in the Report Manager is shown below:
14 | P a g e
 Select Finished to save the report.
Creating Report with Multiple parameters
 If you want to generate a report with multiple input parameters of shipments whose transport mode, weight
utilization, shipment insert date and shipment refnum value those you specify. The report should include
SHIPMENT GID, ORDER RELEASE GID, TRANSPORT MODE, SHIPMENT COST, STARTTIME, WEIGHT
UTILIZATION, ORDER TYPE, SHIPMENT REFNUM VALUE, SOURCE LOCATION XID and DESTINATION
LOCATION XID.
 The basic steps to create an embedded analytical report are:
• create Database Package

• Generate a data model. For this report, we will use a Data Template.
• Create a Query Template record within the system and upload the data model to it.
• Export sample XML data for layout design.
• Design a layout using the XML fields. For this report, you will define an RTF layout using the BI Publisher
Template Builder.
• Create a Format Template record within the system and upload the layout to it.
• Create a Report record within the system, mapping the query template from #2 and the format template
from #5. You will also specify any custom parameters needed by the report and select a Report Manager
UI to hold the report links.
Step 1: Create Database Package and execute in REPORTOWNER schema
 We are using standard pre-defined structured database package to manipulate input parameter into SQL
query understandable condition to query the data from glogowner. At the run time, BI publisher will attach
that condition to query.
15 | P a g e
 Define below variables in the database package specification
 P_L_TRANSPORT_MODE VARCHAR2 (32766) for input parameter
 P_L_TRANSPORT_MODE_WHERE VARCHAR2 (32766) for getting where condition in db query
 P_H_TRANSPORT_MODE VARCHAR2 (32766) for displaying input parameter in format template.
 P_L_WT_UTIL VARCHAR2(32766) for input parameter
 P_L_WT_UTIL_WHERE VARCHAR2(32766) for getting where condition in db query
 P_H_WT_UTIL VARCHAR2(32766) for displaying input parameter in format template
 P_L_SHIPMENT_DATE VARCHAR2(32766) for input parameter
 P_L_SHIPMENT_DATE_WHERE VARCHAR2(32766) for getting where condition in db query
 P_H_SHIPMENT_DATE VARCHAR2(32766) for displaying input parameter in format template
 P_L_SHIPMENT_REF_VALUE VARCHAR2(32766) for input parameter
 P_L_SHIPMENT_REF_VALUE_WHERE VARCHAR2(32766) for getting where condition in db query
 P_H_SHIPMENT_REF_VALUE VARCHAR2(32766) for displaying input parameter in format

template
 Modify SET_LEXICAL_PARAMETERS procedure in the package with defined input parameters.
Step 2: Create a Data Template
 Define input parameters in the parameter section of xml data template.
<parameters>
<parameter name="P_GL_USER" dataType="character" defaultValue="DBA.ADMIN" />
<parameter name="P_ROLE_ID" dataType="character" defaultValue="ADMIN" />
<parameter name="P_L_TRANSPORT_MODE" dataType="character" defaultValue="1=1" />
<parameter name="P_L_WT_UTIL" dataType="character" defaultValue="1=1" />
<parameter name="P_L_SHIPMENT_DATE" dataType="character" defaultValue="1=1" />
<parameter name="P_L_SHIPMENT_REF_VALUE" dataType="character" defaultValue="1=1" />
</parameters>
 P_GL_USER and P_ROLE_ID are pre-fined parameters and P_L_TRANSPORT_MODE is

custom parameter.
 Define query for getting data from glogowner in the dataQuery section.
<dataQuery>
<sqlStatement name="Q_1">
<![CDATA[SELECT OR1.ORDER_RELEASE_GID AS ORDER_ID ,
S.SHIPMENT_GID AS SHIPMENT_ID ,
ROUND(S.total_actual_cost,2) AS SHIPMENT_COST,
16 | P a g e
S.start_time START_TIME,
S.weight_utilization WT_UTILIZATION,
S.transport_mode_gid AS TRANSPORT_MODE,
OR1.order_release_type_gid AS ORDER_TYPE,
S.SOURCE_LOCATION_GID AS SOURCE_LOCATION,
SR.SHIPMENT_REFNUM_VALUE AS SHIPMENT_REFNUM_VALUE
S.DEST_LOCATION_GID AS DEST_LOCATION
FROM ORDER_RELEASE OR1, VIEW_SHIPMENT_ORDER_RELEASE V,SHIPMENT S,
SHIPMENT_REFNUM SR
WHERE OR1.ORDER_RELEASE_GID = V.ORDER_RELEASE_GID
AND S.SHIPMENT_GID = V.SHIPMENT_GID
AND S.SHIPMENT_GID = SR.SHIPMENT_GID
AND SR.SHIPMENT_REFNUM_QUAL_GID = 'BM'
AND S.PERSPECTIVE = 'B'
AND &P_L_TRANSPORT_MODE_WHERE
AND &P_L_WT_UTIL_WHERE
AND &P_L_SHIPMENT_DATE_WHERE
AND &P_L_SHIPMENT_REF_VALUE_WHERE
]]>
</sqlStatement>
</dataQuery>
 Define xml tags to store data in dataStructure
<dataStructure>
<element name="P_L_TRANSPORT_MODE_WHERE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_L_TRANSPORT_MODE_WHERE" />
<element name="P_H_TRANSPORT_MODE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_H_TRANSPORT_MODE" />
<element name="P_L_WT_UTIL_WHERE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_L_WT_UTIL_WHERE" />
<element name="P_H_WT_UTIL" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_H_WT_UTIL" />
<element name="P_L_SHIPMENT_DATE_WHERE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_L_SHIPMENT_DATE_WHERE" />
<element name="P_H_SHIPMENT_DATE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_H_SHIPMENT_DATE" />
<element name="P_L_SHIPMENT_REF_VALUE_WHERE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_L_SHIPMENT_REF_VALUE_WHERE" />
<element name="P_H_SHIPMENT_REF_VALUE" dataType="varchar2"
value="BI_REPORT_WITH_MLT_PARAMETERS.P_H_SHIPMENT_REF_VALUE" />
<group name="G_1" dataType="varchar2" source="Q_1">
<element name="ORDER_ID" dataType="varchar2" value="ORDER_ID"/>
<element name="SHIPMENT_ID" dataType="varchar2" value="SHIPMENT_ID" />
<element name="TRANSPORT_MODE" dataType="varchar2" value="TRANSPORT_MODE" />
<element name="SOURCE_LOCATION" dataType="varchar2" value="SOURCE_LOCATION"/>
<element name="DEST_LOCATION" dataType="varchar2" value="DEST_LOCATION" />
<element name="SHIPMENT_COST" dataType="varchar2" value="SHIPMENT_COST"/>
<element name="START_TIME" dataType="varchar2" value="START_TIME" />
<element name="WT_UTILIZATION" dataType="varchar2" value="WT_UTILIZATION" />
<element name="ORDER_TYPE" dataType="varchar2" value="ORDER_TYPE" />
<element name="SHIPMENT_REFNUM_VALUE" dataType="varchar2"
value="SHIPMENT_REFNUM_VALUE" />
</group>
</dataStructure>
 Attach is the sample xml data template.
BI_REPORT_WITH_
MULTIPLE_PARAMETERS.xml
Step 3: Create a Query Template
17 | P a g e
 Log into Oracle Transportation Management and navigate to Business Process Automation >
Power Data > Document Generation > Query Template. Create a new query template and
upload the sql file.
 Select Finished to save the query template.
Step 4: Export Sample XML for Layout Design
 Reopen the query template and select Generate Sample XML and click Submit.
 Save the document to a drive accessible by the BI Publisher Template Builder.
Step 5: Design a Layout
 Open up Microsoft Word and Add-Ins tab

 Select Data > Load XML Data from the BI Publisher Template Builder menu and select the
XML file saved in previous Step 4 above. This associates the sample XML which is implicitly
defining an XML schema for the layout.
 Use Insert > Field and Insert > Table Wizard to add ad-hoc and tabular data to the layout.
 Use Preview to test the modified layout with the sample XML.
18 | P a g e
 Save the modified layout as a Rich Text Format document to a drive accessible by your local
browser.
 Attach is the sample rtf template.
REPORT_WITH_MUL
TIPLE_PARAMETERS.rtf
Step 6: Create a Format Template
 Return to Oracle Transportation Management and navigate to Business Process Automation

> Power Data > Document Generation > Format Template. Create a new format template
and either:
 Upload the RTF file created in step 5
 Select Finished to save the format template.
Step 7: Create a Report
 Navigate to Business Process Automation > Power Data > Document Generation > Reports.
Create a new report as follows:
 Set Report ID to BI_REPORT_WITH_MULTIPLE_PARAMETERS
 Set Report Display Name to Sample Report with Single Parameter.
 Set Report Description to Sample Report with Single Parameter.
 Set Report Type to SHIPMENT. The report should be available on the Reports menu under
Shipment Management.
 Select the Report Manager Display check box. The report should be available under
Business Process Automation > Reporting > Report Manager.
 Uncheck Use Report Parameters as Bind Values check box.
 Uncheck Run On Third Party Report Server check box.
 Uncheck Run Can Auto Generate check box.
 Select the Select Via UI check box.
 Set Report Group ID to TCTRAINING. In the overall report manager, the report should be
grouped with other shipment reports.
 Set the Query Template to BI_REPORT_WITH_MULTIPLE_PARAMETERS_QT.
 Set the Format Template to BI_REPORT_WITH_MULTIPLE_PARAMETERS_FT.
 Add input parameters in the Report Parameters Section: P_L_TRANSPORT_MODE,
P_L_WT_UTIL, P_L_SHIPMENT_DATE and P_L_SHIPMENT_REF_VALUE
The resulting report in the Report Manager is shown below:
19 | P a g e
 Select Finished to save the report.
Exercise:
1. Create a report in OTM in your domain based on order release. Display the columns Order Release ID,
Source location ID, Weight and volume on the order. The input parameter should be order insert data.
2. Create a report based on the invoice and voucher. Display the columns Invoice ID, Invoice type, Invoice
Number, Invoice date, amount due in invoice, related Voucher ID, amount to pay in voucher, voucher
date and voucher approved by. The input parameter should be Invoice ID, Voucher ID and voucher date.
20 | P a g e
Chapter – 5
Generating Report in OTM
The Report Manager lists all pre-defined and custom reports.
Navigate to Business Process Automation > Reporting > Report Manager.
• Click on Run (Online DB)
Click here
• Specify input parameters, Report format and Delivery Method
• Click Submit then will get below report.
21 | P a g e
22 | P a g e
Chapter – 6
Scheduling Report in OTM
 Navigation: Business Process Automation > Reporting > Report Manager.
• Click on Schedule (Online DB)
Click here
Parameter Section
• Specify input parameters
Email Addresses Section
• Enter Email Addresses for all persons who should receive the report.
• Click Save for each email address you enter.
Printers
• Enter a Printer.
• Enter the Number of Copies.
• Enter the Page Ranges.
• Click Save for each printer you define.
Delivery/Format
• Select a Report Format.

• Select Now if you want to run the report immediately OR
Select Schedule if you want to run the report at a later time.
o If you selected the Schedule option button, specify in the At field when you want the report to
run OR
o If you want to run this report on a recurring basis, enter the frequency of running the report in
the every field.
• Click Schedule to finish scheduling the report.
• Click OK when "The job has been successfully scheduled." page displays.
23 | P a g e
 To view the current scheduled report job requests and the completed report jobs go to Business Process
Automation > Reporting > View Scheduled Jobs or View Completed Jobs.
 The View Scheduled jobs page shows the list of reports that are scheduled. You can select any one of the
schedules and click Finished. A new screen opens where you can change the schedule. Additionally there is
a Delete button if you want to delete the report schedule. Completed jobs screen shows the list of schedule
report requests which are completed.
24 | P a g e
Chapter – 7
Overview of Fusion Transportation Intelligence (FTI)
Fusion Transportation Intelligence (FTI)
 Fusion Transportation Intelligence provides an environment for managing business metrics by monitoring,
analyzing and reporting metrics at various levels of the organization.
 Fusion Transportation Intelligence contains the following components
o Dashboard
 The Dashboard in FTI is a collection of performance metrics reflecting common strategic

goals. There is a default Dashboard or you can customize your own with My Dashboard. In
the default Dashboard, there are multiple tabs organizing the metrics. Dashboard comes pre-
defined with standard metrics or KPIs. You can use My Dashboard to display the metrics you
want in the format you want. Service providers have a different default Dashboard.
 Navigation: Transportation Intelligence > Dashboard.
 This show the default dashboard assigned to the user
 Below Public Dashboards are available in OTM

o Carrier Scorecard Dashboard
o CPG Main Dashboard
o Main Dashboard
o LSP Customer Dashboard
o LSP Host Dashboard
o Servprov Main Dashboard
o System Dashboard
o Tender Dashboard
o Transit Time Variability
 If the Dashboard Preference in User preference is not set then system shows
the Main Dashboard as the default dashboard.
o My Dashboard
 The users can create their own dashboards using this link.
 Navigation: Transportation Intelligence > My Dashboard
o Ad Hoc Query
 Navigation: Transportation Intelligence > Ad Hoc Query.

 This page allows creation of new reports.
o Administration (DBA only)
 Navigation: Transportation Intelligence > Administration.
25 | P a g e
 This Controls administrative functions such as managing sessions.
o Alerts
 Navigation: Transportation Intelligence > Alerts.
 This Allows creation of notification.
 We can determine the priority, recipients, the schedule and conditional requests among other
criteria.
o Data Management (DBA only)

 We can view information related to the data load including the logs, rejects and the KPI load
log.
 Navigation: Transportation Intelligence > Data Management.
 We can view below information with is link
 View FTI Data Load Log: enables us to view the data that uploaded.
 View FTI Data Load Rejects: enables us to view the data that did not get uploaded
 KPI Load Log: shows the KPIs that were uploaded.
o Process Management (DBA only)
 Allows us to manually push data to the HD (historical database) and/or ROD (replicated
operational database).
 Navigation: Transportation Intelligence > Process Management.
 Refresh Replicated Database: updates the ROD (replicated operational database). It

allows us to load the data manually, overriding any nightly job that may be scheduled in
your system. if the Last Refresh Date field is blank, the data has not yet been refreshed
or the ROD is not available.
 Run ETL: runs the ETL from the replicated online database (ROD) or the online
transaction processing (OLTP) database to the historical database (HD).
o Logs
 Integration: record events related to the integration of data, via XML schemas, between
the database and external systems.
 System: is a default log file that records the time, severity, and other data about system
events such as status changes, planning actions, and rate engine actions.
o Recurring Processes
 Use this process to modify the schedule of any process found on the Process Manager
menu. To modify a schedule, a process must have been previously executed.
o Power Data
 Allows us to view and manage setup data for Transportation Intelligence including KPIs and
KPI Target Value Types. Additionally, we can define dashboards.
 Dashboard Preference
 Navigation: Transportation Intelligence > Power Data > Transportation

Intelligence > Dashboard Preference.
26 | P a g e
 We must first create a new dashboard in Fusion Transportation Intelligence

(FTI)/OBIEE. To access that dashboard when clicking the Dashboard link in OTM, we
must come here to link the name of the dashboard to an ID. Then the user
preference points to the OTM ID for that dashboard.
o Enter a Preference ID.
o Enter a Dashboard Type.
o Enter the Dashboard Name.
o Select a Domain or accept the default.
o Click Finished.
 KPI (Key Performance Indicator)
 KPIs are used in Fusion Transportation Intelligence to allow us to enter a target value for
the KPIs that display in FTI. Standard KPIs are already defined in public domain.
 Navigation: Transportation Intelligence > Power Data > Transportation Intelligence >
KPI
 Steps to create New KPI
 Enter a unique KPI ID.

 Select a Domain or accept the default.
 Enter a KPI Target Name. Target Name is used in ETL process while loading the
targets into Historical Database (HD) for each KPI. The Target Name is stored in
the HD representing the KPI in OLTP.
 For an existing KPI, do not change the target name. If we do, we will need to
update the ETL before the KPI can be used.
 For a new, custom KPI, we can enter any target name, but it is best to follow
some standards like we have done for standard KPIs. For example, KPI: Total
Weight; Target Name: TOTAL_WEIGHT_TG. The new KPI cannot be used until
the ETL has been changed.
 Click Finished.
o KPI Target Value Type
o We can view and define key performance indicator (KPI) target value types.
o Navigation: Transportation Intelligence > Power Data > Transportation Intelligence > KPI
Target Value Type
o Steps to create New Target Value Type
27 | P a g e
 Enter a KPI ID.

 Select a Target Type ID.
 Select a Domain Name.
 Enter a Target Value Type.
 Enter a value in the Target Value field. This varies depending on the target value type
selected.
• If you select Fixed, the Target Value will be a text field.
• If you select Moving Average, you will be prompted for Duration In Weeks.
• If you select User Entered, you can specify period, geography, etc. Click the New
Stage button and continue on the KPI Target Value Stage page.
 Select a Perspective. This refers to the shipment perspective as applicable to an LSP
scenario.
 Enter a Service Provider ID.
 Click Finished.
o Transportation Intelligence Roles
o Transportation intelligence roles determine user access for Fusion Transportation Intelligence
(FTI). Roles are then associated with users via the Manage User page. By default, users have no
access, so users must be given rights to access FTI. With below path we can create new
Transportation intelligence roles
o Navigation: Transportation Intelligence > Power Data > Transportation Intelligence >
Transportation Intelligence Roles
o Adding Roles
 Enter a unique Transportation Intelligence Role ID.
 Enter a Domain or accept the default.
 Click Finished.
o If a new Transportation Intelligence Role is added in the system, it also needs to
be added to the Oracle Business Intelligence Enterprise Edition (OBIEE) layer.
The FTI Role provides the functional security. Thus, after adding the new FTI
Role in the OBIEE layer, you should manually add the access that this role has to
Dashboards, Reports and so on.
o Default Roles:
28 | P a g e
o Unload Object from HD

o Navigation: Transportation Intelligence > Power Data >Transportation Intelligence > Unload
Object from HD.
o Use this page to unload (soft delete) data from the Fusion Transportation Intelligence historical
database (HD).
o Steps
 Select an Object Type. These are the types of objects, such as order base or order releases,
that you are unloading.
 Enter an Object ID. The ID is the GID for the object in Oracle Transportation Management.
 Select a Domain Name.
 Click Finished.
 Creating Dashboard for use for other users
1. Create the new dashboard using (DBA Login)

Navigation: Transportation Intelligence -> Administration -> Manage Interactive Dashboards -> Create
Dashboard
2. Create a shared folder to save the reports and prompts for the dashboard using (DBA Login)
Navigation: Transportation Intelligence -> Dashboard -> Administration -> Manage Presentation Catalog
-> Create New Folder
3. Give the Full Control permission to the Developer on this folder.
4. Create Dashboard Preference using Transportation Intelligence -> Power data -> Dashboard Preference
5. Add/modify the value of Dashboard Preference in user preference
6. Attach the user preference to the user/role. Now the new Dashboard will be the default Dashboard for this
user.
7. Open the New Dashboard using Transportation Intelligence -> Dashboard ->Page Options -> Edit
Dashboard
8. Design the Dashboard using

1. Add Pages
2. Add columns
3. Create new sections in the column
4. Add new prompts and reports in the section
5. Save the prompts and the reports in the shared folder.
29 | P a g e
9. Now this dashboard can be attached with any user using the Dashboard Preference user Preference.
Fusion Transportation Intelligence Architecture
o OBIEE is used for development to build reports and/or dashboards within FTI. OBIEE enables OTM
to query, format, and display the information for use in FTI. FTI is the set of rules that govern how
data is moved from OTM to the historical database, defines metrics, and displays the results.
o On the above diagram, OTM with its operational database can be seen to the left. To the right are the
historical database and the OBIEE presentation server. Part of the work FTI performs is to move the
operational OTM data into the historical database which is optimized for read-only queries along with
pre-determined dimensions.
o The process of moving data between the operational database and historical databases is often
referred to as ETL for Extract, Transform, and Load. The HD Schema refers to the way data is
organized in business intelligence applications.
o The data that is available is of two types: facts and dimensions:
 Facts are typically numbers and can be added together. Examples of facts include shipment
weight and number of orders.
30 | P a g e
 Dimensions are often a non-number type of data and allow you to group the facts. Examples of
dimensions include time periods, transport modes, and destination locations.
Exercise:
1. Enter the target value for the KPI - TOTAL WEIGHT with target type – TARGET and target value type -
FIXED.
2. Enter the target value for the KPI - TOTAL CUBE with target type – FORECAST and target value type –
USER ENTERED.
31 | P a g e
Chapter – 8
Dashboard Configuration
Configuring Dashboards:
1. Navigation: Transportation Intelligence > My Dashboard

2. Configuration steps:
a. Add Dashboard Page: Click on the (+) symbol next to Page, which would result in
the below pop up window for adding new dashboard.
b. Add additional Columns: click on the (+) symbol next to the column symbol for
additional columns.
32 | P a g e
c. Add Section: Drag and drop the “Section” on the column and rename it as per the
requirement
d. Create New Common Prompt: Drag and Drop the required “FTI Dashboard Prompt”
on the above section click on “Modify - Properties” in the prompt this would take you
to the next screen.
Click on the save button on the right had top corner, will result in the below pop up window..
33 | P a g e
Now select the folder in which you want to save the prompt for future use, since would not
want to modify the default prompts rename the prompt and save the same in the required
folder, modify the prompt
34 | P a g e
You can constrain the columns on the domain name, like the sql shown below.\
Or else you can create a new prompt by using the following
35 | P a g e
Create a New Report: Similar to creating a prompt, select the common folder “FTI
Dashboard” from which you can access all the existing reports under various sections like
Accessorial Charges,
36 | P a g e
Click on Modify Request, which would take you to the below section, now save the public
report into the required folder before making any changes on the same.
37 | P a g e
The copied report is now ready for making the required changes, follow the steps for
columns and filters as detailed in the write up in the above screen shot.
38 | P a g e
Layout can be modified as required and to share the modified report across login’s the
report should be stored in the Shared Folder only then it would be accessible for other
login’s to use it.
39 | P a g e
To Change the folder names, modify the permissions on the folder you have to go to
Transportation Intelligence -> Alerts and click on “Manage Catalog” and in the pop up
window click on the lock symbol which lands in another pop up window where you can
modify the access rights..
40 | P a g e
Exercise:
1. Create Common Prompts having fields Year, Quarter, Month, Week, Carrier, Transport
Mode, Source Location, Source Province, Source Country, Source Region, Destination
Location, Destination Province, Destination Country and Destination Region as shown
below.
2. Create the Dashboard as shown below:
Example: Output of the “Shipment KPI DASHBOARD”
41 | P a g e
The above output is the result of the below configuration: Go to Dashboard Editor through
Transportation Intelligence -> My Dashboard -> Edit Dashboard
3. Create a new dashboard with your Emp ID for assigning it to some user. Copy the prompt
and some of reports from exercise 2 in this dashboard.
4. Make the dashboard created in exercise 3 as the default dashboard for your user.
42 | P a g e
Chapter – 9
IBOTs
Overview
Fusion Transportation Intelligence ships with an automated report delivery system called Oracle
Delivers. Oracle Delivers contains IBOT’s. Each IBOT can deliver a report to a single user, a
group of users. IBOT’s support sending reports to multiple devices, multiple formats, supports
handheld devices, smart phones or simply an Email.
Configuring an IBOT
1) Navigation: Transportation Intelligence > Alerts. This leads to the Oracle Delivers Home
page
Click here
to get into
Oracle
Delivers
43 | P a g e
Click here
to access Click here
Saved to create a
IBOT’s new IBOT
Click here
to access
Click here to change
saved
Account Settings like
reports
Phone Number or
email address
Oracle Delivers Home Page
2) In order to create an IBOT, Firstly we need to have an account that consists of Email
address, Phone number, Pager information. By Default, if we have sufficient privileges
Oracle Delivers assigns an account. In order to add anything to the account, click on the
Edit my account in the Delivers homepage. This leads to the below screen where we can
save user preferences.
3) After saving the user preferences, click on the Create New IBOT tab.
44 | P a g e
4) The Overview tab gives an overall view of an IBOT like the details of report, what time is it
scheduled, who are the recipients and more. Click on the general tab
Ibot’s are
Priotorized. If
you have
multiple IBOT’s
scheduled at the
same time,
Highest priority
IBOTs will be
sent first.
If you have
sufficient
privileges, you
can create a
IBOT having a
report that is
usually ran by a
different user
5) The Conditional Request tab enables the IBOT to be sent when the report saved through
‘Select condition’ Report returns no records.
45 | P a g e
6) Schedule tab enables to set the time and how many time the report will be sent in the time
frame.
7) As the name suggests, Recipients tab allows us to set the recipients of the reports. User
groups also can be selected if provided sufficient privileges
46 | P a g e
8) Through Delivery Contents tab, we can set the report you want through the IBOT.
9) Destinations tab sets the target destinations of the user selected in the recipients listed.
47 | P a g e
10) Save the IBOT to either My Folder or Shared Folder. The saved IBOT’s can be accessed
through Oracle Delivers home page.
48 | P a g e
11) If the IBOT’s Target Destination is a dashboard, a red flag appears on top of the dashboard
as shown below. Notifies that there is a
report you haven’t
seen
Exercise:
1. Create an ibot for scheduling a report created in dashboard and check if it is delivered to
user as defined.
49 | P a g e
Chapter – 10
Facts and Dimensions table
Dimension Table
 Dimension table is one that describes business entities of enterprise, represented as hierarchical and
categorical information. Dimension tables contain descriptive attributes that are typically textual fields. These
attributes are designed to serve query constraining and/or filtering, and query result set labeling. Dimension
tables sometimes called as lookup or reference tables. Dimension table rows are uniquely identified by a
single key field.
 Example: D_SHIPMENT table, D_INVOICE table and D_ORDER_RELEASE table.
Fact Table
 Fact table consists of the measurements, metrics or facts of a business process. A fact table typically has two
types of columns: those that contain facts and those that are foreign keys to dimension tables. The primary
key of a fact table is usually a composite key that is made up of all of its foreign keys. Fact tables provide the
(usually) additive values that act as independent variables by which dimensional attributes are analyzed.
 Fact table is located at the center of a star schema or a snowflake schema surrounded by dimension tables.
 Example: F_SHIPMENT_DETAIL table, F_INVOICE_VOUCHER_DETAIL table
Understanding Existing Schema (HDOWNER)
 HDOWNER contains historical data of OTM transactions. ETL loads OTM transactional data into HDOWNER
once the shipment status type SHIPMENT_HD_LOAD_STATUS value is changed to
SHIPMENT_READY_TO_LOAD.
 By default oracle provides below list of Dimension and Fact tables in HDOWNER.
Dimension Tables
1. D_DOMAIN contains domain information

2. D_INVOICE contains basic information of OTM invoices
3. D_SHIPMENT contains basic information of OTM shipments
4. D_ORDER_RELEASE contains basic information of OTM order releases
5. D_ORDER_BASE contains basic information of OTM order bases
6. D_PERSPECTIVE contains shipment perspective information
7. D_ITEM contains basic information of OTM items
8. D_LANE contains lane information
9. D_LOCATION contains location information
10. D_QUOTE contains basic information of OTM quote
11. D_SERVPROV contains service provides information
12. D_TRANSPORT_MODE contains transport mode information
13. D_VOUCHER contains basic information of OTM vouchers
14. D_TIME contains date information
15. D_SHIPMENT_REFNUM_QUAL contains shipment refnum qual information
16. D_SHIPMENT_REFNUM contains shipment refnum information
17. D_SHIPMENT_CLIAM_REFNUM contains shipment claims refnum information
18. D_SHIPMENT_CLIAM_REFNUM_QUAL contains shipment claims refnum qual information
50 | P a g e
19. D_SH_INV_BILL_REFNUM contains OTM bill refnum information

20. D_SH_INV_BILL_REFNUM_QUAL contains OTM bill refnum qual information
21. D_SH_INV_BILL_LINE_REFNUM contains OTM bill line refnum information
22. D_SH_INV_BILL_LINE_REFNUM_QUAL contains OTM bill line refnum qual information
23. D_QUOTE_REFNUM contains OTM quote refnum information
24. D_QUOTE_REFNUM_QUAL contains OTM quote refnum qual information
25. D_ORDER_RELEASE_REFNUM contains OTM order release refnum information
26. D_ORDER_RELEASE_REFNUM_QUAL contains OTM order release refnum qual information
27. D_INV_VOUCHER_REFNUM contains OTM voucher refnum information
28. D_INV_VOUCHER_REFNUM_QUAL contains OTM voucher refnum qual information
Fact Tables
1. F_BASE_UOM contains base uoms and conversion factor data

2. F_BULK_PLAN_DETAIL contains OTM bulk plan data
3. F_CAPACITY_COMMIT_ALLOC_DET contains capacity commitment allocation data
4. F_CAPACITY_COMMITMENT_DETAIL contains capacity commitment data
5. F_CARRIER_TENDER_PERFORMANCE contains service provide tender performance data
6. F_COST_VS_REVENUE contains shipment cost and revenue information
7. F_INVOICE_VOUCHER_DETAIL contains invoice voucher facts
8. F_INVOICE_VOUCHER_LINE_DETAIL contains invoice voucher line facts
9. F_ORDER_RELEASE_AUDIT_DETAIL contains order release audit data
10. F_ORDER_RELEASE_DETAIL contains order release facts
11. F_ORDER_RELEASE_ITEM_DETAIL contains order release item facts
12. F_QUOTE_DETAIL contains OTM quote measures
13. F_SHIPMENT_CLAIM contains shipment claims facts
14. F_SHIPMENT_DETAIL contains shipment measures
15. F_SHIPMENT_EVENT contains shipment events information
16. F_SHIPMENT_INVOICE_BILL_DETAIL contains OTM bill measures
17. F_SHIPMENT_INVOICE_BILL_LINE_D contains OTM bill line measures
18. F_SHIPMENT_ORDER_RELEASE_COST contains shipment order release cost information
19. F_SHIPMENT_STOP_ACTIVITY_D contains shipment stop activity measures
20. F_TARGETS contains target measures
Exercise:
1. Create the below dimension tables. Put your Emp ID as suffix to identify the tables created by you.
1. D_ACCESSORIAL_CODE contains accessorial code information
2. D_ACCESSORIAL_COST contains accessorial cost information
3. D_SPECIAL_SERVICE contains special service information
4. D_RATE_DETAIL contains rate record and rate offering information
2. Create the below fact tables. Put your Emp ID as suffix to identify the tables created by you.
1. F_RATE_COST_DETAIL contains rate cost information

2. F_RATE_STOPS_COST contains rate stop cost information
51 | P a g e
Chapter – 11
Overview of ODI tool and use of ODI in FTI
Oracle Data Integrator (ODI)
o Oracle Data Integrator (ODI) is a software application based on ETL (extract-

transform-load) structure used for data transformation and merging processes. In
today's business the meaning of well-organized data has increased dramatically and
that is why having specialized software is so important.
o Furthermore, these applications must be prepared to work in mixed systems and

platforms environment and be sure that none of the quality will deteriorate. Oracle
Data Integrator provides declarative rules apart from implementation details and also
it’s E-LT (extract-load, transform) structure eliminates need of having separate ETL
server which results in optimized performance, efficiency and scalability.
o ODI Architecture
 Main architecture component in Oracle Data Integrator is the repository that is accessed
by client-server mode or thin client mode.
 Repository is absolutely open, comprehensive, shared metadata database which is

accessible for the applications responsible for transformation, project development,
integration and information redistribution. Other architecture components are the
Topology Manager, Designer, Security Manager, Operator and Agent
 Designer defines declarative rules for data transformation and data integrity. All project
development takes place in this module; this is where database and application metadata
are imported and defined. The Designer module uses metadata and rules to generate
scenarios for production. This is the core module for developers and metadata
administrators.
 Operator manages and monitors production. It is designed for production operators and
shows execution logs with error counts, the number of rows processed, execution
52 | P a g e
statistics, the actual code that is executed, and so on. At design time, developers can
also use the Operator module for debugging purposes.
 Topology Manager defines the physical and logical architecture of the infrastructure.
The administrators of the infrastructure or project register servers, schemas, and agents
in the master repository through this module.
 Security Manager manages user profiles and their access privileges. Security Manager
can also assign access privileges to objects and features. Security administrators
generally use this module. All modules store their information in the centralized
repository.
 Repositories
 The repository consists of a master repository and several work repositories.

These repositories are databases stored in relational database management
systems. All objects that the modules configure, develop, or use are stored in
one of these repositories, and are accessed in client-server mode by the
various components of the architecture.
 There is usually only one master repository, which contains the security
information (user profiles and privileges), the topology information (definitions
of technologies and servers), and the versions of the objects. The information
contained in the master repository is maintained with Topology Manager and
Security Manager. All modules have access to the master repository,
because they all store topology and security information there.
 Project objects are stored on the work repository. Several work repositories
can coexist in the same installation. This is useful for maintaining separate
environments or to reflect a particular versioning lifecycle—for example,
development, qualification, and production environments.
 A work repository stores information for

o Models—including data stores, columns, data integrity constraints,
cross references, and data lineage
o Projects—including declarative rules, packages, procedures,
folders, knowledge modules, and variables
o Runtime information—including scenarios, scheduling information,
and logs
53 | P a g e
 Users manage the content of a work repository with the Designer and
Operator modules.
 The Agent at runtime also accesses work repositories. When a work

repository is used only to store execution information (typically for production
purposes), it is called an execution repository. An execution repository is
accessed at runtime with the Operator interface and by Agents. It is
important to remember that all work repositories are always attached to one
and only one master repository.
54 | P a g e
ODI Interfaces for FTI
Understanding Existing Interfaces
ODI interfaces load OTM data from GLOGOWNER to HDOWNER.

By default oracle provides below list of ODI interfaces, which are types
 Initial Load Interfaces
For first time load from GLOGOWNER to HDOWNER
 Incremental Load Interfaces.
For loading incremental data from GLOGOWNER to HDOWNER
Initial Load Interfaces
1. INIT_BILLS_D_INVOICE
2. INIT_BILLS_D_SH_INV_BILL_LINE_REFNUM
3. INIT_BILLS_D_SH_INV_BILL_LINE_REFNUM_QUAL
4. INIT_BILLS_D_SH_INV_BILL_REFNUM
5. INIT_BILLS_D_SH_INV_BILL_REFNUM_QUAL
6. INIT_BILLS_F_SHIPMENT_INVOICE_BILL_DETAIL
7. INIT_BILLS_F_SHIPMENT_INVOICE_BILL_LINE_D
8. INIT_DOMAIN_GRANTS_MADE
9. INIT_DOMAIN_SETTING
10. INIT_D_DOMAIN
11. INIT_D_INVOICE
12. INIT_D_ITEM
13. INIT_D_LANE
14. INIT_D_LOCATION
15. INIT_D_ORDER_BASE
16. INIT_D_ORDER_RELEASE
17. INIT_D_ORDER_RELEASE_REFNUM
18. INIT_D_ORDER_RELEASE_REFNUM_QUAL
19. INIT_D_QUOTE
20. INIT_D_QUOTE_REFNUM
21. INIT_D_QUOTE_REFNUM_QUAL
22. INIT_D_SERVPROV
23. INIT_D_SHIPMENT
24. INIT_D_SHIPMENT_CLAIM_REFNUM
25. INIT_D_SHIPMENT_CLAIM_REFNUM_QUAL
26. INIT_D_SHIPMENT_REFNUM
27. INIT_D_SHIPMENT_REFNUM_QUAL
28. INIT_D_SH_INV_BILL_LINE_REFNUM
29. INIT_D_SH_INV_BILL_LINE_REFNUM_QUAL
30. INIT_D_SH_INV_BILL_REFNUM
31. INIT_D_SH_INV_BILL_REFNUM_QUAL
32. INIT_D_SPECIAL_SERVICE
33. INIT_D_TIME
34. INIT_D_TRANSPORT_MODE
35. INIT_EXTERNAL_PREDICATE
36. INIT_E_KPI
37. INIT_E_ORDER_BASE_KEY
38. INIT_E_ORDER_RELEASE_KEY
39. INIT_E_SHIPMENT_KEY
40. INIT_F_BASE_UOM
41. INIT_F_BULK_PLAN_DETAIL
42. INIT_F_CAPACITY_COMMITMENT_DETAIL
55 | P a g e
43. INIT_F_CAPACITY_COMMIT_ALLOC_DET
44. INIT_F_CARRIER_TENDER_PERFORMANCE
45. INIT_F_COST_VS_REVENUE
46. INIT_F_ORDER_RELEASE_AUDIT_DETAIL
47. INIT_F_ORDER_RELEASE_DETAIL
48. INIT_F_ORDER_RELEASE_ITEM_DETAIL
49. INIT_F_QUOTE_DETAIL
50. INIT_F_SHIPMENT_CLAIM
51. INIT_F_SHIPMENT_DETAIL
52. INIT_F_SHIPMENT_EVENT
53. INIT_F_SHIPMENT_INVOICE_BILL_DETAIL
54. INIT_F_SHIPMENT_INVOICE_BILL_LINE_D
55. INIT_F_SHIPMENT_ORDER_RELEASE_COST
56. INIT_F_SHIPMENT_STOP_ACTIVITY_D
57. INIT_F_TARGETS
58. INIT_F_TARGETS_STAGE
59. INIT_GC3_TABLE_CODE
60. INIT_GC3_VERSION
61. INIT_GL_USER
62. INIT_PLANNING_PARAMETER
63. INIT_PREFERENCE
64. INIT_REPORT_COMMON_PROPERTIES
65. INIT_TABLE_SEQUENCE_ASSOC
66. INIT_TABLE_SET
67. INIT_TABLE_SET_DETAIL
68. INIT_USER_ACCESS
69. INIT_USER_ASSOCIATION
70. INIT_USER_PREFERENCE
71. INIT_USER_PREFERENCE_ACCESS
72. INIT_USER_PREFERENCE_D
73. INIT_USER_ROLE
74. INIT_VPD_CONTEXT
75. INIT_VPD_CONTEXT_VARIABLE
76. INIT_VPD_PROFILE
Incremental Load Interfaces
1. INCR_BILLS_D_INVOICE
2. INCR_BILLS_D_SH_INV_BILL_LINE_REFNUM
3. INCR_BILLS_D_SH_INV_BILL_LINE_REFNUM_QUAL
4. INCR_BILLS_D_SH_INV_BILL_REFNUM
5. INCR_BILLS_D_SH_INV_BILL_REFNUM_QUAL
6. INCR_BILLS_F_SHIPMENT_INVOICE_BILL_DETAIL
7. INCR_BILLS_F_SHIPMENT_INVOICE_BILL_LINE_D
8. INCR_D_DOMAIN
9. INCR_D_INVOICE
10. INCR_D_ITEM
11. INCR_D_LANE
12. INCR_D_LOCATION
13. INCR_D_ORDER_BASE
14. INCR_D_ORDER_RELEASE
15. INCR_D_ORDER_RELEASE_REFNUM
16. INCR_D_ORDER_RELEASE_REFNUM_QUAL
17. INCR_D_QUOTE
18. INCR_D_QUOTE_REFNUM
19. INCR_D_QUOTE_REFNUM_QUAL
56 | P a g e
20. INCR_D_SERVPROV
21. INCR_D_SHIPMENT
22. INCR_D_SHIPMENT_CLAIM_REFNUM
23. INCR_D_SHIPMENT_CLAIM_REFNUM_QUAL
24. INCR_D_SHIPMENT_REFNUM
25. INCR_D_SHIPMENT_REFNUM_QUAL
26. INCR_D_SH_INV_BILL_LINE_REFNUM
27. INCR_D_SH_INV_BILL_LINE_REFNUM_QUAL
28. INCR_D_SH_INV_BILL_REFNUM
29. INCR_D_SH_INV_BILL_REFNUM_QUAL
30. INCR_D_TIME
31. INCR_D_TRANSPORT_MODE
32. INCR_E_KPI
33. INCR_E_ORDER_BASE_KEY
34. INCR_E_ORDER_RELEASE_KEY
35. INCR_E_SHIPMENT_KEY
36. INCR_F_BASE_UOM
37. INCR_F_BULK_PLAN_DETAIL
38. INCR_F_CAPACITY_COMMITMENT_DETAIL
39. INCR_F_CAPACITY_COMMIT_ALLOC_DET
40. INCR_F_CARRIER_TENDER_PERFORMANCE
41. INCR_F_ORDER_RELEASE_AUDIT_DETAIL
42. INCR_F_ORDER_RELEASE_DETAIL
43. INCR_F_ORDER_RELEASE_ITEM_DETAIL
44. INCR_F_QUOTE_DETAIL
45. INCR_F_SHIPMENT_CLAIM
46. INCR_F_SHIPMENT_DETAIL
47. INCR_F_SHIPMENT_EVENT
48. INCR_F_SHIPMENT_INVOICE_BILL_DETAIL
49. INCR_F_SHIPMENT_INVOICE_BILL_DETAIL_INS
50. INCR_F_SHIPMENT_INVOICE_BILL_DETAIL_INV_UPD
51. INCR_F_SHIPMENT_INVOICE_BILL_DETAIL_SH_UPD
52. INCR_F_SHIPMENT_INVOICE_BILL_LINE_D
53. INCR_F_SHIPMENT_INVOICE_BILL_LINE_D_INS
54. INCR_F_SHIPMENT_INVOICE_BILL_LINE_D_INV_UPD
55. INCR_F_SHIPMENT_INVOICE_BILL_LINE_D_SH_UPD
56. INCR_F_SHIPMENT_ORDER_RELEASE_COST
57. INCR_F_SHIPMENT_STOP_ACTIVITY_D
58. INCR_F_TARGETS
59. INCR_F_TARGETS_RECALCULATE
60. INCR_F_TARGETS_RECALCULATE_STEP2
61. INCR_F_TARGETS_STAGE
Custom Development (New development)
Initial Load Interfaces
1. INIT_D_ACCESSORIAL_CODE
2. INIT_D_ACCESSORIAL_COST
3. INIT_D_RATE_DETAIL
4. INIT_D_SPECIAL_SERVICE
5. INIT_F_RATE_COST_DETAIL_RATE_GEO_ACCESSORIAL
6. INIT_F_RATE_COST_DETAIL_RATE_GEO_COST
7. INIT_F_RATE_COST_DETAIL_RATE_OFFERING_ACCESSORIAL_FUAL
8. INIT_F_RATE_COST_DETAIL_RATE_OFFERING_ACCESSORIAL_OTHERS
57 | P a g e
9. INIT_F_RATE_COST_DETAIL_RO_SPECIAL_SERVICE
10. INIT_F_RATE_STOPS_COST_RATE_GEO_STOPS
11. INIT_F_RATE_STOPS_COST_RATE_OFFERING_STOPS
12. INIT_F_SHIPMENT_COST_DETAIL
Incremental Load Interfaces
1. INCR_D_ACCESSORIAL_CODE
2. INCR_D_ACCESSORIAL_COST
3. INCR_D_RATE_DETAIL
4. INCR_D_SPECIAL_SERVICE
5. INCR_F_RATE_COST_DETAIL_RATE_GEO_ACCESSORIAL
6. INCR_F_RATE_COST_DETAIL_RATE_GEO_COST
7. INCR_F_RATE_COST_DETAIL_RATE_OFFERING_ACCESSORIAL_FUEL
8. INCR_F_RATE_COST_DETAIL_RATE_OFFERING_ACCESSORIAL_OTHERS
9. INCR_F_RATE_COST_DETAIL_RO_SPECIAL_SERVICES
10. INCR_F_RATE_STOPS_COST_RATE_GEO_STOPS
11. INCR_F_RATE_STOPS_COST_RATE_OFFERING_STOPS
12. INCR_F_SHIPMENT_COST_DETAIL
Importing Custom table metadata into ODI
 Login to Designer tool of ODI

 Select Model tab and select ORACLE FTI and right click on that and select Edit option
Right click &

select Edit
Model Tab
 Go to Selective Reverse tab and check New Data stores & Objects to Reverse options and select table
names from the list and click on Reverse button.
58 | P a g e
 Once “Done” appears below click OK and Check table names in ORACLE FTI model, which are reversed.
Creating ODI Interface
 Navigate to Projects>FTI ETL>FTI ETL>Interfaces

 Right click on Interfaces and select Insert Interface
59 | P a g e
Definition tab
 Enter name
 select Optimization context as Global
 Check staging area different from target and select ORACLE_HDOWNER from the dropdown list.
Diagram Tab
 Drag all source tables from ORACLE OTM model into Source workplace section.
 Drag target table from ORACLE FTI model into Target datastore section.
 Map the target columns with source table’s columns.
60 | P a g e
 Add required filters

Ex: 1. STATUS_TYPE.STATUS_TYPE_XID = '#V_SHIPMENT_STATUS_TYPE'
2. STATUS_VALUE.STATUS_VALUE_XID = '#V_SHIPMENT_STATUS_VALUE'
Flow Tab
 Select ORACLE_OTM and select LKM SQL to Oracle from the dropdown list of LKM Section.
61 | P a g e
 Select ORACLE_FTI and check distinct Rows option

 Select IKM SQL Control Append from the dropdown list of IKM Section
Control Tab
 Select CKM Oracle from the dropdown list
62 | P a g e
 Click Apply and then OK
Exercise:
1. Create ODI interfaces for populating the dimension table D_ACCESSORIAL_CODE,
D_ACCESSORIAL_COST. Put your Emp ID as suffix to identify the interfaces created by you.
2. Create ODI interface for populating the fact table F_RATE_COST_DETAIL. Put your Emp ID as suffix to
identify the interfaces created by you.
63 | P a g e
Chapter – 12
Overview of OBIEE tool and using OBIEE in FTI
Oracle Business Intelligence Enterprise Edition (OBIEE)

o Oracle Business Intelligence Enterprise Edition (OBIEE) is a business intelligence system for the
enterprise that delivers abilities for reporting, ad hoc query and analysis, online analytical processing
(OLAP), dashboards, and scorecards. OBIEE is a comprehensive suite of enterprise BI products that
delivers a full range of analysis and reporting capabilities along with a unified, highly scalable and
modern architecture .Provides user with accurate and consistent insight to the information.
o The Oracle Business Intelligence components consist of:
o Oracle Business Intelligence Presentation Services
 The Oracle Business Intelligence Presentation Services provides the framework and
interface for presentation of Business Intelligence data to web clients. It maintains a
Presentation Catalog service on the file system for the customization of this
presentation framework. It is a standalone process and integrates with the Oracle
Business Intelligence Presentation Services Plug-in from which it receives web client
requests. It communicates with the Oracle Business Intelligence Server using ODBC
over TCP/IP.
o Oracle Business Intelligence Server
 The Oracle Business Intelligence Server is a stand-alone process that maintains the
logical data model which it provides to BI Presentation Services via ODBC. Metadata is
64 | P a g e
maintained for the data model in a local proprietary file called the repository file (rpd). On
the back-end, the BI Server connects to customer data stores via data source adaptors.
o Oracle Business Intelligence Scheduler
 The Oracle Business Intelligence Scheduler is an extensible scheduling application for

scheduling reports to be delivered to users at specified times. It is the engine behind the
Oracle Business Intelligence Delivers feature.
o Oracle Business Intelligence Publisher
 The Oracle Business Intelligence Publisher generates highly-formatted, pixel-perfect

enterprise reports.
o Oracle Business Intelligence Java Host
 The Oracle Business Intelligence Java host provides services to BI Presentation Services
for Charts, Gauges and PDFs. The services are provided based on request-response
model.
o Oracle Business Intelligence Presentation Services Plug-in
 The Oracle Business Intelligence Presentation Services Plug-in is the entry point for web
client requests to BI Presentation Services.
65 | P a g e
OBIEE Repository (RPD)
Understanding Existing RPD
 Developer is going to have to create the master query that provides business users with their simplified view
of business data. In OBIEE the equivalent of master queries are held in a data store called a repository
(.rpd file), and they are created and maintained using a software product called the BI Administration Tool.
 OBIEE consists of three distinct layers: the Physical layer, the Business Model & Mapping (BMM) layer, and
the presentation layer.
 Physical layer
Represents the physical structure of the data sources to which the Oracle BI Server submits queries. This
layer is displayed in the right pane of the Administration Tool.
 Business Model and Mapping layer
Represents the logical structure of the information in the repository. The business models contain logical
columns arranged in logical tables, logical joins, and dimensional hierarchy definitions. This layer also
contains the mappings from the logical columns to the source data in the Physical layer. It is displayed in
the middle pane of the Administration Tool.
66 | P a g e
 Presentation layer
Represents the presentation structure of the repository. This layer allows you to present a view different
from the Business Model and Mapping layer to users. It is displayed in the left pane of the Administration
Tool.
Custom Development
Adding New Objects to Physical Layer
 Go to start menu and Open Administration tool then Go to file menu ->open -> select Online
option.
 Select rpd name from below list.
 Go to file and select Import then from Database.
67 | P a g e
 Enter below details
 Expand HDOWNER and Select objects to be imported into physical Layer and click on Import
68 | P a g e
 Drag and drop all object into existing HDOWNER folder.
69 | P a g e
 Select all dimension tables related to fact table and right click go to Physical diagram and the
select Selected Objects(s) only.
70 | P a g e
 Select New Foreign Key Icon and select dimension table and then fact table and select matching
column from fact table.
Click on
 Similarly join all dimension tables with fact table then close below window.
71 | P a g e
72 | P a g e
Adding New Objects to Business Model and Mapping layer
 Drag and drop all new objects into Business Model and Mapping layer (middle layer).
 Create dimension for all dimension tables for drill down and drill up option.
 Right click on Fusion transportation Intelligence and select new object and then dimension.
73 | P a g e
 Right click on Accessorial Code and select New Object and then Logical Level
74 | P a g e
 Right click on All Accessorial Codes and select New Object and then Child Level and enter
Accessorial Code in General tab then drag and drop the primary key column from
D_ACCESSORIAL_CODE table.
 Do similar steps for remaining all dimension tables.
75 | P a g e
 Select all related dimension table and new fact table in BMM layer and right click and select
business Model Diagram and then Selected Tables only.
 Select New Foreign Key Icon and select dimension table and then fact table and select matching
column from fact table.
76 | P a g e
 Similarly join all dimension tables with fact table then close below window.
77 | P a g e
Adding New Objects to Presentation layer
 Drag and drop all new logical tables into Fusion transportation Intelligence folder in Presentation
Layer.
 Click on check to check consistency of rpd and save the rpd file.
Click on
Exercise:
1. Create the hierarchy for the Accessorial information in the OTM RPD using the dimension tables
D_ACCESSORIAL_CODE and D_ACCESSORIAL_COST. Put your Emp ID as suffix to identify the hierarchy
and it’s elements created by you.
2. Create the hierarchy for the Accessorial information in the OTM RPD using the fact table
F_RATE_COST_DETAIL. Put your Emp ID as suffix to identify the hierarchy and it’s elements created by
you.
78 | P a g e

OTM Reports FTI Training Manual

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OTM Reports FTI Training Manual

Enviado por

Direitos autorais:

Formatos disponíveis

OTM Reports & FTI Training Manual

Oracle Transportation Management

OTM BI Reports & FTI Training

About this training manual:

In this lesson, you will learn how to:

What is OTM data model?

1. OTM data model is basically the data dictionary.

OTM supports two methodologies to generate reports:

 There are 3 components of the report:

Types of query templates:

 Parameter specification. Parameters can be typed and explicitly listed

There are three primary components of a data template:

Attach is the example for the data template

Creating Query Template in OTM

Section - 1: Query Template

1. Enter a Query Template.

Section - 2: XML Information

Creating Format Template in OTM

Section - 1: Format Template

 Enter a name for the Format Template.

Section - 2: Template Details (Optional)

 Select a Data Query Type.

o PDF Watermark Configuration

 Select Text or Image from the Use Watermark option buttons.

 If you select a watermark type of Text:

 If you select a watermark type of Image:

o PDF Page Configuration

o Translation Template (Optional)

 Enter a Translation Template.

Creating Report with single parameter

The basic steps to create an embedded analytical report are:

• create Database Package

Step 1: Create Database Package and execute in REPORTOWNER schema

 Define three variables in the database package specification

 P_L_TRANSPORT_MODE VARCHAR2 (32766) for input parameter

 P_L_TRANSPORT_MODE_WHERE VARCHAR2 (32766) for getting where condition

 Modify SET_LEXICAL_PARAMETERS procedure in the package with defined input

Step 2: Create a Data Template

 Define input parameters in the parameter section of xml data template.

 P_GL_USER and P_ROLE_ID are prefined parameters and P_L_TRANSPORT_MODE is

 Define xml tags to store data in dataStructure

 Attach is the sample xml data template.

Step 3: Create a Query Template

Step 4: Export Sample XML for Layout Design

 Save the document to a drive accessible by the BI Publisher Template Builder.

Step 5: Design a Layout

 Open up Microsoft Word and Add-Ins tab

 Attach is the sample rtf template.

Step 6: Create a Format Template

 Upload the RTF file created in step 5

 Select Finished to save the format template.

Step 7: Create a Report

 Add input parameters in the Report Parameters Section: P_L_TRANSPORT_MODE.

The resulting report in the Report Manager is shown below:

 Select Finished to save the report.

Creating Report with Multiple parameters

• create Database Package

Step 1: Create Database Package and execute in REPORTOWNER schema

 Define below variables in the database package specification

 P_L_TRANSPORT_MODE VARCHAR2 (32766) for input parameter

 P_L_TRANSPORT_MODE_WHERE VARCHAR2 (32766) for getting where condition in db query

 P_H_TRANSPORT_MODE VARCHAR2 (32766) for displaying input parameter in format template.

 P_L_WT_UTIL VARCHAR2(32766) for input parameter

 P_L_WT_UTIL_WHERE VARCHAR2(32766) for getting where condition in db query