Appendix A :System Parameters

A.1 Introduction

System defined parameters help in configuring system specific data, User-access, location of system files; reports related URLs and other administration controlled data. These are essential to be configured during installation and some of them by nature of application will have to be reviewed and maintained in a regular and periodic manner.

Following are the types of parameters are used in OFSLL system depending on the areas of the system that these would apply and impact:

● System Parameters

● Organization Parameters

● Company Parameters

● Other Parameters

Note

All the above parameters can be controlled (enabled/disabled) only by System Adminis­trators, and users with Admin/Super User privileges who would be involved in setting-up OFSLL system.

A.2 System Parameters

System parameters apply to the entire system. They relate to the overall processing of the system like application server file locations, data purging configurations and so on. Table below details the list of system parameters with their description and pre-defined values.

Sl.No	Parameter	Description
1	ACA_DLQ_AMT_EX­CLUDED	This parameter is used to exclude delinquency amount for account ACH
2	ACA_PAYMENT_AU­TO_LOAD	This parameter is used to control posting directly from the ACH file that has been created for cus­tomer payments. Input parameter value is Boolean (Yes/No). If the parameter is set to ‘Y’, the system automatically creates payment batches for the payments in the ACH file and posts them on the day of payment.
3	ACA_PRENOTE_DAYS	This parameter is used to define the number of days the prenote should be initiated for customer ACH (Automated Clearing House) accounts. Input parameter value is numeric.
4	ACA_PRE_PROCESS_­DAYS	This parameter is used to specify the number of days before draft day for Account ACH process. Input parameter value is numeric.
5	ACH_PAYEE_PRENOTE_­DAYS	This parameter is used to define the number of days for prenote to occur for Producer or Vendor ACH accounts. Input parameter value is numeric
6	ADMIN_SERVER_URL	This parameter is used to define the admin server URL
7	ADR_DIRECTORY	This parameter is used to define the Oracle Direc­tory Object Name for ADR file location
8	ADR_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle Direc­tory Object Name for ADR file location
9	AGE_APPROVED_CON­DITIONED_DAYS	This parameter is used to specify the number of days by which an application in ‘Approved’ or ‘Conditioned’ status is treated as Aged Applica­tion. Input parameter value is numeric with no upper limit.
10	AGE_CONTRACT_DAYS	This parameter is used to specify the number of days by which a contract is treated as Aged Con­tract. Input parameter value is numeric with no upper limit.
11	ASC_COL_SER_ENA­BLED_IND	This parameter is used as the Collection Servicing Enabled Indicator
12	CAC_DIRECTORY	This parameter is used to define the Oracle Direc­tory Object Name for CAC file location
13	CAC_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle Direc­tory Object Name for CAC file location
14	CHECK_PRINT_PREVIEW	Using this parameter we can allow preview of application in pdf form before printing. Input parameter value is Boolean (Yes/No).
15	CMN_AMOUNT_ROUND_FACTOR	This parameter is used to define the rounding fac­tor for applicable fields (in this case calculated amounts). Input parameter value is ‘ROUND AMOUNT TO 2 DECIMALS’. Currently system supports rounding factor 2 only.
16	CMN_AMOUNT_ROUND_METHOD	This parameter is used to define the amount round method during system set-up and would be appli­cable for all calculated amounts (calculated fees, payment etc.) across the application. Input values are ROUND, RAISE and CUTOFF: ROUND: Rounded to nearest number higher or lower RAISE: Rounded to the nearest higher number CUTOFF: Truncate the digits without rounding or raising
17	CMN_APP_ACC_TI­TLE_FN_LN	This parameter is used to set the Application or Account title in one of the formats – First/Last Name or Last/First Name. Input parameter value is Boolean (Yes/No). If Yes is chosen, title would be in the format – First/Last Name, else the other option.
18	CMN_APP_­SERVER_HOME	This parameter is used to set the Application Server Home Directory. Input parameter value is user defined.
19	CMN_CURRENT_MOD­EL_YEAR	This parameter is used to default the Current Model Year.
20	CMN_DEBUG_LEVEL	This is the Common Debug Level
21	CMN_DEBUG_METHOD	This is the Common Debug Method
22	CMN_­FILE_PROCESS_TO_LOB	This parameter is used to change incoming/outgo­ing file process to CLOB process
23	CMN_GL_POST_DT	This parameter is used to specify the General Ledger Posting date. If scheduler is enabled, it automatically updates this to current system date. Else Admin User would need to set this date man­ually to ensure correct posting dates in GL.
24	CMN_HTTP_PROX­Y_PORT	This parameter is enabled to specify the port to be used for outgoing HTTP connections. Input parameter value is user defined.
25	CMN_HTTP_PROXY_­SERVER	This parameter is enabled to specify the proxy server to be used for outgoing HTTP connections. Input parameter value is user defined. There exists an interdependency of this parameter with CMN_HTTP_PROXY_PORT mentioned above.
26	CMN_INT_360_ACCRU­AL_DAYS_MTHD	This parameter is used to specify the interest accrual method for 360 days, to be used by the System for all calculations with interest. Currently two methods are supported. Input parameter value is ‘US’ or ‘EU’ representing American and Euro­pean method of interest accrual for 360 days.
27	CMN_TEST_TOOL_LOG­GING	This parameter is used to set testing tool logging parameter
28	CMN_SCHEMA_ID	This is used to specify the schema identifier for all users.
29	CMN_SCHEMA_NAME	This is used to specify the Oracle User Name for a specific schema. Input parameter value is user defined.
30	CMN_SCHEMA_PASS­WORD	This captures the password for Oracle, for the specific schema. Input parameter value is user defined. This parameter need not be enabled when in Oracle Network.
31	CMN_SERVER_HOME	This parameter captures the Server Home Direc­tory. Input parameter value is user defined.
32	CMN_­SERVER_TEMP_DIR	This parameter is used to specify the temporary directory on the server along with the path. Input parameter value is user defined.
33	CMN_SER_ENVIRON­MENT_FILE	This parameter captures the environment file (and its path) for running the Operating System com­mands from Job Service. Input parameter value is user defined.
34	CMN_SYSTEM_UNDER_­MAINTENANCE	This parameter specifies whether the system is under maintenance or not. Input parameter value is Boolean (Yes/No).
35	CMN_WALLET_PASS­WORD	This parameter is used to specify the common wallet password. Input parameter value is user defined.
36	CMN_WALLET_PATH	This parameter is used to specify the common wallet path for oracle database. Input parameter value is user defined.
37	CPP_NO_OF_PROMISES	This parameter is used to define the maximum number of promises/chances allowed for a cus­tomer who is delinquent and promises to pay. Input parameter value is numeric with no upper limit.
38	CPP_PROMISE_HELD_­DAYS	This parameter is used to define the maximum number of days after the promises made by the customer to pay are broken to initiate further actions. Input parameter value is numeric with no upper limit.
39	CRD_CHS_BIN	This parameter holds the value of the credit card BIN (Bank Identification Number for Credit Cards), for CHASE interface. Input parameter value is user defined. (P.S: OFSLL supports CHASE interface for credit card payments processing)
40	CRD_CHS_CUR_CODE	This parameter is used to specify the currency code of the transacting currency for CHASE inter­face. Input parameter value is user defined.
41	CRD_CHS_DIR_PATH	This parameter is used to specify the directory path for CHASE payment interface for Credit Cards. Input parameter value is user defined.
42	CRD_CHS_IND_TYPE	This is used to specify the industry type for CHASE payment interface for Credit Cards. Input parameter value is user defined.
43	CRD_CHS_MER­CHANT_ID	This captures the merchant ID number for CHASE payment interface for Credit Cards. Input parame­ter value is user defined.
44	CRD_CHS_RE­MOTE_HOST_NAME	This captures the remote host name for seeking approvals for CHASE payment interface. Input parameter value is user defined.
5	CRD_CHS_SEC_RE­MOTE_HOST_NAME	Similar to the previous parameter this captures the secondary remote host name of CHASE interface for seeking approvals for credit card payments. Input parameter value is user defined.
46	CRD_CHS_TIMEOUT	This parameter is used to define the timeout limit when polling the interface for processing credit card payments. Input parameter value is numeric.
47	CRD_CHS_USR_ID	This parameter captures the user id for CHASE interface which is required whenever the System needs to access/seek authorizations/process pay­ments for credit cards etc. Input parameter value is user defined.
48	CRD_PTB_RE­MOTE_HOST_NAME	This is the Protobase Remote Host Name
49	CRD_PTB_RE­MOTE_HOST_PORT	This is the Protobase Remote Host Port
50	CRD_PTB_TIMEOUT	This is the Protobase Timeout Value
51	CRD_SOURCE_TYPE_CD	This is the Source Type Code
52	DDT_CREATE_DUE_­DATE_HISTORY	This parameter must be enabled to create a due date history for any account. Due date history sub tab under Transaction history displays the delin­quency history of an account in a tabular format detailing Due date, Due Amount, Last Payment date, Payment Amount, Balance Amount, Days past due and Payment received flag. The input parameter value for this parameter is Boolean (Yes/No).
53	DECI­SION_BUY_RATE_TOL­ERANCE	This parameter is used to define the variance in buy rate
54	EDF_DIALER_ACCT_­TYPE	This parameter is used to set up the account num­ber reference for the dialer file to pick-up records for Auto dialer interface. Input parameter value is account number.
55	FIN_TIMEOUT	This parameter is used to define the polling inter­val for Fax-in service, i.e. minutes after which the Fax-in service would poll to establish a connection periodically. Input parameter value is numeric.
56	FLL_BPEL_PROCESS	This parameter is set to use BPEL process in OFSLL. Input parameter value is Boolean (Yes/No).
57	ICA_INPUT_FILE_FOR­MAT	This parameter is used to define the input call activity file format
58	IFD_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for IFD file location
59	IFD_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle direc­tory object name for IFD file location
60	INCOM­ING_LOB_PURGE_DAYS	This parameter is used to define the incoming pro­cess file table purge days
61	INPUT_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for INPUT file location
62	ITU_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for ITU file location
63	ITU_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle direc­tory object name for ITU file location
64	IVR_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for IVR file location
65	IVR_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle direc­tory object name for IVR file location
66	JSC_START_OF_BUSI­NESS_TIME	This parameter is used to set the start of business time. Input parameter value is time in 24 hour for­mat.
67	JSC_TIMEOUT	This parameter is used to set the polling interval for job scheduler. Input parameter value is numeric. To check whether it represents minutes/seconds.
68	JSV_ARCHIVE_­SERVER_CONFIG	This parameter is used to set the configuration file for reports archive server. Input parameter value is user defined.
69	JSV_ARCHIVE_­SERVER_URL	This parameter is used to specify the archive server url. Input parameter value is user defined.
70	JSV_BI_PASSWORD	This parameter is used to define the BI Publisher Password
71	JSV_BI_USER	This parameter is used to define the BI Publisher User ID
72	JSV_TEMPORARY_DI­RECTORY	This parameter is used to define Oracle directory object name for Job Service Temp file location
73	JSV_BI_PASSWORD­JSV_REPORTS_RUNT­IME	This parameter is to specify the reports runtime program. Input parameter value is user defined.
74	JSV_REPORTS_RUNT­IME_CMDFILE	This parameter is used to specify the reports runt­ime command file. Input parameter value is user defined.
75	JSV_REPORTS_­SERVER_CONFIG	This parameter is used to specify the configuration file for reports server. Input parameter value is user defined.
76	JSV_REPORTS_­SERVER_URL	This is used to specify the URL for the reports server. Input parameter value is user defined.
77	JSV_REPORT_AR­CHIVE_DIRECTORY	This is used to specify the path & directory of Reports archive, input parameter value being numeric.
78	JSV_SMTP_SERVER	This parameter specifies the SMTP server used by job service for sending email messages. Input parameter value is user defined.
79	JSV_TIMEOUT	This is to specify the polling interval for the job ser­vice during time out. Input parameter value is numeric. To check whether it represents minutes/seconds.
80	JSV_USE_BI_PUBLISHER	This parameter defines whether BI publisher should be used to process reports are not. Input parameter value is Boolean (Yes/No).
81	JSV_USE_REPORTS_­SERVER	This parameter is used to specify whether reports server from job service should be used or not. Input parameter value is Boolean (Yes/No).
82	LBX_TXN_GROUP­ING_CNT	This parameter is used to specify the no. of records per batch for payment transactions and lock box batch records. Input parameter value is numeric.
83	LCO_COL_LET­TER1_GEN_DAYS	This parameter specifies the number of days post which first collection letter should be generated for accounts with dues unpaid. Input parameter value is numeric.
84	LCO_COL_LET­TER2_GEN_DAYS	This parameter specifies the number of days post which second collection letter should be generated for accounts with dues unpaid. Input parameter value is numeric.
85	LCO_COL_LET­TER3_GEN_DAYS	This parameter specifies the number of days post which third collection letter should be generated for accounts with dues unpaid. Input parameter value is numeric.
86	LIEN_RELEASE_DAYS	This parameter is used to define the Lien Release Days
87	LOCKBOX_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for Lockbox file location
88	LOCKBOX_PRO­CESSED_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for processed Lockbox file loca­tion
89	LOR_ADVERSE_AC­TION_GEN_DAYS	This parameter is used to specify the number of days after the third collection letter post which the adverse action letter is to be generated. Input parameter value is numeric.
90	LOG_LOB_PURGE_DAYS	This parameter is used to log files header table purge days
91	MAX_AGED_TXN_AU­THORIZE_DAYS	This parameter is used to specify the maximum number of days within which a transaction should be authorized. Input parameter value is numeric and represents the number of days.
92	MAX_VOID_TXN_AU­THORIZE_DAYS	This parameter is used to set the maximum days to authorize transaction
93	OCP_CUSTOMER_P­MT_SITE_ID	This parameter is used to set the customer pay­ment extract file site id
94	OCP_IN­CLUDE_ACH_ACC	This parameter is used to set the customer pay­ment extract including ach accounts
95	OUTGO­ING_LOB_PURGE_DAYS	This parameter is used to define the outgoing pro­cess file table purge days
96	OUTPUT_DIRECTORY	This parameter is used to define Oracle directory object name for OUTPUT file location
97	PAC_ARCHIVE_DAYS	This parameter is used to define number of days for periodic archiving of account. Input parameter value is numeric.
98	PAC_OARCHIVE_DAYS	This parameter is used to define the number of days for archiving accounts from ‘O’ tables i.e. old tables. Input parameter value is numeric
99	PAP_ARCHIVE_DAYS	This parameter is used to define the number of days for archiving applications on a periodic basis. Input parameter value is numeric.
100	PAP_OARCHIVE_DAYS	This parameter is used to define the number of days for archiving applications from ‘O’ tables. Input parameter value is numeric.
101	PCU_CHECK_REFUND_­DAYS	This parameter is used to specify the maximum number of days within which an overpayment from the customer can be refunded. Input parameter value is numeric.
102	PDC_PRE_PROCESS_­DAYS	This parameter value will define the number of days prior to the due day, regular account PDC process should be initiated. Input parameter value is numeric.
103	PENDING_PDC_DAYS	This parameter value will define the number of days before the initiation day for pending PDC accounts.
104	PGL_ARCHIVE_DAYS	This parameter defines the number of days, post which the transactions in GL would be archived. Input parameter value is numeric
105	PGL_OARCHIVE_DAYS	This parameter is used to define the number of days, post which the transactions in GL will be moved to the ‘O’ tables. Input parameter value is numeric.
106	PJR_PURGE_DAYS	This parameter is used to specify the days post which the job requests are to be purged. Input parameter value is numeric.
107	POD_PURGE_DAYS	This parameter is used to define the number of days after which the Output data file headers are to be purged. Input parameter value is numeric.
108	PPA_ARCHIVE_DAYS	This parameter is used to specify number of days after which pools and its transactions archiving is to be done to ‘O’ tables. Input parameter value is numeric.
109	PPA_OARCHIVE_DAYS	This parameter is used to specify number of days after which pools and its transactions archiving is to be done to ‘OO’ tables. Input parameter value is numeric
110	PPR_ARCHIVE_DAYS	This is used to specify the days for archival of pro­ducers details on a regular basis. Input parameter value is numeric.
111	PPR_OARCHIVE_DAYS	This is used to specify the days after which the producers details from ‘O’ tables need to be archived. Input parameter value is numeric.
112	PPX_ARCHIVE_DAYS	This is used to specify the days after which pro­ducer transactions are to be archived. Input parameter value is numeric.
113	PPX_OARCHIVE_DAYS	This is used to specify the days after which the producer transactions are to be moved from ‘O’ tables. Input parameter value is numeric.
114	PJR_COPY_PURGED_­DATA	This parameter is used to copy data into purge tables
115	PST_ARCHIVE_DAYS	This parameter specifies the number of days for which the statements are to be archived. Input parameter value is numeric.
116	PST_OARCHIVE_DAYS	This parameter specifies the number of days for which the statements are to be archived in the ‘O’ tables. Input parameter value is numeric.
117	PTT_PURGE_DAYS	This is used to specify the number of days after which the PTT table is to be purged. Input parame­ter value is numeric.
118	PTX_ARCHIVE_DAYS	This parameter is used to specify the number of days the transactions are to be archived. Input parameter value is numeric.
119	PTX_OARCHIVE_DAYS	This parameter is used to specify the number of days after which the archived transactions from ‘O’ tables are to be moved. Input parameter value is numeric.
120	PTX_TX­N_LAST_PURGE_DT	This parameter stores the date when transactions were purged last in the OFSLL system. Input parameter value is date.
121	PUL_PURGE_DAYS	This parameter is used to specify the number of days post which the User login details are to be purged. Input parameter value is numeric.
122	PVA_ARCHIVE_DAYS	This parameter stores the number of days for archival of regular vendor assignments. Input parameter value is numeric.
123	PUP_ARCHIVE_DAYS	This parameter stores the number of days for archival of transaction upload. Input parameter value is numeric
124	PUP_OARCHIVE_DAYS	This parameter is used to specify the number of days after which the archived transactions from ‘O’ tables are to be moved. Input parameter value is numeric
125	PUP_TUP_LAST_PURGE_DT	This parameter stores the date when transactions upload were purged last in the OFSLL system. Input parameter value is date.
126	PVA_OARCHIVE_DAYS	This parameter value specifies the number of days for archival of vendor assignments from ‘O’ tables to ‘OO’ tables. Input parameter value is numeric.
127	PVI_ARCHIVE_DAYS	This parameter is used to specify the number of days for which the regular vendor invoices are to be archived. Input parameter value is numeric.
128	PVI_OARCHIVE_DAYS	This parameter is used to specify the number of days post which the regular vendor invoices are to be moved from ‘O’ tables to ‘OO’ tables. Input parameter value is numeric.
129	RAC_LOAD_FREQUENCY	This parameter is used to specify Accounts RDH Load Frequency
130	RAP_LOAD_FREQUENCY	This parameter is used to specify Applications RDH Load Frequency
131	RAT_LOAD_FREQUENCY	This parameter is used to specify Asset Tracking RDH Load Frequency
132	RBK_LOAD_FREQUENCY	This parameter is used to specify Bankruptcy Details RDH Load Frequency
133	RCA_LOAD_FREQUENCY	This parameter is used to specify Call Activities RDH Load Frequency
134	RCH_LOAD_FRE­QUENCY	This parameter is used to specify Deficiency Details RDH Load Frequency
135	RCO_LOAD_FRE­QUENCY	This parameter is used to specify Contracts RDH Load Frequency
136	RFO_LOAD_FREQUENCY	This parameter is used to specify Repo-Foreclo­sure RDH Load Frequency
137	RPR_LOAD_FREQUENCY	This parameter is used to specify Producers Rdh Load Frequency
138	RST_LOAD_FREQUENCY	This parameter is used to specify Setup Data RDH Load Frequency
139	RTX_LOAD_FREQUENCY	This parameter is used to specify Txns RDH Load Frequency
140	SALESAGENT_­MAIL_SEND_IND	This parameter is used to specify whether decision fax needs to be sent to sales agent (yes/no)
141	SCORING_PARAME­TER_ALERT	This parameter is used to set the scoring parame­ter alert
142	SQL_DIRECTORY	This parameter is used to set the Oracle directory object name for SQL file location
143	TES_ANA_PRE_PROCESS_CYCLES	This parameter is used to specify the pre-process cycles required for Escrow analysis. Input parame­ter value is numeric.
144	TES_DSB_ANALY­SIS_PERCENT	This parameter is used to specify the percentage for escrow disbursements. Input parameter value is numeric.
145	TES_DS­B_PRE_PROCESS_DAYS	This is used to specify the number of days for pre-process for escrow disbursements. Input parame­ter value is numeric.
146	TPE_AMORTIZE_AC­CRUED_INT_ONLY	This parameter is used to specify that system has to amortize accrued interest at month end
147	TPE_APPLY_LTC_­FROM_CURR_DUE_DT	This parameter is used for pyramid law fee method to apply late charge from current due date
148	TPE_ESC_ANALY­SIS_DELQ_AMT	Parameter considers billed but uncollected amount for escrow analysis
149	TPE_EXCESS_PAY­MENT_TO_MEMO	Excess payment on the account will be moved to memo payment.
150	TPE_EXCLUDE_ESC_LTC	This parameter defines whether escrow should be included or excluded while calculating late charge. Input parameter value is Boolean (Yes/No).
151	TPE_EXT_CY­CLES_BACKDATED	This parameter is used to define the maximum extension cycles allowed for back dating. Input parameter value is numeric with no upper limit
152	TPE_FUTURE_PAYOFF_­DAYS	The value specified in this parameter validates the ‘Valid Up to Date’ with ‘Payoff quote’ during mone­tary transactions posting.
153	TPE_GL_RE­FUND_HOLD_DAYS	This parameter is used to define the number of days the non-refunded amount can be held in GL. Input parameter value is numeric.
154	TPE_MAX_CY­CLES_BACKDATED	This parameter is used to define the maximum cycles that are allowed for back dating in OFSLL. Input parameter value is numeric.
155	TPE_MIN_1098_INT_AMT_PAID	This parameter is used to specify the lower limit or minimum interest amount paid for 1098 i.e. Mort­gage Interest Statement. In the US, FIs need to report mortgage interest of $600 or more received from individuals, during the course of their busi­ness. Input parameter value is 600, the minimum value above which reporting by FI is required in form 1098 for each mortgage account.
156	TPE_OLDEST_­DUE_DT_NEW_MTHD	This parameter is enabled to specify whether new method for calculation of oldest due date based on given data should be used or not. Input parameter value is Boolean (Yes/No).
157	TPE_PAID_TO_CLOSE_­DAYS	This parameter is used to specify the number of days allowed post which a paid account would be closed. Input parameter value is numeric.
158	TPE_PAYMENT_TO_­MULTI_ACCOUNTS	This parameter is enabled to allow one payment for dues in multiple accounts. Input parameter value is Boolean (Yes/No).
159	TPE_PAYOFF_VAL­ID_THRU_DAYS	This parameter is used to specify the number days the pay-off quote is valid by default. i.e. if the parameter is set as 7, the payoff quote is valid for 7 days and customer can pay the quoted amount as final closure amount within those days. Input parameter value is numeric.
160	TPE_PMT_POST_EOD	This parameter is used to allow payments when the batch process for End of Day is running. Input parameter value is Boolean (Yes/No). If this is set to ‘Y’, payments can be allowed during EOD.
161	TPE_SCHGOFF_DLQ_­DAYS	This parameter is used to define the number of delinquent days to treat an account for SCHGOFF (charge – off). Input parameter value is numeric. (To verify)
162	TPE_SCHGOFF_RE­VIEW_DAYS	This parameter is used to define the number of days allowed for review of SCHGOFF accounts. Input parameter value is numeric.
163	TPE_SCRA_DEFAULT_IN­TEREST_RATE	This parameter is used to define the default inter­est rate that is to be applied for customers who are in military duty. OFSLL will apply the lower of the prevailing interest rate or SCRA default interest rate specified through this parameter. Input parameter value is numeric (in this case 6, which is interest rate to be applied for SCRA accounts.
164	TPE_SHOW_BACK­DATE_WARNING	This parameter is used to define whether a warn­ing message is to be shown if monetary transac­tion is backdated
165	TPE_ST­M_INC_ALL_TXNS	This parameter is enabled to define whether all transactions should be included in the statements or otherwise. Input parameter value is Boolean (Yes/No).
166	TPE_STOP_COMP_DELQ_DAYS	This parameter is used to stop computation when delq days > 60
167	TPE_TXN_POST_DE­FAULT_GLDATE	This parameter is used to default GL date in date type parameters during txn posting (y/n)
168	TPE_VOID_TO_CLOSE_­DAYS	This parameter is used to define the number of days allowed for closing Void accounts. Input parameter value is numeric.
169	UIX_DEFAULT_IMAGE_­PATH	This parameter is used to define the default image directory maintained for the purpose of online attachment of document images to an application using documents maintenance section under Account documentation. Input parameter value is user defined.
170	UIX_DIRECT_LOAN_­COMBO_ULN_UFN	This parameter when set to yes allows underwrit­ing and funding to be carried on by a single responsibility for direct loans only. Input parameter value is Boolean (Yes/No).
171	UIX_INCOMING_FILE_­PATH	This parameter is used to specify incoming file path of app server
172	UIX_LOCAL_COUN­TRY_CD	Through this parameter we can set the local coun­try where an FI has multiple branches across dif­ferent geographies. Input parameter value is user defined.
173	UIX_LOCK_UN­LOCK_AND_COPY	This parameter is used to enable the user inter­face lock / unlock and copy features. Input param­eter value is Boolean (Yes/No).
174	UIX_MAX_ACC_­SEARCH_ROWS	This parameter is used to specify the maximum number of account rows to be returned for search functionality. Input parameter value is numeric.
175	UIX_MAX_APP_­SEARCH_ROWS	This parameter is used to specify the maximum number of application rows to be returned for search functionality. Input parameter value is numeric.
176	UIX_OUTGOING_FILE_­PATH	This parameter is used to specify outgoing file path of app server
177	UIX_REPORTS_­SERVER_CONFIG	This parameter can be used to specify the user interface reports server configuration file. This is not required for OFSLL.
178	UIX_REPORTS_­SERVER_URL	This parameter sets the URL for Reports server. Input parameter value is user defined.
179	UIX_SHOW_LN_VARIA­BLE_RATE_TABS	This parameter can be used to show loan variable rate tabs. Input parameter value is Boolean (Yes/No). This is not required for OFSLL.
180	UIX_UTILITIES_SERV­LET_URL	This parameter can be used to specify the User Interface utilities servlets URL. This is not required for OFSLL.
181	UPR_PRO_NBR_SYS­_GENERATED	This parameter can be used to specify whether producer number should be system generated or seek input from user. Input parameter value is Boolean (Yes/No). Generally this is set to yes for system generation.
182	VEV_NADA_TOKEN_URL	This parameter is used to set the token URL for vehicle evaluation interface NADA. Input parame­ter value is user defined.
183	VEV_NADA_UPDATE_­DAY	This parameter is used to specify the day of the month to update the vehicle evaluations every month. Input parameter value is numeric.
184	VEV_NADA_URL	This parameter is used to set the URL for vehicle evaluation interface NADA. Input parameter value is user defined.
185	VEV_NADA_USER_ID	This parameter is used to specify the User id for login to the NADA interface. Input parameter value is user defined.
186	VEV_NADA_USER_PASS­WORD	This parameter is used to specify the password for login to the NADA interface. Input parameter value is user defined.
187	VEV_VALUATION_RE­GION	This parameter is used to define the default region for vehicle evaluation. Input parameter value is the region name, and is user defined.
188	VEV_VALUATION_­SOURCE_CD	This parameter is used to specify the default vehi­cle evaluation source code. Input parameter value is user defined. A number of parameters are pos­sible in OFSLL as below: 1.Appraisal Company 2.Broker 3.BUC GUIDE 4.DATA QUICK 5.NAMS/SAMS SURVEY – USED 6.REALTOR 7.NADA INTERFACE USED CARS 8.BLACKBOOK INTERFACE USED CARS 9.KELLY INTERFACE 10.NADA – NEW 11.NADA – USED 12.KELLY NEW BLUE BOOK 13.KELLY USED BLUE BOOK 14.INVOICE 15.BLACK BOOK 16.NADA INTERFACE COMMERCIAL TRUCKS 17.COMPANY INVOICE 18.GOLD BOOK 19.GALVS 20.OTHER 21.ALG
189	WFP_DIRECTORY	This parameter is used to specify the Oracle direc­tory object name for WFP file location
190	WFP_MAX_CY­CLES_BACKDT	This parameter is used to specify the back dated cycles date for WFP.
191	WFP_PROCESSED_DI­RECTORY	This parameter is used to define oracle directory object name for wfp file location.
192	WFP_REVERSE_TX­N_IND	This parameter is enabled to define the WFP reversal indicator. Input parameter value is Boolean (Yes/No).
193	XAE_DEALUPD_MAX_AL­LOWED_DAYS	This parameter is used to define the max allowed days for Deal Update
194	XAE_DEALUPD_AL­LOWED_IND	This parameter is used to indicate whether deal update is allowed or not
195	XSL_TAX_INTERFACE	This parameter is used to specify the sales tax interface in OFSLL. Input parameter value is user defined. In this case it is held as ‘Manual’.
196	OUTBOUND_CALL_Q	This parameter is used to generate reports (includ­ing emailing statements/letters) using Application Server instead of Database server.
197	ACA_PRE_PROCESS_­DAYS_FIRST	This parameter is used to configure the number of days before the debit day for ACH process in first time/ one-time case
198	IPR_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle direc­tory object name for processed IPR file location
199	IPR_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for IPR file location
200	UIX_PWD_MGMT_EX­TERNAL_URL	This parameter is used to set external password management url, if applicable
201	UIX_PWD_MGMT_EX­TERNAL	This parameter is used to define the parameter if password management is external. (SET Y IF PASSWORD MANAGEMENT IS EXTERNAL (Y/N)).
202	ICU_PROCESSED_DI­RECTORY	This parameter is used to define the Oracle direc­tory object name for processed ICU file location
203	ICU_DIRECTORY	This parameter is used to define the Oracle direc­tory object name for ICU file location
204	UIX_BILL_CYCLE_AL­LOWED_IND	This parameter is used to indicate whether Billing cycle is allowed at the application level
205	CMN_EOD_SLEEP_MINS	This parameter is used to set in minutes the EOD sleep time
206	CMN_CORE_BANK_TX­N_CD	This parameter is used to set code for OFSLL and Core Banking integration
207	UIX_DIRECT_DISB_MAN­UAL_SELECT	This parameter will allow manual selection of dis­bursement mode for direct loans
208	ICC_DLQ_AMT_EX­CLUDED	This parameter enabling will exclude delinquency amount for CASA account
209	CMN_CORE_BANK_IND	This parameter is used to set whether OFSLL can integrate with Core Banking.
210	BKRP_FILE_REC_LIMIT	This parameter is used to set the limit of total num­ber of records allowed to be added in the ‘Input Data File’ shared from external interface. Note: if the number of records exceeds the set limit, multiple ‘Input Data Files’ are to be created.
211	UVN_VEN_NBR_SYS­_GENERATED	This parameter is used to validate if ‘Vendor Num­ber’ has to be auto generated (if set to Y) or to be specified manually in the Vendor details screen.
212	METRO_WITHOUT_COL­L_IND	This parameter indicates whether Metro II report­ing is handled without OFSLL Collections module being used. If the parameter value is set as ‘Y’ i.e. collection module is not used, system updates the collateral status directly as part of ‘REPO’ call activity. However when Collections module is being used, the Collateral status is tracked with the reposses­sion details updated in 'Repo/Foreclosure' screen of Collections module.
213	METROII_­FIRST_DELQ_DT_ADD_­DAY	This parameter is used to calculate the first delin­quency date that needs to be reported in the Metro II reporting file. By default the parameter is 'disabled' indicating that the initial delinquency date calculated by the system is used for Metro II reporting. The same needs to be enabled to add the parametrized num­ber of days to the system calculated first delin­quency date for the Metro II reporting purpose.
214	DAYS_TO_PULL_CR­B_REPORT	This parameter is used to configure the number of days permitted to pull a Bureau report from the same company and for the same customer.
215	XWS_ACS_RESP_­MULTI_RECORD_IND	This parameter is used to indicate if multiple records exist in the response file received for account search. Accordingly, when there are multiple records found and this parameter is enabled and set to ‘No’ (default), system displays an error message “Too Many Records Found. Please Refine Search by Adding One More Parameter” However, when this parameter is set to ‘Yes’, sys­tem only indicates that there are multiple records/rows in response file.
216	GRI_DLQ_DAYS_AU­TO_STATUS_CHG	This parameter is used to define the delinquency days which inturn is used to automatically update the status of a work order to ‘PENDING ON HOLD’ status.
217	TPE_PMT_POSTING_­CLS_ACCOUNT	This parameter is used to define the payment posting criteria for Closed - Paid Off/ Charged-off accounts. Accordingly, OFSLL accepts payment posting on closed accounts only when the parameter is set to ‘Y’ and all the payments received through Pay­ment Entry screen or ‘Payment Upload’ file are posted to a ‘Suspense’ account.
218	TPE_BACKDT_P­MT_POSTING	This parameter is used to define the payment posting criteria for backdated payments for the fol­lowing type of account conditions: - Paid off - Charged-off - Account under activation - Account under conversion - Non-performing Account - PC2 SI (Pre-computed to Simple Interest) Reschedule Accordingly, OFSLL accepts backdated payment posting only when the parameter is set to ‘Y’ and all the payments received through Payment Entry screen or ‘Payment Upload’ file are posted to a ‘Suspense’ account.
219	EXP_PA_­SOFT_PULL_IND	This parameter when enabled allows ‘Soft Pull’ Credit Bureau request, specifically for Experian Premier Attribute Consumer Report without impacting the consumer FICO score.
220	PMT_BATCH_POSTING	This parameter (PAYMENT BATCH POSTING PREFERENCE) is used to define the status of payment transactions which are uploaded in bulk through a batch process.
221	PAC_PURGE_DAYS	This parameter allows to define the number of days after which the data from archival folders are to be deleted permanently. Purging happens based on elapsed number of days i.e. if value is set to 60 days, only those records which are older by 60 days in archival folder are deleted.

A.3 Organization Parameters

Organization parameters control the functions related to User login, password expirations, responsibilities and accessibility limits in the OFSLL system. Individual parameters can be created with different values for uniquely defined organizations, divisions, and responsibility combinations.

There are three more dimensions other than parameter name, description and enabling (similar to system parameters) as indicated below:

1. Organization
2. Division
3. Responsibility

These dimensions help to define the applicability of the responsibility for specific User in an Organization across selected Divisions/departments.

When determining which parameter to use, OFSLL system selects the best match based on a hierarchical sort by the Organization, Division, and Responsibility fields, with values of 'ALL' being a lower order match than an exact match.

While the system allows for Organization parameters to be defined at all three hierarchical levels (organization, division, and responsibility), not all will be applicable to each parameter.

Sl.No	Parameter	Description
1	MAX_PASSWORD_HISTO­RY_CHECK	This is used to set limit for number of times a password has been repeated during password change. This can be set for specific branches of the Organization, Divisions and Users based on responsibilities. Numeric value to be input to spec­ify the limit.
2	UCS_GROUP_FOL­LOWUP_DAYS	This parameter is used to set up the number of days range for Group follow-up field in customer service screen which displays the set of accounts that share same account condition as the selected account and bear the same customer ID. The pre-requisite for this is Group Follow-up indicator should be enabled in queue setup. Input value is numeric.
3	UCS_REVIEW_­QUEUE_ALLOWED	This is used to specify whether review can be done by the specific responsibility (user group) without entering details in call activities/activities. Parameter value to be input is Boolean (Yes/No).
4	UIX_AP­P_VIEW_ALL_APPS	The system uses this parameter to determine which users have the ability to view all applica­tions. The system selects the best match based on a hierarchical sort by Organization, Division and Responsibility fields, with values of ‘ALL’ being a lower order match than an exact match. Input parameter value is Boolean (Yes/No).
5	UIX_HIDE_RESTRICT­ED_DATA	This is used to hide sensitive data relating to the Contract / Applicant to a specific group/responsi­bility etc. Suppose there is a need to hide data relating to SSN, Bank account details etc. to a specific user responsibility who will not need such data, this parameter can be enabled with input value Boolean (Yes/No). If this parameter is set to ‘Y’, the details appear in a masked format (for e.g. SSN – XXX-XX-456)
6	UIX_SMTP_SERVER	This parameter is used to set up the email server for user interface. The input value would be ‘SETME’ and check the ‘Enable’ flag.
7	UIX_VIEW_SE­CURED_ACCOUNTS	This is used to specify whether an account can be viewed by a specific responsibility (users). Param­eter value is Boolean (Yes/No) and when flagged as Yes, such accounts would be viewable only by users defined in the Organization, Division hierar­chy with the specified responsibilities. For exam­ple, all employee accounts may not be viewable by all users and should be made available only to the HR department with specific responsibility lev­els. Note: While creating application, selecting appro­priate applicant’s classification would be essential for this parameter to be effective.
8	UIX_VIEW_SE­CURED_APPLICATION	This is used to specify whether an application can be viewed by a specific responsibility (users). Parameter value is Boolean (Yes/No) and when flagged as Yes, such applications would be viewa­ble only by users defined in the Organization, Divi­sion hierarchy with the specified responsibilities. For example, all employee accounts may not be viewable by all users and should be made availa­ble only to the HR department with specific responsibility levels. Note: While creating application, selecting appro­priate applicant’s classification would be essential for this parameter to be effective.
9	ULG_DAY_END	This is used to specify the upper limit time in day for a user to be able to work in the System. Parameter value is numeric and range is 1-24, else system will throw error.
10	ULG_DAY_START	This is used to specify the lower limit time in day for a user to be able to work in the System. Parameter value is numeric and range is 0-24, else system will throw error
11	ULG_FAILED_LOGIN_TRI­ALS_MAX	This parameter is used to specify the maximum number of login trials allowed before disabling the User ID due to security reasons. Input parameter value is numeric with upper limit of 999999999999.
12	ULG_INACTIVITY_DAYS_­MAX	This parameter is used to specify the maximum number of days the User ID can be without utiliza­tion before disabling the User ID due to security reasons. Within the specified number of days the User Id must be utilized for sign in at least once. Input parameter value is numeric with upper limit of 999999999999.
13	ULG_PWD_CASE_SENSI­TIVE_REQ	This is used to allow all passwords to be case sen­sitive or otherwise. Input parameter value is Boolean (Yes/No). When this parameter is set as ‘NO’, password would be stored in Upper case. If this parameter is set to N. then the ULG_P­WD_LOWER_CHAR_REQ parameter should also be set to N.
14	ULG_PWD_CHANGE_­DAYS_ACTUAL	This is used to set the maximum number of days after which system will force a password change, in cases where the User has not changed the password. Input parameter value is numeric with upper limit of 999999999999.
15	ULG_PWD_CHANGE_­DAYS_PROMPT	This is used to set the maximum number of days after which system will prompt the User for pass­word change, in cases where password has not been changed within the set period. Input parame­ter value is numeric.
16	ULG_PWD_LENGTH_MIN	This is used to set the minimum length of pass­word string that is required. If this criterion is not met, system would throw an alert specifying mini­mum character length required to be input.
17	ULG_PWD_LOW­ER_CHAR_REQ	This is used to allow at least one lower case char­acter in password strings. Input value is Boolean (Yes/No). Setting this as ‘NO’ would mean pass­words would be allowed in uppercase only.
18	ULG_PWD_NBR_REQ	This parameter allows setting password with at least one numeric character. Input value is Boolean (Yes/No) and setting this as ‘YES’ would require passwords to have at least one numeric character.
19	ULG_PWD_SPE­CIAL_CHAR_REQ	This parameter is used to allow special characters like ‘$’, ‘#’, ‘@’, in passwords. Input value is Boolean (Yes/No) and setting this as ‘YES’ would require passwords to have at least one special character.
20	ULG_PWD_UP­PER_CHAR_REQ	This is used to allow at least one upper case char­acter in password strings. Input value is Boolean (Yes/No). Setting this as ‘NO’ would mean pass­words would be allowed in lowercase only.
21	ULG_WEEK_END	This parameter enables to set the last day of the week when a user can have access to the system. Input parameter value is numeric ranging from 1 to 7. This is useful in business requirements where the Organization does not need a specific set of responsibilities (users) to not access the system on a weekend / week-off day etc.
22	ULG_WEEK_START	This parameter is used to set the start day of the week when a user is allowed to access the sys­tem. Input parameter value is numeric.
23	CRB_ERROR_VALIDA­TION_IND	This parameter is used to validate the Credit Bureau report generation request depending on the number of days permitted to pull a Bureau report from the same company and for the same customer and report as either warning/error. When the number of days is less than or equal to the permitted days (as defined in parameter DAYS_TO_PULL_CRB_REPORT), system dis­plays an ‘Error’ message stating ‘Bureau Report exists for the same Customer from the same Bureau for Account# XYZ’ along with list of account number(s) and/or application number(s). If not, a ‘Warning’ message is display and request is accepted for processing. Note: Both ‘CRB_ERROR_VALIDATION_IND’ and ‘DAYS_TO_PULL_CRB_REPORT’ are to be enabled for Credit Bureau report processing.

A.4 Company Parameters

Company parameters control the processes associated with functions that vary for different companies and branches. These parameters address credit scoring, credit bureau interfaces, fax services, and fax generation.

Individual parameters may be set up with different values for uniquely defined company and branch combinations (i.e. these can be defined to the level of branches in each company or a group of companies in terms of applicability).

Sl.No	Parameter	Description
1	AUD_ADV_REASON_­MODEL	This parameter is used to set-up default adverse action reasons for scoring models during set-up in the Parameters sub page. Whenever the flag ‘Bureau Score Reasons’ is unchecked during credit bureau scoring model set-up, then automat­ically rejected applications scored using this scor­ing model picks up the Adverse Action Reasons from the Parameters sub page.
2	AUD_SCORING_METHOD	This parameter is used to set when/where the application scoring method has to be applied within the company. So when the parameter value is chosen as ‘primary applicant only’, the system will perform the application scoring for the primary applicant only and according to other applicable parameters specified. Other parameter input val­ues are Minimum Score, Maximum Score, Mini­mum Tier (Grade), Maximum Tier (Grade).
3	AUD_SCORING_­METHOD_IN_BUREAU	This parameter is used to define what value to be picked up for application scoring from the scores returned from the various bureaus. The input parameter values are Maximum Score and Mini­mum Score. If Maximum score is set-up in com­pany parameters, then for all applications where a bureau report is pulled, the system will pick-up the Maximum score from the different bureaus.
4	CBU_DATA_SET_SIZE	Parameter to define the metro 2 file data selection criteria, option values are monthly, Daily, weekly, semi monthly.
5	CBU_FILE_FORMAT	Metro 2 file format definition, user need to select from the parameter value drop down.
6	CMN_ASE_VALIDATE_­MAKE_MODEL	This parameter is set up to specify to the system whether it needs to validate the asset make and model at the time of data entry. In parameter value is Boolean (Yes/No).
7	CMN_CMB_DE­FAULT_PRINTER	This is used to define the default printer for print­ing. The input parameter value is the printer name. There is no LOV for this field. If no default printer is defined and the parameter enabled, the system would display ‘Undefined’.
8	CMN_WEEKLY_NONBUSI­NESS_DAYS	This parameter is used to set-up the weekly holi­days at the company level. The input parameter value is character string; if no details specified and parameter is enabled, system would display ‘UNDEFINED’.
9	COR_STORAGE_DIREC­TORY	This parameter is used to specify the path/location for Oracle directory object template for corre­spondence documents. Input parameter value is ‘SETME’; if none is specified and parameter ena­bled, ‘UNDEFINED’.
10	DBR_­JOINT_INC_DEBT_WITH_2NDRY	This parameter defines whether system should consider income and debt details of the Spouse and Secondary Applicant along with that Primary Applicant. Input parameter value is Boolean (Yes/No).
11	DBR_­JOINT_INC_DEBT_WITH_SPOUSE	This parameter is used to define whether system should consider the income and debt details of Spouse alone along with that of Primary applicant details. Input parameter value is Boolean (Yes/No).
12	DDP_CRB_EXPIRATION_­DAYS	This parameter is used to define the credit bureau report expiration days. So if this is set as 30, sys­tem will use all available credit bureau reports pulled which are not older than 30 days from cur­rent day, during de-dupe. Input value is numeric with no upper limit.
13	DDP_DE­DUP_DEBT_WITH_2NDRY	This parameter defines whether the system should de-dupe credit bureau liabilities for Spouse and Secondary Applicants, in addition to de-dup­ing Primary applicant’s liabilities. Input parameter value is Boolean (Yes/No).
14	DDP_DE­DUP_DEBT_WITH_SPOUSE	This parameter defines whether the system should de-dupe credit bureau liabilities for Spouse, in addition to de-duping Primary appli­cant’s liabilities. Input parameter value is Boolean (Yes/No).
15	DOT_STORAGE_DIREC­TORY	This parameter is used to define the location/path of the Oracle Directory Object name for Account Document Loading. Input parameter value is ‘SETME’.
16	ECB_EDIT_­FAIL_ANY_APL	This parameter is used to set the credit bureau edit to fail in case the bureau report for any of the applicant fails. Input parameter value is Boolean (Yes/No). So if this parameter is set to ‘YES’, the edit will fail even if one of the applicant’s bureau score fails to qualify.
17	ECB_USE_APL_CUR­RENT_SCORE_CRH	This parameter is used to define whether the sys­tem should run the credit bureau edits only on the current scored applicant bureau. Input parameter value is Boolean (Yes/No).
18	FIN_IMAGE_STATUS_CD	This parameter is used to set-up default image status for fax-in service. The input parameter val­ues are ‘RUSH’, ‘NEW’, ‘SKIP’, ‘BAD’, ‘PRO­CESSED’ and ‘PURGED’.
19	FIN_POP_PASSWORD	This parameter is used to define the pop pass­word to access the fax-in service. Input parameter value is user (System Administrator) defined.
20	FIN_POP_SERVER	This parameter is used to define the pop server to receive the faxes in fax-in service. Input parame­ter value is location and path of the server.
21	FIN_POP_USERNAME	This parameter is used to define the pop user­name to access the fax-in service. Input parame­ter value is user (System Administrator) defined.
22	FIN_STORAGE_DIREC­TORY	This parameter is used to set-up the Oracle direc­tory object name for storing the images received through the fax-in service. Input parameter value is user (System Administrator) defined.
23	FIN_TEMP_DIRECTORY	This parameter is used to define the temporary directory to be used for the fax-in service. Input parameter value is user (System Administrator) defined.
24	LOR_AUTOMATIC_CON_­FUND_FAX	This is used to define the decision fax generation when an application is funded. The input parame­ter value is Boolean (Yes/No), and when this is set as ‘YES’, system automatically generates the fax approval in the pre-defined template whenever an application is approved.
25	LOG_STORAGE_DIREC­TORY	This parameter is used to define the Oracle stor­age directory. Input parameter value is user (Sys­tem Administrator) defined.
26	LOR_AUTOMATIC_AP­PROVAL_FAX	This is used to define the decision fax generation when an application is approved. The input parameter value is Boolean (Yes/No), and when this is set as ‘YES’, system automatically gener­ates the fax approval in the pre-defined template whenever an application is approved.
27	LOR_AUTOMATIC_RE­JECTION_FAX	This is used to define the decision fax generation when an application is rejected. The input param­eter value is Boolean (Yes/No), and when this is set as ‘YES’, system automatically generates the rejection fax in the pre-defined template whenever an application is declined.
28	MAX_LEAD_DAY_AGE	This parameter is used to define the maximum no. of days, post which the sales lead would be con­sidered cold. Input parameter value is numeric with no upper limit.
29	MULTI_OFFER	Through this parameter the multiple offers (sub-tab) in pricing can be enabled or disabled for a Company/Branch. Input parameter value is Boolean (Yes/No). If the flag is set as ‘Y’, the underwriter can view multiple offers and select one of them to be applied for the specific applica­tion.
30	MULTI_OFFER_MAX­_NUMBER	This parameter is used to specify the maximum number of multiple offers that can be permitted for an application. Input parameter value is numeric with no upper limit. If MULTI_OFFER company parameter is set as ‘N’, this parameter can be ignored as there is no use specifying a value.
31	MULTI_OFFER_MAX­_TERM	This company parameter sets the maximum term (as in no. of instalments, whichever billing cycle is selected) for which multiple offers are calculated and displayed during pricing. Input parameter value is numeric.
32	MULTI_OF­FER_MIN_TERM	This company parameter sets the minimum term (as in no. of instalments, whichever billing cycle is selected) for which multiple offers are calculated and displayed during pricing. Input parameter value is numeric.
33	MULTI_OFFER_PMT_TOL­ERANCE	For Multi offer variance in payment is defined in this parameter.
34	MULTI_OFFER_TERM_­VAR	For multi offer Term variance will be defined in the parameter.
35	PRESENT_VALUE_COM­PUTE_RATE	This parameter will perform Present Value Com­putation Rate (Inflation/Discounting Rate).
36	RATE_CHG_L­TR_PRE_PROCESS_­DAYS	This parameter is used to set up the number of days prior to rate change effective date to gener­ate rate change letters in order to provide advance intimation to customers. Input parameter value is numeric with no upper limit.
37	STM_GEN_AFTER_MATU­RITY_IND	This parameter is used to enable the statement generation for an account after the maturity date but Account remains unpaid. Input parameter value is Boolean (Yes/No). If this is set to ‘Y’, statements will get generated for accounts that remain unpaid even after maturity.
38	UIX_RUN_AAI_ACT	This parameter is used by the system to deter­mine whether to create and activate an account online. Input parameter value is Boolean (Yes/No).
39	UIX_UCS_CAC_MAX_­FOLLOWUP_DAYS	This parameter is used to set up the maximum number of days for follow up when the account is in delinquent state. Input parameter value is numeric with no upper limit.
40	UIX_UCS_CAC_MAX­_PROMISE_DAYS	This parameter is used to set up the maximum number of days allowed for customers who prom­ise to pay when following up for delinquent accounts. Input parameter value is numeric.
41	AUD_QUEUE_INI­TIAL_CRB_FAILED	This parameter enabling will Queue the applica­tion if any bureau failed.
42	UIX_UCS_CUA_MAX_­FOLLOWUP_DAYS	This parameter will allow the user to maintain the Collections maximum follow-up days that are allowed in the system.

A.5 Other Parameters

The following additional set of parameters are also available to control system specific data and other administration process.

Sl.No	Parameter	Description
1	CRB_MAX_BU­REAU_PULL	This parameter is used to determine the number of credit reports automatically per applicant. Input parameter value is numeric.
2	CRB_ALL_APL_BU­REAU_PULL	This parameter is used to set up whether credit bureau reports should be pulled for the primary applicant only or to all other applicants also (for joint applications), regardless of their relationship with the primary applicant. Input parameter value is Boolean (Y/N).
3	CBU_FILE_FREQUENCY	This parameter is used to set the Metro II File Fre­quency 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.
4	JOINT_DE­DUP_SPOUSE_LIABILI­TIES	This parameter is used to determine duplicate lia­bilities in the Spouse’s liabilities in de-duping logic. Input parameter value is Boolean (Yes/No).
5	JOINT_DEDUP_ALLAP­L_LIABILITIES	This parameter is used to determine duplicate lia­bilities of all applicants’ liabilities in de-duping logic, irrespective of whether they are related to each other. Input parameter value is Boolean (Yes/No).
6	ASC_COL_SER_ENA­BLED_IND	This parameter is used for enabling the Collection Servicing Indicator. Input parameter value is Boolean (Y/N).
7	CMN_TEST_TOOL_LOG­GING	This parameter is used to set the testing tool log­ging to enable or disable testing tool log in. Input parameter value is Boolean (Yes/No).
8	FIN_DOWNTIME_BEGIN	This parameter is to define the start of period for down time of Fax-in service. Input parameter value is time in 24 hour format.
9	FIN_DOWNTIME_END	This parameter is used to define the end of period for down time of Fax-in service. Input parameter value is time in 24 hour format.
10	FIN_ERROR_LIMIT	This parameter is used to define the error limit for Fax-in service. Input parameter value is numeric.
11	ICA_INPUT_FILE_FOR­MAT	This parameter is used to specify the Input format for call activity file. Two Parameter values are pos­sible – US format and OFSLL format.
12	JSV_BI_USER	This parameter is used to define the BI publisher User ID. Input parameter value is user defined (Admin user).
13	JSV_BI_PASSWORD	This parameter is used to define the BI publisher User password. Input parameter value is user defined (Admin user).
14	PJR_COPY_PURGED_­DATA	This parameter is used to specify whether data should be copied into the purge tables or not. Input parameter value is Boolean (Yes/No).
15	PUP_ARCHIVE_DAYS	This parameter is used to specify the number of days after which the transactions upload details are to be archived. Input parameter value is numeric.
16	PUP_OARCHIVE_DAYS	This parameter is used to specify the number of days after which the transactions upload details are to be moved from ‘O’ tables. Input parameter value is numeric.
17	PUP_TUP_LAST_PURGE_DT	This parameter is used to capture the last date when transactions upload details were purged. Input parameter value is date.
18	TPE_APPLY_LTC_­FROM_CURR_DUE_DT	This parameter is used to specify whether late charge should be applied from current due date for Pyramid Law fee method. Input parameter value is Boolean (Yes/No).
19	TPE_EXCESS_PAY­MENT_TO_MEMO	This parameter will make excess payment to the memo payment by marking this Parameter as YES.
20	TPE_STOP_COMP_DELQ_DAYS	This parameter is enabled to stop computation if the account is delinquent for more than 60 days.