Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.1 to 220.127.116.11.1 [Release 7.0.0]
Information in this document applies to any platform.
***Checked for relevance on 01-May-2010***
Some accounts with outstanding payments are not being picked up by collections after the initial run.
Once pin_collect runs on these accounts with credit card as payment type and is unsuccessful in collecting, it does not run again. It does not attempt further collections because the initial event was not created in BRM and thus the program has nothing to reference to (event history) on the second try. These accounts have outstanding payment, but pin_collect only attempts once and does not attempt payment collection again.
Query used for searching failed accounts :
LAST_BILL_DATE, COLLECTION_STATE, INFRANET_TO_DATE(P.MOD_T) CREATION,
A.STATUS, INFRANET_TO_DATE(LAST_STATUS_T) AS STATUS_DATE
From ACCOUNT_T A, billinfo_t b,MY_DELINQUENCY_T d, PAYINFO_T P
A.POID_iD0 = B.ACCOUNT_OBJ_ID0 AND
A.POID_iD0 = D.ACCOUNT_OBJ_iD0 (+) AND
B.PAYINFO_OBJ_ID0 = P.POID_iD0 AND
B.pay_type = 10003 and
pending_recv > 1.99 AND
(COLLECTION_STATE NOT IN (1,2,4,5) OR COLLECTION_STATE IS NULL) AND
P.MOD_T < ACTG_LAST_T AND
(SELECT * FROM EVENT_T E WHERE
E.ACCOUNT_OBJ_ID0 = A.POID_iD0 AND
E.END_T > ACTG_LAST_T AND
POID_TYPE = '/event/billing/payment/cc') AND
(SELECT * FROM ITEM_T I WHERE
I.AR_BILLINFO_OBJ_ID0 = B.POID_iD0 AND
DUE > 0 AND infranet_to_date(EFFECTIVE_T) <= sysdate - 4)
-- Business Impact:
Accounts are being thrown into collections due to overdue accounts.
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