TIBRS Error Manual Cover - Edition 7.0 - Color - TBI Seal · Valid Action Type is I ‐ Incident report. Suggested action: Check with your vendor. 57.7 57 Action Typet is no valid

TIBRS ERROR MESSAGE MANUAL

A RESOURCE MANUAL FOR THE TENNESSEE INCIDENT BASED

REPORTING SYSTEM

PREPARED BY: TENNESSEE BUREAU OF INVESTIGATION

CJIS SUPPORT CENTER

EDITION 7.1 MAY 2017

Table of Contents

Introduction………………………………………………………………………………1

Structure Check Errors …………………………………………………………….3

Zero‐Reporting Segment Errors ……………………………………………..16

Administrative Segment Errors …………………………………………...17

Offense Segment Errors …………………………………………………......28

Property Segment Errors ……………………………………………………..55

Victim Segment Errors …………………………………………………….........103

Offender Segment Errors ………………………………………………………..140

Arrestee Segment Errors …………………………………………………………149

Group B Arrest Report Errors ………………………………………………….164

Officer Involved Shooting Segment Errors ………………………………176

Introduction

This manual is designed as a resource tool for correcting errors generated when data is loaded at either the

state or FBI level. Some errors involve multiple data elements and there can be several reasons that can cause

specific errors to be identified. In some cases, correcting the error condition may involve adjusting data

relationships and/or data elements not specifically mentioned within the error explanation. It is not practical to

attempt to show every possible cause for each error. This manual will describe the end effect of the error

condition detected by the computer.

The manual will identify both FBI and Tennessee errors. The FBI errors appear first and the Tennessee specific

errors will follow in the respective listing for the segment to which they apply.

In some cases, errors will have multiple‐cause possibilities. For example, if the Cleared Exceptionally field

contains a value of N for Not Applicable but the Exceptional Clearance Date contains a date, what is the error?

Was the wrong entry made in the Cleared Exceptionally field or was a date put in by mistake? In these cases, the

explanation provided will describe the overall problem but the true cause of the error will have to be determined

by analysis.

The error numbers are presented in numerical sequence.

100 – 199……………………………Administrative Segment 200 – 299…………………………...Offense Segment

300 – 399……………………………Property Segment 400 – 499……………………………Victim Segment 500 – 599……………………………Offender Segment

600 – 699……………………………Arrestee Segment 700 – 799……………………………Group B Arrestee Segment 800 – 899……………………………Officer Involved Shooting Segment

The exceptions are errors found in FBI control programs and structure checks. These type of errors will be in the numeric range of 001 – 089 and indicate exceptional conditions such as missing segments, duplicate segments, etc. Warning messages are assigned n40 – n49 (n = 0 – 8, corresponding to the segment level) and will not cause a rejection of the incident. The valid codes for each data element can be found in the NIBRS Version 2.1: Technical Specification, the TIBRS Data Collection Manual, and the TIBRS File Specification Layout documents. The remainder of this document contains error numbers and messages and is arranged in numerical order. Note: Some transaction types and the errors associated with them in the FBI errors do not apply to Tennessee agencies. The TBI does not accept the transactions of M – Modify or W – Windows. The data is converted to a Window transaction type when necessary before the file is sent to the FBI.

Tennessee FBI Description Error Error Number Number

STRUCTURE CHECK ERRORS

1 1 Must Be Present ‐‐ Mandatory Field

The data field must be entered; it is required on the Zero‐Reporting Segment (Level 0).

Suggested action: Contact your agency vendor.

15 15 Cannot Have Embedded Blanks Between First and Last Non‐Blank Characters

Zero‐Reporting Segment (Level 0). Although Incident Number should be entered with 12 zeroes, a pre‐edit found embedded blanks between the first and last significant characters.


16 16 Must Be Left‐Justified ‐‐ Blank Detected In First Position

Zero‐Reporting Segment (Level 0). Although Incident Number should be entered with 12 zeroes, a pre‐edit found a blank in the first position. It must begin in position 1 and must also contain 12 zeroes.


17 17 Cannot have characters other than A‐Z, 0‐9, hyphen, and /or blanks

Zero‐Reporting Segment (Level 0). Although Incident Number should be entered with 12 zeroes, a pre‐edit discovered characters other than A through Z, 0 through 9, hyphens, and/or blanks had been entered.


50 50 Levels are out of Numeric order for this Incident

Segment Levels in a Group A Incident must be organized in numerical order. Administrative ‐ 1, Offense ‐ 2, Property ‐ 3, Victim ‐ 4, Offender ‐ 5, Arrestee ‐ 6. For example, an incident having segments 1, 2, 2, 3, 4, 5 must be written in that order, not as 1, 2, 2, 5, 4, 3.

Suggested action: Contact your vendor and request that they verify the file structure.

TIBRS Error Manual, Edition 7.0 August 2016

3

Tennessee FBI Description Error Error Number Number 51 51 Invalid Record Level on file

Segment Level must contain data values 0 ‐ 8.

Suggested action: Contact your vendor and request that they verify the file structure.

52 52 Not a valid ORI ‐ Not on UCR ORI file

Data element 1 (ORI Number) and Data Element 25C (ORI ‐ Other Jurisdiction ‐ Officer) when submitted must be valid nine‐character NCIC numbers.

Suggested action: Enter valid ORI for officer entered, must contain valid two letter abbreviation for state and cannot be your own ORI.

55 55 Cannot have an initial Incident record without starting with Record Level 1

When an I ‐ Incident Report is submitted, the first segment must be the Administrative Segment (Level 1). In this case, the first record received for the incident was not an Administrative Segment.

Suggested action: The incident report is missing the administrative segment. Ensure all data is entered for the incident and check with vendor if necessary.

56 56 Incident Already on File

Data Element 2 (Incident Number) must be a unique number for each incident submitted. No two incidents can have the same incident number.

Suggested action: The re‐submission of the incident was not preceded by a delete record. Resubmit the incident or check with your vendor.


4

Tennessee FBI Description Error Error Number Number 57 57 Action Type is not valid for the record level submitted

Segment Action Type must be populated with a valid data value appropriate for the Segment Level. The values of I ‐ Incident report, A ‐ Add, and D ‐ Delete must be applicable to the appropriate segment levels 0 ‐ 8 based upon the following table:

Action – Valid only with these levels

I – Segment Levels 1 – 6, 8

A – 0 – Zero reporting segment

7 – Group B Arrest report

D – 1 – Administrative segment

7 – Group B Arrest report

Suggested action: Check with your vendor.

57.1 57 Action Type is not valid for the record level submitted, Administrative Segment

Valid Action Type is I ‐ Incident report or D ‐ Delete.


57.2 57 Action Type is not valid for the record level submitted, Offense Segment

Valid Action Type is I ‐ Incident report.


57.3 57 Action Type is not valid for the record level submitted, Property Segment




5

Tennessee FBI Description Error Error Number Number 57.4 57 Action Type is not valid for the record level submitted, Victim

Segment



57.5 57 Action Type is not valid for the record level submitted, Offender Segment



57.6 57 Action Type is not valid for the record level submitted, Arrestee Segment



57.7 57 Action Type is not valid for the record level submitted, Group B Arrestee Segment

Valid Action Type is A ‐ Add or D ‐ Delete.


57.8 57 Action Type is not valid for the record level submitted, Officer Involved Shooting Segment



58 58 All Segments on data file must have same control Info

Month of submission and Year of submission must contain the same data values for each segment. The first segment processed will be compared with all other segments to check for this condition.

Suggested action: Some incidents had a different month and year in the tape month and year fields. Check with your vendor.


6

Tennessee FBI Description Error Error Number Number 58.1 58 All Segments on data file must have same control Info,

Administrative Segment

Month of submission and Year of submission are different for Administrative segment.


58.2 58 All Segments on data file must have same control Info, Offense Segment

Month of submission and Year of submission are different for Offense segment.


58.3 58 All Segments on data file must have same control Info, Property Segment

Month of submission and Year of submission are different for Property segment.


58.4 58 All Segments on data file must have same control Info, Victim Segment

Month of submission and Year of submission are different for Victim segment.


58.5 58 All Segments on data file must have same control Info, Offender Segment

Month of submission and Year of submission are different for Offender segment.


58.6 58 All Segments on data file must have same control Info, Arrestee Segment

Month of submission and Year of submission are different for Arrestee segment.



7

Tennessee FBI Description Error Error Number Number 58.7 58 All Segments on data file must have same control Info, Group

B Arrestee Segment

Month of submission and Year of submission are different for Group B Arrestee segment.


58.8 58 All Segments on data file must have same control Info, Officer Involved Shooting Segment

Month of submission and Year of submission are different for Officer Involved Shooting segment.


59 59 All Segments on data file must be from same State

Data Element 1 (ORI) must contain the same state abbreviation code (TN) in the first two positions (record positions 17 and 18).

Suggested action: Some segments had a different state abbreviation in the ORI. Check with your vendor.

59.1 59 All Segments on data file must be from same State, Administrative Segment

State abbreviation in ORI is different for Administrative segment.


59.2 59 All Segments on data file must be from same State, Offense Segment

State abbreviation in ORI is different for Offense segment.


59.3 59 All Segments on data file must be from same State, Property Segment

State abbreviation in ORI is different for Property segment.



8

Tennessee FBI Description Error Error Number Number 59.4 59 All Segments on data file must be from same State, Victim

Segment

State abbreviation in ORI is different for Victim segment.


59.5 59 All Segments on data file must be from same State, Offender Segment

State abbreviation in ORI is different for Offender segment.


59.6 59 All Segments on data file must be from same State, Arrestee Segment

State abbreviation in ORI is different for Arrestee segment.


59.7 59 All Segments on data file must be from same State, Group B Arrestee Segment

State abbreviation in ORI is different for Group B Arrestee segment.


59.8 59 All Segments on data file must be from same State, Officer Involved Shooting Segment

State abbreviation in ORI is different for Officer Involved Shooting segment.


60 60 Processing Date precedes month/year in positions 7‐12, Zero Segment

Month of submission and Year of submission must precede the date the TBI receives the data submission. This edit checks for data submitted for a future month/year. The month/year of each record cannot be after the month/year the TBI processes the file.

Suggested action: The month/year in the submission were after the month/year TBI received the file for processing.


9

Tennessee FBI Description Error Error Number Number 60.1 60 Processing Date precedes month/year in positions 7‐12,

Administrative Segment

The month/year in the Administrative segment were after the month/year TBI received the file for processing.


60.2 60 Processing Date precedes month/year in positions 7‐12, Offense Segment

The month/year in the Offense segment were after the month/year TBI received the file for processing.


60.3 60 Processing Date precedes month/year in positions 7‐12, Property Segment

The month/year in the Property segment were after the month/year TBI received the file for processing.


60.4 60 Processing Date precedes month/year in positions 7‐12, Victim Segment

The month/year in the Victim segment were after the month/year TBI received the file for processing.


60.5 60 Processing Date precedes month/year in positions 7‐12, Offender Segment

The month/year in the Offender segment were after the month/year TBI received the file for processing.


60.6 60 Processing Date precedes month/year in positions 7‐12, Arrestee Segment

The month/year in the Arrestee segment were after the month/year TBI received the file for processing.



10

Tennessee FBI Description Error Error Number Number 60.7 60 Processing Date precedes month/year in positions 7‐12,

Group B Arrestee Segment

The month/year in the Group B Arrestee segment were after the month/year TBI received the file for processing.


60.8 60 Processing Date precedes month/year in positions 7‐12, Officer Involved Shooting Segment

The month/year in the Officer Involved Shooting segment were after the month/year TBI received the file for processing.


65.1 65 Each Level 2 Offense must have at least one victim

Each Offense segment must have at least one Victim segment connected to it in the Victim connected to Offense Code. There must be a Victim for each Offense entered.

Suggested action: Enter a Victim for each Offense in the incident or edit/delete the Offense(s) entered.

65.2 65 Each Related victim Offense must be associated with a valid Offense Segment

Each Victim Offense entered must be connected to a valid offense in the Offense segment.

Suggested action: Verify each Victim offense corresponds to a valid offense in the Offense segment.

70 70 The corresponding offender record must be present

Offender numbers to be related has a value that does not have a corresponding Offender segment. Example, the offender number to be related has a value of 15; however, there is not an Offender segment with a value of 15 in the Offender sequence number.

Suggested action: Correct the offender sequence number ‐ contact your vendor.


11

Tennessee FBI Description Error Error Number Number 71 71 Cannot have Arrestees if Cleared Exceptionally

When an Exceptional Clearance is submitted in the Administrative segment, there can be no arrest segments associated with the Group A Incident report having an Arrest Date on or earlier than the Exceptional Clearance Date.

Suggested action: If an arrest occurred, remove all Exceptional Clearance data.

72 72 Recovered Property must also be submitted as Stolen

The Property Description field contains property that was reported as recovered without also being reported as stolen within that same incident. Any property reported as recovered must first be reported as stolen. An exception to this rule would be if the original property reported stolen is a Vehicle: 03 ‐ Automobile, 05 ‐ Bus, 24 ‐ Other Motor Vehicle, 28 ‐ Recreational Vehicle, or 37 – Trucks and the recovered property is 38 – Vehicle Parts/Accessories.

Suggested action: Check and verify valid codes have been entered. Additionally, ensure that the recovered property is submitted after the stolen property record.

73 73 Number of Recovered Vehicles cannot be greater than the number Stolen

The number of recovered vehicles must be equal to or less than the number of stolen vehicles.

Suggested action: Reconcile the number of stolen and recovered vehicles and resubmit the incident.

74 74 Property Record 9 (Level 3) must exist with this offense

When an I ‐ Incident report is submitted that contains an Offense segment for a Crime Against Property, Kidnapping, Gambling, or Drug/Narcotic Offense, a Property Segment must be submitted.

Suggested action: If offense classification is correct, resubmit the incident with the required property record.


12

Tennessee FBI Description Error Error Number Number 75.4 75 Administrative, Offense, Victim and Offender segments must

all be present

When an I ‐ Incident is submitted, the following segments must be included: Administrative, Offense, Victim, and Offender. One of these is missing.

Suggested action: Ensure all required segments are entered and resubmit the incident.

76 76 Property Record (Level 3) cannot exist with offenses submitted

A Property segment was submitted with a Group A Incident without an applicable property offense code. Property segments can only be submitted with Crimes Against Property, Kidnapping, Gambling, or Drug/Narcotic Offense.

Suggested action: If offense classification is correct, delete all property information and resubmit the incident.

77 77 Need a Property Loss Code of '1' or '8' when this offense is attempted

If Offense Attempted/Completed is "A", and the Offense code is a Crime Against Property, Kidnapping, Gambling, or Drug/Narcotic offense, then the Type of Property Loss must be 1 ‐ None or 8 ‐ Unknown.

Suggested action: If offense classification and offense status is correct, enter correct property loss code with the property information.

78 78 A valid Property Loss Code does not exist for this completed offense

If the Offense code is a Crime Against Property, Kidnapping, Gambling, Drug/Narcotic Violations, or Drug Equipment Violations, and the offense is Completed, a Property segment must be present with a valid code in the Type Property Loss field.

Suggested action: If offense classification is correct, enter correct property loss code with the property information.


13

Tennessee FBI Description Error Error Number Number 80 80 Crimes Against Society can only have one victim

If the Group A Incident report submission only contains offense(s) that are Crimes Against Society, then the type victim must be S ‐ Society/Public and only one victim is submitted.

Suggested action: If the only offense in the incident is a Crime Against Society, delete the other victims entered, else, add other offenses for those victims within the incident report.

81 81 This Property Loss Code cannot exist with the offenses submitted

The Type Property Loss field has a code that is not applicable to any offense submitted with that incident. Refer to the TIBRS Data Collection Manual ‐ Property section for valid codes.

Suggested action: If offense classification is correct, ensure that correct property loss type code is entered for the specific offense(s) occurring in the incident.

84 84 Recovered Property Value cannot be greater than the value when stolen

When Property segments for both stolen and recovered property are in the incident, the recovered value cannot be greater than the value when stolen.

Suggested action: Reconcile the property value entered for stolen and recovered. Recovered value can only be equal to or less than the stolen value.

85 85 When connected, each Victim must be connected to all offenders

When a Victim is connected to a Crime Against Person or Robbery offense(s), all Offender Sequence Number fields must be entered in the Offender Numbers to be Related field. If there are more than ten offenders, use the ten closest in relationship to all the victims.

Suggested action: One or more offender sequence number(s) were omitted in the Victim segment. Ensure that all victims are linked to all offenders.


14

Tennessee FBI Description Error Error Number Number 86 86 The last 2 positions of the participant's ORI are Invalid

A nonfederal participant must have 00 in positions 8 and 9 in the ORI number field. However, some agencies in Tennessee have other characters in these positions and have valid ORI numbers.

Suggested action: Ensure that the ORI is valid.

86.1 86 The last 2 positions of the participant's ORI are Invalid, Administrative Segment

The last two digits in the ORI number are not 00 in the Administrative segment.


86.2 86 The last 2 positions of the participant's ORI are Invalid, Offense Segment

The last two digits in the ORI number are not 00 in the Offense segment.


86.3 86 The last 2 positions of the participant's ORI are Invalid, Property Segment

The last two digits in the ORI number are not 00 in the Property segment.


86.4 86 The last 2 positions of the participant's ORI are Invalid, Victim Segment

The last two digits in the ORI number are not 00 in the Victim segment.


86.5 86 The last 2 positions of the participant's ORI are Invalid, Offender Segment

The last two digits in the ORI number are not 00 in the Offender segment.



15

Tennessee FBI Description Error Error Number Number 86.6 86 The last 2 positions of the participant's ORI are Invalid,

Arrestee Segment

The last two digits in the ORI number are not 00 in the Arrestee segment.


86.7 86 The last 2 positions of the participant's ORI are Invalid, Group B Arrestee Segment

The last two digits in the ORI number are not 00 in the Group B Arrestee segment.


86.8 86 The last 2 positions of the participant's ORI are Invalid, Officer Involved Shooting Segment

The last two digits in the ORI number are not 00 in the Officer Involved Shooting segment.


ZERO ‐ REPORTING SEGMENT ERRORS

90 90 Zero‐Reporting Month is not 01‐12

A segment level 0 (Zero report) was submitted that had an invalid month in positions 38 ‐ 39.


91 91 Zero‐Reporting Year is Invalid

The Zero report did not have four valid numeric digits in positions 40 ‐ 43.


92 92 Zero‐Reporting Incident Number must be all Zeroes

The Zero report Incident Number was not all zeroes.



16

Tennessee FBI Description Error Error Number Number 93 93 Zero‐Reporting Month/Year was prior to the Base Date

The Zero report was submitted with a month and year entered that is earlier than January 1 of the previous year or before the agency converted to NIBRS/TIBRS.


94 94 Zero‐Reporting Month/Year Exceeded Month/Year of Tape

The Zero report was submitted with a month/year that was later than the month and year of the file.

Note: Error Numbers 001, 015, 016, and 017 are also Zero‐reporting segment errors.


94.1 The zero report was submitted with a month/year that was later than month/year on file

The Zero report was submitted with a month/year that was later than the month and year of the file.

Note: Error Numbers 001, 015, 016, and 017 are also Zero‐reporting segment errors.


ADMINISTRATIVE SEGMENT ERRORS

101.1 101 Segment 1 ORI is too long

ORI number entered is too many characters.

Suggested action: Valid ORI number is nine (9) characters long, with the first two digits being the state abbreviation (TN). Edit ORI number.

101.2 101 Segment 1 ORI is required

The ORI number was not included in the submission.

Suggested action: Enter the ORI number and resubmit the incident.


17

Tennessee FBI Description Error Error Number Number 101.3 101 Segment 1 Incident Number is required

The data field must be entered ‐‐ it is required.

Suggested action: Refer to the field number on the error report and ensure data is entered for that field then resubmit the incident.

101.5 101 Exceptional Clearance entry is required

The data field must be entered ‐‐ it is required.

Suggested action: Refer to the field number on the error report and ensure data is entered for that field then resubmit the incident.

104 104 Exceptional Clearance is invalid

The field for Exceptional Clearance contains data that is not a valid TIBRS code.

Suggested action: Delete the Exceptional Clearance data or edit to a valid TIBRS code and resubmit the incident.

104.91 104 Cargo Theft Entry MUST be either Y, N, or Blank.

Data entry in the Cargo Theft field must be one of the following: Y ‐ Yes, N ‐ No or the field must be left blank.

Suggested action: Edit the data in the Cargo Theft field to either Y or N or delete the entry in the Cargo Theft field and leave blank.

104.92 104 Cargo Theft Entry is required with the incident offenses.

An entry in the Cargo Theft field is required if the reported Offense is one of the following: 120 ‐ Robbery, 23D ‐ Theft From a Building, 23F ‐ Theft From a Motor Vehicle, 23H ‐ All Other Larceny, 26A ‐ Fraud ‐ False Pretenses/Swindle/Con, 26B ‐ Credit Card/ATM Fraud, 26C ‐ Fraud ‐ Impersonation, 26E ‐ Wire Fraud, 210 ‐ Extortion/Blackmail, 220 ‐ Burglary, 240 ‐ Motor Vehicle Theft, 270 ‐ Embezzlement, or 510 ‐ Bribery.

Suggested action: If the offense reported is one requiring a Cargo Theft indicator, an entry in the Cargo Theft field of Y or N must be made. If the offense is not one of the ones requiring a Cargo Theft indicator, the Cargo Theft field must be blank.


18

Tennessee FBI Description Error Error Number Number 105.1 105 Incident Date invalid ‐ YEAR

An entry in the Incident Date ‐ Year field has been made using invalid characters.

Suggested action: Edit the Incident Date field and enter the Incident Date ‐ Year using 4 numeric characters.

105.2 105 Incident Date invalid ‐ MONTH

An entry in the Incident Date ‐ Month field has been made using invalid characters.

Suggested action: Edit the Incident Date field and enter the Incident Date ‐ Month using 2 numeric characters (01 ‐ 12).

105.3 105 Incident Date invalid ‐ DAY

An entry in the Incident Date ‐ Day field has been made using invalid characters.

Suggested action: Edit the Incident Date field and enter the Incident Date ‐ Day using 2 numeric characters (01 ‐ 31).

105.4 105 Incident Date contains invalid characters

The Incident Date field contains a date that is not entered correctly. Each component of the date must be valid. The months must be 01 ‐ 12, days must be 01 ‐ 31, and the year must include 4 numeric digits. Days cannot exceed the maximum for the month and the date cannot exceed the current date.

Suggested action: Enter the Incident Date in the correct format and resubmit the incident.

105.5 105 Exceptional Clearance Date invalid ‐ YEAR

An entry in the Exceptional Clearance Date ‐ Year field has been made using invalid characters.

Suggested action: Edit the Exceptional Clearance Date field and enter the Exceptional Clearance Date ‐ Year using 4 numeric characters.


19

Tennessee FBI Description Error Error Number Number 105.6 105 Exceptional Clearance Date invalid ‐ MONTH

An entry in the Exceptional Clearance Date ‐ Month field has been made using invalid characters.

Suggested action: Edit the Exceptional Clearance Date field and enter the Exceptional Clearance Date ‐ Month using 2 numeric characters (01 ‐ 12).

105.7 105 Exceptional Clearance Date invalid ‐ DAY

An entry in the Exceptional Clearance Date ‐ Day field has been made using invalid characters.

Suggested action: Edit the Exceptional Clearance Date field and enter the Exceptional Clearance Date ‐ Day using 2 numeric characters (01 ‐ 31).

105.8 105 Exceptional Clearance Date contains invalid characters

The Exceptional Clearance Date field contains a date that is not entered correctly. Each component of the date must be valid. The months must be 01 ‐ 12, days must be 01 ‐ 31, and the year must include 4 numeric digits. Days cannot exceed the maximum for the month and the date cannot exceed the current date.

Suggested action: Enter the Exceptional Clearance Date in the correct format and resubmit the incident.

115 115 Incident Number contains embedded blanks

The Incident Number contains embedded blanks between the first and last significant characters.

Suggested action: Use only incident numbers that conform to the parameters for the incident number which include: capital letters only, numerals, hyphens, or blanks at the end of the incident number (no blanks within the incident number or at the beginning). If the incident number is automatically generated, contact your vendor about the issue.


20

Tennessee FBI Description Error Error Number Number 116 116 Incident Number must be left justified

The Incident Number must be left justified with blank right‐fill. Since the number is less than 12 characters, it must begin in position 1. One or more blanks were entered starting in position 1 by the data.

Suggested action: Remove blanks at the beginning of the incident number and resubmit. If the incident number is automatically generated, contact your vendor about the issue.

117 117 Incident Number contains invalid characters

The Incident Number can only have character combinations of A ‐ Z, 0 ‐ 9, hyphens, and /or blanks. Example 89‐123‐SC is valid, but 89+123*SC is invalid.

Suggested action: Use only incident numbers that conform to the parameters for the incident number which include: capital letters only, numerals, hyphens, or blanks at the end of the incident number (no blanks within the incident number or at the beginning). If the incident number is automatically generated, contact your vendor about the issue.

118 118 Incident Date is after stop date

Incidents have been submitted containing an Incident Date on or after the date that an agency is placed in Covered by Status. When data is received for an agency in Covered by Status, the agency will be removed from Covered by Status, the submission processed and the agency notified.

Suggested action: If the agency is in Covered by Status, no data should be submitted by that agency. If data has been submitted, then the agency should notify TBI that they are beginning to submit data again.


21

Tennessee FBI Description Error Error Number Number 119.91 119 Cargo Theft Entry is only allowed for selected property

offenses.

The entry of either "Yes" or "No" in the Cargo Theft Field is only allowed for the following Crime Against Property offenses: 120 ‐ Robbery, 23D ‐ Theft From a Building, 23F ‐ Theft From Motor Vehicle, 23H ‐ All Other Larceny, 26A ‐ False Pretenses/Swindle/Con, 26B ‐ Credit Card/ATM Fraud, 26C ‐ Impersonation, 26E ‐ Wire Fraud, 210 ‐ Extortion/Blackmail, 220 ‐ Burglary, 240 ‐ Motor Vehicle Theft, 270 ‐ Embezzlement, and 510 ‐ Bribery.

