My Oracle Support Banner

Dm_vertex Is Rounding Tax Rate To 5 Decimal Places But Comtax Ctq Series 6 Supports More Decimals (Doc ID 2218475.1)

Last updated on MARCH 24, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.15.0 and later
Information in this document applies to any platform.

Symptoms

dm_vertex is rounding tax rate to 5 decimal places but Comtax ctq series 6 supports more decimals.

ACTUAL BEHAVIOR
---------------
ctq currently stores tax rates with a precision up to 8 decimal places.
The rate is rounded in the dm_vertex to 5 decimal places and ultimately stored with this precision in the event_tax_jurisdiction_t table.

As a result the tax amount as calculated by vertex and stored in tax_jurisdiction_t, can no longer be reconciled with using the tax rate in the same table.

EXPECTED BEHAVIOR
-----------------------
The dm_vertex code should not round Tax rate 5 Decimal Places, this should be configurable in either the pin.conf or a business parameter to allow tax rate with more precision.

STEPS
-----------------------
Example:
The city tax for geocode 320010020 is defined in ctq table RTERDD as 0.011875, but is returned as 0.01188 from dm_vertex

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.