My Oracle Support Banner

After Installing CU5 RU5 Rate Conditions are Saved With XID Value Rather Than GID Value (Doc ID 847483.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 5.5.05.05 to 5.5.06 [Release 5.5]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

-- Problem Statement:
On 5.5.05.05, When saving a Rate Record Condition that checks for a Reference Qualifier, it is saved with the qualifier XID (i.e. domain name removed). This causes the rate condition to fail as the condition checked uses the GID column but checks with a value without the domain name.
This started to happen only in CU5 RU5

EXPECTED BEHAVIOR
Expect that the Reference Qualifier is saved with the domain name

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Set up a rate record with a condition that checks for an Order Release Reference Number of Shipment Reference Number qualifiers that are in a user's domain
2. See that the check is saved without the domain name
3. Try to plan an order that uses the Rate and see that the order fails to plan due to the rating failure

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.