GST - After RUP9, System Is Truncating 'Tax Conversion Rate' To 2 Places After Decimal

(Doc ID 2324685.1)

Last updated on NOVEMBER 03, 2017

Applies to:

Oracle Financials for India - Version 12.1.3 and later
Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On R12: GST Order Management

ACTUAL BEHAVIOR

After applying RUP9, the system is truncating the "Tax Conversion Rate" to 2 places after the decimal.

Example

Created an export sales order with User defined "Tax Conversion Rate" = 0.571.
But in India Tax Details, system is using Tax Conversion Rate = 0.57.
Due to this issue, there is 165 Rupee gap (less) in the Tax amount. This equates to $2.57 US dollars.
This difference is on just 1 line of 1 order. Adding all lines from all orders will make the difference in the Tax huge.

The calculations of the tax can be found in the LOCOMLIST output in tables JAI_TAX_LINES, JAI_TAX_JOURNAL_ENTRIES and GL_INTERFACE.


EXPECTED BEHAVIOR

System should use all 3 digitis to the right of decimal of the "Tax Conversion Rate"

For example, system should use Tax Conversion Rate of 0.571, not just 0.57.

This worked as expected before RUP9 was applied

STEPS

1. Create sales order
2. Check the India Tax Details
3. See the tax Conversion Rate shows as .57 (instead of .571.



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