The information in this article applies to:
This article provides examples of the Data File Integrity Check Error Reports in each STI system, along with explanations of the information contained in each report.
Each time a Data File Integrity Check (DFIC) program is run in an STI system, a log file is created in the STI program directory. This file consists of information identical to the Data File Integrity Check Error Report (if any). The file name of this log file corresponds to the system in which the DFIC is run. The existing log file is deleted to allow for creation of a new log file with the same file name. DFIC log files can be accessed using any text editor (e.g., Windows Notepad, WordPad, etc.). The file name for each system's DFIC log file is provided below.
|
System |
Log File |
|---|---|
| PracticeMaster DFIC Error Report | CMDFIC.LOG |
| TABS III DFIC Error Report | T3DFIC.LOG |
| TABS III Archive File Integrity Check Error Report | T3AFIC.LOG |
| APS DFIC Error Report | A3DFIC.LOG |
| GLS DFIC Error Report | G5DFIC.LOG |
| TAS DFIC Error Report | T4DFIC.LOG |
| TABS III Remote DFIC Error Report | R3DFIC.LOG |
The following is an example of the PracticeMaster Data File Integrity Check Error Report. Clicking a column heading on the report will display the definition for that column.
Date: 01/16/03 PracticeMaster Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Code AOP Name AOP Title File Name File Title Field ID <Index> Rec # Client ID (Key)
54 CMSYSTEM System Files CMJRNL Journal Client_ID 5 110.01 - N
____________________________________________
DFIC was started at: 09:48 AM on 01/16/03
DFIC ended at: 09:48 AM on 01/16/03
1 error(s) were found
|
The following table explains the contents of each column on the PracticeMaster Data File Integrity Check Error Report.
| Column Name | Description | |||||||||||||||
| Error Code | The Error Code indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 54. |
|||||||||||||||
| AOP Name | The AOP Name column shows the directory name of the Area of Practice associated with the file that has the error. In the example shown above, the file containing the error 54 is located in the CMSYSTEM directory. For example, if the PracticeMaster program directory is F:\STI, then the file is located in F:\STI\CMSYSTEM. |
|||||||||||||||
| AOP Title | The AOP Title column indicates the title of the Area of Practice associated with the file that has the error. In the example shown above, the file containing the error 54 belongs to the System Files Area of Practice. |
|||||||||||||||
| File Name | The File Name column shows the file name of the data file in which the error has been found. In the example shown above, the file name of the file containing the error is CMJRNAL. |
|||||||||||||||
| File Title | The File Title column provides the description of the data file in which the error has been found. In the example shown above, the error is in the Journal file. |
|||||||||||||||
| Field ID <Index> | The Field ID <Index> column indicates the field or index containing the error. In the example shown above, the error is in the Client ID field. |
|||||||||||||||
| Rec # | The Rec # column indicates the position of the record in the data file. This information can be used to access the record via the Load Record program, which allows editing of a specific record when the record number is the only information available. The Load Record program can be accessed by selecting Edit | Load Record from the List tab of any PracticeMaster data file. In the example shown above, the error is in record 5. |
|||||||||||||||
| Client ID (Key) | The Client ID (Key) column shows the Client ID or key field associated with the record that has the error. Note: Errors in the Journal, Calendar or Tcode file will include a letter following the value shown in the Client ID (Key) column. This letter indicates the record type. Possible values include the following:
In the example shown above, the record containing the error is for Client ID 110.01, and it is a Note record. |
The following is an example of the TABS III Data File Integrity Check Error Report:
Date: 01/16/03 TABS III Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Client ID Key<Ref#> Seq No
1 11 Invalid Category TK By Cat Prod Category Number 4 :8 278
Key for the 'Key<Ref#>' field.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key represents
Billing Freq Frequency ID
Budget Phase Task ID
Category Category Number
Cat Prod Category Number
Client Fund Reference Number
Client Rate Timekeeper Number
Ledger Reference Number
Ledger Detail Reference Number
Location Location ID
Pymt Alloc Ledger Reference Number
Rect Alloc Record Type
Stmt Code Code ID
Stmt Note Note ID
Task Code ID
Timekeeper Timekeeper Number
TK by Cat Prod Timekeeper Number:Category Number
TK by Tcode Prod Timekeeper Number:Transaction Code Number
TK Prod Timekeeper Number
Fee Reference Number
Cost Reference Number
Pymt Reference Number
Tcode Transaction Code Number
Fee Verif User ID
Cost Verif User ID
Pymt Verif User ID
Flat Fee Verif User ID
Fund Verif User ID
Split Fee Verif User ID
Transf Verif User ID
Upd Stmt Verif User ID
Wrt Off Verif User ID
Wrt UpDn Verif User ID
____________________________________________
DFIC was started at: 09:52 AM on 01/16/03
DFIC ended at: 09:52 AM on 01/16/03
1 error(s) were found
|
The report includes a key that explains the contents of the Key<Ref#> column. The following table explains the contents of each column on the TABS III Data File Integrity Check Error Report.
| Column Name | Description |
| Count | The Data File Integrity Check keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. In the example shown above, there is only one error, so it is the first error. |
| Error Code | The Error Code column indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 11. |
| Error Description | The Error Description column provides a description of the error that has been found. In the example shown above, the error 11 indicates an Invalid Category. |
| File Name | The File Name indicates the file in which the error has been found. In the example shown above, the error is in the TK By Cat Prod (Productivity by Category for Each Timekeeper) file. |
| Field | The Field column indicates which field in the affected file contains the error. In the example shown above, the error is in the Category Number field. |
| Client ID | The Client ID column indicates which client the affected record belongs to, if any. Records in the Productivity by Category for Each Timekeeper file are not stored by Client ID, so this column is blank for the error 11 in the example shown above. |
| Key<Ref#> | The meaning of the information in the Key<Ref#> column varies depending on the file in which the error was found. The legend printed on the report explains the possible meanings of the information in this column. For the Productivity by Category for Each Timekeeper file, the Key<Ref#> column indicates the timekeeper number followed by the category number, separated by a colon. In the example shown above, the error in the example is for timekeeper 4, category 8. |
| Seq No | The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for STI's use only. In the example shown above, the record containing the invalid category has a sequence number of 278. |
The following is an example of the TABS III Archive File Integrity Check Error Report:
Date: 01/17/03 TABS III Archive File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Client ID F/C/P Typ Seq No
1 51 Invalid ID Arch File Client Id 123.sss F 11
____________________________________________
AFIC was started at: 04:47 PM on 01/17/03
AFIC ended at: 04:47 PM on 01/17/03
1 error(s) were found
|
The following table explains the contents of each column on the TABS III Archive File Integrity Check Error Report.
| Column Name | Description |
| Count | The Archive Data Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. In the example shown above, there is only one error, so it is the first error. |
| Error Code | The Error Code column indicates what type of error was found. KB article R10771, "Archive File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 51. |
| Error Description | The Error Description column provides a description of the error that was found. In the example shown above, the error indicates that an invalid ID was found. |
| File Name | The File Name column indicates the file in which the error was found. For the Archive Data Integrity Check program, the value in this column will always be "Arch File", indicating the TABS III Archive file (T3ARCH). |
| Field | The Field column indicates which field in the Archive file contains the error. In the example shown above, the error is in the Client ID field. |
| Client ID | The Client ID column indicates the client to which the affected record belongs. In the example shown above, the archive record belongs to client 123.sss. This is also the actual error, since the TABS III system in which this error occurred is configured for a numeric Key Type. Because 123.sss is an invalid Client ID, this record has apparently become corrupt. |
| F/C/P Typ | The F/C/P Typ column indicates whether the archive transaction that contains the error is a (F)ee, (C)ost or (P)ayment transaction. In the example shown above, the error is in a fee transaction. |
| Seq No | The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for STI's use only. In the example shown above, the record containing the error 51 has a sequence number of 11. |
The following is an example of the APS Data File Integrity Check Error Report:
Date: 01/17/03 APS Data File Integrity Check Error Report Page: 1
Error Record
Count Code Error Description File Name Vendor /Ref # Field Offset
1 5 Missing federal ID Vendor 290.00 18 ID/1099 65
____________________________________________
DFIC was started at: 10:08 AM on 01/17/03
DFIC ended at: 10:08 AM on 01/17/03
1 error(s) were found
|
The following table explains the contents of each column on the APS Data File Integrity Check Error Report.
| Column Name | Description |
| Count | The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. In the example shown above, there is only one error, so it is the first error. |
| Error Code | The Error Code column indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 5. |
| Error Description | The Error Description column provides a description of the error that has been found. In the example shown above, the error 5 indicates a missing Federal ID number in a vendor record. |
| File Name | The File Name column indicates the file name of the file containing the error. In the example shown above, the error is in the Vendor file. |
| Vendor | The Vendor column indicates the vendor number associated with the record containing the error. In the example shown above, the record missing its Federal ID number is for vendor number 290.00. |
| Record/Ref # | The Record/Ref # column indicates the record number of the record containing the error. However, if the error is in the invoice file, the value in this column represents the reference number of the invoice/manual check record. In the example shown above, the record containing the error has a record number of 18. |
| Field | The Field column indicates which field in the affected file contains the error. In the example shown above, the error is in the ID/1099 field. |
| Offset | The Offset column indicates the character position of the invalid character within the file. This information is provided for STI's
use only. Because the error 5 in the example shown above is not an invalid character error, the number 65 in this column is not relevant. |
The following is an example of the GLS Data File Integrity Check Error Report:
Date: 01/17/03 Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
ErrCode 10/045 - Account 110.01 / Ref 68 in Trans File
____________________________________________
DFIC was started at: 09:56 AM on 01/17/03
DFIC ended at: 09:56 AM on 01/17/03
1 error(s) were found
|
The GLS Data File Integrity Check Error Report consists of one line for each error found by the Data File Integrity Check program. The format of each line is as follows:
ErrCode: a /b - Account c / Ref d in e File
The following table explains the meaning of each variable in the example above.
| Variable | Description |
| a | The first variable is the Error Code, which indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 10. |
| b | The second variable indicates the character position of the invalid character. This information is provided for STI's
use only. In the example shown above, the invalid character is in character position 45. |
| c | The third variable indicates the account number associated with the record containing the error. In the example shown above, the error is in a record for account 110.01. |
| d | The fourth variable indicates the reference number of the record containing the error. The reference number can be used to access the record for editing. In the example shown above, the reference number of the record containing the error is 68. |
| e | The fifth and final variable provides a description of the file containing the error. In the example shown above, the error is located in the Trans (transaction) file, which stores GLS journal entries. |
Note: The G5DFIC.LOG file is always created in the GLS program directory, regardless of which GLS client is selected when the DFIC is run. For example, if you select GLS client 1 and run a Data File Integrity Check, then select GLS client 2 and run the DFIC program again, the G5DFIC.LOG file will contain the results of the second DFIC only, regardless of each client's GLS data path.
The following is an example of the TAS Data File Integrity Check Error Report:
Date: 01/16/03 TAS Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Trust ID Key<Ref#> Seq No
1 6 Mismatched Fed ID Master Federal ID 200.03 <3 6
'Key<Ref#>' Legend.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key represents
Master Trust Acct and Bank Acct
Transaction Reference Number
Bank Bank Acct
Payee Payee Name
Attorney Attorney Number
Verification User ID
____________________________________________
DFIC was started at: 09:11 AM on 01/16/03
DFIC ended at: 09:11 AM on 01/16/03
1 error(s) were found
|
The report includes a legend that explains the contents of the Key<Ref#> column. The following table explains the contents of each column on the TAS Data File Integrity Check Error Report.
| Column Name | Description |
| Count | The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. In the example shown above, there is only one error, so it is the first error. |
| Error Code | The Error Code column indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 6. |
| Error Description | The Error Description column provides a description of the error that has been found. In the example shown above, the error 6 indicates mismatched Federal ID numbers (i.e., two or more accounts with the same Trust ID have different Federal ID numbers). |
| File Name | The File Name column indicates the file name of the file containing the error. In the example shown above, the error is in the Master file, which stores trust account information and balances. |
| Field | The Field column indicates which field in the affected file contains the error. In the example shown above, the error is in the Federal ID field. |
| Trust ID | The Trust ID column indicates the Trust ID associated with the record containing the error. In the example shown above, the record containing the error is for Trust ID 200.03. |
| Key<Ref#> | The meaning of the information in the Key<Ref#> column varies depending on the file in which the error is found. Using the legend on the report, we can see that because the error in the example shown above is in the Master file, the value in this column indicates that the error exists in a record for Trust ID 200.03, bank account 3. |
| Seq No | The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for STI's use only. In the example shown above, the record containing the error has a sequence number of 6. |
The following is an example of the TABS III Remote Data File Integrity Check Error Report:
Date: 01/17/03 TABS III Remote Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code File Name Location Description Seq No
1 10 Fee Client 560.00 Ref 4 Fee Hold/Print 9
____________________________________________
DFIC was started at: 12:24 PM on 01/17/03
DFIC ended at: 12:24 PM on 01/17/03
1 error(s) were found
|
The following table explains the contents of each column on the TABS III Remote Data File Integrity Check Error Report.
| Column Name | Description |
| Count | The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. In the example shown above, there is only one error, so it is the first error. |
| Error Code | The Error Code column indicates what type of error has been found. KB article R10528, "Data File Integrity Check Errors (Ver. 10)", lists each possible error code and its meaning. In the example shown above, the Error Code is 10. |
| File Name | The File Name column provides a description of the file containing the error. In the example shown above, the error is in the Fee file. |
| Location | The Location column indicates the client or record with which the error is associated. In the example shown above, the error is in the fee record with reference number 4 for client 560.00. |
| Description | The Description column describes the field that contains the error. In the example shown above, the error is in the Hold/Print field. |
| Seq No | The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for STI's use only. In the example shown above, the record containing the error has a sequence number of 9. |
THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
© 1999-2003 Software Technology, Inc. All rights
reserved.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com