Setup Configurations

3 Setup Configurations

Following is the table showing Parameter Name, Description and purpose for setting up the configurations involved in generating the Metro II reporting file.

Table 3-1 Setup Configurations

S.No	Parameter Name & Description	Parameter Purpose
Company parameters
1	CBU_DATA_SET_SIZE Lookup code: CBU_DATA_SET_SIZE_CD	This parameter set the frequency of Metro II reporting file generation – MONTHLY DAILY WEEKLY SEMIMONTHLY Note: For the weekly file generation frequency, system will generate two separate files when whole week spread across the two months. I.e., 1st file will have the account till month-end date, & 2nd file will have 1st to remaining days.
2	CBU_FILE_FORMAT This parameter set the format of the Metro II reporting file required Lookup code: CBU_FILE_FORMAT_CD Values: 426 626 826 1026 1226 480 680 880 1080 1280 710 910 1110 1310 810 1010 1410 1710 844 1144 1444 1744	System will report with combination of “Base 426 segment, multiple J2 and L1 sub-segments” if - 426 – system will report only the Base segment 626 - one BASE segment + one J2 sub-segment 826 - one BASE + two J2 sub-segments 1026 – one BASE + three J2 sub-segments 1226 – one BASE + four J2 sub-segments 480 – one BASE + one L1 sub-segment 680 – one BASE + one J2 + one L1 sub-segments 880 – one BASE + two J2 + one L1 sub-segments 1080 - one BASE + three J2 + one L1 sub-segments1280 – one BASE + four J2 + one L1 sub-segments 710 – one BASE + one J2 + one K4 + one L1 sub-segments 910 – one BASE + two J2 + one K4 + one L1 sub-segments 1110 - one BASE + three J2 + one K4 + one L1 sub-segments 1310 – one BASE + four J2 + one K4 + one L1 sub-segments 810 – one BASE + one J1+ one J2 + one K4 + one L1 sub-segments 1010– one BASE + one J1 + two J2 + one K4 + one L1 sub-segments [Note: two J1 are not supported] 1410- one BASE + three J1+ three J2 + one K4 + one L1 sub-segments 1710 – one BASE + four J1 + four J2 + one K4 + one L1 sub-segments 844 - one BASE + one J1+ one J2 + one K2 + one K4 + one L1 sub-segments 1144 - one BASE + two J1+ two J2 + one K2 + one K4 + one L1 sub-segments 1444 - one BASE + three J1+ three J2 + one K2 + one K4 + one L1 sub-segments 1744 - one BASE + four J1+ four J2 + one K2 + one K4 + one L1 sub-segments
3	CBU_MONTHS_CLOSED_LIMIT	This parameter dictates the system that, how many times, that the system should report if the account is paid off / closed.
4	CBU_FILE_FREQUENCY	This parameter is used to set the Metro II File Frequency and determine whether output file is to be generated daily or monthly. If this is monthly, then output file is written with daily data but generated monthly.
System Parameters
5	METROII_RETRY_SKIP_ACC_IND	If an account is skipped on the day of Bill Generation or on the Due Day (during the month), and if this parameter is set it as ‘Y’, then system will try again on the month end. In general, while processing the account, if it has STOPCB condition, system skip the account.
6	METROII_BASE_DT_CLOSE_IND	This parameter controls the behavior of reporting ‘Close Date’ If the account status is reported as 13 / 61 / 62 / 63 / 64 / 65 then how system should report the Closed Date If Y and Enabled, Paid Off Date; If N or Disabled, Last Payment Date which is last payment made on the account
7	METROII_FIRST_DELQ_DT_ADD_DAYS	When system reports ‘FCRA Compliance/ Date of First Delinquency’, it considers the value in this delesystem parameter and added to the oldest due date on the account and report it.
8	MET_SCH_PMT_METHOD	System reports ‘Scheduled Monthly Payment Amount’ based on this parameter value If CURRENT_DUE_AMT = amount equal to the actual bill generated If STANDARD_PAYMENT_AMT = amount equal to the contract payment amount
9	CBU_APND_COMPANY_TO _FILENAME	To control the display of PTC Companies in the file name. If parameter is set to Y, then PTC company names are appended to the file name. If parameter is set to N, then PTC company names are not appended to the file name.