Last updated on SEPTEMBER 19, 2016
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.1 [Release 7.3.1]Information in this document applies to any platform.
Goal
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.
Questions:
- How could those inactivations have happened?
- Does pin_collection_process use some other rules to perform actions, apart from the configured templates?
Solution
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