Course Presentation-OTM

1-1 © 2008 Oracle Corporation – Proprietary and Confidential
The following is intended to outline our general

product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle‟s
products remains at the sole discretion of Oracle.
For Oracle employees and authorized partners only. Do not distribute to third parties. 2
© 2009 Oracle Corporation – Proprietary and Confidential
Oracle Training Materials – Usage Agreement
Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:
1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and
copy the information, documents, and the online training courses (collectively, “Materials") found on this
Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner‟s
employees only. The Materials may not be used for training, promotion, or sales to customers or other
partners or third parties.
2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other
third party at no time has any right to resell, redistribute or create derivative works from the Materials.
3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any

Materials. Materials are provided "as is" without warranty of any kind, either express or implied,
including without limitation warranties of merchantability, fitness for a particular purpose, and non-
infringement.
4. Under no circumstances shall Oracle or the Oracle Authorized Delivery Partner be liable for any loss,
damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site
of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against
any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys'
fees) arising out of Partner‟s use of the Materials.
5. Reference materials including but not limited to those identified in the Boot Camp manifest can not be
redistributed in any format without Oracle written consent.
<Insert Picture Here>
OTM 6.2 Functional Implementation Boot Camp

What is Functional Boot Camp Training?
 Designed for Consultants who will implement OTM
 Participants should have an understanding of OTM and Logistics

concepts
 Participants will learn the basic configurations of OTM 6.2
 Participants will also receive “Hands-on” Training via:
 Multi-Stop, Multi-Leg, and Freight Payment Scenarios
 Fleet Management, Data Management, and Agent Configuration

walk-through exercises
BOOT CAMP AGENDA
Day 1:
 OTM Core Functionality & Shipment Planning Overview
Day 2:
 OTM Core Functionality & Shipment Planning Overview (continued from Day 1, as needed)
 Fleet Management Overview & Student Exercises
 Freight Payment Overview & Student Exercises
 Freight Payment Configuration document (Share with students. Review at end of week as time allows)
 Multi-Stop Student Work Assignment Introduction / Overview
Day 3:
 Data Management & Loading Overview
 Automation Agents, Application Workflow Overview & Student Exercises
 Multi-Stop Student Work Assignment Introduction / Overview (continued from Day 2, as needed)
 Multi-Stop Student Work Assignment (Student Work Session)
Day 4:
 Multi-Stop Student Work Assignment (Student Work Session) ((continued from Day 3, as needed)
 Multi-Leg Student (TEAM) Work Assignment Introduction / Overview
Day 5:
 Multi-Leg Student (TEAM) Work Assignment (Student Work Session)
 Multi-Leg Student (TEAM) Work Assignments PRESENTATIONS TO THE CLASS
 Course Wrap-Up and Feedback
OTM Domains
The “out of the box” domains provide two logon IDs at the time of creation:
 “domain name”.ADMIN
 “domain name”.DEFAULT
 Examples: “GUEST.ADMIN”, “GUEST.DEFAULT”,
“SERVPROV.ADMIN”, etc.
For each new standalone, child, grandchild, etc. domain that is created, one
logon is created:
 “domain name”.ADMIN
 e.g. “COREDEMO.ADMIN”
Default Permissions for each domain to the others is:

 Public has READWRITE to all domains
 Each domain has READ permission to PUBLIC
 SERVPROV has READWRITE to each standalone domain, and each
standalone domain has READWRITE to SERVPROV
 Each domain has READWRITE to itself
OTM DEFAULT Domain relationships
PUBLIC
READ & WRITE READ ONLY
BLUEPRINT S READ “Company X”

WRITE
WRITE
E
READ
READ WRITE
GUEST R
R
READ WRITE
READ
EBSO V WRITE “C1”
NO rights
P
GLOG READ
to
R WRITE “C2” Company X
E1 O
READ
V “C3”
STAGE WRITE
GLOBAL
READ ONLY
REPORT USER
OTM Domain Permissions
Go to Configuration and Administration > Domain Management >

Domain Grants to view and manage OTM domain relationships
 By default, PUBLIC grants READ access to COREDEMO (a standalone domain)
 By default, SERVPROV grants READ & WRITE access to COREDEMO
 By default, COREDEMO grants READ & WRITE access to SERVPROV
 By default, COREDEMO grants READ access to GLOBAL_REPORT_USER
 By default, COREDEMO grants READ & WRITE access to itself
OTM Domain Creation
Create a subdomain (child) to the COREDEMO domain, named COREDEMOSUB1; go to

Configuration and Administration > Domain Management > Add Domain. Name the
domain and set parameters if desired (none are needed), then click the “Add Subdomain”
button.
 While OTM is in the process of creating

the domain, the button will read “Adding
Subdomain”. When the process is
complete, OTM will display a confirmation
window showing the name of the
subdomain; (“COREDEMO /
COREDEMOSUB1” e.g.)
OTM Domain Permissions
Go to Configuration and Administration > Domain Management > Domain
Grants to view COREDEMO/COREDEMOSUB1 permissions;
 By default, COREDEMO/COREDEMOSUB1 is granted READ access to PUBLIC
 By default, COREDEMO/COREDEMOSUB1 is granted READ & WRITE access to
SERVPROV
 By default, SERVPROV grants READ & WRITE access to
COREDEMO/COREDEMOSUB1
 By default, COREDEMO/COREDEMOSUB1 grants READ access to
GLOBAL_REPORT_USER
Menus help you to navigate through the different
areas of OTM that are important to you
 Menus are typically customized to

display only what the users need
to see. For example, a Planner‟s
menu will include menu items for
Planning like Order Management,
Shipment Management and
Operational Planning.
 An Accounts Payable Clerk‟s
menu may only display
Financials.
 A carrier‟s menu may only allow
them to manage their tenders and
capacity, and update shipment
status events.
OTM can be customized for a user
 User roles
 User preferences
User roles control the data
each user can access
Corporation
One
Planner
PUBLIC DATA
Internet
Corporation Corporation One
Two Buyer
Corporation Two
Corporation Shipper
Three Corporation Three
Warehouse
OTM Data
Corporation
Four
Customer Secured User Data
Remote
Administrator User Role
User Preferences enable you to define how
certain data is displayed to the user
When implementing
OTM, you need to load
your business-specific
data
OTM contains location data including details
that pertain to your business
 Location
 Calendar
 Contact
A location is a fixed node or point where
cargo is shipping to, shipping from, or flowing
through
A calendar allows or limits activities at a
location
A contact is a person or system to which
you want to send notifications or tenders
OTM includes information about your service
providers and their rates
 Service Provider
 Rates
A service provider is a company which
provides some sort of service to you
Rates are used by service providers to define
the cost of a transportation-based service
Rate Distance Rate Service
Rate Offering
Rate Record Rate Record Rate Record
The 4 Components of Rates
 Rate Distance determines the distance from one location

to another location.
 Rate Service determines the time required to transport
goods from one location to another location.
 Rate Offering contains the contract level data specific to a
service provider.
 Rate Record contains specific costing data from one
location to another.
Additional data is defined specific to your
business
 Items
 Equipment
 Itinerary
Items are what you are shipping from one
location to another
Equipment is used to transport items from one
location to another
Equipment Group
Profile Set
40‟ and 45‟ Equipment
Equipment Group Equipment Group

Profile Profile
40‟ Equipment 45‟ Equipment
Equipment Group Equipment Group Equipment Group

40‟ Trailer 45‟ Trailer 45‟ Container
An itinerary determines the specific route for a
shipment
Once configured, you
can begin to use OTM
on a day-to-day basis,
building shipments and
processing transactions
OTM enables you to manage your orders at
different levels
 Order Base
 Order Release
 Order Movement
Orders represent the requirement to move
freight from one point
to another
Order
An Order Base includes detailed
information about an order
An Order Release represents an order that is
ready to ship
An Order Release has at least two Order Stops
 Order Stops provide a way of routing an order that

needs to make specific stops between the source
and destination location(s).
 Every Order Release has at least two stops; (1)
pick-up stop, and (1) drop-off stop
Order Movements enable you to plan
separate legs of a shipment separately, based
on routing
OTM enables you to plan your orders
into shipments
 Planning
 Consolidation
OTM can plan each Order Release into its
own shipment
Order Order Release Shipment
OTM can consolidate two or more Order
Releases into one or more shipments, in
order to achieve the least cost move
Order Release
Shipment
Order Release
OTM provides several options for building
shipments
 Build Buy Shipment on Primary
Leg
 Build Buy Shipment on Primary
Leg Show Consol Options
 Bulk Plan-Buy
 Direct
 Manual
 Manually Assign To Existing
Shipment
 Move Order to Existing
Shipment
 Multi-stop
 Show Routing Options
Build Shipment on Primary Leg
 Build Buy Shipment on Primary Leg and Build Buy

Shipment on Primary Leg Show Consol Options are used
when you want to book an order release on a charter
voyage or flight.
Bulk Plan
 You can bulk plan multiple

orders into shipments to
achieve optimal solutions
and consolidation Order
opportunities. Order Release-
Release- 001
002
Order
Release-
003
Multi-Stop Shipment
Direct Shipment
Direct Shipments
 Use this action to create shipments from one or more

order releases. When you create a shipment from an
order release, Oracle Transportation Management
determines the equipment group, costs, stop times, the
stop sequence, and itinerary for the new shipment.
Manual Shipments
 Use this action to manually create a shipment for order

releases and ignore the standard shipment planning logic.
Planning
Logic
Manually Assign To Existing Shipment
&
Move Order to Existing Shipment
 Use either of these actions to manually move an

order release onto an existing shipment. These
actions can be used in situations when you do not
want to invoke the OTM planning algorithm.
Multi-Stop Shipments
 This action is used to create multi-stop shipments from
order releases with different source and destination
locations.
Pickup
Stop 1
Pickup Delivery
Stop 2 Stop
Show Routing Options
 Use this action when you want to create a shipment , and
you want to review and assign an itinerary from a valid
list of itineraries generated by Oracle Transportation
Management.
Option 1
Option 2
Option 3
Option 4
Orders can be planned on priority basis
Order 1
High Priority
Order 2
Medium Priority
Order 3
Low Priority
OTM enables you to manage your
shipments
 Shipments
 Tender
 Shipment Events
Shipments represent the movement of freight
from one location to another location
A tender is a notice sent to the service
provider with an offer to move the cargo
Service providers can send information about
shipments to OTM using shipment events
Fleet Management
 Company ABC can manage their Fleet and

Contract Carriers within OTM.
Company ABC
Dedicated/Private
Contract Carriers
Fleet
Fulltime Independent
TL Carriers LTL Carriers Steamship Lines
Employees Contractors
Fleet Management
 Advantages
 OTM Fleet Management allows companies to manage their

private fleet and contract carriers on one platform.
 Allows companies to make better decisions regarding the
utilization of their private fleet.
 OTM Fleet Management covers asset management, driver
management and financial management of a company‟s
private fleet.
Fleet Management
 What kind of companies use OTM Fleet
Management?
 Companies that wish to manage both private fleets and
contract carriers.
 Companies that wish to manage orders and shipments with a
private fleet.
 Logistics Service Providers with multiple lines of business.
Fleet Management
 Manage drivers, shipments and assets using the Dispatch

Board.
 Users can drag and drop drivers to shipments to manually
assign them.
 Manage Truck, Ocean and Rail Fleets in OTM
You are beginning to understand the key
functionality within OTM
Fleet Management
Fleet Management Course Agenda
1) Introduction & Overview

