Appendix : Handling Metro II Special Comment Codes

D Appendix : Handling Metro II Special Comment Codes

Following are the steps involved in recording special comment codes on an account and reporting the same in Metro II reporting file.

Step-1: Create the Metro II specific special comment codes mentioned in the CDIA documentation using Lookup Type ‘CAC_REASON_CD’ and Lookup Sub code ‘SPCC’. Lookup code has to be created as SPCC_<code mentioned in the CDIA resource guide>.E.g. To create the reason ‘ Affected by Natural or Declared Disaster ‘ which is having the code ‘AW’ for installment loans, we need to create the Lookup Code as ‘SPCC_AW’.

To deport ‘DE’ special comment code, user can post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event ‘Debt Extinguished’, then system will automatically post the following call activities.

Action	QR QUEUE/CONDITION REQUEST	QR QUEUE/CONDITION REQUEST
Result	OSPCC	Open Debt Extinguished
Reason	DE [Debt Extinguished]	-
Condition	None – if no Active SPCC Condition on account SPCC – if active SPECIAL COMMENT CODE (METRO 2) condition exist on the account	SPECIAL COMMENT CODE (METRO 2)

System will allow to post if the Account status is ‘Active’ else, shows an error message → “Debt Extinguished is allowed to post only on Active Account”.
After reporting Special Comment Code DE, system will discontinue reporting the account in the next metro ii run cycle.
If user closes / updates the SPCC Reason Code ‘DE’, then system will continue report as existing based on the current status of the account and reporting will affect from next reporting cycle.
System reports the following key fields as follows
- Scheduled monthly payment amount = 0
- Current Balance = 0
- Amount Past Due = 0
- SPCC Code = DE
To report ‘BA’ special comment code, user can also post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as ‘VEHICLE SOLD’, then system will automatically post the call activity with reason code as ‘BA’.
To report ‘AX’ special comment code, system will verify the account if the account is paid off during the reporting period for FULL BALANCE and if VRP or IVR repossession exists for an account then system will post the bellow call activity with ‘AX’ reason code while running the termination process batch job - TXNTIP_BJ_100_01 (SET-TPE) to change the account status to 'PAID OFF' or while posting ‘Paid Off’ monetary transaction.
To report ‘AZ’ special comment code, user can post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as
- ‘RE-INSTATION’ - then system will verify the account that If there is no PAST DUE amount on the account and If the REPO marked on the account is ‘IVR’ then system will automatically post the below call activity with reason code as ‘AZ’. If there is PAST DUE, then reason code should be null
- ‘REDEMPTION’ – then if account status is ‘Paid Off’ (manual or through batch job TXNTIP_BJ_100_01 (SET-TPE)) and If the REPO marked on the account is ‘IVR’ then system will automatically post the below call activity with reason code as ‘AZ’
To report ‘AV’ special comment code, user can post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as ‘FIRST PAYMENT NEVER RECEIVED’, then system will automatically post the following call activity with ‘AV’ reason code.
To report ‘AW’ special comment code, user can post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as ‘NATURAL DISASTER’, then system will automatically post the following call activity with ‘AW’ reason code.
To repot ‘AU’ special comment code, when user posts “Account Settlement’ monetary transaction on Loan account then, when the batch job under SET-TPE ‘Account Settlement Processing ‘executes, it will check whether the agreed settlement amount is fully paid. If it is paid, system will internally post the ‘Condition Request’ call activity for OSPCC posting with special comment code ‘AU’.
If user post the above transaction then user need not to post this call activity again for above special comment codes.

To report following Special Comments for the account type 3A (Auto Lease) or 13 (Lease Non-Auto), instead of posting the call activity manually, provided a new ‘Event Type’ LOV parameter to ‘Termination’ transaction based on the selection following call activity will be posted on to the account with validations:

Table D-1 Termination Call Activity

Dt / Follow up Date	Termination Txn Date
Action:	QR
Result:	OSPCC
Contact:	Null
Reason:	As per the Event Type
Condition:	None / OSPCC

Table D-2 Lease Event type V/s Reason Code

S.No	If Event Type	Reason Code
1	Prepaid Lease	SPPC_BS Validation: Transaction date should be less than the maturity date (either buyout indicator Y/N) and No payments are due.
2	Full Termination/Balance Owing	SPPC_BD Validation: Transaction on or after the maturity date (either buyout indicator Y/N) and if the current balance is greater than zero
3	Full Termination/Status Pending	SPPC_BB No Validation
4	Full Termination/Obligation Satisfied	SPPC_BC Validation: if Current Balance = 0 (user expected to post Paid off after this)
5	Early Termination / Status Pending	SPPC_BE No Validation
6	Early Termination / Obligation Satisfied	SPPC_BF Validation: if Current Balance = 0 (user expected to post Paid off after this)
7	Early Termination / Balance Owing	SPPC_BG No Validation
8	Early Termination/Insurance Loss	SPPC_BH No Validation
9	Involuntary Repossession	SPPC_BI Validation: If the collateral repo type (ASE_REPO_FORC_TYPE_CD) other than VOL and active REPO condition exist.
10	Involuntary Repossession / Obligation Satisfied	SPPC_BJ Validation: If the collateral repo type (ASE_REPO_FORC_TYPE_CD) other than VOL and active REPO condition exist.
11	Involuntary Repossession / Balance Owing	SPPC_BK Validation: If the collateral repo type (ASE_REPO_FORC_TYPE_CD) other than VOL and active REPO condition exist.

Step-2: Post special comment ACCOUNT CONDITION through the following CALL ACTIVITY:

Action: QR QUEUE/CONDITION REQUEST

Result: OSPCC OPEN OSPCC

Reason: Any of the reason codes provided by CDIA

Condition: SPECIAL COMMENT CODE (METRO 2)

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_SPECIAL_COMMENT will be updated with the latest special comment code posted. This will be taken from ACCOUNT_CONDITION.ACO_ACC_CONDITION_REASON_CD.

Step-4: Once Metro II reporting file generation batch CBUUTL_BJ_100_03 (SET-ODD2), system creates the reporting file and CIIC code is populated on the base segment field ‘19 – Special Comment’.

Please refer the below screen shot of posting a special comment code specific call activity on an account. In the ‘Reason’ drop down, we can see that all the Consumer Information Indicator Codes (SPCC) created using the above mentioned Lookup code Type ‘CAC_REASON_CD’ and Lookup Sub Code ‘OSPCC’ are available for user selection.

If there is no new OSPCC code selected for an account during the current reporting period, system posts a blank fill which indicates removing any previously reported Special Comment Code, or no Special Comment applies for this activity period.

Please note that system will not do any internal processing based on the special comment code posted on the account and it is only for the Metro II reporting purpose.

Screen: Customer Service → Call Activities (Special Comment Code Posting)

Figure D-1 Special Comment Code Posting

Description of "Figure D-1 Special Comment Code Posting"