Duplicate Detect Configuration File

Transcription

1 Duplicate Detect Configuration File Overview... A-171 Making a Backup Copy of the DupDetect.INI File... A-172 Configuring Variables in the Configuration File... A-173 Setting the Duplicate Detection Variables in the [GLOBAL] Section... A-173 Saving Changes and Re-Initializing the Duplicate Detect Background Task... A-176 Sample DupDetect.INI Configuration File... A-177

2

3 Duplicate Detect Configuration File Overview The Duplicate Detect Configuration file (DupDetect.ini) defines the settings used by the system when processing work through the Duplicate Detection Module. The Duplicate Detect Configuration file allows you to define the following: Whether to utilize a global Duplicate Detect Database or a separate database for each application system (i.e., Test, Training, Production) * Number of days batches are stored in the duplicate detect database Types of items to evaluate (i.e., payments, remittances, or all) MICR fields (Aux, Tran Code, EPC) to evaluate in addition to the Routing and Transit and Account fields Whether to evaluate the Applied Amount field Whether to automatically store all the valid (non-duplicate) items in the duplicate detect database ** Whether to reject duplicate items *** Whether to reject an entire transaction containing a duplicate item Whether to enable system debug mode messages for batches, transactions, items, payments, remittances and rejects NOTE: A sample Duplicate Detect Configuration file is included in this document, beginning on page A-177. Before modifying the Duplicate Detect Configuration file, you must do the following: CRITICAL STEP: Stop the Duplicate Detect background task NOTE: For instructions on stopping a background task, see the document Background Tasks in the Background Tasks section of the RemitTrac Workflow Manual. Make a backup copy of the existing DupDetect.ini configuration file * Current version of the system requires use of separate databases. ** Current version of the system automatically stores all valid items in the duplicate detect database. *** Current version of the system automatically rejects all duplicate items. Appendix A: Configuration Files Duplicate Detect (rev. 4/30/2009) A-171

4 Once modifications have been made to the configuration file, you must do the following: Save changes made to the DupDetect.ini configuration file Initialize the Duplicate Detect background task NOTE: For instructions on initializing a background task, see the document Background Tasks in the Background Tasks section of the RemitTrac Workflow Manual. Making a Backup Copy of the DupDetect.INI File Before you make changes to the Duplicate Detect Configuration file, you should make a copy of the existing DupDetect.ini file. NOTE: The Duplicate Detect Configuration file is stored in the Remitrac\SitNNNNN directory on the Database Server, where NNNNN represents your Site ID number You may require Administrator security rights to backup the configuration file. Contact your Network Administrator if you require assistance with security access issues. To copy the Duplicate Detect Configuration file 1. Open Windows Explorer. 2. Double-click on Network Neighborhood (My Network Places). 3. Double-click on Entire Network. 4. Double-click on Microsoft Windows Network. 5. Double-click on the RemitTrac workgroup. 6. Double-click on the Database Server. 7. Double-click on the folder containing the Remitrac\SitNNNNN directory (usually on Disk D). 8. Double-click on the Remitrac directory folder. 9. Double-click on the SitNNNNN directory folder. 10. Right-click on the filename DupDetect.ini. 11. Choose Copy. 12. Right-click inside the window, and then choose Paste. A copy of the DupDetect.ini file is placed in the SitNNNNN directory and is named Copy of DupDetect.ini. A-172 RemitTrac Setup Manual

5 Configuring Variables in the Configuration File Before you can modify the Duplicate Detect Configuration file, you must open it in an editor such as the Notepad program. NOTE: The Duplicate Detect Configuration file is stored in the Remitrac\SitNNNNN directory (where NNNNN represents your Site ID number) on the Database Server. You may require Administrator access rights to open and modify settings within the configuration file. Contact your Network Administrator if you require assistance with security access issues. To open the Duplicate Detect Configuration file 1. If you are not in the Remitrac\ SitNNNNN directory, follow Steps 1 through Step 9 under Making a Backup Copy of the Printers.ini file on page A-172. Otherwise, skip to Step Double-click the filename DupDetect.ini to open the file in Notepad. Setting the Duplicate Detection Variables in the [GLOBAL] Section The Duplicate Detect Configuration file contains one section of variables used for Duplicate Detection processing. Table 1 summarizes the variables that you can set in the [GLOBAL] section. Table 1. Variables in the [GLOBAL] Section Variable Description Values / Example UseGlobal* Set to Yes to utilize one duplicate Yes or No detect database across processing systems (i.e., test, training, UseGlobal = No production). Set to No if each processing system uses its own duplicate detect database. * Current version of the system automatically sets the variable to No. Appendix A: Configuration Files Duplicate Detect (rev. 4/30/2009) A-173