2) New Fleet Business Objects
3) Equipment, Location Asset Inventory & Buckets
4) HOS (Hours of Service)
5) New Fleet Actions menus
6) Work Invoices
7) Advanced Layouts & the Dispatch Board
8) Logic Configuration
9) Agents
10) Fleet Management Student Exercises
Introduction & Overview
Documented Benefits of a Fleet Management
System
Companies using a fleet technology solution reported an average

improvement in:
 vehicle utilization of 13.0%
 vehicle downtime of 15.4%,
 operating costs of 10.4%
 average travel time per job of 14.8%
 operator compliance of 27.9%.
(Source: Service on the Move: Driving Profitability via

Fleet Management, Aberdeen Group, March 2007)
Logistics In the Coming Decade…
“The next ten years will be all about mobile

communications and real time data.”
Noel Perry
Principal – Transport Fundamentals LLC
ITLC 2010 Conference
Real-Time Information: Fleet Operations
Route & Appointment

HOS Updates Temp Sensors
Braking Patterns
Geo-Fencing
Asset
Availability
Real-Time Information: Supply Chain
Management
Inventory
Customer Service
Management
Lower
Landed
Cost
Carbon Footprint
Promotion
Execution
OTM Fleet Management
Comprehensive fleet solution that enables broader scope of operation
Manage transportation footprint on a single network

• Central control with local execution across all orders, modes, hubs
Align with overall information management strategy

• Extensible, web-native, standards-based architecture
• Maximize use of information as volume of data, number of attributes,
and number of consumers increases
Increase visibility and coordination

• Expand fleet responsiveness to order, inventory, capacity, and
customer services needs
What is Fleet Management?
 Oracle introduced the Fleet Management module with the release of

OTM in version 6.0.
 Fleet Management offers a wide variety of uses for managing an

internal fleet of “drivers”, “power units” and “equipment”.
 In addition to these fleet-specific enhancements, Oracle introduced

other new functionality into OTM which can be leveraged in Fleet and
other modules. These enhancements include:
 Advanced Layouts (used to configure dispatch boards)
 Enhanced mapping tools
New Fleet Business Objects
New Fleet Business Objects
The Fleet Module introduces us to several new business objects. Some

of these are listed below:
 Driver
 Driver Type
 Power Unit
 Order Release with Stops (Stop Sequence & Special Services mods)
 Fleet-specific Tracking Events
 Calculated Fields (used on Dispatch Boards)
 Work Invoices
Drivers
 Drivers were
configured
as part of the
day 1 team
exercises.
 If you have
not
completed
this yet, take
a moment to
complete
your driver
setup.
Driver Teams
• A key point to keep in mind for Driver Teams is that the HOS rules
associated to the primary driver are the rules that are considered when
assigning the driver team to a shipment.
• Take a moment now to create a team. Make sure that the drivers you pair
together have the same driver type.
Power Unit
 A Power Unit in Fleet is a truck that is assigned to a driver (or drivers)
 Your power units should have been generated in a previous team

exercise. If you haven‟t completed them, take a moment now to create the
power units
Equipment,
Location Asset Inventory,
Buckets
Equipment Hierarchy
 OTM provides the hierarchy shown here. At the Equipment level, the
Fleet Module can track equipment location and status throughout its life
cycle.
EQUIPMENT GROUP ROAD EQUIPMENT

PROFILE SET
EQUIPMENT GROUP 50‟ Dry Vans

PROFILE
EQUIPMENT GROUP 52‟ Vans 55‟ Vans
EQUIPMENT TYPE 52‟ Dry HAZMAT 52‟ Dry Vans 55‟ Dry Vans
SAC_001 SAC_003 SAC_005

EQUIPMENT
SAC_002 SAC_004 SAC_006
Location Asset Inventory – Location Setup
Location Asset Inventory was developed to help track driver and equipment
movement between locations, as well as their various statuses
 Location Role Setup – Equipment Pool
 Equipment Pool role indicates to OTM which locations are

considered for Fleet equipment locations and availability
 Fleet Logic Configuration Identifies the Location Role that is to be used to

identify those locations involved in the Equipment Pool.
Location Asset Inventory
 You can use special service codes on locations, service providers, and
orders. You can specify what special services must be offered by the
service provider who transports your shipment. Several of the location-
specific special service codes are shown here.
Bucket Types and Buckets
 Bucket Types are used to manage and track sets and
subsets of inventories
 Bucket Types only need to be associated to a domain
 Equipment can be linked directly to “instance” bucket types
 Instance bucket types can stand alone, or they can be subsets
of “total” bucket types
 Buckets are used to manage and track equipment,

power units or drivers at a specific location
Location Asset Inventory – Bucket Types
Bucket Types
 Bucket Types are used to manage and track sets and subsets of
inventories
 Equipment can be linked directly to “instance” bucket types
 Instance bucket types can be subsets of “total” bucket types
Location Asset Inventory – Bucket Types
Bucket Types
 In this example, total bucket type “ALL EMPTY” is the sum of “MT
ASSIGNED”, “MT AVAILABLE”, and “MT RESERVED” bucket
types. (“MT” is for “empty”).
Location Asset Inventory – Buckets
Creating Buckets
 Buckets must be associated with a Location
 Buckets must be associated with an Asset Type (* see note)
 Buckets must be associated with a Bucket Type
Location Asset Inventory – Bucket Level Types
 Bucket Level Types
Bucket Level Types allow you to set important quantity levels for your
equipment inventories. Bucket level types are user-defined. You might
create levels such as "Maximum," "Minimum," and "Reorder."
 If you select a Monitoring Type of “Maximum” or “Minimum” and the
bucket level goes above the maximum or below the minimum, then a
specified event is triggered.
 If you select a Monitoring Type of “Informational” and the bucket level is
out of its given threshold, no action is taken.
Location Asset Inventory – Equipment Actions
 Assigning Equipment to Buckets and Bucket Types:
View Inventory Summary
 The Inventory Summary shows the trailer types available at each
location, also the status types of each
 Location View Inventory Summary
 Location Asset Inventory
 Establishing a quantity for a Bucket or Bucket Type, also
associating the count with one or more Level Types:
HOS (Hours of Service)
Hours of Service HOS
 The Fleet Module provides a way to store, calculate, maintain and
optimize Hours of Service
 Driver HOS Daily Summary
 The Driver HOS Daily Summary provides a way to manually

override a driver‟s activity for a given day. These hours are then
taken into consideration as time used when determining feasibility
for future shipment assignments.
Hours of Service HOS
 Rate Service
 Periodic vs. Continuous HOS Rule
Fleet Actions Menus
Fleet Actions
Many new Actions are available in OTM as a result of the additional Fleet
business objects and their relationships preexisting OTM business
objects.
 In the next few slides we will review Shipment, Driver, and Equipment
Actions.
 Shipment Fleet Actions
 Driver Fleet Actions
 Equipment Fleet Actions
Shipment Fleet Actions
Drivers and Equipment can be Assigned to
Shipments via Shipment Actions:
 Assignments can be made regardless of feasibility and
removed as needed
 Shipment Information can be sent to a driver via Driver

Dispatch actions
 Despite feasibility, Drivers, Equipment, and Equipment Type

can all be assigned by using the Force Assign actions
 Relays can be made in order to swap equipment enroute.

The shipment can be reverted back to its original state via the
Revert Swap action
 Repositions can be generated when it is desirable to merge

or split shipments
Driver Fleet Actions
 Driver Assignment to Shipment

 Driver Positioning including NAT/NAL Override
 Driver Assignments allows you to view existing
or past driver assignments
 Driver HOS Daily Summary allows the user to
manually update HOS.
Equipment Fleet Actions
 In OTM v6.2, Equipment Fleet actions

address Location Asset Inventory and
general Repositioning
 Assignment occurs via drag and drop or
Shipment actions
Work Invoices
Driver Work Invoices
 Create a driver
work invoice for
the shipment
created during the
team exercises
 Driver Work Invoices are typically interfaced to an HR or ERP system
Advanced Layouts & the
Dispatch Board
Advanced Layout
The advanced layout uses Panel Splitters and Panel Panes to combine
multiple business objects onto one screen
 Shipment, driver and equipment actions allow for automatic

assignment and association between the objects
 “Drag and Drop” functionality can be utilized to manually assign objects

to shipments
 The advanced layouts also allow the use of screen sets and saved
queries, giving the users more defined information.
Advanced Layout
Some of the business objects that can be combined on the Advanced
Layout are:
 Buy Shipment
 Driver
 Driver with Time Phased chart
 Equipment
 Equipment Type
 Location Asset Inventory
 Order Release
 Power Unit
Advanced Layout
Advanced Layout
Dispatch Board
Configured Dispatch Board
Logic Configuration
Logic Configurations
Logic Configuration is a collection of related parameters used by the OTM
planning logic. A configuration can handle different scenarios and be
shared by different parameter sets.
 Fleet-related Logic Configurations influence how drivers and equipment
are planned onto shipments during bulk planning. The configurations
can be assigned to one or more planning parameters to be used during
optimization:
 Driver Configuration – Driver constraints & preferences
 Fleet Optimization – Fleet & Driver optimization settings
 Fleet Equipment – see details in the following slides
Logic Configuration – Fleet Equipment
Moving Equipment Between Buckets
 Logic Configuration settings will determine which buckets are
incremented and decremented as a result of having a piece of
equipment assigned to a shipment, and the status of the shipment as it
progresses on its route.
 When a piece of equipment is assigned to a shipment, the Logic
Configuration and the Special Services of the shipment locations
determines what is done with the equipment. These settings
determine when the equipment is moved among the various
buckets within the Location Asset Inventory.
 When Actions are executed, OTM will move equipment to the
appropriate bucket types, per the Logic Configuration settings
Location Asset Inventory – Assigning Equipment
Logic Configuration
 LOC INV CHECK INVENTORY BUCKET NAME (e.g. TOTAL) – the bucket type that OTM logic
will consider when making CHECK INVENTORY decisions
 LOC INV AVAILABLE BUCKET NAME (e.g. EMPTY) – the bucket type that empty/available
equipment will be pulled from for assignment
 LOC INV ASSIGNED BUCKET NAME (e.g. ASSIGNED) - the bucket type that is incremented
when equipment is assigned to a move, for each location involved in the move
 LOC INV INBOUND BUCKET NAME (e.g. INBOUND EMPTY) – the bucket type used to
manage non-drop-loaded equipment into a location
 LOC INV INBOUND LOADED BUCKET NAME (e.g. INBOUND LOADED) - the bucket type
used to track only the dropoff of drop-loaded equipment into a location*
* Note: (Bug) When Loaded equipment gets assigned to a move, it will not go into an ASSIGNED or INBOUND bucket;
instead it will go into the INBOUND LOADED bucket.
Logic Configuration – Workflow Example
 LOC INV CHECK INVENTORY BUCKET NAME (e.g. TOTAL)
 LOC INV AVAILABLE BUCKET NAME (e.g. EMPTY)
 LOC INV ASSIGNED BUCKET NAME (e.g. ASSIGNED)
 LOC INV INBOUND BUCKET NAME (e.g. INBOUND EMPTY)
 LOC INV INBOUND LOADED BUCKET NAME (e.g. INBOUND LOADED)
 Given the bucket type configuration described in the previous slide, a

