Control On Deletion Of /Payinfo/Xxx When It Is Associated To Custom Objects
Last updated on APRIL 27, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.1 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 12-Jul-2013***
There is a payinfo object "/payinfo/cc" which is associated to custom object "/aur_topup".
If we delete this "/payinfo/cc" from Customer Center (Manage payment method from payments tab), the deletion of the "/payinfo" object "/payinfo/cc" is successful, as it’s only associated in "/aur_topup" object and NOT "/billinfo" object.
If the same "/payinfo" object "/payinfo/cc" is associated with "/billinfo", the opcode returns an error:
"Payinfo - Billinfo association exists cannot delete" .
Couple of expectations here:
1) There is no hook in Customer Center to call CUSTOM opocde (which checks for objects associated to this payinfo) rather than calling OOB opcode PCM_OP_CUST_DELETE_PAYINFO.
2) There are no policy files provided for opocde PCM_OP_CUST_DELETE_PAYINFO, so we do not have any control to check whether this payinfo is associated to custom objects or not .
3) Opcode PCM_OP_CUST_DELETE_PAYINFO should create an event when ever it deletes /payinfo object. Currently it does not create any event for this activity.
When we delete a payinfo which is associated to custom object, it deletes the payinfo object successfully . Still /payinfo is associated to custom object, where as the actual /payinfo object is missing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms