PIN_COLLECTIONS_PROCESS Setting Action Status To Err Without Any Err In Pinlog
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Checked for relevance on 10-Jun-2014
-- Problem Statement:
Had recently upgraded BRM system from 6.5 --> 7.3. While executing pin_collections_process, some of the jobs frequently error out(but this is not happening for all the accounts). While analyzing those, have found that after deleting the /schedule object pertaining to that /collection_actions, the action is executed successfully.
By following the track of the passed account, after the /schedule object has been deleted for the failed account and the pin_collection_process is run again, the action is executed successfully.
-- Steps To Reproduce:
1. execute pin_collection_process.
2. check the execution flow of /collections_action/policy_action and /collections_action/dunning_letter.
3. For /collections_action/policy_action - PCM_OP_COLLECTIONS_POL_EXEC_POLICY_ACTION should be called.
4. For /collections_action/dunning_letter - SET_DUNNING should be called.
-- Business Impact:
Not able to execute collection scenarios on our customers who are not paying their bills.
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