Backdate Purchase Results in Two Cycle Events (Doc ID 2141411.1)

Last updated on JUNE 03, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

There are two cycle events generated from backdated purchase, which can be reproduced with the following scenarios:

Scenario #1:
- system is set to 28 day billing, not 31 day billing
- PVT set to April 3 2016
- create account with BDOM of 1st, and in the same transaction, purchase a semi-annual cycle product back-dated to March 30 2016
- in SPEC_CYCLE_FEE_INTERVAL, force the charge into a slight long-cycle from March 30 to Oct 1 2016 (six months + a two day long cycle)
- some Oracle OOB code in the immediate aftermath of SPEC_CYLE_FEE_INTERVAL is then causing two events to be generated, one from March 30 to April 1 (two days) and another from April 1 to Oct 1 (the remaining six months)

Scenario #2:
- system is set to 28 day billing, not 31 day billing
- PVT set to March 1 2016
- create account with no services
- move PVT to April 1 2016 and run billing
- move PVT to April 3 2016
- on the account above, purchase a semi-annual cycle product back-dated to March 30 2016
- in SPEC_CYCLE_FEE_INTERVAL, force the charge into a slight long-cycle from March 30 to Oct 1 2016 (six months + a two day long cycle)
- some Oracle OOB code in the immediate aftermath of SPEC_CYLE_FEE_INTERVAL is then causing two events to be generated, one from March 30 to April 1 (two days) and another from April 1 to Oct 1 (the remaining six months)

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