5.0 OTM INTEGRATION -SHIPMENTSTATUS INTERFACE - DOESN'T LOOK UP STOP NUMBER (Doc ID 459704.1)

Last updated on JULY 09, 2014

Applies to:

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

Symptoms

Issue observed in GC3v50-P20061031

When modifying an existing ShipmentStatus xml to use a different stop location
reference number, it is observed that the interface works when the location reference number qualifier is GLOG but not when the qualifier is DUNS.

Error as below occurs:
:
<TransmissionReport><TransmissionNo>3152673</TransmissionNo><SenderTransmission
No>214ES3</SenderTransmissionNo><IntegrationLogMessage><ILogSeqNo>8246423</I
LogSeqNo><ITransactionNo>12182821</ITransactionNo><ObjectGid><Gid><Dom
ainName>PLAN</DomainName><Xid>577823</Xid></Gid></ObjectGid><Wri
ttenBy>TRANSACTION_PROCESSOR</WrittenBy><IMessageClass>E</IMessageClass><IMe
ssageCode>TRANSACTION_EXCEPTION</IMessageCode><IMessageText>CAUGHT THE FOLLOWING
EXCEPTION WHILE PROCESSING TRANSACTION: Related shipment stop number must be provided for event group EST_ARRIVAL at sun.reflect.GeneratedConstructorAccessor233.newInstance(Unknown Source)>


.

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