Appendix C :System Parameters

C.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.

C.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.

Parameter

Description

ACA_DLQ_AMT_EX­CLUDED

This parameter is used to exclude delinquency amount for account ACH

ACA_PAYMENT_AU­TO_LOAD

This parameter is used to control posting directly from the ACH file that has been created for customer payments. Input parameter value is Boolean (Yes/No). If the parame­ter 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.

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.

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.

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

ADMIN_SERVER_URL

This parameter is used to define the admin server URL

ADR_DIRECTORY

This parameter is used to define the Oracle Directory Object Name for ADR file location

ADR_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle Directory Object Name for ADR file location

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 Application. Input parameter value is numeric with no upper limit.

AGE_CONTRACT_DAYS

This parameter is used to specify the number of days by which a contract is treated as Aged Contract. Input param­eter value is numeric with no upper limit.

ASC_COL_SER_ENA­BLED_IND

This parameter is used as the Collection Servicing Ena­bled Indicator

CAC_DIRECTORY

This parameter is used to define the Oracle Directory Object Name for CAC file location

CAC_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle Directory Object Name for CAC file location

CHECK_PRINT_PREVIEW

Using this parameter we can allow preview of application in pdf form before printing. Input parameter value is Boolean (Yes/No).

CMN_AMOUNT_ROUND_FACTOR

This parameter is used to define the rounding factor for applicable fields (in this case calculated amounts). Input parameter value is ‘ROUND AMOUNT TO 2 DECIMALS’. Currently system supports rounding factor 2 only.

CMN_AMOUNT_ROUND_METHOD

This parameter is used to define the amount round method during system set-up and would be applicable for all calcu­lated amounts (calculated fees, payment etc.) across the application. Input values are ROUND, RAISE and CUT­OFF:
ROUND: Rounded to nearest number higher or lower
RAISE: Rounded to the nearest higher number
CUTOFF: Truncate the digits without rounding or raising

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.

CMN_APP_­SERVER_HOME

This parameter is used to set the Application Server Home Directory. Input parameter value is user defined.

CMN_CURRENT_MOD­EL_YEAR

This parameter is used to default the Current Model Year.

CMN_DEBUG_LEVEL

This is the Common Debug Level

CMN_DEBUG_METHOD

This parameter allows to define the location to which generic debug logs (other than Alert/Warning and GRI) are to be written. If set to ‘ADVANCE_QUEUE’, system writes the logs in Logs table and if set to ‘UTL_FILE’, system gen­erates the alert log file.

CMN_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing files/documents are to be pro­cessed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

The same is used by the batch jobs available in SET-IFP (input file processing) Batch Job Set.

CMN_GL_POST_DT

This parameter is used to specify the General Ledger Post­ing date. If scheduler is enabled, it automatically updates this to current system date. Else Admin User would need to set this date manually to ensure correct posting dates in GL.

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.

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 men­tioned above.

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 cal­culations with interest. Currently two methods are sup­ported. Input parameter value is ‘US’ or ‘EU’ representing American and European method of interest accrual for 360 days.

CMN_TEST_TOOL_LOG­GING

This parameter is used to set testing tool logging parame­ter

CMN_SCHEMA_ID

This is used to specify the schema identifier for all users.

CMN_SCHEMA_NAME

This is used to specify the Oracle User Name for a specific schema. Input parameter value is user defined.

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.

CMN_SERVER_HOME

This parameter captures the Server Home Directory. Input parameter value is user defined.

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.

CMN_SER_ENVIRON­MENT_FILE

This parameter captures the environment file (and its path) for running the Operating System commands from Job Service. Input parameter value is user defined.

CMN_WALLET_PASS­WORD

This parameter is used to specify the common wallet pass­word. Input parameter value is user defined.

CMN_WALLET_PATH

This parameter is used to specify the common wallet path for oracle database. Input parameter value is user defined.

CPP_NO_OF_PROMISES

This parameter is used to define the maximum number of promises/chances allowed for a customer who is delin­quent and promises to pay. Input parameter value is numeric with no upper limit.

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.

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 pay­ments processing)

CRD_CHS_CUR_CODE

This parameter is used to specify the currency code of the transacting currency for CHASE interface. Input parameter value is user defined.

CRD_CHS_DIR_PATH

This parameter is used to specify the directory path for CHASE payment interface for Credit Cards. Input parame­ter value is user defined.

CRD_CHS_IND_TYPE

This is used to specify the industry type for CHASE pay­ment interface for Credit Cards. Input parameter value is user defined.

CRD_CHS_MER­CHANT_ID

This captures the merchant ID number for CHASE pay­ment interface for Credit Cards. Input parameter value is user defined.

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.

CRD_CHS_SEC_RE­MOTE_HOST_NAME

Similar to the previous parameter this captures the sec­ondary remote host name of CHASE interface for seeking approvals for credit card payments. Input parameter value is user defined.

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.

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 payments for credit cards etc. Input parameter value is user defined.

CRD_PTB_RE­MOTE_HOST_NAME

This is the Protobase Remote Host Name

CRD_PTB_RE­MOTE_HOST_PORT

This is the Protobase Remote Host Port

CRD_PTB_TIMEOUT

This is the Protobase Timeout Value

