Schedule Object Updated Wrongly After Cancellation Of Future Dated Product
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.1 [Release 7.2.1]
Information in this document applies to any platform.
***Checked for relevance on 17-Sep-2013***
-- Problem Statement:
With the use of Telco Framwork, schedule object gets updated wrongly after cancellation of future
dated product. This results in features getting un-provisioned.
-- Steps To Reproduce:
1. In Customer Center with Telco Framwork, issue a future dated purchase of the same deal twice The deal should include 8 products. After the first deal is purchased, it creates a /schedule obj with 8 product
poids as the input flist to the deal purchase opcode. After the second deal is purchased, the /schedule obj will have 16 product poids as the input flist to the deal purchase opcode.
2. In Customer Center, cancel one product out of the 8 products from the first deal. Check on the /schedule obj and verify that two product poids are deleted from the input flist. The two products have the same poid but different NODE_LOCATION. When all 8 products are canceled from the first deal, the /schedule obj is also deleted even though there should have been 8 products left under the 2nd deal purchase.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms