Error ACK Created After Importing ICSR Using EMA R3 Profile
(Doc ID 2936138.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.2.3 and laterInformation in this document applies to any platform.
Symptoms
The imported ICSR does not populate in (menu) Reports > ICSR Pending after importing it using EMA R3 message profile.
Instead, the imported ICSR appears with failure status in (menu) Reports > Processed ICSR and then Argus generates error ACK.
However, there is no details in ACK <acknowledgementDetail> so it is unknown why this ICSR importing failed.
Steps:
- Import ICSR (xml) using EMA R3 message profile
** Note that this reporting destination does not have the auto-accept ICSR settings in Codelist: reporting destination
- Go to (menu) Reports > ICSR Pending
- The imported ICSR does not display
- Go to (menu) Reports > Processed ICSR
- Select "Failure" in the "Import Status" filter and press the [Retrieve] button
- Imported ICSR displays with "Failure / Errors" status
- Argus generates error ACK which is ACK.B.r.6 (CR) and ACK.A.4 (AR).
The text in ACK <acknowledgementDetail> contains only warning/comments message . Thus it is unknown why this ICSR importing failed.
Changes
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 |
Changes |
Cause |
Solution |