6 Table 1. Variables in the [GLOBAL] Section (continued) Variable Description Values / Example DaysOnline Defines the number of days of data to store in the Duplicate Detect Database. Any value between 0 and 366 The Site End-of-Day process uses this value to determine when to remove Daysonline = 31 batches from the Duplicate Detect Database. When batches in the NOTE: When the database are older than the number of value is set to 0, days defined (from the current process only the batches for date), the Site End-of-Day process will the current process remove those batches from the day are stored in the Duplicate Detect Database. duplicate detect NOTE: For values of 1 and greater, database. Duplicate Detection will slow down the Site End-of-Day process. DetectMode Defines the types of items that the Duplicate Detection process evaluates. AutoFill** Controls whether the Duplicate Detect process will automatically store valid (non-duplicate) items in the Duplicate Detect Database. ItemReject*** Determines whether the Duplicate Detect process marks a duplicate item as rejected. TranReject Determines whether the Duplicate Detect process marks the transaction and all the other items in the transaction containing the duplicate item as rejected. Payment, Remit or All Detectmode = All Yes or No AutoFill = Yes Yes or No ItemReject = Yes Yes or No TranReject = Yes ** Current version of the system automatically stores all valid items in the duplicate detect database. Variable cannot be set to No. *** Current version of the system automatically rejects all duplicate items. Variable cannot be set to No. A-174 RemitTrac Setup Manual

7 Table 1. Variables in the [GLOBAL] Section (continued) Variable Description Values / Example AmountTest Set to Yes to perform the Yes or No Duplicate Detection process after item processing and just prior to AmountTest = Yes Final Balance. In addition to performing a MICR or Scanline match, the Applied Amount of the item is also evaluated and must match to mark an item as a duplicate. If set to Yes, and a duplicate item is found, the transaction and all the other items in the transaction containing the duplicate item are automatically rejected, regardless of the value defined in the TranReject variable. MICRTest = F1 F2 F3 Set to No to perform the Duplicate Detection process after all the items in the batch have completed MICR, Foreign and Scanline Field Repair. The Applied Amount is not part of the evaluation. Defines up to three additional MICR fields to evaluate during the Duplicate Detection process. As a default, the Routing and Transit Number and Account fields are evaluated. The three additional fields are: F1: Aux field F2 EPC field F3: Trancode field NOTE: It is recommended that at least the Aux (F1) and Trancode (F3) fields are defined. Yes or No MICRTest = Yes Yes Yes Appendix A: Configuration Files Duplicate Detect (rev. 4/30/2009) A-175

8 Table 1. Variables in the [GLOBAL] Section (continued) Variable Description Values / Example DebugMode = Defines the fields for which debug Yes or No F1 F2 F3 F4 messages are output to the Event F5 F6 F7 F8 Logger during Duplicate Detection DebugMode = processing. Debug information can Yes Yes Yes Yes be used as a troubleshooting tool by Yes Yes No No ImageScan. The fields are as follows: F1: Batch F2: Transactions F3: Items F4: Payments F5: Remittances F6: Rejects F7: Field Not Used F8: Field Not Used Saving Changes and Re-Initializing the Duplicate Detect Background Task In order for the Duplicate Detection Module to utilize the new Duplicate Detect Configuration settings, you must save the changes made to the configuration file and re-initialize the Duplicate Detect background task. To save changes to the Duplicate Detect Configuration file 1. From Notepad or another text editor, select File Save to save changes made to the Printers.ini file. 2. Select File Exit. The DupDetect.ini file is closed and Windows Explorer is displayed on the screen. 3. Re-initialize the Duplicate Detect background task. The Duplicate Detection process is re-initialized using the new configuration settings. NOTE: For instructions on initializing a background task, see the document Background Tasks in the Background Tasks section of the RemitTrac Workflow Manual. A-176 RemitTrac Setup Manual

9 Sample DupDetect.INI Configuration File The contents are a series of Windows INI file sections. These sections are used to control different aspects of the software. As of RemitTrac V g, the only section that is functional is the Global Section, thus, at this time, only that section will be described below. The other sections in the file will be documented when they become active. Example Duplicate Detect INI File- Global Section ; ; This is the Duplicate Detect Module Configuration file ; ; This file lives in the site directory and is read by all the modules that ; are required to perform Duplicate Detection and Resolution. [Global] USEGLOBAL = NO ; Indicates to NOT use the system wide Duplicate Detect database ; This implies that each application system Production, Testing, ; Training, will have their own duplicate detect database to use. DAYSONLINE = 31 ; Set the count of days that a batch will live in the database. ; This value can be between 0 and 366. We will not allow longer ; time frames than one year. The End Of Day software will decide ; how many days have passed and remove the batches that have ; expired. If ZERO (0), the Duplicate Database will be purged at ; each End of Day Rollover DETECTMODE = ALL ; Indicates that the module is to evaluate every item ; Values are: ALL, REMIT, PAYMENT ; The module will use the other flags to control what is performed ; in the system. The individual items will be marked Duplicate if ; they match an entry in the database. The items will only be ; rejected if the flag below is set. AUTOFILL = YES ; Duplicate Detect will AutoFill any non-duplicate items ; The Module will fill the database with valid items as they ; are processed ITEMREJECT = YES ; Indicates that the module is to reject all duplicates found TRANREJECT = YES ; Indicates that the module is to reject the entire transaction AMOUNTTEST = YES ; Indicates that the Applied Amount field is to be tested as well MICRTEST = YES YES YES ; Which additional fields to test for Duplicate Items ; AUX EPC TRAN ; Set these fields for ; additional tests DEBUGMode = YES YES YES YES YES YES NO NO ; control dumping messages ; Batch Trans Items Payments Remits Rejects Free Free ; These flags will enable dumping of more messages to the logger Appendix A: Configuration Files Duplicate Detect (rev. 4/30/2009) A-177

10 A-178 RemitTrac Setup Manual *** This page intentionally left blank ***