No Separate G/L ID For Tax Record Within Pipeline Rating
(Doc ID 1362631.1)
Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Checked for relevance on 22-Nov-2013.
In the BRM 7.4 documentation, it is mentioned several times that tax amounts/records can have separate G/L-IDs. Unfortunately. this does not seem to be the case for Pipeline rating.
In Pipeline rating, G/L-IDs can be defined on a pricemodel-step level. It is also possible to check the "tax treatment" box for a certain product, but it's not possible to assign separate G/L codes for the tax (record).
So the documentation seems to be wrong here. Is this a bug, or is there any non documented workaround available?
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