My Oracle Support Banner

High Level Message Wrongly Converting Long Account Numbers to Scientific Notation (Doc ID 2374920.1)

Last updated on MARCH 08, 2019

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.0.0 and later
Oracle Network Management for Utilities - DMS - Version 2.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:

NMS - Oracle Network Management System

On : 2.3.0.1.0 version, Web Call Entry

An interface is being set up to auto-populate the Call Entry application.  The problem is that when there is number sent through a high-level message that is more than 8 digits, it gets converted to scientific notation. This means that accounts numbers sent through this process are not being located.

Expect:

The account number should not get converted since this would result in breaking a match and the auto-population failing.

Changes

 The following custom configuration was added to the CallEntry.xml

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
References


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