Allow JSON Numbers with High Precision and Scale

For JSON numbers with high precision and scale, Oracle Integration automatically converts the number to four decimal places. To prevent this conversion, you have several options based on the adapter you are using.

  • For the REST Adapter, you must set the Allow High Precision Numbers connectivity property in the mapper to allow JSON numbers with high precision and scale.

    The default value for this connectivity property is false. Oracle Integration internally restricts the precision scale to four (decimal places) by default. Set this property to true for a higher precision scale. Use this property value carefully because undefined precision does not mean infinite precision.


    The Target tree shows the Connectivity Properties section, which includes entries for Post Query String, Use Form URL Encoding, Enforce Empty JSON Object Payload, Enforce Absolute Endpoint URI, Skip Control Characters, and Allow High Precision Numbers.

  • For all other adapters that supply a schema for response processing, the following schema annotation is included.
    <xs:schema xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" nxsd:version="JSON" nxsd:allowHighPrecisionNumbers="true">

    If you receive a REST response with more than 10 decimal places, Oracle Integration converts it to XML, but does not round off the values.

    If you do not use this schema annotation, the value is rounded off at four decimal places.