Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.1 to 220.127.116.11.1 [Release 7.3.1]
Information in this document applies to any platform.
When PCM_OP_CUST_SET_STATUS is called for parent account of hierarchy, standard opcode internally calls this opcode twice.
1> Create a parent account.
2> Create a non-paying child account under parent account.
3> Change status of parent account to inactive.
1> Internally set status is called twice for the same account. .
2> By looking at the logs, you can see there is a search which returns parent account along with child account which has probably triggered this operation twice.
3> It is also observed that if status of account is already inactive with status flag 4 and again status is changed to inactive with same status flag 4 then OBRM is generating a service order which may not be correct.
1> Cust set status should not be called twice internally.
2> Changing inactive account to inactive with same flag should not have generated the service order.
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