My Oracle Support Banner

Business Number Rule with Character 'C*' is Throwing an Error: 'The Sequence Null For Rule Is Exhausted' (Doc ID 981015.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Transportation Management - Version 6.0.2 and later
Information in this document applies to any platform.


When using OTM Version 6.0.2 and attempting to have a Business Number Rule generate a value that contains an Alpha character, using the 'C*' instruction, it is expected that the Alpha character will move from A to B, to Z and then onto AA and so on. However once Z is reached the rule is generating an error as follows:

The sequence null for rule is exhausted

at sun.reflect.GeneratedConstructorAccessor355.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
at java.lang.reflect.Constructor.newInstance(
at glog.util.exception.GLException.factory(
at glog.util.exception.GLException.factory(
at glog.util.exception.GLException.factory(
at glog.server.bngenerator.BNSequence.increment(
at glog.server.bngenerator.BNSequence.increment(
at glog.server.bngenerator.picture.BNPictureSegment$Sequence.increment(
at glog.server.bngenerator.picture.BNPictureGenerator.perform(
at glog.server.bngenerator.picture.BNPictureGenerator.perform(
at glog.server.bngenerator.BNEngine.generateWithBNSequence(
at glog.server.bngenerator.BNEngine.generate(
at glog.server.bngenerator.BNEngine.generate(
at glog.server.bngenerator.BNSessionBean.testBNG(
at glog.server.bngenerator.BNSessionServerSideEJBWrapper.testBNG(
at glog.server.bngenerator.BNSessionHome_7sdgcx_EOImpl.testBNG(
at glog.server.bngenerator.gen.BNSessionSkel.testBNG(
at glog.server.bngenerator.gen.BNSessionSkel.exec(
at glog.webserver.wrapper.SkelImpl.execDispatch(
at glog.server.wrapper.WrapperSessionBean.execDispatch(
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(
at weblogic.rmi.cluster.ClusterableServerRef.invoke(
at weblogic.rmi.internal.BasicServerRef$
at weblogic.rmi.internal.BasicServerRef.handleRequest(
at weblogic.rmi.internal.BasicServerRef.access$300(
at weblogic.rmi.internal.BasicServerRef$

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

1 - Log onto an OTM 6.0 system.

2 - Navigate to: Business Process Automation > Power Data > Business Numbers > Business Number Rules.

3 - Click NEW

4 - Set the following:
ID: As needed.
BN Type: MAWB (or other)
Rule Definition:
BN Generator: PICTURE

5 - Click Finished.

6 - View the BN Rule

7 - Click Actions > Test BN Rule.

8 - Enter Shipment ID: 01004

9 - Click Save

10 - Click OK

11 - Repeat until the Letter in the BN reaches 'Y', so the value is '09Y00001'

12 - Test one more time.

13 - Because the C* was used is is expected that the Y moves to Z and then AA, per Online Help in the Alphabetic Instructions section:

"An asterisk after the last "c" indicates that the sequence has no maximum length. For example, {c*} specifies A, B, C,..., AA, AB, AC,..., ZZ, AAA, AAB, etc."

14 - The sequence null for rule is exhausted


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

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