My Oracle Support Banner

Post Processing Bill Segments Getting Created With Wrong Dates (Doc ID 2206967.1)

Last updated on MARCH 07, 2019

Applies to:

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


On RMB v2. against FW v4.2.0.3, BI - Billing:

Post Processing bill segments getting created with wrong dates.

Currently it is observed in production that if Bill contains bill segments from previous months billable changes, then on same bill post processing bill segments are created with date range earliest date of bill segments and latest date of the bill segment, rather than based on bill cycle.

For example, if bill has following bill segments from regular with following date range :

BSEG 1 1st Sep 2016 30th Sep 2016 (Any Product)
BSEG 2 1st Oct 2016 30th Oct 2016 (Any Product)

Then all post processing bill segments on this bill are created with date range of 1st Sep 2016 to 30th Oct 2016.

It is expected that bill segment to be created with date range of 1st Oct 2016 to 30th Oct 2016.
In above example if there had been a bill segment with date range of 1st Jan to 30th Jan, then Post processing bill segment would have been created with date range of 1st Jan to 30th Oct instead of 1st Oct 2016 to 30th Oct 2016.

The issue has the following business impact:
This is effecting post processing bills which have adhoc regular bsegs.
As an example, for merchant XYX we created an uploaded charge for $X,XXX.XX on 15-AUG-16 using adhoc bill, then post processing BSEG was created with date range 15-AUG-16 to 15-AUG-16 rather than 1st Aug to 30th Aug which was the bill cycle.


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.