My Oracle Support Banner

Short Billing Cycle Incorrect For Account Created On Any Months 27,28 Date With DOM As 29 (Doc ID 1665168.1)

Last updated on JULY 19, 2020

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

Billing Cycle is incorrect for account created on January 27 with Billing Day of Month (BDOM) as 29. Current billing cycle is Jan 27 - Feb 28; here it has become a long cycle.

If it is short Cycle current billing cycle should be Jan 27 - Jan 29. This scenario happens for the month 27th onwards: instead of a short cycle, a long cycle is generated.

PCM_OP_CUST_POL_PREP_BILLINFO opcode is calling PCM_OP_BILL_POL_SPEC_FUTURE_CYCLE to prepare billing cycle next_t and future_t. This opcode PCM_OP_BILL_POL_SPEC_FUTURE_CYCLE is returning wrong next_t and future_t (SHORT_CYCLE) because of function "future_t = fm_utils_cycle_actgnextt(next_t, dom, ebufp);".

Below is the SHORT_CYCLE scenario input and output flist for PCM_OP_BILL_POL_SPEC_FUTURE_CYCLE:

Reproduction Steps:

Case 1) Account created on 27th Jan

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.