typical workflow would look like this:
 When EMPTY equipment is assigned to a shipment;
 @ the Pickup Stop, the equipment being assigned
 is moved out of the AVAILABLE bucket
 is moved into the ASSIGNED bucket
 @ the Dropoff Stop, the equipment being assigned
 is moved into the INBOUND bucket
* Note: If equipment type or equipment is unassigned from a shipment, the equipment should move out
of the ASSIGNED bucket and also move out of the INBOUND bucket
Logic Configuration – Workflow Example
 LOC INV CHECK INVENTORY BUCKET NAME (e.g. TOTAL)
 LOC INV AVAILABLE BUCKET NAME (e.g. EMPTY)
 LOC INV ASSIGNED BUCKET NAME (e.g. ASSIGNED)
 LOC INV INBOUND BUCKET NAME (e.g. INBOUND EMPTY)
 LOC INV INBOUND LOADED BUCKET NAME (e.g. INBOUND LOADED)
 Given the bucket type configuration described in the previous slide, a

typical workflow would look like this:
 When LOADED equipment is assigned to a shipment;
 @ the Pickup Stop, no buckets are updated *
 @ the Dropoff Stop, the equipment being assigned
 is moved into the INBOUND LOADED bucket
* Note: (Bug) When Loaded equipment gets assigned to a move, it will not go into an ASSIGNED or
INBOUND bucket; instead it will go into the INBOUND LOADED bucket
Logic Configurations
Advanced Filters
 Advanced Filters are used for Drivers, Equipment Types and
Shipments, in order to find the best combination and improve
performance during optimization:
 Driver Example: Driver Maximum Distance to Shipment
 Equipment Type Example: Equipment Type Min Distance to
Shipment
 Shipment Example: Shipment Match Driver Retained
Equipment
Agents
Agents
Process Review:
 For fleet shipments, Location Asset Inventory leverages the
use of buckets to track asset inventories (i.e. drivers, pieces of
equipment, and power units)
 These Buckets Types are used for maintaining the status and
count of each asset at a specific location
 Throughout their lifecycle, assets are monitored and moved to
different buckets as a result of fleet management processes or
manual actions
* Note: In this section we will give an overview of the use of agents, however agents
are considered an advanced
For Oracle employees and topic
authorizedthat
partnersis covered
only. into third
Do not distribute detailparties.in another Boot Camp 110
course.
Agents
There are two ways to move equipment from one bucket to another:
1. Using the Logic Configurations, move the inventory among
OTM‟s pre-defined Bucket Types (see below) as described in
the Logic Configuration section of this module:
 Total
 Empty
 Assigned
 Inbound Empty
 Inbound Loaded
2. Create custom Agents to provide additional functionality to:
 manage these OTM pre-defined bucket types in new
ways
 manage custom inventory buckets types* that are
needed to support a company‟s business processes
Agents
Logic Configuration equipment movement example:
 When the action „Assign Equipment to Shipment‟ is performed,

OTM Logic Configuration can do the following:
 Move the equipment from one bucket (EMPTY) to another
(ASSIGNED) at the source location (to prevent it from being
considered for assignment to another shipment)
 Add the equipment to a bucket (INBOUND_LOADED) that
will make it visible to the shipment destination location
Agents
Agent logic example:
 OTM‟s Logic Configuration is not yet robust enough to manage

every circumstance that may occur regarding equipment, power
units and drivers. In such cases, custom Agents and custom
Buckets may be required. For example, Agents may help in the
following circumstances:
 You wish to create a bucket for tracking equipment that is
under repair, either at a pool location or while enroute
 You want to supplement how OTM manages the trailer
inventory for the INBOUND_LOADED Bucket Type (see
Logic Configuration notes)
 You wish to kick off other actions based on the movement of
Fleet equipment & drivers (alerts, instructions, etc.)
Agents
In order to use Agents to support a customer‟s special requirements,
keep in mind the following:
 OTM does not provide any default agents to move equipment,
therefore they would have to be developed by the implementation
professional
 OTM does not provide default equipment statuses, therefore any
equipment statuses required by an agent must be created by the
implementation professional
Student Exercises
Fleet Exercises
 Team Driver – Assign Team Drivers to a shipment
 Work Invoice – Generate a Work Invoice for the Boot Camp Multi-Stop
Shipment Exercise and the Team Drivers that have been assigned in
today‟s exercise.
 HOS - Define the HOS to be used by individual and team drivers
 Dispatch Board - Create a dispatch board that shows the following:
 Order Releases; Shipments; Drivers; Location Asset Inventory
Fleet Exercises
 Equipment
 Identify the pieces of equipment (trailers) that will be used during the fleet
exercise. *(if none, create 10 trailers)
 Assign Equipment to various buckets that are related to orders and

shipments in previous exercises
 Assign the Equipment to the Shipment via the Dispatch Board
 Logic Configuration
 Copy the default logic configuration and assign it to the planning
parameter in use
 Adjust the Fleet-based logic configuration accordingly
 Assign drivers via AutoAssignment to shipments that don‟t have drivers
Freight Settlement
OTM Freight Settlement Overview
Freight Settlement (Freight Payment) is a process made up of several

components:
 Freight Movements (i.e. executing shipments)
 Freight Payment or Customer Billing
 Cost Allocation
The Significant Business Objects for Freight Settlement are:
 Order Releases
 Buy Shipments and Sell Shipments
 Invoices and Vouchers
Process Overview
 BUY SHIPMENT
Execute the Pay Create Send to

Invoicing
Shipment Approval Voucher Accounting
• Order Release • Receive Invoice • Auto-Pay • Authorize • Pay the Carrier

• Buy Shipment (via Integration) • Match-Pay Payment (via an A/P
• Create Invoice system)
(in OTM)
Send to
INITIATE ALLOCATIONS Allocation
Accounting
INITIATE ALLOCATION
RULES • Order Level • Cost Accounting
• Order Line Level or G/L system
• Ship Unit
• Ship Unit Line
Process Overview
 SELL SHIPMENT
Execute the Bill Send to

Billing
Shipment Approval Accounting
• Sell Shipment • Review • Authorize Billing • Bill the

Customer (via
an A/R system)
INITIATE ALLOCATIONS Send to

Allocation
Accounting
• Order Level • Cost Accounting

• Order Line Level or G/L system
• Ship Unit
• Ship Unit Line
OTM provides sets of Rules (configurable to match a company‟s business
processes) to support the Freight Settlement process:
 Match Rules
 Linking Invoices to Orders and Shipments
 Approval Rules
 Comparing Shipment Costs to Invoice Costs
 Line Approval Tolerance Rules

 Comparing Costs vs. Invoice Amounts at the line level, or using dates
 Match Validation Rules

 Matching on Shipment and Order refnums
 User Signing Authority Rules

 Setting limits that a user (or role) can approve or adjust
Freight Payment
Freight Payment is associated with Buy Shipments (i.e. when the shipper
buys transportation service from a carrier). OTM provides two ways to
manage the invoicing + payment authorization cycle:
1. Match Pay
 The shipper receives invoice from the service provider
 The invoice is matched to a Buy shipment
 The invoice is approved for payment to the service provider
 The payment data is sent to an external system for payment to the service provider
2. Auto Pay
 The shipper automatically generates an invoice based on the Buy shipment
 The invoice is approved for payment to the service provider
 The payment data is sent to an external system for payment to the service provider
Match Rule Setup
 When Payment invoices are created or received (via integration) in OTM, they are
matched to existing Buy shipments. Match rules specify the criteria used to
automate the matching of payment invoices to Buy shipments.
Match Rule Setup – 6.2 enhancement
 In OTM 6.2 there is an enhancement to the Match Rule that allows the Invoice
Matching to occur even at the shipment‟s Ship Unit and Ship Unit Line levels. This is
useful for Parcel shipments where there may be several parcels on one shipment
and the invoice that is received from the service provider is only for some but not all
the parcels.
Match Rule Profile Setup
Match Rule Profiles enable us to group and sequence Match Rules.
They specify the criteria by which an Invoice can be matched to a
Shipment.
 Once a Match Rule Profile has been created , it must be assigned

to a service provider before payment invoices can be matched to
Buy shipments using the Match Rule Profile
Approval Rule Setup
Once a Payment Invoice has been matched to a Buy shipment, it
needs to be approved for payment. Approvals can be done manually
or via automation agents.
 When using the automated approval process, OTM uses rules to

determine if the amount due on the invoice and the Total Actual
cost on the shipment are within a defined tolerance range of each
other.
 OTM 6.2 enhancements to the Approval rule includes Effective and

Expiration dates.
 OTM 6.2 also has functionality to allow the Invoice to be approved

if the Total Tolerance is within limits, even though the individual
invoice lines on the Invoice may be out of tolerance
Approval Rule Setup
Approval Rule Profiles
 Auto Approval Rule Profiles enables OTM to group and sequence
auto approval rules. They specify the criteria by which a matched
Payment invoice may be approved for payment
Line Approval Tolerance Rule
The line approval tolerance rule establishes tolerance thresholds for individual
shipment cost/invoice lines
 You may specify tolerance thresholds to prevent automatic approval of invoice

lines that are too high or too low compared to the corresponding shipment cost
Line Approval Tolerance Rule Profile
 The Line Approval Tolerance Rule Profile is a collection of rules to
define line approval tolerance checks. Profiles may be assigned to
one or more service providers
Match Validation Rules
Match Validation Rules allows OTM to further validate the invoice/shipment
match by using additional reference information. These reference numbers
could be:
 Shipment reference numbers (Invoice vs. shipment)
 Order reference numbers ( Invoice vs. order on shipment)
Match Validation Rule Profile
 Match Validation Rule Profiles allows OTM to combine multiple
match validation rules in sequential order of importance to dictate
which rule should take precedence over others
Assigning Rules to Service Providers
 The freight settlement rules for allocating costs, matching invoices
