My Oracle Support Banner

How To Generate Invoice Correctly Without Garbled Characters From A Custom Policy? (Doc ID 782126.1)

Last updated on FEBRUARY 03, 2022

Applies to:

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


During Invoice generation to build the flist for invoicing, in fm_inv_pol_prep_invoice() code a user has customized the code to add the SERVICES array with the element ID as the poid_id0 of the service, using the OOB function PIN_FLIST_ELEM_ADD().

1 PIN_FLD_SERVICES ARRAY [2637995461] allocated 20, used 8

pin_flist_elem_add (pin_flist_t *flistp,
                         pin_fld_num_t fld,
                         int32 elem_id,
                         pin_errbuf_t *ebufp);

In OOB elem_id is defined as int32, where as the poid is int64. So once the value of poid_id0 exceeds int32, junk characters is stored in the array element. The invoices generated are garbled and cannot be viewed, exported and send to customers.

Can the user change the defination of pin_flist_elem_add in pcm.h from:
EXTERN pin_flist_t *pin_flist_elem_add( pin_flist_t *flistp, pin_fld_num_t fld, int32 elem_id, pin_errbuf_t *ebufp );
EXTERN pin_flist_t *pin_flist_elem_add( pin_flist_t *flistp, pin_fld_num_t fld, int64 elem_id, pin_errbuf_t *ebufp );

If not, how to resolve this problem?


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.