Tax Stored Procedure And Skipped Billing Accounts
Last updated on APRIL 27, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
While comparing billing results between BRM 7.0 and BRM 7.4 systems and have detected a tax difference being caused by the following scenario:
1. If there is a bill that is supposed to be billed on 15/10, but it didn't get closed for some reasons.
2. So the bill for 15/9 to 15/10 is still not closed
3. The bill for 15/10 to 15/11 is also not closed
4. On 15/12, close the bill for 15/9 to 15/10 and 15/10 to 15/11. Because of this, looks like the tax is not computed properly as the BRM 7.4 taxation store procedure is doing partition pruning based on the start_t and end_t of the bill. It should also consider the day when the bill was actually run.
These accounts are being skipped via an operational process of updating the billing segment. This is a normal business process to deal with accounts that have billing issues. This works fine in BRM 7.0 as Taxation stored proc does not do Partition pruning
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