CRD_SOURCE_TYPE_CD

This is the Source Type Code

DDT_CREATE_DUE_­DATE_HISTORY

This parameter must be enabled to create a due date his­tory for any account. Due date history sub tab under Trans­action history displays the delinquency 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).

DECI­SION_BUY_RATE_TOL­ERANCE

This parameter is used to define the variance in buy rate

EDF_DIALER_ACCT_­TYPE

This parameter is used to set up the account number refer­ence for the dialer file to pick-up records for Auto dialer interface. Input parameter value is account number.

FLL_BPEL_PROCESS

This parameter is set to use BPEL process in OFSLL. Input parameter value is Boolean (Yes/No).

ICA_INPUT_FILE_FOR­MAT

This parameter is used to define the input call activity file format

IFD_DIRECTORY

This parameter is used to define the Oracle directory object name for IFD file location

IFD_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle directory object name for IFD file location

INCOM­ING_LOB_PURGE_DAYS

This parameter is used to define the incoming process file table purge days

INPUT_DIRECTORY

This parameter is used to define the Oracle directory object name for INPUT file location

ITU_DIRECTORY

This parameter is used to define the Oracle directory object name for ITU file location

ITU_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle directory object name for ITU file location

IVR_DIRECTORY

This parameter is used to define the Oracle directory object name for IVR file location

IVR_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle directory object name for IVR file location

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.

JSV_ARCHIVE_­SERVER_CONFIG

This parameter is used to set the configuration file for reports archive server. Input parameter value is user defined.

JSV_ARCHIVE_­SERVER_URL

This parameter is used to specify the archive server url. Input parameter value is user defined.

JSV_BI_PASSWORD

This parameter is used to define the BI Publisher Pass­word

JSV_BI_USER

This parameter is used to define the BI Publisher User ID

JSV_TEMPORARY_DI­RECTORY

This parameter is used to define Oracle directory object name for Job Service Temp file location

JSV_BI_PASSWORD­JSV_REPORTS_RUNT­IME

This parameter is to specify the reports runtime program. Input parameter value is user defined.

JSV_REPORTS_RUNT­IME_CMDFILE

This parameter is used to specify the reports runtime com­mand file. Input parameter value is user defined.

JSV_REPORTS_­SERVER_CONFIG

This parameter is used to specify the configuration file for reports server. Input parameter value is user defined.

JSV_REPORTS_­SERVER_URL

This is used to specify the URL for the reports server. Input parameter value is user defined.

JSV_REPORT_AR­CHIVE_DIRECTORY

This is used to specify the path and directory of Reports archive, input parameter value being numeric.

JSV_SMTP_SERVER

This parameter specifies the SMTP server used by job ser­vice for sending email messages. Input parameter value is user defined.

JSV_TIMEOUT

This is to specify the polling interval for the job service dur­ing time out. Input parameter value is numeric. To check whether it represents minutes/seconds.

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).

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).

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.

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.

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.

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.

LIEN_RELEASE_DAYS

This parameter is used to define the Lien Release Days

LOCKBOX_DIRECTORY

This parameter is used to define the Oracle directory object name for Lockbox file location

LOCKBOX_PRO­CESSED_DIRECTORY

This parameter is used to define the Oracle directory object name for processed Lockbox file location

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 let­ter is to be generated. Input parameter value is numeric.

LOG_LOB_PURGE_DAYS

This parameter is used to log files header table purge days

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.

MAX_VOID_TXN_AU­THORIZE_DAYS

This parameter is used to set the maximum days to author­ize transaction

OCP_CUSTOMER_P­MT_SITE_ID

This parameter is used to set the customer payment extract file site id

OCP_IN­CLUDE_ACH_ACC

This parameter is used to set the customer payment extract including ach accounts

OUTGO­ING_LOB_PURGE_DAYS

This parameter is used to define the outgoing process file table purge days

OUTPUT_DIRECTORY

This parameter is used to define Oracle directory object name for OUTPUT file location

PAC_ARCHIVE_DAYS

This parameter is used to define number of days for peri­odic archiving of account. Input parameter value is numeric.

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

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.

PAP_OARCHIVE_DAYS

This parameter is used to define the number of days for archiving applications from ‘O’ tables. Input parameter value is numeric.

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.

PDC_PRE_PROCESS_­DAYS

This parameter value will define the number of days prior to the due day, regular account PDC process should be ini­tiated. Input parameter value is numeric.

PENDING_PDC_DAYS

This parameter value will define the number of days before the initiation day for pending PDC accounts.

PGL_ARCHIVE_DAYS

This parameter defines the number of days, post which the transactions in GL would be archived. Input parameter value is numeric

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.

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.

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.

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.

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

PPR_ARCHIVE_DAYS

This is used to specify the days for archival of producers details on a regular basis. Input parameter value is numeric.

PPR_OARCHIVE_DAYS

This is used to specify the days after which the producers details from ‘O’ tables need to be archived. Input parame­ter value is numeric.

PPX_ARCHIVE_DAYS

This is used to specify the days after which producer trans­actions are to be archived. Input parameter value is numeric.

PPX_OARCHIVE_DAYS

This is used to specify the days after which the producer transactions are to be moved from ‘O’ tables. Input param­eter value is numeric.

