My Oracle Support Banner

Cost Allocation Using Dim Weight Factor Does Not Work In Certain Circumstances (Doc ID 989514.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Transportation Management - Version 5.5.05 to 5.5.05 [Release 5.5]
Information in this document applies to any platform.

Symptoms

On OTM version 5.5.05.07 when attempting to allocate by Dimensional Weight the following error occurs.

ERROR
-----------------------
Error Exception AllocationMetric::adjustOrderCosts - ERROR - allocation stopped to prevent endless loop.

at sun.reflect.GeneratedConstructorAccessor110.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at glog.util.exception.GLException.factory(GLException.java:413)
at glog.util.exception.GLException.factory(GLException.java:390)


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

1. Set up an Allocation Rule where each of the 3 parts allocate by Dimensional Weight (100%)

2. Add the Rule to an Allocation Profile and make it the Default profile.

3. Have an Order Release with the DIM factor attached.

4. Plan the order onto a Shipment.

5. Note the Shipment has no Dimensional weight value calculated.

6. Attempt to Allocation.

7. The allocation fails and the error is seen.

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.