Sourcing

Solve Scenario

This page is accessed via:

  • Sourcing > Process Management > Solve Scenario
  • Sourcing > Bid Analysis > Scenario > Actions > Solve Scenario

The Solve Scenario action determines how to make awards to transportation service providers.

You use parameters and a sourcing rule set to create rules that determine how the solve process builds a solution. Oracle Transportation Sourcing uses parameters to define/control events at the project level and a sourcing rule to set to influence how the solve process builds a solution for lanes or sets of lanes.

Parameter Set Definition

Also, to avoid parameter conflicts, be sure you have selected the default parameter set on the Project page. If necessary, create a parameter set that includes the following values:

  • CREATE INTEGER AWARDS -0
  • PROCUREMENT SOLVER MAXTIME -0
  • PROCUREMENT SOLVER PERCENT OPTIMAL -0

Solving a Scenario

Before running this action, be sure to include all of the bids in the bid round by using the Bid Include action, and use the Commit Bids in Bid Round action to change the commitment status from COMMITMENT_NEW to COMMITMENT_COMMITED.

  1. Enter a solution ID in the Solution ID drop-down list.
  2. Select the Award Backup Service Providers check box if you want to have a backup carrier in place. You may want to do this for important lanes. The awards for backup drivers is always 0.
  3. If you selected the Award Backup Service Providers check box, enter the Number of Backup Service Providers Per Lane to Award. For a very important lane, you may want a couple backups.
  4. If you accessed the page from Scenario actions, and you want to run the action in the background, accept the default of Yes for the Run Job in Background field. The server can time out while waiting for a result if the action is run in the foreground for a large data set. Hence, for large data sets, you need to run the action in the background.
  5. Designate a contact in the Contact ID field if you selected Yes to Run Job in Background. When the action finishes, an email will be sent to the contact. Email notification is the only communication method even if fields are populated for other communication methods. There is no results page so the email notification is the only notification.
  6. If you are running cluster scalability, specify a cluster to which this request should be assigned.
  7. Enter a User Role. When you run, publish, or schedule a recurring process, you can specify the user role used to perform the process, just like when you run agents. The user role can be used to specify a separate VPD role or another domain to run the agent. When a recurring process is modified, the user role of the recurring process can be modified as well.
  8. Select a Log Profile to generate focused logging when reproducing an error for the specific action. You cannot select a log profile when you choose to schedule a process, as automatic generation of action logs is not supported.
  9. Select Execute, Publish, or Schedule to determine when the process will be executed.
  10. Click Submit.
  11. The page will appear blank initially while processing.
  12. Click Refresh.

Related Topics