to shipments and tolerances for approving the invoices need to be
added to the Service Provider in order for them to take affect.
Lab Exercise on creating Rules
Solution Design Solution Design Details
Create Match Rule - P_SCOTT_MATCH_RULE,
Match Rules use Service Provider – exact match, Match Invoice
Reference Numbers to - BM
Create Match Rule Profile -
Match Rule Profile P_SCOTT_MATCH_RULE_PROFILE ,
Include Match rule -- P_SCOTT_MATCH_RULE
Create Approval Rule -
P_SCOTT_APPROVAL_RULE, use Allowable
Approval Rule percent above and below as 1%. Use Allowable
amount above and below as $25.
Create Approval Rule Profile -
P_SCOTT_APPROVAL_RULE_PROFILE ,
Approval Rule Profile Include Approval rule --
P_SCOTT_APPROVAL_RULE
Create Line Approval Tolerance Rule -
P_SCOTT_LINE_APPROVAL_RULE, use Cost
Line Approval Tolerance Rule Type – Base allowable percent -1%, amount -$15.
Cost Type – accessorial FSC - allowable percent -
1% .
Lab Exercise on creating Rules
Create Line Approval Rule Profile -
P_SCOTT_LINE_APPROVAL_TOLERANCE_RULE
Line Approval Tolerance Rule Profile _PROFILE ,
Include Approval rule --
P_SCOTT_LINE_APPROVAL_RULE
Create Match Validation Rule -
Match Validation Rule P_SCOTT_MATCH_VALIDATION_RULE, use Order
release validation – PO, Shipment validation - PO
Create Match Validation Rule Profile -
P_SCOTT_VALIDATION_RULE_PROFILE ,
Match Validation Rule Profile Include Match Validation rule --
P_SCOTT_MATCH_VALIDATION_RULE
Assign the match rule profile –
P_SCOTT_MATCH_RULE_PROFILE , and the
Assigning the Rules to the Service
approval rule profile -
Providers P_SCOTT_APPROVAL_RULE_PROFILE to the
service providers
Setting User Signing Authority
Before a user can perform certain functions in the Freight Settlement process,
the user must be granted user signing authority in OTM
 This authority controls the maximum amounts users can manually approve
or adjust on a Payment Invoice
Invoice Status Types and Status Values
 These statuses indicate where an invoice is in the Freight Payment
Process.
Creating an Invoice within OTM
There are two ways to create a Payment Invoice directly within OTM:
 Manually create an Invoice through the OTM Payment Invoice

manager
 Create an Invoice from a Buy Shipment
Manually Created Invoices within OTM
Manually created invoices in OTM require the following information
 Consolidation Type
 Service Provider Alias Qualifier and value
 Invoice Date
 Date Received
 Other information that may be entered are:

 Invoice number
 Line Item Cost data
 Equipment information‟
 Stop information
Invoices created from a shipment in OTM
When Invoices are created from a Buy shipment via „Actions‟, the
following data is copied from the shipment to the Invoice:
 Header data
 Involved party Information
 Stop Information
 Shipment Cost information
* Note: The important point to note here is that Invoices and Shipments are
automatically matched in this process since the Invoice was created directly
from the shipment
Manually matching an Invoice to a shipment
Once an Invoice is created , it is matched to a shipment. There are two
ways to match an Invoice to a Shipment:
 Manually – via manual Invoice „Actions‟ on the payment Invoice

Actions Menu
 Automatically – using rules assigned to the service provider that

define how OTM automatically matches an Invoice to a Buy
Shipment. Automatic matching can occur via:
 Automation Agents
 By creating an Invoice directly from a shipment
* Note: It is important to note that a Shipment must have a „SECURE RESOURCES‟

value of ACCEPTED, BOOKED, or PICKUP NOTIFICATION for it to be eligible for a
match
Actions to manually match an Invoice
There are two „Actions‟ to manually match an Invoice to a shipment:
 Manually Match Invoice – this action overrides any Match rules
assigned to the Service Provider and manually matches the invoice.
 Find valid Matches – this action finds all Buy shipments that match a
selected invoice using the rules specified on the Service Provider.
Invoice Approval Process
The Invoice needs to be Approved in OTM. This will generate a
Voucher. A voucher can then be sent to an external system for
payment.
 There are two ways to Approve an Invoice:

 Manually – via Manual Payment Invoice Actions in the Payment
Invoice Actions Menu. The Approve Invoice Action overrides any rules
assigned to the Service Provider and manually approves the Invoice.
 Automatically – via Automation Agents. Rules assigned to the Service

provider define how OTM automatically approves an Invoice for
payment.
*Note: When an Invoice has been manually approved , the Invoice status value is set to
APPROVED_APPROVED_MANUAL
Invoice Approval by Total or Line Amount
The Invoice Approval process could either be by the Total Invoice
Amount or the Individual Line Amounts. This depends on the property
setting that is set on the OTM App server.
 Approve Total Invoice Amount – the Total Amount due for the Invoice is
entered on the “Amount to Pay” field. This amount may be modified if
required.
 Approve Invoice by Line – the user has the ability to approve specific
line items of an Invoice while not approving others.
Resolve Invoices that do not Auto Match
When Invoices are interfaced into OTM from an external system the
Invoices may fail to auto match. The common reasons for this are:
 OTM cannot find a service provider assigned to a Buy shipment which matches
the service provider on the Invoice
 OTM cannot find a reference number qualifier and value on a Buy shipment
which matches the Reference number qualifier and value on the Invoice.
Resolution: manual intervention is necessary to determine where the discrepancy

has occurred. Review the service provider and the reference number(s) on the
invoice and verify that
 the service provider exists in OTM
 the reference number qualifier(s) is/are specified on at least one match rule
assigned to the service provider
 the reference number value on the invoice is correct
Resolve Invoices that do not Auto Approve
When Invoices are interfaced into OTM from an external system the
Invoices may fail to auto approve. The common reasons for this are:
 The difference between the Total Amount due on the Invoice and the Total
Actual Cost on the Buy shipment is outside the specified tolerance range.
 The difference between the Total Invoice weight and the Total Shipment weight
is outside the specified tolerance range.
 In the situation where the Line Approval Rule is being used, the difference
between and individual line amount (or weight) on the invoice and the individual
line amount (or weight) on the Buy shipment for that line item may be outside
the specified tolerance range
Resolution: manual intervention is necessary to determine where the discrepancy

has occurred
 Look at both the Invoice and the Buy shipment to determine which information is
out of tolerance
Modifying an Invoice or a Buy Shipment
Once a determination has been made where the discrepancy lies, the
situation could be resolved by either:
 Modifying the data on the Payment Invoice
 Modifying the Invoice in the external system where it was created and
resending it to OTM
 Using the Invoice Manager to make the necessary changes to the Invoice
 Modifying the data on the Buy Shipment
 Editing the shipment directly
 Edit via the Buy Shipment Actions
Modifying an Invoice or a Buy Shipment
If you edit the shipment, for example;
 Change service provider, shipment route, or shipment details
then you must recalculate the shipment and copy the modifications to
the associated payment invoice:
 Use the Buy Shipment Actions:
 Assign Rate Action – this recalculates the cost of a shipment
 Invoice Adjusted Cost Action – when this action is triggered, OTM
compares Buy Shipment costs and Invoice line items and
creates a new line item to accommodate any cost changes. If a
cost is removed from a shipment, the Invoice will show a line item
with a negative amount.
Vouchers
A voucher is an authorization to pay all or part of the amount due on a
payment invoice
 Vouchers are typically created when an invoice is approved for

payment.
 A voucher is then issued (sent) to an external (Accounts Payable)

system for payment to a service provider.
* Note: When a Voucher is first created the status value is set to an initial value of
ISSUED_NOT_ISSUED. Once the voucher has been sent to external system, the value
is changed to ISSUED_ISSUED . This prevents a voucher from being modified once it
has been sent to an external system.
Lab Exercise on creating Invoices
Assign the P_SCOTT_INVOICE_APPROVAL
Setting User Signing Authority _RULE_PROFILE to PSCOTT user
Create a manual Invoice from the Order release -

Create a Manual Invoice from
WC_SAN_FRANCISCO_OR and manually
Shipment approve the Invoice. Verify the status values .
Create a new Order Release -
WC_SAN_FRANCISCO_OR_2, and build a
Create a Manual Invoice – Auto
shipment. Secure resources for Shipment. Create a
Match to Shipment manual invoice and auto match to shipment. Verify
the status values of Invoice.
Create a new Order Release -
WC_SAN_FRANCISCO_OR_3, and build a
Create a Manual Invoice – Manual
shipment. Secure resources for Shipment. Create a
Match to Shipment manual invoice and manually match to shipment.
Verify the status values of Invoice.
Use WC_SAN_FRANCISCO_OR_3 and the
shipment created from this OR. Change the
Adjusted shipment cost to adjust
shipment cost to $450. Then use the Action -
Invoice Invoice Adjustment Cost‟- to propagate this
change to the Invoice.
Auto Pay Process
Auto Pay is a way for OTM to generate payment invoices based on
Buy shipments. Auto Pay can be configured based on the specific
business process that applies to an organization. For example:
 When a shipment is created, generate and auto-pay a payment

invoice
 When a shipment arrives at the first stop, generate and auto-

pay a payment invoice
 When a proof of delivery is received from the final stop,

generate and auto-pay a payment invoice
Auto Pay Process
The requirements for using the Auto-pay process are:
 Buy shipments with shipment status value of PAYMENT_NEW
 The service provider allows automatic payment of Invoices *
* Note: The Autopay check box on the service provider‟s record must be
checked in order for the Autopay process to occur
Auto Pay Using Automation Agents
 The following is an example of triggering the Auto Pay process
when a proof of delivery is received from the final stop.
Auto Pay Using Automation Agents
 Since the Invoice is generated from a Buy Shipment, the invoice is
automatically matched to the shipment. The following Agent will approve
the Invoice leading to a Voucher being created for payment
Lab Exercise on creating an Invoice via Auto Pay

Verify that the Agent
CREATE_INVOICE_FOR_SHIPMENT exists and is
Create/verify Agent to Auto
Active. Otherwise create a new Agent that will
generate Invoice generate an Invoice when a status is received -
SHIPMENT - STATUS RECEIVED
Create a new OR -WC_SAN_FRANCISCO_OR_4
and use the shipment created from this OR. Add a
Create Invoice using the Auto pay
delivery completed status to the shipment and have
Agent Process an Agent auto create an Invoice and approve it.
Verify the status of the Invoice
Process Manager in Freight Payment
The Process Manager in OTM can be used for batch processing of
Payment Manager. The three options available are:
 Generate all auto-pay invoices – this is used to create payment

invoices from Buy shipments at specific time intervals.
 Process all invoices – this is used to automatically match and

approve invoices in a batch. The Match Rule profile is used to
match the invoices to shipments and the Auto Approve Rule
Profile is used to determine the tolerance limits for approval.
 Send Integration – this is used to send freight payment

information to an external system in a batch. This would include
invoices and vouchers.
Consolidated Invoices
A consolidated Invoice is a parent invoice that combines a group of
invoices that have the same service provider. Each shipment related to
the parent invoice has its own child invoice, which is used for invoice-
to-shipment matching.
 The parent invoice represents summary level information and links the
child invoices.
 The child invoice is similar to a standard invoice and usually provide a

one-to-one relationship between child invoices and Buy shipments
 The difference between a child invoice and a standard invoice is that:
 The value of financial consolidation type value = „CHILD‟
 The parent invoice ID is populated
Sell Shipments and Customer Billing
Sell Shipments represent the cost for shipping freight to a specific final
customer and contains orders for only one customer
 Customer billing is associated with Sell shipments in OTM.

Customer billing involves planning Sell shipments for a final
customer and billing the customer for the services rendered.
 Customer bills are OTM business objects that document payment

due from shippers and other customers
 Similar to Invoices, customer bills too could be either standard bills

or consolidated bills
 Bills can be allocated on a per order and per line item basis
 Once the bill has been approved in OTM, the information could be
sent to an external Accounts Receivable system
Cost Allocation
Cost Allocation is the process of dividing transportation-related costs
across the orders on the shipment. The costs can be the planned costs
or the actual costs.
 Cost Allocation uses Allocation Rules assigned to the service

