Local Authority Returns An E2B R2 Acknowledgement For A Case Which Was Submitted In E2B R3 Format
(Doc ID 2516855.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Interchange - Version 8.1.2 and laterInformation in this document applies to any platform.
Symptoms
On Applications Oracle Argus Safety Version: 8.1.2
Submitted R3 E2B Report / Case returns an Acknowledgment (ACK) that cannot be processed by the Argus Interchange service.
The report is sent out as an R3 report that authorities acknowledge, but these authorities can only return ACK in R2 format.
The MDN is received correctly.
Error
28-Jan-2019 11:00:11 AM DEFAULT : Attached Acknowledgment file [\\10.254.4.80\COMMON\XXXXXL\DATA\IN\ack_ICSRACK_XXXXX_25-1-2019_16-3-1-549_JXXXXX.xml]
is not processed by ESM. ESM has searched all databases and is unable to find the following configuration
Please verify that the Primary Receive Agency Flag is checked in the Regulatory Authority Setup.
DTD version [1.1]
DTD release [1.0]
Active Profile [Y]
Profile type starts [ACL%]
the following is the Message Header Information:
Message Sender Identifier [XXXXX]
Message Receiver Identifier [XXXXX]
Message Number [873002]
File Type [XML]
ICSR Message Number [763895_777]
Sending an R3 report to authorities who are returning an R2 ACK because of technical limitations are hindering the correct processing of the ACK returned.
Cases are pending in EDI IN.
Potential impact on following reporting destinations:
| Bulgaria |
| Croatia |
| Denmark |
| Germany |
| Hungary |
| Ireland |
| Latvia |
| Lithuania |
| Malta |
| Norway |
| Portugal |
| Slovakia |
| United Kingdom |
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 |