Wrong Validity End For Events Created During Delayed Period

(Doc ID 978402.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.1 to 7.3.0.0.1 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.
***Checked for relevance on 29-Mar-2012***

Symptoms

Purchasing a product within the delayed period, with a Cycle Forward Monthly with a resource balance impact configured for a grant End Date as "relative: 1 Accounting Cycle", the corresponding balance group is created with a VALID_TO set to next month, not to next accounting cycle, as expected.

If the same purchase happens past the delayed billing period, the result is as expected.

E.g.

Accounting DOM = 1
delayed period = 15
ACTG_NEXT_T = 1-Dec-09

Purchase of Cycle Forward Montly product made on 13-Nov-09 creates the following balance group details:

BAL_GRP_SUB_BALS_T.VALID_FROM = 13-Nov-09
BAL_GRP_SUB_BALS_T.VALID_TO = 13-Dec-09

A similar purchase, but made AFTER delayed billing period has passed (i.e. on 17-Nov), produced the following validity range (as expected):

BAL_GRP_SUB_BALS_T.VALID_FROM = 17-Nov-09
BAL_GRP_SUB_BALS_T.VALID_TO = 01-Dec-09

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms