Issue with Product Transition From Cycle_forward_arrear to Cycle_arrear (Doc ID 2999030.1)

Last updated on JANUARY 23, 2024

Applies to:

Symptoms

During the product transition from cycle_forward_arrear to cycle_arrear the following problem occurs: 

It was observed that pin_cycle_fees is not respecting the end date passed in the input.
The offerings were fetched as per the passed end date but the CF (Cycle Fee) opcode was being called with current PVT(Pin Virtual Time) always.
This caused discrepancies in applying cycle fees.

Scenario:

1. On Nov 6, backdate purchase to Sep 15
This will charge cycle_forward_arrear from Sep 15 to Oct 1

2. Run pin_cycle_fees with end date in previous accounting cycle to set dates correctly
pin_cycle_fees -regular_cycle_fees –end 10/31/23

3. Run pin_cycle_fees as usual
pin_cycle_fees -regular_cycle_fees

This will trigger cycle_arrear event for the below cycle i.e.
cycle_arrear event from => Oct 1st - Nov 1st

Note: Step 2 is the additional step one will have to perform. This will pick the accounts that were purchased in previous accounting cycle and set the dates correctly in them. After that it work normally.

Cause

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