Taxes Jurisdiction Is Not Correctly Calculated For Delayed Events On Rerating (Doc ID 1175243.1)

Last updated on APRIL 13, 2012

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 to 7.4.0.0.0 - Release: 7.4.0 to 7.4.0
Information in this document applies to any platform.

Symptoms

When running rerating, the adjustment event created by the rerating process does not correctly set the tax_jurisdiction sign for the impact to do the backout:
e.g.

0 PIN_FLD_POID POID [0] 0.0.0.1 /event/billing/adjustment/event 260997672155587324 0
...
0 PIN_FLD_BAL_IMPACTS ARRAY [2] allocated 22, used 22
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 581782 0
1 PIN_FLD_AMOUNT DECIMAL [0] -180
...
0 PIN_FLD_TAX_JURISDICTIONS ARRAY [2] allocated 20, used 8
1 PIN_FLD_AMOUNT DECIMAL [0] 0.29
1 PIN_FLD_AMOUNT_EXEMPT DECIMAL [0] 0
1 PIN_FLD_AMOUNT_GROSS DECIMAL [0] 180
1 PIN_FLD_AMOUNT_TAXED DECIMAL [0] 180
1 PIN_FLD_ELEMENT_ID INT [0] 1
1 PIN_FLD_NAME STR [0] " "
1 PIN_FLD_PERCENT DECIMAL [0] 0.16
1 PIN_FLD_TYPE ENUM [0] 0

The above highlighted field should have negative sign for the numbers, as different as it behaves when an specific adjustment event is created manually (Customer Center).
e.g.

0 PIN_FLD_POID POID [0] 0.0.0.1 /event/billing/adjustment/event 260997672155553720 0
....
0 PIN_FLD_BAL_IMPACTS ARRAY [0] allocated 22, used 22
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 581782 0
1 PIN_FLD_AMOUNT DECIMAL [0] -18
....
0 PIN_FLD_TAX_JURISDICTIONS ARRAY [2] allocated 20, used 8
1 PIN_FLD_AMOUNT DECIMAL [0] -2.88
1 PIN_FLD_AMOUNT_EXEMPT DECIMAL [0] 0
1 PIN_FLD_AMOUNT_GROSS DECIMAL [0] -18
1 PIN_FLD_AMOUNT_TAXED DECIMAL [0] -18
1 PIN_FLD_ELEMENT_ID INT [0] 1
1 PIN_FLD_NAME STR [0] " "
1 PIN_FLD_PERCENT DECIMAL [0] 0.16
1 PIN_FLD_TYPE ENUM [0] 0
...

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