Suggested action: Review the offense(s) entered. If the offense is not one of the permitted offenses, then delete the Cargo Theft indicator and leave blank or edit the offense.

151 151 RDI must be R or blank

Within the Incident Date/Hour field is a report indicator. This field must be blank if the incident date is known. If the incident date is unknown, the report date would be entered instead and must be indicated with an "R" in the report indicator field in the Administrative segment.

Suggested action: If entering "Report Date" instead of Incident Date, only an "R" can be entered in the indicator field. NOTE: Report Date should be used on a very limited basis. In almost all cases, the incident date or the first date an incident reasonably could have happened can be determined.

152.1 152 Incident Hour is invalid

If hour is entered within the Incident Date/Hour, it must be 00 through 23. If 00 is entered, ensure the Incident Date is entered as if the time was 1 minute past midnight. NOTE: TIBRS uses 24 hour military time.

Suggested action: An incorrect number was entered in the first position of the hour field. It can only be 0, 1, or 2. The second position can be 0 – 9.


22

Tennessee FBI Description Error Error Number Number 152.2 152 Incident Hour is non‐numeric or blank

If hour is entered within the Incident Date/Hour, it must be 00 through 23. If 00 is entered, ensure the Incident Date is entered as if the time was 1 minute past midnight. NOTE: TIBRS uses 24 hour military time.

Suggested action: An incorrect number was entered in the first position of the hour field. It can only be 0, 1, or 2.

153 153 Exceptional Clearance entry without Exceptional Clearance Date

Data has been entered for Cleared Exceptionally; however, there is no date entered in the Exceptional Clearance Date field.

Suggested action: If the incident is cleared exceptionally, enter the Exceptional Clearance Date in the date field. If the incident is not cleared exceptionally, delete the entry in the Cleared Exceptionally field.

155 155 Exceptional Clearance Date is prior to Incident Date

The Exceptional Clearance Date is earlier than the Incident Date.

Suggested action: Reconcile the Exceptional Clearance Date and the Incident Date ‐ Exceptional Clearance Date cannot be earlier than the Incident Date.

156 156 Exceptional Clearance Date is required

The Exceptional Clearance Date must be present if the case was cleared exceptionally. If an entry of A ‐ E is made in the Cleared Exceptionally field, than a date must be present.

Suggested action: The Exceptional Clearance Date field is blank but a value was entered in the Cleared Exceptionally field.

170 170 Incident Date is after Tape Date

The incident date is later than the year and month of the file. Ex. A May 2011 file cannot contain incidents occurring later than May 2011.

Suggested action: Resubmit the incidents with the date that was later than the submission month with the next month's submission.


23

Tennessee FBI Description Error Error Number Number 172 172 Incident Date precedes 1/1/91

The Incident Date/Hour cannot be earlier than 01/01/1991. This is applied to all Incident Report submissions. The beginning date will eliminate dates that are known to be obviously incorrect since NIBRS began accepting data on this date.

Suggested action: TIBRS still requires the information. Ignore the FBI error message.

173 173 Incident Date is prior to NIBRS start date

A Group A Incident Report was submitted with a date entered in the Incident Date/Hour field that occurred before the agency converted to TIBRS.

Suggested action: Verify the Incident Date that has been entered. If the date is prior to the date the agency converted to TIBRS, the incident should not be reported. The exception to this rule is when an Exceptional Clearance is reported for a pre‐TIBRS incident.

175.1 175 Incident Date invalid ‐ MONTH

The tape control date and the Incident Date must be valid dates for calculating time frames. Months must be entered using 2 numeric characters (01 ‐ 12).

Suggested action: The data in the Incident Date field must contain valid month numbers (01 ‐ 12). Check with your vendor if this error occurs.

175.2 175 Incident Date invalid ‐ YEAR

The tape control date and the Incident Date must be valid dates for calculating time frames. Year must be entered using 4 numeric characters.

Suggested action: The data in the Incident Date field must contain valid year numbers. Check with you vendor if this error occurs.

175.3 175 Tape Date invalid ‐ MONTH

The Tape Month must be a valid month for calculating time frames.

Suggested action: The positions in these fields must contain valid month numbers. Check with your vendor if this error occurs.


24

Tennessee FBI Description Error Error Number Number 175.4 175 Tape Date invalid ‐ YEAR

The Tape Year must be a valid year for calculating time frames.

Suggested action: The positions in this field must contain valid year numbers. Check with your vendor if this error occurs.

UCRR_010 NULL Unable to conduct transaction: Action type not implemented

The action type is not used in Tennessee.


UCRR_011 NULL Unable to conduct transaction‐ (I)ncident Action: Incident Already Exists

The Group A Incident could not be added ‐ an incident with that number is already in the database. If the incident needs to be updated, a delete record must precede the "I" type transaction.

Suggested action: Resubmit the incident and ensure that a "Delete" record is submitted in the file first for the incident. Check with your vendor.

UCRR_012 NULL Unable to conduct transaction‐ (A)dd Action: Arrestee Already Exists

The Group B Arrest could not be added ‐ a Group B Arrest with that number is already in the database. If the Group B Arrest needs to be updated, a delete record must precede the "A" type transaction. The Delete record must contain the complete Group B Arrest to be valid.

Suggested action: Resubmit the Group B Arrest record and ensure that a "Delete" record is submitted in the file first for the Group B Arrest. Check with your vendor.

UCRR_013 NULL Unable to conduct transaction‐ (D)elete Action: Incident Does Not Exist

The Incident could not be deleted. There was not a matching Incident number in the database.

Suggested action: Review agency records and verify that the Incident Number submitted is a valid Incident Number.


25

Tennessee FBI Description Error Error Number Number UCRR_014 NULL Unable to conduct transaction‐ (I)ncident Action: Illegal

Action for Group 'B' Arrest Report

Action type is not valid for a Group B Arrest.


UCRR_015 NULL Unable to conduct transaction‐ Action Type Unknown

Action type is not valid.


UCRR_016 NULL Unable to conduct transaction‐ (A)dd Group B Arrest Action to Group A Incident

A Group B Arrest cannot be added to a Group A Incident with an action type of "A". The Group A Incident must be preceded by a delete, and the record resubmitted with an action type of "I". The Group B Arrest offense must come in with the Group A Arrest Segment.

Suggested action: If the Group A Incident actually is cleared by a Group B Arrest, the Group B arrest record must be the same format as a Group A Arrest Record. NOTE: In almost all circumstances, a Group A Incident will be cleared with an arrest with a Group A Offense as the arresting offense.

UCRR_017 NULL Unable to conduct transaction‐ (A)dd Group A Arrest Action to Group B Incident

Cannot add a Group A Arrest offense to a Group B Arrest segment.


TENNESSEE SPECIFIC ADMINISTRATIVE SEGMENT ERRORS

TN_100 Officer Involved Shooting must be Y or N

Data entry in the Officer Involved Shooting field must be one of the following: Y ‐ Yes or N ‐ No.

Suggested action: Edit the data in the Officer Involved Shooting field to either Y or N.


26

Tennessee FBI Description Error Error Number Number TN_101.1 Officer Involved Shooting Investigated by Outside Agency

field must be Y/N

Data entry in the Officer Involved Shooting Investigated by Outside Agency field must be one of the following: Y ‐ Yes or N ‐ No, if the Officer Involved Shooting Flag is Y ‐ Yes. Otherwise this field must be blank.

Suggested action: Edit the data in the Officer Involved Shooting Investigated by Outside Agency field to either Y or N or delete the entry in the Officer Involved Shooting Investigated by Outside Agency field and leave blank.

TN_101.2 Officer Involved Shooting cannot be blank

Data entry in the Officer Involved Shooting field must be one of the following: Y ‐ Yes or N ‐ No. It cannot be blank.

Suggested action: Edit the data in the Officer Involved Shooting field to either Y or N.

TN_102.1 Address must include street number, street, city, state, and zip code

Incident address must include the following data: street number, street name, city, state, and the zip code for the location where the incident occurred.

Suggested action: Enter the required data in the appropriate Address field.

TN_102.2 Invalid Address

The correct format for Incident Address is Street number, address1, address2, city, state, and zip code. All fields are separated by commas. If address2 field is not applicable, place a comma (,) to denote it is empty.

Suggested action: Enter the missing data in the appropriate Address field.

TN_102.3 Latitude must be within 34.85654 and 36.75412

The valid latitude for Tennessee would be from 34.85654 to 36.75412.

Suggested action: Edit the data in the Latitude field to a valid value.


27

Tennessee FBI Description Error Error Number Number TN_102.31 Officer Involved Shooting Investigated by Outside Agency

field must be blank (no entry in Officer Involved Shooting)

The incident is not flagged as an Officer Involved Shooting, therefore the Officer Involved Shooting Investigated by Outside Agency field must be blank.

Suggested action: Delete the Officer Involved Shooting Investigated entry.

TN_102.4 Longitude must be within ‐81.59809 and ‐90.49735

The valid longitude for Tennessee would be from ‐81.59809 to ‐90.49735.

Suggested action: Edit the data in the Longitude field to a valid value.

TN_102.5 Latitude and Longitude are required

Any location without a specific street address must have the latitude and the longitude submitted instead of the address. Note: The administrative segment must still be 182.

Suggest action: Enter either a valid Incident Address or Latitude and Longitude for the incident.

OFFENSE SEGMENT ERRORS

201.1 201 Segment 2 ORI is missing

The ORI number was not included in the offense segment It is required.

Suggested action: Enter the NCIC ORI number for the agency and resubmit the incident.

201.2 201 Segment 2 Incident Number is missing

The Incident number was not included in the offense segment. It is required.

Suggested action: Enter the Incident number and resubmit the incident.


28

Tennessee FBI Description Error Error Number Number 201.3 201 UCR Offense Code is missing

The Offense code was not included in the offense segment. It is required.

Suggested action: Enter the Offense code and resubmit the incident.

201.4 201 Attempted/Completed entry is missing

The data element to indicate whether the offense was Attempted or Completed was not included in the offense segment. It is required.

Suggested action: Enter the data to indicate whether the incident offense was Attempted or Completed and resubmit the incident.

201.5 201 Using entry is missing

The Offender Suspected of Using data was not included in the Offense segment. It is required.

Suggested action: Enter the data to indicate whether the Offender was suspected of using and resubmit the incident.

201.6 201 Location entry is missing

The Location where the offense occurred was not included in the offense segment. It is required.

Suggested action: Enter the Location where the offense occurred and resubmit the incident.

201.7 201 Hate/Bias entry is missing

Data to indicate whether or not the incident was Hate/Bias motivated was not included in the submission.

Suggested action: Enter the data to indicate whether the incident was Hate/Bias motivated or not and resubmit the incident.


29

Tennessee FBI Description Error Error Number Number 202 202 Number of Premises Entered value is non‐numeric

Data entered in the number of premises entered field was not entered as a numeric entry. Valid data value is: 01 ‐ 99.

Suggested action: Enter a numeric entry for number of premises and resubmit the incident.

204.1 204 UCR Offense Code is invalid

The UCR Offense code entered for the incident is not a valid TIBRS offense code.

Suggested action: Edit the incident offense segment and enter a valid TIBRS offense code and resubmit the incident.

204.11 204 Weapon Code is invalid

The code entered for the type of Weapon used in the commission of the offense(s) is not a valid TIBRS code.

Suggested action: Enter a valid Weapon Type code and resubmit the incident.







204.2 204 Hate/Bias entry is invalid

The code entered for the Hate/Bias Motivation is not a valid TIBRS code.

Suggested action: Enter a valid Hate/Bias Motivation code and resubmit the incident.


30

Tennessee FBI Description Error Error Number Number 204.3 204 Location entry is invalid

The code entered for the Location where the incident/offense occurred is not a valid TIBRS code.

Suggested action: Enter a valid Location code and resubmit the incident.

204.4 204 Method of Entry code is invalid

The code entered for the Method of Entry, Force or No Force, is not a valid TIBRS code.

Suggested action: Enter a valid code for the Method of Entry and resubmit the incident.

204.5 204 Using Code is invalid

The code entered for the Offender Suspected of Using is not a valid TIBRS code.

Suggested action: Enter a valid code and resubmit the incident.







204.8 204 Type Criminal Activity is invalid

The code entered for the Criminal Activity Type is not a valid TIBRS code.



31

Tennessee FBI Description Error Error Number Number 204.9 204 Type Criminal Activity is invalid

The code entered for the Criminal Activity Type is not a valid TIBRS code.


204.10 204 Type Criminal Activity is invalid

The Type Criminal Activity entered is not a valid TIBRS code.

Suggested action: Enter a valid Criminal Activity Type and resubmit the incident.

206.1 206 Duplicate Using Code (1 and 2)

The data element in error is one that contains multiple data values. When more than one is entered, none can be duplicate codes.

Suggested action: Refer to the field number in the error message and enter valid information for all options without entering duplicate values.








32

Tennessee FBI Description Error Error Number Number 206.4 206 Duplicate Type of Criminal Activity entry (1 and 2)



206.5 206 Duplicate Type of Criminal Activity entry (1 and 3)



206.6 206 Duplicate Type of Criminal Activity entry (2 and 3)



206.7 206 Duplicate Weapon entry (1 and 2)




33

Tennessee FBI Description Error Error Number Number 206.8 206 Duplicate Weapon entry (1 and 3)



206.9 206 Duplicate Weapon entry (2 and 3)



206.11 206 Duplicate Bias Motivations (1 through 5)



207.1 207 Entry of N in Using field must be exclusive

The data element in error can have multiple data values and was entered with multiple values. However, the entry shown in brackets cannot be entered with any other data value.

Suggested action: Refer to the field number in the error message and enter valid information. In most cases, one of the entries was "none" which indicates that no other information is valid for that field value in the particular incident.


34

Tennessee FBI Description Error Error Number Number 207.2 207 Entry of 99 in the Weapon/Force field must be exclusive



207.3 207 Entry of 99 in the Weapon/Force field must be exclusive



207.4 207 Entry of 99 in the Weapon/Force field must be exclusive




Incident Number contains embedded blanks between the first and last significant numbers.

Suggested action: Remove blanks at the beginning of the incident number and resubmit. If incident number is automatically generated, contact your vendor about the issue.


35

Tennessee FBI Description Error Error Number Number 216 216 Incident Number must be left justified

Incident Number must be left justified with blank right‐fill. Since the number is less than 12 characters, it must begin in position 1; one or more blanks were entered starting in position 1 followed by data.



The Incident Number can only have character combinations of A ‐ Z, 0 ‐ 9, hyphens, and/or blanks. Example: 89‐123‐SC is valid, but 89+123*SC is invalid.

Suggested action: Use only incident numbers that conform to the parameters for the incident number which include: capital letters only, numerals, hyphens, or blanks at the end of the incident number (no blanks within the incident number or at the beginning). If incident number is automatically generated, contact your vendor about the issue.

219.1 219 Type of Criminal Activity required

Type Criminal Activity field can only be entered when the UCR offense code is: 250 ‐ Counterfeiting/Forgery, 280 ‐ Stolen Property Offense, 35A ‐ Drug/Narcotic Violations, 35B ‐ Drug Equipment Violations, 39C ‐ Gambling Equipment Violations, 370 ‐ Pornography/Obscene Material, 520 ‐ Weapon Law Violations, and 720 – Animal Cruelty. Note: Gang Information is entered in a separate field in Tennessee and by statute, any offense can be gang related.

Suggested action: An invalid entry was made in the Criminal Activity Field. Refer to the information above and correct the issue. The field number should be displayed or the message will be specific to indicate which field contains invalid data.


36

Tennessee FBI Description Error Error Number Number 219.2 219 Type of Criminal Activity not allowed

Type Criminal Activity field can only be entered when the UCR offense code is: 250 ‐ Counterfeiting/Forgery, 280 ‐ Stolen Property Offense, 35A ‐ Drug/Narcotic Violations, 35B ‐ Drug Equipment Violations, 39C ‐ Gambling Equipment Violations, 370 ‐ Pornography/Obscene Material, 520 ‐ Weapon Law Violations, and 720 – Animal Cruelty. Note: Gang Information is entered in a separate field in Tennessee and by statute, any offense can be gang related.

Suggested action: An invalid entry was made in the Criminal Activity Field. Refer to the information above and correct the issue. The field number should be displayed or the message will be specific to indicate which field contains invalid data.

219.3 219 Type Weapon entry required

Type Weapon/Force Involved can only be entered when the UCR Offense Code is: 09A ‐ Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, 09D – Negligent Vehicular Manslaughter, 100 ‐ Kidnapping/Abduction, 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault with an Object, 11D ‐ Fondling, 120 ‐ Robbery, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 210 ‐ Extortion, 520 ‐ Weapon Law Violations, 64A – Commercial Sex Acts, and 64B – Involuntary Servitude.

Suggested action: An invalid entry was made in the Type Weapon Field. Refer to the information above and correct the issue. The field number should be displayed or the message will be specific to indicate which field contains invalid data.

219.4 219 Type Weapon entry not allowed

Type Weapon/Force Involved can only be entered when the UCR Offense Code is: 09A ‐ Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, 09D – Negligent Vehicular Manslaughter, 100 ‐ Kidnapping/Abduction, 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault with an Object, 11D ‐ Fondling, 120 ‐ Robbery, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 210 ‐ Extortion, 520 ‐ Weapon Law Violations, 64A – Commercial Sex Acts, and 64B – Involuntary Servitude.


37


Suggested action: An invalid entry was made in the Type Weapon Field. Refer to the information above and correct the issue. The field number should be displayed or the message will be specific to indicate which field contains invalid data.

251 251 Attempted/Completed must be 'A' or 'C'

Offense Attempted/Completed must be valid code of A or C.

Suggested action: Correct the entry in the Offense Attempted/Completed field to either A or C.

252.1 252 Number of Premises Entered cannot be '00'

The data in this field must be entered with two numeric characters ranging from 01 ‐ 99.

Suggested action: Enter data using two numeric characters, ranging from 01 ‐ 99 and resubmit the incident.

252.2 252 Number of Premises Entered allowed only for offense 220

Data in the Number of Premises field is only allowed for the offense of 220 ‐ Burglary.

Suggested action: Delete the data in the Number of Premises field or edit the Offense to 220 ‐ Burglary and resubmit the incident.

252.3 252 Location Type must be 14 or 19

Data can only be entered into the Number of Premises field when the location is 14 ‐ Hotel/Motel/etc. or 19 ‐ Rental Storage Facility and the Offense is Burglary (220).

Suggested action: Remove the entry from number of premises field or change location to Hotel/Motel/etc. or Rental Storage Facility and resubmit the incident.

253 253 Entry Method required for offense 220

Method of Entry field, (Force or No Force), was not entered; it must be entered when the offense is 220 ‐ Burglary.

Suggested action: Enter method of entry with the Burglary and resubmit the incident.


38

Tennessee FBI Description Error Error Number Number 254 254 Entry Method not allowed

Data may only be entered in the Method of Entry field for the offense of 220 – Burglary

Suggested action: Remove the entry from method of entry field or change the offense to Burglary.

255.1 255 Automatic Indicator must be A or blank

Type of Weapon/Force Involved, the third character must be A = Automatic or blank. In this case, a value other than these two was entered.

Suggested action: Incorrect data entered in Automatic Weapon indicator. Either enter "A" if automatic weapon or leave field blank. Resubmit the incident.







256 256 UCR Offense code requires Completed categorization

Offense Attempted/Completed must be Completed for Homicide or Assault offenses.

Suggested action: Change the data value to "C" and resubmit the incident.


39

Tennessee FBI Description Error Error Number Number 257 257 Number of Premises Entered required for UCR Offense = 220

and Location Type = 14 or 19

Number of Premises must be entered if offense is Burglary and Location Type is Hotel/Motel/etc. or Rental Storage Facility. Must be numeric entry 01 ‐ 99.

Suggested action: Enter a correct value in the "number of premises" field or change location from Hotel/Motel/etc. or Rental Storage Facility to another location type (if location entered incorrectly) and resubmit the incident.

258.1 258 Automatic Indicator invalid for Weapon entered

With type of Weapon/Force Involved, an "A” can only be used in the third position if the weapon is one of the following: 11 ‐ Firearm (type not stated), 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, and 15 ‐ Other Firearm. A weapon code other than those mentioned was entered with the automatic indicator to generate this error. An automatic weapon is by definition a firearm.

Suggested action: Remove the entry from "automatic weapon indicator" field or change the weapon type to one of the firearm types listed above and resubmit the incident.


With type of Weapon/Force Involved, an "A” can only be used in the third position if the weapon is one of the following: 11 ‐ Firearm (type not stated), 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, and 15 ‐ Other Firearm. A weapon code other than those mentioned was entered with the automatic indicator to generate this error. An automatic weapon is by definition a firearm.




40

Tennessee FBI Description Error Error Number Number With type of Weapon/Force Involved, an "A” can only be used

in the third position if the weapon is one of the following: 11 ‐ Firearm (type not stated), 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, and 15 ‐ Other Firearm. A weapon code other than those mentioned was entered with the automatic indicator to generate this error. An automatic weapon is by definition a firearm.


262 262 Two or more offenses with the same UCR Code cannot be submitted in the same Incident

When a Group A Incident Report is submitted, the individual segments comprising the incident cannot contain duplicates. In this case, two Offense segments were submitted with the same offense in the UCR offense code field.

Suggested action: Delete the duplicate offense(s) or change offense code(s) to other offenses if valid for the incident and resubmit.

263 263 No more than 10 offenses allowed

A Group A Incident Report was submitted with more than 10 offense segments. The maximum number allowed is ten (10).

Suggested action: Review the total offenses in the incident and report the 10 most serious. Delete any other offenses above 10 offenses.

264 264 Must be a Group A offense

Only Group A offenses can be submitted in the UCR Offense Code field in a Group A Incident.

Suggested action: Change the offense code to a valid Group A Offense code or if the offense was Group B Arrest, delete the Group A Offense and enter a Group B Arrest.

265.1 265 Invalid Weapon entry for UCR Offense 13B


41

Tennessee FBI Description Error Error Number Number An Offense segment was submitted for a Simple Assault. The

Type Weapon/Force Involved can be Personal Weapon, Other, or Unknown. All other weapons are invalid because they do not relate to a Simple Assault.

Suggested action: Change the weapon used in the offense to a valid entry with Simple Assault or edit the offense to a valid offense with the weapon type ‐ based upon the circumstances of the incident. NOTE: TIBRS does not allow the Weapon Type of None for a Simple Assault.


An Offense segment was submitted for a Simple Assault. The Type Weapon/Force Involved can be Personal Weapon, Other, or Unknown. All other weapons are invalid because they do not relate to a Simple Assault.



An Offense segment was submitted for a Simple Assault. The Type Weapon/Force Involved can be Personal Weapon, Other, or Unknown. All other weapons are invalid because they do not relate to a Simple Assault.


266 266 When an offense of 09C is submitted no other offenses can exist in the Incident

When a Justifiable Homicide is reported, no other offense can be reported in the Group A Incident Report. Any other offenses occurring should be submitted on a separate Group A Incident Report.

Suggested action: Delete the 09C ‐ Justifiable Homicide from the incident and enter the 09C as a separate incident.


42

Tennessee FBI Description Error Error Number Number 267 267 Invalid Weapon entry for homicide

Homicide offenses must have a Weapon Type other than None. Some Type of Weapon/Force must be used in a Homicide.

Suggested action: Enter a valid weapon code used in the offense segment. Homicide offenses must have a weapon entered.

268 268 Single Larceny Offense cannot have Property Description of Motor Vehicle (i.e. 03, 05, 24, 28, 37, 87)

Stolen vehicles cannot be reported under Larceny/Theft offenses. Analysis will be necessary to determine the correction needed. A data entry error may have been made resulting in the vehicle code being entered by mistake, or maybe a second property offense should be submitted that logically allows for stolen vehicles.

Suggested action: Edit the offense to a valid offense that can contain a motor vehicle or edit the property category. The action will be based upon the incident circumstances.

269 269 Possible Classification error, 13A as 13B

A Simple Assault was submitted but the Type Weapon/Force Involved field has a weapon code reflecting Aggravated Assault. The wrong weapon code may have been entered or the wrong offense code was entered.

Suggested action: Based upon the incident circumstances, either change the weapon code or the offense code and resubmit the incident.

270 270 Justifiable Homicide must be coded as Non‐Bias Motivated

A Justifiable Homicide was submitted but the Bias Motivated field has a bias code reflecting a bias other than None. The offense of Justifiable Homicide must be submitted with a bias of None.

Suggested action: Based upon the incident offense, either change the bias motivated code to None or edit the offense code and resubmit the incident.


43


TENNESSEE SPECIFIC OFFENSE SEGMENT ERRORS

MP_09A.1 NULL With offenses 09A‐D type weapon is required

Entry for Weapon Type is a required element for the following offenses: 09A ‐Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, and 09D ‐Negligent Vehicular Manslaughter.


MP_09A.2 NULL With offenses 09A – 09D attempted/completed must be C

Entry for Attempted/Completed must always be Completed for the offenses of: 09A ‐ Murder, Non‐negligent Manslaughter, 09B – Negligent Manslaughter, 09C ‐ Justifiable Homicide, and 09D – Negligent Vehicular Manslaughter.

Suggested action: Edit Attempted/Completed to Completed or edit Offense and resubmit the incident.

MP_09B.1 NULL With offenses 09A‐D type weapon is required

Entry for Weapon Type is a required element for the following offenses: 09A ‐ Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, and 09D – Negligent Vehicular Manslaughter.


MP_09B.2 NULL With offenses 09A – 09D attempted/completed must be C



MP_09C.1 NULL With offenses 09A‐D type weapon is required

Entry for Weapon Type is a required element for the following offenses: 09A ‐ Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, and 09D – Negligent Vehicular Manslaughter..


44

Tennessee FBI Description Error Error Number Number Suggested action: Enter a valid Weapon Type code and

resubmit the incident.

MP_09C.2 NULL With offenses 09A – 09D attempted/completed must be C



