Tracking Event Match Order Release - Time Zone Is Missing On Order Release Events
(Doc ID 2725066.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.4.3 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior:
When a Tracking Event created to Match Order Release -Time zone is missing in the Order Release Events
Expected Behavior:
Timezone should be shown in the Order Release tracking events
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an Agent as below
Agent Header: TRACKING EVENT - PROCESSING REQUEST FILING RESPONSE -COMPLIANCE
Action :
MATCH SHIPMENT: By Shipment ID
ASSIGN VARIABLE: $SHIPMENT_ID, GET_SHIP_GID (Saved Query :SELECT DISTINCT
SSH.SHIPMENT_GID FROM SS_STATUS_HISTORY SSH, SHIPMENT S WHERE S.SHIPMENT_GID
= SSH.SHIPMENT_GID AND S.PERSPECTIVE = 'B' AND SSH.I_TRANSACTION_NO = '$GID')
MATCH ORDER RELEASE: By Order Release ID (Saved Query ID: SELECT
ORDER_RELEASE_GID FROM ORDER_MOVEMENT OM WHERE SHIPMENT_GID=$SHIPMENT_ID)
2. Search for a shipment
3. Add a Shipment Tracking Event as per the Agent Set up
4. Verify the Order RELEASE Event and it does not show the timestamp
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 |