Accounts Unexpectedly Becoming Inactive

(Doc ID 1603335.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.1]
Information in this document applies to any platform.


Understand and solve the issue of having unexpected account de-activations, on execution of pin_collection_process.

The steps followed to reproduce the problem are:

- created a future date scheduled action, (e.g. 'Inactivate Services of Billinfo') using the pin_collections_process.
- deleted the action using 'PCM_OP_ACT_SCHEDULE_DELETE' (e.g. from Customer Center, or testnap) opcode successfully.
- executed pin_collections process on the scheduled date.

Expected result:

Account should not become inactive, as scheduled action was deleted.

Actual result:

Account still gets inactivated.


- How could those inactivations have happened?
- Does pin_collection_process use some other rules to perform actions, apart from the configured templates?


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