Dropping PIN_FLD_TAXES in fm_bill_utils_tax_apply2_impact (Doc ID 3079112.1)

Last updated on APRIL 03, 2025

Applies to:

Goal

Both the input and output of op_rate_pol_post_tax receive two distinct PIN_FLD_TAXES arrays from dm_vertex.

However, we observe that fm_bill_utils_tax_apply2_impact retains only one PIN_FLD_TAXES array, with the second array missing when invoked.

This behavior is related to BRM taxation when integrating with Vertex O Series using a custom database.

The flist "50616 fm_bill_utils_tax_apply2_impact res_flistp" resembles the output of op_rate_pol_post_tax, as both contain two PIN_FLD_TAXES arrays.

In contrast, the flist "50519 fm_bill_utils_tax_apply2_impact tax_flistp" contains only one PIN_FLD_TAXES array. At line 50616, there were initially two PIN_FLD_TAXES arrays, but the second array (array[1]) was removed afterward.

A specific price plan, such as a 50-50 split, dictates that 50% of the taxes apply to Location A, while the remaining 50% applies to Location Z. To implement this partitioning, fm_rate_pol_pre_tax.c was modified to generate two PIN_FLD_TAXES arrays.

A similar process occurs during billing. Customers may have purchased services such as VOICE, INTERNET, etc., which are taxed during billing. Here, PIN_FLD_TAXES is used to separate tax calculations per service, and further subdivisions may occur within each service.

Solution

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