How to Limit the Number of Order Releases Being Converted During the Convert Order Process
(Doc ID 1297740.1)
Last updated on MAY 06, 2022
Applies to:Oracle Transportation Management - Version 6.0 to 6.2.0 [Release 6 to 6.2]
Information in this document applies to any platform.
Many clients have experienced long run times for the convert order processes due to the number of orders and shipments they have on their OTM instance. This is especially true for clients that do not purge shipments and orders.
The goal of this document is provide information about reducing the number of orders being converted during after migrating to OTM version 6.x and running the convert order process.
The Order conversion needs to be run in steps:
Step 1 - convert with SQL script convert_orders.sql
Step 2 - convert with java process
In Step 1 the convert_orders.sql is used to convert orders on shipments with simpler structures. In Step 2 a java process is used to convert orders on shipments with more complicated structures. The reason this is broken up into a two step process was to improve the overall performance since we are able to do bulk inserts for the order movements needed for the simpler shipments while the more complex shipments need to processed one at a time.
Currently the convert_orders.sql does not give the user any controls and it will convert all orders satisfying it’s criteria in the database. The Java process does allow for some flexibility by taking a starting date as a parameter. With the date provided the Java process will convert all orders with INSERT_DATE >= starting date.
Whether you are running the convert_orders.sql or the Java process OTM distinguishes the converted orders from non-converted orders the same way, through the new OTM_VERSION field on the ORDER_RELEASE table. Unconverted orders will have OTM_VERSION set to null and converted orders would have OTM_VERSION set to 6.0.
Note: Be sure and install the latest Roll Up Patch for your OTM Version before running the convert order process. This will ensure you don't encounter issues reported previously by other clients.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document