My Oracle Support Banner

FDA E2B (R2) transmission failed at EDI In (Doc ID 2762268.1)

Last updated on MARCH 22, 2021

Applies to:

Oracle Argus Safety - Version 8.2 to 8.2.2 [Release 8.2]
Information in this document applies to any platform.

Symptoms

In the regulatory report tab, final FDA E2B (R2) is generated.

When transmitting this report, E2B transmission failed at EDI In with the red icon on Worklist > Bulk ICSR transmit.

The following error appears in the ESM transmission log
------------------------------------
: Unable to encode XML string due to following reason

Error has occurred on Line: 0, Source Text: , Error Code: 0
------------------------------------

Note:
In the regulatory report tab, delete the failed report, re-schedule the report and generate the final report by clicking the final link.
But the transmission fails with same errors while transmitting the report.


Steps:
1. In regulatory report tab, schedule FDA E2B (R2)
2. Lock the case
3. Click the final link and confirm that E2B viewer appears properly
4. Save the case
5. Confirm that report status is set as "Generated" with the generated date
6. Transmit the report
7. Monitor the report transmission from (menu) worklist > Bulk ICSR transmit
8. Transmission failed at EDI In with a red circle icon

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.