MP_09D.1 NULL With offenses 09A‐D type weapon is required

Entry for Weapon Type is a required element for the following offenses: 09A ‐ Murder, Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, and 09D – Negligent Vehicular Manslaughter..


MP_09D.2 NULL With offenses 09A – 09D attempted/completed must be C



MP_100.4 NULL With offense 100 type weapon is required

Entry for Weapon Type is a required element for the offense of Kidnapping/Abduction.


MP_11A.1 NULL With offenses 11A‐D type weapon is required

Entry for Weapon Type is a required element for the offenses of: 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object, and 11D ‐ Fondling.



45

Tennessee FBI Description Error Error Number Number MP_11B.1 NULL With offenses 11A‐D type weapon is required



MP_11C.1 NULL With offenses 11A‐D type weapon is required



MP_11D.1 NULL With offenses 11A‐D type weapon is required



MP_13A.1 NULL With offenses 13A and 13B type weapon is required

Entry for Weapon Type is a required element for the offenses of Aggravated Assault and Simple Assault.


MP_13A.2 NULL With offenses 13A‐D attempted/completed must be C

Entry for Attempted/Completed must always be Completed for the offenses of: 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation, and 13D ‐ Stalking.



46

Tennessee FBI Description Error Error Number Number MP_13B.1 NULL With offenses 13A and 13B type weapon is required

Entry for Weapon Type is a required element for the offenses of Aggravated Assault and Simple Assault.


MP_13B.2 NULL With offenses 13A‐D attempted/completed must be C



MP_13C.2 NULL With offenses 13A‐D attempted/completed must be C



MP_13D.2 NULL With offenses 13A‐D attempted/completed must be C



MP_210.4 NULL With offense 210 type weapon is required

Entry for Weapon Type is a required element for the offense of 210 ‐ Extortion/Blackmail.



47

Tennessee FBI Description Error Error Number Number MP_220.4 NULL With offense 220, entry method is required

Method of Entry field, (Force or No Force), was not entered; it must be entered when the offense is 220 ‐ Burglary.

Suggested action: Enter method of entry with the Burglary and resubmit the incident.

MP_220.5 NULL With offense 220, number of premises entered is required

With an Offense of 220 ‐ Burglary and the Location of either Hotel/Motel/Etc. or Rental Storage Facility, the Number of Premises field must contain data.

Suggested action: Enter the Number of Premises entered with numeric data ranging from 01 ‐ 99, edit the Offense, or edit the Location for the incident. Resubmit the incident.

MP_250.4 NULL With offense 250 type activity is required

Entry for Type Criminal Activity is required for the offense of 250 ‐ Counterfeiting/Forgery.

Suggested action: Enter the Type Criminal Activity or edit the offense. Resubmit the incident.


Entry for Type Criminal Activity is required for the offense of 280 ‐ Stolen Property Offenses.



Entry for Type Criminal Activity is required for the offense of 370 ‐ Pornography/Obscene Material.


MP_39C.4 NULL With offense 39C type activity is required

Entry for Type Criminal Activity is required for the offense of 39C ‐ Gambling Equipment Violations.



48

Tennessee FBI Description Error Error Number Number MP_520.1 NULL With offense 520 type weapon is required

Entry for Weapon Type is a required element for the offense of 520 ‐ Weapon Law Violations.



Entry for Type Criminal Activity is required for the offense of 520 ‐ Weapon Law Violations.



Entry for Type Criminal Activity is required for the offense of 720 ‐ Animal Cruelty. Valid codes for the offense are: A – Simple/Gross Neglect, F – Organized Abuse, I – Intentional Abuse and Torture, or S – Animal Sexual Abuse.


TN_201.2 Data element not allowed with Gang Activity of N=No Gangs

If No Gang Activity is selected, all gang fields must be blank.

Suggested action: Edit Gang Activity field to a selection other than "No Gang Activity" or remove the data from the other gang fields.

TN_201.4 Home Invasion is required when Offense code = 120 and Location Code = 20

An entry is required in the Home Invasion field if the location code is 20 ‐ Residence/Home and the offense is 120 ‐ Robbery.

Suggested action: Based on incident circumstances, either enter a code for the Home Invasion field, change the location or change the offense classification and resubmit.


49


TN_201.5 Home Invasion required when Offense Code = 220, Location

Code = 20 , Additional Offense = (11A‐11D, 13A‐13C, 09A, 100 and 120)

An entry is required in the Home Invasion field if the location code is 20 ‐ Residence/Home and the offense is 220 ‐ Burglary and one of the following offenses also occurs in the incident: 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault with an Object, 11D ‐ Fondling, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation, 09A ‐ Murder/Nonnegligent Manslaughter, 100 – Kidnapping, and 120 ‐ Robbery.

Suggested action: Based on incident circumstances, either enter a code for the Home Invasion field, change the location or change the offense classification(s) and resubmit.

TN_204.1 Invalid Data Value – Entry for Gang Activity must be J, O, B, or N

Enter valid code for Gang Activity.

Suggested action: change the Gang Activity Code to a valid code.

TN_204.2 Invalid Data Value ‐ Gang Type must be T, O, S, R, C or M

Enter valid code for Gang Type.

Suggested action: Change the Type of Gang Code to a valid code.

TN_204.3 Home Invasion must be Y or N when entered

Enter valid code for Home Invasion ‐ Yes or No. Mandatory when location is Residence/Home and offense is 120 ‐ Robbery or when location is Residence/Home, one offense is 220 ‐ Burglary and second offense is one of the following: 11A ‐ 11D, 13A, 13B, 13C, 09A, 100. Otherwise, field must be blank.

Suggested action: Based on incident circumstances, either enter Y or N if the above conditions exist or leave field blank.


50

Tennessee FBI Description Error Error Number Number TN_204.31 Home Invasion entry not allowed

Home Invasion entry is only allowed, when location is Residence/Home and offense is 120 ‐ Robbery or when location is Residence/Home, one offense is 220 ‐ Burglary and second offense is one of the following: 11A ‐ 11D, 13A, 13B, 13C, 09A, 100. Offense(s) submitted do not meet the criteria for Home Invasion.

Suggested action: Edit the offense(s) submitted to valid offense type or remove data from Home Invasion field.

TN_204.5 Drug Related must be Y or N

Enter valid code for Drug Related ‐ mandatory entry.

Suggested action: Change the Drug Related Code to a valid code.

TN_204.6 Entry for Drug Type is invalid

Enter valid code for Drug Type. Valid codes are: 01 ‐ Crack Cocaine, 02 ‐ Powder Cocaine, 03 ‐ Methamphetamine, 04 ‐ Processed Marijuana, 05 ‐ Cultivated Marijuana, 06 ‐ Ecstasy, 07 ‐ GHB, 08 ‐ Ketamine, 09 ‐ Heroin, 10 ‐ Oxycodone, 11 ‐ Hydrocodone, 12 ‐ Other Prescription Drug, and 13 ‐ Other Non‐Prescription Drug.

Suggested action: Enter one of the codes above for the Drug Type.

TN_204.7 Entry for Drug Origin is invalid

Enter valid code for Drug Origin. Valid codes are: 01 ‐ Clandestine Lab, 02 ‐ Diverted Prescription Drug, 03 ‐ Illegally Imported, 04 ‐ Indoor Marijuana Growth, and 05 ‐ Outdoor Marijuana Growth.

Suggested action: Based on incident circumstances, enter valid code for Drug Origin from list above.


51

Tennessee FBI Description Error Error Number Number TN_204.8 Entry for Drug type, origin, or precursor is invalid

Enter valid code for Precursors if Drug Origin is Clandestine Lab (01) and Drug Type is Methamphetamine (03). Valid codes are: 01 ‐ Single entity tablet/capsule, 02 ‐ Combination tablet/capsule, 03 ‐ Gelcap, 04 ‐ Liquid, and 05 ‐ Unknown/not present.

Suggested action: Based on incident circumstances, enter valid code for Drug Precursor from list above.

TN_204.9 Gang Name is required when gang activity = J, O, or B

Entry of Gang Name is required when Gang Activity is one of the following: J ‐ Juvenile Gang, O ‐ Other Gang, and B ‐ Juvenile and Other.

Suggested action: Enter the name of the gang in the Gang Name field or remove data from the Gang Activity field.

TN_204.10 Entry for Drug Related must be Y ‐ Yes when offense code = 35A

Entry for Drug Related must be Y ‐ Yes when the offense code is 35A ‐ Drug/Narcotic Violations.

Suggested action: Edit the Drug Related code to Y ‐ Yes or edit the offense.

TN_205.2 Entry for Drug Type is required

Entry for Drug Type is a required element and should be one of the following valid codes: 01 ‐ Crack Cocaine, 02 ‐ Powder Cocaine, 03 ‐ Methamphetamine, 04 ‐ Processed Marijuana, 05 ‐ Cultivated Marijuana, 06 ‐ Ecstasy, 07 ‐ GHB, 08 ‐ Ketamine, 09 ‐ Heroin, 10 ‐ Oxycodone, 11 ‐ Hydrocodone, 12 ‐ Other Prescription Drug, and 13 ‐ Other Non‐Prescription Drug.



52

Tennessee FBI Description Error Error Number Number TN_205.5 Drug precursor is required

Enter valid code for Precursors if Drug Origin is Clandestine Lab (01) and Drug Type is Methamphetamine (03). Valid codes are: 01 ‐ Single entity tablet/capsule, 02 ‐ Combination tablet/capsule, 03 ‐ Gelcap, 04 ‐ Liquid, and 05 ‐ Unknown/not present.

Suggested action: Based upon the incident circumstances, enter a valid code for the Drug Precursor.

TN_206.1 Identity Theft Flag must be Y or N for this offense

Must enter either a Y ‐ Yes or N ‐ No if the Incident Offense is one of the following: 120 ‐ Robbery, 220 ‐ Burglary, 250 ‐ Counterfeiting/Forgery, 270 ‐ Embezzlement, 26A ‐ Fraud, False Pretenses/Swindle/Con, 26B ‐ Credit Card/ATM Fraud, 26C ‐ Fraud ‐ Impersonation, 26D ‐ Welfare Fraud, 26E ‐ Wire Fraud, 26F – Identity Theft, 26G – Computer Hacking/Invasion, 23A ‐ Pocket Picking, 23B ‐ Purse Snatching, 23D ‐ Theft From a Building, 23F ‐ Theft From a Motor Vehicle, 23G ‐ Theft of Vehicle Parts/Accessories, 23H ‐ All Other Larceny, 240 ‐ Motor Vehicle Theft, 210 ‐ Extortion/Blackmail, or Attempted 510 ‐ Bribery.

Suggested action: If the Incident offense is one of the ones requiring an Identity Theft Flag, an entry in the Identity Theft Flag of Y or N must be made.

TN_206.2 Identity Theft Flag must be blank for this offense

The Incident Offense is not a valid offense that requires an entry in the Identity Theft Flag.

Suggested action: Delete the entry in the Identity Theft Flag field or edit the Incident Offense.

TN_206.3 Identity Theft offense must have Identity Theft Flag reported as “Y”

The Identity Theft Flag must be reported as “Y” – Yes for this offense. It cannot be “N”.

Suggested action: Edit the entry in the Identity Theft Flag field to “Y”‐ Yes or edit the Incident Offense.


53

Tennessee FBI Description Error Error Number Number TN_206.4 Identity Theft Offense must be reported with additional

offense(s) in the incident

If the offense of Identity Theft is reported, there must be at least one additional offense from the following: 120, 220, 250, 270, 26A – E, 26G, 23A, 23B, 23D, 23F, 23G, 23H, 240, 210, or attempted 510.

Suggested action: Add the additional offense(s) to the incident or edit the Incident Offense.

TN_206.5 Additional offense for Identity Theft must also have the Identity Theft Flag reported as “Y”

If the offense of Identity Theft is reported, there must be at least one additional offense from the following: 120, 220, 250, 270, 26A – E, 26G, 23A, 23B, 23D, 23F, 23G, 23H, 240, 210, or attempted 510. This offense must also have the Identity Theft Flag reported as “Y” – Yes.

Suggested action: Edit the Identity Theft Flag to “Y” – Yes for the reported offense or edit the Incident Offense(s).

TN_207 Justifiable Homicide Offenses with Arrests or Exceptional Clearance.

The offense of Justifiable Homicide was submitted with a clearance. For TIBRS reporting, a Justifiable Homicide cannot be cleared.

Suggested action: Remove the clearance or edit the offense submitted in the Offense segment and resubmit the incident.

TN_208 Simple Assault without a weapon and Minor Injuries

The offense of Simple Assault was submitted with the Victim suffering Minor Injuries; however, no Weapon Type was submitted.

Suggested action: Enter a valid Weapon Type and resubmit the incident.

TN_209 Cyberspace may not be reported as the first Location Code

An entry of the location code of 58 – Cyberspace may not be reported as the first Location Code in an incident.


54

Tennessee FBI Description Error Error Number Number Suggested action: Edit the location code entered in the first

location code and resubmit the incident.

TN_209.1 Cyberspace cannot be the only Location Code reported

The Location Code of 58 – Cyberspace cannot be the only location code reported for an Incident.

Suggested action: Edit the location code entered and resubmit the incident. The location code of 58 – Cyberspace may only be reported as the second Location Code.

TN_210 Offender Suspected of Using must have Drugs and/or Alcohol indicated

For the offense of 09D – Negligent Vehicular Manslaughter, you must report the Offender Suspected of Using Drugs and/or Alcohol. It is required.

Suggested action: Enter the Offender Suspected of Using Drugs and/or Alcohol and resubmit the incident.

TN_210.1 Offense Weapon Type can only be Motor Vehicle

The only weapon type that can be reported for the offense 09D – Negligent Vehicular Manslaughter is 35 – Motor Vehicle.

Suggested action: Edit the Offense Weapon to Motor Vehicle and resubmit the incident or edit the Incident Offense.

PROPERTY SEGMENT ERRORS


The ORI number was not included in the property segment. It is required.



The Incident Number was not included in the property segment. It is required.


55

Tennessee FBI Description Error Error Number Number Suggested action: Enter the Incident Number and resubmit

the incident.

301.3 301 Type Property Loss entry is missing

Enter a valid code for Type Property Loss. Valid codes are: 1 ‐ None, 2 ‐ Burned, 3 ‐ Counterfeited/Forged, 4 ‐ Damaged/Destroyed/Vandalized, 5 ‐ Recovered, 6 ‐ Seized, 7 ‐ Stolen, and 8 ‐ Unknown.

Suggested action: Based upon the incident circumstances, enter a valid code for the Type Property Loss.

302.1 302 Property Value entry is non‐numeric

Report the total dollar Property Value of the property burned, stolen, destroyed, etc., as a result of the incident. Property Value should be reported in whole dollar amounts only. Value should be entered using only numeric characters 0 ‐ 9.

Suggested action: Enter the Property Value using numeric digits 0 ‐ 9 and resubmit the incident.

302.2 302 Number of Stolen Vehicles entry non‐numeric

If Type Property Loss is 7 ‐ Stolen and the Property Description is one of the following: 03 ‐ Automobile, 05 ‐ Buses, 24 ‐ Other Motor Vehicle, 28 ‐ Recreational Vehicle, 37 ‐ Trucks, or 87 – Van (MV Type), enter the number of known stolen vehicles using two numeric digits ‐ 01 ‐ 99. If the number stolen is unknown, enter the Number of Stolen Vehicles as 00 ‐ Unknown.

Suggested action: Enter the Number of Stolen Vehicles using numeric digits 01 ‐ 99 or 00 if Unknown and resubmit the incident.

302.3 302 Number of Recovered Vehicles entry non‐numeric

If Type Property Loss is 5 ‐ Recovered and the Property Description is one of the following: 03 ‐ Automobile, 05 ‐ Buses, 24 ‐ Other Motor Vehicle, 28 ‐ Recreational Vehicle, 37 ‐ Trucks, or 87 – Van (MV Type), enter the number of known recovered vehicles using two numeric digits ‐ 01 ‐ 99. If the number recovered is unknown, enter the Number of Recovered Vehicles as 00 ‐ Unknown.


56

Tennessee FBI Description Error Error Number Number Suggested action: Enter the Number of Recovered Vehicles

using numeric digits 01 ‐ 99 or 00 if Unknown and resubmit the incident.

302.4 302 Suspected Drug Quantity entry non‐numeric

Must be numeric entry with zero left fill. Any decimal or fractional quantity must be rounded to thousandths as three numeric digits. If no fractional quantity was involved, then all zeroes should be entered.

Suggested action: Enter the Suspected Drug Quantity using numeric digits and resubmit the incident.

304.2 304 Invalid Type Property Loss entry

Type Property Loss entry is invalid code. Valid codes are: 1 ‐ None, 2 ‐ Burned, 3 ‐ Counterfeited/Forged, 4 ‐ Damaged/Destroyed/Vandalized, 5 ‐ Recovered, 6 ‐ Seized, 7 ‐ Stolen, and 8 ‐ Unknown.

Suggested action: Enter the Type Property Loss using valid code and resubmit the incident.

304.3 304 Invalid Property Description

Valid Codes are: 01 ‐ 39, 41 – 51, 59, 64 – 87, 88, 89 and 99. Refer to the TIBRS Data Collection Manual for a complete listing of Property Descriptions.

Suggested action: Based upon the incident circumstances, enter a valid Property Description and resubmit the incident.

304.4 304 Suspected Drug Type entry invalid

Entry for Drug Type is a required element and should be one of the following valid codes: 01 ‐ Crack Cocaine, 02 ‐ Powder Cocaine, 03 ‐ Methamphetamine, 04 ‐ Processed Marijuana, 05 ‐ Cultivated Marijuana, 06 ‐ Ecstasy, 07 ‐ GHB, 08 ‐ Ketamine, 09 ‐ Heroin, 10 ‐ Oxycodone, 11 ‐ Hydrocodone, 12 ‐ Other Prescription Drug, and 13 ‐ Other Non‐Prescription Drug.



57

Tennessee FBI Description Error Error Number Number 304.5 304 Suspected Drug Measure entry invalid

Entry for Suspected Drug Measure is a required element and should be one of the following valid codes: GM ‐ Gram, KG ‐ Kilogram, OZ ‐ Ounce, LB ‐ Pound, DU ‐ Dosage Unit, ML ‐ Milliliter, LT ‐ Liter, FO ‐ Fluid Ounce, GL ‐ Gallon, NP ‐ Number of Plants, and XX ‐ Not Reported (Not Reported is a temporary, interim report and must be replaced with true value).

Suggested action: Based upon the incident circumstances, enter a valid Suspected Drug Measure and resubmit the incident.

305.1 305 Date entered is not a valid date, must be valid calendar date

Date entered is not a valid date. Must be valid calendar date. Months must be between 01 ‐ 12, Days must be between 01 ‐ 31, and year must be four digits. Days cannot exceed maximum for the month ‐ June cannot have 31 days. The date cannot be earlier than the Incident Date. The date cannot be later than that entered within the Month of Tape and Year of Tape fields.

Suggested action: Enter the correct date information and resubmit the incident.

305.12 305 Recovered Date is invalid ‐ YEAR

Date recovered year must be four numeric digits and cannot be later than that entered in the Year of Tape fields.

Suggested action: Enter the correct Recovered Date ‐ Year and resubmit the incident.

305.2 305 Recovered Date is invalid ‐ MONTH

Date recovered month must be two numeric digits and cannot be later than that entered in the Month of Tape fields. Months must be between 01 ‐ 12.

Suggested action: Based upon the incident circumstances, enter a valid Recovered date month and resubmit the incident.


58

Tennessee FBI Description Error Error Number Number 305.3 305 Recovered Date cannot precede Incident Date

The Recovered Date cannot be earlier than the Incident Date/Hour.


305.4 305 Recovered Date cannot postdate Current Date

The Recovered Date cannot be later than that entered within the Month of Tape and Year of Tape fields.

Suggested action: Based upon the incident circumstances, enter a valid Recovered Date and resubmit the incident.

305.5 305 Recovered Date non‐numeric

Recovered Date entered using non numeric characters. Months must be between 01 ‐12, Days must be between 01 ‐ 31, and year must be four digits.

Suggested action: Enter a Recovered Date and resubmit the incident.

306.1 306 Duplicate Property Description

The data element Property Description contains multiple values. When more than one code is entered, none can be duplicated.

Suggested action: Review the Property Descriptions entered and remove the duplicate description. Resubmit the incident.

306.2 306 Duplicate Suspected Drug Type

If more than one code is entered in Suspected Drug Type, the same code cannot be duplicated in the incident.

Suggested action: Review the Suspected Drug Type and either delete the duplicate code or edit the code to another valid code. Resubmit the incident.

306.3 306 Duplicate Suspected Measure

If more than one code is entered in Suspected Measure, the same code cannot be duplicated in the incident.


59

Tennessee FBI Description Error Error Number Number Suggested action: Review the Suspected Measure and either

delete the duplicate code or edit the code to another valid code. Resubmit the incident.




316 316 Incident Number must be left justified






320 320 Recovered Date before Base Date

The Recovered Date submitted is earlier than January 1 of the previous year or before the agency converted to NIBRS/TIBRS.



60

Tennessee FBI Description Error Error Number Number 342 342 Property Value exceeds 1,000,000

This is a warning message only. The property value contains a value that is greater than 1,000,000. The submitting agency should check to see if the value entered is a data entry error or if the value is correct.

Suggested action: Review the property and value and correct if necessary. If the original value is correct, please notify CSC.

343 343 For offenses of 240 and 280 the vehicles involved must be reported as both Stolen and Recovered

This is a warning message only. This warning is generated when a Stolen Property offense and a Motor Vehicle Theft are submitted that contain questionable property reporting. When an incident contains a recovered vehicle but does not contain a stolen vehicle, this message is generated.

Suggested action: The incident should be reviewed and if there was indeed a stolen vehicle, the incident should be resubmitted reflecting both stolen and recovered vehicles. NOTE: If the vehicle was reported stolen by another jurisdiction, then that agency must report the recovery.

351 351 Property Value cannot be 0

Value of property has a value of zero but the Property Description entered cannot have zero for the value. If the value is unknown, enter a value of $1; otherwise, enter the property value. Property value of zero is mandatory for the following categories: Credit/Debit Cards, Nonnegotiable Instruments, Documents ‐ Personal or Business, Identity Documents, and Identity ‐ Intangible. Property value of zero is optional for the following categories: Other, and Special. Category of Special to be used only when instructed by TBI.

Suggested action: Based upon the incident circumstances, either enter correct value for property in the incident or change property classification.


61

Tennessee FBI Description Error Error Number Number 352 Data elements 15‐22 must be blank when property loss code

= 1 or 8

When this error occurs, one or more data elements were found in the referenced fields. These data elements must be blank if the property loss code is None or Unknown. Example: if property loss is unknown, all data elements involving Property ‐ description, value, and date recovered must be blank. If it is None and the offense is a Drug/Narcotic Violations, then all referenced fields but Suspect Drug Type must be blank.

Suggested action: Delete property description and value or change the type property loss and resubmit.

352.1 352 When Type Property Loss = 8: Property Description, Value, Date Recovered and Drug fields must be blank



352.2 352 With Suspected Drug Type entry Type Property Loss must be 1

When data is entered in the Suspected Drug Type field and not in the Quantity or Measure field, then the Loss Type must be 1 = None.

Suggested action: Delete Quantity and Measure or change the type property loss and resubmit.


62

Tennessee FBI Description Error Error Number Number 352.3 352 When Type Property Loss = 1: Property Description, Value,

Date Recovered and Drug fields must be blank



353 353 Pending Inventory entry must have Property Value of 1

If the Property Description entered is "Pending Inventory", then the property value must be 1.

Suggested action: Based upon the circumstances, either change the value to 1 or change the property description.

354 354 Property Value not valid without Property Description

If a Property Description was not entered, the property value cannot contain a value.

Suggested action: Based upon incident circumstances, either enter a property description or delete the property value and resubmit.

355 355 Recovered Date not allowed without Type Property Loss of 5

Type Property Loss field must be 5 = Recovered for a Recovered Date to be entered.

Suggested action: Based upon incident circumstances, either remove the recovered date entry or change loss type to "Recovered".


63

Tennessee FBI Description Error Error Number Number 356 356 Recovered Date not allowed without Property Description

and Value

Date recovered was entered but Property Description and Property Value were not entered.

Suggested action: Based upon incident circumstances, either remove the recovered date entry or enter property description and value.

357 357 Number of Stolen Vehicles is valid only with Property Loss = 7 and offense of 240

Number of stolen vehicles was entered. However, the Type Property Loss field was not entered, or Motor Vehicle Theft offense was not entered, or the Motor Vehicle offense was Attempted. To report number of stolen vehicles, the Motor Vehicle Theft offense must be Completed.

Suggested action: Based upon incident circumstances, remove the entry from "Number of Stolen Vehicles" field or enter the Type Property Loss and/or enter a Completed Motor Vehicle Theft offense.

358 358 Number of Stolen Vehicles is required with Property Loss = 7 and offense of 240

Entry must be made in the Number of Stolen Vehicles field when the offense is Motor Vehicle Theft, the offense is Completed and the Type Property Loss is 7 = Stolen.

Suggested action: Enter data into the "Number of Stolen Vehicles" field.

359.1 359 Number of Stolen Vehicles entry not allowed

When the Number of Stolen Vehicles is entered and is 01 ‐ 99, the Property Description must be one of the following: 03 ‐ Automobile, 05 ‐ Bus, 24 ‐ Other Motor Vehicle, 28 ‐ Recreational Vehicle, 37 – Trucks, or 87 – Van (MV Type).

Suggested action: Based upon incident circumstances, remove entry from "Number of Stolen Vehicles" field, or change Property Description to one of the above types of Motor Vehicles.


64

Tennessee FBI Description Error Error Number Number 359.2 359 Number of Recovered Vehicles entry not allowed

When the Number of Recovered Vehicles is entered and is 01 ‐ 99, the Property Description must be one of the following: 03 ‐ Automobile, 05 ‐ Bus, 24 ‐ Other Motor Vehicle, 28 ‐ Recreational Vehicle, 37 – Trucks, or 87 – Van (MV Type).