PJR_COPY_PURGED_­DATA

This parameter is used to copy data into purge tables

PST_ARCHIVE_DAYS

This parameter specifies the number of days for which the statements are to be archived. Input parameter value is numeric.

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.

PTT_PURGE_DAYS

This is used to specify the number of days after which the PTT table is to be purged. Input parameter value is numeric.

PTX_ARCHIVE_DAYS

This parameter is used to specify the number of days the transactions are to be archived. Input parameter value is numeric.

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.

PUL_PURGE_DAYS

This parameter is used to specify the number of days post which the User login details are to be purged. Input param­eter value is numeric.

PVA_ARCHIVE_DAYS

This parameter stores the number of days for archival of regular vendor assignments. Input parameter value is numeric.

PUP_ARCHIVE_DAYS

This parameter stores the number of days for archival of transaction upload. Input parameter value is numeric

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

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.

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.

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.

RAC_LOAD_FREQUENCY

This parameter is used to specify Accounts RDH Load Fre­quency

RAP_LOAD_FREQUENCY

This parameter is used to specify Applications RDH Load Frequency

RAT_LOAD_FREQUENCY

This parameter is used to specify Asset Tracking RDH Load Frequency

RBK_LOAD_FREQUENCY

This parameter is used to specify Bankruptcy Details RDH Load Frequency

RCA_LOAD_FREQUENCY

This parameter is used to specify Call Activities RDH Load Frequency

RCH_LOAD_FRE­QUENCY

This parameter is used to specify Deficiency Details RDH Load Frequency

RCO_LOAD_FRE­QUENCY

This parameter is used to specify Contracts RDH Load Frequency

RFO_LOAD_FREQUENCY

This parameter is used to specify Repo-Foreclosure RDH Load Frequency

RPR_LOAD_FREQUENCY

This parameter is used to specify Producers Rdh Load Frequency

RST_LOAD_FREQUENCY

This parameter is used to specify Setup Data RDH Load Frequency

RTX_LOAD_FREQUENCY

This parameter is used to specify Txns RDH Load Fre­quency

SALESAGENT_­MAIL_SEND_IND

This parameter is used to specify whether decision fax needs to be sent to sales agent (yes/no)

SCORING_PARAME­TER_ALERT

This parameter is used to set the scoring parameter alert

SQL_DIRECTORY

This parameter is used to set the Oracle directory object name for SQL file location

TES_ANA_PRE_PROCESS_CYCLES

This parameter is used to specify the pre-process cycles required for Escrow analysis. Input parameter value is numeric.

TES_DSB_ANALY­SIS_PERCENT

This parameter is used to specify the percentage for escrow disbursements. Input parameter value is numeric.

TES_DS­B_PRE_PROCESS_DAYS

This is used to specify the number of days for pre-process for escrow disbursements. Input parameter value is numeric.

TPE_AMORTIZE_AC­CRUED_INT_ONLY

This parameter is used to specify that system has to amor­tize accrued interest at month end

TPE_APPLY_LTC_­FROM_CURR_DUE_DT

This parameter is used for pyramid law fee method to apply late charge from current due date

TPE_ESC_ANALY­SIS_DELQ_AMT

Parameter considers billed but uncollected amount for escrow analysis

TPE_EXCESS_PAY­MENT_TO_MEMO

Excess payment on the account will be moved to memo payment.

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).

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

TPE_FUTURE_PAYOFF_­DAYS

The value specified in this parameter validates the ‘Valid Up to Date’ with ‘Payoff quote’ during monetary transac­tions posting.

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.

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.

TPE_MIN_1098_INT_AMT_PAID

This parameter is used to specify the lower limit or mini­mum interest amount paid for 1098 i.e. Mortgage Interest Statement. In the US, FIs need to report mortgage interest of $600 or more received from individuals, during the course of their business. Input parameter value is 600, the minimum value above which reporting by FI is required in form 1098 for each mortgage account.

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).

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.

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).

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.

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.

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)

TPE_SCHGOFF_RE­VIEW_DAYS

This parameter is used to define the number of days allowed for review of SCHGOFF accounts. Input parame­ter value is numeric.

TPE_SCRA_DEFAULT_IN­TEREST_RATE

