My Oracle Support Banner

Unexpected Tax Entries In General Ledger Reporting (Doc ID 1069712.1)

Last updated on FEBRUARY 13, 2019

Applies to:

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


The understanding from the documentation is that the taxcode (a single one: CST) has to be provided in the GLID definition.

The expectation is that for each event, such as purchase fee, for which the charges are applied, the corresponding tax should also be displayed in the same GLID.

For example, for mobile sales with GLID = 102145, the expectation is that the tax corresponding with this event should be reported in the tax entry for GLID 102145.

However, this is not happening. As all the products have the same taxcode CST configured, BRM is putting the tax in GLID 100100, that is the GLID where the tax CST occurs for the first time in pin_glid.

Reproduction steps

1) the taxcode is defined for 13% tax (taxcode_map file):

As seen, the tax amount is appearing on GLID 100100, in place of the expected 102145.




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

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