My Oracle Support Banner

Geocode Not Passed to BRM for Bundled Products (Doc ID 2047192.1)

Last updated on FEBRUARY 19, 2019

Applies to:

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


On : version, Taxation

Geocode not passed to BRM for bundled products

When BRM sends a tax calculation request to Vertex for a bundled product, the vertex output response does not send back geocode in the output flist. A bundled product is a single subscription product created in BRM that splits into 3 components on the Vertex side - Voice, Text, Data. For example, $100 subscription fee has 50% voice, 20% text and 30% data split in terms of MRC (Monthly Recurring Charge).

BRM contains geocode in PIN_FLD_TAXES-> PIN_FLD_SUBTOTAL -> PIN_FLD_NAME field. In case of bundled product, the output returns in the format "; CategoryCode 43-02/10-01; PUC Tax". The geocode is not populated before the first semicolon so expecting geocode in the output flist.

The issue can be reproduced at will with the following steps:
1. Create a bundle in Vertex and publish for use. The bundled product uses following configuration for tax calculation purpose. As an example, an MRC product of $100 consists of 45% on voice and 55% on data.
2. Create a normal subscription/Monthly Recurring Charge( MRC) product in BRM and assign an appropriate tax code which maps to the bundle created in step 1. Set the tax to be calculated at bill time.
3. Purchase the MRC on customer and run billing. During billing, BRM will hit vertex for tax calculation and vertex response does not have geocode.




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.