Suggested action: Based upon incident circumstances, remove entry from "Number of Recovered Vehicles" field, or change Property Description to one of the above types of Motor Vehicles.

360 360 Number of Recovered Vehicles entry not allowed

The Number of Recovered Motor Vehicles was entered. However, the Type Property Loss of 5 = Recovered was not entered and/or the offense of Motor Vehicle Theft was not entered, and/or the offense was Attempted.

Suggested action: Based upon incident circumstances, either remove the entry from "Number of Recovered Motor Vehicles" field, or change the loss type to "Recovered", and/or change the offense to Completed Motor Vehicle Theft.

361 361 Number of Recovered Vehicles entry required with Property Loss = 5 and offense of 240

Entry must be made for the Number of Recovered Vehicles when the offense is Motor Vehicle Theft, Completed and the Type Property Loss is 5 ‐ Recovered.

Suggested action: Based upon incident circumstances, enter Number of Recovered Vehicles, or change offense from Completed Motor Vehicle Theft, or change Property Loss type from "Recovered".

362 362 Suspected Drug Type of 'X' must requires 2 previous entries

Since the Suspected Drug Type field contains an "X" (over three (3) Drug Types present), two other drug codes must be present.

Suggested action: Based upon incident circumstances, either edit the drug type choice to something other than "X" or enter two other drug types in the property segment.


65

Tennessee FBI Description Error Error Number Number 363.1 363 Suspected Drug Type 'X' cannot have a Quantity or Measure

associated with it

Since the Suspected Drug Type field contains an "X", the Quantity and Measurement fields must be blank for the Drug Type "X".

Suggested action: Based upon incident circumstances, either change the drug type field to something other than "X”: or remove the entries in "quantity" and "measurement".

363.2 363 Suspected Drug Type 'X' cannot have a Quantity or Measure associated with it



363.3 363 Suspected Drug Type 'X' cannot have a Quantity or Measure associated with it



364.1 364 Suspected Drug Quantity entry missing

When the offense is Drug/Narcotic Violations, the Type Property Loss is Seized, the Property Description is Drugs, and the Suspected Drug Type is entered, the Estimated Quantity and Measurement must also be entered.

Suggested action: Enter the values in the "quantity" and "measurement" fields.


66

Tennessee FBI Description Error Error Number Number 364.2 364 Suspected Drug Measure entry missing

When the offense is Drug/Narcotic Violations, the Type Property Loss is Seized, the Property Description is Drugs, and the Suspected Drug Type is entered, the Estimated Quantity and Measurement must also be entered.

Suggested action: Enter the values in the "quantity" and "measurement" fields.

365.1 365 Suspected Drug Type entered without Property Type 6

The Suspected Drug Type was entered but one or more required fields were not entered. The offense must be Drug/Narcotic Violations, the Type Property Loss must be 6 = Seized, and the Property Description must be Drugs/Narcotics. There could be multiple underlying reasons causing this error. One of them might be that the Suspected Drug Type was entered by mistake. Possibly, the Property Description should have been Aircraft (category 01) but the Property Description of Drugs/Narcotics (category 10) was entered instead and an entry was made in the Suspected Drug Type field in error.

Suggested action: Review the incident report to ensure accurate classification of the offense and if it is a Drug/Narcotic Violation, complete the information needed for Drug/Narcotic property including Property Loss, Description, and Drug Type, Quantity, and Measurement. If the offense is not a Drug/Narcotic Violation, change the offense code to the correct classification and enter data into required fields based on the offense.


67

Tennessee FBI Description Error Error Number Number 365.2 365 Suspected Drug Type entered without Property Description

10

The Suspected Drug Type was entered but one or more required fields were not entered. The offense must be Drug/Narcotic Violation, the Type Property Loss must be 6 = Seized, and the Property Description must be Drugs/Narcotics. There could be multiple underlying reasons causing this error. One of them might be that the Suspected Drug Type was entered by mistake. Possibly, the Property Description should have been Aircraft (category 01) but the Property Description of Drugs/Narcotics (category 10) was entered instead and an entry was made in the Suspected Drug Type field in error.

Suggested action: Review the incident report to ensure accurate classification of the offense and if it is a Drug/Narcotic Violation, complete the information needed for Drug Narcotics property including Property Loss, Description, and Drug Type, Quantity, and Measurement. If the offense is not a Drug/Narcotic Violation, change the offense code to the correct classification and enter data into required fields based on the offense.

365.3 365 Suspected Drug Type entered without offense 35A

The Suspected Drug Type was entered but one or more required fields were not entered. The offense must be Drug/Narcotic Violation, the Type Property Loss must be 6 = Seized, and the Property Description must be Drugs/Narcotics. There could be multiple underlying reasons causing this error. One of them might be that the Suspected Drug Type was entered by mistake. Possibly, the Property Description should have been Aircraft (category 01) but the Property Description of Drugs/Narcotics (category 10) was entered instead and an entry was made in the Suspected Drug Type field in error.

Suggested action: Review the incident report to ensure accurate classification of the offense and if it is a Drug/Narcotic Violation, complete the information needed for Drug Narcotics property including Property Loss, Description, and Drug Type, Quantity, and Measurement. If the offense is not a Drug/Narcotic Violation, change the offense code to the correct classification and enter data into required fields based on the offense.


68

Tennessee FBI Description Error Error Number Number 366.1 366 Suspected Drug Quantity with no Measure and/or Type

The Estimated Quantity was entered but Suspected Drug Type and/or Type Measurement were not entered. Both must be entered.

Suggested action: Enter Drug Type and Type Measurement and resubmit.

366.2 366 Suspected Drug Quantity with no Measure and/or Type



366.3 366 Suspected Drug Quantity with no Measure and/or Type



367 367 Drug Type Measure invalid, NP with no Type of 'E'

The Type Measurement was entered with Number of Plants (NP) in combination with an illogical Drug Type. Based upon the various ways a drug can be measured, very few edits can be done to check for illogical combinations of Drug Type and Measurement. The only restriction will be on NP ‐ Number of Plants ‐ to the following drugs: E = Marijuana, G = Opium, and K = Other Hallucinogens. All other Type Measurement codes are applicable to any Suspected Drug Type.

Suggested action: Based on drug type, either edit the drug type to one of the ones above and enter the quantity or change the measurement to the correct measurement type.

368.1 368 Drug Type is missing

The Type Measurement was entered, but Suspected Drug Type was not entered. Suspected Drug Type must be entered.


69

Tennessee FBI Description Error Error Number Number Suggested action: Enter the Suspected Drug Type and

resubmit.

368.2 368 Drug Quantity is missing

The Type Measurement was entered, but Estimated Quantity was not entered. Estimated Quantity must be entered.

Suggested action: Enter the Estimated Quantity and resubmit.

372 372 Property Type entry required

If the Type Property Loss is Burned, Counterfeited/Forged, Destroyed/Damaged/Vandalized, Recovered, Seized, or Stolen, then data elements 15 ‐ 22 must have applicable entries in the segment.

Suggested action: Enter property description, value, and any other applicable data fields relating to the property in the incident and resubmit.

375 375 Property Description entry required

At least one of the Property Description codes must be entered when the Type Property Loss contains Property segment(s) for: Burned, Counterfeited/Forged, Destroyed/Damaged/Vandalized, Recovered, Seized, or Stolen.

Suggested action: Enter the Property Description based on the incident circumstances.

376 376 Duplicate Property Segments are not allowed

When a Group A Incident Report is submitted, the individual segments comprising the incident cannot contain duplicates. In this case, two Property segments were submitted having the same entry in Type Property Loss field.

Suggested action: If the Loss Type is the same according to the incident report, include all property in one segment or change the property loss type.


70

Tennessee FBI Description Error Error Number Number 382 382 Type Property Description of 10 must accompany offense

35A

A Property segment was submitted with the Property Description of Drugs/Narcotics and the Value of Property containing blanks. In this situation, an offense of Drug/Narcotic Violations must be submitted. No such offense was submitted.

Suggested action: Based on incident circumstances, enter an additional offense of Drug/Narcotic Violations, edit the offense to another offense and make appropriate changes to property or change the property description type.

383 383 Property Value must be blank if 35A is the only offense in the Incident

The Value of Property has a value other than zero (0) entered. Since the Property Description code is Drugs/Narcotics and the only Crime Against Society offense submitted is Drug/Narcotic Violations, the Value of Property field must be blank.

Suggested action: Based on incident circumstances, either change the property description to one that needs a value or delete the value entered for drugs.

384 384 With an unknown Suspected Drug Measure 'XX', Quantity must = 1

The Estimated Quantity field does not have a value of 1 when XX = Not Reported was entered for the Type Measurement. Submission of a Not Reported indication requires that a value of 1 also be submitted as a quality assurance check. Once the Type Measurement has been determined, a Group A Incident Report with this information should be resubmitted.

Suggested action: Based on incident circumstances, change the value in "Estimated Quantity" field to "1" or change the Type Measurement from "XX".

387.1 387 Property Description of 11 not allowed with a single offense of 35A

To ensure that Drug/Narcotic Violations offenses and Drug Equipment Violations are properly reported, the Property Description of Drug/Narcotic Equipment is not allowed with a single offense of Drug/Narcotic Violations.


71

Tennessee FBI Description Error Error Number Number Suggested action: Based on incident circumstances, if

Drug/Narcotic Equipment is seized, enter the offense of Drug Equipment Violations. The two offenses require specific property descriptions.

387.2 387 Property Description of 10 not allowed with a single offense of 35B

To ensure that Drug/Narcotic Violations offenses and Drug Equipment Violations are properly reported, the Property Description of Drugs is not allowed with a single offense of Drug Equipment Violations.

Suggested action: Based on incident circumstances, if Drugs are seized, enter the offense of Drug/Narcotic Violations. The two offenses require specific property descriptions.

388 388 Number of Stolen Vehicles is less than the total number of vehicle Property Description codes

More than one vehicle code was entered in the Property Description field but the number stolen is less than this number. For example, if an Automobile and Bus were entered as being stolen in the Property Description, then the number Stolen must be at least 2.

Suggested action: Based on incident circumstances, either change the Number of Stolen Vehicles to be at least the same as the number of different vehicle codes or change the Property Description to something different than a vehicle type.

389 389 Number of Recovered Vehicles is less than the total number of vehicle Property Description codes

More than one vehicle code was entered in the Property Description field but the number recovered is less than this number. For example, if an Automobile and Bus were entered as being recovered in the Property Description, then the number Recovered must be at least 2.

Suggested action: Based on incident circumstances, either change the Number of Recovered Vehicles to be at least the same as the number of different vehicle codes or change the Property Description to something different than a vehicle type.


72

Tennessee FBI Description Error Error Number Number 390 390 Illogical Property Description for the offense(s) submitted

A property code was entered in the Property Description field that is illogical for the property offense. Either the offense was classified incorrectly or the wrong Property Description was entered. Example: Livestock would be an illogical Property Description for the offense of Larceny ‐ Pocket Picking.

Suggested action: Review the incident and make appropriate edits to the Property Description or Offense classification based on incident circumstances.

391 391 Property Value must be 0 for this Property Description

The Property Description code has a description that requires a value of zero (0) in the Value of Property field. Either the wrong Property Description was entered or the Property Value was not entered.

Suggested action: Based on incident circumstances, either edit the Property Description, enter a Property Value or change the Offense classification.

392 392 Suspected Drug Type required

An offense of Drug/Narcotic Violations with Type Property Loss of 1 = None was entered but the Suspected Drug Type was not entered. Since a drug seizure did not occur, the Suspected Drug Type must be entered.

Suggested action: Even though no drugs were seized (Property Loss of 1 = None), the Suspected Drug Type must still be entered.

TENNESSEE SPECIFIC PROPERTY SEGMENT ERRORS

MP_100.1 NULL With completed offense 100, the loss type must be 1, 5, 7 or 8 with attempted offense, loss type must be 1 or 8

With completed offense 100 ‐ Kidnapping/Abduction, the Type Property Loss must be 1 ‐ None, 5 ‐ Recovered, 7 ‐ Stolen, or 8 ‐ Unknown and attempted 100 ‐ Kidnapping/Abduction can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.


73

Tennessee FBI Description Error Error Number Number Suggested action: Edit the Type Property Loss to None,

Recovered (if the Stolen record is entered), Stolen or Unknown if the offense is completed or None or Unknown if the offense is Attempted and resubmit the incident.

MP_100.2 NULL With completed offense 100, Property Description is required

With completed offense of 100 ‐ Kidnapping/Abduction, a Property Description must be entered.

Suggested action: Enter a valid Property Description and resubmit the incident.

MP_100.3 NULL With completed offense 100, and a loss type of 5, Date Recovered is required

With a completed 100 ‐ Kidnapping/Abduction and a loss type of 5, an entry in the Date Recovered field is required.

Suggested action: Enter the Date Recovered and resubmit the incident.

MP_100.9 NULL With completed offense 100, Property Value is required

With a completed 100 ‐ Kidnapping/Abduction offense, an entry in the Property Value field is required.

Suggested action: Enter the value for the property in the offense.

MP_120.1 NULL With completed offense 120, property loss type must be 5 or 7, with attempted offense, loss type must be 1 or 8

With a completed offense of 120 ‐ Robbery, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen and attempted 120 ‐ Robbery can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit the Type Property Loss to Recovered (if the Stolen record is entered), or Stolen if the offense is completed or None or Unknown if the offense is Attempted.

MP_120.2 NULL With completed offense 120 Property Description is required

With completed offense of 120 ‐ Robbery, an entry in the Property Description field is required.


74

Tennessee FBI Description Error Error Number Number Suggested action: Enter a valid Property Description and

resubmit the incident.


With completed offense of 120 – Robbery and a loss type of 5, an entry in the Date Recovered field is required.

Suggested action: Enter the Date Recovered and resubmit the incident.


With completed offense of 120 ‐ Robbery, an entry in the Property Value field is required.


MP_200.1 NULL With completed offense 200, the loss type must be 2 with attempted offense, loss type must be 1 or 8

With an offense of completed 200 ‐ Arson, the Type Property Loss must be 2 ‐ Burned and attempted 200 ‐ Arson can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit the Type Property Loss to Burned if 200 ‐ Arson is Completed or if 200 ‐ Arson is attempted, edit Type Property Loss to None or Unknown and resubmit the incident.


With completed offense of 200 ‐ Arson, an entry in the Property Description field is required.



With completed offense of 200 ‐ Arson, an entry in the Property Value field is required.



75

Tennessee FBI Description Error Error Number Number MP_210.1 NULL With completed offense 210, the loss type must be 5 or 7,

with attempted offense, loss type must be 1 or 8

With an offense of completed 210 ‐ Extortion/Blackmail, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen and attempted 210 ‐ Extortion/Blackmail can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Recovered or Stolen if the 210 ‐ Extortion/Blackmail is completed or if 210 ‐ Extortion/Blackmail is attempted, edit Type Property Loss to None or Unknown and resubmit the incident.


With completed offense of 210 ‐ Extortion/Blackmail, an entry in the Property Description is required.


MP_210.3 NULL With completed offense 210 and a loss type of 5, Date Recovered is required

With completed offense of 210 – Extortion/Blackmail and a loss type of 5, an entry in the Date Recovered field is required.

Suggested action: Enter a valid date in the Date Recovered field and resubmit the incident.


With completed 210 ‐ Extortion/Blackmail, an entry in the Property Value field is required.


MP_220.1 NULL With completed offense 220, the loss type must be 1, 5, 7,or 8 with attempted offense, loss type must be 1 or 8

With an offense of completed 220 ‐ Burglary, the Type Property Loss must be 1 ‐ None, 5 ‐ Recovered, 7 – Stolen or 8 ‐ Unknown and attempted 220 ‐ Burglary can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.


76

Tennessee FBI Description Error Error Number Number Suggested action: Edit the Type Property Loss to None,

Recovered (if the Stolen record is entered), Stolen or Unknown if the offense is completed or None or Unknown if the offense is Attempted and resubmit the incident.


With completed offense of 220 ‐ Burglary, an entry in the Property Description field is required.



With completed offense of 220 ‐ Burglary and a loss type of 5, an entry in the Date Recovered field is required.



With completed offense of 220 ‐ Burglary, an entry in the Property Value field is required.


MP_23A.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8

With an offense of completed Larceny/Theft, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen and attempted Larceny/Theft can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Recovered or Stolen if the Larceny/Theft is completed or if Larceny/Theft is attempted, edit Type Property Loss to None or Unknown and resubmit the incident.


77

Tennessee FBI Description Error Error Number Number MP_23A.2 NULL With completed offense 23A‐H, Property Description is

required

With completed offense of Larceny/Theft, an entry in the Property Description field is required.


MP_23A.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required

With completed offense of Larceny/Theft and a loss type of 5, an entry in the Date Recovered field is required.


MP_23A.9 NULL With completed offense 23A‐H, Property Value is required

With completed offense of Larceny/Theft, an entry in the Property Value field is required.


MP_23B.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_23B.2 NULL With completed offense 23A‐H, Property Description is required




78

Tennessee FBI Description Error Error Number Number MP_23B.3 NULL With completed offense 23A‐H, and a loss type of 5, Date

Recovered is required



MP_23B.9 NULL With completed offense 23A‐H, Property Value is required



MP_23C.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_23C.2 NULL With completed offense 23A‐H, Property Description is required



MP_23C.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required




79

Tennessee FBI Description Error Error Number Number MP_23C.9 NULL With completed offense 23A‐H, Property Value is required



MP_23D.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_23D.2 NULL With completed offense 23A‐H, Property Description is required



MP_23D.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required



MP_23D.9 NULL With completed offense 23A‐H, Property Value is required




80


MP_23E.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7




MP_23E.2 NULL With completed offense 23A‐H, Property Description is required



MP_23E.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required



MP_23E.9 NULL With completed offense 23A‐H, Property Value is required




81

Tennessee FBI Description Error Error Number Number MP_23F.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7




MP_23F.2 NULL With completed offense 23A‐H, Property Description is required



MP_23F.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required



MP_23F.9 NULL With completed offense 23A‐H, Property Value is required




82

Tennessee FBI Description Error Error Number Number MP_23G.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7




MP_23G.2 NULL With completed offense 23A‐H, Property Description is required



MP_23G.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required



MP_23G.9 NULL With completed offense 23A‐H, Property Value is required




83

Tennessee FBI Description Error Error Number Number MP_23H.1 NULL With completed offense 23A‐H, the loss type must be 5 or 7




MP_23H.2 NULL With completed offense 23A‐H, Property Description is required



MP_23H.3 NULL With completed offense 23A‐H, and a loss type of 5, Date Recovered is required



MP_23H.9 NULL With completed offense 23A‐H, Property Value is required



MP_240.1 NULL With completed offense 240, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8

With an offense of completed 240 ‐ Motor Vehicle Theft, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen and attempted 240 ‐ Motor Vehicle Theft can only have a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.


84

Tennessee FBI Description Error Error Number Number Suggested action: Edit Type Property Loss to Recovered or

Stolen if the 240 ‐ Motor Vehicle Theft is completed or if 240 ‐ Motor Vehicle Theft is attempted, edit Type Property Loss to None or Unknown and resubmit the incident.


With completed offense of 240 ‐ Motor Vehicle Theft, an entry in the Property Description field is required.



With completed offense of 240 ‐ Motor Vehicle Theft and a loss type of 5, an entry in the Date Recovered field is required.


MP_240.4 NULL With completed offense 240, a property segment for a stolen vehicle is required

With a completed 240 ‐ Motor Vehicle Theft offense, a Property segment including a stolen vehicle is required.

Suggested action: Edit the incident to include a Property segment with a Type Loss of Stolen and Property Description of Vehicle and resubmit the incident.


With completed offense of 240 ‐ Motor Vehicle Theft, an entry in the Property Value field is required.



85

Tennessee FBI Description Error Error Number Number MP_250.1 NULL With completed offense 250, the loss type must be 3, 5,or 6


With a completed 250 ‐ Counterfeiting/Forgery offense, the Type Property Loss must be 3 ‐ Counterfeited/Forged, 5 ‐ Recovered, or 6 ‐ Seized. An attempted 250 ‐ Counterfeiting/Forgery offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Counterfeited/Forged, Recovered or Seized if the 250 ‐ Counterfeiting/Forgery is completed or if 250 ‐ Counterfeiting/Forgery is attempted, edit the Type Property Loss to None or Unknown.


With completed offense of 250 ‐ Counterfeiting/Forgery, an entry in the Property Description field is required.



With completed offense of 250 ‐ Counterfeiting/Forgery and a loss type of 5, an entry in the Date Recovered field is required.



With completed offense of 250 ‐ Counterfeiting/Forgery, an entry in the Property Value field is required.



86

Tennessee FBI Description Error Error Number Number MP_26A.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7


With a completed Fraud offense, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen. An attempted Fraud offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Recovered or Stolen if the Fraud offense is completed or if Fraud is attempted, edit the Type Property Loss to None or Unknown.

MP_26A.2 NULL With completed offense 26A‐G, Property Description is required

With completed offense of Fraud, an entry in the Property Description field is required.


MP_26A.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required

With completed offense of Fraud and a loss type of 5, an entry in the Date Recovered field is required.


MP_26A.9 NULL With completed offense 26A‐G, Property Value is required

With completed offense of Fraud, an entry in the Property Value field is required.


MP_26B.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8




87

Tennessee FBI Description Error Error Number Number MP_26B.2 NULL With completed offense 26A‐G, Property Description is

required



MP_26B.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required



MP_26B.9 NULL With completed offense 26A‐G, Property Value is required



MP_26C.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_26C.2 NULL With completed offense 26A‐G, Property Description is required




88


MP_26C.3 NULL With completed offense 26A‐G, and a loss type of 5, Date




MP_26C.9 NULL With completed offense 26A‐G, Property Value is required



MP_26D.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_26D.2 NULL With completed offense 26A‐G, Property Description is required



MP_26D.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required




89


MP_26D.9 NULL With completed offense 26A‐G, Property Value is required



MP_26E.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8



MP_26E.2 NULL With completed offense 26A‐G, Property Description is required



MP_26E.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required



MP_26E.9 NULL With completed offense 26A‐G, Property Value is required




90

Tennessee FBI Description Error Error Number Number MP_26F.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7




MP_26F.2 NULL With completed offense 26A‐G, Property Description is required



MP_26F.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required



MP_26F.9 NULL With completed offense 26A‐G, Property Value is required



MP_26G.1 NULL With completed offense 26A‐G, the loss type must be 5 or 7 with attempted offense, loss type must be 1 or 8




91

Tennessee FBI Description Error Error Number Number MP_26G.2 NULL With completed offense 26A‐G, Property Description is

required



MP_26G.3 NULL With completed offense 26A‐G, and a loss type of 5, Date Recovered is required



MP_26G.9 NULL With completed offense 26A‐G, Property Value is required



MP_270.1 NULL With completed offense 270, the loss type must be 5 or 7 with attempted offense type must be 1 or 8

With a completed 270 ‐ Embezzlement offense, the Type Property Loss must be 5 ‐ Recovered or 7 ‐ Stolen. An attempted 270 ‐ Embezzlement offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Recovered or Stolen if the 270 ‐ Embezzlement offense is completed or if 270 ‐ Embezzlement is attempted, edit the Type Property Loss to None or Unknown.


With completed offense of 270 ‐ Embezzlement, an entry in the Property Description field is required.



92

Tennessee FBI Description Error Error Number Number MP_270.3 NULL With completed offense 270, and a loss type of 5, Date


With completed offense of Embezzlement and a loss type of 5, an entry in the Date Recovered field is required.


MP_270.9 NULL With completed offense 270 Property Value is required

With completed offense of 270 ‐ Embezzlement an entry in the Property Value field is required.


MP_280.1 NULL With completed offense 280, the loss type must be 1 or 5 with attempted offense type must be 1 or 8

With a completed 280 ‐ Stolen Property Offenses offense, the Type Property Loss must be 1 – None or 5 – Recovered. An attempted 280 ‐ Stolen Property Offenses offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Recovered or Stolen if the 280 ‐ Stolen Property Offenses offense is completed or if 280 ‐ Stolen Property Offenses offense is attempted, edit the Type Property Loss to None or Unknown.


With completed offense of 280 ‐ Stolen Property Offenses an entry in the Property Description field is required.



With completed offense of 280 ‐ Stolen Property Offenses and a loss type of 5, an entry in the Date Recovered field is required.



93

Tennessee FBI Description Error Error Number Number MP_280.9 NULL With completed offense 280, Property Value is required

With completed offense of 280 ‐ Stolen Property Offenses an entry in the Property Value field is required.


MP_290.1 NULL With completed offense 290, the loss type must be 4 with attempted offense type must be 1 or 8

With a completed 290 ‐ Vandalism offense, the Type Property Loss must be 4 ‐ Destroyed/Damaged/Vandalized. An attempted 290 ‐ Vandalism offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Destroyed/Damaged/Vandalized if the Vandalism offense is completed or if Vandalism offense is attempted, edit the Type Property Loss to 1 ‐ None or 8 ‐ Unknown.


With completed offense of 290 ‐ Vandalism an entry in the Property Description field is required.



With completed offense of 290 ‐ Vandalism an entry in the Property Value field is required.


MP_35A.1 NULL With completed offense 35A, the loss type must be 1 or 6 with attempted offense type must be 1 or 8

With completed 35A ‐ Drug/Narcotic Violations offense, the Type Property Loss must be 1 ‐ None or 6 ‐ Seized. An attempted 35A ‐ Drug/Narcotic Violations offense requires a type Property Loss of 1 ‐ None or 8 ‐ Unknown.


94

Tennessee FBI Description Error Error Number Number Suggested action: Edit Type Property Loss to None or Seized if the

35A ‐ Drug/Narcotic Violations offense is completed or if 35A ‐ Drug/Narcotic Violations offense is attempted, edit the Type Property Loss to None or Unknown.

MP_35A.2 NULL With completed offense 35A, and a loss type of 6, Property Description is required. With loss type of 1, Property Description is blank and a Suspected Drug Type must be entered.

