My Oracle Support Banner

English Term with Currency='Y' Is Not Encoded when XML Is Imported (Doc ID 1642502.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Argus Safety - Version 6.0.2 to 6.0.6 [Release 6.0]
Information in this document applies to any platform.


English Term with E-Currency = 'Y' is not encoded when:
--the case was created by importing an E2B XML file,
--the Term is specified by LLT Code in the E2B XML file,
--E-Currency is 'Y' but J-Currency is 'N' for the Term,
--and the environment is having Meddra-J (both E and J terms) loaded.

Users are unable to recognize the Terms are actually not the term of Meddra
dictionary, or actually the term of Meddra dictionary but currently not
encoded unexpectedly.

In the case which was created by importing the XML file, the following
fields are observed as not encoded:
Case Form >> Events >> Event >> (event-name):
--Event Coding = Red-Cross icon
--Hierarchy of Event Coding = No Terms are displayed on any levels
Case Form >> Products >> (product-name) >> Drug >> Product Indication:
--Reported Indication = <English-Term>
--Coded Indication = <null>
Case Form >> Patient >> Patient >> Other Relevant History:
--Coded PT / Description of condition LLT / Indication PT / Reaction PT
field displays <LLT-Code> number value instead of Term Text.

How to Reproduce:
Prepare an E2B XML file.
The XML file contains non-PMDA sender agency and LLT code for the DTD items
corresponding to the above fields.
No Japanese texts are contained in this XML file.
Import the XML file, and Accept E2B for the imported E2B.
Open the newly created case by case form.





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

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