This parameter is used to define the default interest 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 parame­ter. Input parameter value is numeric (in this case 6, which is interest rate to be applied for SCRA accounts.

TPE_SHOW_BACK­DATE_WARNING

This parameter is used to define whether a warning mes­sage is to be shown if monetary transaction is backdated

TPE_ST­M_INC_ALL_TXNS

This parameter is enabled to define whether all transac­tions should be included in the statements or otherwise. Input parameter value is Boolean (Yes/No).

TPE_STOP_COMP_DELQ_DAYS

This parameter is used to stop computation when delq days > 60

TPE_TXN_POST_DE­FAULT_GLDATE

This parameter is used to default GL date in date type parameters during txn posting (y/n)

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.

UIX_DEFAULT_IMAGE_­PATH

This parameter is used to define the default image direc­tory maintained for the purpose of online attachment of document images to an application using documents main­tenance section under Account documentation. Input parameter value is user defined.

UIX_DIRECT_LOAN_­COMBO_ULN_UFN

This parameter when set to yes allows underwriting and funding to be carried on by a single responsibility for direct loans only. Input parameter value is Boolean (Yes/No).

UIX_INCOMING_FILE_­PATH

This parameter is used to specify incoming file path of app server

UIX_LOCAL_COUN­TRY_CD

Through this parameter we can set the local country where an FI has multiple branches across different geographies. Input parameter value is user defined.

UIX_LOCK_UN­LOCK_AND_COPY

This parameter is used to enable the user interface lock / unlock and copy features. Input parameter value is Boolean (Yes/No).

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.

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.

UIX_OUTGOING_FILE_­PATH

This parameter is used to specify outgoing file path of app server

UIX_REPORTS_­SERVER_CONFIG

This parameter can be used to specify the user interface reports server configuration file. This is not required for OFSLL.

UIX_REPORTS_­SERVER_URL

This parameter sets the URL for Reports server. Input parameter value is user defined.

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.

UIX_UTILITIES_SERV­LET_URL

This parameter can be used to specify the User Interface utilities servlets URL. This is not required for OFSLL.

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.

VEV_NADA_TOKEN_URL

This parameter is used to set the token URL for vehicle evaluation interface NADA. Input parameter value is user defined.

VEV_NADA_UPDATE_­DAY

This parameter is used to specify the day of the month to update the vehicle evaluations every month. Input parame­ter value is numeric.

VEV_NADA_URL

This parameter is used to set the URL for vehicle evalua­tion interface NADA. Input parameter value is user defined.

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.

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.

VEV_VALUATION_RE­GION

This parameter is used to define the default region for vehi­cle evaluation. Input parameter value is the region name, and is user defined.

VEV_VALUATION_­SOURCE_CD

This parameter is used to specify the default vehicle evalu­ation source code. Input parameter value is user defined. A number of parameters are possible 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

WFP_DIRECTORY

This parameter is used to specify the Oracle directory object name for WFP file location

WFP_MAX_CY­CLES_BACKDT

This parameter is used to specify the back dated cycles date for WFP.

WFP_PROCESSED_DI­RECTORY

This parameter is used to define oracle directory object name for wfp file location.

WFP_REVERSE_TX­N_IND

This parameter is enabled to define the WFP reversal indi­cator. Input parameter value is Boolean (Yes/No).

XAE_DEALUPD_MAX_AL­LOWED_DAYS

This parameter is used to define the max allowed days for Deal Update

XAE_DEALUPD_AL­LOWED_IND

This parameter is used to indicate whether deal update is allowed or not

OUTBOUND_CALL_Q

This parameter is used to generate reports (including emailing statements/letters) using Application Server instead of Database server.

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

IPR_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle directory object name for processed IPR file location

IPR_DIRECTORY

This parameter is used to define the Oracle directory object name for IPR file location

UIX_PWD_MGMT_EX­TERNAL_URL

This parameter is used to set external password manage­ment url, if applicable

UIX_PWD_MGMT_EX­TERNAL

This parameter is used to define the parameter if password management is external. (SET Y IF PASSWORD MAN­AGEMENT IS EXTERNAL (Y/N)).

ICU_PROCESSED_DI­RECTORY

This parameter is used to define the Oracle directory object name for processed ICU file location

ICU_DIRECTORY

This parameter is used to define the Oracle directory object name for ICU file location

UIX_BILL_CYCLE_AL­LOWED_IND

This parameter is used to indicate whether Billing cycle is allowed at the application level

CMN_EOD_SLEEP_MINS

This parameter is used to set in minutes the EOD sleep time

CMN_CORE_BANK_TX­N_CD

This parameter is used to set code for OFSLL and Core Banking integration

UIX_DIRECT_DISB_MAN­UAL_SELECT

This parameter will allow manual selection of disbursement mode for direct loans

ICC_DLQ_AMT_EX­CLUDED

This parameter enabling will exclude delinquency amount for CASA account

CMN_CORE_BANK_IND

This parameter is used to set whether OFSLL can inte­grate with Core Banking.

BKRP_FILE_REC_LIMIT

This parameter is used to set the limit of total number 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, multi­ple ‘Input Data Files’ are to be created.

UVN_VEN_NBR_SYS­_GENERATED

This parameter is used to validate if ‘Vendor Number’ has to be auto generated (if set to Y) or to be specified manu­ally in the Vendor details screen.

METRO_WITHOUT_COL­L_IND

This parameter indicates whether Metro II reporting is han­dled 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 Col­lateral status is tracked with the repossession details updated in 'Repo/Foreclosure' screen of Collections mod­ule.

METROII_­FIRST_DELQ_DT_ADD_­DAY

This parameter is used to calculate the first delinquency date that needs to be reported in the Metro II reporting file.

By default the parameter is 'disabled' indicating that the ini­tial delinquency date calculated by the system is used for Metro II reporting. The same needs to be enabled to add the parametrized number of days to the system calculated first delinquency date for the Metro II reporting purpose.

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.

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’, system only indicates that there are multiple records/rows in response file.

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.

TPE_PMT_POSTING_­CLS_ACCOUNT

This parameter is used to define the payment posting crite­ria 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 Payment Entry screen or ‘Pay­ment Upload’ file are posted to a ‘Suspense’ account.

TPE_BACKDT_P­MT_POSTING

This parameter is used to define the payment posting crite­ria for backdated payments for the following 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.

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.

PMT_BATCH_POSTING

This parameter (PAYMENT BATCH POSTING PREFER­ENCE) is used to define the status of payment transactions which are uploaded in bulk through a batch process.

POOL_ACTIVE_AC­COUNTS_ONLY

This parameter controls the type of accounts that can be added to a Securitization Pool and allows adding only ‘Active’ status accounts since the same is enabled (value set to ‘Y’) by default. To add accounts with other status such as Active, Paid Off, Charged Off, Void, Terminate. and so on, set the value of system parameter to ‘N’.

AUTO_GEN_ACC_NBR_­CONV

This parameter is used for conversion accounts to decide option of account number generation. If the value of parameter is set to ‘Y’ the account number is automatically generated in OFSLL during conversion and if the value is ‘N’, then external reference number (generated in third party system) itself is appended as the account number.

OUTBOUND_DL­R_TRACK_Q

This parameter defines the settings for batch job ‘SET_XPR’ to either use MDB (Message Driven Bean) flow (if value set to ‘Y’) or existing work flow (if value set to ‘N’) to dump producer details maintained in the system into Dealer Track.

MDB flow generates outbound JMS message though the configured MDB interface and can avoid current database outbound calls and session timeout.

In the existing workflow, the database makes synchronous outbound calls to producer data dump web service, to dump the data and acknowledge the database with the sta­tus (success or failure).

OUTBOUND_ROUTE­ONE_Q

This parameter defines the settings for batch job ‘SET_XPR’ to either use MDB (Message Driven Bean) flow (if value set to ‘Y’) or existing work flow (if value set to ‘N’) to dump producer details maintained in the system into ROUTEONE.

MDB flow generates outbound JMS message though the configured MDB interface and can avoid current database outbound calls and session timeout.

In the existing workflow, the database makes synchronous outbound calls to producer data dump web service, to dump the data and acknowledge the database with the sta­tus (success or failure).

GRI_WEBSER­VICE_LOG_IND

This parameter is used to decide on logging GRI (Generic Recovery Interface) communications. If enabled, system logs all the GRI related web service communications between OFSLL and external interfaced system.

The recorded logs can be viewed in Dashboard > System Monitor > Database Server Log Files tab by selecting ‘Interfaces’ view option.

PVE_ARCHIVE_DAYS

This parameter stores the number of days for archival of regular vendors. Input parameter value is numeric.

PVE_OARCHIVE_DAYS

This parameter is used to specify the number of days post which the regular vendors are to be moved from ‘O’ tables to ‘OO’ tables. Input parameter value is numeric.

LBX_DR_CR_VALI­DATE_AMT_IND

This parameter (VALIDATE LOCKBOX DR/CR BATCH TOTALS) is used to facilitate NACHA file validation. Based on the status of the parameter, system is either allowed to validate the file or process without validation.

PAP_PURGE_DAYS

This parameter allows to define the number of days after which the application 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.

PAC_PURGE_DAYS

This parameter allows to define the number of days after which the accounts 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.

CMN_SED_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing seed data is to be processed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

CMN_EDF_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing data from Dialer Interface is to be processed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

The same is used by the batch jobs EDFADR_BJ_100_01 and EDFIVR_BJ_100_01 which are available in SET-EDF Batch Job Set.

CMN_FAX_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing Fax data is to be processed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

CMN_RED_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the outgoing details of Data Masking Policy (i.e. Redaction policy output file) is to be processed. If set to ‘Y’, system processes the data from LOB and if set to ‘N’, system pro­cesses the data from FILE.

The same is used by the batch job REDPRC_BJ_100_01 available in SET-RED Batch Job Set.

CMN_WFP_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing WFP Unit details are to be pro­cessed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

The same is used by the batch job WUPPRC_BJ_132_01 available in SET-WFP Batch Job Set.

CMN_AUD_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the outgoing Audit scripts are to be processed. If set to ‘Y’, system processes the data from LOB and if set to ‘N’, sys­tem processes the data from FILE.

CMN_LBT_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the incoming or outgoing Lockbox files are to be pro­cessed. If set to ‘Y’, system processes the data to/from LOB and if set to ‘N’, system processes the data to/from FILE.

The same is used by the batch jobs LBXPRC_BJ_100_01 and LBXSEP_BJ_100_01 available in SET-LBT Batch Job Set.

CMN_ODD_­FILE_PROCESS_TO_LOB

This parameter allows to define the location from where the outgoing ODD or Output Data Dump files are to be pro­cessed. If set to ‘Y’, system processes the data from LOB and if set to ‘N’, system processes the data from FILE.

The same is used by the batch job ODDPRC_BJ_000_01 available in SET-ODD3 Batch Job Set.

CMN_ALERT_DE­BUG_METHOD

This parameter allows to define the location to which Alert and Warning logs are to be written. If set to ‘ADVANCE_­QUEUE’, system writes the logs in Logs table and if set to ‘UTL_FILE’, system generates the alert log file.

CMN_GRI_WS_DE­BUG_METHOD

This parameter allows to define the location to which GRI (Generic Recovery Interface) web service logs are to be written. If set to ‘ADVANCE_QUEUE’, system writes the logs in Logs table and if set to ‘UTL_FILE’, system gener­ates the log file.

UIX_CUSTOM­ER_BASED_PMT_IND

If this parameter is set to ‘Y’ and is ‘Enabled’, system accepts posting direct payment to an account and also accepts customer based payments to all linked accounts.

To facilitate customer based payments, ‘Customer/Busi­ness #’ and ‘Payment Hierarchy’ fields along with ‘Popu­late Accounts’ button are enabled in ‘Payment Entry’ screen to specify required values.

PMT_HIERARCHY_CODE

In this parameter, you can specify a payment hierarchy which is populated by default in Customer Details and Business Details (if applicable) screen after account acti­vation.

However, the specified value is selected by default only if there is a matching hierarchy definition enabled record maintained in Setup > Administration > User > Payment Hierarchy screen. Else, ‘Equal Amount’ value is selected which in-turn adjusts the payment equally to all customer/business linked accounts.

Note: System does not consider this parameter value while ‘creating account using existing customer/business details’ since the default selection is done during the crea­tion of existing customer / business account.

EVI_MAX_RE­TRY_COUNT

This parameter, records and controls the maximum attempts to re-trigger FAILED Webhook requests which cannot exceed more than 5 times. However, this parame­ter can be modified if the maximum re-trigger attempts is to be less than 5 times.

UIX_CUSTOM_LA­BEL_ENABLED_IND

This parameter indicates if the field label customizations are allowed i.e. ability to change label and provide access to fields in Label Configuration and Security User Access Definition Details screens.

If set to ‘Y’, system refers data from database

If set to ‘N’, system refers data from XLIB file.

UIX_MASTER_AC­C_BASED_PMT_IND

If this parameter is set to ‘Y’ and is ‘Enabled’, system accepts posting direct payment to a master account and also accepts master account based payments to all linked accounts.

To facilitate master account based payments, ‘Master Account #’ field is enabled in ‘Payment Entry’ screen.

TPE_PMT_RE­FUND_CURRENCY_S­RC_CD

This parameter indicates the currency in which payment refund has to be processed in the system as either ‘Pay­ment Currency’ or ‘Account Currency’. The same is consid­ered during payment refund operation in Payment Maintenance screen.

AUTO_GEN_ACTIVE_TX­N_CONV

This parameter if enabled, auto posts a dummy ACTIVE transaction on all ‘migrated accounts’ during the schedule batch job run. This in-turn allows to post RESCISSION / VOID transaction specifically for migrated accounts by selecting the dummy transaction from Customer Service > Maintenance screen or Transaction History transactions tab,

For more information, refer ‘Voiding an Account’ section Servicing user guides.

FLL_CMN_JET_JWT_EN­ABLED_IND

(JET JWT TOKEN ENA­BLE INDICATOR )

This parameter if set to ‘Y’, enables the ‘Account Dash­board’ screen in Servicing LHS menu. This screen is based on Oracle JET framework and facilitates to view Account summary details maintained in the system. For information on screen functionality, refer to Servicing User Manuals and for details on deployment and configuration, refer to Installation Manuals.

FLL_CMN_JET_JWT_TO­KEN_URL

(JET JWT TOKEN GENER­ATION URL )

Define the value of the O-JET URL (app-shell application URL) in the format https://<hostname>:<port no>/ofsll-app-shell/<token>

FLL_SER_JET_AC­C_CREATE_URL

(JET SIMPLE ACCOUNT CREATE URL)

Define the value of the O-JET URL (app-shell application URL) in the format https://<hostname>:<port no>/ofsll-app-shell?root=accountonboarding

FLL_SER_JET_ACC_­DASHBOARD_URL

(JET ACCOUNT DASH­BOARD URL)

Define the value of the O-JET URL (app-shell application URL) in the format https://<hostname>:<port no>/ofsll-app-shell?root=accountdetailsdashboard

FLL_SET_JET_INTELLI­GENTSEG_URL

(JET INTELLIGENT SEG­MENTATION URL)

Define the value of the O-JET URL (app-shell application URL) in the format https://<hostname>:<port no>/ofsll-app-shell?root=queuecreation

ACCOUNT_PROCESS­ING_THRESHOLD

(ACCOUNT ON-BOARD­ING ASYNCHRONOUS PROCESSING THRESH­OLD)

This parameter allows to restrict the number of accounts that can be created ‘synchronously’ using Account on-boarding WebService.

However, creating accounts asynchronously in the system is further processed by the below batch jobs based on val­ued defined in this parameter.

SET-API2 (ASYNCHRONOUS ACCOUNT CREATION)

-- ACXVAL_BJ_100_01 (VALIDATE IAPP TABS)

-- ACXAAI_BJ_100_01 (ASYNCHRONOUS ACCOUNT CREATION)

VTX_OUTBOUND_URL (OUTBOUND CALL URL FOR VERTEX)

This parameter defines the URL of the external adapter (Vertex) that is used to integrate with OFSLL.

VTX_VERSION (VERTEX VERSION)

This parameter defines the version of Vertex adapter that is required to be configured by the system.

AUTO_GEN_AGREE­MENT_NBR (AUTO GEN­ERATE AGREEMENT NUMBER FOR ACCOUNT ONBOARDING)

This parameter defines the mode by which agreement number is generated to an account. If set to ‘Y’, system generates the agreement number. If set to ‘N’, system accepts the external agreement number provided in Account on-boarding payload.

Note: When system parameter is set to ‘Y’, the agreement number is also used as an identifier to validate the contract details and decide on which accounts should get same Agreement number.

C.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.

Parameter

Description

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 specify the limit.

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 con­dition as the selected account and bear the same cus­tomer ID. The pre-requisite for this is Group Follow-up indicator should be enabled in queue setup. Input value is numeric.

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).

