"Invalid DateTime" (11001, 1850) In CCB & MWM Integration Due To Inconsistent OUAF Time Configurations
(Doc ID 2187147.1)
Last updated on JUNE 05, 2017
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.1.0 and laterOracle Process Integration Pack for Oracle Utilities Field Work - Version 3.1 and later
Oracle Utilities Customer Care and Billing - Version 2.4.0.0.0 and later
Information in this document applies to any platform.
Symptoms
On : FW PIP 12.1, CCB 2.4, MWM 2.1
ACTUAL BEHAVIOR
---------------
CCB & MWM Integration Error
MWM transaction processed and sent the message to PIP. But, it failed to update the CCB record to complete due to date time issue.
Customer has not done any customization and all three systems are using the same nls date format and are using AMERICAN/Eastern timezone date format. It seems PIP is doing translation of date/time into the format not acceptable by CCB.
Error log from CCB:
****Error At: 22/09/2016 12:02:08:767 OH\58 Origin IP:10.229.120.67 user: SYSUSER XML length:5964 Error Number:1016
Unexpected error during request processing. (Server Message)
Category: 11001
Number: 1850
Call Sequence:
Program Name: ServiceBeanSessionHelper$1$1
Text: Input request field Dispatch Date/Time has an invalid value. Invalid DateTime value 2016-09-22T10:22:20-04:00, expected in format YYYY-MM-DD-HH.MM.SS.
Description:
Table: null
Field: null
Unexpected error during request processing. (Server Message)
Category: 11001
Number: 1850
Call Sequence:
Program Name: ServiceBeanSessionHelper$1$1
Text: Input request field Dispatch Date/Time has an invalid value. Invalid DateTime value 2016-09-22T10:22:20-04:00, expected in format YYYY-MM-DD-HH.MM.SS.
Description:
Table: null
Field: null
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! |