With completed offense of 35A ‐ Drug/Narcotic Violations an entry in the Property Description field is required.


MP_35A.4 NULL With completed offense 35A, and a property loss type 6, property value is required if the Property Description is any code but “10 – Drugs/Narcotics”. If the Property Description is Drugs/Narcotics, then the Property Value must be blank.

With completed offense of 35A ‐ Drug/Narcotic Violations an entry in the Property Value field is required.


MP_35A.5 NULL With offense 35A, and loss type of 6, drug type is required

With a 35A ‐ Drug/Narcotic Violations and a loss type of 6 ‐ Seized, a Drug Type must be entered.

Suggested action: Edit the Type Property Loss to Seized for a completed drug offense. For an attempted 35A ‐ Drug/Narcotic Violations, the Type Property Loss must be None or Unknown. The suspected drug type must be entered.

MP_35A.6 NULL With offense 35A, and loss type of 6, drug quantity is required

With a 35A ‐ Drug/Narcotic Violations and a loss type of 6 ‐ Seized, Drug Quantity must be entered.

Suggested action: For the Type Property Loss of seized, enter a Drug Quantity.

MP_35A.7 NULL With offense 35A, and loss type of 6 type, drug measure is required

With a 35A ‐ Drug/Narcotic Violations and a loss type of 6 ‐ Seized, a Drug Measurement must be entered.

Suggested action: For the Type Property Loss of seized, enter a Drug Measurement.


95

Tennessee FBI Description Error Error Number Number MP_35A.8 NULL With single offense 35A, and property type 6 property description

of 11 is not allowed

Must include the offense of 35B ‐ Drug Equipment Violations to report seized Drug Equipment in an incident.

Suggested action: Enter a Drug Equipment Violations offense if Drug Equipment was seized.

MP_35B.1 NULL With completed offense 35B, the loss type must be 1 or 6 with attempted offense type must be 1 or 8

With completed 35B ‐ Drug Equipment Violations offense, the Type Property Loss must be 1 ‐ None or 6 ‐ Seized. An attempted 35B ‐ Drug Equipment Violations offense requires a type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to None or Seized if the 35B ‐ Drug Equipment offense is completed or if 35B ‐ Drug Equipment Violations offense is attempted, edit the Type Property Loss to None or Unknown.

MP_35B.2 NULL With completed offense 35B, and a loss type of 6, a Property Description is required

With completed offense of 35B ‐ Drug Equipment Violations an entry in the Property Description field is required.


MP_35B.4 NULL With completed offense 35B, and a loss type of 6 property value is required

With completed offense of 35B ‐ Drug Equipment Violations an entry in the Property Value field is required.


MP_35B.5 NULL With single offense 35B and loss type of 6, property description of 10 is not allowed

Must include the offense of 35A ‐ Drug/Narcotic Violations to report Seized Drugs in an incident.

Suggested action: Enter a 35A ‐ Drug/Narcotic Violations offense if drugs/narcotics were seized.


96

Tennessee FBI Description Error Error Number Number MP_39A.1 NULL With completed offense 39A‐D, the loss type must be 6, with

attempted offense type must be 1 or 8

With completed 39A ‐ Gambling ‐ Betting/Wagering offense, the Type Property Loss must be 6 ‐ Seized. An attempted 39A ‐ Gambling ‐ Betting/Wagering offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Seized if the 39A ‐ Gambling ‐ Betting/Wagering offense is completed or if 39A ‐ Gambling ‐ Betting/Wagering offense is attempted, edit the Type Property Loss to None or Unknown.

MP_39A.2 NULL With completed offense 39A‐D, Property Description is required

With completed offense of 39A ‐ Gambling ‐ Betting/Wagering an entry in the Property Description field is required.


MP_39A.9 NULL With completed offense 39A‐D, Property Value is required

With completed offense of 39A ‐ Gambling ‐ Betting/Wagering an entry in the Property Value field is required.


MP_39B.1 NULL With completed offense 39A‐D, the loss type must be 6, with attempted offense type must be 1 or 8

With completed 39B ‐ Gambling ‐ Operating/Promoting/Assisting offense, the Type Property Loss must be 6 ‐ Seized. An attempted 39B ‐ Gambling ‐ Operating/Promoting/Assisting offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Seized if the 39B ‐ Gambling ‐ Operating/Promoting/Assisting offense is completed or if 39B ‐ Gambling ‐ Operating/Promoting/Assisting offense is attempted, edit the Type Property Loss to None or Unknown.

MP_39B.2 NULL With completed offense 39A‐D, Property Description is required


97

Tennessee FBI Description Error Error Number Number With completed offense of 39B ‐ Gambling ‐

Operating/Promoting/Assisting an entry in the Property Description field is required.


MP_39B.9 NULL With completed offense 39A‐D, Property Value is required

With completed offense of 39B ‐ Gambling ‐ Operating/Promoting/Assisting an entry in the Property Value field is required.


MP_39C.1 NULL With completed offense 39A‐D, the loss type must be 6, with attempted offense type must be 1 or 8

With completed 39C ‐ Gambling ‐ Equipment Violation offense, the Type Property Loss must be 6 ‐ Seized. An attempted 39C ‐ Gambling ‐ Equipment Violation offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Seized if the 39C ‐ Gambling ‐ Equipment Violation offense is completed or if 39C ‐ Gambling ‐ Equipment Violation offense is attempted, edit the Type Property Loss to None or Unknown.

MP_39C.2 NULL With completed offense 39A‐D, Property Description is required

With completed offense of 39C ‐ Gambling ‐ Equipment Violation an entry in the Property Description field is required.


MP_39C.9 NULL With completed offense 39A‐D, Property Value is required

With completed offense of 39C ‐ Gambling ‐ Equipment Violation an entry in the Property Value field is required.


MP_39D.1 NULL With completed offense 39A‐D, the loss type must be 6, with attempted offense type must be 1 or 8


98

Tennessee FBI Description Error Error Number Number With completed 39D ‐ Gambling ‐ Sports Tampering offense,

the Type Property Loss must be 6 ‐ Seized. An attempted 39D ‐ Gambling ‐ Sports Tampering offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to Seized if the 39D ‐ Gambling ‐ Sports Tampering offense is completed or if 39D ‐ Gambling ‐ Sports Tampering offense is attempted, edit the Type Property Loss to None or Unknown.

MP_39D.2 NULL With completed offense 39A‐D, Property Description is required

With completed offense of 39D ‐ Gambling ‐ Sports Tampering an entry in the Property Description field is required.


MP_39D.9 NULL With completed offense 39A‐D, Property Value is required

With completed offense of 39D ‐ Gambling ‐ Sports Tampering an entry in the Property Value field is required.


MP_510.1 NULL With completed offense 510, the loss type must be 1, 5, 7,or 8 with attempted offense type must be 1 or 8

With completed 510 ‐ Bribery offense, the Type Property Loss must be 1 ‐ None, 5 ‐ Recovered, 7 ‐ Stolen or 8 ‐ Unknown. An attempted 510 ‐ Bribery offense requires a Type Property Loss of 1 ‐ None or 8 ‐ Unknown.

Suggested action: Edit Type Property Loss to None, Recovered, Stolen or Unknown if the 510 ‐ Bribery offense is completed or if 510 ‐ Bribery offense is attempted, edit the Type Property Loss to None or Unknown.


99

Tennessee FBI Description Error Error Number Number MP_510.2 NULL With completed offense 510, Property Description is

required

With completed offense of 510 ‐ Bribery, an entry in the Property Description field is required.



With completed offense of 510 ‐ Bribery and a loss type of 5, an entry in the Date Recovered field is required.



With completed offense of 510 ‐ Bribery, an entry in the Property Value field is required.


TN_301.1 Property Value Flag over $500 must by Y or N for this offense and property loss type

Data entry in this field must be either Y ‐ Yes or N ‐ No for each property segment with a loss type of: 2 ‐ Burned, 4 ‐ Damaged/Destroyed/Vandalized, or 7 ‐ Stolen. This field is required for the following offenses: 200 ‐ Arson, 220 ‐ Burglary, 240 ‐ Motor Vehicle Theft, 290 ‐ Vandalism, 23A ‐ Pocket Picking, 23B ‐ Purse Snatching, 23D ‐ Theft From a Building, 23E ‐ Theft From Coin Machine, 23F ‐ Theft From a Motor Vehicle, 23G ‐ Theft of Vehicle Parts/Accessories, or 23H ‐ All Other Larceny, 26A – Fraud False Pretense, 26B – Credit Card Fraud, 26C – Impersonation, 26D – Welfare Fraud, 26E – Wire Fraud, 26F – Identity Theft and 26G – Computer Hacking/Invasion.

Suggested action: If the offense reported and the loss type is one of the ones requiring a Property Value Over $500, an entry in the Property Value Over $500 of Y or N must be made.


100

Tennessee FBI Description Error Error Number Number TN_301.2 Property Value Flag over $500 must be blank for this offense

and property loss type

The Incident Offense and Property Loss Type do not allow for an entry in the Property Value Over $500 field. The field must be blank.

Suggested action: Delete the entry in the Property Value Over $500 field or edit the Incident Offense and Property Loss Type.

TN_301.3 Property Value for this Property loss Type is $500 or less

The total Property Value submitted for this Loss Type is $500 or less.


TN_302.1 Prescription Drugs cannot be reported as a property type with 35A

The Property Category of Prescription Drugs cannot be submitted as a Property Type with the offense of 35A ‐ Drug/Narcotic Violations.

Suggested action: Based on incident circumstances, edit the Property Category or the Incident Offense.

TN_304.1 Entry for Location Marijuana fields must be I,O, or B when entered

If the Measurement Type for Marijuana is NP ‐ Number of Plants, one of the following entries is required in Type of Growth Field: I ‐ Indoor, O ‐ Outdoor, or B ‐ Both.

Suggested action: Based on incident circumstances, enter one of the valid codes from the list above in the Type of Growth field.

TN_304.2 Entry for Number of Plots must be a value between 1 ‐ 999

If the Measurement Type for Marijuana is NP ‐ Number of Plants, a numeric entry between 1 ‐ 999 is required in the Number of Plots field.

Suggested action: Enter a numeric value between 1 ‐ 999 in the Number of Plots field.


101

Tennessee FBI Description Error Error Number Number TN_304.3 Entry for Latitude of Marijuana Plots must be a value

between 34.8565 and 36.7541

If the measurement for Marijuana is NP ‐ Number of Plants, and an entry is made in the latitude field, it must have a value between 34.8565 and 36.7541.

Suggested action: Enter a numeric value between 34.8565 and 36.7541 in the latitude field.

TN_304.4 Entry for Longitude of Marijuana Plots must be a value between ‐81.5980 and ‐90.4973

If the measurement for Marijuana is NP ‐ Number of Plants, and an entry is made in the longitude field, it must have a value between ‐81.5980 and ‐90.4973.

Suggested action: Enter a numeric value between ‐81.5980 and ‐90.4973 in the longitude field.

TN_305 With a completed offense of 720, reported property seized may only be pets, livestock or money

The only Property Categories that may be reported for the offense of 720 – Animal Cruelty are: Pets, Livestock, or Money.

Suggested action: Edit the property category to pets, livestock, or money and resubmit the incident or edit the Incident Offense.

TN_305.1 With a completed offense of 720, seized is the only Loss Type that may be submitted

The only Loss Type that may be reported with the offense of 720 – Animal Cruelty is 6 – Seized.

Suggested action: Edit the Loss Type to 6 – Seized and resubmit the incident.

TN_306 Each Property Description must include a reported offense

Each Property Description must include an entry to indicate which offense the Property is related to.

Suggested action: Edit the Property segment and indicate the offense the Property Category is related to.


102

Tennessee FBI Description Error Error Number Number TN_306.1 Property Offense cannot be blank

Each Property Description must include an entry to indicate which offense the Property is related to. It is required and cannot be blank.

Suggested action: Edit the Property segment and indicate the offense the Property Category is related to and resubmit the incident.

TN_306.2 Property offense must be reported as one of the Incident Offenses

The Property offense reported in the Property segment is not included in the Offense segment.

Suggested action: Edit the Property offense reported in the Property segment and resubmit the incident. Or add the reported Property offense to the Offense segment for the incident and resubmit the incident.

VICTIM SEGMENT ERRORS


The ORI Number for the agency must be entered. It is required.

Suggested action: Enter the ORI Number for the agency and resubmit the incident.


The Incident Number must be entered. It is required.

Suggested action: Enter the Incident Number and resubmit the incident.

401.3 401 Victim Sequence Number is missing

The Victim Sequence Number must be entered. It must be a numeric entry 001 ‐ 999. It is required.

Suggested action: Enter the Victim Sequence Number and resubmit the incident.


103

Tennessee FBI Description Error Error Number Number 401.4 401 Victim Offense Code is missing

The Victim Offense Code must be entered. It is required.

Suggested action: Enter the Victim Offense Code and resubmit the incident.

401.5 401 Type Victim is missing

The Type Victim must be entered. It is required.

Suggested action: Enter the Type Victim and resubmit the incident.

401.6 Aggravated Assault/Homicide entry is missing

The Aggravated Assault/Homicide circumstances must be entered for victims of the following offenses: Aggravated Assault, Murder/Non‐negligent Manslaughter, Negligent Manslaughter, Justifiable Homicide, and Negligent Vehicular Manslaughter.

Suggested action: Enter the Aggravated Assault/Homicide circumstances and resubmit the incident.

401.7 LEOKA Activity type is required with Victim Type of L

With the Victim Type of L = Law Enforcement Official, you must enter the LEOKA Activity Type the victim officer was engaged in during the incident.

Suggested action: Enter the LEOKA Activity Type and resubmit the incident.

401.8 LEOKA Assignment type is required with Victim Type of L

With the Victim Type of L = Law Enforcement Official, you must enter the LEOKA Assignment Type for the victim officer during the incident.

Suggested action: Enter the LEOKA Assignment Type and resubmit the incident.


104

Tennessee FBI Description Error Error Number Number 401.9 Offender Number to be Related is mandatory

If the offense is a Crime Against Persons or Robbery, a Victim to the Offender Relationship must be entered.

Suggested action: Enter the Victim to Offender Relationship or edit the Incident Offense. Resubmit the incident.

402.1 402 Invalid Victim Sequence Number entry is non‐numeric

The Victim Sequence Number must be a numeric entry 001 ‐ 999. It is required.

Suggested action: Enter the Victim Sequence Number as a numeric entry, 001 ‐ 999, and resubmit the incident.

402.2 403 Invalid Victim/Offender Relationship

If the offense is a Crime Against Persons or Robbery, a Victim to the Offender Relationship must be entered.

Suggested action: If the Offense is a Crime Against Persons or Robbery, enter the Victim to Offender Relationship, edit the relationship entered, or edit the Incident Offense. Resubmit the incident.

404.1 404 Invalid Victim Offense Code

The Victim Offense Code must be a valid TIBRS Group A Offense Code.

Suggested action: Edit the Victim Offense Code and resubmit the incident.

404.11 404 Invalid Injury Type entry

The Injury Type submitted must be a valid code based on the Incident Offense.

Suggested action: Edit the Injury Type and resubmit the Incident.


105

Tennessee FBI Description Error Error Number Number 404.12 404 Invalid Victim/Offender Relationship entry

A Victim/Offender Relationship has been submitted for an Offense that is not a Crime Against Persons or Robbery or the value submitted is not valid based on victim/offender demographic data submitted.

Suggested action: Edit the Incident Offense or the victim/offender demographic data and resubmit the incident.

404.13 Invalid LEOKA Activity type

The LEOKA Activity Type must be a valid code.

Suggested action: Edit the LEOKA Activity Type and resubmit the incident.

404.14 Invalid LEOKA Assignment type

The LEOKA Assignment Type must be a valid code.

Suggested action: Edit the LEOKA Assignment Type and resubmit the incident.

404.15 404 Invalid Additional Justifiable Homicide Circumstances entry

The Additional Justifiable Homicide Circumstances entry must be a valid code.

Suggested action: Edit the Additional Justifiable Homicide Code and resubmit the incident.

404.2 404 Invalid Type Victim entry

The data within the referenced field contains invalid data.

Suggested action: Edit the Type Victim and resubmit the incident.

404.3 404 Invalid Victim Age entry



106

Tennessee FBI Description Error Error Number Number Suggested action: Edit the Victim Age and resubmit the

incident.

404.4 404 Invalid Victim Sex entry


Suggested action: Edit the Victim Sex and resubmit the incident.

404.5 404 Invalid Victim Race entry


Suggested action: Edit the Victim Race and resubmit the incident.

404.6 404 Invalid Victim Ethnicity entry


Suggested action: Edit the Victim Ethnicity and resubmit the incident.

404.7 404 Invalid Victim Resident Status entry


Suggested action: Edit the Victim Resident Status and resubmit the incident.

404.8 404 Invalid Aggravated Assault/Homicide entry


Suggested action: Edit the Aggravated Assault/Homicide entry and resubmit the incident.

404.9 404 Invalid Aggravated Assault/Homicide entry



107

Tennessee FBI Description Error Error Number Number Suggested action: Edit the Aggravated Assault/Homicide

entry and resubmit the incident.

406.1 406 Duplicate Victim Offense Code

The data element in error is one that contains multiple data values. When more than one code is entered, there cannot be a duplicate code.

Suggested action: Refer to the data value in the error message and enter a valid data value for all options without entering duplicate values.

406.2 406 Duplicate Aggravated Assault/Homicide Circumstances entry



406.3 406 Duplicate Injury Type entry



406.4 406 Duplicate Victim/Offender Relationship entry

The data element in error is one that contains multiple data values. When more than one code is entered, none can be duplicate ones.

Suggested action: Refer to the data value in the error message and enter valid data for all options without entering duplicate values.


108

Tennessee FBI Description Error Error Number Number 407 407 Injury Type of 'N' is mutually exclusive

Type Injury can have multiple data values and was entered with multiple values. However, the data value of None cannot be entered with other data.

Suggested action: Edit Injury Type and resubmit the incident.

408 408 Victim Age must be left‐justified

Victim Age contains data, but is not left‐justified. A single two‐character age must be in positions 1 and 2 of the field.

Suggested action: Enter valid age and ensure that a numeric age is in the first two places in the file and resubmit the incident. Contact your vendor if necessary.

409 409 Victim Age is non‐numeric

Victim Age contains more than two characters indicating a possible age‐range was attempted. If so, the field must contain numeric entry of four digits.

Suggested action: Enter valid age range containing 4 digits and resubmit the incident. Contact your vendor if necessary.

410 410 Invalid Age Range

Age of Victim was entered as an age range. Accordingly, the first age component must be less than the second age.

Suggested action: Enter a correct age range with the lowest age in the first two positions and resubmit the incident. Contact your vendor if necessary.


109

Tennessee FBI Description Error Error Number Number 415 415 Incident Number contains embedded blanks

The Incident Number contains embedded blanks between the first and last significant number.

Suggested action: Remove blanks at the beginning of the Incident Number and resubmit. If the Incident Number is automatically generated, contact your vendor about the issue.


The Incident Number must be left‐justified with blank right‐fill. Since the number is less than 12 characters, it must begin in position 1; one or more blanks were entered in position 1 followed by the data.



The Incident Number can only have character combinations of A ‐ Z, 0 ‐ 9, hyphens, and/or blanks. Example 89‐123‐SC is valid, but 89+123*SC is invalid.

Suggested action: Use only Incident Numbers that conform to the parameter for the Incident Number which include: capital letters only, numerals, hyphens or blanks at the end of the Incident Number (no blanks within the Incident Number or at the beginning). If the Incident Number is automatically generated, contact your vendor about the issue.

419.1 419 Aggravated Assault/Homicide Circumstances entry not allowed

Aggravated Assault/Homicide Circumstances data can only be entered when one or more Victim Connected to UCR Offense Code(s) entries are: 09A ‐ Murder/Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, 09D ‐ Negligent Vehicular Manslaughter, or 13A ‐ Aggravated Assault.


110

Tennessee FBI Description Error Error Number Number Suggested action: Based on incident circumstances, remove

the data from the Aggravated Assault/Homicide Circumstances or change the Offense(s) entered to Offense(s) that allow for entry of this data.

419.2 419 Injury Type entry not allowed

Type Injury data can only be entered when one or more Victim Connected to UCR Offense Code(s) entries are: 100 ‐ Kidnapping/Abduction, 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object, 11D ‐ Fondling, 120 ‐ Robbery, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, or 210 ‐ Extortion/Blackmail.

Suggested action: Based on incident circumstances, remove the data from the Injury Type or change the Offense(s) entered to Offense(s) that allow for entry of this data.

422 422 Victim Age Range cannot start with a '00'

Victim Age was entered as an age‐range. Therefore, first age component cannot be 00 (unknown).

Suggested action: If victim age is unknown, leave completely blank. If an age or age range is known, first age must be greater than 00.

450 450 Victim spouse Age must be greater than 10

Relationship of Victim to Offender contains a relationship of SE = Spouse. When this is so, the age of the Victim cannot be less than 10 years.

Suggested action: Review the Incident report and either change the age of the Victim or the relationship between the Victim and the Offender.

451 451 Duplicate Victim Number

When a Group A Incident Report is submitted, the individual segments comprising the incident cannot have duplicates. In this case, two victim segments were submitted having the same Victim Sequence Number.


111

Tennessee FBI Description Error Error Number Number Suggested action: Delete one Victim or check with your

vendor since Victim Sequence Numbers should be automatically and sequentially generated.

452 452 Victim is Law Enforcement Officer but age is not between 18 and 98, or Unknown

When Victim Type = L – Law Enforcement Official, the Victim Age must be 18 or greater and less than or equal to 98 or 00 = Unknown.

Suggested action: Enter valid Victim Age or Age Range or edit Victim Type and resubmit the incident.

453.1 453 Victim Age is missing

Victim Age must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Age or edit Victim Type and resubmit the incident.

453.2 453 Victim Sex is missing

Victim Sex must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Sex or edit Victim Type and resubmit the incident.

453.3 453 Victim Race is missing

Victim Race must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Race or edit Victim Type and resubmit the incident.

453.4 Victim Ethnicity is missing

Victim Ethnicity must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Ethnicity or edit Victim Type and resubmit the incident.


112

Tennessee FBI Description Error Error Number Number 453.5 Resident status is missing

Victim Resident Status must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Resident Status or edit Victim Type and resubmit the incident.

454 454 MUST BE PRESENT WHEN VICTIM TYPE (25) = L

When Victim Type = L ‐ Law Enforcement Official, the data fields for LEOKA Activity Type, LEOKA Assignment, Victim Age, Victim Race, Victim Ethnicity, and Victim Sex must be filled in also.

Suggested action: Enter valid data for the missing data field(s) or edit Victim Type and resubmit the incident.

455 455 Justifiable Homicide Circumstances entry is missing

Aggravated Assault/Homicide Circumstances contains: 20 = Criminal killed by private citizen or 21 = Criminal killed by police officer; but Additional Justifiable Homicide Circumstances was not entered.

Suggested action: Enter appropriate choice in the "Additional Justifiable Homicide Circumstances" or change the entry in the "Aggravated Assault/Homicide Circumstances" field based on incident circumstances.

456 456 Aggravated Assault/Homicide Circumstances entries can only contain one value greater than 10

Aggravated Assault/Homicide Circumstances was entered with two entries, but was rejected for one of the following reasons: 1) Value 10 ‐ Unknown Circumstances is mutually exclusive with any other value or 2) More than one category (i.e. Aggravated Assault, Negligent Manslaughter, etc.) was entered.


113

Tennessee FBI Description Error Error Number Number Suggested action: Based on incident circumstances, if

"Unknown Circumstances" is correct, delete the other entry for this data value. If reason 2, enter information in one category only and resubmit the incident.

457 457 Aggravated Assault/Homicide Circumstances entry not allowed

Additional Justifiable Homicide Circumstances was entered but Aggravated Assault/Homicide Circumstances does not reflect a Justifiable Homicide Circumstance.

Suggested action: Based upon incident circumstances, either change Aggravated Assault/Homicide Circumstances entry to reflect Justifiable Homicide or delete entry in the "Additional Justifiable Homicide Circumstances" field and resubmit the incident.

458 Victim Type must be I for data to be entered

The data element associated with this error cannot be entered when the Victim Type is not I = Individual.

Suggested action: Based upon incident circumstances, either change the Victim Type to "I" or delete the fields referenced in the error message.

458.1 458 Victim Age entry not allowed



458.2 458 Victim Sex entry not allowed




114

Tennessee FBI Description Error Error Number Number 458.3 458 Victim Race entry not allowed



458.4 458 Victim Ethnicity entry not allowed



458.5 458 Victim Resident Status entry not allowed



458.6 458 Victim/Offender Relationship entry not allowed




115

Tennessee FBI Description Error Error Number Number 459 459 Victim/Offender Relationship only valid for a Crime Against

People or Robbery

Offender Numbers to be Related was entered but should only be entered if one or more of the offenses entered in the Victim Connected to UCR Offense Code(s) is a Crime Against Person or a Robbery. None of these type Offenses were entered.

Suggested action: Based on incident circumstances, either change the Offense(s) to a Crime Against Persons or Robbery or delete the relationships between the Offender and Victim.

460 460 Victim/Offender Relationship is missing

Victim to Offender Relationship data must be entered when the Offender Numbers to be Related is entered with a value greater than 00.

Suggested action: If the Offense is a Crime Against Persons or Robbery, relate each Offender to each Victim. If the offense is anything else, remove the Offender Sequence Number and resubmit the incident. Contact your vendor if necessary.

461 461 Type Victim cannot equal 'S' with an offense of 220

The Type Victim cannot be Society/Public when the offense is 220 ‐ Burglary.

Suggested action: Based on incident circumstances, either change the Victim Type or change the offense classification and resubmit the incident.


116

Tennessee FBI Description Error Error Number Number 462.1 462 For Offense Code 13A the valid Aggravated Assault/Homicide

Circ. entries are 01‐06, and 08‐10

An Offense segment was submitted for 13A ‐ Aggravated Assault. Accordingly, Aggravated Assault/Homicide Circumstances can only have codes of 01 through 06 and 08 through 10. All other codes, including 07 ‐ Mercy Killing, are not valid because they do not relate to a 13A ‐ Aggravated Assault.