UIX_AP­P_VIEW_ALL_APPS

The system uses this parameter to determine which users have the ability to view all applications. The system selects the best match based on a hierarchical sort by Organiza­tion, Division and Responsibility fields, with values of ‘ALL’ being a lower order match than an exact match. Input parameter value is Boolean (Yes/No).

UIX_HIDE_RESTRICT­ED_DATA

This is used to hide sensitive data relating to the Contract / Applicant to a specific group/responsibility 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)

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.

UIX_VIEW_SE­CURED_ACCOUNTS

This is used to specify whether an account can be viewed by a specific responsibility (users). Parameter value is Boolean (Yes/No) and when flagged as Yes, such accounts would be viewable only by users defined in the Organization, Division hierarchy with the specified respon­sibilities. For example, all employee accounts may not be viewable by all users and should be made available only to the HR department with specific responsibility levels.
Note: While creating application, selecting appropriate applicant’s classification would be essential for this param­eter to be effective.

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 viewable only by users defined in the Organization, Division hierarchy with the specified responsibilities. For example, 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 appropriate applicant’s classification would be essential for this param­eter to be effective.

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.

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

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.

ULG_INACTIVITY_DAYS_­MAX

This parameter is used to specify the maximum number of days the User ID can be without utilization 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.

ULG_PWD_CASE_SENSI­TIVE_REQ

