Unable To Import And E2b - MESSAGEDATEFORMAT M2 Validation failed (Doc ID 1557332.1)

Last updated on NOVEMBER 25, 2016

Applies to:

Oracle Argus Safety - Version 7.0.2 and later
Oracle Argus Interchange - Version 8.1 to 8.1 [Release 8.0]
Information in this document applies to any platform.

Symptoms

Unable to Import E2B file:

An error appears in the import log " M2 Validation failed for incoming message. The following are the elements and values: Element: MESSAGEDATEFORMAT; MESSAGEDATE, Value: 204; 20130509163217'

10-May-2013 10:32:25 PM TCS : ========== Start Receive Process for File : C:\INCOMING\4.xml ==========
10-May-2013 10:32:25 PM TCS : >>DEBUG>> Profile Type: MSG
10-May-2013 10:32:25 PM TCS : >>DEBUG>> Enter Fn:ExtractXML_Header
10-May-2013 10:32:25 PM TCS : >>DEBUG>> Exit Fn:ExtractXML_Header
10-May-2013 10:32:25 PM TCS : >>DEBUG>> Enter Fn:ExtractXML_Header
10-May-2013 10:32:25 PM TCS : M2 Validation failed for incoming message. The following are the elements and values:
Element: MESSAGEDATEFORMAT; MESSAGEDATE, Value: 204; 20130509163217
10-May-2013 10:32:25 PM TCS : ========== Finish Receive Process for file C:\INCOMING\4.xml ==========

 

Changes

 The sample file

<ichicsrmessageheader>
<messagetype>ichicsr</messagetype>
<messageformatversion>2.1</messageformatversion>
<messageformatrelease>2.0</messageformatrelease>
<messagenumb>1_001</messagenumb>
<messagesenderidentifier>TestDrugM</messagesenderidentifier>
<messagereceiveridentifier>FDA</messagereceiveridentifier>
<messagedateformat>204</messagedateformat>
<messagedate>20130509163217</messagedate>
</ichicsrmessageheader>

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