Suggested action: Based on incident circumstances, enter a valid code for the data field based upon the circumstances or change the offense classification and resubmit the incident.

462.2 462 For Offense Code 13A the valid Aggravated Assault/Homicide Circ. entries are 01‐06, and 08‐10

An Offense segment was submitted for 13A ‐ Aggravated Assault. Accordingly, Aggravated Assault/Homicide Circumstances can only have codes of 01 through 06 and 08 through 10. All other codes, including 07 ‐ Mercy Killing, are not valid because they do not relate to a 13A ‐ Aggravated Assault.


463 463 For Offense Code 09C the valid Aggravated Assault/Homicide Circ. entries are 20 or 21

When a 09C ‐ Justifiable Homicide is reported, Aggravated Assault/Homicide Circumstances can only have codes of 20 ‐ Criminal Killed by Private Citizen or 21 ‐ Criminal Killed by Police Officer. In this case, a code other than the two mentioned was entered.



117

Tennessee FBI Description Error Error Number Number 464 464 Crime Against Person must have a Type Victim = I or L

Victim Connected to UCR Offense Codes contains a Crime Against Persons offense, but the Type of Victim is not an Individual or Law Enforcement Officer.

Suggested action: Based on incident circumstances, change the Type Victim to Individual or Law Enforcement Officer or change the offense classification and resubmit the incident.

465 465 Crime Against Society must have a Type Victim = S

Victim Connected to UCR Offense Codes contains a Crime Against Society offense, but the Type of Victim is not Society.

Suggested action: Change the Victim Type to "Society" or the offense classification and resubmit the incident.

466 466 Victim Offense was not found among submitted offenses.

Each UCR Offense Code entered into Victim Connected to UCR Offense Codes must have the Offense Segment for the value. In this case, the victim was connected to offense(s) that were not submitted as offense segments. A victim cannot be connected to an offense when the offense itself is not present.

Suggested action: Review the incident and connect each victim to an offense reported in the incident or add another offense segment to the incident. Resubmit the incident.

467 467 Crime Against Property cannot have a Type Victim = S

Victim Connected to UCR Offense Codes contains a Crime Against Property but the Victim Type is Society. This is not an allowable code for a Crime Against Property Offense.

Suggested action: Change the Victim Type to an appropriate code for a Crime Against Property offense.


118

Tennessee FBI Description Error Error Number Number 468 468 Victim/Offender Relationship not allowed

Relationship of Victim to Offender cannot be entered when the Offender Number to be Related is zero. Zero means the number of offenders is Unknown; therefore, the relationship cannot be entered.

Suggested action: Delete the Victim to Offender relationship or enter information about the offender(s).

469 469 Sex of Victim must be 'M' or 'F' for offenses 11A or 36B

Sex of Victim must be "M" or "F" to be connected to offenses of Rape or Statutory Rape.

Suggested action: Enter valid code for the sex of the Victim and resubmit the incident.

470.1 470 Victim/Offender Relationship 'VO' requires two or more Victims

Relationship of Victim to Offenders has a relationship of Victim was Offender. When this relationship is entered, a minimum of two victim and two offender segments must be submitted. In this case, only one victim and/or one offender segment was submitted.

The entry of Victim was Offender on one or more of the victims indicates situations such as brawls and domestic disputes. In the vast majority of cases, each victim is also the offender; therefore, every victim would contain a VO code. However, there may be some situations where only one of the victims is also the offender but where the other victim(s) is not also the offender(s).

Suggested action: Please enter at least two Victims and two Offenders for the incident with codes of "VO".


119

Tennessee FBI Description Error Error Number Number 470.2 470 Victim/Offender Relationship 'VO' requires two or more

Offenders

Relationship of Victim to Offenders has a relationship of Victim was Offender. When this relationship is entered, a minimum of two victim and two offender segments must be submitted. In this case, only one victim and/or one offender segment was submitted.

The entry of Victim was Offender on one or more of the victims indicates situations such as brawls and domestic disputes. In the vast majority of cases, each victim is also the offender; therefore, every victim would contain a VO code. However, there may be some situations where only one of the victims is also the offender but where the other victim(s) is not also the offender(s).

Suggested action: Please enter at least two Victims and two Offenders for the incident with codes of "VO".

470.3 Relationship of VO requires additional relationship(s)

Data entry in the Victim to Offender Relationship field of the relationship VO ‐ Victim was Offender requires more than one (1) relationship code be entered.

Suggested action: Enter additional relationships or edit the code of VO.

470.4 VO relationship requires at least 2 victim segments and at least 2 relationships of VO

Entry of the Victim to Offender relationship of VO requires 2 or more Victim segments and 2 or more relationships of VO.

Suggested action: Based on incident circumstances, either enter two or more Victim segments and two or more relationships of VO or edit the victim to offender relationship code of VO.


120

Tennessee FBI Description Error Error Number Number 471 471 Only one 'VO' Relationship is allowed per Victim

The Relationship of Victim to Offenders has relationships of Victim was Offender that point to multiple offenders, which is an impossible situation. A single Victim cannot be two Offenders.

Suggested action: Edit the relationship codes to reflect correct relationship. If all Victims were also all Offenders, then the same number of victims and offenders must be entered.

472 472 If Offender Age/Sex/Race/Ethnicity are Unknown, then Relationship must be RU = Unknown

Relationship of Victim to Offenders has a relationship to the offender that is not logical. In this case, the offender was entered with Unknown values for age, sex, race, and ethnicity. Under these circumstances, the relationship must be entered as "RU" ‐ relationship unknown.

Suggested action: If an offender is not known, the relationship between the Victim to Offender must be unknown ‐ enter "RU" for relationship for applicable offenses.

473 473 When Assault/Homicide(31) is '08,' must have 2 or more offenses

If Other Felony Involved is checked under Assault/Homicide Circumstances, two or more Offense segments must be submitted.

Suggested action: Based on incident circumstances, either enter two or more offenses in the incident or change the data value for "Assault/Homicide Circumstances" field.

474 474 Only one 'VO' Relationship can be assigned to specific Offender

Two of more Victim segments have Relationship of Victim to Offender with a relationship of VO = Victim was Offender entered that point to the same offender.

Suggested action: Edit incident to reflect correct victim to offender


121

Tennessee FBI Description Error Error Number Number 475.1 475 Victim cannot be assigned the Relationship of 'SE' (Spouse)

more than once

A Victim can only have one spousal relationship. In this instance, the Victim has a relationship of spouse to two or more offenders.

Suggested action: Review the incident and correct Victim to Offender relationship codes.

475.2 475 Offender cannot be assigned the Relationship of 'SE' (Spouse) more than once

An Offender can only have one spousal relationship. In this instance, two or more Victims have a relationship of spouse to the same Offender.

Suggested action: Review the incident and correct Victim to Offender relationship codes.

477 477 Invalid Aggravated Assault/Homicide Circumstance only valid with offenses 09A, 09B, 09C, 09D, 13A

A Victim segment was submitted with Victim Connected to UCR Offense Code having an offense that does not have a permitted code for Aggravated Assault/Homicide Circumstances. Only those circumstances listed in the Victim section of the TIBRS Data Collection manual are valid for the particular Offense.

Suggested action: Based on incident circumstances, either edit/delete the entry in the "Aggravated Assault/Homicide Circumstances" field or change the Offense classification.


122

Tennessee FBI Description Error Error Number Number 478 478 Victim connected to an invalid combination of offenses (see

FBI table page 66)

Mutually Exclusive offenses are ones that cannot occur to the same victim by UCR definition. A Lesser included offense is one that is an element of another offense and should not be reported as having happened to the Victim along with the other offense. Lesser included and Mutually Exclusive offenses are defined as follows:

1. Murder ‐‐ Aggravated Assault, Simple Assault, Intimidation, and Stalking are all lesser included offenses of Murder. Negligent Manslaughter is Mutually Exclusive.

2. Aggravated Assault ‐‐ Simple Assault, Intimidation, and Stalking are lesser included offenses of Aggravated Assault. NOTE: Aggravated Assault is a lesser included offense of Murder, Rape, Sodomy, Sexual Assault With an Object, and Robbery.

3. Simple Assault ‐‐ Intimidation and Stalking are lesser included offenses of Simple Assault.

4. Intimidation ‐‐ Intimidation and Stalking are lesser included offenses of Murder, Aggravated Assault, Rape, Sodomy, Sexual Assault With an Object, Fondling and Robbery.

5. Stalking ‐‐ Stalking is a lesser included offense of Murder, Aggravated Assault, Rape, Sodomy, Sexual Assault With an Object, Fondling, and Robbery. NOTE: Stalking is a Tennessee specific Offense.

6. Negligent Manslaughter ‐‐ Murder, Aggravated Assault, Simple Assault, Intimidation, and Stalking are Mutually Exclusive offenses. Negligent Manslaughter is defined as "The killing of another person through negligence." Assault offenses are characterized by "unlawful attack(s)."

7. Rape ‐‐ Aggravated Assault, Simple Assault, Intimidation, Stalking, and Fondling are lesser included offenses of Rape. Incest and Statutory Rape are Mutually Exclusive offenses and cannot occur with Rape. The prior two offenses involve consent, while Rape involves forced action against the victim's will.

8. Sodomy ‐‐ Aggravated Assault, Simple Assault, Intimidation, Stalking, and Fondling are lesser included offenses of Sodomy. Incest and Statutory Rape are Mutually Exclusive offenses and cannot occur with Sodomy. The prior two offenses involve consent, while Sodomy involves forced action against the victim's will.


123

Tennessee FBI Description Error Error Number Number 9. Sexual Assault With an Object ‐‐ Aggravated Assault, Simple

Assault, Intimidation, Stalking, and Fondling are lesser included offenses of Sexual Assault With an Object. Incest and Statutory Rape are Mutually Exclusive offenses and cannot occur with Sexual Assault With an Object. The prior two offenses involve consent while Sexual Assault With an Object involves forced action against the victim's will.

10. Fondling ‐‐ Simple Assault, Intimidation, and Stalking are lesser included offenses of Fondling. Incest and Statutory Rape are Mutually Exclusive offenses and cannot occur with Fondling. The prior two offenses involve consent, while Fondling involves forced action against the victim's will. NOTE: Fondling is a lesser included offense of Rape, Sodomy, and Sexual Assault With an Object.

11. Incest ‐‐ Rape, Sodomy, Sexual Assault With an Object, and Fondling are Mutually Exclusive offense. Incest involves consent while the prior offenses involve sexual relations against the victim's will.

12. Statutory Rape ‐‐ Rape, Sodomy, Sexual Assault With an Object, and Fondling are Mutually Exclusive offenses. Statutory Rape involves consent while the prior offenses involve sexual relations against the victim's will.

13. Robbery ‐‐ Aggravated Assault, Simple Assault, Intimidation, Stalking and all Theft offenses (including Motor Vehicle Theft) are lesser included offenses of Robbery. The chart on the following page shows the offense that cannot occur to the same Victim in the same incident.

Suggested action: Based on incident circumstances, edit the offenses based on provided criteria.

478.1 478 Victim connected to an invalid combination of offenses

Mutually Exclusive offenses are ones that cannot occur to the same victim by UCR definition. Victim cannot be a victim of the offense of Intimidation and Stalking in the same incident.

Suggested action: Based on incident circumstances, edit the offenses based on provided criteria.


124

This chart shows TIB

RS

offenses that cannot occur to the same victim

, perpetrated by the same offender in the sam

e incident. Each “X

” on the chart where offenses intersect indicates that those tw

o offenses cannot occur in the sam

e incident under those circumstances.

09A M

urder X

X

X X

X X

09B N

egligent Manslaughter

X X

X

X X

X

11A R

ape

X

X

X X

X X

X

X

11B S

odomy

X

X

X

X X

X

X X

11C S

exual Assault w

ith an Object

X X

X

X X

X

X X

11D Fondling

X X

X X

X X

X

X X

120 Robbery

X X

X X

X X

X X

X X

X X

X X

13A A

ggravated Assault

X X

X X

X

X X

X X

X

13B S

imple A

ssault X

X X

X X

X X

X X

X X

13C Intim

idation X

X X

X X

X X

X X

X X

13D S

talking X

X X

X X

X X

X X

X X

23A P

ocket Picking

X

X

23B P

urse Snatching

X

X

23C S

hoplifting

X

X

23D Theft from

a Building

X

X

23E Theft from

a Coin O

perated Machine

X

X

23F Theft from a M

otor Vehicle

X

X X

23G Theft of M

otor Vehicle P

arts and Accessories

X

X X

23H A

ll Other Larceny

X

X

240 Motor V

ehicle Theft

X

X

36A Incest

X X

X X

X

36B S

tatutory Rape

X X

X X

X

40A P

rostitution

X

64A H

uman Trafficking – C

omm

ercial Sex A

cts

X

09C Justifiable H

omicide cannot

occur with any other offense

09A Murder

09B Negligent Manslaughter

11A Rape

11B Sodomy

11C Sexual Assault w/Object

11D Fondling

120 Robbery

13A Aggravated Assault

13B Simple Assault

13C Intimidation

13D Stalking

23A Pocket Picking

23B Purse Snatching

23C Shoplifting

23D Theft from a Building

23E Theft from Coin Machine

23F Theft from Motor Vehicle

23G Theft of Vehicle Parts

23H All Other Larceny

240 Motor Vehicle Theft

36A Incest

36B Statutory Rape

40A Prostitution

64A Human Trafficking Commercial Sex Acts

TIBRS Error manual, Edition 7.0 August 2016

125

Tennessee FBI Description Error Error Number Number 479 479 Simple Assault ('13B') cannot have 'Major Injuries'

A 13B ‐ Simple Assault was committed against a Victim but the Victim had major injuries/trauma entered for the Type Injury. Either the offense should have been classified as a 13A ‐ Aggravated Assault or the victim's injury should not have been entered as major.

Suggested action: Based on incident circumstances, either change the Injury Type or the offense classification.

480 480 When Assault/Homicide(31) is '08,' must have 2 or more offenses

Aggravated Assault/Homicide Circumstances has 08 ‐ Other Felony Involved but the incident has only one offense. For this code to be used there must be two or more offenses.

Suggested action: Either multiple entries for the UCR Offense Code should have been submitted, or multiple individual victims should have been submitted for the incident report. Please review the report and enter additional offense(s) or victims.

480.1 480 When Assault/Homicide(31) is 08, Incident must have 2 or more offenses or 2 Victims

Aggravated Assault/Homicide Circumstances has 08 ‐ Other Felony Involved but the incident has only one offense. For this code to be used there must be two or more offenses.

Suggested action: Either multiple entries for the UCR Offense Code should have been submitted, or multiple individual victims should have been submitted for the incident report. Please review the report and enter additional offense(s) or victims.


126

Tennessee FBI Description Error Error Number Number 481 481 Victim's Age must be less than state limit for Statutory Rape

('36B')

Among the states, the age at which a Victim is considered a Statutory Rape victim varies. The victim's age exceeds the maximum age possible for a Statutory Rape in the state.

Suggested action: For TIBRS, in order to report the offense of Statutory Rape, the Victim must be between the ages of 13 and 17, and the Offender must be at least 4 years older. Based on incident circumstances, either change the Victim age or change the Offense classification.

482 482 Victim type L can only be used when connected to certain offenses

To have a Victim Type of "L", Victim Connected to UCR Offense code must contain at least one of these offense codes: 09A ‐ Murder and Nonnegligent Manslaughter, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation, or 13D ‐ Stalking.

Suggested action: Based on incident circumstances, either change the Victim Type or the Offense classification.

482.1 482 No valid LEOKA offense was found for Victim type of L

To have a Victim Type of "L", Victim Connected to UCR Offense code must contain at least one of these offense codes: 09A ‐ Murder and Nonnegligent Manslaughter, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation, or 13D ‐ Stalking.

Suggested action: Based on incident circumstances, either change the Victim Type or the Offense classification.

482.2 482 LEOKA fields must be blank when Victim type is not L

Data has been entered in LEOKA Activity Type and the Victim Type is not L ‐ Law Enforcement Official.

Suggested action: Based on incident circumstances, either change the Victim Type or delete the entry in LEOKA Activity Type.


127

Tennessee FBI Description Error Error Number Number 482.3 482 LEOKA fields must be blank when Victim type is not L

Data has been entered in LEOKA Assignment Type and the Victim Type is not L ‐ Law Enforcement Official.

Suggested action: Based on incident circumstances, either change the Victim Type or delete the entry in LEOKA Assignment Type.

482.4 482 LEOKA fields must be blank when Victim type is not L

Data has been entered in LEOKA Other Jurisdiction ORI field and the Victim Type is not L ‐ Law Enforcement Official.

Suggested action: Based on incident circumstances, either change the Victim Type or delete the entry in LEOKA Other Jurisdiction field.

483 483 Victim Type (25) must be L for data to be entered

The data element associated with this error cannot be entered when the Victim Type is not L = Law Enforcement Official.

Suggested action: Based on incident circumstances, either change the Victim Type to "L" or delete the entered information in the referenced fields.

484 484 This Victim segment has a conflicting length

The Victim segment is not the same physical length as the first Victim segment submitted. All Victim segments within a submission must be formatted the same.



128


TENNESSEE SPECIFIC VICTIM SEGMENT ERRORS

MV_09.1 NULL Victim of offenses 09A‐D must be an 'I' type victim

The Victim for the Homicide Offenses ‐ 09A ‐ Murder/Non‐negligent Manslaughter, 09B ‐ Negligent Manslaughter, 09C ‐ Justifiable Homicide, or 09D – Negligent Vehicular Manslaughter must be an Individual.

Suggested action: Based upon incident circumstances, change the Victim Type to I ‐ Individual or change the Offense classification.

MV_09.2 NULL Victim of 09A‐D requires homicide circumstance entry

The Victim segment of a Homicide offense must have an entry in the Aggravated Assault/Homicide Circumstances field.

Suggested action: Enter the applicable code for the Aggravated Assault/Homicide Circumstances field. It cannot be blank.

MV_09C.1 NULL Victim of offense 09C homicide circumstance must be 20 and/or 21

The Victim segment of a 09C ‐ Justifiable Homicide offense must have an entry in the Aggravated Assault/Homicide Circumstances field of 20 ‐ Criminal Killed by Private Citizen or 21 ‐ Criminal Killed by Police Officer.



129

Tennessee FBI Description Error Error Number Number MV_09C.2 NULL Victim of offense 09C requires entry of justifiable homicide

circumstances

The Victim segment of a 09C ‐ Justifiable Homicide offense must have an entry in the Additional Justifiable Homicide Circumstances field. Valid Codes: A ‐ Criminal Attacked Police Officer and that Officer Killed Criminal, B ‐ Criminal Attacked Police Officer and Criminal Killed by Another Police Officer, C ‐ Criminal Attacked a Civilian, D ‐ Criminal Attempted Flight from a Crime, E ‐ Criminal Killed in Commission of Crime, F ‐ Criminal Resisted Arrest, and G ‐ Unable to Determine/Not Enough Information.

Suggested action: Enter the applicable code for the Additional Justifiable Homicide Circumstances field. It cannot be blank.

MV_100.1 NULL Victim of offense 100 must be an 'I' type victim

The Victim for a 100 ‐ Kidnapping/Abduction offense must be an Individual.


MV_100.2 NULL Victim of offense 100 must be associated with a type injury

The Victim of a 100 ‐ Kidnapping/Abduction offense must have an Injury Type entered.

Suggested action: Based upon incident circumstances, enter the appropriate Injury Type or change the offense classification.

MV_11.1 NULL Victim of offenses 11A‐D must be an 'I' type victim

The Victim for a Sex Offense ‐‐ 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object or 11D ‐ Fondling must be an Individual.



130

Tennessee FBI Description Error Error Number Number MV_11.2 NULL Victim of offenses 11A‐D must be associated with a type

injury

The Victim for a Sex Offense ‐‐ 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object or 11D ‐ Fondling must have an Injury Type entered.


MV_120 NULL Individual type victim requires an injury type entry

When the Victim Connected to UCR Offense code is a Crime Against Persons, the Victim Type is I ‐ Individual, or one of the following offenses: 100 ‐ Kidnapping/Abduction, 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object, 11D ‐ Fondling, 120 ‐ Robbery, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, or 210 ‐ Extortion/Blackmail, the Injury Type field must have data entered.


MV_13.1 NULL Victim of offenses 13A, 13B, 13C, or 13D must be an 'I' or 'L' type victim

The Victim Type for 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation or 13D ‐ Stalking offense must be an Individual.


MV_13.2 NULL Victim of offenses 13A and 13B must be associated with a type injury

The Victim segment for an 13A ‐ Aggravated Assault or 13B ‐ Simple Assault must have an Injury Type entered.



131

Tennessee FBI Description Error Error Number Number MV_13A NULL Victim of 13A requires homicide circumstance entry

The Victim segment of 13A ‐ Aggravated Assault must have an entry in the Aggravated Assault/Homicide Circumstances field.


MV_210 NULL Victim of offense 210 must be an 'I' type victim

The Victim of a 210 ‐ Extortion/Blackmail offense must be an Individual.

Suggested action: Change the Victim Type to Individual or change offense classification based upon incident circumstances.

MV_35 NULL Victim of a 35A or 35B offense must be an 'S' type victim

The Victim Type for 35A ‐ Drug/Narcotics Violation or 35B ‐ Drug Equipment Violation must be S ‐ Society.

Suggested action: Change the Victim Type to Society or change offense classification based upon incident circumstances.

MV_36 NULL Victim of offenses 36A or 36B must be an 'I' type victim

The Victim Type for 36A ‐ Incest or 36B ‐ Statutory Rape must be an Individual.


MV_370 NULL Victim of offense 370 must be an 'S' type victim

The Victim Type of a 370 ‐ Pornography/Obscene Material offense must be S ‐ Society.



132

Tennessee FBI Description Error Error Number Number MV_39 NULL Victim of offenses 39A‐D must be an 'S' type victim

The Victim Type of a 39A – D Gambling Offense must be S ‐ Society.


MV_40 NULL Victim of offenses 40A‐C must be an 'S' type victim

The Victim Type of a 40A – C Prostitution offense must be S ‐ Society.


MV_520 NULL Victim of offense 520 must be an 'S' type victim

The Victim Type of a 520 ‐ Weapon Law Violations offense must be S ‐ Society.


MV_64 NULL Victim of offenses 64A‐B must be an 'I' type victim

The Victim Type of a 64A – B Human Trafficking offense must be I ‐ Individual.


TN_401.1 LEOKA Incident Type entry is required with Victim Type L

If the Type Victim entered is L ‐ Law Enforcement Official, an entry is required in the LEOKA Incident Type field.

Suggested action: Based on incident circumstances, enter information into LEOKA fields or change Victim Type.


133

Tennessee FBI Description Error Error Number Number TN_401.10 Transported to Safety is not allowed

Data entry in the Transported to Safety field is not allowed. The Incident Offense or Victim to Offender Relationship are not valid for Domestic Violence.

Suggested action: Based on incident circumstances, edit the Incident Offense or the Victim to Offender relationship or delete data entered in the Transported to Safety field.

TN_401.11 Order of Protection Violation is not allowed

Data may not be entered in this field unless Transported to Safety is Y or N.

Suggested action: Based upon incident circumstances, edit Transported to Safety to either Y or N or delete the entry in Order of Protection Violation field.

TN_401.4 Entry for Campus Code must be Y or N if ORI is not a college/university

The entry for campus code must be "Y" or "N" for On Campus if the ORI is not a college/university and the victim attends a college/university in that county.

Suggested action: Enter a valid code of "Y" or "N" based on circumstances of the incident.

TN_401.5 School Code entry is valid only for non‐college agencies

The entry for college name may only be completed if the ORI is not a college/university.

Suggested action: Delete the data entered in the college name field.


134

Tennessee FBI Description Error Error Number Number TN_401.6 Transported to safety is required for specified offense and

victim to offender relationship

If the incident involves domestic violence, an entry in the Victim Transported to Safe Place field is required. Valid entries are "Y" or "N".

Suggested action: Based on incident circumstances either delete the entry in Transported to Safe Place field or enter a valid code in the specified field.

TN_401.7 Transported to Safety is required when Domestic Violence is Y

If Domestic Violence = "Y", an entry in the Victim Transported to Safe Place field is required. Valid entries are "Y" or "N".

Suggested action: Based on incident circumstances either delete the entry in Domestic Violence field or enter a valid code in the specified field.

TN_401.8 Transported to Safety is required with domestic violence entry

If the incident involves domestic violence, an entry in the Victim Transported to Safe Place field is required. Valid entries are "Y" or "N".

Suggested action: Based on incident circumstances either delete the entry in Transported to Safe Place field or enter a valid code in the specified field.

TN_401.9 Violation of Order of Protection is required with Domestic Violence entry

If the incident involves domestic violence, an entry in the Violation of Order of Protection field is required. Valid entries are "Y" or "N".

Suggested action: Based on incident circumstances either delete the entry in Violation of Order of Protection field or enter a valid code in the specified field.


135

Tennessee FBI Description Error Error Number Number TN_404.4 Entry for school code must be a valid TN state school code

The School Code field must contain a valid school code from the Tennessee School Code table.

Suggested action: Enter a valid school code.

TN_404.6 Entry for classification must be S,F,G, or O when entered and agency is a college

The Classification field may only be used by Colleges/Universities and the only valid entries are S ‐ Student, F ‐ Faculty, G ‐ Guard, and O ‐ Other.

Suggested action: Based on incident circumstances and if the reporting entity is a college/university, enter a valid code. If the reporting entity is not a college/university, remove entry from the field.

TN_404.7 Entry for Transportation must be Y or N when entered

Please change the entry to a valid code.


TN_404.8 Entry for Violation of Order of Protection must be Y or N when entered

Please change the entry to a valid code.



136

Tennessee FBI Description Error Error Number Number TN_405.1 Entry for Transportation is only allowed with offenses

09A,11A‐D,13A‐D,36A‐B

