/item/sponsor Object is Incorrectly Created when Calling the PCM_OP_CUST_UPDATE_SERVICES Opcode
(Doc ID 2399483.1)
Last updated on MARCH 18, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management version 7.5.0 patchset 18, when calling the PCM_OP_CUST_UPDATE_SERVICES opcode, a /item/sponsor object is being created. It is expected that this object should not be created when this opcode is being executed.
Create a customer and add service using custom opcodes and using (pvt) move 10 days forward. Disconnect the same service by calling the standard opcode PCM_OP_CUST_UPDATE_SERVICES. Getting success response but it's creating /item/sponsor object wrongly.
The issue can be reproduced at will with the following steps:
- Create an account and add service (it has negative cycle forward product) using a custom opcode
- Shift pin_virtual_time (pvt) forward 10 days
- Disconnect the service by calling the standard PCM_OP_CUST_UPDATE_SERVICES opcode
Despite the success response, a /item/sponsor item is being created when it should not be.
Due to this issue, users cannot generate invoice reports because of /item/sponsor.
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