BPEL Process Cannot Map Java Decimal/Long in Scientific Format to DB Number Properly (Doc ID 1284966.1)

Last updated on APRIL 21, 2011

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.4 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

BPEL sometimes adds an extra zero at the end of a NUMBER data type parameter when it is mapped from a java long scientific exponential format data (ex. 2.1E2).
For example a client consumes a web service changes a format of decimal data type (ex. "212121210") to exponential format (ex. "2.1212121E8").
This input is passed to a NUMBER parameter of a procedure in the database.
The procedure stores this parameter in a table. The stored number is "2121212100" instead of "212121210". There's an extra zero at the end.

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