Shipment Business Number (BN) Rule Definition Using Refnums Replacement Values Is Causing Java.Lang.NullPointerException (Doc ID 735143.1)

Last updated on APRIL 01, 2016

Applies to:

Oracle Transportation Management - Version: 5.5 to 5.5
This problem can occur on any platform.

Symptoms

-- Problem Statement:
On 5.5.03.02 :
When attempting to create a shipment using a new Business Number (BN) Rule Definition using Replacement value to control how the SHIPMENT_XID is created based on Shipment REFNUMS, the following error occurs:

ERROR
java.lang.NullPointerException
BN RULE REFNUM IS CAUSING JAVA.LANG.NULLPOINTEREXCEPTION

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:

1- Edit the Current Default Business Number Rule "SHIPMENT_XID.DEFAULT" and unchecked the Default
Flag.
2- Created new Business Number Rule with the bellow Rule Definition replacement for instance :

* Default: Checked
* Rule Definition: {r*:xml=REFNUM/BM}-{dddddddd:id=1}-{nnnn:contexts=1:start=1}


OR

* Rule Definition: {r*:xml=REFNUM/PO_NUMBER}-{dddddddd:id=1}-{nnnn:contexts=1:start=1}


* BN Type ID: SHIPMENT_XID
* BN Generator ID: PICTURE

3- When trying to plan the above mentioned OR, you get the JNLP error.

-- Business Impact:
The issue has the following business impact:
Due to this issue, users cannot use Business Number (BN) Rule Definition using Replacement value
to control how the SHIPMENT_XID is created based on Shipment REFNUMS.

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