Backdating Is Not Allowed Before Offering Effective Date
(Doc ID 1512213.1)
Last updated on NOVEMBER 17, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
Migration happened from BRM 7.2 to 7.5, Afer migration facing issue while purchasing a deal
What is happening :
When a new deal is purchased, existing purchased product purchase_start_t is being verified with the min(effective_t) in au_purchased_product_t table for expired product. If purchase_start_t < min(effective_t) then it return error that “Backdating is not allowed before service effective date”.
when there is a account which has a active product and get deactivated after 2nd Dec(go live date) then entry is created in au_purchased_product_t with effective_t as current date.
This is first entry created in the table au_purchased_product_t .But the purchased product is having the purchased_start_t when it was purchased that is always less then the current date which is set to effective date .
Example: customer has active product from 5 Dec 2011 to 4 Dec 2012 so if customer does not have balance it get deactivated on 4th Dec 2012 while billing and entry is created in au_purchased_product_t with effective_t as current date as 4th Dec 2012 while purchased start_t is 5th Dec2011. This is first entry created in the table au_purchased_product_t .
In this case purchase_start_t(5 Dec,2011) < effective_t(4 Dec 2012 ) so error returned as not allowed before service effective date"
How can this validation be avoided for existing functionality work properly?
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