This is used to allow all passwords to be case sensitive 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_PWD_LOWER_CHAR_REQ parameter should also be set to N.

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.

ULG_PWD_CHANGE_­DAYS_PROMPT

This is used to set the maximum number of days after which system will prompt the User for password change, in cases where password has not been changed within the set period. Input parameter value is numeric.

ULG_PWD_LENGTH_MIN

This is used to set the minimum length of password string that is required. If this criterion is not met, system would throw an alert specifying minimum character length required to be input.

ULG_PWD_LOW­ER_CHAR_REQ

This is used to allow at least one lower case character in password strings. Input value is Boolean (Yes/No). Setting this as ‘NO’ would mean passwords would be allowed in uppercase only.

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.

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.

ULG_PWD_UP­PER_CHAR_REQ

This is used to allow at least one upper case character in password strings. Input value is Boolean (Yes/No). Setting this as ‘NO’ would mean passwords would be allowed in lowercase only.

ULG_WEEK_END

This parameter enables to set the last day of the week when a user can have access to the system. Input parame­ter 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.

ULG_WEEK_START

This parameter is used to set the start day of the week when a user is allowed to access the system. Input param­eter value is numeric.

CRB_ERROR_VALIDA­TION_IND

This parameter is used to validate the Credit Bureau report generation request depending on the number of days per­mitted 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 per­mitted days (as defined in parameter DAYS_TO_PULL_CRB_REPORT), system displays 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 num­ber(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.

OCP_CUST_PMT_PREF

This parameter MASTER ACCOUNT ROLLUP FOR PMT EXTRACT FILE is used to decide the basis of dues consol­idation at master account level based on the parameter values selected. For more information, refer to ‘Outbound Customer Extracts To Payment Agencies Batch’ section.

C.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).

