Issue with Migration Of Order Releases to 6.0 Version of Oracle Transportation Management
(Doc ID 1318740.1)
Last updated on JULY 09, 2014
Oracle Transportation Management - Version: 6.2.1 and later [Release: 6.2 and later ] Information in this document applies to any platform.
When executing the order convert scripts as part of the upgrade to 6.2, many order releases are not converted to otm_version = '6.0' When further checked, its found that most of the order releases which already had order movement, but the Order Movements were not planned on any shipment were not converted. It is also noticed that convert_orders_with_oms procedure in the convert_orders package seems to be ignoring the above business case. The problem is with the business case where, OR already have OM created before the upgrade and convertion script is run, but OM is not planned on a shipment. In the ORDER_RELEASE table for a problematic order release (with pre-existing Order Movements) for which the order convert scripts have been executed , the OTM_VERSION field on the ORDER_RELEASE table is not getting updated to '6.0'
When any attempt to plan any such OM is made, OTM throws below error:
"As part of the 6.0 migration process all existing planned orders should have been converted to the new 6.0 structure. Serious problems can occur if they were not converted after migration. This action encountered order movements for order releases that have not yet been converted to the new 6.0 shipment structure. Please convert all planned orders to the new structure before attempting any modification. The process for modification is available under Order Management Process Control.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms