PCM_OP_CUST_DELETE_PAYINFO Requires PAYINFO_OBJ Index On BILLINFO_T
(Doc ID 2134513.1)
Last updated on MARCH 28, 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.
Issue clarified that:
The only input for PCM_OP_CUST_DELETE_PAYINFO is the /payinfo POID.
A policy op-code (PCM_OP_CUST_POL_PRE_DELETE_PAYINFO) is called first to allow additional validation before deleting the /payinfo, but then a search is executed for all /billinfo objects containing the currently /payinfo POID.
However, there does not appear to be any OOB index to support this (i.e. on BILLINFO_T.PAYINFO_OBJ_ID0). Why not? Nothing in the op-code docs warns about this.
Wouldn't it be better to require an /account POID in addition to the /payinfo POID so the /billinfo can be retrieved by the /account POID, or perhaps better to do PCM_OP_READ_FLDS to get the /account POID from the /payinfo object? (I assume a /payinfo object cannot be shared across multiple /billinfo objects on different accounts. ).
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