Custom Invoicing Stop Working After Upgrade From BRM 7.2 To 7.5 (Doc ID 1592236.1)

Last updated on FEBRUARY 18, 2019

Applies to:

Goal

Qn1: On BRM 7.5 PS4, while upgrading from 7.2

In 7.2 invoice_data was limited to 4000 bytes. When an event has more than X Balance Impacts (X was set in pin.conf) taken by PCM_OP_ACT_POL_SPEC_EVENT_CACHE, then in invoice_data field PIN_FLD_STATUS_PROPAGATE is set instead of Balance Impacts. This is for reducing the length of invoice_data to prevent overflow. That field tells the invoicing opcodes to read the bal_impacts themselves, instead of reading them from invoice_data field. However after upgrading to 7.5 when PCM_OP_INV_DECODE_INVOICE_DATA tries to read this field it ends with an error.

Found a temporary solution for testing purposes - after PIN_FLD_STATUS_PROPOGATE, add dummy BAL_IMPACT (with amount 0 and item null pointer) it works fine.
But this solution would not work in the long run, as it would require to data fix a few million events.

After further investigation, found out that in 7.2 there was no such thing as "detailed invoice" or "summary invoice" and according to BRM 7.5 documentation "A detailed invoice lists the bill items for the bill unit and the events that have currency balance impacts greater than zero. The detailed invoice mode is the default."

Tried to check if setting invoicing to "summary invoice" would fix the problem as invoicing is fully customized, but pin_inv_accts ignores '-summary' parameter and calls the application with PIN_FLD_INV_TYPE 0.

Need a way to to run invoicing like it was in 7.2 - without obligatory BAL_IMPACTS array in Invoice_data fields for not null fields.

Is this possible?
 
Qn2: Patch 16708122 is a pre-requisite of another patch. Would like to know what is changed in the patch to decide testing scope.
 

Solution

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