Parameter

Description

AUD_ADV_REASON_­MODEL

This parameter is used to set-up default adverse action reasons for scoring models during set-up in the Parame­ters sub page. Whenever the flag ‘Bureau Score Reasons’ is unchecked during credit bureau scoring model set-up, then automatically rejected applications scored using this scoring model picks up the Adverse Action Reasons from the Parameters sub page.

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 applica­ble parameters specified. Other parameter input values are Minimum Score, Maximum Score, Minimum Tier (Grade), Maximum Tier (Grade).

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 Max­imum Score and Minimum Score. If Maximum score is set-up in company parameters, then for all applications where a bureau report is pulled, the system will pick-up the Maxi­mum score from the different bureaus.

CBU_DATA_SET_SIZE

Parameter to define the metro 2 file data selection criteria, option values are monthly, Daily, weekly, semi monthly.

CBU_FILE_FORMAT

Metro 2 file format definition, user need to select from the parameter value drop down.

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).

CMN_CMB_DE­FAULT_PRINTER

This is used to define the default printer for printing. 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’.

CMN_WEEKLY_NONBUSI­NESS_DAYS

This parameter is used to set-up the weekly holidays at the company level. The input parameter value is character string; if no details specified and parameter is enabled, system would display ‘UNDEFINED’.

COR_STORAGE_DIREC­TORY

