Charge for Backdated Reactivation Is Being Billed Only After The Second Billing Cycle (Doc ID 2961166.1)

Last updated on JULY 13, 2023

Applies to:

Goal

Test case:

Step-1:
Jul 1: Account created (DOM=1);
Step-2:
Jul 10: Product suspended with backdated to Jul 1;
Step-3:
Aug 6: Execute pin_bill_accts utility
Step-4:
Aug 8: Reactivate the product with backdate (Jul 1);
Step-5:
Sep 6: Execute pin_bill_accts utility
Step-6:
Oct 6: Execute pin_bill_accts utility again.

Actual Result: charges corresponding to the suspended period (Jul)   are not getting included in the Sept bill after step-5, instead those Jul cycle charges are getting included in the Oct bill after step-6.

Expected Result:  After Step-5, the bill generated on Sep 6th should include charges for the Jul cycle and Aug cycle.
What is the reason for these backdated reactivation charges getting reflected in the next bill which is October, how to make it get reflected in the bill generated in Sep instead?

Solution

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