Products Configured With Prorate_last = 701 Gives Non-zero Amount On Cancellation (Doc ID 2594400.1)

Last updated on SEPTEMBER 08, 2023

Applies to:

Symptoms

One has encountered an issue wherein products configured with 1 month bill-in-advance and with prorate_last = "full" (or prorate_last = 701, meaning cancel proration = charge for full cycle) in the rate table, still gives a non-zero amount for cancellation events of the configured products

Expected behavior is that, on cancellation, the cancel events (refund events) should have zero balance impact because proration is set to full (charge for full cycle).

Consider following scenarios:

Scenario 1) Product Cancellation in the middle of billing period.

Steps:

• Account Creation
• Purchase Product (configured with prorate_last = 701) and bill-in-advance = 1 month
• Bill Now
• Move PVT (pin virtual time) to next DOM (accounting day of month) + 17
• Run Billing
• Cancel Product
• Two refund events are produced, one with zero charge, one with non-zero charge. Expected both with zero charge

Scenario 2) Product Cancellation in DOM

Steps:

• Account Creation
• Purchase Product (configured with prorate_last = 701) and bill-in-advance = 1 month
• Bill Now
• Move PVT to next DOM
• Run Billing
• Cancel Product
• Two refund events produced, both with non-zero charge. Expected both with zero charge
  
  
  
  

Cause

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