Search Results optimize_across_trips

Overview

The concurrent program OPTIMIZE_ACROSS_TRIPS belongs to the CSR - Scheduler product module within Oracle E-Business Suite. Its user-facing name is Optimize across Trips, and the program is documented as Enabled: Yes in both the 12.1.1 and 12.2.2 ETRM repositories. The stated purpose, per the ETRM metadata, is to "Optimize the trips of the Selected Resources or Resources in the Selected Territories."

Functionally, the program performs a cross-trip optimization pass. Rather than optimizing each trip independently, it considers a set of trips belonging to one or more selected resources (or resources grouped within selected territories) and re-sequences the work assigned to them to reduce travel time, mileage, or other optimization costs. This is distinct from single-trip optimization, since the optimizer examines the aggregate schedule and redistributes or reorders tasks across the affected trips. The program is therefore typically invoked after trips have been created — manually or by an earlier planning or scheduling process — when a planner wishes to consolidate, rebalance, or refine the resulting routes.

Execution Details

The documented execution details for OPTIMIZE_ACROSS_TRIPS are:

• Execution Method: Java Concurrent Program
• Argument Method: Standard
• Executable: OPTIMIZE_ACROSS_TRIPS
• Execution Filename: AutoOptimizer
• Subroutine Name: (not specified in the ETRM metadata)

Because the execution method is a Java Concurrent Program, the runtime is hosted by the Oracle E-Business Suite Java concurrent processing framework, and the actual optimization logic resides in the AutoOptimizer class. The Standard argument method indicates that the program accepts a fixed set of defined parameters, rather than a free-form or token-based argument list, which means the parameter window is generated from the registered concurrent program arguments.

How to Run

Planners and schedulers submit this program through the standard Submit Request (SRS) window, using the responsibility that owns the CSR - Scheduler concurrent programs and request group. The user-facing request name is Optimize across Trips. After submitting, the request can be monitored in the Requests window, and completion status is reported through the standard concurrent manager output file.

Since the program optimizes either resources or territories, the parameter window typically presents a selection for the scope of the optimization (resources versus territories) together with the relevant resource or territory identifiers. Planners should run the program during periods of low scheduling activity, because it operates on a set of trips that may also be edited interactively. The resulting trip assignments should be reviewed before dispatch, to ensure the optimizer's decisions comply with business constraints such as time windows, capacity, and driver qualifications.

Related Objects

OPTIMIZE_ACROSS_TRIPS is closely associated with other CSR - Scheduler optimization and trip-management components. Commonly related objects include:

• Trips and trip stop interface data — the source records the optimizer evaluates and updates.
• Single-trip optimizer programs — companion concurrent programs that optimize one trip at a time and are often run before cross-trip optimization.
• Resource and territory definitions — the selection basis for the program's parameters.
• Scheduler planning and dispatch windows — where the optimized trips are subsequently reviewed, adjusted, and released.

Administrators and implementers should consult the ETRM 12.2.2 entry for the authoritative metadata and verify any environment-specific argument registrations, since the ETRM excerpt does not enumerate individual parameter names.