Siebel Order Management Guide Addendum for Fleet Management > Administering Siebel Orders for Fleet Management >

Configuring Validation for Verifying and Submitting Orders for Fleet Management

When the user clicks the Verify button or the Submit button, two levels of the order are checked:

• Order validation. The fields in the order are checked for valid values.
• Solution validation. The pricing solution in Oracle Transportation Management or another fulfillment system is checked to see that it is still valid.

You can configure either or both of these levels.

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.)
• For all records, the following applies:
  • The field, Order Entry - Orders.Solution Valid, must be True.
  • The field, Order Entry - Line Items.Solution Valid, must be True.
  • The field, FM Stops.Solution Valid, must be True.

    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.

The following procedure describes how to modify the validation rules.

To modify the order validation rules

1. Navigate to the Administration - Data Validation screen, then Rule Sets view.
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.
3. Modify this rule set by adding, editing, or deleting rules.

   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.

All of the fields are automatically populated in the following ways:

• 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.