Numeric Data Loaded into Text Field using EPMA Data Synchronizer Appears with Scientifc Notation (Doc ID 1330905.1)

Last updated on MARCH 08, 2017

Applies to:

Hyperion Planning - Version: 11.1.1.3.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Numeric data loaded into a Planning text type member via the Data Synchronizer is stored incorrectly in the Planning repository.

When loading a numeric  string, invoice number for example, into a cell that has been defined as having a data type of text, the value is stored differently in the HSP_TEXT_CELL_VALUE than if the value had been entered directly via a Planning form.

Example:

The following numbers when loaded via the Data Synchronizer: 3000290972; 1457, are stored as 3.000263193E9 and 1457.0

If you view this data in a Planning Web form it appears as 3,000,290,972 and 1,457.
However when this data is viewed via a Financial Report (FR) it displays the numbers as they are stored in the database: 3.000263193E9 and 1457.0


Cause

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