My Oracle Support Banner

Bill Cycle Is Getting Saved Even Though Overlapping Window Period Exists (Doc ID 2800180.1)

Last updated on AUGUST 24, 2021

Applies to:

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


On RMB v2., Bill cycle is getting saved even though overlapping window period exists.

Bill cycle is getting saved even when overlapping period is set.
System throws validation error when window period end is later than next period start date which is expected and working fine.
The issue occurs only when Bill cycle window period end date is equal to next period start date. Ideally system should throw the same validation error but currently system is allowing to save.
Due to this, BILLOPEN batch errors out the records for the bill cycle for which window periods overlaps.

It should alert users with same validation message when End date is greater than next Start date.

The issue can be reproduced at will with the following steps:
1. For a bill cycle enter 'Window End Date' of current period is equal to 'Window Start Date' of next period.
  System does not throw any alert message like it does when 'End Date' overlaps the 'Start Date' of next period. This should ideally throw the same validation message to alert the user.
2. Run BILLOPEN batch for same 'End Date' (say 30-MAR-21).
  Records are erred out for the overlap periods.
3. After removing the overlapping change, batch run works as expected.


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.