Oracle Transportation Management v5.0 Updating LANE via powerdata does not remove some info from X_LANE
Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 5.0
This problem can occur on any platform.
In version 5.0 clients have reported that changing LANE information via powerdata does not update the X_LANE record as expected.
If the rate record is currently based on STATE/PROVINCE and the rate record is changed, via the rate edit function, to a region based rate, the STATE/PROVINCE information is removed and the new region info is updated as expected.
If a client attempts to change the LANE record associated with the rate via powerdata from a lane based on a specific geo hierarchy, like STATE/PROVINCE, to a lane that is region based the system does not remove the original STATE/PROVINCE information.
The system works as expected when a lane is changed from a region based lane to a lane that covers a specific geo hierarchy, like STATE/PROVINCE, then the region information is removed from the X_LANE record as expected.
Clients are expecting the x_lane record to match the lane record after they are modified via the rate record itself or via powerdata
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Create a rate record that is based on a specific geo hierarchy, like STATE/PROVINCE
2. Via SQL find out the lane/x_lane associated with rate
3. Edit the lane in powerdata and change it from a STATE/PROVINCE to region based
( Be sure to leave the STATE information on the second page on the lane screen, just remove
the geo hierarchy information and add the region information and save the lane. )
4. Check the X_LANE table and you should see the SOURCE_PROVINCE_CODE and
DEST_PROVINCE_CODE is still listed as well as the region information that was recently
NOTE: This only happens when the LANE is edited via powerdata and changed from a specific geo hierarchy to be region based.
-- Business Impact:
The issue has the following business impact:
Clients may notice that the data in the x_lane is not correct and the Lane Summary Report from Procurement may display additional/incorrect information.
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