provider, to divide the planned or actual costs of a shipment to
Order Release(s) on the shipment
 This Cost Allocation may be based on either:
 The Order Release – separate allocated cost for each Order

release on a Shipment
 Order Release Line Item – separate allocated cost for each

product line item on a Shipment
Basis of Cost Allocation
 To Perform Cost Allocation based on Planned Costs, OTM requires
 Shipment Costs on the Buy / Sell Shipment
 Allocation Rules
 Shipment Status value of ALLOCATION_SHIPMENT_NOT_ALLOCATED
 To Perform Cost Allocation based on Actual Voucher Costs

 Amount to pay on the Voucher
 Voucher status value of ALLOCATION_VOUCHER_NOT_ALLOCATED
 To Perform Cost Allocation based on Actual Cost of the Bill

 Amount due on the Bill
 Bill status value of ALLOCATION_BILL_NOT_ALLOCATED
Allocation By Weight
Order Release Order Release

(4000 LB.) ( 6000 LB. )
D Allocate Shipment Allocate

40% of 60% of
Shipment ( 10000 LB. ) Shipment
Cost Cost
Allocation Rule
Allocation Rules are sets of parameters that govern the allocation of the transportation
costs. Allocation Rules specify the type of costs (planned or actual), the basis (by order
release and by line item), the metrics, and the percentages of allocation to be applied.
 In OTM 6.2, Allocation Rules also allow for different metrics when defining base and accessorial
costs. For example, the base cost allocation may be based on weight while an accessorial cost
may be based on volume.
Allocation Rule Profile
 An Allocation Rule Profile is an ordered list of Allocation Rules that
governs how planned and vouchered (actual) transportation costs
are allocated. You can create a default Allocation Rule Profile, as
well as Allocation Rule Profiles to be applied to specific service
providers as service provider attributes.
Lab Exercise on creating Allocation Rules
Create a new Allocation Rule
P_SCOTT_ALLOCATION_RULE that will allocate
costs based on weight both at the order level as
Create an Allocation Rule well as the line level. The Allocation Rule will be for
both base cost as well as Accessorial cost. Use
FSC (Fuel Surcharge) as the Accessorial cost.
Create a new Allocation Rule Profile –
Create an Allocation Rule Profile P_SCOTT_ALLOCATION_RULE_PROFILE that
contains the Allocation Rule that was just created.
Assign the Allocation Rule Profile –
P_SCOTT_ALLOCATION_RULE_PROFILE to the
Assign the Allocation Rule to the
service providers - LA_LOGISTICS,
Service Provider „NIC_TRUCKING_OR‟ and
„OREGON_TRUCKING‟
Allocate the Shipment created earlier and verify

Verify the Allocation Rule Works that the freight cost is allocated to the order
releases.
General Ledger (GL) Allocation
 There are three steps in OTM to assign General Ledger Codes:
 General Ledger Key Component – this defines the basic types

of information to be coded. (For example, the GL code is based
on the source origin of the shipment)
 General Ledger Lookup Key – this groups and ranks the Key
component
 General Ledger Code – this is the specific details of the order or

shipment information that is associated with the code. (For
example, assign a GL code of XYZ123 when the source
location is the Sacramento DC)
General Ledger Allocation
Example to Assign GL Code XYZ123 To Sacramento DC

How GL Key Component A key component of
Location to look at
all source locations
on Order Releases
When GL Lookup Key A Lookup Key
containing the
source location
component
What GL Code A code of XYZ123
for a source location
of Sacramento DC
is assigned to the
Order Release and
Order release Line
General Ledger Allocation
Example to Assign GL Code XYZ456 To Sacramento DC and service
provider of Oregon Trucking
How GL Key A key component of Location to
Component look at all source locations on
Order Releases. Second key
looking at service provider on the
Buy shipment
When GL Lookup Key A Lookup Key containing the
source location component and
carrier
What GL Code A code of XYZ456 for a source
location of Sacramento DC and a
Buy shipment with a service
provider OREGON_TRUCKING
is assigned to the Order Release
and Order release Line
General Ledger Key Component
General Ledger Key Components are the basic building blocks of
General Ledger Lookup Keys, and General Ledger Codes. They are
split up between Orders and Shipments.
 Each General Ledger Key Component defines a type of information

that can be used to assign General Ledger codes to order releases
and order release line items, as well as to shipment costs.
General Ledger Lookup Key
General Ledger Lookup Keys organize and rank the General Ledger
Key Components that are used by General Ledger Codes. They are
split between Orders and Shipments.
 For General Ledger Lookup Keys, only one Buy-side and one Sell-
side key are allowed per domain.
General Ledger Codes
 General Ledger codes are used to allocate costs on order releases,
shipments, and payment invoices
General Ledger Assignment
 Once General Ledger codes have been created, they can be
assigned to shipments, order releases, and order release line items
using the Assign General Ledger Code actions in the Shipment
Manager and Order Manager.
General Ledger Assignment Agent
 An Agent could also be setup to automatically generate GL codes
for order releases and shipments. The following Agents listens for a
shipment being created and assigns the GL codes.
Lab Exercise on creating Invoices
Create General Ledger Key Create two new keys – SOURCE_LOCATION_KEY
Component and CARRIER_KEY
Create a new shipment GL lookup key -

Create shipment General Ledger
P_SCOTT_SOURCE_CARRIER_KEY using the
lookup key two components that were just created.
Create a new GL code „XYZ456‟ for source location

Create General Ledger Codes „SACROMENTO_DC‟ and carrier
„OREGON_TRUCKING‟.
Use the shipments that have already been created

Verify that the GL codes are and perform the Action to assign the GL codes to
assigned to shipments the shipments. Verify the GL codes on the
shipments.
Freight Settlement Agents
 There are a few standard Agents that are available within OTM
 One is the INVOICE – POST INSERT Agent. This is a PUBLIC

Agent that –
 Is used for Invoices received through Integration
 Automatically matches and approves Invoices Provided that the

appropriate Match Rules and Auto Approve Rules are created
and assigned to Service Providers
 Applies to both Standard and Consolidated Invoices
INVOICE – POST INSERT AGENT
When a Standard Invoice is received, the

Automation Agent matches the Invoice to
a Shipment and auto approves that
Invoice based on rules assigned to the
Service Provider
Send Voucher Interface Agent
 Once an Invoice is approved for payment, a Voucher is created. In most
instances, a Voucher is then sent to an external accounts payable system
for payment. This could be done either manually from the Invoice/voucher
Actions menu or via an Automation Agent
Summary and Conclusion
 Summary of Freight Settlement

 Questions and Discussions
Title of Presentation
Functional Agents Overview
Presenter‟s Name
Presenter‟s Title
For Oracle employees and authorized partners only. Do not distribute to third parties.
Automation in OTM
Course Topics
 Automation in OTM
ForFor
Oracle employees
Oracle employeesand
andauthorized
authorizedpartners
partners only. Do not
only. Do notdistribute
distributetoto third
third parties.
parties. 182
©© 2009
2009 OracleCorporation
Oracle Corporation –– Proprietary
Proprietary and
andConfidential
Confidential
Automation in OTM
Listens for Notify the

Checks Executes a
Planned & Involved
Conditions Series of
Actual Events Parties
Actions
Anticipate Analyze Resolve Collaborate
Automation Objects in OTM
 OTM Automation Objects
 Milestone Monitors*
* Milestone Monitors are not covered in this course
Automation Functions - Anticipate
Order Changes Via Integration
Or Manual Entry
OMS
Any Modification
WMS
Date
Quantity
CSR Location
Supplier
Status
Automation Functions - Analyze
Who is the Order

Owner?
Is the Order
Released?
Are there
Shipments?
What is the Shipment
Status?
Automation Functions - Resolve
Cancel Shipments
Re- Release
Re-Plan
Execute
Update Status
Automation Functions - Collaborate
Message
Update WMS
Update OMS
Email EDI/ Carrier
Email Supplier
Automation Functions - Collaborate
 24 X 7 Monitoring of Supply Chain Events
 Improved Operational Efficiency
 Better visibility on In-Transit data
 Better Analysis, Resolution, Collaboration

capabilities
Automation Agents
Automation Agents Basic Workings
Automation
Agents
Actions
Events in
Business
Object
lifecycle
Automation Agent Design Steps
1
2
Identify the
Business Object
3
Identify the event
4
List actions to be
performed
List actions to be
performed when
error occurs
Automation Agent Definition - Header
 Identify the Object
 Identify the Triggering Event
 Identify the Triggering Event

 For certain Events, you can specify Event Restrictions. Clicki
the button to enter more details for the event.
 Integration- the event occurs as a result of Integration.
 Internal- the event occurs as a result of standard workflow processing in
OTM.
 User – the event occurs as a result of an user performing an action via the
UI.
 Specify Filtering conditions and security

restrictions
 An agent always checks the business object for
a Saved Condition.
 Threshold is also like an additional saved
condition that can be used to specify the
modification limits for weight and cost.
 The User Role allows an action requested by
one user to be executed with the data security
of another.
Automation Agent Definition - Actions
 Define Actions
 Click Add Action Button
 Data Type Association

 An agent associated with a business object can perform an
action for another business object. For example, an agent is
configured for a shipment. Using the data association, we
can have all related order releases perform an action when
this shipment agent is triggered.
Automation Agent Definition - Error Handling
 Define Actions on Error
 If there is an error during the execution of the

agent, what do you want to do?
 Notifications are commonly used as error handler
actions
Automation Agent Standards
 Group all actions to be performed on any one event (e.g.

tender decline, shipment failed to plan, etc.) into one agent
 Always use Error Handlers
 It is usually better to use Saved Conditions; this stops
unwanted actions from being performed in the initial stage
 Saved Queries to be optimized
 Use Direct SQL updates with caution
 Write and call PL/SQL procedures to handle complex logic
Walk-Thru Session
Simple Automation Agent - Configuration
 Navigate to:
 Business Process Automation > Agents and Milestones >
Automation Agent > Click on New
 Set the indicator to Yellow

 Use the Data Association to set the Indicator to
Yellow for the Order Release
 Set the indicator to Red for the Shipment if

there is an error
Simple Automation Agent -
Configuration
Student Exercises
 Create 3 new Automation Agents:

1. Create an agent to set the order release indicator to „red‟ if it
fails to plan. The agent name should be:
ORDER_RELEASE_FAILED
2. Create an agent to copy all Order Release Refnums to the
Shipment when the shipment is created. The agent name
should be: COPY_ORDER_RELEASE_REFNUMS.
3. Create an agent to create an invoice when a „Delivered‟ event is
entered for a shipment. The agent name should be:
CREATE_INVOICE_FOR_SHIPMENT.
 The Event can be either (but NOT both):
 ORDER-FAILED PLAN BUY SHIPMENT, or
 ORDER-STATUS CHANGED /
INTERNAL,PLANNING_PLANNED-FAILED
Note - When an Order Release fails, it’s status changes to
“FAILED”. The “INTERNAL” identifier is used because the status
change is triggered by an OTM workflow.
 The only action required is to set the indicator to

red
 Remember to add an Error Handler action to

help you manage and troubleshoot agent
issues
COPY_ORDER_RELEASE_REFNUMS
 In the Event Restrictions field, only “INTERNAL” is
