Professional Documents
Culture Documents
Order MG T Fleet
Order MG T Fleet
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in
your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by
any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law
for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing
it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed
on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and
other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program
website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information,
visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Choosing a Solution 43
Verifying the Order 44
Upselling to the Customer 45
Submitting the Order to Oracle Transportation Management to Execute 46
Checking the Status of the Order 46
About Working with Existing Fleet Management Orders 48
Revising Fleet Management Orders 48
Rejecting the Revision of the Order 49
Canceling the Order 49
Index
NOTE: Siebel Innovation Pack 2015 is a continuation of the Siebel 8.1/8.2 release.
This chapter provides an overview of Siebel Orders for Fleet Management. It includes the following
topics:
■ Oracle Transportation Management. Fleet planning and execution, and driver management
■ Enterprise Business Suite Asset Lifecycle Management. Asset definition, management and
maintenance
■ Enterprise Business Suite Human Resources. Driver human resources, such as scheduling
and pay
NOTE: It is possible to integrate with other applications instead of with these Oracle applications.
For example, you might have a legacy, transportation-management application that you integrate
with instead of Oracle Transportation Management. If you have integrated with another
transportation-management application, whenever this document mentions Oracle Transportation
Management, use this other application instead.
The following standard features of Siebel Order Management do not apply to Siebel Orders for Fleet
Management:
■ Pricing. Any discussion of pricing in Siebel Order Management Guide and Siebel Pricing
Administration Guide does not explicitly apply to Siebel Orders for Fleet Management, which uses
the rating inquiry engine of Oracle Transportation Management to do its pricing.
■ Quotes. Siebel Orders for Fleet Management supports spot quoting, as described in “About Spot
Quoting” on page 31. The discussion of other forms of quoting in Siebel Order Management Guide
does not apply to Siebel Orders for Fleet Management.
■ Upsell Products. The discussion of upsell products in Siebel Product Administration Guide does
not explicitly apply to Siebel Orders for Fleet Management, which has its own method of creating
upsell products, described in “About Administering Upselling for Fleet Management” on page 11.
■ Eligibility. Eligibility to purchase products, as described in Siebel Order Management Guide and
Siebel Product Administration Guide, does not apply to fleet management, and the fields related
to eligibility are removed from Order and Product records.
NOTE: The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle E-Delivery.
It might also be installed locally on your intranet or on a network location.
Oracle Fleet Management requires the integration of the Siebel application with the other
applications listed previously in “Oracle Fleet Management” on page 7. This integration uses the Web
services covered in Siebel CRM Web Services Reference
The customer service representative looks up the customer in the Siebel application. If the customer
is an existing customer, the customer service representative uses the customer information already
in the database. If the customer is a new customer, the customer service representative adds the
account and contacts in the Siebel application in the usual way, as described in Siebel Applications
Administration Guide.
The customer service representative creates a new order, entering information in the order header
and order line item for Siebel Orders for Fleet Management, as described in “Process of Creating
Orders for Fleet Management” on page 32. The order contains added fields that are specific to fleet
management. For example, the header includes the origin and destination locations for this delivery.
This information will be passed to back-office applications and used to price and manage the order.
In the Line Items view, the customer service representative adds a line item for the product named
Transportation. In addition, because this is an order to transport fragile material, the customer
service representative adds a line item for the accessorial product Driver Hand Unload By Piece,
which means that the routine precautions for dealing with fragile materials will be taken and will be
included in the price charged to the customer.
The customer service representative enters the stop records for the transportation product. Because
this order is a one-way delivery, it has only two stops, the origin where the material is picked up,
and the destination where it is delivered.
The customer service representative also enters actions that are necessary at each of these stops.
In this case, the actions are special instructions that are needed while picking up and delivering
fragile products.
In the Commodity view, the customer service representative adds records specifying the commodity
that will be delivered. The customer service representative enters the weight of the product and
other relevant details. The customer service representative enters the stops and actions for the
commodity.
The rating engine determines the availability of resources to perform the delivery, based on the
requested start date and the requested end date for the origin and destination. The rating engine
also determines prices, including the total price, the base price for the delivery on each date, the
price for the special handling, and other possible pricing details, such as a surcharge for fuel. It
returns this information to the Siebel application, where it is displayed in the Solutions view.
Information about this solution is added to the additional fields in the order record. These fields are
used to capture pricing and resource information from Oracle Transportation Management.
This view shows that, during the last six weeks, the customer has placed a large number of orders
for rail transportation from Chicago to New York and that these orders had a large static profit. It
also shows that rail transportation from Chicago to New York is a targeted lane, which the
transportation company is focusing on selling.
The customer service representative asks whether the customer will want rail transportation from
Chicago to New York in the near future. The customer will want it later in the week and will want to
check the pricing, and possibly place the order now.
After submitting the current order, the customer service representative clicks the Auto-Order button
to create the new upsell order. The customer service representative will then get more details for
the new order from the customer, and will generate possible solutions for the customer. The
customer service representative asks whether the customer will also want transportation in some of
the other lanes in the Upsell list, but the customer does not want this immediately.
If the customer inquires about the status of the order, the customer service representative can
respond by looking at the Status field of the order record, line item records, stop records, and action
records in the Siebel application.
This chapter covers the administrative tasks for Siebel Orders for Fleet Management that are
different from the standard administrative tasks for order management. It includes the following
topics:
■ “Configuring Validation for Verifying and Submitting Orders for Fleet Management” on page 28
■ Score. A score is calculated for each lane for this customer, based on the customer’s order
history; see “Configuring the Score for Upselling” on page 12. It displays the ten lanes with the
highest scores in the Upsell view. The customer is most likely to ship product using these lanes,
and they have the highest profit.
■ Targeted lanes. Your marketing department creates a list of targeted lanes, which are routes
where your company wants to focus on selling transportation. If a lane displayed in the Upsell
view is also a targeted lane, it is indicated in the NM (network management) field for that lane.
The customer service representative can upsell to this customer in these ten lanes and can
emphasize the lanes that are targeted lanes, as described in “Upselling to the Customer” on page 45.
If the customer places an upsell order, it is an additional order, which is separate from the initial
order.
This history is used to calculate a score for each lane that each account uses.
With the preconfigured Siebel Orders for Fleet Management application, the score is calculated for
the last six weeks. This period is configurable and is stored in the system preference, FM Eval Period
in Weeks.
The score is configurable. It is a calculation with a weighted measure, including loads for each week
and static profit for all orders that a customer has placed for a lane during the evaluation period.
With the preconfigured application, the score for each lane for each account is calculated using the
following formula:
Min(FM Upsell Score Max Ord Count, Order Count)*Min(FM Upsell Score Max Stat Prft,
Order Static Profit).
The formula uses the following variables, some of which are configurable:
■ Order Count. The total number of orders from this account for this lane during a given
period. The period is defined by system preference: FM Eval Period in Weeks, as mentioned
previously, and it can be configured by changing the value of this system preference. The
Order Count field itself must be part of the formula and cannot be removed or replaced with
another field. The Order Count field is in the FM Order History business component.
■ FM Upsell Score Max Ord Count. A system preference that indicates the maximum value
for the number of orders used in the calculation. The default value is 6. You can configure
the variable by changing the value of the system preference.
■ Order Static Profit. The total static profit from this account for this lane. You cannot
configure this variable. The Order Static Profit field is in the FM Order History business
component.
■ FM Upsell Score Max Stat Prft. A system preference that indicates the maximum value for
the static profit used in the calculation. The default value is 500. You can configure the
variable by changing the value of the system preference.
For more information about setting system preferences, see Siebel Applications Administration
Guide.
The customer service representative tries to sell the customer more orders for these lanes in addition
to the initial order, because these are the lanes where the customer is likely to place orders with a
high static profit.
A lane is a route between an origin and a destination using a given line of business. For example:
Instead of cities, regions can be used as the origin and destinations of lanes. For example, if a
transportation provider targets the lane representing truck deliveries from Berlin to Paris, it might
also want this lane to include deliveries from the suburbs of Berlin and to the suburbs of Paris . To
include the suburbs, it defines the regions, based on the postal codes, or on city and state names.
Regions are defined in external applications, which must be integrated with the Siebel application.
You can define targeted lanes in an external application that is integrated with the Siebel application,
or you can define targeted lanes in the Siebel application, as described in the following procedure.
b Use the Columns Displayed dialog box to move the Effective Start Date, Effective End Date, and
Active fields from the Available Columns list to the Selected Columns list.
c Click Save.
3 Add new records to the Targeted Lanes list, and complete the necessary fields, described in the
following table.
Field Description
Origin City, Origin State If you are using a city as the origin, enter the name of the
city and state.
Destination City, Destination If you are using a city as the destination, enter the name of
State the city and state.
Origin Pricing Region If you are using a region as the origin, enter the name of the
region.
Destination Pricing Region If you are using a region as the destination, enter the name
of the region.
LOB Select the line of business for this lane. For example, lines of
business might be truck, rail, or intermodal.
Effective Start Date Enter the date when the designation of this lane as a targeted
lane first becomes effective.
Effective End Date Enter the date when the designation of this lane as a targeted
lane is no longer effective.
Table 1 shows some product types and some examples of products that you might create for each
type. The product types and products that you want depend on your business model.
Commodity The products that you deliver for your customers. ■ Frozen Foods
■ Fresh Foods
■ Gravel
If necessary, you can create your own product types. For information about configuring your own
product types, see Configuring Siebel Business Applications. For information about creating
products, see Siebel Product Administration Guide.
The Location screen is specific to orders administration for Fleet Management. It includes an Account
view and a Contact view, which uses accounts and contacts created in the standard Siebel
application. For more information about working with accounts and contacts, see Siebel Applications
Administration Guide.
For fleet management, one account might have many locations. For example, one of your accounts
might be a large retail chain, and the locations that you provide transportation services to might
include all of this chain’s individual warehouses and stores in your region. You must enter a location
record for each of these locations.
Because many deliveries are to repeat customers, with pickup and drop off at the same locations,
the customer service representative does not always have to enter new location information while
placing an order.
NOTE: The Siebel application contains an Administration - Location screen that is used for Siebel
Events Management. This field is not related to the locations that are used in Siebel Orders for Fleet
Management.
2 Add a new record to the Location list, and complete the necessary fields. Some fields are
described in the following table.
NOTE: Other fields in this record are filled in when you enter information in other views.
Field Description
Location Name Enter a name for the location. The name is not the same as
the account name, because one account might have many
locations.
Location Type Select the location type. Some types are Ship From/Ship To,
Invoice To, Airport, Port, Rail Station.
Location Valid The field indicates whether the location is valid. You can
update this field manually, or integrate it with an external
application that updates this field.
Organization Name Select the organization within the account that owns this
location. The default is Default Organization.
Active Do not select this check box when you are first entering the
location record. Select it after you have entered all necessary
information in all views and the location is ready to be used.
When the customer service representative adds the origin, destination, or other stops for an order,
the Siebel Orders for Fleet Management displays only locations associated with the tendering party.
Thus, you must add all tendering parties who use this location, so the customer service
representative can choose the location as stops in their orders.
With the preconfigured Siebel Orders for Fleet Management application, all the stops for an order
display only locations associated with the tendering party for the offer. Thus, you must add the
accounts for all tendering parties who use the location, to allow the location to be used in orders
from those tendering parties.
For example, if the location is a warehouse that is owned by a third-party retailer and that is used
by a number of your accounts as tendering parties, you enter the third-party retailer as the owner
account in the location record, and you enter all the accounts that use the warehouse in this Accounts
list.
To add an account
1 Click the Accounts view tab.
2 Click Add.
3 In the Add Accounts dialog box, select the appropriate account, and click OK.
The Contacts list displays all existing contacts in the Siebel application. If the contacts at this location
do not already exist, you must create them, as described in Siebel Applications Administration Guide.
To add a contact
1 Drill down on the Name field of the location record.
3 Click Add.
4 In the Add Contacts dialog box, select a contact, and click OK.
Though you can enter many addresses for a location in Siebel Orders for Fleet Management, only
one address is sent to Oracle Transportation Management, the primary address. Select the Primary
checkbox for the address that you want to be sent to Oracle Transportation Management. This is
generally the address where the pickup or delivery is made, since this is the address that Oracle
Transportation Management provides to the driver.
To add an address
1 Click the Addresses view tab.
2 Click Add.
3 In the Add Address dialog box, select the appropriate address, and click OK.
4 Select the Primary checkbox of the address that you want to be sent to Oracle Transportation
Management.
To add a role
1 Click the Role view tab.
2 Add a new record and complete the necessary fields. Some fields are described in the following
table.
Field Description
Primary Select this check box if this role is the primary role for the
location.
If the location has only one role, select this check box.
Active Flag By default, this check box is selected, so the role is active.
You can use this field to deactivate roles rather than deleting
them, so the role is not used.
Role Type Select the type of the role. The types are: Invoice To and
Ship From/Ship To.
2 In the Locations list, in the record for this location, select the Active check box.
Product favorites have the advantage of allowing the customer service representative to associate
accounts, agreements, or lines of business with the product favorite, as described in “Adding Product
Favorites” on page 36. This association is useful because:
■ A favorite can represent a common scenario of order fulfillment for a specific account, line of
business, or agreement.
■ Within the common scenario, a favorite can include products automatically using associated
product favorites.
Product favorites can reduce the effort of creating orders, and can also add another level of control
to eliminate errors in order entry.
■ Product favorites for Fleet Management are created in the Administration - Fleet Management
screen.
■ The fields described in Table 2 are added to the product favorites record, and all are optional.
Field Description
Start Effective Date Enter the date when the product favorite can first be used.
End Effective Date Enter the date when the product favorite can no longer be used.
Field Description
Line of Business Choose a line of business to which this product favorite applies.
If you leave this field empty, this favorite will be available regardless of the
line of business in the order header.
If you leave this field blank, this favorite will be available regardless of the
agreement in the order header.
If you leave this field blank, this favorite will be available regardless of the
account in the order header.
Associated Product Select the parent product for the product favorite.
Favorites
All the line items for this product favorite are displayed in this picklist. You
must select the parent product so relationships among the line items in the
product favorite can be generated correctly.
This field allows the administrator to enforce the selection of one product
each time the other product is chosen. For example, you can associate the
special service product Live Load/Unload with the commodity Cattle. In this
example, the commodity Cattle would be the parent product, and the special
service Live Load/Unload would be the associated product. Thus, whenever
the customer service representative selects this favorite for transporting
cattle, the service product would be added also.
When the customer service representative uses the product favorite, as described in “Adding Product
Favorites” on page 36, the product favorite item’s actions are associated with the order's stop record,
as follows:
■ When the customer service representative adds the product favorite to the order, an order line
item is created for each product favorite line item.
■ When the customer service representative creates a stop record for the appropriate order line
item, the action is automatically added for that stop.
The values displayed in this picklist are controlled in the List of Values view of the Data
Administration screen. For each value displayed in the picklist, there is one record in the List of
Values view.
Table 3 shows the value of the Type field for picklists used in Siebel Orders for Fleet Management
and the default values for each type. If you want to change the default values for any type, modify
the records in the List Of Values view.
Language Independent
Type Display Values by Default Code by Default
Complete Complete
In Progress In Progress
Inactive Inactive
Feet Feet
Inches Inches
Meter Meter
Yard Yard
Miles Miles
Language Independent
Type Display Values by Default Code by Default
Intermodal Intermodal
Regional Regional
SFI SFI
Carrier Carrier
Invoice To Invoice To
Port Port
XDock XDock
PTV PTV
Language Independent
Type Display Values by Default Code by Default
All All
Handling Handling
LTL LTL
Multi Multi
Ocean Ocean
Rail Rail
Truckload Truckload
Unknown Unknown
Language Independent
Type Display Values by Default Code by Default
Accepted Accepted
Received Received
Assigned Assigned
Moving Moving
Released Released
Submitted-Pending Submitted-Pending
FM_PACKAGING Bags BG
Bales BL
Boxes BX
Bundles BD
Cans CA
Coils CO
Crates CR
Drums DR
Kegs KG
Pail PA
Racks / Cages RX
Rolls RL
Super Sacks SS
Tubes TU
Language Independent
Type Display Values by Default Code by Default
Failed To Meet Min Profit Req Failed To Meet Min Profit Req
No agreement No agreement
No capability No capability
FM_SHIPPING Floor FL
Slipsheet SS
Language Independent
Type Display Values by Default Code by Default
Assigned Assigned
Cancelled Cancelled
Complete Complete
Inactive Inactive
Unassigned Unassigned
DROP-OFF DROP-OFF
Delivery Delivery
Other Other
PICK-UP PICK-UP
Gallons Gallons
Liters Liters
Language Independent
Type Display Values by Default Code by Default
POUNDS POUNDS
Accessorial Accessorial
Commodity Commodity
To configure a picklist
1 Navigate to the Administration - Data screen, then the List of Values view.
2 In the Type field, query for the type you want to modify, using one of the type values listed in
Table 3.
3 Add one record for each value of this type that will be displayed in the picklist.
■ Order validation. The fields in the order are checked for valid values.
Order Validation
The workflow, SWISendOrder, has been modified to call a fleet management specific rule set. This
workflow calls rules in the Data Validation Manager in the rule set named, FM Order Validation. You
can modify the rules in this rule set to change the validation functionality.
If this workflow is not modified, it checks the following fields and displays error messages if any are
not valid:
■ The business component [Order Entry - Orders] must have valid values in the following fields:
Tendering Party, Liable Party, Origin Location, Destination Location, Origin Start Req Pick Up
Date, Origin End Req Pick Up Date, Destination Start Req Pick Up Date, Destination End Req Pick
Up Date.
■ The business component [Order Entry - Line Items] must have at least one record where the field
Product Type is set to Transportation.
■ There must be one stop record where Type is set to DROP-OFF (Dest), and Location Id is set to
Order Entry - Orders.Destination Location Id.
■ There must be one stop record where Type is set to PICK-UP (Origin), and Location Id is set to
Order Entry - Orders.Origin Location Id.
■ The field, Order Entry - Orders.Status, must have one of the following values: Accepted,
Released, Assigned, Moving, Complete, Cancelled. (A cancelled order is valid and must be
submitted to Oracle Transportation Management.)
■ If the field, Order Entry - Orders.Revision is greater than 1, then this order must be the latest
revision. For example, if five revisions exist for a given order, and the user is trying to verify
order revision number three, then an error message appears.
■ The field, Order Entry - Orders. Hold Flag, must be False. (If it is True, the order is on credit hold,
meaning that it cannot be shipped until the customer’s credit is confirmed.)
These fields indicate that the pricing solution is valid. They must be configured as described in
the following topic.
■ If the product type is Commodity, there must be one pickup stop and one drop-off stop for it.
2 In the Validation Rule Set list, drill down on the rule set that has the name, FM Fleet Order
Validation, and the status of Active.
For detailed instructions about creating and modifying rules, see Siebel Order Management
Infrastructure Guide
Solution Validation
Solution validation provides the Boolean field [Solution Valid Flag] within three Siebel business
components:
■ [Order Entry - Orders.Solution Valid Flag]. The field Solution Valid Flag in the business
component Order Entry - Orders.
■ [Order Entry - Line Items.Solution Valid Flag]. The field Solution Valid Flag in the business
component Order Entry - Line Items.
■ [FM Order Entry - Stops.Solution Valid Flag]. The field Solution Valid Flag in the business
component FM Order Entry - Stops.
Based on your own business process, you configure the application to populate these fields with
values that indicate whether the solution is valid.
■ When the user clicks the Confirm button, the fields are set to true.
■ When the user clicks the Save button, the fields are set to false.
■ When the user clicks the Cancel button, the fields are set to false.
Apart from these values, you must configure the product to populate these fields using any
declarative logic, such as Business Component User Properties or On Field Update Set expression.
For example, you might want to say that a pricing solution is no longer valid for an order, a line item,
or a stop is no longer valid if a user changes the requested start date or requested end date of the
order.
You can configure the product to update one or more of these three fields with the value False
whenever the requested start date or requested end date changes. Then the Validation functionality
detects that the solution is no longer valid.
You can change the rules used to validate this cancel order.
2 In the Validation Rule Set list, drill down on the rule set that has the name, Fleet Cancel Order
Validation, and the status of Active.
For detailed instructions about creating and modifying rules, see Siebel Order Management
Infrastructure Guide
This chapter describes how customer service representatives (CSRs) use Siebel Orders for Fleet
Management. It includes the following topics:
The recommended methods of placing orders for accessorial products are summarized in Table 4.
The customer requires the accessorial product In this case, the accessorial product is identified
for every order. as part of the agreement with the customer, and
the rating engine will automatically add the
accessorial product to all the customer’s orders.
The customer requests the accessorial product In this case, the accessorial product is added to
for a specific order. the order as a separate line; see “Adding Order
Line Items for Fleet Management” on page 35.
The commodity transported requires the In this case, a product favorite is created that
accessorial product. includes the commodity and accessorial
product. This product favorite is added to the
order; see “Adding Product Favorites” on
page 36.
Spot quoting provides prices rates for shipments that are due to be shipped soon and that meet
certain requirements such as size, which the transportation provider must determine.
Spot quoting allows the customer service representative to price a movement of freight between the
origin and destination by collecting a limited set of data. The origin and destination location data can
be one of the following sets of data:
This partial data is passed to the rating engine, which returns the pricing for the more generic lane,
based on these partial location details. If the customer agrees to confirm the order based on this
price, the customer service representative must enter full location details before submitting the order
to Oracle Transportation Management.
To create orders in Siebel Orders for Fleet Management, perform the following tasks:
1 “Creating the Order Header for Siebel Orders for Fleet Management” on page 33
2 “Adding Order Line Items for Fleet Management” on page 35
NOTE: When you create the header, you must select a tendering party and the party liable for paying
for the order, which are accounts already entered in the Siebel application, as described in Siebel
Applications Administration Guide. You must also select an origin location and destination location,
which are locations already entered, as described in “Creating Locations for Fleet Management” on
page 15. If this information has not already been entered, you must enter it before creating the order
header.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
3 Drill down on the new record by clicking the Order Number field.
4 Complete the necessary fields in the order header. Some fields are described in the following
table.
Field Description
Liable Party Select the party liable for paying for the order.
Hold Indicates whether the order has been placed on hold. For
example, orders might be placed on hold because of issues
with the customer’s credit.
Origin Location Select the origin location where the order is picked up. This
list includes all the addresses of the tendering party.
Destination Location Select the destination location where the order is delivered.
This list includes all the addresses of the tendering party.
Start Req PickUp Enter the earliest pickup date and time that the customer can
accept.
Field Description
End Req PickUp Enter the latest pickup date and time that the customer can
accept.
Start Req Delivery Enter the earliest delivery date and time that the customer
can accept.
End Req Delivery Enter the latest delivery date and time that the customer can
accept.
Division Enter the division for the line of business for the order.
Revision The revision number of the order. For more information, see
the section about revising an order in Siebel Order
Management Guide.
Total Price Displays the total price after a solution and price are returned
by the rating engine.
5 Complete any necessary, additional fields in the More Info form. Some fields are described in the
following table.
Field Description
Tender Last Name Select your contact at the tendering party. The first name is
filled in automatically.
Total Stops Displays the total number of stops for the order.
Gross Weight Displays the gross weight of the commodity being delivered.
Weight UOM Displays the unit of measure for the gross weight.
Field Description
You can also add groups of line items to the order, instead of adding line items individually, as
described in “Creating Product Favorites for Fleet Management” on page 19.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 In the Line Items list, add new records, and complete the necessary fields. Some fields are
described in the following table.
NOTE: There must be one record for the transportation product, which is the default record
created because you chose Transportation Order as the order type. Optionally, you can add other
records for accessorial products.
Field Description
Accepted Price The rating engine will return values for these fields after you
get the solution for this order.
Pricing Method
NOTE: The rating engine can also add new line items to the
Price Offered
order, such as specific accessorial products or special
Counter Offer services.
Before CSRs can use product favorites, the product administrator must define them. For more
information, see “Creating Product Favorites for Fleet Management” on page 19.
The product administrator can associate product favorites with an account, a line of business, or an
agreement, and can create an effective start date and end date for the product favorite. When the
customer service representative creates an order, the customer service representative must choose
an account and line of business for the order, and can choose an agreement for the order. When the
customer service representative chooses a product favorite to add to the order, product favorites are
available to add to that order only if they meet the following conditions:
■ Start and End Effective Date. These two fields in the product favorite are checked against the
order header’s origin start-requested date. A product favorite is available to add to the order only
if the order header’s start-requested date is between the product favorite’s start-effective date
and its end-effective date.
■ Line of Business, Agreement, and Account. If these fields in the product favorite are not null,
then a favorite is available to add to the order only if the value of these fields in the product
favorite match the value of the corresponding field in the order header.
■ When you add the favorite, the products in that favorite are displayed in the Products list.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 In the Favorites list, select a product favorite that you want to add.
The line items for that product favorite are displayed in the All Line Items list.
3 In the All Line Items list, select the line items that you want to add.
The selected line items are added to the Line Items view for the order.
The simplest order is a one-way delivery with no accessorial products. For this order, you have one
line item with the product named, Transportation. This line item has two stops:
■ One stop is of the type pickup (Origin) and is the same as the origin location for the delivery as
a whole, which is in the order header.
■ The other stop is of the type DROP-OFF (Dest) and is the same as the destination location for
the delivery as a whole, which is in the order header.
These two stop records are created automatically, based on the information you entered in the order
header, when you click the Create O-D Pair button.
More complex deliveries, with intermediate pickups or deliveries, might have additional stops, for
example, one stop for each pickup or delivery. You must add a stop record for each of these stops.
Accessorial products also have stops where they apply. For example, if the customer wants the
commodities to be unloaded by hand at two stops, you add these two stops to an accessorial product
that might be named Unload by Hand.
There can be more than one stop at one location. For example, a single order might include the
following:
■ Pick up in the Chicago warehouse and drop off in the Detroit store.
■ Pick up in the Detroit store and drop off in the Chicago warehouse.
In this case, this one order has two stops in the Chicago warehouse on two different dates.
NOTE: All stops must be locations that have already been entered. If they have not been entered
already, enter them as described in “Creating Locations for Fleet Management” on page 15.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
Records are added to the Stops list for the origin and destination stop, with information based
on the origin and destination that you entered in the order header.
3 To add additional stops, add a new record to the Stop list for each stop, and complete the
necessary fields. Some fields are described in the following table.
Field Description
The list in the Location dialog box includes only locations that
are already associated with one of the line items in the order,
so you might have to use the New button to add more
locations to it.
Status Displays the status of the delivery at this stop. For more
information on how the status is used, see “Checking the
Status of the Order” on page 46.
Req Start Enter the earliest time that the customer requests for the
delivery.
Req End Enter the latest time that the customer requests for the
delivery.
Planned Start After a solution is generated and selected, this field will
display the planned earliest delivery time.
Planned End After a solution is generated and selected, this field will
display the planned latest delivery time.
Appointment Requested Select this check box if the customer wants to create an
appointment with the delivery vehicle at this stop.
Appointment Confirmed Select this check box when the appointment is confirmed.
Distance Displays the distance between this stop and the previous
stop, which is provided by the integrated back-office
application.
Distance UOM Displays the unit of measure used in the distance provided by
the integrated back-office application.
b Add records to the Stop list, and complete the necessary fields, as described in Step 3.
The stops are given new sequence numbers, based on their start and end times.
■ When the customer service representative adds the product favorite to the order, an order line
item is created for each product favorite line item.
■ When the customer service representative creates a stop record for the appropriate order line
item, the action is automatically added for that stop.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
3 In the Actions list, add records for each action, and complete the necessary fields. Some fields
are described in the following table.
Field Description
You must add a commodity record for every combination of a pickup and delivery. For example, if
you are picking up 1,000 cases of frozen food at a warehouse, and you are delivering 600 cases to
supermarket location A and 400 cases to supermarket location B, you must create two commodity
records:
■ One commodity record says you pick up 600 cases at the warehouse, and deliver them to
supermarket location A.
■ One commodity record says you pick up 400 cases at the warehouse, and deliver them to
supermarket location B.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 In the Commodity list, add records for each commodity being delivered, and complete the
necessary fields. Some fields are described in the following table.
Enter only the fields that apply to the commodity being shipped. For example, if the commodity
is shipped and billed by units, such as pallets, enter values in the Packaging, PKG/Unit, Shipping,
and Ship Units fields. However, if the commodity is shipped and billed by weight, enter values in
the Weight and Weight UOM fields.
Field Description
Field Description
PKG/Unit Enter the number of packages for each shipping unit. For
example, if the product is packaged in cases and shipped on
pallets, and there are 100 cases on a pallet, then enter 100.
Shipping Select the method used for shipping, for example, pallets.
Ship Units Select the number of shipping units in this pickup and
delivery. For example, if you are delivering four pallets, enter
4.
Weight UOM Enter the unit of measure for the weight of the commodity.
Dimensions UOM Enter the unit of measure for the height and width of the
commodity.
Over Dimension Indicates whether the freight is larger than the vehicle’s
recommended load.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 In the Stops list, add new records, and complete the necessary fields.
Add these records in the same way that you add stops to line items, as described in “Adding Stops
to the Order” on page 36.
On the other hand, an action might apply to the entire stop and not to a specific commodity. The
order provides the flexibility to implement either approach.
2 In the Actions list, add records for each action for this stop, and complete the necessary fields.
Some fields are described in the following table.
Field Description
The minimum data set necessary to request a solution includes the following set of fields: Liable
Party, Tendering Party, Partial set of Origin or Destination fields (if no Agreement is specified), Full
set of Origin or Destination fields (if Agreement is specified), Requested Start Date, and Requested
End Date.
After entering all of these order details, the customer service representative gets the possible
solutions that are available for the delivery dates and time slots that were specified:
■ The Siebel application verifies that the minimum set of data needed to generate a solution is
present.
■ The Siebel application calls the rating engine of Oracle Transportation Management, making an
external Web service call to Oracle Transportation Management, and providing the order data
structure in the request message.
■ The Siebel application automatically navigates the user to the Solutions view and displays the
list of solutions.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
Choosing a Solution
The customer service representative asks the customer to choose among the solutions that have
been generated.
After the rating engine generates solutions, the following information appears in the Solutions view:
■ The Solution list includes all the available solutions, with the planned start time, planned end
time, total price, and other information for each solution.
■ The Solutions Details list includes details for each solution, including service providers and modes
for each detail. If the order is multimodal, or includes several different pickups and deliveries,
the list might include several service providers.
■ The Solution Detail Pricing list includes the pricing for each Solution Detail, breaking the price
into elements, such as the basic transportation price, plus any other charges, such as the price
of accessorial services, or the price of special services.
If there is a contractual agreement with the customer, the customer can choose one of the solutions
and the published price displayed for it. If the customer does not have a contractual agreement, the
customer can select one of the solutions and the spot price displayed for it, or the customer can
choose one of the solutions and negotiate a different spot price.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
To choose a solution
1 View the possible solutions in the Fleet Management screen, Solutions view.
After you have clicked Get Ratings and Routes, the rating engine generates the solutions, and
the Siebel application navigates you to the Solutions view, where the solutions are displayed.
a Click the Select check box for the solution that the customer prefers.
b Click Save Order to save the order and this solution for later reuse.
a Click the Select check box for the solution that you want.
In the Line Items view, records are added representing the commodities and special services
in the order. In the Order Header, the value Accepted appears in the Status field, and the
total price of the solution appears in the Total Price field.
5 If the customer does not have a contractual agreement and wants to renegotiate the price of one
of the solutions:
a Click the Select check box for the solution that you want.
The Select check box must be checked so you can edit the solution.
b In the Solution Detail Pricing list, in the Customer Offer field, enter the customer’s offered price
for each of the products listed.
Some accessorial products have a nonnegotiable price, so the NON-Negotiable check box is
selected. The fields used for negotiating their prices are read-only. The rating engine
determines which items are nonnegotiable.
c If the customer and the customer service representative agree a price for the products in the
Solution Detail list, enter it in the Accepted Price field.
In the Order Header, the value Accepted appears in the Status field, and the total price
appears in the Total Price field.
For information about what information the Verify functionality checks and about how to configure
the Verify functionality to check different information, see “Configuring Validation for Verifying and
Submitting Orders for Fleet Management” on page 28. The same Verify functionality is called when you
submit an order, so it is not necessary to verify the order as a separate step before submitting it.
2 Either select the order that you want in the Orders list, or drill-down on the Order number field
of the order.
3 Click Verify.
If the customer wants to place an upsell order, the customer service representative can auto-create
a record for the new order and enter more details.
When the customer service representative clicks Auto-Create, the Siebel application displays the new
order. The customer service representative can do one of the following:
■ Click Auto-Create, navigate back to the current order later, and submit it.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 Ask whether the customer wants to place additional orders for any of the lanes listed in upsell
view. Some fields of the Upsell view are described in the following table.
NOTE: The lane is defined by the LOB in the header plus the origin and destination entered in
this view.
Field Description
NM If this lane is one of the targeted lanes, then Y is displayed.
Static Profit Displays the static profit for the last order placed by this
customer for this lane.
Count Displays the number of orders from this customer for this
lane in the last six weeks.
Accepted Price Displays the accepted price for transportation for the last
order placed by this customer for this lane.
3 If the customer wants to purchase a transportation product listed in the Upsell view:
A new order is created for the upsell lane, and you complete the details for this order in the
usual way.
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 Drill down on the record for the appropriate order by clicking the Order Number field.
If the customer contacts the customer service representative to ask about the status of the order,
the customer service representative can look at the order record to check the status of the order as
a whole, the status of each line item, the status of each stop, and the status of each action.
The values for these status fields change depending on the stage in the order creation and
fulfillment:
■ Immediately before submitting to Oracle Transportation Management, the values for these status
fields are:
■ When Oracle Transportation Management creates an order, the values for these status fields are:
■ When Oracle Transportation Management assigns the carrier, the values for these status fields
are:
■ When the carrier arrives and departs from the shipper, the values for these status fields are:
■ When the carrier leaves the consignee, the values for these status fields are:
■ When Oracle Transportation Management generates the invoice, the values for these status fields
are:
This task is a step in “Process of Creating Orders for Fleet Management” on page 32.
2 Drill down on the record for the appropriate order by clicking the Order Number field.
3 To check the status of the entire delivery, look at the Status field in the order header.
5 To check the status of the stops and actions for a given line item:
It is most common to select the line item for the transportation product, so you can see the
stops where the stops transportation has been completed.
c In the Stops list, look at the Status field for each stop.
d To check whether all actions have been completed for a stop, select the stop record, and look in
the Actions list at the Status field for each action.
6 To check the status of the stops and actions for a given commodity:
c In the Stops list, look at the Status field for each stop.
d To check whether all actions have been completed for a stop, select the stop record, and look in
the Actions list at the Status field for each action.
To revise an order
1 Check the status of the order.
For more information on the status, see “Checking the Status of the Order” on page 46.
2 If the status does not prevent the order from being changed, do the following:
b Change the data as needed, select a new solution, and submit the changed order in the same
ways used to create a new order.
For more information, see “Process of Creating Orders for Fleet Management” on page 32.
When you reject the revision of an order, the last active revision of the order that does not have the
status of Rejected is given the status of Active again. For example:
2 The user revises Order 12345. Order 12345 Revision 1 is set to Inactive, and Order 12345
Revision 2 is set to Active.
3 The user rejects Order number12345 Revision 2. Order 12345 Revision 1 is set to Active.
4 The user revises Order 12345. Order 12345 Revision 1 is set to Inactive. Order 12345 Revision
3 is set to Active.
5 The user rejects Order 12345, Revision 3. Order 12345 Revision 1 is set to Active.
NOTE: If you are working on the first version of the order rather than on a revision, clicking the
Reject button cancels the order, but saves the information about the cancelled order in the Siebel
database.
2 Either select the order that you want in the Orders list, or drill-down on the Order number field
of the order.
■ Click Cancel to set the status of the order to Cancelled and cancel the appropriate line items and
stops.
When you click Cancel, any line item or stop in the order that is not complete is updated with the
status of Cancelled, and Oracle Transportation Management cancels the instructions to pick up or
deliver at these stops. Line items or stops that already have the status of Complete are not updated
with the status of Cancelled.
After an order is cancelled, none of its versions can be revised. For example:
2 The user revises Order 12345 and then rejects the revision. Order 12345 Revision 2 is Inactive
with the status Rejected. Order 12345 can be revised, and the changes apply to Revision 1.
3 The user revises Order 12345 and cancels the order. Order 12345, Revision 3 is Inactive with
the status Cancelled. Order 12345 cannot be revised; none of the revisions can be changed.
Oracle Transportation Management might charge the customer cancellation fees for any parts of the
order that were completed before cancellation. The cancellation fee is set up in Oracle Transportation
Management, and not in the Siebel Business application.
If the customer wants to add any accessorial or special service products for the order to be cancelled,
these products must be added before cancelling the order, because an order cannot be revised after
being cancelled. First, revise the order to add the accessorial or special service products, if
necessary, see “Revising Fleet Management Orders” on page 48, and then cancel the order.
2 Either select the order that you want in the Orders list, or drill-down on the Order number field
of the order.
3 Click Revise.
5 Click Cancel.
6 Click Submit.
A L
actions 39 lanes 13
adding actions to orders 39 line items, adding to orders 35
adding commodities to orders 40 locations, creating 15
adding order line items 35
adding product favorites to orders 36 O
adding stops to orders 36 Oracle Fleet Management 7, 46
adding targeted lanes 13 Oracle Transportation Management 7, 42
Application Integration Architecture 7 order header, creating 33
order validation 28
C orders
canceling order 49 adding actions 39
checking status of orders 8, 46 adding commodities 40
choosing a solution 43 adding line items 35
commodities, adding to orders 40 adding product favorites 36
completing the order, scenario 8 adding stops 36
configuration canceling 49
picklists 21 checking status 8
score for upselling 12 creating the header 33
validation of cancel 30 process of creating 32
validation of submit 28 rejecting revision 49
validation of verify 28 status 46
creating locations 15 submitting 46
creating products 14 validating 44
creating the order header 33 verifying 44
CRM
See Siebel Customer Relationship P
Management picklists, configuring 21
product favorites
E adding to orders 36
Enterprise Business Suite Asset Lifecycle creating 19
Management 7 scenario 8
Enterprise Business Suite Financials 7 product types 14
Enterprise Business Suite Human products, creating 14
Resources 7
R
F rating engine 42, 43
favorites rating the order, scenario 8
See product favorites ratings, getting 42
rejecting revision of order 49
G routes, getting 42
getting ratings 42
getting routes 42 S
getting solutions 42 scenario for orders for fleet management 8
score for upselling 12