The Victim Transported to a Safe Place field must be blank unless one of the following offenses is present: 09A ‐ Murder/Non‐negligent Manslaughter, 100 – Kidnapping/Abduction, 11A ‐ Rape, 11B ‐ Sodomy, 11C ‐ Sexual Assault With an Object, 11D ‐ Fondling, 13A ‐ Aggravated Assault, 13B ‐ Simple Assault, 13C ‐ Intimidation, 13D ‐ Stalking, 36A ‐ Incest or 36B ‐ Statutory Rape.

Suggested action: Based on incident circumstances, either remove the entry from Transported to Safe Place field or change the offense classification.

TN_405.2 Entry for Transportation is only allowed with Victim/Offender Relationships SE,PA,CH,GC,SP,SS,VO,XS,CF,CS,SB,GP,IL,SC,OF,HR, or BG

The Victim Transported to a Safe Place field must be blank unless one of the following Victim to Offender Relationships exist: SE ‐ Spouse, PA ‐ Parent, CH ‐ Child, GC ‐ Grandchild, SP ‐ Stepparent, SS ‐ Stepsibling, VO ‐ Victim was Offender, XS ‐ Ex‐spouse, CF ‐ Child of Boyfriend/Girlfriend, CS ‐ Common Law Spouse, SB ‐ Sibling, GP ‐ Grandparent, IL ‐ In‐law, SC ‐ Stepchild, OF ‐ Other Family Member, HR ‐ Homosexual Relationship, or BG ‐ Boyfriend/Girlfriend. NOTE: Tennessee Specific Error Codes TN_401.1, TN_401.2, TN_401.3 and TN404.3 are now covered under error code numbers 454, 458, 462, 482, and 483.

Suggested action: Based on incident circumstances, either remove the entry from Transported to Safe Place field or change the relationship code.

TN_406 Statutory Rape with Victim to Offender Relationship of Family Invalid

Victim to Offender Relationship within Family cannot be used for this offense.

Suggested action: Based on incident circumstances, edit relationship or change offense.


137

Tennessee FBI Description Error Error Number Number TN_406.1 Domestic Violence Flag is required

If the Incident Offense and Victim to Offender Relationship meet domestic violence criteria, then an entry in the Domestic Violence Flag is required. Valid entries are Y ‐ Yes or N ‐ No.

Suggested action: Based on incident circumstances, if the offense and victim to offender relationship meet the domestic violence criteria, make an entry in the Domestic Violence Flag or edit offense and/or victim to offender relationship.

TN_406.2 Domestic Violence Flag is not allowed

If the Incident Offense and Victim to Offender Relationship do not meet the domestic violence criteria, an entry in the Domestic Violence Flag is not allowed. The field must be blank.

Suggested action: Based on incident circumstances, remove the data from the Domestic Violence Flag or edit the offense and/or victim to offender relationship.

TN_407 Incest with Victim to Offender Relationship as non‐family invalid

Victim to Offender Relationship must be one of the “Within the Family” codes for this offense.

Suggested action: Based on incident circumstances, edit relationship or change offense.

TN_407.1 Previous Domestic Violence Flag is required

If the Domestic Violence Flag is submitted as Y ‐ Yes, an entry in the Previous Domestic Violence Flag is required. Valid entries are Y ‐ Yes or N ‐ No.

Suggested action: Based on incident circumstances, either remove the Domestic Violence Flag entry of Y ‐ Yes, or enter valid data in the Previous Domestic Violence Flag.


138

Tennessee FBI Description Error Error Number Number TN_407.2 Previous Domestic Violence Flag is not allowed

If the Domestic Violence Flag is blank or submitted as N ‐ No, the Previous Domestic Violence Flag must be blank.

Suggested action: Based on incident circumstances, either remove the Previous Domestic Violence Flag entry or enter Y ‐ Yes in the Domestic Violence Flag entry.

TN_408 ORI in the "Other LEOKA" field in Victim segment invalid

The ORI number used in this data field cannot be the same as the submitting agency ORI. The ORI number used must be a valid 9 character number with correct two digit state code.

Suggested action: Based on incident circumstances, edit ORI number or delete data entered in the field.

TN_409 Victim of offense 09D – Negligent Vehicular Manslaughter must be an 'I' type victim

The Victim Type of a 09D ‐ Negligent Vehicular Manslaughter offense must be I ‐ Individual.


TN_409.1 Victim Age is missing

Victim Age must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Age or edit Victim Type and resubmit the incident.

TN_409.2 Victim Sex is missing

Victim Sex must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Sex or edit Victim Type and resubmit the incident.


139

Tennessee FBI Description Error Error Number Number TN_409.3 Victim Race is missing

Victim Race must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Race or edit Victim Type and resubmit the incident.

TN_409.4 Victim Ethnicity is missing

Victim Ethnicity must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Ethnicity or edit Victim Type and resubmit the incident.

TN_409.5 Resident status is missing

Victim Resident Status must be present when the Victim Type is I = Individual.

Suggested action: Enter valid Victim Resident Status or edit Victim Type and resubmit the incident.

OFFENDER SEGMENT ERRORS


The Agency ORI number must be entered.



The Incident Number must be entered.



140

Tennessee FBI Description Error Error Number Number 501.3 501 Offender Sequence Number is missing

The Offender Sequence Number must be entered with a numeric value.

Suggested action: Enter the Offender Sequence Number using a numeric value 00 ‐ 99.

501.4 501 Offender Age is missing

The Offender Age must be entered.

Suggested action: Enter valid Offender Age or age range in a numeric entry (01 ‐ 99) and resubmit the incident.

501.5 501 Offender Sex is missing

The Offender Sex must be entered.

Suggested action: Enter valid Offender Sex and resubmit the incident.

501.6 501 Offender Race is missing

The Offender Race must be entered.

Suggested action: Enter valid Offender Race and resubmit the incident.

501.7 Offender Ethnicity is missing

The Offender Ethnicity must be entered.

Suggested action: Enter valid Offender Ethnicity and resubmit the incident.

502 502 Offender Sequence Number is non‐numeric

The Offender Sequence Number must be entered with a numeric value (00 ‐ 99) with zero left‐fill.

Suggested action: Enter a valid Offender Sequence number and resubmit the incident.


141

Tennessee FBI Description Error Error Number Number 504.1 504 Offender Sex is invalid

The Offender Sex must be entered.

Suggested action: Enter valid Offender Sex and resubmit the incident.

504.2 504 Offender Race is invalid

The Offender Race must be entered.

Suggested action: Enter valid Offender Race and resubmit the incident.

504.3 Offender Ethnicity is invalid

The Offender Ethnicity must be entered.

Suggested action: Enter valid Offender Ethnicity and resubmit the incident.

508 508 Offender Age is not left‐justified

Age of Offender contains data but is not left‐justified. A single two‐character age must be in positions 1 through 2 of the field.

Suggested action: Enter valid age and ensure that a numeric age is in the first two places in the field. Contact your vendor if necessary.

509 509 Offender Age is non‐numeric

Age of Offender contains more than two characters indicating a possible age‐range is being attempted. If so, the field must contain a numeric entry of four digits.

Suggested action: Enter valid age range containing 4 digits and resubmit the incident. Contact your vendor if necessary.

510 510 First Age must be less than second for Age Range

Age of Offender was entered as an age‐range. Accordingly, the first age component must be less than the second age.


142

Tennessee FBI Description Error Error Number Number Suggested action: Enter a correct age range with the lowest

age in the first two positions and resubmit the incident. Contact your vendor if necessary.



Suggested action: Remove blanks at beginning of Incident Number and resubmit. If the Incident Number is automatically generated, contact your vendor about the issue.


Incident Number must be left‐justified with blank right‐fill. Since the number is less than 12 characters, it must begin in position 1; one or more blanks were entered starting in position 1 followed by the data.




Suggested action: Use only Incident Numbers that conform to the parameter for the Incident Number which include: capital letters only, numerals, hyphens or blanks at the end of the Incident Number (no blanks within the Incident Number or at the beginning). If Incident Number is automatically generated, contact your vendor about the issue.

522 522 Offender Age Range cannot start with a '00'

Age of Offender was entered as an age‐range. Therefore, the first age component cannot be unknown (00).


143

Tennessee FBI Description Error Error Number Number Suggested action: If Offender Age is unknown, leave

completely blank. If an age or age range is known, first age must be greater than 00.

550 550 Offender is a spouse but Age is less than 10

Relationship of Victim to Offender contains a relationship of spouse. When this is so, the age of the Offender cannot be less than 10 years.

Suggested action: Review the incident report and either change the age of the Offender or the relationship between the Victim and the Offender.

551 551 Duplicate Offender Segment

When a Group A Incident Report is submitted, the individual segments comprising the incident cannot contain duplicates. In this case, two Offender Segments were submitted having the same entry in the Offender Sequence Number.

Suggested action: Delete one Offender or check with your vendor since Offender Sequence numbers should be automatically and sequentially generated.

552.1 552 For Unknown Offender '00', Age is invalid

Age of Offender cannot be entered when the Offender Sequence Number is 00 ‐ Unknown.

Suggested action: If age is known, Offender Sequence Number cannot be 00. If sequence number is 00, age must be blank.

552.2 552 For Unknown Offender '00', Sex is invalid

Sex of Offender cannot be entered when the Offender Sequence Number is 00 ‐ Unknown.

Suggested action: If sex is known, Offender Sequence Number cannot be 00. If sequence number is 00, sex must be blank.


144

Tennessee FBI Description Error Error Number Number 552.3 552 For Unknown Offender '00', Race is invalid

Race of Offender cannot be entered when the Offender Sequence Number is 00 ‐ Unknown.

Suggested action: If race is known, Offender Sequence Number cannot be 00. If sequence number is 00, race must be blank.

552.4 552 For Unknown Offender '00', Ethnicity is invalid

Ethnicity of Offender cannot be entered when the Offender Sequence Number is 00 ‐ Unknown.

Suggested action: If ethnicity is known, Offender Sequence Number cannot be 00. If sequence number is 00, ethnicity must be blank.

553.1 553 Sex of the Victim and the Offender cannot be the same

Relationship of Victim to Offender has a relationship that is inconsistent with the offender's sex. The sex of the Victim and/or Offender must reflect the implied relationship. For example, if the relationship of the Victim to the Offender is spouse, then victim's sex cannot be the same as the offender's sex. The following relationships must reflect either the Same or Different sex code depending upon the relationship: BG ‐ Victim was Boyfriend/Girlfriend ‐ different sex code, XS ‐ Victim was Ex‐Spouse ‐ different sex code, SE ‐ Victim was Spouse – different sex code, CS ‐ Victim was Common‐Law Spouse ‐ different sex code.

Suggested action: Review Offender and Victim information and make necessary changes based on codes above.


145

Tennessee FBI Description Error Error Number Number 553.2 553 Sex of the Victim and the Offender must be the same

Relationship of Victim to Offender has a relationship that is inconsistent with the offender's sex. The sex of the Victim and/or Offender must reflect the implied relationship. For example, if the relationship of the Victim to the Offender is spouse, the victim's sex cannot be the same as the offender's sex. The following relationships must reflect either the Same or Different sex code depending upon the relationship: HR ‐ Homosexual Relationship ‐ same sex code.

Suggested action: Review Offender and Victim information and make necessary changes based on codes above.

554.1 554 For Relationship of PA, or GP Victim must be older than Offender

Relationship of Victim to Offenders has a relationship that is inconsistent with the offender's age. The age of the Victim and/or Offender must reflect the implied relationship. For a relationship of PA ‐ Victim was Parent or GP ‐ Victim was Grandparent, the Victim Age should be older.

Suggested action: Review Offender and Victim information and edit relationship or age as needed and resubmit the incident.

554.2 554 For Relationship of CH, or GC Victim must be younger than Offender

Relationship of Victim to Offenders has a relationship that is inconsistent with the offender's age. The age of the Victim and/or Offender must reflect the implied relationship. For a relationship of CH ‐ Victim was Child or GC ‐ Victim was Grandchild, the Victim Age should be younger.



146

Tennessee FBI Description Error Error Number Number 554.3 554 For Relationship of VO Victim must be same age

Relationship of Victim to Offenders has a relationship that is inconsistent with the offender's age. The age of the Victim and/or Offender must reflect the implied relationship. For a relationship of VO ‐ Victim was Offender, the Victim Age and Offender Age must be the same.


555 555 Offender '00' exists ‐‐ cannot submit more offenders

When multiple Offender segments are submitted, none can contain a 00 ‐ unknown value because the presence of 00 indicates that the number of offenders is unknown. In this case, multiple offenders were submitted, but one of the segments contains the 00 ‐ unknown value.

Suggested action: Either delete all offenders or change Offender Sequence Number of Offender who has "00" to a sequential number based on other offenders. Check with your vendor.

556 556 Age format invalid

Age of Offender must entered in numeric format. Valid data format: 00 ‐ 99.

Suggested action: Enter age in numeric digits. Check with your vendor.

557 557 If incident is Cleared Exceptionally then Offender Sequence Number cannot be '00'

Offender Sequence Number contains 00 indicating that nothing is known about the offender(s) regarding the number and any identifying information. In order to exceptionally clear the incident, the value cannot be 00. The incident was submitted with the Cleared Exceptionally field having a value of A ‐ E.


147

Tennessee FBI Description Error Error Number Number Suggested action: Either enter an offender sequence number

of "01" or delete the entry in the Cleared Exceptionally field. Check with your vendor.

558 558 At least one offender must have known values

None of the Offender segments contain all known values for age, sex, race and ethnicity. When an incident is cleared exceptionally, one offender must have all known values.

Suggested action: Enter age, race, sex, and ethnicity for one offender or change Exceptional Clearance Indicator to "Not Applicable" and resubmit.

559.1 559 For offense 09C, Offender Sequence Number cannot be '00'

The incident was submitted with the UCR Offense of 09C ‐ Justifiable Homicide but the Offender Sequence number submitted was 00 ‐ unknown. At least one of the offenders must have known information for age, sex, race, and ethnicity.

Suggested action: Edit Offender Sequence Number and enter age, race, sex, and ethnicity for one offender or change UCR Offense.

559.2 559 For offense 09C, Offender Age cannot be '00', Sex cannot be Unknown, and Race cannot be Unknown

The incident was submitted with the UCR Offense of 09C ‐ Justifiable Homicide but unknown information was submitted for all the offender(s). At least one of the offenders must have known information for age, sex, race, and ethnicity.

Suggested action: Enter age, race, sex, and ethnicity for one offender.

560 560 Victim's Sex cannot be same as all Offenders for offenses of 11A

The Victim was connected to the Rape offense but had the same sex as the offender(s) submitted for the incident. At least one offender must have a different sex than the Victim.

Suggested action: Edit at least one Offender or the Victim Sex to be opposite of each other.


148


TENNESSEE SPECIFIC OFFENDER SEGMENT ERRORS

TN_561 Juvenile offenders involving prostitution must be reported as victims of Human Trafficking ‐ Commercial Sex Acts (64A)

The incident offense is one of the Prostitution offenses and the submitted offender is a juvenile. If the offender in an incident involving Prostitution is a juvenile, then the incident must be reported with the UCR Offense of 64A ‐ Human Trafficking ‐ Commercial Sex Acts and the juvenile offender is reported as a victim of the 64A ‐ Human Trafficking ‐ Commercial Sex Acts.

Suggested action: Edit the offense to 64A ‐ Commercial Sex Acts.

GROUP A ARRESTEE SEGMENT ERRORS


The Agency ORI number must be entered.


601.11 601 Arrestee Sex is missing

The Arrestee Sex must be entered.

Suggested action: Enter the Arrestee Sex and resubmit the incident.

601.12 601 Arrestee Race is missing

The Arrestee Race must be entered.

Suggested action: Enter the Arrestee Race and resubmit the incident.

601.13 Arrestee DOB is required

The Arrestee Date of Birth must be entered.

Suggested action: Enter the Arrestee DOB and resubmit the incident.


149

Tennessee FBI Description Error Error Number Number 601.14 601 Arrestee Age is missing

The Arrestee Age must be entered.

Suggested action: Enter the Arrestee Age and resubmit the incident.


The Incident Number must be entered.


601.3 601 Arrestee Sequence Number is missing

The Arrestee Sequence Number must be entered.

Suggested action: Enter the Arrestee Sequence Number and resubmit the incident.

601.4 601 Arrestee Transaction Number is missing

The Arrestee Transaction Number must be entered.

Suggested action: Enter the Arrestee Transaction Number and resubmit the incident.

601.5 601 Arrest Date is missing

The Arrest Date must be entered.

Suggested action: Enter the Arrest Date and resubmit the incident.

601.6 601 Arrest Type is missing

The Arrest Type must be entered.

Suggested action: Enter the Arrest Type and resubmit the incident.


150

Tennessee FBI Description Error Error Number Number 601.7 601 Multiple Arrest Clearance is missing

The Arrest Clearance must be entered.

Suggested action: Enter the Arrest Clearance and resubmit the incident.

601.8 601 Arrest Offense Code is missing

The Arrest Offense Code must be entered.

Suggested action: Enter the Arrest Offense Code and resubmit the incident.

601.9 601 Arrestee Armed With entry is missing

The Arrestee Armed With entry must be entered.

Suggested action: Enter the Arrestee Armed With and resubmit the incident.

602 602 Arrestee Sequence Number is non‐numeric

The Arrestee Sequence Number must be numeric entry of 01 ‐ 99 with zero left‐fill.

Suggested action: Remove blanks at the beginning of sequence number and resubmit. If non‐numeric entry such as alpha characters is in the number, remove as well. If the sequence number is automatically generated, contact your vendor about the issue.

604.1 604 Invalid Arrest Offense Code

The Arrest Offense Code is not a valid TIBRS Offense Code.

Suggested action: Review the incident and edit the Arrest Offense Code to a valid TIBRS Offense Code.


151

Tennessee FBI Description Error Error Number Number 604.12 604 Invalid Juvenile Disposition entry

The Juvenile Disposition entry is not a valid TIBRS Code.

Suggested action: Enter the Juvenile Disposition entry using one of the following valid codes: H ‐ Handled Within Department or R ‐ Referred to Other Authorities.

604.2 604 Invalid Arrest Type

The Arrest Type entry is not a valid TIBRS Code.

Suggested action: Enter the Arrest Type using one of the following codes: O ‐ On View, S ‐ Summoned/Cited or T ‐ Taken Into Custody. If the agency is a college/university, the Arrest Type of R – Referred to Institution Authority may also be used.

604.3 604 Invalid Multiple Arrestee Segments Indicator

The Multiple Arrestee Segment Indicator is not a valid TIBRS Code.

Suggested action: Enter the Multiple Arrestee Segment Indicator using one of the following codes: C ‐ Count Arrestee, M ‐ Multiple, or N ‐ Not Applicable.


The Arrest Offense Code is not a valid UCR Offense Code.

Suggested action: Review the incident and edit the Arrest Offense Code to a valid UCR Offense Code.

604.5 604 Invalid Arrestee Armed With entry

The Arrestee Armed With entry is not a valid TIBRS code.


152

Tennessee FBI Description Error Error Number Number Suggested action: Enter the Arrestee Armed With using one

of the following codes: 01 ‐ Unarmed, 11 ‐ Firearm ‐ Type Unknown, 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, 15 ‐ Other Firearm, 16 ‐ Lethal Cutting Instrument, or 17 ‐ Club/Blackjack/Brass Knuckles. NOTE: When applicable, an "A" is placed after the code to indicate that the Firearm was an Automatic Weapon.


The Arrestee Armed With entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Armed With using one of the following codes: 01 ‐ Unarmed, 11 ‐ Firearm ‐ Type Unknown, 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, 15 ‐ Other Firearm, 16 ‐ Lethal Cutting Instrument, or 17 ‐ Club/Blackjack/Brass Knuckles. NOTE: When applicable, an "A" is placed after the code to indicate that the Firearm was an Automatic Weapon.

604.7 604 Invalid Arrestee Race

The Arrestee Race entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Race using one of the following codes: W ‐ White, B ‐ Black or African American, I ‐ American Indian or Alaska Native, A ‐ Asian, P ‐ Native Hawaiian or Other Pacific Islander, or U ‐ Unknown.

604.8 604 Invalid Arrestee Ethnicity

The Arrestee Ethnicity entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Ethnicity using one of the following codes: H ‐ Hispanic or Latino, N – Not Hispanic or Latino, or U ‐ Unknown.

604.9 604 Invalid Arrestee Resident Status

The Arrestee Resident Status entry is not a valid TIBRS Code.


153

Tennessee FBI Description Error Error Number Number Suggested action: Enter the Arrestee Resident Status using

one of the following codes: R ‐ Resident, N ‐ Non‐Resident, or U ‐ Unknown.

605.1 605 Arrest Date invalid ‐ YEAR

The Arrest Date Year is invalid.

Suggested action: Enter the correct Arrest Date year (using four numeric characters) and resubmit the incident.

605.2 605 Arrest Date invalid ‐ MONTH

The Arrest Date month is invalid.

Suggested action: Enter the correct Arrest Date month (using two digit numeric characters, 01 ‐ 12) and resubmit the incident.

605.3 605 Arrest Date invalid ‐ DAY

The Arrest Date Day is invalid.

Suggested action: Enter the correct Arrest Date Day (using two digit numeric characters, 01 – 31) and resubmit the incident.

605.4 605 Arrest Date cannot predate Incident Date

Arrest Date cannot be earlier than Incident Date/Hour. A person cannot be arrested before the Incident occurred.

Suggested action: Enter correct arrest date or correct incident date and resubmit the incident.

605.5 605 Arrest Date cannot be after current date

The Arrest Date entered cannot be later than the current day's date.

Suggested action: Review the incident report and enter valid Arrest Date and resubmit the incident.


154

Tennessee FBI Description Error Error Number Number 605.6 605 Arrest Date is non‐numeric

The Arrest Date must be entered using numeric characters. Months must be between 01 ‐ 12, Days must be between 01 ‐ 31, and Year must be four numeric digits. Additionally, days cannot exceed maximum for the month ‐ ex. June cannot have 31 days.


605.7 605 Arrest Date invalid ‐ Cannot be after TapeDate

The Arrest Date entered cannot be later than that entered within the month of Tape and Year of Tape.


606 606 Duplicate Arrestee Armed With entry

Arrestee Armed With contains multiple data values. When more than one code is entered, none can be duplicate codes.

Suggested action: Remove duplicate entry and if applicable select a different weapon type and resubmit the incident. Contact your vendor if necessary.

607.1 607 Arrestee Armed With entry of 01 is exclusive

Arrestee was Armed With can have multiple data values and was entered with multiple values. However, the entry of code 01 ‐ Unarmed cannot be entered with any other data value.

Suggested action: If "None" is selected, no other weapons can be selected. Delete other weapons or change "None" to other type weapon based on incident circumstances.




155

Tennessee FBI Description Error Error Number Number Suggested action: If "None" is selected, no other weapons

can be selected. Delete other weapons or change "None" to other type weapon based on incident circumstances.

608 608 Arrestee Age must be left‐justified

Age of Arrestee contains data but is not left‐justified. A single two‐character age must be in positions 1 ‐ 2 of the field.

Suggested action: Enter valid age and ensure that a numeric age is in the first two places in the file. Contact your vendor if necessary.

609 609 Arrestee Age must be either 2 or 4 digits

Age of Arrestee contains more than two characters indicating a possible age‐range is being attempted. If so, the field must contain a numeric entry of four digits.

Suggested action: Enter valid age range containing 4 digits. Contact your vendor if necessary.


Age of Arrestee was entered as an age‐range. Accordingly, the first age component must be less than the second age.


615.1 615 Incident Number contains embedded blanks




156

Tennessee FBI Description Error Error Number Number 615.2 615 Arrestee Transaction Number contains embedded blanks

Arrestee Transaction Number contains embedded blanks between the first and last significant number.

Suggested action: Remove blanks at beginning of Arrestee Transaction Number and resubmit. If the Arrestee Transaction Number is automatically generated, contact your vendor about the issue.

616.1 616 Incident Number must be left justified

The Incident Number must be left‐justified; one or more blanks were entered in starting position 1 followed by the data.


616.2 616 Arrestee Transaction Number must be left justified

The Arrestee Transaction Number must be left‐justified; one or more blanks were entered in starting position 1 followed by the data.

Suggested action: Remove blanks at the beginning of the Arrestee Transaction Number and resubmit. If the Arrestee Transaction Number is automatically generated, contact your vendor about the issue.

617.1 617 Incident Number contains invalid characters




157

Tennessee FBI Description Error Error Number Number 617.2 617 Arrestee Transaction Number contains invalid characters

The Arrestee Transaction Number can only have character combinations of A ‐ Z, 0 ‐ 9, hyphens, and/or blanks. Example 89‐123‐SC is valid, but 89+123*SC is invalid.

Suggested action: Use only Arrestee Transaction Numbers that conform to the parameter for the Arrestee Transaction Number which include: capital letters only, numerals, hyphens or blanks at the end of the Arrestee Transaction Number (no blanks within the Arrestee Transaction Number or at the beginning). If the Arrestee Transaction Number is automatically generated, contact your vendor about the issue.

620 620 Arrest Date cannot predate the Base Date

The Arrest Date entered cannot be before the agency began reporting TIBRS data.

Suggested action: Edit the Arrest Date and resubmit the incident.

622 622 Arrestee Age Range cannot start with a '00'

Age of Arrestee was entered as an age‐range. Therefore, the first age component cannot be 00 ‐ unknown.

Suggested action: If Arrestee Age is unknown, leave completely blank. If an age or age range is known, the first age must be greater than 00.

640 640 Warning ‐ No Disposition for possible Juvenile Arrestee

Disposition of Arrestee Under 18 was not entered, but the Age of Arrestee indicates an age‐range for a juvenile. The low age is a juvenile and the high age is an adult, but the average age is a juvenile. NOTE: When an age‐range is not entered and the age is a juvenile, the disposition must be entered. These circumstances were flagged by the computer as a possible discrepancy between age and disposition and should be checked for possible correction by the agency.

Suggested action: Based on incident circumstances, edit Arrestee Age or age‐range to 18 or over (including average of age range) or enter Juvenile Disposition information.