selected. Since we are creating Shipments using an
action in OTM it is considered standard workflow
processing.
 Add the action “COPY REFNUMS TO SHIPMENT” and
use the Associated Object of: SHIPMENT TO ORDER
RELEASE
 Leave the From and To Refnum Qualifier fields blank
in order to copy all Refnums
 Once again, don‟t forget to add an action to

the Error Handler
CREATE_INVOICE_FOR_SHIPMENT
 The Event is: SHIPMENT STATUS-RECEIVED /

DELIVERED
 Add the action “GENERATE INVOICE”
 Add an action to the Error Handler
Testing Agent Configuration
 Copy the Order Release Labeled:

TEST_AUTOMATION_AGENTS
 Your new Order Release Name should be:
 “YOURDOMAIN”_TEST_ORDER
 (e.g. “CORE001_TEST_ORDER”)
 Create a Buy Shipment

 Use the Order Release Action:
 Operational Planning > Create Buy Shipment > Direct
 Click “OK” to create a Direct Shipment
The action should have failed:

 Refresh your screen to see if the indicator for your
Order Release is red
 The agent ORDER_RELEASE_FAILED should
have triggered the color change on the failed order
 Edit the Order Release and change the destination

location to LOCATION_3.
 Save the information and build a Buy Shipment again,

using the Use Order Release Action:
 Create Buy Shipment > Direct
 Click “OK” to create a Direct Shipment
 Edit the new shipment and check the reference numbers

at the bottom of the Identification tab
 The Reference Number Qualifier “DIVISION” should have
copied from the Order Release to the shipment
 Select the new shipment and perform the

following actions to Tender the shipment to the
carrier. You will accept the tender on behalf of
the carrier.
 From the Shipment Actions Screen:
 Shipment Management > Tender> Secure
Resources
 Shipment Management > Tender > Accept
Tender
 Now we will enter a shipment event of “Delivered” to test

