Inconsistent CYCLE_FEE_END_T Upon Customizing PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL (Doc ID 2288116.1)

Last updated on JULY 27, 2017

Applies to:

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

Symptoms

On Oracle Communications Billing and Revenue Management (BRM) version 7.5.0 patchset 12 when customizing the PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL opcode in Subscription Management, the CYCLE_FEE_END_T is inconsistent.

Details:

0 PIN_FLD_CYCLE_FEES ARRAY [1] allocated 20, used 6
1    PIN_FLD_CHARGED_FROM_T TSTAMP [0] (1493967600) Fri May 5 00:00:00 2017
1    PIN_FLD_CHARGED_TO_T TSTAMP [0] (1496646000) Mon Jun 5 00:00:00 2017
1    PIN_FLD_COUNT INT [0] 1
1    PIN_FLD_CYCLE_FEE_END_T TSTAMP [0] (1494486000) Thu May 11 00:00:00 2017
1    PIN_FLD_CYCLE_FEE_START_T TSTAMP [0] (1493967600) Fri May 5 00:00:00 2017
1    PIN_FLD_UNIT ENUM [0] 0

Looking at the PIN_FLD_CYCLE_FEES array in above snippet, actual cycle fee charged is from the 5th of May to the 5th of June, but CYCLE_FEE_END_T is being set to the 11th of May.  This causes problems when billing is run on the 11th of June as it charges from the 11th of June which causes all charges between the 5th of June and the 11th of June to be missing.

It is expected that the CYCLE_FEE_END_T be set as the 5th of June instead of the 11th of May.

In order to reproduce this problem:

1. Create an account on 5 May 2017 with DOM as 11
2. Customize OP_SUBSCRIPTION_POL_CYCLE_FEE_INTERVAL opcode to apply cycle fee from 5 May to 5 June 2017
3. After purchase  of a product, see below values in purchased_product object :

0 PIN_FLD_CYCLE_FEES    ARRAY [1] allocated 20, used 6
1     PIN_FLD_CHARGED_FROM_T TSTAMP [0] (1493967600) Fri May  5 00:00:00 2017
1     PIN_FLD_CHARGED_TO_T TSTAMP [0] (1496646000) Mon Jun  5 00:00:00 2017
1     PIN_FLD_COUNT           INT [0] 1
1     PIN_FLD_CYCLE_FEE_END_T TSTAMP [0] (1494486000) Thu May 11 00:00:00 2017
1     PIN_FLD_CYCLE_FEE_START_T TSTAMP [0] (1493967600) Fri May  5 00:00:00 2017
1     PIN_FLD_UNIT           ENUM [0] 0

 4. Note that PIN_FLD_CYCLE_FEE_START_T is OK and PIN_FLD_CYCLE_FEE_END_T is not OK.

Changes

 

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