1

2
3
Welcome to the Oracle Transportation Management Transfer of
Information session for enhancements to the planning section of the
OTM 6.2 release. This product introduction provides a high-level
description of the key features added to planning in the OTM release
6.2.

4
This session will prepare you to:

Identify the new functionality included in this release

Learn how to configure the new functionality
Find additional release information and resources

5
This session will cover the new features added to Oracle
Transportation Management for planning in version 6.2 including:
Parameter Set Persistence
Diagnostics Enhancements
For each feature, we will review:
A description of the feature and the business value it provides.

At the end of the session, we will provide a list of resources where you
can find additional information.

6
First, lets review the changes added for parameter sets.

7
Parameters determine how various processes behave within OTM.
For example, you could use parameters to rank itineraries for
shipment processing, perform order bundling, or to determine how to
estimate rate distance. Parameters are grouped into parameter sets
and parameter sets are selected when executing actions or processes
against certain orders or shipments. Parameter sets are used to
control the way OTM builds and modifies shipments. They can be
selected in the context of executing an action from the OTM
managers or they can assume default values specified on either the
user preference or at the domain level.

8
 In previous versions of OTM, without manual intervention, there was no way to
ensure that the parameter set that was used to create the shipment would be
used during subsequent shipment actions. The result is that the modified
shipment would be re-driven using potentially different business rules.
Once a parameter set was invoked, there was no way to ensure that the same
parameter set was used again for subsequent actions. This could cause
problems if parameter settings were different between the default parameter set
and the parameter set that was used against the shipment. For example, if a
parameter set containing the parameter value Hold As Late As Possible set to
FALSE was used to create a shipment, that shipment would be built from the
pickup dates of the order. If the shipment was subsequently tendered and the
tender timed out, the shipment would be re-driven using the default parameter
set. If the default parameter set had a Hold As Late As Possible set to TRUE,
this shipment would be re-driven using the delivery dates on the order. This
could mean that an entirely different solution set would be tried for the
retendered shipment, resulting in incorrect carrier selection.
To view and edit parameter sets, go to Shipment Management > Power Data >
General > Parameter Sets.

9
 In this release, OTM stores the parameter set used to create the shipment on
the shipment object itself. This value will appear in the Shipment Manager and
can be queried via the shipment search page. If configured, subsequent
shipment actions can use this parameter set to calculate and redrive the
shipment, leading to more consistent results.
The Parameter Set ID is an editable field in the Shipment Manager which allows
you to manually override the value that is used during bulk plan. This provides
an additional level of control over the parameter set used in subsequent actions.

10
You can set parameter persistence up either at the domain level or the
user level. To set on the domain level, select the User Parameter Set
on Shipment on the Domain Setting page. To access the Domain
Setting page, go to Configuration and Administration > Domain
Management > Domain Settings.

You can also control parameter set persistence via a property,

glog.business.shipment.useShipmentPlanningParameterSet. If true,
use the shipment's parameter set (if any) for shipment actions.
Otherwise, use the default parameter set (for user or for domain). The
default is true.

11
Next, lets review the enhancements to planning diagnostics.

12
The Planning Diagnostics feature was introduced in OTM 6.0 as an
infrastructure that enhances planning-related error handling and
diagnostics. The diagnostic log is an additional logging tool that
provides a more readable report of the activity performed in a
process. When properly configured, you can view diagnostics via the
View Diagnostics button wherever it appears.
Diagnostics configuration is set up on the Diagnostic Process
Configuration page which is accessed via Operational Planning >
Power Data > Planning > Diagnostic Process Configuration.

13
 In previous versions of OTM, diagnostics logging was available for several areas
of the bulk plan process. However, there were still several major areas for which
diagnostics were not provided.

Diagnostics has been enhanced in 6.2 to include the following additional areas
within bulk plan:
General bulk plan flow
Multi-stop
Service provider assignment
Container optimization
Multi-leg
Service time

The additional information is provided to assist you in isolating processing logic

and errors which should lead to quicker resolution of unexpected process
results.

14
 Bread crumb trails have been added to OTM for 6.2. One example is on the
Diagnostic Log Viewer page shown here. Bread crumb trail displays the Process
Step of a selected row as well as all of its ancestors.
If you click on any of the ancestors (links) in the trail, the viewer will move to that
specified row, the row will be highlighted and the bread crumb trail will be
updated.

To access the Diagnostic Log Viewer page, click the View Diagnostics button.
This page can also be accessed via Operational Planning > Process
Management > Diagnostics > View Diagnostics. Enter a Diagnostic Log File ID
and click View Results. If no processes were run, or diagnostics is not enabled,
the process list will be empty.

Diagnostics configuration is set up on the Diagnostic Process Configuration

page which is accessed via Operational Planning > Power Data > Planning >
Diagnostic Process Configuration.

15
 OTM has new capabilities to filter results you see on the Diagnostics Log View page.
You can filter by process step, status, and entity name. For example, if you run a bulk
plan for 20 orders you do not need to review the results for all 20 orders. You can filter
the results for just the one order that failed.
The Diagnostic Log Filter page is accessed by clicking the Filter button on the
Diagnostics Log View page shown on the previous slide.

Process Steps: You can select multiple process steps to filter on. Examples of process
steps are Identify Valid Itineraries, Build Shipments, Create Bundles, Simulation Drive,
and Trailer Build.
Statuses allow you to restrict the log to certain statuses such as Failure, Success, etc.
Entity Name: Examples of Entity Names are: BULK_PLAN, ORDER_RELEASE,
EQUIPMENT_GROUP, ITINERARY, and RATE_SERVICE.
Entity values can be optionally specified as well, such as returning only entities which
match an ORDER_RELEASE of 004-OR.

You can filter by one or more filters. Additionally, you can specify multiple items within a
filter. So if you wanted to see all bulk plan and order release lines which failed within the
Identify Valid Itineraries process step, you would set up the Diagnostic Log Filter as
shown on this slide.

The Diagnostics Log Viewer is refreshed showing the filtered data. The Viewer will show
any process step that matches the selected filters, the parent process, and any sub-
processes under the matching process steps. When the viewer displays filtered data, you
can click the Filter button to show the filter criteria.

16
17
18
OTM specific resources including TOIs, Education, and My Oracle
Support information are listed on the next few slides.

19
20
21
22