This parameter is used to specify the path/location for Oracle directory object template for correspondence docu­ments. Input parameter value is ‘SETME’; if none is speci­fied and parameter enabled, ‘UNDEFINED’.

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 parame­ter value is Boolean (Yes/No).

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 parame­ter value is Boolean (Yes/No).

DDP_CRB_EXPIRATION_­DAYS

This parameter is used to define the credit bureau report expiration days. So if this is set as 30, system will use all available credit bureau reports pulled which are not older than 30 days from current day, during de-dupe. Input value is numeric with no upper limit.

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-duping Primary applicant’s lia­bilities. Input parameter value is Boolean (Yes/No).

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 applicant’s liabilities. Input parameter value is Boolean (Yes/No).

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’.

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.

ECB_USE_APL_CUR­RENT_SCORE_CRH

This parameter is used to define whether the system should run the credit bureau edits only on the current scored applicant bureau. Input parameter value is Boolean (Yes/No).

LOR_AUTOMATIC_CON_­FUND_FAX

This is used to define the decision fax generation when an application is funded. The input parameter 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.

LOG_STORAGE_DIREC­TORY

This parameter is used to define the Oracle storage direc­tory. Input parameter value is user (System Administrator) defined.

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 generates the fax approval in the pre-defined template whenever an application is approved.

LOR_AUTOMATIC_RE­JECTION_FAX

This is used to define the decision fax generation when an application is rejected. The input parameter 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.

MAX_LEAD_DAY_AGE

This parameter is used to define the maximum no. of days, post which the sales lead would be considered cold. Input parameter value is numeric with no upper limit.

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.

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.

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.

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.

MULTI_OFFER_PMT_TOL­ERANCE

For Multi offer variance in payment is defined in this parameter.

MULTI_OFFER_TERM_­VAR

For multi offer Term variance will be defined in the param­eter.

PRESENT_VALUE_COM­PUTE_RATE

This parameter will perform Present Value Computation Rate (Inflation/Discounting Rate).

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 generate rate change let­ters in order to provide advance intimation to customers. Input parameter value is numeric with no upper limit.

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.

UIX_RUN_AAI_ACT

This parameter is used by the system to determine whether to create and activate an account online. Input parameter value is Boolean (Yes/No).

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.

UIX_UCS_CAC_MAX­_PROMISE_DAYS

This parameter is used to set up the maximum number of days allowed for customers who promise to pay when fol­lowing up for delinquent accounts. Input parameter value is numeric.

AUD_QUEUE_INI­TIAL_CRB_FAILED

This parameter enabling will Queue the application if any bureau failed.

UIX_UCS_CUA_MAX_­FOLLOWUP_DAYS

This parameter will allow the user to maintain the Collec­tions maximum follow-up days that are allowed in the sys­tem.

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’.

CMN_SYSTEM_UNDER_­MAINTENANCE

This parameter specifies whether the system is under maintenance or not. Input parameter value is Boolean (Yes/No).

CMN_GL_POST_DT

This parameter is used to define the GL Post Date of Company in MM/DD/YYYY format. The same is also updated by Scheduler if ENABLED.

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.

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.

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 format.

CMN_PROMISE_FU­TURE_MTHD

This parameter helps to define the future promise handling method in the system.

When multiple ‘Promise to Pay’ records are defined on an account and if any one of the promise is not satisfied i.e. if there is no credit / Payment transaction of the correspond­ing amount on the promise date, then system uses any of the following method defined in this parameter to update the future promises.

- No Action on future promises (default)

- Mark current and future promises as broken

- Mark current as broken but future promise as cancelled

C.5 Other Parameters

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

Parameter

Description

CRB_MAX_BU­REAU_PULL

This parameter is used to determine the number of credit reports automatically per applicant. Input parameter value is numeric.

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).

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.

JOINT_DE­DUP_SPOUSE_LIABILI­TIES

This parameter is used to determine duplicate liabilities in the Spouse’s liabilities in de-duping logic. Input parameter value is Boolean (Yes/No).

JOINT_DEDUP_ALLAP­L_LIABILITIES

This parameter is used to determine duplicate liabilities of all applicants’ liabilities in de-duping logic, irrespective of whether they are related to each other. Input parameter value is Boolean (Yes/No).

ASC_COL_SER_ENA­BLED_IND

This parameter is used for enabling the Collection Servic­ing Indicator. Input parameter value is Boolean (Y/N).

CMN_TEST_TOOL_LOG­GING

This parameter is used to set the testing tool logging to enable or disable testing tool log in. Input parameter value is Boolean (Yes/No).

ICA_INPUT_FILE_FOR­MAT

This parameter is used to specify the Input format for call activity file. Two Parameter values are possible – US for­mat and OFSLL format.

JSV_BI_USER

This parameter is used to define the BI publisher User ID. Input parameter value is user defined (Admin user).

JSV_BI_PASSWORD

This parameter is used to define the BI publisher User password. Input parameter value is user defined (Admin user).

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).

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.

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.

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).

TPE_EXCESS_PAY­MENT_TO_MEMO

This parameter will make excess payment to the memo payment by marking this Parameter as YES.

TPE_STOP_COMP_DELQ_DAYS

This parameter is enabled to stop computation if the account is delinquent for more than 60 days.