Appendix : Payment Rating Code Derivation

F Appendix : Payment Rating Code Derivation

Following are the steps involved in deriving the payment rating code for an account and reporting the same in Metro II reporting file.

Step-1: Create the Metro II specific ‘Payment Rating Codes’ mentioned in the CDIA documentation using Lookup Type ‘CRB_PMT_RATING_CD’.

Step-2: During the billing batch job (TXNDDT_BJ_100_01-SET-TPE) run system checks whether the Metro II account status of the account falls into 05, 13, 65, 88, 89, 94 or 95. Then system calculates the days past due for the account by calculating the difference between current GL post date and effective date of last billing date and derives the payment rating code from the above mentioned lookup as per the below mentioned rules -

0 = Current account (0–29 days past the due date)
1 = 30-59 days past the due date
2 = 60-89 days past the due date
3 = 90-119 days past the due date
4 = 120-149 days past the due date
5 = 150-179 days past the due date
6 = 180 or more days past the due date
G = Collection [account should have Collections condition]
L = Charge-off [account status – Charged Off and having deficiency balance greater than zero]

Above mentioned derived payment rating code is stored in ACCOUNTS. ACC_CRB_PMT_RATING_CD

Step-3: When system executes the batch job CBUUTL_BJ_100_02 (SET-ODD2) to populate the METRO_II_DATA table for an account, column MET_BASE_PMT_RATING will be updated with the payment rating code derived.

Step-4: Once Metro II reporting file generation batch CBUUTL_BJ_100_03 (SET-ODD2), system creates the reporting file and payment rating code is populated on the base segment field ‘17B – Payment Rating’.