A work around solution is to make the run time to use BigDecimal::compareTo() method while performing consistency check. This method compares the 'value' alone while comparing two objects. The place where you add this piece is OracleSQLBuilderImpl::compareFetchedValue(...) method, which can be done by customizing the default SQL builder class . The following blog may help you to understand how to add your custom SQL builder to an application module: http://www.jobinesh.com/2013/02/customizing-sql-builder-class.html
You can download the sample workspace from here. Take a look at the model.ContextAwareOracleSQLBuilderImpl class in the Model project to get a feel of the custom SQL builder class that we discussed a while back. Also see the bc4j.xcfg file in the model project where the custom sql builder is configured by specifying appropriate values for jbo.SQLBuilderClass and jbo.SQLBuilderClass properties.
[Runs with Oracle JDeveloper 184.108.40.206.0 or higher + HR Schema]