Hi Philippe,
This is how the system works, especially with currency… The standard is described below:
Meaningful Digit
While values cannot be truncated or rounded off during conversion, the result can be rounded off according to the rule defined in this field. The Meaningful digit refers to the last significant or meaningful digit that must be present in the final displayed value. In each of the available selections, the number one (1) indicates the location of the meaningful digit.
Beyond this meaningful digit, the application knows to round off according to the standard rounding rule: if the value of the next digit is 5 or greater, then round off the meaningful digit to one number higher. If the value of the next digit is less than 5, the meaningful digit remains unchanged. The value, after rounding off, is saved in the application database.
When a monetary value is written in U.S. notation, only two decimal places are used. Let’s say that the value received at the end of the currency conversion was 100.006. Because we will use only two decimal places, a meaningful digit of 0.01 is defined in this field.
The application knows that the number “6” should be rounded off according to the standard rounding rule. The value returned by the application is 100.01.
This applies to purchase requisition and would also require code changes to accommodate higher precision which is what you need based on the question. A change like this can be intensive and will not be done to standard so would have to be done as a custom code change with a high level of testing the impact on various modules (mobile also besides the Alliance client).
Sorry, I can’t think of a way to do what you are asking in the current code.