158

Tennessee FBI Description Error Error Number Number 641 641 Warning ‐ Arrestee had an Age of 99 or older

The Age of Arrestee was entered with a value of 99 which means that the Arrestee was over 98 years of age. Verify that the submitter of data is not confusing the 99 ‐ Over 98 years old with 00 ‐ Unknown.

Suggested action: Please verify that the Arrestee Age was entered correctly. Make changes if necessary and resubmit the incident.

652 652 Juvenile Disposition must be entered when Arrestee Age is less than 18

Disposition of Juvenile was not entered but Age of Arrestee is under 18. Whenever an Arrestee Age indicates a juvenile (01 ‐ 17), the disposition must be entered.

Suggested action: Verify Arrestee is under 18 and if correct, enter Juvenile Disposition and resubmit the incident.

653 653 Juvenile Disposition not allowed

Disposition of Juvenile was entered, but Age of Arrestee is 18 or greater. Whenever an Arrestee Age indicates an adult, the juvenile disposition cannot be entered because it does not apply.

Suggested action: Verify the Arrestee is older than 17, and if correct, remove Juvenile Disposition entry.

654.1 654 Automatic Weapon Indicator must be A or blank

Arrestee was Armed With does not have "A" or a blank in the third position.

Suggested action: Incorrect data entered in Automatic Weapon Indicator. Either enter "A: if automatic weapon or leave field blank. Resubmit the incident.


159

Tennessee FBI Description Error Error Number Number 654.2 654 Automatic Weapon Indicator must be A or blank



655.1 655 Automatic Weapon Indicator only valid with Weapons 11 ‐ 15

In the Arrestee Armed With field, the third position is for "A" ‐ automatic weapon. It is valid only with the following weapon types: 11 ‐ Firearm (type not stated), 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, or 15 ‐ Other Firearm. A weapon code other than those mentioned was entered with the automatic indicator. An automatic weapon is, by definition, a firearm.

Suggested action: Remove the entry from "automatic weapon indicator" field or change the weapon type to a firearm type weapon and resubmit the incident.

655.2 655 Automatic Weapon Indicator only valid with Weapons 11 – 15


Suggested action: Remove the entry from "automatic weapon indicator" field or change the weapon type to a firearm type weapon and resubmit the incident.


160

Tennessee FBI Description Error Error Number Number 656 656 For Group A Incidents the number of Arrestees cannot

exceed the number of offenders

A Group A Incident Report was submitted with more arrestees than Offenders. The number (nn) of Offenders is shown within the message. The incident must be resubmitted with additional Offender segments. This message will also occur if an arrestee was submitted and the Offender Sequence Number was 00 ‐ unknown.

Suggested action: Check the number of offenders shown in the error message. Either add more offenders to correspond to the number of arrestees or delete arrestees ‐ based on incident circumstances.

660 660 Previous incident must exist on file

An Arrestee segment was submitted with Segment Action Type A ‐ Add must correspond to an incident already on file.

Suggested action: Verify the Incident previously submitted did not error out. Resubmit the entire Incident including the updated Arrestee data.

661 661 Duplicate Arrestee Segments on file

When a Group A Incident Report is submitted, the individual segments comprising the incident cannot contain duplicates. In this case, two Arrestee Segments were submitted having the same entry in the Arrestee Sequence Number.

Suggested action: Delete one Arrestee or check with your vendor since Arrestee Sequence numbers should be automatically and sequentially generated.

664 664 Arrestee Age is non‐numeric

Age of Arrestee does not contain a numeric entry of 01 ‐ 99 for an exact age.

Suggested action: Enter Arrestee Age in numeric digits (01 ‐ 99). Check with your vendor.


161

Tennessee FBI Description Error Error Number Number 665 665 Arrest Date precedes Incident Date

Arrest Date cannot be earlier than Incident Date/Hour. A person cannot be arrested before the incident occurred.

Suggested action: Enter correct arrest date or correct Incident Date and resubmit the incident.

667 667 Arrestee Sex is invalid

Arrestee Sex does not contain a valid code of M ‐ Male or F ‐ Female. NOTE: U ‐ Unknown is not valid for an Arrestee.

Suggested action: Enter valid code for sex "M" or "F" only and resubmit the incident.

669 669 Arrestee Segment not allowed with offense 09C

Group A Incident Reports cannot have arrests when the Offense is a Justifiable Homicide. By definition, a Justifiable Homicide never involves an arrest of the Offender (the person who committed the Justifiable Homicide).

Suggested action: Remove Arrestee from the Incident. If more than one Offense entered in the Incident including the Justifiable Homicide offense, delete the Justifiable Homicide offense and submit it as a separate Incident.

670 670 Arrestee Offense Code cannot be Justifiable Homicide (09C)

The Arrest Offense Code was entered as Justifiable Homicide. This is not a valid Arrest Offense.

Suggested action: Edit the Arrest Offense Code to a valid Offense or remove the arrest record if this is a single Offense of Justifiable Homicide.


162


TENNESSEE SPECIFIC GROUP A ARRESTEE SEGMENT ERRORS

TN_601.2 Entry for warrant is required when Transportation field is not blank

The Warrant Signed By field in the Arrestee Segment cannot be blank if an entry is made in the Victim Transported to a Safe Place field in the Victim Segment.

Suggested action: Based on incident circumstances, either enter a valid code in the Warrant Signed By field in the Arrestee segment or delete the Victim Transported to Safe Place entry in the Victim segment. NOTE: Several conditions must be met to remove the entry in Victim Transported to Safe Place field. Please see error message numbers TN_404.7, TN_404.8, TN_405.1 and TN_405.2.

TN_604.1 Invalid data value ‐ Entry for warrant must be V, O, or B

The only valid entries for the Warrant Signed By field are: V ‐ Victim, O ‐ Officer, or B ‐ Both (Victim and Officer).

Suggested action: Based on incident circumstances, enter a valid code for Warrant Signed By field or leave blank.

TN_605 Juvenile arrests for prostitution must be reported as victims of Human Trafficking ‐ Commercial Sex Acts (64A)

The incident offense is one of the Prostitution offenses and the submitted arrestee is a juvenile. If the arrestee in an incident involving Prostitution is a juvenile, then the incident must be reported with the UCR Offense of 64A ‐ Human Trafficking ‐ Commercial Sex Acts and the juvenile arrestee is reported as a victim of the Human Trafficking ‐ Commercial Sex Acts.

Suggested action: Edit the offense to 64A ‐ Commercial Sex Acts and enter the juvenile demographic data in the Victim segment.

TN_606 Arrest type of “R” may only be submitted by a college/university ORI.

An arrest segment was submitted with an arrest type of “R” and the submitting ORI/agency is not a college/university. Arrest type of “R” may only be submitted by a college/university ORI. All other ORIs must use O, S, and T.


163

Tennessee FBI Description Error Error Number Number Suggested action: Based upon incident circumstances, edit

the Arrestee segment and enter a valid arrest type.

GROUP B ARRESTEE SEGMENT ERRORS


The ORI number for the agency must be entered; it is required.

Suggested action: Enter ORI number and resubmit the incident.

701.11 Arrestee DOB is required

The Arrestee DOB must be entered; it is required.

Suggested action: Enter Arrestee DOB and resubmit the incident.

701.12 701 Arrestee Race is missing

The Arrestee Race must be entered; it is required.

Suggested action: Enter valid Arrestee Race and resubmit the incident.

701.2 701 Arrestee Sequence Number is missing

The Arrestee Sequence Number must be entered; it is required.

Suggested action: Enter Arrestee Sequence Number and resubmit the incident.

701.3 701 Arrestee Transaction Number is missing

The Arrestee Transaction Number must be entered; it is required.

Suggested action: Enter the Arrestee Transaction Number and resubmit the incident.


164

Tennessee FBI Description Error Error Number Number 701.4 701 Arrest Date is missing

The Arrest Date must be entered; it is required.

Suggested action: Enter the Arrest Date and resubmit the incident.

701.5 701 Arrest Type is missing

The Arrest Type must be entered; it is required.

Suggested action: Enter the Arrest Type and resubmit the incident.

701.6 701 Arrest Offense Code is missing

The Arrest Offense Code must be entered; it is required.

Suggested action: Enter the Arrest Offense Code and resubmit the incident.

701.7 701 Arrestee Armed With entry is missing

The Arrestee Armed With must be entered; it is required.

Suggested action: Enter the Arrestee Armed With and resubmit the incident.

701.8 701 Arrestee Age is missing

The Arrestee Age must be entered; it is required.

Suggested action: Enter the Arrestee Age and resubmit the incident.

701.9 701 Arrestee Sex is missing

The Arrestee Sex must be entered; it is required.

Suggested action: Enter the Arrestee Sex and resubmit the incident.


165

Tennessee FBI Description Error Error Number Number 702 702 Arrestee Sequence Number is non‐numeric

The Arrestee Sequence Number must be numeric entry of 01 ‐ 99 with zero left‐fill.

Suggested action: Remove blanks at the beginning of the sequence number and resubmit. If non‐numeric entry such as alpha characters is in the number, remove as well. If the sequence number is automatically generated, contact you vendor about the issue.

704.1 Invalid Arrest Type

The Arrest Type entry is not a valid TIBRS Code.

Suggested action: Enter the Arrest Type using one of the following codes: O ‐ On View, S ‐ Summoned/Cited or T ‐ Taken Into Custody. If the agency is a college/university, the Arrest Type of R – Referred to Institution Authority may also be used.


The Arrest Offense Code is not a valid TIBRS Code.

Suggested action: Review the incident and edit the Arrest Offense Code to a valid TIBRS Group B Offense Code.


The Arrestee Armed With is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Armed With using one of the following codes: 01 ‐ Unarmed, 11 ‐ Firearm ‐ type unknown, 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, 15 ‐ Other Firearm, 16 ‐ Lethal Cutting Instrument, or 17 ‐ Club/Blackjack/Brass Knuckles. NOTE: When applicable, an "A" is placed after the code to indicate that the Firearm was an Automatic Weapon.


166

Tennessee FBI Description Error Error Number Number 704.4 704 Invalid Arrestee Armed With entry

The Arrestee Armed With is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Armed With using one of the following codes: 01 ‐ Unarmed, 11 ‐ Firearm ‐ type unknown, 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, 15 ‐ Other Firearm, 16 ‐ Lethal Cutting Instrument, or 17 ‐ Club/Blackjack/Brass Knuckles. NOTE: When applicable, an "A" is placed after the code to indicate that the Firearm was an Automatic Weapon.

704.5 704 Invalid Arrestee Race

The Arrestee Race entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Race using one of the following codes: W ‐ White, B ‐ Black or African American, I ‐ American Indian or Alaska Native, A ‐ Asian, P ‐ Native Hawaiian or Other Pacific Islander, or U ‐ Unknown.

704.6 704 Invalid Arrestee Ethnicity

The Arrestee Ethnicity entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Ethnicity using one of the following codes: H ‐ Hispanic or Latino, N – Not Hispanic or Latino, or U ‐ Unknown.

704.7 704 Invalid Arrestee Resident Status

The Arrestee Resident Status entry is not a valid TIBRS Code.

Suggested action: Enter the Arrestee Resident Status using one of the following codes: R ‐ Resident, N ‐ Non‐Resident, or U ‐ Unknown.

704.8 704 Invalid Juvenile Disposition entry

The Juvenile Disposition entry is not a valid TIBRS Code.

Suggested action: Enter the Juvenile Disposition entry using one of the following valid codes: H ‐ Handled Within Department or R ‐ Referred to Other Authorities.


167

Tennessee FBI Description Error Error Number Number 705.1 705 Arrest Date invalid ‐ YEAR

The Arrest Date Year is invalid.

Suggested action: Enter the correct Arrest Date year (using four numeric characters) and resubmit the incident.

705.2 705 Arrest Date invalid ‐ MONTH

The Arrest Date month is invalid.

Suggested action: Enter the correct Arrest Date month (using two digit numeric characters, 01 ‐ 12) and resubmit the incident.

705.3 705 Arrest Date invalid ‐ DAY

The Arrest Date Day is invalid.

Suggested action: Enter the correct Arrest Date Day (using two digit numeric characters, 01 ‐ 31) and resubmit the incident.

705.4 705 Arrest Date cannot predate Incident Date

Arrest Date cannot be earlier than Incident Date/Hour. A person cannot be arrested before the Incident occurred.

Suggested action: Enter correct arrest date or correct incident date and resubmit the incident.

705.5 705 Arrest Date cannot be after current date

The Arrest Date entered cannot be later than the current day's date.



168

Tennessee FBI Description Error Error Number Number 705.6 705 Arrest Date is non‐numeric

The Arrest Date must be entered using numeric characters. Months must be between 01 ‐ 12, Days must be between 01 ‐ 31, and Year must be four numeric digits. Additionally, days cannot exceed maximum for the month ‐ ex. June cannot have 31 days.


706 706 Duplicate Arrestee Armed With entry

Arrestee Armed With contains multiple data values. When more than one code is entered, none can be duplicate codes.

Suggested action: Remove duplicate entry and if applicable select a different weapon type and resubmit the incident. Contact your vendor if necessary.







708 708 Arrestee Age must be left‐justified

Age of Arrestee contains data but is not left‐justified. A single two‐character age must be in positions 1 ‐ 2 of the field.


169

Tennessee FBI Description Error Error Number Number Suggested action: Enter valid age and ensure that a numeric

age is in the first two places in the file. Contact your vendor if necessary.



Suggested action: Enter age in numeric digits. Check with your vendor.


Age of Arrestee was entered as an age‐range. Accordingly, the first age component must be less than the second age.






The Incident Number must be left‐justified; one or more blanks were entered in starting position 1 followed by the data.



170

Tennessee FBI Description Error Error Number Number 717 717 Incident Number contains invalid characters



720 720 Arrest Date cannot predate the Base Date

The Arrest Date entered cannot be before the agency began reporting TIBRS data.

Suggested action: Edit the Arrest Date and resubmit the incident.

722 722 Arrestee Age Range cannot start with a '00'

Age of Arrestee was entered as an age‐range. Therefore, the first age component cannot be 00 ‐ unknown.

Suggested action: If Arrestee Age is unknown, leave completely blank. If an age or age range is known, the first age must be greater than 00.

740 740 Warning ‐ No Disposition for possible Juvenile Arrestee

Disposition of Arrestee Under 18 was not entered, but the Age of Arrestee indicates an age‐range for a juvenile. The low age is a juvenile and the high age is an adult, but the average age is a juvenile. NOTE: When an age‐range is not entered and the age is a juvenile, the disposition must be entered. These circumstances were flagged by the computer as a possible discrepancy between age and disposition and should be checked for possible correction by the agency.

Suggested action: Based on incident circumstances, edit Arrestee Age or age‐range to 18 or over (including average of age range) or enter Juvenile Disposition information.


171

Tennessee FBI Description Error Error Number Number 741 741 Warning ‐ Arrestee had an Age of 99 or older

The Age of Arrestee was entered with a value of 99 which means that the Arrestee was over 98 years of age. Verify that the submitter of data is not confusing the 99 ‐ Over 98 years old with 00 ‐ Unknown.

Suggested action: Please verify that the Arrestee Age was entered correctly. Make changes if necessary and resubmit the incident.

751 751 Arrestee Transaction Number already exists

The Arrestee Transaction Number already exists and was previously submitted.

Suggested action: Enter a valid Arrestee Transaction Number, without entering duplicate numbers, and resubmit the incident.

752 752 Juvenile Disposition must be entered when Arrestee Age is less than 18

Disposition of Juvenile was not entered but Age of Arrestee is under 18. Whenever an Arrestee Age indicates a juvenile (01 ‐ 17), the disposition must be entered.

Suggested action: Verify Arrestee is under 18 and if correct, enter Juvenile Disposition and resubmit the incident.

753 753 Juvenile Disposition not allowed

Disposition of Juvenile was entered, but Age of Arrestee is 18 or greater. Whenever an Arrestee Age indicates an adult, the juvenile disposition cannot be entered because it does not apply.

Suggested action: Verify the Arrestee is older than 17, and if correct, remove Juvenile Disposition entry.

754.1 754 Automatic Weapon Indicator must be A or blank




172

Tennessee FBI Description Error Error Number Number 754.2 754 Automatic Weapon Indicator must be A or blank





Suggested action: Remove the entry from "automatic weapon indicator" field or change the weapon type to a non‐firearm type weapon and resubmit the incident.



Suggested action: Remove the entry from "automatic weapon indicator" field or change the weapon type to a non‐firearm type weapon and resubmit the incident.



Suggested action: Enter Arrestee Age in numeric digits (01 ‐ 99). Check with your vendor.


173

Tennessee FBI Description Error Error Number Number 758 758 Invalid Arrestee Sex value

Arrestee Sex does not contain a valid code of M ‐ Male or F ‐ Female. NOTE: U ‐ Unknown is not valid for an Arrestee.

Suggested action: Enter valid code for sex "M" or "F" only and resubmit the incident.

759 759 Duplicate Group B on file

The Group B Arrest Report submitted had a duplicate Arrestee Sequence Number. If multiple arrestees are involved in the incident, ensure that each one has a unique Arrestee Sequence Number.

Suggested action: Delete one arrestee, change sequence number of one arrestee or check with vendor since arrestee sequence numbers should be automatically and sequentially generated.

760 760 Arrest Offense Code must be a valid Group B offense

Group B Arrest Reports must contain a Group B offense code in the UCR Offense Code field. The offense code submitted is not a Group B offense code.

Suggested action: Change offense code to one of the Group B Arrest codes and resubmit the incident.

TENNESSEE SPECIFIC GROUP B ARRESTEE SEGMENT ERRORS

TN_701 Entry for Arrestee Name is Required

Arrestee Name must be entered.

Suggested action: Enter Arrestee Name. Note for juveniles, you may use "unknown" as the first name and "name" as the last name if you prefer.

TN_701.1 DUI Cause field must be A, D or B for all 90D offenses

Arrest offense submitted is 90D ‐ Driving Under the Influence. You must submit a valid DUI Cause for this offense. Valid codes are: A ‐ Alcohol, D ‐ Drugs, or B ‐ Both.


174

Tennessee FBI Description Error Error Number Number Suggested action: Edit DUI Cause to valid code or edit arrest

offense.

TN_701.2 DUI Cause field is only valid for 90D offenses. All other Group B offenses must be blank

Data is entered in the DUI Cause field. Arrest offense is not 90D ‐ Driving Under the Influence. DUI Cause field must be blank.

Suggested action: Delete data entered in the DUI Cause field or edit arresting offense.

TN_702 Invalid Group B Offense Code

Group B Arrest Offense Code of 850 ‐ Violation Order of Protection is no longer used as an arrest offense in TIBRS.

Suggested action: Edit offense code to one of the valid Group B Arrest codes and resubmit the incident.

TN_702.1 Address must include street number, street, city, state, and zip code

Incident address must include the following data: street number, street name, city, state, and the zip code for the location where the incident occurred.

Suggested action: Enter the required data in the appropriate Address field.

TN_702.2 Invalid Address

The correct format for the Incident Address is street number, address1, address2, city, state, and zip code. All fields are separated by commas. If address2 field is not applicable, place a comma (,) to denote it is empty.

Suggested action: Enter the missing data in the appropriate Address field.


175

Tennessee FBI Description Error Error Number Number TN_702.3 Latitude must be within 34.85654 and 36.75412

The valid latitude for Tennessee would be from 34.85654 to 36.75412.

Suggested action: Edit the data in the Latitude field to a valid value.

TN_702.4 Longitude must be within ‐81.59809 and ‐90.49735

The valid longitude for Tennessee would be from ‐81.59809 to ‐90.49735.

Suggested action: Edit the data in the Longitude field to a valid data value.

TN_702.5 Latitude and Longitude are required

If the Street Number and/or Street Name cannot be determined, you must enter the latitude and longitude of the location. Note: The administrative segment must still be 182.

Suggested action: Enter either a valid Incident Address or Latitude and Longitude for the incident.

TN_703 Arrest type of “R” may only be submitted by a college/university ORI.

An arrest segment was submitted with an arrest type of “R” and the submitting ORI/agency is not a college/university. Arrest type of “R” may only be submitted by a college/university ORI. All other ORIs must use O, S, and T.

Suggested action: Based upon incident circumstances, edit the Arrestee segment and enter a valid arrest type.

OFFICER INVOLVED SHOOTING SEGMENT ERRORS

801.1 Segment 8 ORI is missing

The ORI number was not included in the Officer Involved Shooting segment. It is required.



176

Tennessee FBI Description Error Error Number Number 801.2 Segment 8 Incident Number is missing

The Incident number was not included in the Officer Involved Shooting segment. It is required.

Suggested action: Enter the Incident number and resubmit the incident.

815 Incident Number contains embedded blanks



816 Incident Number must be left justified



817 Incident Number contains invalid characters




177

Tennessee FBI Description Error Error Number Number 818 Officer Sequence Number is missing

The Officer Sequence Number must be entered. It must be a numeric entry 01 ‐ 99. It is required.

Suggested action: Enter the Officer Sequence Number and resubmit the incident.

818.2 Invalid Officer Sequence Number entry is non‐numeric

The Officer Sequence Number must contain numeric entry (01 ‐ 99) with zero left‐fill.

Suggested action: Enter the Officer Sequence Number as a numeric entry (01 ‐ 99) and resubmit the incident.

819 Type Weapon entry required

The Officer's Weapon Type must be entered. It is required.

Suggested action: Enter the Officer's Weapon Type and resubmit the incident.

819.1 Type Weapon entry invalid

The Officer's Weapon Type may only contain one of the following weapon types: 11 ‐ Firearm (type unknown), 12 ‐ Handgun, 13 ‐ Rifle, 14 ‐ Shotgun, or 15 ‐ Other Firearm (machine bun, bazooka, etc.)

Suggested action: Edit the Type Weapon to one of the valid types and resubmit the incident.

820 Incident Level entry required

The Incident Level must be entered. It is required.

Suggested action: Enter the Incident Level and resubmit the incident.


178

Tennessee FBI Description Error Error Number Number 820.1 Incident Level entry invalid

The Incident Level must be entered using one of the following codes: F – Felony or M ‐ Misdemeanor.

Suggested action: Edit the Incident Level to one of the valid codes and resubmit the incident.

821 Multi‐Agency entry required

The Multi‐Agency must be entered.

Suggested action: Enter the Multi‐Agency indicator and resubmit the incident.

821.1 Multi‐Agency entry invalid

The Multi‐Agency must be entered using one of the following codes: Y – Yes or N ‐ No.

Suggested action: Edit the Multi‐Agency to one of the valid codes and resubmit the incident.

822 Officer's Years on Force required

The Officer's Years on Force must be entered. It is required.

Suggested action: Enter the Officer's Years on Force and resubmit the incident.

822.1 Officer's Years on Force entry invalid

The Officer's Years on Force must contain numeric entry (01 ‐ 99).

Suggested action: Enter the Officer's Years on the Force as a numeric entry (01 ‐ 99) and resubmit the incident.

822.2 Law Enforcement Assignment type must be U, P or S

Data entry in the Law Enforcement Assignment Type must be one of the following: U ‐ Uniformed, P ‐ Plain Clothes, or S ‐ Special Assignment.

Suggested action: Edit the data in the Law Enforcement Assignment Type to U, P, or S.


179

Tennessee FBI Description Error Error Number Number 823 Victim Type must be L ‐ Law Enforcement Official for data to

be entered

The data element associated with this error cannot be entered when Victim Type is not L ‐ Law Enforcement Official.

Suggested action: Based on incident circumstances, either edit the Victim Type to L or delete the entered information and resubmit the incident.

823.1 LEOKA Incident entry required

The LEOKA Incident must be entered. It is required.

Suggested action: Enter the LEOKA Incident and resubmit the incident.

823.12 Number of shots fired must be numeric

Data entry in the Number of Shots Fired field must be 3 digit numeric. Valid format is 001 to 999.

Suggested action: Enter a numeric entry for the Number of Shots Fired.

823.2 LEOKA Incident entry invalid

The LEOKA Incident must be entered using one of the following codes: Y – Yes or N ‐ No.

NOTE: The number of officer records with "Y" in this field must equal the number of Victim segments with "L" as the Victim Type.

Suggested action: Edit the LEOKA Incident to one of the valid codes and resubmit the incident.

823.3 Number of shots fired cannot be blank

In an Officer Involved Shooting, the Number of Shots Fired field must be completed. It cannot be blank. Valid format is: 001 ‐ 999.

Suggested action: Based on incident circumstances, enter the number of shots fired by the officer.


180

Tennessee FBI Description Error Error Number Number 824.1 Distance in Feet Between Law Enforcement Official and

Suspect must be numeric

Data entry in the Distance in Feet Between Law Enforcement Official and Suspect may be 3 digit numeric for exact distance or 6 digit numeric for a range. Valid format is: 001 ‐ 999.

Suggested action: Enter a numeric entry for the Distance in Feet Between Law Enforcement Official and Suspect.

824.2 Distance in Feet Between Law Enforcement Official and Suspect cannot be blank

In an Officer Involved Shooting, the Distance in Feet Between Law Enforcement Official and Suspect must be completed. It cannot be blank. May be 3 digit numeric for exact distance or 6 digit numeric for range.

Suggested action: Based on incident circumstances, enter the Distance in Feet Between Law Enforcement Official and Suspect.

825.1 Officer Involved Shooting Field = "Y" requires at least one Officer Involved Shooting Segment submission

The Officer Involved Shooting flag has been marked "Y". The incident did not include an Officer Involved Shooting Segment.

Suggested action: Based on incident circumstances, either edit the Officer Involved Shooting flag to "N" or enter data and submit an Officer Involved Shooting Segment.

825.2 Officer involved Shooting Field = "N" cannot have an Officer Involved Shooting Segment submission

The Officer Involved Shooting flag has been marked "N". However, when the incident was submitted, an Officer Involved Shooting Segment was included for the incident.

Suggested action: Based on incident circumstances, either edit the Officer Involved Shooting flag to "Y" or delete the data submitted for the Officer Involved Shooting Segment.


181