Order Release Actions Not Using the Parameter Set Defined by the User Preference (Doc ID 979985.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5.05 to 6.0.4 - Release: 5.5 to 6
Information in this document applies to any platform.
***Checked for relevance on 08-Jul-2011***

Symptoms


PROBLEM
------------------------
When setting the Parameter Set ID on the User Preference, the Parameter Set ID is not used for action ‘Unassign Order’ or when using the ‘Move to Shipment’ action.

EXPECTED BEHAVIOR
-----------------------
Expect parameter set ID selected on the user preference to be used when actions: ‘unassign order’ and ‘move to shipment’ are used

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Set a user and assign to him in user preference a parameter set ID of interest
2. Create two Order Releases
3. Bulk Plan both
4. Notice the Parameter Set ID (is the user preference set one) not the default
5. On one perform the Action of Unassign Order, and on the other Move Order to existing Shipment
6. Review the resulting logs for both and you will find both are using the wrong Parameter Set ID (the Default one)

Cause

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