the last agent.
 From the Shipment Actions Screen, select:
 Shipment > Events > Add Shipment Event
 Select the Delivery Stop on the shipment (Stop #2) and enter a
date of next Monday. Click “Save” at the bottom of the
screen.
 Enter the Status and Reason information as shown below:
 Go to:
Financials > Payment Invoice Management > Payment
Invoice
 Click the search button to display the Invoice
 The Invoice creation was triggered by the agent:
Multi-Stop/Fleet Scenario
Course Structure
226
Course Structure – Overview
Multi-Stop Business Scenario
Understanding and Creating Understand Importance of

Business Requirements Business Requirements
Solution Based on
Business Requirements
Configuration of OTM
227
What is your Role in this Project?
Understand the
Business Scenario
Business Scenario
Create Business Requirements
Map-Solution to Requirements
Create Solution Based on

Configure OTM
228
Business
Scenario
229
Current Business Scenario
TL
Northern California
DCs Redding
Store
TL
TL Sacramento Store
TL TL
Fresno Store
San Francisco Modesto Store
Store
P Scott has divided their network into Northern and Southern California.
The Northern California DCs are responsible for 5 stores in the northern
section of the state. The Sacramento DC is the only DC currently using the
company fleet.
230
TL
Bakersfield
Southern California Store
DCs
TL
Los Angeles
TL Store #2
TL
TL
TL
Los Angeles
Store #1
Santa Barbara
Store
San Diego Store Santa Clarita
Store
The Southern California DCs are responsible for 6 stores in the southern
region of the state.
231
Business Scenario:
P Scott Furniture’s expected benefits from OTM
Benefit Benefit Description
Consolidating cargo movement by optimum utilization of

Leveraging cost the service providers, equipment and scheduled
delivery
Optimal Utilization OTM to plan and optimize the cargo movement on the
West Coast
Visibility Track the finished goods being transported to DC‟s
Automate the below mentioned processes
Shipment
Automation Tender
Notification
Freight Settlement
232
Business Requirements:
Objectives
Functions Required for the Project Elements Required for the Project Needs to be Accurate, Detailed, Clear
Gathering the Requirements
Documenting the Requirements Analyzing the Requirements
Topics Covered
Security Locations Freight Settlement
Items and Commodities
Order Management Automation

Service Providers
Shipment Execution Equipment Visibility
Rates
Fleet Management
Itinerary
Security / Orders / Shipments
(List some of the questions needed for a successful OTM Implementation)
Business Requirement Business Requirement Details

Number of Users
Security Access and Access Level to Distributors
Access to Service Providers
Order Capture
Order Management Quantity of Orders
Reference Numbers on Orders
Consolidation of Orders for Shipment
Cut-off times for Orders

Shipment Execution
Route Selection
Notifications
Master Data
Number of Distributors
Location of Distributors
Distributors/Locations
Frequency of Cargo to the each location
Grouping into Regions
Details of Items
Number of Items
Classifications
Item Packaging Details
Number of Service Providers
Selection Criteria
Service Providers Notifications

Constraints in Contracts
Modes of Transport
Types of Equipment
Equipment Capacity of Equipment

Classification and Grouping of Equipment
Master Data
Basis of Rates
Modes of Transport for Rating

Rates
Constraints in Contracts
Validity of the Contract
Schedules Involved with Shipment
Route taken for Delivery

Itinerary
Mode of Transport and Equipment used in
Deliveries
Visibility / Financials
Notifications on Shipment Events

Visibility
Cargo Status
Mode of Invoice Receipt from Service Providers
Invoice Matching to Shipments

Freight Settlement
Invoice Approval
Voucher Creation
Business Requirements Detail:
Security
Security
Security
What access is given to users
How many domains

Security
What can the users see
How many different types of users
Domain structure
Order Management
(List some of the questions needed for a successful OTM Implementation )
Order Management
Order Management
How will orders be entered
Order volume (daily, weekly, monthly)
Any Order Priorities

Order Management
What do the dates represent on the Order
Any special naming convention for Order
Any reference numbers or remarks needed
Any involved parties needed on the Order
Shipment Execution
Shipment Execution
Shipment Execution
Consolidate orders for shipment execution
Shipment naming convention
Tender process
Service provider notification on shipment to be

Shipment Execution picked up
Communication method to notify stakeholders
on shipment status and shipment events
Optimum route selection for shipment planning
Cut-off for orders to be planned into shipments

Criteria for consolidating the orders for shipment
creation
Master Data
Locations
Master Data
Constraints for the location
Location naming convention
Location of DC‟s and Stores

Locations
Work Times of DC‟s and Stores (Calendars)
Regions for DC‟s and Stores
Contacts
The number of DC‟s and Stores
Master Data
Service Providers
Master Data
The number of Service Providers
Any Preferred Service Providers
Selection Criteria
Service Providers Notification method
Primary contacts for tendering
Modes of transport offered
Capacity limits
Naming convention
Master Data
Fleet Management
Master Data
The number of drivers/units
Fleet Management Selection criteria
Locations using company fleet
How will fleet be dispatched
Master Data
Master Data
Number of Items
Naming convention for Items
Weight and volume of Items

Item classification
Compatibility issues for items to be shipped

together
Packaging of Items
Relationship between items and packaging
items
Master Data
Equipment
Master Data
Types of equipment that will be used
Grouping of the equipments with similar

attributes
Equipment
Capacity of the equipments
Classification of equipments
Naming convention for Equipments
Master Data
Rates
Master Data
Specific contracts with Service Providers
Contracts based on transport mode
Validity of the contracts

Rates
Geo Hierarchy of the contracts
Basis of the rates that is agreed upon (Per

Shipment, Weight/Volume, Equipment)
Preferred rates for particular service provider
contracts
Naming convention for the rates
Financials
Freight Settlement
Financials
Naming convention for invoices
Consolidated or stand alone invoices
When is invoice created

Freight Settlement
Invoice approval for payment
Any tolerance limits for Invoices to be approved
Voucher creation after invoice approval
How to handle exceptions
Solution Design
Solution Design:
Objectives
Solution Design - a high level design report
How to Implement Requirements Defined into Solutions Gives Data Flow on

Business Requirement to Enable Configuration how Solution will look like
Review
Solution Design and
Configuration Documents
Data Management Using CSV
Course Structure
 Data Management overview
 Import data using CSV
 Export data using CSV
Data Management Overview
Data Management Overview
Service Provider
Location
Item
$ #
Rate
Data Management – Using CSV
CSV Files OTM DB Tables
Advantages of Using CSV
 Fast data upload compared to data entered from GUI
 Easy to prepare compared to XML
 Large volume of data can be upload at a time
CSV File Structure
CSV files should be opened in Microsoft Excel

First line - Contains the Table Name
Second Line – Column names to be uploaded
Third Line – Optional – Contains format for date fields in the data
From Fourth Line – the data is entered, each column should contain data specific to the column
specified in the heading
CSV Guidelines
 All Data - Specified in UPPERCASE
 Data upload using CSV does not trigger OTM events
 Foreign key tables to be uploaded first
 Comma in data to be specified within “Double quotes”
OTM Data Dictionary
The OTM Data Dictionary is a reference database of every database
table and object. The data dictionary defines every relationship for the
OTM RDBMS.
It is important to understand any possible foreign key relationships
regarding any data that you wish to upload into OTM. When uploading
multiple tables of related data, the tables must be loaded in the proper
order so that foreign key constraints are not violated.
 Oracle includes the Data Dictionary as part of the installation
package
 Depending on the OTM installation, you may be able to view the
Data Dictionary on line:
 In the OTM URL bar, after the server name, delete all the text
and specify /html/data_dict
 e.g. “http://otm62test.com/GC3/html/data_dict”
OTM Data Dictionary
 Left Pane of data dictionary displays the complete list of OTM tables
 Right Pane displays the Field list of selected tables and field descriptions
 Table linked to the selected table is also displayed below.
 „I‟ icon – click on it and the details are displayed in the lower pane.
 Star – Mandatory field
Lab Exercise
Lab Exercise
In this exercise we will:

 Create a CSV by exporting an existing contact
 Import a new contact into OTM using the new
template
Export Data Using CSV
Export Data Using CSV
Export Single CSV

File
OTM DB Tables
Export Multiple CSV Files
Export a Single CSV File
 Navigate to Business Process Automation > Data Export > CSV
Export
Export Object Type: How do you want to

export the data. (Table, Set of Tables or Using
SQL Query)
Output Destination: Where do you want the
data placed. (Browser, File on WebServer or
Remote Instance)
Run Job in Background: Choose whether to
run the process in the background.
Use Select List: Export data from a list you
have already created.
Export Single CSV File – Select the Table
For this exercise choose

the CONTACT Table
Name.
Choose a Command from the drop-down list:

XCSV- One CSV file only
XCSVWPCD- CSV files with parent and child data
XCSVWPD- CSV files with just parent
XCSVWCD- CSV files with just child data
You can further define what to export by using the Where Clause field
Click Run to export the CSV
Data Export Result
Internet Explorer users:

Right Click on your mouse and select View Source
File>Save As> “CONTACT.CSV”
Firefox users:
Right Click on your mouse and select View Frame>View Frame Source
Highlight the text starting with (green text) “CONTACT”, and ending just before the green “—>” symbol.
Right mouse click and select Copy. Open a new Notepad document and paste your CSV into the document.
File>Save As> “CONTACT.CSV”
Data Export Result
Open the MS Excel files to view the contact information.

This will be used as a template for importing a new CSV.
Clean the exported CSV by removing the Columns: INSERT_USER, UPDATE_USER, INSERT_DATE,
UPDATE_DATE. Click Save to save your new template.
Data Export Result
Students should perform the same process for the

CONTACT_COM_METHOD table:
 Export CONTACT_COM_METHOD table
 Save the file as a CSV file
 Remove the columns that aren’t needed
Prepare CSV File for Import
 Prepare a Contact CSV from an MS Excel spreadsheet.
 We will need to identify what other tables link to the

Contact table.
 Prepare CSV for other table(s) that link to Contact
Contact CSV Template
Enter the following information into the Contact CSV Template:
CONTACT_GID COREXXX.ORACLE_CONTACT
CONTACT_XID ORACLE_CONTACT
FIRST_NAME STEVE
LAST_NAME HOODMAKER
JOB_TITLE VICE PRESIDENT
EMAIL_ADDRESS STEVE@ORACLETEST.COM
Click Save to record the new information for the Contact
Contact Comm. Method CSV Template
Enter the following information into the Contact Com Method CSV Template:
CONTACT_GID COREXXX.ORACLE_CONTACT
COM_METHOD_RANK 1
COM_METHOD_GID EMAIL
EXPECTED_RESPONSE_TIME 86400
EXPECTED_RESP_UOM_CODE S
EXPECTED_RESP_CNV_BASE 86400
The CONTACT_GID must be exactly like it was spelled on the Contact CSV. If it is
different, the system will not recognize this line in the CSV. Click Save to save
your new information.
Import Data Using CSV
Upload Single CSV

File
OTM DB Tables
Upload Multiple CSV Files
When uploading CSV into OTM, you can load one CSV at a time or load multiple
CSVs at the same time using the CSVUTIL functionality in OTM.
Upload the CSV Files into OTM
 Navigate to Business Process Automation > Integration > Integration Manager > Upload a
CSV/XML File
 Click Browse to select the CSV you created.
 The CSVs must be loaded in this order:
 CONTACT
 CONTACT_COM_METHOD
 Click Upload
Select IU from the Command dropdown.

 iu- Insert/ Update; attempts to Insert first, if record exists it
updates the record.
 i- Insert Only
 ii- Insert data, while suppressing unique key constraint
violations.
 u- Update Only
 uu- Update data, while suppressing “no data found”
constraint violations
 d- Delete
 dd- Delete data, while suppressing “no data found”
constraint violations
 Click Run to upload the CSV file
A successful CSV upload is identified when

there is “0” in the ErrorCount field and your
ProcessCount is what you expected to
upload.
After loading the CONTACT CSV, the

CONTACT_COM_METHOD CSV should be loaded
using the same process.
Verify the data in OTM
 Navigate to Business Process Automation > Communication
Management > Contacts
 Enter ORACLE_CONTACT in Contact ID field and click Search
Import using CSVUTIL
CSVUTIL allows the user to consolidate all the CSVs into a Zip file for a single upload
• CSVs are prepare as normal
• A command file is created and named “csvutil”
• All the files are consolidated into a zip file
Modify the 2 CSVs (CONTACT and CONTACT_COM_METHOD)

 Change the CONTACT_GID for both CSVs to:
 COREXXX.ORACLE_CONTACT_2
 Change the CONTACT_XID for the CONTACT CSV to:
 ORACLE_CONTACT_2
 Save both files
To create a Command File:

Open up Notepad
The format is:
-dataFileName CSV FILE NAME.CSV –command TRANSACTION CODE(iu , i, u, etc…)
List the CSVs in the order they should be uploaded. (Contact and then Contact Com Method)
Save the file as “csvutil.ctl”
 Consolidate all 3 files into a single Zip file
 Upload the Zip file using the same upload method as a single CSV
 When using CSVUTIL, OTM sends a results file of the upload. Select Save File and
save it to your computer
 Open the results Zip file and view the results. This contains the same
information that was visible on the screen when uploading a single CSV
 View the new contact in OTM to verify the CSVs loaded correctly
Data Management Summary
 Import/ Export large volume of static OTM data using CSV
 One CSV file corresponds to one table in OTM
 csvutil utility is used to import/export multiple CSV files
Multi-Leg
The Multi-Leg Scenario is a Team Activity. This

scenario is designed to be very challenging for the
class. The scenario includes the Business
Requirements and Solution Design Documents. The
teams are responsible for developing the configuration
based on the information in these 2 documents. The
following slides will provide very helpful information
involving the configuration needed. At the end of the
activity, each team will present their design solution to
the class……….
Good Luck!
P Scott Furniture Multi-Leg Scenario
Multi-Leg Business Scenario
Understand and Determine Understand Importance of

Business Requirement Business Requirement
Solution Based on
Business Requirement
Configuration of OTM
What is your Role in this Project?
Understand the
Business Scenario
Business Scenario
Understand and
Create Business Requirement
Map-Solution to Requirement
Create Solution Based on

Configure OTM
Business Scenario
Business Scenario - P Scott Furniture’s expected
benefits from OTM
Benefit Benefit Description
Consolidating cargo movement by optimum utilization of

the service providers, equipment and scheduled
Leveraging cost delivery, cost benefit by using deferred service where
appropriate
Optimal Equipment Utilization OTM to plan and optimize the cargo movement to
Japan thus bringing down the cost of cargo movement
Track the finished goods being transported

Shipment Visibility Internationally
Automate the below mentioned processes:

•Shipment
Automation of Business Processes •Tender
•Notification
•Freight Settlement
Business Requirement - Objectives
Functions Required for the Project Elements Required for the Project Needs to be Accurate, Detailed, Clear
Gathering the Requirements
Documenting the Requirements Analyzing the Requirements
Business Requirement – Topics Covered
Security Locations Automation
Order Management Visibility
Service Providers
Shipment Execution Equipment
Rates
Itinerary
Solution Design
Solution Design - Objectives
Solution Design - A high level design report
How to Implement Requirements Defined into Solutions Gives Data Flow on

Business Requirement to Enable Configuration how Solution will look like
Business Solution – P Scott Furniture Corp Multi-leg
Configuration Help for
the Students
Solution Design – High Level View of OTM Objects used for West Coast Delivery
Purchase Orders from the Hiroya Order Releases manually entered by OTM Shipment(s)
Co Ltd sent by FAX / E-Mail Planner Orders Consolidated – Multi-Leg shipment
Ship Units calculated from the OR Line (s) created in OTM
quantities and Packaging Data
Order 1 Order DC 1
Order 2 Order DC 2 Shipment Created
Order 3 Order DC 3
OTM Shipment TL or LTL, Ocean or Air
Purchase Orders from Hiroya, OTM Order Releases contains - Source Location
Japan contain - Destination Location
- Source Location - Packaged Item
- Item - Destination Location - Order Quantity
- Order Quantity - Packaged Item - ETD and ETA
- Delivery Date - Order Quantity - Mode for Each Leg
- Location - Late Delivery Date (Cargo Required - Service Provider
- Priority Date) - Cost
- Priority
- Ship Unit - Ship Unit
- Ship Unit Weight - Ship Unit Weight
- Ship Unit Volume - Ship Unit Volume
- Bill of Lading Number
Solution Design – Distributors / Locations
Master Data

Portland Port, Nagoya Port, Kobe Port, San
Location of Ports and Airports Francisco Airport, Narita Tokyo Airport, P Scott
Furniture Corp
Location of Distribution Centers in

Tokyo, Nagoya and Osaka
Japan
Japan Locations grouped into region - to create
Regions Rates and Itineraries
Calendars will be attached to give the working

Calendars hours of the Japan Distribution centers
Contacts attached to Locations to receive the

Notification notifications
Naming convention - respective DC Location

Naming Convention names followed by _HIROYA followed by „_DC‟ for
example TOKYO_HIROYA_DC
Configuration – Distributors / Locations
Configuration Objects Configuration Details
Create nine Locations
1. USPRT – Port of Portland
2. JPNGO – Nagoya Port
3. JPKBE – Kobe Port
4. USSFO – San Francisco Airport
Locations 5. JPTYO – Tokyo Airport
6. TOKYO_HIROYA_DC
7. NAGOYA_HIROYA_DC
8. OSAKA_HIROYA_DC
9. P_SCOTT_FURNITURE_CORP
Select role
- PORT for Sea ports
Role - AIRPORT for Airports
- SHIPFROM/SHIPTO for DC‟s and P Scott Furniture
Create Cyclical Calendars for each Location
Calendars
Attach the calendars to the respective Locations
Contact Create a contact and attach to each location
Create a Region HIROYA_JAPAN_REGION

Region
Attach the Locations to the Region
Solution Design – Service Providers
Service Providers Three Service Providers – for moving cargo to Japan
Preference One Service Provider - Preferred Carrier
Respond to Tender using On-line Booking and

Tender Response Tendering
Access to OTM Service Provider given access – SERVPROV Domain
Primary contact attached to Service Provider to receive

Contact/Notification the notifications
Calendar Service Providers have working hour Calendar attached
Naming convention – Service Provider Name followed

Naming Convention by _INT
Configuration – Service Providers

Create three Service Providers
1. BX_INTERNATIONAL_INT
Service Providers
2. PAN_FREIGHT_INT
3. AR_XPRESS_INT
Create a Primary contact and give Message Centre as

Contact Communication Method
Create a Cyclical Calendar with work timings 8am to

8pm
Calendars
Attach the calendar to the Service Provider
Solution Design – Schedule
Master Data

Vessel Schedule will give the schedule of the
Vessel Schedule Ocean Vessel movement
Schedule with shorter transit but more expensive,

Vessel Schedule - Express will be moved via Nagoya Port
Schedule with longer transit but less expensive, will

Vessel Schedule - Deferred be moved via Kobe Port
Air Schedule will give the schedule of the Air

Air Schedule movement from San Francisco (SFO) Airport to
Tokyo (TYO)
Configuration – Schedule
Master Data

Create multiple Express Vessel schedules for
Vessel Schedule - Express respective by creating Service Provider Profile
Transit time of the Schedule will be 2 weeks
Create multiple Deferred Vessel schedules for
Vessel Schedule - Deferred respective by creating Service Provider Profile
Transit time of the Schedule will be 3 weeks
Create one Air Schedule for AR_XPRESS_INT with

Air Schedule movement for 5 days of the week – MO,TU, WE,
TH, FR
Solution Design – Items and Commodities
Items List of items that needs to be created
One Packaged Item for each Item that is

created
Packaged Item Select the packaging details in the packaging

item
Enter the TiHi information in the packaged item
Naming Convention Commodity ID (DINING_TABLE_FURNITURE)
Configuration – Items and Commodities
Create the list of ten Items
Items
Create a packaged item for each item with appropriate
weight volume
To auto calculate the number of ship units to be used

Auto Calc Ship Unit to ship enter the TiHi information in the packaged item
section
Items in the format of Item name_Commodity ID
Naming Convention (DINING_TABLE_FURNITURE)
Solution Design – Equipment

Two equipment groups will be created for the two
Equipment Group different container types in use.
1. 40FT Trailers for 20FT Trailers LTL movements

2. 40FT HQ and 20FT HQ for TL and Vessel
movements
3. 2 TON Pallet for Air Shipments
Equipments 1. Maximum volume of 50CBM for 40FT Trailer
and 20CBM for 20FT Trailers
2. Max volume of 50CBM and 25TON for 40FT HQ
and 25 CBM and 25TON for 20FT HQ
3. 2 TON for 2 TON pallet
1. OCEAN_CONTAINERS for Ocean Containers

Equipment Group Profile 2. AIR_PALLET for Air Equipment
3. INLAND_TRAILERS for LTL movement
Configuration – Equipment

Create an equipment group for the following:
1. 40FT Trailers and 20FT Trailers for LTL
movements
Equipment Group
1. 40FT HQ and 20FT HQ for vessel movements
2. 2 TON Pallet for Air Shipments
Create an Equipment group profile

• OCEAN_CONTAINERS for Ocean Containers
Equipment Group Profile and TL inland movements
• AIR_PALLET for Air Equipment
Solution Design – Rate Service – Transit Time

1. A Vessel schedule needs to be created for
calculating transit time for the Ocean Leg of the
shipment
2. An Air schedule needs to be created for
Ground Schedule calculating transit time for the Air leg of the
shipment
Create a Voyage Service Type for the Ocean

schedule to be attached to the Rate Service
The rate service is a mandatory object on the Rate

Offering, when specifying a rate service on the Rate
Record, it will override the Rate Service that is
populated against the Rate Offering
1. Rate Service of type VOYAGESCHEDULE will

Rate Service be created for ocean
2. Rate Service of type AIRSCHEDULE will be
created for Air
3. Rate Service of type LOOKUP will be created for
LAND
Configuration – Rate Service
Create the necessary Voyage and Air Schedules
Ground Schedule
Give the same Voyage Service Type for all the voyage
schedules to be attached to the Rate Service
Crete one Rate Service of type VOYAGESCHEDULE,

AIRSCHEDULE and LOOKUP for Ocean, Air and Land
Rate Service Attach the Voyage Service Type for the Ocean Rate
Service, for LOOKUP create a lane and attach that to
the Rate Service Details
Attach the Rate Service to the Rate Offerings to be

Rate Offering created
Solution Design – Contracts – Rate Offering
One Rate Offering will be defined for each mode of
Transport service offered
1. Service Provider followed by _Mode of Transport
Rate Offering followed by _INL for the origin and destination
inland movement.
2. Service Provider followed by _Mode of Transport
followed by „_INT_Ocean‟ or Air for the Ocean and
Air movement
Rate Offering type will be TL or LTL or Vessel or Air for
Offering Type the different types of the rate offerings to be created
TL or LTL or Vessel CO or Air for the different types of
Offering Transport Mode Rate Offering
Will contain the Rate Service created for the LOOKUP
Rate Service for TL and LTL, VESSELSCHEDULE for Vessel and
AIRSCHEDULE for Air
Exchange Rate Exchange Rate ID will be set to DEFAULT
Rate Distance Rate Distance ID as LOOKUP ONLY
Configuration – Rate Offering
Three Rate Offerings for the three Service Providers

Rate Offering
One each for TL, Vessel and Air for each service
provider
Offering Type Select Rate Offering type will be TL or Vessel or Air
Offering Transport Mode Select TL or Vessel or Air for the rate offerings
Rate Service Enter the rate service ID created earlier
Exchange Rate Select DEFAULT
Rate Distance Enter Rate Distance ID as LOOKUP
Solution Design – Rate Record
Each Rate Record will belong to a Rate Offering

Rate Record
Can contain multiple rate records for a single offering
Service Provider ID_Mode of Transport_Origin_

Naming Convention Destination
Four location-to-location type

Rate Basis Two location-to-Region type
Rates will be defined as in the Solution Design

Rate Cost Document
Configuration – Rate Record
Create Nine Rate Records for TL, Vessel and Air for
the corresponding Rate Offerings for each Service
Rate Record Provider
Create three Rate Records for LTL for the
corresponding Rate Offerings
For Inland Cost Origin –
USD 500 for 20 FT HQ (TL)
(OR)
USD 900 for 40FT HQ (TL)
For Ocean Cost -

USD 3000 for 40FT HQ for 50 C UM
(OR)
USD 2500 for 20FT HQ Container
Rate Cost
For Air Cost - Minimum – USD 100
USD 3.5 – 0-100 kg
USD 3.0 – 100-300 kg
USD 2.5 – 300-500 kg
USD 2 – 500-2000 kg
For Inland Cost Destination –
USD 100 / 1 TON
(OR)
USD 100 / 1 CU M
Configuration – Rate Record - OCEAN
Configuration – Rate Record - AIR
Solution Design – Itinerary

Define the basic attributes for itineraries such as an ID
and name, buy perspective, and geographic elements
Parameters Check the Deconsolidation Pool and Match Deconsol
Pool to Destination
1. Define the Geography that the Itinerary is going to

be servicing:
Lane Definitions • P_ SCOTT_FURNITURE to
HIROYA_JAPAN_REGION
Define the details for each leg of the shipment like

Itinerary Legs Mode, Equipment Group Profile, Consolidating
equipment.
Configuration – Itinerary

1. Create two Multi-leg itineraries – Ocean and Air
2. Give the Geo-hierarchy for the Itinerary (i.e. from
Parameters Location to Hiroya Japan Region)
Check the Deconsolidation Pool and Match Deconsol
Pool to Destination
1. Enter the following:
Lane Definitions • P_ P_SCOTT_FURNITURE in the Location field
Define three legs for the Multi-Leg shipment as defined
Itinerary Legs in the following slides
Configuration – ITINERARY - OCEAN
Configuration – ITINERARY - AIR
Solution Design – Order Capture & Shipment Creation
Solution Design – Order Capture

Preliminary discussion takes place between P Scott
Planner and Hiroya Co Ltd, Japan to refine order
quantities and agree on production schedule and
delivery dates
Order Entry
This is done using e-mail
Once the order is „agreed‟, it is entered manually using

Order Release Template
Cargo will be consolidated at P Scott Furniture, moved
to the port and consolidated into a container load and
moved to Japan to be delivered to different distribution
centres
Order Release Adhering to the OTM Project decision to model one

Shipment per TL movement
Multiple orders if will be consolidated into one
shipment to the different distribution centers of Hiroya
Co Ltd in Japan
Solution Design – Shipment
Shipments will be planned in OTM for multiple orders
be consolidated into one shipment
Shipment This bundling feasibility will be done using the
weight/volume of the orders that can be consolidated
together
Shipments will be planned in OTM using the rates and
itineraries available in OTM
Shipment Bulk Plan
Bulk plan will group the orders to be bundled together
using the defined criteria
Each shipment tendered automatically to the selected
service provider in OTM
Shipment Tender
Carrier will either confirm or decline the booking by
viewing the shipment in the SERVPROV login
The next step in the process is to perform the pickup
Shipment Event of the cargo and updated the event in OTM which will
send a notification to the involved parties
Solution Design - Planning

Automatic planning takes place by means of
scheduled background job or by setting up a workflow
Automatic Planning that triggers planning based on an event
Scheduling the bulk plan at 7pm of every 2nd and 4th
Wednesday to enable loading on the Sunday Vessel
A user logging on to OTM and selecting order releases
for planning will perform manual planning
Manual Planning
To aid the user in selecting orders for planning, saved
queries can be created
The planning parameters will need to be changed from
their default setting
Planning Parameters
Planning parameters are included in the Planning
Parameter Set PSCOTT
Solution Design - Shipment Execution
Planner selects one or many Order Releases and
creates a Shipment
A shipment describes how and under what conditions
Shipment (rates) an order can be shipped
In OTM, all TL , LTL, Ocean and Air contracts have
been set up and will be used to create the shipments
Each shipment tendered automatically to the selected

service provider in OTM
Shipment Tender
Carrier will either confirm or decline the booking by
viewing the shipment in the SERVPROV login
The next step in the process is to perform the pickup
Shipment Event of the cargo and updated the event in OTM which will
send a notification to the involved parties
Key Content Contributors
Contributing Companies
1 - 344 © 2008 Oracle Corporation – Proprietary and Confidential
1 - 345 © 2008 Oracle Corporation – Proprietary and Confidential

Course Presentation-OTM

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Course Presentation-OTM

Hochgeladen von

Copyright:

Verfügbare Formate

1-1 © 2008 Oracle Corporation – Proprietary and Confidential

The following is intended to outline our general

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any

OTM 6.2 Functional Implementation Boot Camp

 Designed for Consultants who will implement OTM

 Participants should have an understanding of OTM and Logistics

 Participants will learn the basic configurations of OTM 6.2

 Participants will also receive “Hands-on” Training via:

 Multi-Stop, Multi-Leg, and Freight Payment Scenarios

 Fleet Management, Data Management, and Agent Configuration

Default Permissions for each domain to the others is:

BLUEPRINT S READ “Company X”

Go to Configuration and Administration > Domain Management >

Create a subdomain (child) to the COREDEMO domain, named COREDEMOSUB1; go to

 While OTM is in the process of creating

 Menus are typically customized to

Rate Distance Rate Service

Rate Record Rate Record Rate Record

 Rate Distance determines the distance from one location

Equipment Group Equipment Group

Equipment Group Equipment Group Equipment Group

 Order Stops provide a way of routing an order that

Order Order Release Shipment

 Build Buy Shipment on Primary Leg and Build Buy

 You can bulk plan multiple

 Use this action to create shipments from one or more

 Use this action to manually create a shipment for order

 Use either of these actions to manually move an

 Company ABC can manage their Fleet and

 OTM Fleet Management allows companies to manage their

 Manage drivers, shipments and assets using the Dispatch

1) Introduction & Overview

