Specials Characters Can Be Inserted Into Free-Text Fields & Causes E2B Failures

(Doc ID 1164993.1)

Last updated on APRIL 04, 2016

Applies to:

Adverse Event Reporting System - Version: 4.6.1 and later   [Release: 4.6 and later ]
Information in this document applies to any platform.


AERS 4.6.1.

It is possible to enter/insert special (illegal) characters into free text fields in AERS (most likely from copy/paste narrative or long text data from other programs).

These special characters get mapped into the E2B XML message and cause the submissions to fail.

Multiple cases are often submitted in one message, one failure can cause all submissions in that message to fail - leading to potentially late submissions.

There should be an automated method of preventing this from happening.


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