BN Rule Including LATEPICKUP Ignored In Order Release ID
(Doc ID 1486165.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.2.4 and laterInformation in this document applies to any platform.
Symptoms
A BN Rule that includes LATEPICKUP is part of an inbound XML. This part of the BN Rule is not getting included on the ID of the Order Release.
Example: S{rrrrrr:padchar=0:id=1:xml=SOURCE}{r*:id=2:xml=LATEPICKUP:substring=2,4}{r*:id=3:xml=LATEPICKUP:substring=5,7}{r*:id=4:xml=LATEPICKUP:substring=8,10}{nn:contexts=1,2,3,4:start=01}
To reproduce:
1. Navigate to Business Process Automation -> Integration -> Integration Manager -> Upload an XML/CSV Transmission
2. Upload XML
This creates an Order Release. It is expected to include the pickup date portion that is on the XML, as follows:
20120308170000
<Timezone>
+01:00
N
N
For example, the ID should be:
S = Prefix
00000A = Source Location padded to 6 chars
12 = Year
03 = Month
08 = Day
09 = Counter
But the Year, Month and Day are missing.
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 |