1

2
3
Welcome to Session 3 of the daily driver scenario for Oracle
Transportation Management 6.1 Transfer of Information Fleet
Management course.

4
This 5-part course is intended to:

Provide an overview of how to set up and use OTM Fleet Management

Help you find additional release information and resources

5
The first session of this course will include:
An explanation of some basic OTM Fleet Management terms and the general
flow of OTM Fleet Management
An explanation of the business scenario for this course
A review of the processes used within OTM to manage your fleet daily driver
operations, including:
Defining Next Available Time or NAT and Next Available Location or NAL
overrides
Associating a driver with a power unit
Viewing order releases
Building shipments
Assigning drivers via the dispatch board

6
The second session of this course will include:
A review of the processes used within OTM to manage your fleet daily driver
operations, including:
Assigning equipment type via dispatch board
Assigning equipment via dispatch board
Assignments for fleet drivers, a shipment with special services, and non-
fleet shipments

7
The third session of this course will include:
A review of the processes used within OTM to manage your fleet daily driver
operations, including:
Dispatch plan optimization (which is sometimes called stringing/stacking or
multi-driver/multi-shipment
Asset tracking events
Mobile communications
Driver work invoices

8
This fourth session of this 5-part course includes:
A review of the setup of the main business objects necessary to run this
scenario, including:
Power units
Drivers
Hours of service (HOS)
Driver calendar events
Locations
Equipment

9
The final session of this course will include:
A review of the setup of the main business objects necessary to run this
scenario, including:
Setting up asset inventory on locations
Setting up and understanding the dispatch board
Commodities and items
Itineraries and service providers
Rate services and cost categories
Rate offerings and rate records
Logic configuration for dispatch plan optimization

10
The third session of this 5-part course includes the following sections:
A review of the process used within OTM to manage your fleet daily driver
operations, including:
Dispatch plan optimization functionality (which is sometimes called
stringing/stacking or multi-driver/multi-shipment)
Asset tracking events
Mobile communication functionality
Fleet financials
Additional Resources

11
First, lets review the concept of dispatch plan optimization which is
also sometimes called stringing/stacking or multi-driver/multi-
shipment.

12
Lets review how to use the dispatch plan optimization options
provided in OTM Fleet Management.

13
The dispatch plan optimization feature optimizes and assigns drivers while considering many
shipments and many drivers.
Optimization can be performed via:
the dispatch board
a new process, Optimize Fleet Resource Assignment, via process management, or
the Shipment manager using the following Buy Shipment actions: Optimize Driver
Assignment and Optimize Equipment Assignment
Given a set of drivers and a set of shipments, dispatch plan optimization will create the
optimal solution to assign the set of drivers to their most optimal shipments for all the
drivers at that given time. The number of shipments per driver is controlled by the
MAXIMUM NUMBER OF SHIPMENTS IN STRING parameter which is described in
session 5 of this training.
After running the dispatch plan optimization, you can see the results on the Fleet
Resource Assignment Results page.
It can also assign equipment at the same time. You can use this feature to have a fully
realized equipment type and driver assignment to include multiple shipments for those
drivers. Dispatch plan optimization allows you to plan a drivers entire day or days with a
single action in OTM.
As part of this feature, a new logic configuration parameter page has been added which
is called Fleet Optimization. You turn on the dispatch plan optimization feature through
these OTM parameters. For details on how to set up dispatch plan optimization using the
OTM parameters, refer to session 5 of this training course.
Once the correct parameters are turned on, you can select multiple drivers and multiple
shipments and run the actions Optimize Driver Assignment or Optimize Equipment
Assignment against.
In this section, lets look at the process of using the dispatch plan optimization feature in more
detail.

14
First, lets review the Optimize Driver Assignment action.
To run the action either from the Shipment manager or the dispatch board,
complete the following:
1. Select multiple shipments.
2. Then, click Actions.
3. Then, select Fleet Management > Assign > Optimize Driver Assignments.
When you run the action, first OTM unassigns the driver(s) from any shipments
that you have selected which had drivers assigned previously and then OTM
runs the optimize fleet assignment logic.

On the Optimize Fleet Assignment Input page, you can specify:

A Parameter Set ID. In this example, Warbler Holdings used their customized ID
of DAILY DRIVER SCENARIO. You must enter a Parameter Set ID.
A description for this fleet resource assignment.
A Driver Saved Query ID which is required. In this case, the driver saved query
of WARBLER ALL DRIVERS was used. This query limits the search to all
drivers in the TOI/FLEET domain.

15
First, lets review the Optimize Equipment Assignment action.
To run the action either from the Shipment manager or the dispatch board,
complete the following:
1. First, select multiple shipments.
2. Then, click Actions.
3. Then, select Fleet Management > Assign > Optimize Equipment
Assignments.
Running the action will unassign the equipment from any shipments that you
have selected which already have equipment assigned.
The Optimize Equipment Assignments action determines the optimal equipment
assignments for a series of shipments. For these selected shipments, OTM finds
the best equipment. This batch action allows you to automate the process of
assigning equipment to shipments and requires that equipment type already be
assigned to the shipment.

On the Optimize Fleet Assignment Input page, you can enter the
following:
A Parameter Set ID. A parameter set ID is required.
A description for this fleet resource assignment.
An Equipment Saved Query ID. In this case, the equipment saved query of
WARBLER HOLDINGS EQUIPMENT was used. This query limits the search to
all equipment in the TOI/FLEET domain.

16
Next, lets review how to run dispatch plan optimization from the OTM
Process Manager.
Go to Fleet Management > Process Management. Then under Asset
Management, select Optimize Fleet Resource Assignment.
On the Optimize Fleet Resource Assignment process management page, you
can enter the following:
Fleet Bulk Plan ID This is the ID that you want OTM to use for the fleet
bulk plan ID instead of automatically creating one. This is not a required
field.
Shipment Saved Query This is the shipment saved query that the process
manager will use to select the appropriate shipments to which to assign
either drivers or equipment.
Driver Saved Query or Equipment Saved Query You must enter either a
driver saved query or equipment saved query to tell OTM which drivers or
equipment to use when completing the assignments. Either a driver saved
query or an equipment saved query is required.
Parameter Set ID This is the parameter set chosen to run this bulk
assignment. This is required.
Description This is the description of this assignment.
Application Server This field only appears when running OTM in a
scalability environment.
Now and Schedule options You can either have this process complete
immediately by selecting Now, or you can Schedule the process to occur at
another time.
One of the outputs of this page is a fleet bulk plan which is different from a
regular bulk plan. Lets review this fleet bulk plan on the next slide.
17
The Fleet Resource Assignment Result page automatically opens if you run the Optimize Driver Assignments action, the Optimize Equipment
Assignment action, or the Optimize Fleet Resource Assignment process. In addition, this page can also be accessed via Fleet Management >
Planning Results > Fleet Resource Assignment Result.
This is a view only page. Below are some of the fields that appear on this page:
Description This is blank because no description was entered on the previous page.
Fleet Bulk Plan ID This specific fleet bulk plan ID was automatically generated by OTM using the business number generator.
Shipment Query Name This field is blank because no shipment query was specified on the previous page.
Resource Query Name When assigning a driver, this saved query was used to retrieve available drivers.
Resource Type The type of resource for this bulk assignment.
Status The current status of this fleet bulk plan. Note that this particular fleet bulk plan has a status of RUNNING.
Parameter Set ID The parameter set chosen to run this bulk assignment.
Start Time and End Time - The start and end time of the bulk process. This fleet bulk plan has no end time because it has not yet completed.
Shipments Selected The number of shipments selected prior to running this fleet bulk assignment. These are the shipments for which the
driver and equipment assignment will be attempted.
Shipments Assignable The number of shipments that are in assignable states.
Shipments Assigned The number of shipments actually assigned as a result of the fleet bulk assignment. This field is only populated when
the fleet bulk plan completes.
Total Cost Before Assignment The total cost of all the shipments selected before resources are assigned. This is the sum of all shipment
costs retrieved from the shipment weighted cost.
Total Cost After Assignment The total weighted cost of all shipments after assignment of resources.
Resources Selected The number of resources (drivers or equipment types) selected prior to running this fleet bulk assignment. This is the
number of resources that OTM will attempt to assign to the selected shipments.
Resources Assignable The number of drivers or equipment types that are in assignable states.
Resources Assigned The number of resources (drivers or equipment types) actually assigned due to the fleet bulk assignment. This field is
only populated when the fleet bulk plan completes.
Resources Assigned Multiple Shipments The number of resources that have multiple shipments assigned during this bulk plan process.
Bobtail Distance The total bobtail distance of all the shipments after fleet bulk assignment.
Deadhead Distance The total deadhead distance of all shipments after fleet bulk assignment.
Total Empty Distance The sum of the bobtail distance and deadhead distance.
Loaded Distance The total loaded distance of all shipments after fleet bulk assignment.
Additionally, there is a Cost Details section which includes the following:
Cost Category This is the category of the cost. Refer to session 5 to learn more about cost categories in OTM.
Total Cost Before Assignment The total cost of this category of all the shipments selected before assignment. It is retrieved from the
SHIPMENT_COST table before launching the assignment.
Total Cost After Assignment The total cost of this category of all the shipments selected after assignment.
18
Next, lets review the process of entering asset tracking events for the
daily driver scenario.

19
Next, lets review how a dispatcher could enter an asset tracking
event to indicate that a shipment has completed.

20
 You can receive inbound event messages for assets instead of just for
shipments.
This allows events to come into OTM about an asset while it is at rest. And also,
allows events to be processed directly against drivers.
You can now view each of those distinct objects and see what has happened to
the object as a result of the inbound asset event message.
You can send in asset event messages using any of the following:
EDI
CLM
Mobile communications via in-cab systems
Trailer tracking devices
Driver collaboration
3rd part web-based collaboration
This data is sent to OTM via XML and can contain:
Key fields which OTM will match against data in the OTM database (an
asset, such as driver, power unit, equipment, etc.)
Data fields against which OTM can process data
Information fields that OTM can populate into either the user interface or the
database

21
An asset tracking event can provide information related to just that
asset or it can provide information that is relative to related OTM
business objects. For example, a driver event could provide
information about that driver, the power unit, and the shipment the
driver is working on.
When OTM receives an inbound asset event message, it attempts to
match the message to a primary asset.
The match is either successful or unsuccessful. Based on this success, a status
is set on the asset tracking event.
An inbound asset event message can have pointers to more that one asset (e.g.,
equipment ID, power unit, driver, shipment ID)
OTM attempts to match the inbound asset event message to an asset
as follows:
First, OTM uses the key fields plus source and target information provided in the
message.
Second, OTM searches via attributes which can also be provided in the
message.
Finally, OTM may require that you manually intervene and match the event
message to an asset.

22
Drivers, dispatchers, and tracking devices can send real world
information about assets to OTM using an asset tracking event. An
asset tracking event is similar to a shipment event.

An asset tracking event describes:

What has happened via a status code
Why it happened via a status reason code
When it happened via a date and time
Where it happened via a shipment ID, shipment stop number, location name,
latitude/longitude, driver ID, power unit ID, or equipment ID.

23
 First, lets take a look at the Tracking Event search page, results page, and the
Tracking Event Manager.
To view the new Tracking Event search page, go to Fleet Management >
Visibility > Event Tracking.
You first see the tracking event search page which contains the following tabs:
Identification
Detail
Equipment
Location
Special Service
Driver, and
Processing Results

You can use the fields on any of these tabs to narrow down your search for a
specific tracking event.
Or, you can create a new tracking event. Details on creating a new tracking
event will be reviewed in the guided demonstration later in this section.

24
 If you search for an existing tracking event, you see a Tracking Event results
page similar to the one shown on this slide.
To view more details about a particular tracking event, click the ID link.

Lets click the ID 1518524 to see the details of that tracking event on the next
slide.

25
 One major difference between a shipment tracking event and an asset tracking
event is that you can edit an asset tracking event after it has been created. You
may need to edit the asset tracking event for several reasons:
You may need to edit the status information on the asset object.
You may need to edit the asset activity record data (to include status and
actual arrival time).
You will review exactly how this particular tracking event was entered into OTM
in the guided demonstration later in this section.

26
Through the actions menu for the Tracking Event Manager, you can
also complete the following:
Mark as Error You can mark an event as error using the Mark as Error action.
Reprocess You can re-process an event that you have made changes to using
the Reprocess action.
Copy Tracking Event Copy an event and save it with a new name using the
Copy Tracking Event action. Then, you can modify the newly named event and
process it. This allows you to keep a record of what the original event was.
Send Interface Transmission You can also send the event to an external
system using the Send Interface Transmission action.

27
This guided demonstration reviews how to enter an asset tracking
event for the completed delivery of shipment 01046.

28
Next, lets review at a high level how mobile communication works
with fleet management.

29
Next, lets review how mobile communication works at a high level for
a fleet scenario.

30
Office workers and truck drivers need to communicate to execute their
fleet operation. OTM mobile communication allows messages to flow
between the two using devices in the truck, on the trailers, or even
with the driver.
The mobile communication feature in OTM sits between the XML
transmission layer and outside communications. This layer consists of
a message hub and message viewers.
The hub contains logic that can transform inbound and outbound messages from
a variety of formats to the OTM XML format or visa versa.
The message hub also allows you to take in external messages from a device
and map them to the internal asset (power unit, driver, or equipment).
The message hub also collects and stores many of these inbound and outbound
messages.
The OTM message center acts as a console which allows you to view,
edit, and re-process messages. There will be many messages in the
message hub, but a sub-set of those will be listed in the message
center as requiring your attention.

31
Since all messages are sent via a device, OTM mobile communication
must relate the driver, the truck, and the trailer to a device for a period
of time.

32
You can create the association in the OTM user interface or via log on
and log off messages.
A device can be associated to an asset for an extended period of
time. The device can also be associated to an asset more dynamically
as the driver logs into and out of the device.

33
You can send messages via the message hub for the following:
Dispatch static association to a message type
Compose and send (for ad-hoc notifications)
Standard notifications
Standard integrations

34
A key object when configuring mobile messages is the message type;
it helps you control the following:
If saving a copy in the message hub
How to format the message
Who to send the message to and any parties to CC (carbon-copy)
What communication method to use for a particular mobile vendor

35
As the message travels to its recipient it passes several milestones,
OTM mobile communication can relate receipts to the original
message and store the status and date from the receipt in the original
message.

36
Inbound messages fall into two categories: light-weight and
actionable:
For frequent, inbound messages that do not require automation agent
processing in OTM, there is a light-weight approach. Examples of these
messages are periodic positional pings, driver logins, work assignment receipts,
and free-form messages.
For messages that require automation agent processing, you could create a
GLogXML, raise events, and use the full functionality of the OTM automation
agents. Examples of these messages are NAT/NAL updates, pickup/delivery
notifications, and change of equipment.
It is the message type that helps OTM determine what to do with the
message. If the message type is not specified, it can be obtained from
the message.
Message type lets you control the following:
If the message is actionable?
If actionable, what OTM API to use shipment actual or tracking event?
If OTM should propagate to the message center never, always, or only on
error?
If someone should be notified about this particular message?

37
Next, lets review the process of creating a driver work invoice for the
daily driver scenario.

38
Next, lets review how a dispatcher can create a driver work invoice to
make sure the driver gets paid.

39
 Now that John Scarlett has completed the shipment, you want to create a driver
work invoice. You know that John Scarlett has completed the shipment because
he had the Warbler Holdings dispatcher enter an asset tracking event indicating
that the shipment was completed.
The purpose of generating a work invoice is to create a record that represents all
of the activities and miles associated with a particular shipment, such that, the
driver can be paid for those activities and miles.
In OTM, the Driver Work Invoice page enables you to view or edit existing driver
work invoices and to transmit the data to an external payroll processing system
such as Oracle Incentive Compensation. These invoices consolidate pay
information based on driver activities.
A driver work invoice or work invoice is similar to a carrier invoice in that it
references individual charges related to a shipment. Driver work invoices contain
actual special service information pertaining to activities that were performed as
part of the shipment. They state what the driver did and how much pay the driver
should anticipate for services. Modifications, line additions, and subtractions can
be performed against the work invoice to capture an accurate summary of work
performed at a particular point in time.

The downstream payroll system is responsible for determining who gets paid
what for which activities. It is OTMs responsibility to ensure that all pertinent
variables are sent so payroll has flexibility to perform the necessary calculations.

40
Miles come in three types:
Bobtail refers to the driver and tractor or power unit only, but not the freight,
trailer, or container.
Deadhead refers to the driver, tractor or power unit, and trailer or container only,
but not the freight.
Freighted refers to the driver, tractor or power unit, trailer or container, and the
freight.

41
 Activities are represented by a particular special service and will contain one or
more than one of the following values defined on the activity:
Distance
Duration
Weight
Volume
Ship Unit Count
Item Package Count

Later, this section reviews these activities in more detail when looking at the
work invoices activities page in OTM.

42
Payable indicators control whether a work invoice activity gets paid to the driver. These
values are set on the special service and can be overridden on the shipment or work invoice.
You can specify the following payable indicators on the special service using the Default
Payable Indicator field:
Not Payable
Payable
Payable (Zero Amount)
Requires Approval
Lets look at these payable indicators in more detail.
Not Payable For example, the driver must check in at the guard shack upon arrival at
the customer delivery. This is entered as a special service on the shipment but is not
approved for payment and should not appear on the drivers payroll report.
Payable An example of payable is hand unload. Some locations always require the
driver to hand unload deliveries. This special service can be attached to the location and
copied to the shipment when a stop is created for this location. The driver can be
dispatched with this information ahead of time and paid when the shipment is completed.
Payable (Zero Amount) This can be used to display an activity that the driver
performed as part of another activity. A payable zero activity is sent over to the payroll
system so that it may be displayed on a drivers pay statement.
Requires Approval Pre-approval or management initiated approval is required for
certain types of special services for example lumper service. For these special services,
the payable indicator defaults to Requires Approval. Once approval has been given, the
payable indicator should be manually changed to one of the other three values. The work
invoice cannot be generated when a special service has a payable indicator of Requires
Approval and OTM displays an error message when you try to create the driver work
invoice.

43
A driver work invoice is generated by running the action Generate
Driver Work Invoice.
This screen shot shows the action being used from the Dispatch
Board.
1. First on the Dispatch Board, select a shipment.
2. Then, click the Actions icon.
3. And finally, select Fleet Management > Driver Dispatch > Generate Driver
Work Invoice.

Once the driver work invoice is created, you see the confirmation
message shown on the next page.

44
When you select the Generate Driver Work Invoice action, you see a
screen similar to the one shown on this slide confirming that the work
invoice was created and indicating the shipment from which the Work
Invoice ID was created.
The Work Invoice ID is a combination of the driver, shipment ID, and a
sequence number (starting with 01). This is created via OTM business
number generation.
Note that OTM populates the driver work invoice based on data in the
shipment. If using multiple currencies, note that the shipment displays
the costs in the user preference currency, whereas the driver work
invoice displays the revenue in the currency entered, which may be
different than the user preference currency.

45
You can navigate to the work invoice through the Fleet and Asset Management > Driver Work Invoice menu option or
by clicking the Work Invoice ID on the confirmation message.
Work invoices are created through the buy shipment actions which are available either from the Buy Shipment
Manager or the Dispatch Board. You can also generate a driver work invoice through the SHIPMENT agent
actions.
Note that you cannot directly create a work invoice from the Work Invoice manager. However, from the Work
Invoice manager, you can view or edit an existing work invoice.
The work invoice is similar to a carrier invoice in that it references activities related to a shipment. Modifications,
line additions, and subtractions can be performed against the work invoice to capture an accurate summary of
work performed at a particular point in time.
Some of the fields shown on the work invoice are the Work Invoice ID, Driver ID, and Shipment ID.
Work Invoice Number is a combination of the shipment ID and a sequence number. The sequence number
will remain the same if the work invoice ID changes due to modifications, deletions, withdrawals (void), etc.
This sequence number is added for traceability.
You can view the related shipment and driver directly from the work invoice by clicking the v (view) button to
the right of the appropriate field.
Date Sent is filled in when the invoice is actually sent via the Send Interface Transmission action. This will be
reviewed later in this section.
A revenue amount is also included and is used for drivers that are paid a percentage of the revenue that is
generated from the sell shipment. The details of the drivers percentage are managed outside of OTM;
however, OTM captures the revenue amount here so it can be sent downstream.
Status Lets review this in more detail in a few slides.
Within the Work Invoice Activities section, a Work Invoice Activity is created for each special service on a
shipment assigned to the given driver or driver team. You can click the pencil icon to see more detail about a
specific Work Invoice Activity. Lets review the specific special services that were pulled in for this work invoice:
UNLOAD and PICKLOADED came in directly from the shipment and indicate the activity of the driver
actually picking up the pre-loaded equipment at the Woodbury location (PICKLOADED) and unloading the
freight at the Marcus Hook location (UNLOAD).
BOBTAIL was calculated from the information provided on the shipment at the time of the work invoice
creation.
TRANSPORT is the special service that is added automatically at the time of work invoice creation to
capture freighted miles.
Lets take a look at a specific work invoice activity on the next slide.
46
To view the details of the bobtail work invoice activity, click the BOBTAIL link.
Each work invoice activity captures the elements needed to convey payroll
information. While the initial values for these fields are pulled from the related
shipment or special service, these values can be overridden if needed. Against a
given activity on a work invoice, you can see more detail about that activity.
OTM includes information about the work that was performed, including:
Activity Date This is either the date when you ran the Generate Driver Work
Invoice action or the date taken from the event date / time that was entered on
the asset tracking event that updated this special service.
This is the Special Service ID related to the activity.
Location data includes the Source Location ID and Destination Location ID.
Also, one or more of the following values may be recorded against the special
service and are used outside of OTM to calculate drivers pay. These values can
be brought in from the shipment and updated via shipment tracking events. In
this case, the distance and duration were populated directly from the shipment.
These values can include:
Distance
Duration
Weight
Volume
Ship Unit Count
Item Package Count
Note the Payable Indicator which is set to PAYABLE.

47
Lets go back to the main Work Invoice page. You can click on the Status button to see the
work invoice statuses.
The two status types are WORK_INVOICE_SENT and WORK_INVOICE_VALID. Lets
review these in more detail.
WORK_INVOICE_SENT can have one of the following status values:
WORK_INVOICE_SENT_SENT Indicates that the Send Interface Transmission
action has been run.
WORK_INVOICE_SENT_NOT_SENT Indicates that the Send Interface
Transmission action has not been run.
WORK_INVOICE_SENT_RECEIVED This can be set by an OTM automation
agent based on an external event. If this is not set on the invoice, the invoice cannot
be sent to an external system.
WORK_INVOICE_SENT_FAILED This can be set by an OTM automation agent
based on an external event.
WORK_INVOICE_VALID is set when the Payable Type on any of the special services
requires approval and can have one of the following status values:
WORK_INVOICE_VALID_VALID If the work invoice requires approval and has
been approved, the status value is set to WORK_INVOICE_VALID_VALID.
WORK_INVOICE_VALID_VOID This status value indicates that a work invoice
has been voided. There is an action to void an invoice called Cancel Work Invoice. If
you cancel a work invoice before it is sent, then it is deleted. This status is only set if
the invoice was already sent, then a reversal work invoice transmission is sent
automatically based on running the Cancel Work Invoice action.
WORK_INVOICE_VALID_REVERSAL This is set when the invoice is canceled but
the invoice has already been sent to an external system.
For this specific work invoice, the status type of WORK_INVOICE_SENT is set to
WORK_INVOICE_SENT_NOT_SENT since you just created the invoice and have
not sent it out via integration. The status type of WORK_INVOICE_VALID is set to
WORK_INVOICE_VALID_VALID since this invoice does not require approval.

48
You can send driver work invoice data to an external system from either the Buy
Shipment manager or the Dispatch Board.
When you send an interface transmission, the OTM manager packages all the
information and publishes a Send Integration topic. OTM then activates a trigger that
listens for the topic and does the work of sending out the XML document.
To send an interface transmission for a work invoice, complete the following:
1. Select the appropriate work invoice.
2. Then, select Actions > Send Interface Transmission.
3. Choose Send Full Text or Send Summary Only.
If you select send full text, OTM sends a complete record to the external
system, which consists of all the information for the object you are sending. If
you select send summary only, OTM sends only the ID of the record you
selected to send to the external system.
4. Next, enter text in the Remarks field to add a comment describing the
transmission being sent.
5. Then, select the External System to which you want to send the transmission.
If the external system does not exist yet, you can create it here.
6. And then, from the drop-down list, select Notify Type. This tells OTM how to
send the transmission. The options are:
HTTP
FTP
QUEUE
SERVICE
7. The Guarantee Delivery check box is reserved for future use.
8. Click Send to send the interface transmission.
49
Once you click send to send the interface transmission, you see a
confirmation message stating that the interface transmission has been
successfully scheduled.

If you search for and edit the work invoice, you can click the Status
button to see the WORK_INVOICE_SENT status has changed from
WORK_INVOICE_SENT_NOT_SENT to
WORK_INVOICE_SENT_SENT as shown on this slide.

50
You can edit a work invoice if the status of the invoice is NOT set to
one of the following:
WORK_INVOICE_VALID_VOID or WORK_INVOICE_VALID_REVERSAL

and

WORK_INVOICE_SENT_SENT or WORK_INVOICE_VALID_VALID

In the screen shot on this slide, notice that the Driver ID, Work Invoice
Number, Shipment ID, and Revenue fields are all grayed out which
means that you cannot make any changes to those fields.

51
There is an action to void an invoice called Cancel Work Invoice. If
you cancel a work invoice before it is sent, then it is deleted. If the
invoice was already sent, then a reversal work invoice transmission is
sent automatically based on running the Cancel Work Invoice action.

52
53
See session 1 of this training course for a complete list of glossary
terms.

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

56
57
58
59