Companies using a fleet technology solution reported an average

(Source: Service on the Move: Driving Profitability via

“The next ten years will be all about mobile

Route & Appointment

Manage transportation footprint on a single network

Align with overall information management strategy

Increase visibility and coordination

 Oracle introduced the Fleet Management module with the release of

 Fleet Management offers a wide variety of uses for managing an

 In addition to these fleet-specific enhancements, Oracle introduced

 Advanced Layouts (used to configure dispatch boards)

 Enhanced mapping tools

The Fleet Module introduces us to several new business objects. Some

 A Power Unit in Fleet is a truck that is assigned to a driver (or drivers)

 Your power units should have been generated in a previous team

EQUIPMENT GROUP ROAD EQUIPMENT

EQUIPMENT GROUP 50‟ Dry Vans

EQUIPMENT GROUP 52‟ Vans 55‟ Vans

SAC_001 SAC_003 SAC_005

 Location Role Setup – Equipment Pool

 Equipment Pool role indicates to OTM which locations are

 Fleet Logic Configuration Identifies the Location Role that is to be used to

 Buckets are used to manage and track equipment,

 Bucket Level Types

 Assigning Equipment to Buckets and Bucket Types:

 The Driver HOS Daily Summary provides a way to manually

 Periodic vs. Continuous HOS Rule

 Shipment Fleet Actions

 Driver Fleet Actions

 Equipment Fleet Actions

 Shipment Information can be sent to a driver via Driver

 Despite feasibility, Drivers, Equipment, and Equipment Type