Uniform Crime Reporting
Louisiana Incident-Based
Reporting System
Error Message Manual
Release 2.1
i
2
Table of Contents
UCR/LIBRS Error Message Manual
I. MANDATORIES..................................................................................................................... 1
MANDATORY DATA ELEMENT REQUIREMENTS NOT MET ..................................... 2
SECTION 1: ERROR MESSAGE FOR INITIAL INCIDENT REPORTS ............... 2
SECTION 2: ERROR MESSAGES FOR INITIAL INCIDENT REPORTS
CONTAINING ARRESTEE SEGMENTS ................................................... 3
SECTION 3: ERROR MESSAGES FOR UPDATES (ADD ARREST, MODIFY
AND DELETE) OF PREVIOUSLY SUBMITTED INCIDENTS ................... 3
SECTION 4: DATA ELEMENT MANDATORY EDITS ........................................ 3
II. DATA ELEMENT EDITS ..................................................................................................... 16
DATA ELEMENT EDITS ............................................................................................... 17
CONTROL DATA ELEMENTS ........................................................................... 17
ADMINISTRATIVE SEGMENT EDITS ............................................................... 20
OFFENSE SEGMENT EDITS ............................................................................. 26
PROPERTY SEGMENT EDITS .......................................................................... 46
VICTIM SEGMENT EDITS ................................................................................. 60
OFFENDER SEGMENT EDITS .......................................................................... 76
ARRESTEE SEGMENT EDITS .......................................................................... 80
III. ERROR NUMBERS AND MESSAGES ............................................................................. 87
ERROR NUMBERS AND MESSAGES ........................................................................ 88
STRUCTURE CHECK ERRORS ........................................................................ 88
ZERO REPORTING SEGMENT ERRORS......................................................... 96
ADMINISTRATIVE SEGMENT ERRORS .......................................................... 97
OFFENSE SEGMENT ERRORS ...................................................................... 106
PROPERTY SEGMENT ERRORS ................................................................... 111
OFFENDER SEGMENT ERRORS ................................................................... 127
VICTIM SEGMENT ERRORS ........................................................................... 132
ARRESTEE SEGMENT ERRORS ................................................................... 145
SUBMISSION TRAILER SEGMENT ERRORS ................................................ 152
LIBRS ERROR MESSAGES & EDITS ............................................................. 153
3
I. MANDATORIES
MANDATORY DATA ELEMENT REQUIREMENTS NOT MET
Error Messages should be expanded to be more specific as follows:
Agencies should receive a more detailed error message to better describe what the error is.
Numbering for these error messages will be structured as follows:
lst Character
8=
2nd Character
1=
Mandatory
Error Msg.
Section with
Mandatory
3rd Character
0=
4th and 5th Character
00 = Overall DE edits all
sections except Section 4
Error Msg. Number
01-21 = DE specific edits
within Section
within Section 4
SECTION 1: ERROR MESSAGE FOR INITIAL INCIDENT REPORTS-- each incident must
have the following data elements or the entire incident will be rejected:
0.
“Incident missing a mandatory data element required for all incident submissions.”
(Error Message 81000)
This edit should identify the missing data element, so the agency can determine
which exact data element is missing. This edit applies to Data Elements # 1, 2,
3, 4, 6, L6, 7, 8, 8A, 9, 23, 24, or 25
1.
“Exceptional Clearance Date is required if this incident has any code except "N" in DE
4.”
(Error Message 81100)
2.
“When Type of Victim (DE 25) is "I" or "L" the following data element(s) must have a
valid code.”
(Error Message 81200)
This edit should identify the missing data element(s), so the agency can
determine which exact data element is missing. This edit applies to Data
Elements # 26, 27, 28, 29, 30, or 36
3.
“When DE 36 is not "000", the following data element(s) must have a valid code.”
(Error Message 81300)
This edit should identify the missing data element(s), so the agency can
determine which exact data element is missing. This edit applies to Data
Elements # 37, 38 or 39
MANDATORIES
2
RELEASE 2.1
Print Date: March 7, 2016
MANDATORIES
3
RELEASE 2.1
Print Date: March 7, 2016
4.
"When DE 36 = "000", then DE 8 must be "N" and DE 8A must be "88"."
(Error Message 81400)
SECTION 2: ERROR MESSAGES FOR INITIAL INCIDENT REPORTS CONTAINING
ARRESTEE SEGMENTS:
0.
“Arrest Segment is missing a mandatory data element.”
(Error Message 82000)
This edit should identify the missing data element(s), so the agency can
determine which exact data element is missing. This edit applies to Data
Elements # 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, and 51.
1.
“When DE 47 is less than "17", must have a valid code in DE 52.”
(Error Message 82100)
SECTION 3: ERROR MESSAGES FOR UPDATES (ADD ARREST, MODIFY AND DELETE)
OF PREVIOUSLY SUBMITTED INCIDENTS
0.
“This segment must have a valid code in DE 1 and DE 2.”
(Error Message 83000)
ERROR MESSAGES FOR UPDATES OF ARRESTEE SEGMENTS:
1.
“When submitting an arrestee segment a mandatory data element is missing.”
(Error Message 83100)
This edit should identify the missing data element(s), so the agency can
determine which exact data element is missing. This edit applies to Data
Elements # 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, and 51.
2.
“When DE 47 is less than "17", must have a valid code in DE 52.”
(Error Message 83200)
SECTION 4: DATA ELEMENT MANDATORY EDITS:
SUBSECTION 01
Any initial incidents that have a LRS code of: 14:51/H, 14:51/U, 14:51.1/H, 14:51.1/U,
14:52/H, 14:52/U, 14:53/H, 14:53/U, 14:54/H, 14:54/U, 14:205/H, 14:205/U and also
has a NIBRS code of 200 (ARSON - "Crimes Against Property") on the Master
LIBRS/LRS Code Table should receive the following error messages:
MANDATORIES
4
RELEASE 2.1
Print Date: March 7, 2016
0.
"When LRS = 200 and DE 7 = "A", then DE 14 must be a code of "1" or "8"."
(Error Message 84001)
1.
"When LRS = 200 and DE 7 = "C", then DE 14 must be a code of "2" and DE 15
and 16 must have a valid code."
(Error Message 84101)
SUBSECTION 02
Any incidents that have a LRS code of: 14:34, 14:34.1, 14:34.2, 14:34.3, 14:34.4,
14:34.5, 14:35, 14:35.1, 14:37, 14:37.1, 14:37.2, 14:38, 14:38.1, 14:38.2, 14:39.1,
14:39.2, 14:40, 14:40.1, 14:40.2, 14:43.5, 14:87.2/F, 14:87.5/F, 14:92.3, 14:93/F,
14:94/E, 14:103/A1, 14:107.1/F, 14:122/F, 14:122/T, 14:122.1, 14:122.2, 14:129/A1,
14:129/A2F, 14:129/A2T, 14:129.1, 14:129.1/F, 14:129.1/T, 14:130.1/A, 14:130.1/T,
14:130.1/F, 14:133.1/F, 14:133.1/T, 14:285, 14:404/Q and also has a NIBRS code of
13A, 13B or 13C (Aggravated Assault, Simple Assault and Intimidation - "Crimes
Against Person") on the Master LIBRS/LRS Code Table should receive the following
error messages:
0.
"When LRS = 13A, 13B or 13C DE 7 must equal "C", and DE 25 must be a code
of "I" or "L"."
(Error Message 84002)
1.
"When LRS = 13A, 13B or 13C DE 36 not equal to "000", then DE 34 and 35
must have a valid code."
(Error Message 84102)
2.
"When LRS = 13A, DE 13, 31 & 33 must have a valid code."
(Error Message 84202)
Any incidents that have a LRS code of: 14:34, 14:34.1, 14:34.5, 14:37, 14:37.1,
14:37.2, 14:38.1, 14:39.1, 14:39.2, 14:43.5, 14:87.2/F, 14:87.5/F, 14:93/F,
14:94/E, 14:107.1/F, 14:122/F, 14:129/A2F, 14:129.1/F, 14:130.1/F, 14:133.1/F,
14:404/Q and also has a NIBRS code of 13A (Aggravated Assault - "Crimes
Against Person") on the Master LIBRS/LRS Code Table should receive the
above error message.
3.
When LRS = 13A and Data Element #25 (Type of Victim) is “L”= Law
Enforcement Officer, Data Element #31 must have three valid codes. One
code of “02" = Assault on Law Enforcement Officer, also must have
another valid code of “01" or “03"-“10" to describe the circumstances of
the Aggravated Assault. Must also have one valid code of “12-18" in Data
Element #31 and one valid code of “K-U” in Data Element #32.
(Error Message 84302)
MANDATORIES
5
RELEASE 2.1
Print Date: March 7, 2016
Any incidents that have a LRS code of: 14:34, 14:34.1, 14:34.5, 14:37, 14:37.1,
14:37.2, 14:39.1, 14:39.2, 14:43.5, 14:94/E, 14:122/F, 14:129.1/F, 14:130.1/F,
14:133.1/F, and also has a NIBRS code of 13A (Aggravated Assault - "Crimes
Against Person") on the Master LIBRS/LRS Code Table should receive the
above error message.
4.
"When LRS = 13B, DE 13 must have a valid code and DE 33 must have a code
of "M" or "N"."
(Error Message 84402)
Any incidents that have a LRS code of: 14:34.2, 14:34.3, 14:34.4, 14:35, 14:35.1,
14:38, 14:38.2, 14:103/A1, 14:129.1, 14:130.1/A, and also has a NIBRS code of
13B (Simple Assault - "Crimes Against Person") on the Master LIBRS/LRS
Code Table should receive the above error message.
5.
When LRS = 13B and Data Element #25 (Type of Victim) is “L” = Law
Enforcement Officer, Data Element #31 must have three valid codes. One
code of “02" = Assault on Law Enforcement Officer, also must have
another valid code of “01" or “03"- “10" to describe the circumstances of
the Simple Assault. Must also have one valid code of “12-18" in Data
Element #31 and one valid code of “K-U” in Data Element #32.
(Error Message 84502)
Any incidents that have a LRS code of: 14:34.2, 14:35, 14:38, 14:129.1,
14:130.1/A, and also has a NIBRS code of 13B (Simple Assault - "Crimes
Against Person") on the Master LIBRS/LRS Code Table should receive the
above error message.
SUBSECTION 03
Any incidents that have a LRS code of: 14:73, 14:118, 14:119, 14:119.1, 14:120,
14:131, 14:141, 14:352 and also has a NIBRS code of 510 (Bribery - "Crimes Against
Property") on the Master LIBRS/LRS Code Table should receive the following error
messages:
0.
"When LRS = 510 and DE 7= "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84003)
1.
“When LRS = 510 and DE 7 = "C", then DE 14 must have a code of "1", "5", "7"
or "8".”
(Error Message 84103)
2.
When there is only one completed property offense in an incident, a
property segment can contain a "7" = Stolen Property or an "8" = Unknown.
The incident will reject if an agency sends a "7" and also an "8" within the
MANDATORIES
6
RELEASE 2.1
Print Date: March 7, 2016
same incident, when there is only one completed property offense within
the incident.
(Error Message 84203)
3.
“When LRS = 510 and DE 14 = "5" or "7", then DE 15 and 16 must have a valid
code.”
(Error Message 84303)
4.
“When LRS = 510 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84403)
SUBSECTION 04:
Any incidents that have a LRS code of: 14:62/I, 14:62.1, 14:62.2, 14:62.3, 14:62.4,
14:62.5, 14:62.6, 14:130.1/I, 14:228/A4 and also has a NIBRS code of 220
(Burglary/Breaking and Entering - "Crimes Against Property") on the Master
LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 220 and DE 9 = "14" or "19", then DE 10 and 11 must have a valid
code.”
(Error Message 84004)
1.
“When LRS = 220 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84104)
2.
“When LRS = 220 and DE 7 = "C", then DE 14 must have a code of "1", "5", "7"
or "8".”
(Error Message 84204)
3.
When there is only one completed property offense in an incident, a
property segment can contain a "7" = Stolen Property or an "8" = Unknown.
The incident will reject if an agency sends a "7" and also an "8" within the
same incident, when there is only one completed property offense within
the incident.
(Error Message 84304)
4.
“When LRS = 220 and DE 14 = "5" or "7", then DE 15 & 16 must have a valid
code.”
(Error Message 84404)
5.
“When LRS = 220 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84504)
MANDATORIES
7
RELEASE 2.1
Print Date: March 7, 2016
SUBSECTION 05:
Any incidents that have a LRS code of: 14:72, 14:72.1, 14:72.2, 14:130.1/X, 14:133,
14:134.2, 14:223.7, 14:228/A6X, 14:229, 14:353, 27:263, 40:971/B1BX, 40:971/B1D,
40:971/B1E, 40:971/B1F, 40:971/B1G, and also has a NIBRS Code of 250
(Counterfeiting/Forgery - "Crimes Against Property") on the Master LIBRS/LRS
Code Table should receive the following error messages:
0.
“When LRS = 250, DE 12 must have a valid code.
(Error Message 84005)
1.
“When LRS = 250 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84105)
2.
“When LRS = 250 and DE 7 = "C", then DE 14 must have a code of "3", "5" or "6"
and DE 15 & 16 must have a valid code.”
(Error Message 84205)
3.
“When LRS = 250 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84305)
SUBSECTION 06:
Any incidents that have a LRS code of: 14:55, 14:56, 14:56.1, 14:56.2, 14:57, 14:58,
14:59/A3, 14:59/A10, 14:63.2, 14:73.3, 14:101, 14:130.1/Y, 14:132, 14:206, 14:207,
14:225, 14:227, 14:228/A2, 14:228/A6Y and also has a NIBRS Code of 290
(Destruction/Damage/Vandalism - "Crimes Against Property") on the Master
LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 290 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84006)
1.
“When LRS = 290 and DE 7 = "C", then DE 14 must have a code of "4" and DE
15 & 16 must have a valid code.”
(Error Message 84106)
SUBSECTION 07:
Any incidents that have a LRS code of: 14:30.1/D, 40:962.1, 40:966, 40:967, 40:968,
40:969, 40:970, 40:971.1, 40:981, 40:981.1, 40:981.2, 40:981.3, 40:982, 40:989,
40:1032, 40:1033, 40:1033.1 and also has a NIBRS Code of 35A (Drug/Narcotic
Violations) and 35B (Drug Equipment Violations - "Crimes Against Society") on
the Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 35A or 35B, DE 12 must have a valid code.
MANDATORIES
8
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 84007)
1.
“When LRS = 35A or 35B and DE 7 = "A", then DE 14 must have a code of "1"
or "8".”
(Error Message 84107)
2.
“When LRS = 35A or 35B and DE 7 = "C", then DE 14 must have a code of "1"
or "6".”
(Error Message 84207)
3.
“When LRS = 35A or 35B, DE 16 must have a valid code *** (or must be blank
if DE 14 = "1" or "8") and DE 25 must be "S".”
(Error Message 84307)
Any incidents that have a LRS code of: 14:30.1/D, 40:962.1, 40:966, 40:967,
40:968, 40:969, 40:970, 40:971.1, 40:981, 40:981.1, 40:981.2, 40:981.3, 40:982,
40:989 and also has a NIBRS code of 35A (Drug/Narcotic Violations - "Crimes
Against Society") on the Master LIBRS/LRS Code Table should receive the
following error messages:
4.
“When LRS = 35A and DE 14 = "6", then DE 15 cannot be equal to "11".”
(Error Message 84407)
5.
“When LRS = 35A and DE 14 = "1", then DE 20 must have a valid code.”
(Error Message 84507)
6.
“When LRS = 35A, DE 14 = "6" and DE 15 = "10", then DE 16, 20, 21 and 22
must have a valid code.”
(Error Message 84607)
7.
“When LRS = 35B and DE 14 = "6", then DE 15 cannot be equal to "10".”
(Error Message 84707)
Any incidents that have a LRS code of: 40:1032, 40:1033, 40:1033.1 and also
has a NIBRS code of 35B (Drug Equipment Violations - "Crimes Against
Society") on the Master LIBRS/LRS Code Table should receive the above error
message.
SUBSECTION 08:
MANDATORIES
9
RELEASE 2.1
Print Date: March 7, 2016
Any incidents that have a LRS code of: 14:66, 14:135, 14:136, 14:511, 14:512 and also
has a NIBRS Code of 210 (Extortion/Blackmail - "Crimes Against Property") on the
Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 210, DE 13 must have a valid code.
(Error Message 84008)
1.
“When LRS = 210 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84108)
2.
“When LRS = 210 and DE 7 = "C", then DE 14 must have a code of "5" or "7"
and DE 15 & 16 must have a valid code.”
(Error Message 84208)
3.
“When LRS = 210 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84308)
4.
“When LRS = 210 and DE 25 = "I" or "L", then DE 33 must have a valid code.”
(Error Message 84408)
SUBSECTION 09:
Any incidents that have a LRS code of: 14:67.3, 14:67.11, 14:67.14, 14:70, 14:70.1,
14:70.2, 14:70.3, 14:70.4, 14:73.2, 14:112, 14:112.1, 14:126.3, 14:133.3, 14:138,
14:139, 14:139.1, 14:139.2, 14:140, 14:213, 14:220, 14:220.1, 14:228/A3, 14:331,
14:351, 27:99, 27:100/A, 27:100/B, 27:264/A, 27:264/B, 32:421, 40:971/B1A,
40:971/B1B, 40:971/B1C, 40:971/B1H, 40:975, 40:1321.G, 46:114.2 and also has a
NIBRS Code of 26A-E (Fraud Offenses - "Crimes Against Property") on the Master
LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 26A-E and DE 7 = "A", then DE 14 must have a code of "1" or
"8".”
(Error Message 84009)
1.
“When LRS = 26A-E and DE 7 = "C", then DE 14 must have a code of "5" or "7"
and DE 15 & 16 must have a valid code.”
(Error Message 84109)
2.
“When LRS = 26A-E and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84209)
SUBSECTION 10:
MANDATORIES
10
RELEASE 2.1
Print Date: March 7, 2016
Any incidents that have a LRS code of: 14:90/G, 14:90/R, 14:90.1, 14:90.2/G,
14:90.2/R, 14:90.3, 14:102.5, 14:102.6, 14:102.10, 14:118.1, 14:118.2, 14:214 and also
has a NIBRS Code of 39A-D (Gambling Offenses - "Crimes Against Society") on the
Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 39A-D and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84010)
1.
“When LRS = 39A-D and DE 7 = "C", then DE 14 must have a code of "6", DE 15
& 16 must have a valid code, and DE 25 must be "S".”
(Error Message 84110)
2.
“When LRS = 39C, DE 12 must have a valid code.”
(Error Message 84210)
Any incidents that have a LRS code of: 14:90.1, 14:102.6 and also has a NIBRS
code of 39C (Gambling Equipment Violations - "Crimes Against Society") on
the Master LIBRS/LRS Code Table should receive the above error message.
SUBSECTION 11:
Any incidents that have a LRS code of: 14:20, 14:30, 14:30.1, 14:31, 14:32,
14:32.1/AA, 14:87.1, 14:87.2/L, 14:87.5/L, 14:501 and also has a NIBRS Code of 09A,
09B or 09C (Homicide Offenses - "Crimes Against Persons") on the Master
LIBRS/LRS Code Table should receive an error message that says:
0.
“When LRS = 09A, 09B or 09C, DE 7 must equal "C", DE 13 & 31 must have a
valid code, and DE 25 must equal "I" or "L".”
(Error Message 84011)
1.
“When LRS = 09A, 09B or 09C, if DE 36 not equal to "000", then DE 34 & 35
must have a valid code.”
(Error Message 84111)
2.
“When LRS = 09C, DE 31 must have "20" or "21" and DE 32 must have a valid
code of "A-G".”
(Error Message 84211)
Any incidents that have a LRS code of: 14:20 and also has a NIBRS code of 09C
(Justifiable Homicide - "Crimes Against Persons") on the Master LIBRS/LRS
Code Table should receive the above error message.
3.
When LRS = 09A and Data Element #25 (Type of Victim) is “L” = Law
Enforcement Officer, Data Element #31 must have at least two valid codes:
One valid code of “01" or “03-10" (can enter up to two codes, but cannot be
MANDATORIES
11
RELEASE 2.1
Print Date: March 7, 2016
duplicate codes) to describe the circumstances of the Murder and
Nonnegligent Manslaughter. Must also have one valid code of “12-18" in
Data Element #31 and one valid code of “K-U” in Data Element #32.
(Error Message 84311)
Any incidents that have a LRS code of: 14:30, 14:30.1, 14:31, 14:32.1/AA,
14:87.1, 14:87.2/L, 14:87.5/L and also has a NIBRS Code of 09A (Murder and
Nonnegligent Manslaughter - "Crimes Against Persons") on the Master
LIBRS/LRS Code Table should receive the above error message.
4.
When LRS = 09B and Data Element #25 (Type of Victim) is “L” = Law
Enforcement Officer, Data Element #31 must have two valid codes. One
valid code of “30-34" to describe the circumstances of the Negligent
Manslaughter. Must also have one valid code of “12-18" in Data Element #
31 and one valid code of “K-U” in Data Element #32.
(Error Message 84411)
Any incidents that have a LRS code of: 14:32, 14:501 and also has a NIBRS
Code of 09B (Negligent Manslaughter - "Crimes Against Persons") on the
Master LIBRS/LRS Code Table should receive the above error message.
SUBSECTION 12:
Any incidents that have a LRS code of: 14:44, 14:44.1, 14:45, 14:45.1, 14:46, 14:46.1
and also has a NIBRS Code of 100 (Kidnapping/Abduction - "Crimes Against
Person") on the Master LIBRS/LRS Code Table should receive the following error
messages:
0.
“When LRS = 100, DE 13 must have a valid code.
(Error Message 84012)
1.
“When LRS = 100 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84112)
2.
“When LRS = 100 and DE 7 = "C", then DE 14 must have a code of "1", "5", "7",
or "8".”
(Error Message 84212)
3.
When there is only one completed property offense in an incident, a
property segment can contain a "7" = Stolen Property or an "8" = Unknown.
The incident will reject if an agency sends a "7" and also an "8" within the
same incident, when there is only one completed property offense within
the incident.
(Error Message 84312)
MANDATORIES
12
RELEASE 2.1
Print Date: March 7, 2016
4.
“When LRS = 100 and DE 14 equals to "5" or "7", then DE 15 and 16 must have
a valid code.”
(Error Message 84412)
5.
“When LRS = 100 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84512)
6.
“When LRS = 100 and DE 25 equals to "I" or "L", then DE 33 must have a valid
code.”
(Error Message 84612)
7.
“When LRS = 100 and DE 36 is not equal to "000", DE 34 and 35 must have a
valid code.”
(Error Message 84712)
SUBSECTION 13:
Any incidents that have a LRS code of: 14:62/M, 14:62/Z, 14:65.1, 14:67, 14:67/B,
14:67/C, 14:67/E, 14:67/K, 14:67/S, 14:67/Z, 14:67.1, 14:67.2, 14:67.4, 14:67.5,
14:67.6, 14:67.7, 14:67.8, 14:67.9, 14:67.10, 14:67.13, 14:67.15, 14:68, 14:68.1,
14:68.2, 14:68.3, 14:71.1, 14:71.2, 14:73.5, 14:93.4, 14:130.1/B, 14:217, 14:219,
14:221, 14:222, 14:222.1, 14:223.5, 14:223.6, 14:228/A6, 27:98/B, 27:98/C, 27:262
and also has a NIBRS Code of 23A-H (Larceny/Theft Offenses - "Crimes Against
Property") and 270 (Embezzlement Offenses - "Crimes Against Property") on the
Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 23A-H or 270 and DE 7 = "A", then DE 14 must have a code of "1"
or "8".”
(Error Message 84013)
1.
“When LRS = 23A-H or 270 and DE 7 = "C", then DE 14 must have a code of "5"
or "7" and DE 15 & 16 must have a valid code.”
(Error Message 84113)
2.
“When LRS = 23A-H or 270 and DE 14 = "5", then DE 17 must have a valid
date.”
(Error Message 84213)
SUBSECTION 14:
Any incidents that have a LRS code of: 14:67, 14:68, 14:68.4 and also has a NIBRS
Code of 240 (Motor Vehicle Theft - "Crimes Against Property") on the Master
LIBRS/LRS Code Table should receive the following error messages:
MANDATORIES
13
RELEASE 2.1
Print Date: March 7, 2016
0.
“When LRS = 240 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84014)
1.
“When LRS = 240 and DE 7 = "C", then DE 14 must have a code of "5" or "7"
and DE 15 & 16 must have a valid code.”
(Error Message 84114)
2.
“When LRS = 240 and DE 14 = "5", then DE 15 must have a valid code, and DE
17 must have a valid date."
(Error Message 84214)
3.
"When LRS = 240 and DE 14 = “5", if DE 15 has a code of "03", "05", "24", "28",
or "37", then DE 19 must have a valid code.”
(Error Message 84314)
4.
“When LRS = 240 and DE 14 = "7", then DE 15 must have a code of "03", "05",
"24", "28", or "37" and DE 18 must have a valid code.”
(Error Message 84414)
SUBSECTION 15:
Any incidents that have a LRS code of: 14:81.1, 14:85.1, 14:91.11, 14:106, 14:106.1,
32:378.1 and also has a NIBRS Code of 370 (Pornography/Obscene Material
Offenses - "Crimes Against Society") on the Master LIBRS/LRS Code Table should
receive the following error message:
0.
“When LRS = 370, DE 12 must have a valid code and DE 25 must equal "S".”
(Error Message 84015)
SUBSECTION 16:
Any incidents that have a LRS code of: 14:82, 14:82.1, 14:83, 14:83.1, 14:83.2, 14:83.3,
14:83.4, 14:84, 14:85, 14:86, 14:107/9, 14:282 and also has a NIBRS Code of 40A or
40B (Prostitution Offenses - "Crimes Against Society") on the Master LIBRS/LRS
Code Table should receive the following error messages:
0.
“When LRS = 40A or 40B, DE 25 must equal "S".”
(Error Message 84016)
SUBSECTION 17:
Any incidents that have a LRS code of: 14:60, 14:64, 14:64.1, 14:64.2, 14:65, 14:65.1/F
and also has a NIBRS Code of 120 (Robbery Offenses - "Crime Against Property")
on the Master LIBRS/LRS Code Table should receive the following error messages:
MANDATORIES
14
RELEASE 2.1
Print Date: March 7, 2016
0.
“When LRS = 120, DE 13 must have a valid code."
(Error Message 84017)
1.
“When LRS = 120 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84117)
2.
“When LRS = 120 and DE 7 = "C", then DE 14 must have a code of "5" or "7"
and DE 15 & 16 must have a valid code.”
(Error Message 84217)
3.
“When LRS = 120 and DE 14 = "5", then DE 17 must have a valid date.”
(Error Message 84317)
4.
“When LRS = 120 and DE 25 = "I" or "L", then DE 33 must have a valid code.”
(Error Message 84417)
5.
“When LRS = 120 and DE 25 = "I" or "L" and DE 36 not equal to "000", then DE
34 and 35 must have a valid code.”
(Error Message 84517)
SUBSECTION 18:
Any incidents that have a LRS code of: 14:42/A, 14:42/V, 14:42.1/A, 14:42.1/V,
14:43/A, 14:43/V, 14:43.1/N, 14:43.1/P, 14:43.2/N, 14:43.2/P, 14:43.3, 14:43.4,
14:44.1/A, 14:44.1/N, 14:44.1/O, 14:44.1/P, 14:44.1/V, 14:81.2, 14:89.1, 14:93.5 and
also has a NIBRS Code of 11A - 11D (Sex Offenses, Forcible - "Crimes Against
Persons") on the Master LIBRS/LRS Code Table should receive the following error
messages:
0.
“When LRS = 11A - 11D, DE 13 must have a valid code, DE 25 must have a "I"
or "L", and DE 33 must have a valid code.”
(Error Message 84018)
1.
“When LRS = 11A - 11D and 36 not equal to "000", then DE 34 and 35 must
have a valid code.”
(Error Message 84118)
SUBSECTION 19:
Any incidents that have a LRS code of: 14:78, 14:78.1, 14:80 and also has a NIBRS
Code of 36A or 36B (Sex Offenses, Nonforcible - "Crimes Against Persons") on the
Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 36A or 36B, DE 25 must have a "I" or "L".”
(Error Message 84019)
MANDATORIES
15
RELEASE 2.1
Print Date: March 7, 2016
1.
“When LRS = 36A or 36B and DE 36 not equal to "000", then DE 34 and 35
must have a valid code.”
(Error Message 84119)
SUBSECTION 20:
Any incidents that have a LRS code of: 14:69, 14:211, 14:212, 14:228/A7 and also has
a NIBRS Code of 280 (Stolen Property Offenses - "Crimes Against Property") on
the Master LIBRS/LRS Code Table should receive the following error messages:
0.
“When LRS = 280, DE 12 must have a valid code.”
(Error Message 84020)
1.
“When LRS = 280 and DE 7 = "A", then DE 14 must have a code of "1" or "8".”
(Error Message 84120)
2.
“When LRS = 280 and DE 7 = "C", then DE 14 must have a code of "1" or "5".”
(Error Message 84220)
3.
“When LRS = 280 and DE 14 = "5", then DE 15, 16 & 17 must have a valid
code.”
(Error Message 84320)
SUBSECTION 21:
Any incidents that have a LRS code of: 14:54.2, 14:54.3, 14:59/A9, 14:91, 14:94/F,
14:95, 14:95.1, 14:95.2, 14:95.5, 14:95.6, 14:95.7, 32:292, 40:1783, 40:1784, 40:1785,
40:1787, 40:1788, 40:1789, 40:1792 and also has a NIBRS Code of 520 (Weapons
Law Violations - "Crimes Against Society") on the Master LIBRS/LRS Code Table
should receive the following error messages:
0.
“When LRS = 520, DE 12 & DE 13 must have a valid code and DE 25 must be
equal to "S".”
(Error Message 84021)
MANDATORIES
16
RELEASE 2.1
Print Date: March 7, 2016
II. DATA ELEMENT EDITS
DATA ELEMENT EDITS
CONTROL DATA ELEMENTS
DATA ELEMENT # C1
SEGMENT DESCRIPTOR
1) Must be present -- cannot be blank.
(Error Message 20001)
2) Must be a valid code.
(Error Message 20002)
3) Must identify a segment of proper length.
(Error Message 20015)
DATA ELEMENT # C2
SUBMITTING AGENCY
1) Must be a valid agency.
(Error Message 20010)
DATA ELEMENT # C3
SUBMISSION DATE
1) Must be present -- cannot be blank.
(Error Message 20001)
2) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days).
(Error Message 20025)
3) The date must be greater than that entered within Data Element
# C4 (Reporting Period).
(Error Message 20026)
DATA ELEMENT # C4
REPORTING PERIOD
1) Must be present--cannot be blank.
(Error Message 20001)
2) Each component of the date must be valid; that is, months must
be 01-12, and year must include then century (i.e., 19xx, 20xx).
DATA ELEMENT EDITS
18
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 20025)
3) The date cannot be greater than that entered within Data
Element # C3 (Date of Submission).
(Error Message 20026)
4) Reporting period date cannot precede incident date.
(Error Message 20060)
DATA ELEMENT # C5
ACTION TYPE
1) Must be present--cannot be blank.
(Error Message 20001)
DATA ELEMENT # C6
CLEARANCE INDICATOR for "Time-Window" Submissions
only
1) Must be present -- cannot be blank, if Data Element # C5 = "W"
= Time-Window
(Error Message 20001)
2) Must be a valid code.
(Error Message 20002)
3) Must be blank when action type is not "W" = Time-Window.
(Error Message 16058)
DATA ELEMENT # C7
NUMBER OF SEGMENTS TRANSFERRED
1) Must be present -- cannot be blank.
(Error Message 20001)
2) Must be 3 or greater.
(Error Message 20030)
3) Must be equal to the total number of segments written to the
tape.
(Error Message 20031)
DATA ELEMENT # C8
END OF SEGMENT MARKER
1) Must be present -- cannot be blank.
(Error Message 20001)
DATA ELEMENT EDITS
19
RELEASE 2.1
Print Date: March 7, 2016
2) Must be equal to "ZZ".
(Error Message 20029)
DATA ELEMENT # C9
PADDING
1) Must be blank spaces if fixed length records are submitted. Must
be one newline character ASCII 13 if variable length records are
submitted.
2) If fixed length records are used this field must be appropriate to
"pad" segment length out to exactly column 150.
DATA ELEMENT EDITS
20
RELEASE 2.1
Print Date: March 7, 2016
ADMINISTRATIVE SEGMENT EDITS
DATA ELEMENT # 1
ORI NUMBER
1) Must be present -- cannot be blank.
(Error Messages 10001, 11001, 12001, 13001, 14001,
15001, 16001)
2) Must be a valid 9-character NCIC number, where the last 2
positions of the ORI must reflect "00" for all state and local
agencies.
(Error Messages 10052, 10086, 11004, 12004, 13004,
14004, 15004, 16004)
3) First two positions must be the code of the state, "LA", in which
the incident occurred.
(Error Message 10059)
DATA ELEMENT # 2
INCIDENT NUMBER
1) Must be present -- cannot be blank.
(Error Messages 10001, 11001, 12001, 13001, 14001,
15001, 16001)
2) Zero Reporting Segments (Segment 01) must contain twelve
zeros as the incident number.
(Error Message 10092)
3) Must be left justified with blank right-fill if under 12 characters in
length.
(Error Messages 10016, 11016, 12016, 13016, 14016,
15016, 16016)
4) Valid character combinations can include A-Z, 0-9, hyphens,
and/or blanks.
(Error Messages 10017, 11017, 12017, 13017, 14017,
15017, 16017)
5) Must be blank right-fill if under twelve characters in length. The
field cannot have embedded "Blanks" between the first and last
characters entered.
(Error messages 10015, 11015, 12015, 13015, 14015,
15015, 16015)
DATA ELEMENT EDITS
21
RELEASE 2.1
Print Date: March 7, 2016
6) This field must be unique for each incident reported by the
agency. This means that no two incidents can have the same
incident number. Some agencies ensure uniqueness by
prefixing every incident number with a two-digit year followed by
a number starting with 1, while others just increment the number
by one for each new incident.
(Error Message 10056)
7) Cannot have duplicate incident number for "Time-Window"
Segment.
(Error Message 10087)
DATA ELEMENT # 3
INCIDENT DATE/HOUR
1) Must be present -- cannot be blank.
(Error Message 11001)
2) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). The
date cannot exceed the current date.
(Error Message 11005)
3) When an ORI becomes inactive, no incident data may be
submitted to LIBRS with an incident date on or after that date.
However, adjustments to previously submitted data may be
done.
(Error Message 11018)
4) The date cannot be earlier than 01/01/1991 for "I" = Incident
Report submissions. This edit will preclude dates that are
obviously incorrect since the FBI began accepting data on this
date.
(Error Message 11072)
5) When an agency converts from Summary reporting to Incident
Based Reporting (IBR) or commences to report LIBRS data, no
data regarding an incident previously submitted under the
Summary reporting system can be submitted with an incident
date later than the date the agency commenced reporting,
otherwise it will be regarded as a duplicate submission and be
rejected since the Summary System already contains the
aggregate data for the months before LIBRS conversion. In
DATA ELEMENT EDITS
22
RELEASE 2.1
Print Date: March 7, 2016
other words, if an agency sends IBR data for the first time on 20
September 1995, all dates in data element # 3 for incidents,
recovered property, and arrests must be within September,
1995. The exception to this is when EXCEPTIONAL
CLEARANCES occur for a pre-IBR incident. In this case, Data
Element #3 (Incident Date/Hour) may be earlier than
September,1995, but Data Element # 5 (Exceptional Clearance
Date) must be within September,1995. The State will maintain a
table of start dates (base dates) for each local agency. Except
for the above example, the State will reject data submitted with
an Incident Date for months prior to the agency's start date.
(Error Message 11073)
6) The date cannot be later than the year and month the tape
represents. (example: The May 1995 tape cannot contain
incidents happening later than this date)
(Error Message 11070)
7) The Submission Date (#C3), in positions 23-30, and the
incident date must be valid entries. The state software uses
these to determine if the complete incident should have been
reported to the state, or if a subset of the segments should have
been submitted as "Time Window" submissions.
(Error Message 11075)
8) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "W" = Time-Window Submission cannot
have a date in Data Element # 3 (Incident Date/Hour) which
would be a valid date for an Incident. For any subsequent "M" =
Modify of a previously submitted "W" = Time-Window
Submission, this is also true.
(Error Message 11076)
9) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify cannot change the date in
Data Element # 3 (Incident Date/Hour) of segments which were
previously submitted with a Segment Action Type of "I" =
Incident Report.
(Error Message 11061)
10) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify cannot change the
Report Date Indicator (position 51 of the segment) of
Segments which were previously submitted with a Segment
Action Type of "I" = Incident Report.
DATA ELEMENT EDITS
23
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 11062)
11) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify cannot change the
hours in Data Element # 3 (Incident Date/Hour) of Segments
which were previously submitted with a Segment Action Type
of "I' = Incident Report.
(Error Message 11063)
12) If HOUR is entered it must be "00" through "23." Note: If the
incident Date occurred at exactly midnight, enter the Incident
Date as if the time was 1 minute past midnight. (Example: If
the crime occurred at exactly midnight on Thursday, enter
Friday's date) and 00 for the hour.
(Error Message 11052)
13) If the Incident Date is unknown, use the report date. Indicate
a report date with an "R" in the space before the hour. If this
is the Incident Date, then leave the "Report" indicator blank.
(Error Message 11051)
DATA ELEMENT # 4
CLEARED EXCEPTIONALLY
1) Must be present -- cannot be blank.
(Error Message 11001)
2) Must be a valid code.
(Error Message 11004)
3) Cannot be "N" = Not Applicable if Data Element # 5 (Exceptional
Clearance Date) is entered.
(Error Message 11053)
4) When a value other than "N" = Not Applicable is entered, there
can be no Arrestee Segments associated with the Incident.
(Error Message 10071)
5) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify must have an "N" = Not
Applicable in Data Element # 4 (Exceptional Clearance Indicator)
when arrestees were already present for the incident report.
(Error Message 11064)
DATA ELEMENT EDITS
24
RELEASE 2.1
Print Date: March 7, 2016
6) Administrative Segment (Segment 10) submitted with a
Segment Action Type of "W" = Time Window Submission
cannot contain an "N" = Not Applicable in Data Element #4
(Cleared Exceptionally).
(Error Message 11054)
DATA ELEMENT # 5
EXCEPTIONAL CLEARANCE DATE
1) The clearance date cannot be earlier than the incident date.
(Error Message 11055)
2) Must be present if case was cleared exceptionally per data value
code in Data Element # 4 (Cleared Exceptionally).
(Error Message 11056)
3) Each component of the date must be valid; that is, months must
be 0-12, days must be 01-31, and year must include the century
(i.e. 19xx, 20xx). In addition, days cannot exceed maximum for
the month (e.g., June cannot have 31 days). The date cannot be
greater than that entered within the "Month of Tape" and "Year of
Tape" are "06/1995", "the clearance date cannot contain any
date 07/01/1995 or greater.
(Error Message 11005)
4) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "W" = Time-Window Submission must
contain Data Element # 4 (Cleared Exceptionally) and # 5
(Exceptional Clearance Date). Both must be present to be a
valid submission.
(Error Message 11057)
5) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "W" = Time-Window Submission cannot
have an Exceptional Clearance Date (Data Element # 5) earlier
than the "Time-Window" Base Date. For any subsequent "M" =
Modify of a previously submitted "W" = Time-Window
Submission, this is also true.
(Error Message 11020)
6) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify with an "N" = Not
Applicable in Data Element # 4 (Exceptional Clearance Indicator)
cannot have an entry in Data Element # 5 (Exceptional
Clearance Date).
DATA ELEMENT EDITS
25
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 11066)
7) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify for a previously submitted
"W" = Time-Window Submission must have a date in Data
Element # 5 (Exceptional Clearance Date).
(Error Message 11067)
8) Administrative Segments (Segment 10) submitted with a
Segment Action Type of "W" = Time-Window Submission or "M"
= Modify cannot have a date earlier than the date the ORI was
certified for LIBRS submission. Data Element # 5 (Exceptional
Clearance Date), was earlier.
(Error Message 11074)
DATA ELEMENT EDITS
26
RELEASE 2.1
Print Date: March 7, 2016
DATA ELEMENT EDITS
27
RELEASE 2.1
Print Date: March 7, 2016
OFFENSE SEGMENT EDITS
DATA ELEMENT # L6
OFFENSE SEQUENCE NUMBER
1) Must be present -- cannot be blank.
(Error Message 12001)
2) Must be numeric entry (001 through 999) with zero left-fill. The
purpose of the field is to distinguish one offense from another.
(Error Message 15002)
3) Must be unique -- cannot be duplicated.
(Error Message 25001)
DATA ELEMENT # 6
LOUISIANA REVISED STATUE NUMBER
1) Must be present--cannot be blank.
( Error Message 12001)
2) Must be a valid code on Master LIBRS/LRS Code Table.
(Error Message 12004)
Refer to the Master LIBRS/LRS Code Table to determine: 1)
LRS Codes that are accepted, 2) What offense the LRS code
was assigned (NIBRS Code determines offense to be
reported), 3) Index Class assigned to each LRS, 4) IBR and
UCR rankings. To determine definitions of qualifiers see the
list at the end of this section.
ALLOWED
ENTRIES
for SUBPARTS:
Some LRS codes are broken down in subparts and must be submitted
with the subpart. Each code may be a different offense when submitted to
LIBRS. For instance 14:107/1 would be reported as Drunkenness (90E)
and 14:107/9 would be Prostitution (40A).
The following LRS codes will be rejected if not submitted with a subpart
and have been deleted from the Master LIBRS/LRS Code Table.
14:59
14:130.1
DATA ELEMENT EDITS
14:94
28
RELEASE 2.1
14:103
14:107
Print Date: March 7, 2016
The LRS codes listed below will require a subpart to determine the
proper offense to be submitted to LIBRS.
14:59/A1
14:59/A5
14:59/A9
14:103/A1
14:103/A5
14:107/3
14:107/7
27:98/B
27:264/A
14:59/A2
14:59/A6
14:59/A10
14:103/A2
14:103/A6
14:107/4
14:107/8
27:98/C
27:264/B
14:59/A3
14:59/A7
14:94/E
14:103/A3
14:107/1
14:107/5
14:107/9
27:100/A
14:59/A4
14:59/A8
14:94/F
14:103/A4
14:107/2
14:107/6
14:130.1/A
27:100/B
NOTE: 14:130.1 can also be submitted with a qualifier. See Allowed
Entries for Qualifiers.
3)
If these LRS codes are submitted without a subpart the entire
incident will be rejected and the agency would receive an error
message that says: “This LRS code must be submitted with a
subpart to identify offense applicable.”
(Error Message # 22005)
ALLOWED
ENTRIES
for SUBPARTS
and SUBPARTS
with QUALIFIERS: Some LRS Codes are broken down into subparts and some must have
subparts with qualifiers. Each code may be a different offense when
submitted to LIBRS. For instance 14:129/A1 would be reported as
Intimidation (13C) and 14:129/A2F would be reported as an Aggravated
Assault (13A).
The following LRS codes will be rejected if not submitted with a subpart or
subpart with a qualifier and have been deleted from the Master
LIBRS/LRS Code Table.
14:129
14:228
40:971
The LRS codes listed below will require a subpart or a subpart with a
qualifier to determine the proper offense to be submitted to LIBRS.
14:129/A1
14:228/A2
DATA ELEMENT EDITS
14:129/A2F
14:228/A3
29
RELEASE 2.1
14:129/A2T
14:228/A4
14:228/A1
14:228/A5
Print Date: March 7, 2016
14:228/A6
40:971/A
40:971/B1C
40:971/B1G
14:228/A6X
40:971/B1A
40:971/B1D
40:971/B1H
14:228/A6Y
14:228/A7
40:971/B1BX 40:971/B1B
40:971/B1E
40:971/B1F
40:971/C
4)
If this LRS is submitted without a subpart or a subpart with a
qualifier the entire incident will be rejected. The agency would
receive an error message that says: “This LRS code must be
submitted with a subpart or a subpart with a qualifier to define the
offense applicable.”
(Error Message # 22010)
5)
If the LRS is submitted with a subpart and no qualifier, the agency
would receive a warning message that says: “WARNING--This LRS
code was submitted with a subpart and no qualifier.” Check Master
LIBRS/LRS Code Table to be sure the correct offense is being
reported.
(WARNING # 22015)
ALLOWED ENTRIES
for QUALIFIERS: Some LRS codes must be submitted with a qualifier in order to determine
the proper offense to be reported. For instance 14:42/V would be reported
as a Forcible Rape (11A) and 14:42/A would be a Forcible Sodomy (11B).
The following LRS codes will be rejected if not submitted with a qualifier
and have been deleted from the Master LIBRS/LRS Code Table.
14:42
14:43.2
14:54
14:87.2
14:122
14:42.1
14:51
14:62
14:87.5
14:130.1
14:43
14:52
14:63
14:90
14:205
14:43.1
14:53
14:63.3
14:90.2
14:404
The LRS codes listed below will require a qualifier to determine the
proper offenses to be submitted to LIBRS.
14:42/A
14:43/A
14:43.2/N
14:51.1/H
14:53/H
14:62/I
DATA ELEMENT EDITS
14:42/V
14:43/V
14:43.2/P
14:51.1/U
14:53/U
14:62/M
30
RELEASE 2.1
14:42.1/A
14:43.1/N
14:51/H
14:52/H
14:54/H
14:62/Z
14:42.1/V
14:43.1/P
14:51/U
14:52/U
14:54/U
14:63/I
Print Date: March 7, 2016
14:63/M
14:87.2/L
14:87.5/W
14:90.2/R
14:130.1/F
14:130.1/Y
14:404/Q
14:63.3/I
14:87.2/W
14:90/G
14:122/F
14:130.1/I
14:205/H
14:63.3/M
14:87.5/F
14:90/R
14:122/T
14:130.1/T
14:205/U
14:87.2/F
14:87.5/L
14:90.2/G
14:130.1/B
14:130.1/X
14:404/J
NOTE: 14:130.1 can also be submitted with a subpart. See Allowed
Entries for Subparts.
6)
If these LRS codes are submitted without a qualifier the entire
incident will be rejected and the agency would receive an error
message that says: "This LRS must be submitted with a qualifier to
identify offense applicable."
(Error message # 22020)
ALLOWED ENTRIES
for WITH OR WITHOUT
QUALIFIERS:
Some LRS codes are allowed to be submitted with or without a qualifier.
For instance 14:44.1 would be reported as a Kidnapping (100) and
14:44.1/N would be Forcible Fondling (11D).
The LRS codes listed below will be accepted with or without a qualifier or
a hard code to determine the proper offense code to be reported to
LIBRS.
14:30.1
14:44.1
14:44.1/P
14:67
14:67/K
14:93/F
14:129.1/F
14:133.1/T
14:30.1/D
14:44.1/A
14:44.1/V
14:67/B
14:67/S
14:107.1
14:129.1/T
14:32.1
14:44.1/N
14:65.1
14:67/C
14:67/Z
14:107.1/F
14:133.1
14:32.1/AA
14:44.1/O
14:65.1/F
14:67/E
14:93
14:129.1
14:133.1/F
The LRS codes listed below would produce these Error Messages:
7) 14:30.1 with no qualifier would be reported as Murder and
Nonnegligent Homicide (09A).
The reporting agency would receive a warning message that
says:
DATA ELEMENT EDITS
31
RELEASE 2.1
Print Date: March 7, 2016
"WARNING -- This LRS submitted without a qualifier will be
reported as Murder and Nonnegligent Homicide (09A).” If this
is not the correct offense resubmit this LRS code with a
qualifier.
(WARNING # 22125)
8) 14:32.1 with no qualifier would be reported as Driving Under the
Influence (90D).
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as Driving Under the Influence (90D).” If this is not
the correct offense resubmit this LRS code with a qualifier.
(WARNING # 22025)
9) 14:44.1 with no qualifier would be reported as Kidnapping (100).
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as Kidnapping (100).” If this is not the correct
offense resubmit this LRS code with a qualifier.
(WARNING # 22030)
10) 14:65.1 with no qualifier would be reported as a Purse Snatching
(23B).
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as Purse-Snatching (23B)." If this is not the correct
offense resubmit this LRS code with a qualifier.
(WARNING # 22035)
11) 14:93 without a qualifier this LRS would be reported as a Family
Offense Nonviolent (90F).
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as Family Offense Nonviolent (90F).” If this is not
the correct offense resubmit this LRS code with a qualifier.
(WARNING # 22040)
12) 14:107.1 without a qualifier the offense will be reported as All
or Other Offenses (90Z). If this is not the correct offense
14:133.1 resubmit this LRS code with a qualifier.
DATA ELEMENT EDITS
32
RELEASE 2.1
Print Date: March 7, 2016
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as All Other Offenses (90Z).” If this is not the correct
offense resubmit this LRS code with a qualifier.
(WARNING # 22045)
13) 14:129.1
without a qualifier this LRS would be reported as a Simple
Assault (13B).
The reporting agency would receive a warning message that
says:
"WARNING -- This LRS submitted without a qualifier will be
reported as a Simple Assault (13B).” If this is not the correct
offense resubmit this LRS code with a qualifier.
(WARNING # 22050)
DATA ELEMENT EDITS
33
RELEASE 2.1
Print Date: March 7, 2016
HARD CODE EDITS on LRS with no Qualifier based on PROPERTY DESCRIPTIONS
14:67 with no qualifier would be reported as All Other Larceny-Theft (23H); or
other offenses as determined by hard codes as defined below.
14)
If LRS code of 14:67 is submitted without a qualifier and if DE #
15 is not equal to: "03", "05", "24", "28", or "37"; or "38"; or
"04", then the agency would receive this warning message:
"WARNING-- This LRS submitted without a qualifier will be
reported as All Other Larceny-Theft (23H)" If this is not the
correct property description code resubmit property description
code.
(WARNING # 22055)
15)
If LRS code of 14:67 is submitted without a qualifier and if DE #
15 = "38", which equals Theft of Motor Vehicle Parts (23G), then
the agency would receive this warning message:
"WARNING-- This LRS submitted without a qualifier and "38" in
DE # 15 will be reported as Theft of Motor Vehicle Parts (23G)."
If this is not the correct property description code resubmit
property description code.
(WARNING # 22060)
16)
If LRS code of 14:67 is submitted without a qualifier and if DE #
15 = "03", "05", "24", "28", or "37", which equals Motor Vehicle
Theft (240), then the agency would receive this warning message:
"WARNING -- This LRS submitted without a qualifier and "03",
"05", "24", "28", or "37" in DE # 15 will be reported as Motor
Vehicle Theft (240)." If this is not the correct property description
code resubmit property description code.
(WARNING # 22065)
17)
If LRS code of 14:67 is submitted without a qualifier and if DE #
15 = "04", which equals theft of a bicycle, then the agency would
receive this warning message:
"WARNING -- This LRS submitted without a qualifier and "04" in
DE # 15 will be reported as theft of a bicycle." If this is not the
correct property description code resubmit property description
code.
(WARNING # 22070)
14:68 would be reported as All Other Larceny-Theft (23H); or Motor Vehicle
Theft (240) as determined by hard codes as defined below.
DATA ELEMENT EDITS
34
RELEASE 2.1
Print Date: March 7, 2016
18)
19)
If LRS code of 14:68 is submitted and if DE # 15 is not equal to:
“03", “05", “24", “28" or “37", then the agency would receive this
warning message:
“WARNING-- This LRS submitted will be reported as All Other
Larceny-Theft (23H).” If this is not the correct property
description code resubmit property description code.
(WARNING # 22071)
If LRS code of 14:68 is submitted and if DE # 15 = “03", “05",
“24", “28" or “37", which equals Motor Vehicle Theft (240), then
the agency would receive this warning message:
“WARNING-- This LRS submitted and “03", “05", “24", “28" or
“37", in DE # 15 will be reported as Motor Vehicle Theft (240).” If
this is not the correct property description code resubmit property
description code.
(WARNING # 22072)
ALLOWED ENTRIES
for JUVENILE
QUALIFIERS:
In order to capture juvenile specific reportable offenses that do not relate
to any of the LRS codes, LIBRS will accept the following identifiers in lieu
of a LRS code:
An Agency should submit the following codes in this data element for
juvenile specific offenses:
JU:CUR = Juvenile Curfew Violations would be reported as
Curfew/Loitering/Vagrancy Violations (90B - Society)
JU:RUN = Juvenile Runaways would be reported under Runaways
offense (90I - Society - Not a crime)
JU:TRU = Juvenile Truancy would be reported as All Other Offenses
(90Z - Society - not a crime)
JU:UNG = Juvenile Ungovernables would be reported under Disorderly
Conduct offense (90C - Society)
20)
DATA ELEMENT EDITS
When Juvenile Qualifiers are used the age must be “01" - “16" for a
JU:RUN - Runaway Offense (90I), JU:UNG - Ungovernable (90C),
JU:CUR - Curfew (90B), or JU:TRU - Truancy (90Z).
(Error Message 22100)
35
RELEASE 2.1
Print Date: March 7, 2016
ALLOWED
ENTRIES FOR
INCHOATES:
When LRS Codes of 14:25, 14:26, 14:28 and 14:107.2 are applicable the
LRS code of the actual offense must be submitted and immediately
proceeding the dash the data values listed below would indicate which
inchoate would be applicable to this LRS charge. Only the following
modifiers can be used:
Enter only one code per Louisiana Revised Statute Offense (i.e. if LRS
charge is aggravated assault of 14:87.2/F and the offender or the arrestee
was responsible for accessory after the fact then the agency would submit
the following: 14:87.2/F-A, this would be reported as an aggravated
assault, accessory after the fact as the offense and for LIBRS reporting
this would be considered an All Other Offenses (90Z).
When a LRS Code is a Group A Offense and is submitted with the
inchoates of "-A", "-C", "-I", or "-S" appended, the offense is reported to
NIBRS as all other offenses (90Z).
When a LRS Code is a Group B Offense and is submitted with the
inchoates of "-A", "-C", "-I", or "-S" appended, the offense is reported to
NIBRS as the appropriate Group B Offense as defined on the LIBRS/LRS
Master Code Table.
Only one modifier can be used per LRS offense:
LRS MODIFIERS (inchoates).
-A
- Accessory After the Fact
-C
- Conspiracy
-I
- Inciting a Felony
-S
- Solicitation
-H
- Hate Crime Penalty Enhancer
Requirements:
When 14:28.1 Solicitation for Murder is used this LRS would be
submitted without a qualifier. This offense will be reported as an All Other
Offense (90Z) for LIBRS reporting.
When 14:24 Principal is used as an LRS charge, since this is a
definitional LRS and does not carry any penalties, it is not necessary to
submit this LRS to LIBRS.
21)
DATA ELEMENT EDITS
If the LRS Code is appended with "-A", "-C", "-I", "-S" or "-H"
this means the offense was an inchoate of the LRS Offense shown
in first ten digits of DE # 6 or DE # 45. These modifiers for the LRS
36
RELEASE 2.1
Print Date: March 7, 2016
Code should always be considered "Completed", even if the
principal LRS offense was not. The offender completed the
conspiracy, even if the offense itself was not completed by the
offender conspired with.
(Error Message 22085)
When a LRS Code is submitted with the inchoate of "-H" appended, the
LRS would be reported to NIBRS under the offense code defined on the
LIBRS/LRS Master Code Table.
Note: If LRS Code is appended with "-H" this means the offense was a
hate crime and the penalty has been enhanced by 14:107.2. This
offense will be reported based on the LRS shown on the first ten
digits of DE # 6 or DE # 45.
DATA ELEMENT EDITS
37
RELEASE 2.1
Print Date: March 7, 2016
QUALIFIERS FOR LRS BREAKDOWN
Qualifiers must be associated with the LRS Codes as shown in the LIBRS/LRS Master
Code Table. Only the combinations shown on this table qualify as a valid entry in Data
Element # 6 (LRS of Offense) and Data Element # 45 (LRS of Arrest Offense). An agency
cannot append these qualifiers to any LRS Code to classify offense to be reported,
unless it is a valid LRS Code combination as classified on the LIBRS/LRS Master Code
Table.
AA
=
A
=
B
=
C
=
E
=
F
=
G
=
H
=
I
=
J
JU:CUR
=
=
Vehicular homicide with intent to kill (Murder and Nonnegligent
Manslaughter - 09A - Person)
Anal penetration Anal sexual intercourse with another person, forcibly
and/or against that person's will; or not forcibly or against the persons will
where the victim is incapable of giving consent because of his/her youth or
because of his/her temporary or permanent mental or physical incapacity.
(Forcible Sodomy - 11B - Person)
Theft from Building A theft from within a building which is either open to
the general public or where the offender has legal access. (Theft from
Building - 23D - Property)
Theft from Coin Operated Machine A theft from a machine or device
which is operated or activated by the use of coins. (Theft from Coin
Operated Machine - 23E - Property)
Embezzlement The unlawful misappropriation by an offender to his/her
own use or purpose of money, property, or some other thing of value
entrusted to his/her care, custody, or control. (Embezzlement - 270 Property)
Actual force was used against the victim or threat of force displaying a
weapon (i.e. of strong arm robbery would be used to determine whether
the purse snatching is to be reported as strong-arm robbery or as larcenytheft--14:65.1/F and 14:65.1) (Aggravated Assault - 13A - Person, or
Robbery- 120 - Person)
Betting and Wagering To unlawfully stake money or something else of
value on the happening of an uncertain event or on the ascertainment of a
fact in dispute. (Betting/Wagering - 39A - Society)
Inhabited Dwelling A structure occupied as a place of settled residence or
habitat (lived in regularly or routinely). Arson reporting (Arson - 200 Property)
Immovable Structures Fixed permanent or immovable things; include
house trailer or houseboat if used as permanent dwelling.
Burglary - The unlawful entry into a building or other structure with the
intent to commit a felony or a theft. Trespass of Real Property - To
unlawfully enter land, a dwelling, or other real property. (Burglary - 220 Property, or Trespass of Real Property - 90J - Society)
Self inflicted serious bodily injuries (All Other Offenses - 90Z - Person)
Juvenile Curfew Violations would be reported as curfew/loitering/vagrancy
violations (Curfew/Loitering/Vagrancy Violations - 90B - Society)
DATA ELEMENT EDITS
38
RELEASE 2.1
Print Date: March 7, 2016
JU:RUN
=
JU:TRU
=
JU:UNG
=
K
=
L
=
M
=
N
=
0
=
P
=
Q
=
R
=
S
=
T
=
U
=
V
=
Juvenile Runaways would be reported under runaways offense (Runaway
- 90I - Society - Not a Crime)
Juvenile Truancy Absent from school without permission. Reported to
NIBRS under All Other Offenses (90Z - Society - Not a Crime)
Juvenile Ungovernables would be reported under disorderly conduct
(Disorderly Conduct - 90C - Society)
Pocket Picking The theft of articles from another person's physical
possession by stealth where the victim usually does not become
immediately aware of the theft. (Pocket Picking - 23A - Property)
Murder and Nonnegligent manslaughter The willful (nonnegligent) killing
of one human being by another (human being live born--not an embryo or
fetus in utero) (Murder and Nonnegligent manslaughter - 09A - Person)
Movable Structures (motor vehicles, tents, recreational vehicles, etc.--not
permanent dwellings--Larceny Theft) (All Other Larceny - 23H- Property)
Rubbing/touching No actual penetration-"indecent liberties", "child
molesting", no elements of 11A, B or C were applicable (Forcible Fondling
- 11D - Person)
Oral intercourse Oral sexual intercourse with another person, forcibly
and/or against that person's will; or not forcibly or against the persons will
where the victim is incapable of giving consent because of his/her youth or
because of his/her temporary or permanent mental or physical incapacity.
(Forcible Sodomy - 11B - Person)
Sexual Assault With an Object To use an object or instrument to
unlawfully penetrate, however slightly, the genital or anal opening of the
body of another person, forcibly and/or against that person's will; or not
forcibly or against the persons will where the victim is incapable of giving
consent because of his/her youth or because of his/her temporary or
permanent mental or physical incapacity. (Sexual Assault With an Object 11C - Person)
Victim had offender to inflict serious bodily injuries to him/her (victim made
the offender inflict injuries to his/her person--no intent on part of the
offender) (Aggravated Assault - 13A - Person)
Operating/Assisting Gambling To unlawfully operate, promote, or assist in
the operation of a game of chance. (Operating/Promoting/ Assisting
Gambling - 39B - Property)
Shoplifting The theft, by someone other than an employee of the victim, of
goods or merchandise exposed for sale. (Shoplifting - 23C - Property)
Threat of force was used against the victim (no weapons and no physical
attack used in this threat) (Intimidation - 13C - Person)
Uninhabited Dwelling Structures uninhabited or abandoned or not
normally in use. Arson reporting (Arson - 200 - Property)
Vaginal penetration with force or without force where the victim is
incapable of giving consent because of youth or because of temporary or
permanent mental incapacity (Forcible Rape - 11A - Person)
DATA ELEMENT EDITS
39
RELEASE 2.1
Print Date: March 7, 2016
W
=
X
=
Y
=
Z
=
Fetal Death a human embryo or fetus in utero (All Other Offenses - 90Z Society)
Falsified records by forgery or counterfeiting The altering, copying, or
imitation of something, without authority or right, with the intent to deceive
or defraud by passing the copy or thing altered or imitated as that which is
original or genuine; or the selling, buying, or possession of an altered,
copied, or imitated thing with the intent to deceive or defraud.
(Counterfeiting/Forgery - 250 - Property)
Destroyed records or property (Destruction/Damage/Vandalism of
Property - 290 - Property)
Theft from a Motor Vehicle The theft of articles from MV whether locked
or unlocked. (Theft from a Motor Vehicle - 23F - Property)
LRS MODIFIERS (INCHOATE)
-A
-C
-I
-S
-H
=
=
=
=
=
Accessory After the Fact
Conspiracy
Inciting a Felony
Solicitations
Hate Crime Penalty Enhancer
DATA ELEMENT # 7
OFFENSE ATTEMPTED/COMPLETED
1) Must be present -- cannot be blank.
(Error Message 12001)
2) Must be a valid code of "A" = Attempted or "C" = Completed.
(Error Message 12051)
3) If "A" = Attempted is entered and Data Element # 6 (Louisiana
Revised Statute Number) is a "Crime Against Property,"
Gambling, Kidnapping or Drug/Narcotic offenses (see Master
LIBRS/LRS Code Table), Data Element # 14 (Type Property
Loss/Etc.) must be "1" = None or "8' = Unknown.
(Error Message 10077)
4) If Data Element # 6 (Louisiana Revised Statute Number) was a
"Crime Against Property", Kidnapping (100), Gambling (39A and
39B), or Drug Offenses (35A and B), and Data Element # 7
(Offense Attempted/Completed) was "C" = Completed, a
Property Segment (Segment 30 and 31) must be sent with a
valid code in Data Element # 14 (Type Property Loss/Etc.).
(Error Message 10078)
DATA ELEMENT EDITS
40
RELEASE 2.1
Print Date: March 7, 2016
5) Data Element # 7 (Offense Attempted/Completed) code must
be "C" = Completed if Data Element # 6 (Louisiana Revised
Statute Number) is an "Assault" or "Homicide."
(Error Message 12056)
DATA ELEMENT # 8
OFFENDER SUSPECTED of USING/ GAMING MOTIVATION
*Offender Segment
1) Must be present -- cannot be blank.
(Error Message 14001)
2) Must be a valid code.
(Error Message 14004)
3) If more than one code entered, cannot be a duplicate.
(Error Message 12006)
4) Value "N" = Not Applicable is mutually exclusive of any other
value entered, i.e., "N" is to be entered only if no other code
applies.
(Error Message 12007)
DATA ELEMENT # 8A
BIAS MOTIVATION/BIAS CRIME TYPE
*Offender Segment
1) Must be present -- cannot be blank.
(Error Message 14001)
2) Must be a valid code.
(Error Message 14004)
DATA ELEMENT # 9
LOCATION TYPE
1) Must be present -- cannot be blank.
(Error Message 12001)
2) Must be a valid code.
(Error Message 12004)
DATA ELEMENT # 10
DATA ELEMENT EDITS
NUMBER of PREMISES ENTERED
41
RELEASE 2.1
Print Date: March 7, 2016
1) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on the Master LIBRS/LRS Code Table of: 220 and
Louisiana Revised Statute Number is one of the following:
14:62/I
14:62.1
14:62.4
14:62.5
14:228/A4
Requirement 1
14:62.2
14:62.6
14:62.3
14:130.1/I
and Data Element # 9 (Location Type) contains "14" =
Hotels/Motels/Etc. or "19" = Rental Storage Facility.
(Error Message 12057)
2) Must be numeric entry of 01-99 if entered.
(Error Message 12002)
3) When entered, Data Element # 9 (Location Type) must be "14" =
Hotel/Motel/Etc. or "19" = Rental Storage Facility, and Data
Element # 6 has a NIBRS offense code as defined on the
Master LIBRS/LRS Code Table of: 220 and Louisiana Revised
Statute Number is one of the following:
14:62/I
14:62.1
14:62.4
14:62.5
14:228/A4
Requirement 3
(Error Message 12052)
DATA ELEMENT # 11
14:62.2
14:62.6
14:62.3
14:130.1/I
METHOD of ENTRY
1) Must be a valid code.
(Error Message 12004)
2) Must be entered if Data Element # 6 have a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of: 220
(Burglary) and Louisiana Revised Statute Number is one of the
following:
14:62/I
14:62.1
14:62.4
14:62.5
14:228/A4
Requirement 2
(Error Message 12053)
DATA ELEMENT EDITS
42
RELEASE 2.1
14:62.2
14:62.6
14:62.3
14:130.1/I
Print Date: March 7, 2016
3) Must be blank when offense code is not 220 (Burglary) and
Louisiana Revised Statute Number is not one of the
following:
14:62/I
14:62.1
14:62.4
14:62.5
14:228/A4
Requirement 3
(Error Message 12054)
DATA ELEMENT # 12
14:62.2
14:62.6
14:62.3
14:130.1/I
TYPE of CRIMINAL ACTIVITY/GANG INFORMATION
1) Must be a valid code.
(Error message 12004)
2) If more than one code entered, cannot be a duplicate.
(Error message 12006)
3) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on the Master LIBRS/LRS Code Table of: 250;
280; 35A, 35B; 39C; 370; 520; 90A and 90Z "Crime Against
Property" and LRS is one of the following:
14:30.1/D
14:59/A2
14:59/A7
14:71
14:73.4
14:91
14:95.1
14:95.7
14:130.1/X
14:202
14:209
14:218
14:224
14:228/A7
14:353
32:292
40:966
40:970
40:971/B1F
40:981.1
40:989
DATA ELEMENT EDITS
14:54.2
14:59/A4
14:59/A8
14:72
14:81.1
14:91.11
14:95.2
14:102.6
14:133
14:203
14:210
14:223
14:226
14:228.1
14:513
32:373
40:967
40:971/B1BX
40:971B1G
40:981.2
40:1032
43
RELEASE 2.1
14:54.3
14:59/A5
14:59/A9
14:72.1
14:85.1
14:94/F
14:95.5
14:106
14:134.2
14:204
14:211
14:223.7
14:228/A1
14:229
27:263
32:378.1
40:968
40:971/B1D
40:971.1
40:981.3
40:1033
14:59/A1
14:59/A6
14:69
14:72.2
14:90.1
14:95
14:95.6
14:106.1
14:201
14:208
14:212
14:223.8
14:228/A6X
14:230
32:291
40:962.1
40:969
40:971/B1E
40:981
40:982
40:1033.1
Print Date: March 7, 2016
40:1783
40:1784
40:1788
40:1789
Requirement 3
(Error Message 12019)
40:1785
40:1792
40:1787
4) Must be entered if DE # 6 has a NIBRS offense code as
defined in the Master LIBRS/LRS Code Table of: 09A, 09B,
100, 120, 11A, 11B, 11C, 11D, 13A, 13B, or 13C and LRS is
one of the following:
14:30
14:30.1
14:32.1/AA
14:34
14:34.3
14:34.4
14:35.1
14:37
14:38
14:38.1
14:39.2
14:40
14:42/A
14:42/V
14:43/A
14:43/V
14:43.2/N
14:43.2/P
14:43.5
14:44
14:44.1/N
14:44.1/O
14:45
14:45.1
14:60
14:64
14:65
14:65.1/F
14:87.2/F
14:87.2/L
14:89.1
14:92.3
14:94/E
14:103/A1
14:122/T
14:122.1
14:129/A2F
14:129/A2T
14:129.1/T
14:130.1/A
14:133.1/F
14:133.1/T
14:501
Requirement 4
(Error Message 12019)
14:31
14:34.1
14:34.5
14:37.1
14:38.2
14:40.1
14:42.1/A
14:43.1/N
14:43.3
14:44.1
14:44.1/P
14:46
14:64.1
14:81.2
14:87.5/F
14:93/F
14:107.1/F
14:122.2
14:129.1
14:130.1/T
14:285
14:32
14:34.2
14:35
14:37.2
14:39.1
14:40.2
14:42.1/V
14:43.1/P
14:43.4
14:44.1/A
14:44.1/V
14:46.1
14:64.2
14:87.1
14:87.5/L
14:93.5
14:122/F
14:129/A1
14:129.1/F
14:130.1/F
14:404/Q
5) Value "N" = None\Unknown is mutually exclusive with any
other gang information codes.
(Error Message 12007)
DATA ELEMENT # 13
TYPE of WEAPON/FORCE INVOLVED
1) Must be a valid code.
(Error Message 12004)
DATA ELEMENT EDITS
44
RELEASE 2.1
Print Date: March 7, 2016
2) If more than one code entered, cannot be a duplicate.
(Error Message 12006)
3) Value "99" = None is mutually exclusive with any other value, i.e.
"99" to be entered only if no other code applies.
(Error Message 12007)
4) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on Master LIBRS/LRS Code Table of: 09A, 09B,
or 09C; 100; 11A, 11B, 11C,or 11D; 120; 13A or 13B; 210; or
520 and Louisiana Revised Statute Number is one of the
following:
14:20
14:30
14:32
14:32.1/AA
14:34.2
14:34.3
14:35
14:35.1
14:37.2
14:38
14:39.1
14:39.2
14:42.1/V
14:42.1/A
14:43.1/P
14:43.1/N
14:43.3
14:43.4
14:44.1
14:44.1/V
14:44.1/P
14:44.1/N
14:46
14:46.1
14:59/A9
14:60
14:64.2
14:65
14:81.2
14:87.1
14:87.5/F
14:87.5/L
14:93/F
14:93.5
14:95
14:95.1
14:95.6
14:95.7
14:122/F
14:129/A2F
14:130.1/A
14:130.1/F
14:136
14:404/Q
14:512
32:292
40:1785
40:1787
40:1792
Requirement 4
(Error Message 12019)
14:30.1
14:34
14:34.4
14:37
14:38.1
14:42/V
14:43/A
14:43.2/P
14:43.5
14:44.1/A
14:45
14:54.2
14:64
14:65.1/F
14:87.2/F
14:89.1
14:94/E
14:95.2
14:103/A1
14:129.1
14:133.1/F
14:501
40:1783
40:1788
14:31
14:34.1
14:34.5
14:37.1
14:38.2
14:42/A
14:43/V
14:43.2/N
14:44
14:44.1/O
14:45.1
14:54.3
14:64.1
14:66
14:87.2/L
14:91
14:94/F
14:95.5
14:107.1/F
14:129.1/F
14:135
14:511
40:1784
40:1789
5) If the firearm is an Automatic, add "A" as the third character;
valid only with codes: "11"= Firearm (Type not Stated), "12" =
Handgun, "13" = Rifle, "14" = Shotgun, and "15" = Other
Firearm.
DATA ELEMENT EDITS
45
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 12058)
6) The third character of the code must be "A" = Automatic or
blank.
(Error Message 12055)
7) If an Offense Segment (Segment 20) was submitted for one of
the following Louisiana Revised Statute Numbers, the offense
would be reported as a simple assault (13B) and must have
codes of "40", "90", "95", or "99" in this data element:
14:34.2
14:34.3
14:35.1
14:38
14:129.1
14:130.1/A
Requirement 7
14:34.4
14:38.2
14:35
14:103/A1
Data Element 13 (Type Weapon/Force Involved) can only
have codes of "40" = Personal Weapons, "90" = Other, "95" =
Unknown or "99" = None
(Error Message 12065)
8) If a homicide offense (09A, B or C) is submitted, Data Element
# 13 (Type Weapon/Force Involved) cannot have "99" = None.
Some type of weapon/force must be used in a homicide offense.
14:20
14:30
14:32
14:32.1/AA
14:87.5/L
14:501
Requirement 8
(Error Message 12067)
14:30.1
14:87.1
14:31
14:87.2/L
9) If Data Element # 6 (Louisiana Revised Statute Number) is a
simple assault (13B), but the weapon involved is "11", "12",
"13" "14", "15" or "11A", "12A", "13A", "14A", or "15A", then
this offense should be reported as an aggravated assault
(13A).
(Error Message 12069)
DATA ELEMENT EDITS
46
RELEASE 2.1
Print Date: March 7, 2016
PROPERTY SEGMENT EDITS
DATA ELEMENT # 14
TYPE of PROPERTY LOSS
1) Must be present -- cannot be blank.
(Error Message 13001)
2) Must be a valid code.
(Error Message 13004)
3) If "1" = None or "8" = Unknown, Data Elements 15 through 22
must be blank if offense is not a 35A (Drug Violation Offense).
The exception being when the offense is one of the following
LRS Drug Violation Offenses (35A):
14:30.1/D
40:968
40:981
40:982
40:962.1
40:969
40:981.1
40:989
40:966
40:970
40:981.2
40:967
40:971.1
40:981.3
If “1" = None is entered for one of the above LRS Codes,
(Suspected Drug Type) must be completed.
Requirement 3
(Error Message 13052)
The following edits would apply to the LRS codes listed above
only:
3a) If Data Element # 7 is "A" = Attempted, then Data Element
# 14 (Type of Property Loss) must be "1" = None or "8" =
Unknown. These are the only two data values accepted.
(Error Message 84001, 84003, 84104, 84105, 84006,
84107, 84108, 84009, 84010, 84112, 84013, 84014,
84117, 84120)
4) Must be entered if Data Element # 6 is a "Crime Against
Property" and has a NIBRS offense code as defined on
Master LIBRS/LRS Code Table of: 100; 120; 200; 210; 220;
23A, 23B, 23C, 23D,23E, 23F, 23G, 23H; 240; 250; 26A, 26B,
26C, 26D, 26E; 270; 280; 290; 35A, 35B; 39A, 39B, 39C, 39D;
510; 90A or 90Z if "Crime Against Property":
14:30.1/D
14:45.1
14:51/U
DATA ELEMENT EDITS
14:44
14:46
14:51.1/H
47
RELEASE 2.1
14:44.1
14:46.1
14:51.1/U
14:45
14:51/H
14:52/H
Print Date: March 7, 2016
14:52/U
14:54/U
14:56.2
14:59/A2
14:59/A6
14:60
14:62.1
14:62.5
14:64.1
14:65.1/F
14:67/C
14:67/Z
14:67.4
14:67.8
14:67.13
14:68.1
14:69
14:70.3
14:71.2
14:73
14:73.5
14:90.2/G
14:101
14:112
14:118.2
14:126.3
14:130.1/Y
14:133.3
14:138
14:140
14:203
14:206
14:210
14:214
14:220
14:222.1
14:223.7
14:226
14:228/A3
14:228/A6X
14:230
14:353
27:98/B
27:100/B
27:264/B
DATA ELEMENT EDITS
14:53/H
14:55
14:57
14:59/A3
14:59/A7
14:62/I
14:62.2
14:62.6
14:64.2
14:66
14:67/E
14:67.1
14:67.5
14:67.9
14:67.14
14:68.2
14:70
14:70.4
14:72
14:73.2
14:90/G
14:90.2/R
14:102.5
14:112.1
14:119
14:130.1/B
14:131
14:134.2
14:139
14:141
14:204
14:207
14:211
14:217
14:220.1
14:223
14:223.8
14:227
14:228/A4
14:228/A7
14:331
14:511
27:98/C
27:262
32:291
48
RELEASE 2.1
14:53/U
14:56
14:58
14:59/A4
14:59/A8
14:62/M
14:62.3
14:63.2
14:65
14:67
14:67/K
14:67.2
14:67.6
14:67.10
14:67.15
14:68.3
14:70.1
14:71
14:72.1
14:73.3
14:90/R
14:90.3
14:102.6
14:118
14:119.1
14:130.1/I
14:132
14:135
14:139.1
14:201
14:205/H
14:208
14:212
14:218
14:221
14:223.5
14:224
14:228/A1
14:228/A6
14:228.1
14:351
14:512
27:99
27:263
32:373
14:54/H
14:56.1
14:59/A1
14:59/A5
14:59/A10
14:62/Z
14:62.4
14:64
14:65.1
14:67/B
14:67/S
14:67.3
14:67.7
14:67.11
14:68
14:68.4
14:70.2
14:71.1
14:72.2
14:73.4
14:90.1
14:93.4
14:102.10
14:118.1
14:120
14:130.1/X
14:133
14:136
14:139.2
14:202
14:205/U
14:209
14:213
14:219
14:222
14:223.6
14:225
14:228/A2
14:228/A6Y
14:229
14:352
14:513
27:100/A
27:264/A
32:421
Print Date: March 7, 2016
40:962.1
40:966
40:969
40:970
40:971/B1C 40:971/B1H
40:971/B1E 40:971/B1F
40:975
40:981
40:981.3
40:982
40:1033
40:1033.1
Requirement 4
(Error Message 13019)
40:967
40:971/B1A
40:971/B1BX
40:971/B1G
40:981.1
40:989
40:1321.G
40:968
40:971/B1B
40:971/B1D
40:971.1
40:981.2
40:1032
46:114.2
5) If "5" = Recovered, every property description code entered into
Data Element # 15 (Property Description) must also have been
reported as "7" = Stolen/Etc. This applies to both initial
submissions and resubmissions for incident reports with
Segment Action Type "I" = Incident Report. This does not apply,
of course, for offenses that allow "recovered" property without
first being "stolen." (does not apply to NIBRS offense codes of
280 and 250) Nor does it apply when Property Description
Code "38" = Vehicle Parts/Accessories is subsequently
reported as recovered when a vehicle was stolen.
(Error Message 10072 modified)
6) If code is "2" = Burned, "3" = Counterfeited/Forged, "4" =
Destroyed /Damaged/Vandalized, "5" = Recovered, "6" = Seized,
or "7" = Stolen/Etc., Data Elements # 15-22 must have
applicable entries in this segment.
(Error Message 13072)
7) When submitting Segment Action Type of "W" = Time-Window
Submission or "M" = Modify, Data Element # 14 (Type of
Property Loss/Etc.) must be "5" = Recovered.
(Error Message 13078)
8) When there is only one completed property offense in an
incident, a property segment can contain a "7" = Stolen
Property or an "8" = Unknown. The incident will reject if an
agency sends a "7" and also an "8" within the same
incident, when there is only one completed property offense
within the incident.
(Error Message 84203, 84304, 84312)
9) To ensure that 35A-35B Drug/Narcotic Offenses are properly
reported, Data Element # 15 (Property Description) cannot
be "11" = Drug/Narcotic Equipment for a 35A Drug/Narcotic
DATA ELEMENT EDITS
49
RELEASE 2.1
Print Date: March 7, 2016
Violation. Similarly, "10" = Drug/Narcotics cannot be
entered for a 35B Drug Equipment Violation. This is
enforced by software when there is a single "Crime Against
Property" offense.
However, in multiple "Crimes Against Property" offenses
where one offense is a 35A Drug/Narcotic Violation and
the other is, say, a 120 Robbery that involves "11" =
Drug/Narcotic Equipment, it can be entered. In this case,
the above edit will be bypassed. Similarly, "10" =
Drugs/Narcotics can be entered along with a 35B Drug
Equipment Violation as long as that property is involved
in the 120 Robbery.
(Error Message 13087)
10) Property Loss Code must be applicable to offense(s)
submitted in Data Element 6. Refer to (Mandatories) for
the correct values to use for each of the offenses.
(Error Message 10081)
DATA ELEMENT # 15
PROPERTY DESCRIPTION
1) Must be a valid code.
(Error Message 13004)
2) If more than one code entered, cannot be a duplicate.
(Error Message 13006)
3) If "88" = Pending Inventory is entered, then Data Element # 16
(Value of Property) must be "1" = Unknown ($1.00). One dollar
is used as a quality assurance edit check that instructs the
State's computer to accept the "88"= Pending inventory entry.
(Error Message 13053)
4) At least one description code must be entered when Data
Element # 14 (Type Property Loss/etc.) contains Property
Segment(s) for: "2" = Burned, "3" = Counterfeited/Forged, "4" =
Destroyed / Damaged / Vandalized, "5" = Recovered, "6" =
Seized, "7" = Stolen/Etc.
(Error Message 13075)
5) If Data Element # 14 (Type Property Loss/etc.) contains "5" =
Recovered, every property description code entered into Data
Element # 15 (Property Description) must also have been
DATA ELEMENT EDITS
50
RELEASE 2.1
Print Date: March 7, 2016
reported in Data Element # 14 (Type Property Loss/etc.) as "7" =
Stolen/Etc. This applies to both initial submissions and
resubmissions for incident reports with Segment Action Type "I"
= Incident Report. This does not apply, of course, for offenses
(refers to NIBRS offenses of 250 and 280) that allow
"recovered" property without being first "stolen." Nor does it
apply when Property Description Code "38" = Vehicle
Parts/Accessories is subsequently reported as recovered
when a vehicle was stolen.
(Error Message 10072 modified)
DATA ELEMENT # 16
VALUE of PROPERTY
1) Must be numeric entry with zero or blank left-fill if entered.
(Error Message 13002)
2) If value is unknown, must have a value of "1" = Unknown
($1.00). A value of zero is allowed only for property description
codes of: "09" = Credit/Debit Cards, "22" = Nonnegotiable
Instruments, "77" = Other, "99" = (special category). Note that
codes "09" and "22" require that a zero value be submitted.
(Error Message 13051)
3) If Data Element # 15 (Property Description) has a code of "09" =
Credit/Debit Cards or "22" = Nonnegotiable Instruments, a zero
value is required for Data Element # 16 (Value of Property).
(Error Messages 13091)
NOTE: This edit was formerly warning message #
13040.
4) If a value is entered, then Data Element # 15 (Property
Description) must be entered.
(Error Message 13054)
5) When Data Element # 14 (Type Property Loss/etc.) entries are
made for both "7" = Stolen/Etc. and "5" = Recovered, the
recovered "property" cannot have property value(s) greater than
corresponding property value(s) reported stolen.
(Error Message 10084)
6) When Data Element # 16 (Value of Property) contains a value
that exceeds a LIBRS assigned threshold amount, a "warning"
message will be created. The participant is asked to check to
see if the value entered was a data entry error, or if it was
DATA ELEMENT EDITS
51
RELEASE 2.1
Print Date: March 7, 2016
intended to be entered. A warning message is always produced
when the value is $1,000,000 or greater. For example, if the
value of a property was $12,000.99 but was inadvertently
entered as $1,200,099 in the computer record sent to LIBRS, a
"warning" message will be generated. In this case, the cents
were entered as whole dollars.
(Error Message 13042)
DATA ELEMENT # 17
DATE RECOVERED
1) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). The
date cannot be greater than that entered within the "Month of
Tape" and "Year of Tape" fields on the data record. For
example, if "Month of Tape" and "Year of Tape" are "06/1995,"
the recovered date cannot contain any date 07/01/1995 or
greater.
(Error Message 13007)
2) Cannot be earlier than Data Element # 3 (Incident Date/Hour).
(Error Message 13005)
3) If entered, then both Data Elements # 15 (Property Description)
and # 16 (Value of Property) must be entered.
(Error Message 13056)
4) If entered, Data Element # 14 (Property Type Loss/etc.) must be
"5" = Recovered.
(Error Message 13055)
5) Property Segments (Segment 31) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot have a
Date Recovered (Data Element # 17) before the date which is
calculated using the base date technique (January 1 of the year
prior to the current year, or earlier than the date the agency went
IBR). For any subsequent "M" = Modify of a previously
submitted "W" = Time-Window Submission, this edit also
applies.
(Error Message 13020)
DATA ELEMENT # 18
DATA ELEMENT EDITS
NUMBER of STOLEN VEHICLES
52
RELEASE 2.1
Print Date: March 7, 2016
1) Must be numeric entry with zero left-fill if entered.
(Error Message 13002)
2) Must be entered if Data Element # 6 has a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of: 240 or
hard coded edit based on Data Element # 15 (Property
Description) having Motor Vehicle codes as property being
stolen and the Louisiana Revised Statute Number is one of the
following:
14:67
14:68
Requirement 2
14:68.4
Data Element # 14 (Type Property Loss/Etc.) must be "7" =
Stolen/Etc and Data Element # 7 (Offense Attempted/
Completed) must also be "C" = Completed.
(Error Message 13057)
3) Entry must be made when Data Element # 6 has a NIBRS
offense code as defined on Master LIBRS/LRS Code Table
of: 240 or hard coded edit based on Data Element # 15
(Property Description) having Motor Vehicle codes as
property being stolen and the Louisiana Revised Statute
Number is one of the following:
14:67
14:68
Requirement 3
14:68.4
And Data Element # 14 (Type Property Loss/Etc.) is "7" =
Stolen/Etc and Data Element # 7 (Offense Attempted/
Completed) is "C" = Completed.
(Error Message 13058)
4) Data Element # 15 (Property Description) must contain at least
one of the following vehicle codes:
"03" - Automobiles
"05" - Buses
"24" - Other Motor Vehicles
"28" - Recreational Vehicles
"37" - Trucks
(Error Message 13059)
5) If more than one vehicle code is entered in Data Element # 15
(Property Description), entry must be equal to or greater than
DATA ELEMENT EDITS
53
RELEASE 2.1
Print Date: March 7, 2016
this number of different codes, unless the number of stolen
vehicles is unknown ("00").
(Error Message 13088)
6) If LRS code of 14:67 is submitted without a qualifier and if DE
# 15 = "03", "05", "24", "28", or "37", which equals Motor
Vehicle Theft (240), then the agency would receive this warning
message:
"WARNING -- This LRS submitted without a qualifier and
"03", "05", "24", "28", or "37" in DE # 15 will be reported
as Motor Vehicle Theft (240)." If this is not the correct
property description code resubmit property description
code.
(WARNING # 22065)
7) If LRS code of 14:68 is submitted and if DE # 15 is not equal to:
“03", “05", “24", “28" or “37", then the agency would receive
this warning message:
“WARNING-- This LRS submitted will be reported as All
Other Larceny-Theft (23H).” If this is not the correct
property description code resubmit property description
code.
(WARNING # 22071)
8) If LRS code of 14:68 is submitted and if DE # 15 = “03", “05",
“24", “28" or “37", which equals Motor Vehicle Theft (240), then
the agency would receive this warning message:
“WARNING-- This LRS submitted and “03", “05", “24",
“28" or “37", in DE # 15 will be reported as Motor Vehicle
Theft (240).” If this is not the correct property description
code resubmit property description code.
(WARNING # 22072)
9) Data Element # 18 must be left blank if the LRS Offense is
not reported as a Motor Vehicle Theft (240) or hard coded
edit based on Data Element # 15 (Property Description) does
not list one of the following Motor Vehicle codes as Stolen
property: “03", “05", “24", “28" or “37"
(Error Message 23220)
DATA ELEMENT # 19
NUMBER of RECOVERED MOTOR VEHICLES
1) Must be a numeric entry with zero left-fill if entered.
(Error Message 13002)
DATA ELEMENT EDITS
54
RELEASE 2.1
Print Date: March 7, 2016
2) Must be entered if Data Element # 6 has a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of: 240 or
hard coded edit based on Data Element # 15 (Property
Description) having Motor Vehicle codes as property being
recovered and Louisiana Revised Statute Number is one of the
following:
14:67
14:68
Requirement 2
14:68.4
And when Data Element # 14 (Type Property Loss/Etc.) is "5"
= Recovered.
(Error Message 13060)
3) When entry is 01 to 99, it must be equal to or less than the
number reported stolen in Data Element # 18 (Number of Stolen
Motor Vehicles).
(Error Message 10073)
4) Entry must be made when Data Element # 6 has a NIBRS
offense code as defined on Master LIBRS/LRS Code Table
of: 240 or hard coded edit based on Data Element # 15
(Property Description) having Motor Vehicle codes as
property being recovered and Louisiana Revised Statute
Number is one of the following:
14:67
14:68
Requirement 4
14:68.4
And Data Element # 14 (Type Property Loss/Etc.) is "5" =
Recovered, and Data Element # 15 (Property Description)
contains a vehicle code.
(Error Message 13061)
5) When entry is "01" to "99," Data Element # 15 (Property
Description) must contain at least one of the following vehicle
codes:
"03" - Automobiles
"05" - Buses
"24" - Other Motor Vehicles
"28" - Recreational Vehicles
"37" - Trucks
(Error Message 13059)
DATA ELEMENT EDITS
55
RELEASE 2.1
Print Date: March 7, 2016
6) More than one vehicle code was entered in Data Element #
15 (Property Description), but the number recovered in Data
Element # 19 (Number of Recovered Motor Vehicles) was
less than this number. For example, if vehicle codes of "03"
= Automobiles and "05" = Buses were entered as being
recovered, then the number recovered must be at least 2,
unless the number recovered was unknown ("00").
(Error Message 13089)
7) Data Element # 19 must be left blank if the LRS Offense is
not reported as a Motor Vehicle Theft (240) or hard coded
edit based on Data Element # 15 (Property Description) does
not list one of the following Motor Vehicle codes as
Recovered property: “03", “05", “24", “28" or “37"
(Error Message 23230)
DATA ELEMENT # 20
SUSPECTED DRUG TYPE
1) Must be entered if Data Element # 6 has a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of: 35A
and Louisiana Revised Statute Number is one of the following:
14:30.1/D
40:962.1
40:968
40:969
40:981
40:981.1
40:982
40:989
Requirement 1
40:966
40:970
40:981.2
40:967
40:971.1
40:981.3
And, "6" = Seized was entered into Data Element # 14 (Type
Property Loss/Etc.), and "10" = Drugs/Narcotics was entered
in Data Element # 15 (Property Description). If there are other
offenses involved and "10" = Drugs/Narcotics was split
between the different types of offenses, only enter the drug
types applicable to the offenses listed above.
(Error Message 13065)
2) If more than one code is entered, the same code cannot be
entered within the same category in Data Element # 22 (Type
Drug Measurement). In other words, cocaine cannot be reported
in grams and pounds (same weight category), but could be
reported in grams and liters (weight and capacity categories).
For the drug type of "U" = Unknown this does not apply; "U"
= Unknown can be entered only once.
(Error Message 13006)
DATA ELEMENT EDITS
56
RELEASE 2.1
Print Date: March 7, 2016
3) Must be a valid code.
(Error Message 13004)
4) When Data Element # 6 has a NIBRS offense code as defined
on Master LIBRS/LRS Code Table of: 35A and Louisiana
Revised Statute Number is one of the following:
14:30.1/D
40:962.1
40:968
40:969
40:981
40:981.1
40:982
40:989
Requirement 4
40:966
40:970
40:981.2
40:967
40:971.1
40:981.3
And, Data Element # 14 (Type Property Loss/Etc.) is "6" =
Seized, Data Element # 15 (Property Description) is "10" =
Drugs/Narcotics, and Data Element # 20 (Suspected Drug
Type) are entered, both Data Element # 21 (Estimated
Quantity), Data Element # 22 (Type Drug Measurement), and
Data Element # 16 (Value of Property) must be entered.
(Error Message 13064)
5) When Data Element # 6 has a NIBRS offense code as defined
on Master LIBRS/LRS Code Table of: 35A and the offense is
one of the following:
14:30.1/D
40:962.1
40:966
40:967
40:968
40:969
40:970
40:971.1
40:981
40:981.1
40:981.2
40:981.3
40:982
40:989
Requirement 5
And Data Element # 14 (Type Property Loss/Etc.) is "1" =
None, Data Element # 20 (Suspected Drug Type) is required.
If "6" = Seized was also reported, this edit is bypassed.
(Error Messages 13092)
NOTE: This edit was formerly warning message #
13041.
6) Second character must be "X" or Blank.
(Error Message 23201)
DATA ELEMENT # 21
ESTIMATED DRUG QUANTITY
1) Must be numeric entry with zero or blank left-fill and right-fill.
The decimal fractional quantity must be expressed in
DATA ELEMENT EDITS
57
RELEASE 2.1
Print Date: March 7, 2016
thousandths as three digits, and a decimal point must separate
the whole part of the number from the fractional part. This
decimal point must be the tenth character of the field.
(Error Message 13002)
2) If entered , Data Element # 20 (Suspected Drug Type), Data
Element # 22 (Type Drug Measurement) and Data Element # 16
(Value of Property) must also be entered.
(Error Message 13066)
3) This data element is valid only if Data Element # 6 has a NIBRS
offense code as defined on Master LIBRS/LRS Code Table
of: 35A and Louisiana Revised Statute Number is one of the
following:
14:30.1/D
40:962.1
40:968
40:969
40:981
40:981.1
40:982
40:989
Requirement 3
40:966
40:970
40:981.2
40:967
40:971.1
40:981.3
And, "6" = Seized was entered into Data Element # 14 (Type
of Property Loss), and "10" = Drugs/Narcotics was entered
into Data Element # 15 (Property Description).
(Error Message 13065)
DATA ELEMENT # 22
TYPE DRUG MEASUREMENT
1) Must be a valid code, if entered.
(Error Message 13004)
2) This data element is to be used if Data Element # 6 has a
NIBRS offense code as defined on Master LIBRS/LRS Code
Table of: 35A and Louisiana Revised Statute Number is one of
the following:
14:30.1/D
40:962.1
40:968
40:969
40:981
40:981.1
40:982
40:989
Requirement 2
DATA ELEMENT EDITS
58
RELEASE 2.1
40:966
40:970
40:981.2
40:967
40:971.1
40:981.3
Print Date: March 7, 2016
And, "6" = Seized was entered into Data Element # 14 (Type
of Property Loss), and "10" = Drugs/Narcotics was entered
into Data Element # 15 (Property Description).
(Error Message 13065 )
3) 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 to limit "NP" =
Number of Plants to the following drugs:
"E" = Marijuana
"G" = Opium
"K" = Other Hallucinogens
All other "Type Drug Measurement" codes are applicable to
any Data Element # 20 (Suspected Drug Type) code.
(Error Message 13067)
4) If entered, Data Element # 20 (Suspected Drug Type), Data
Element # 21 (Estimated Drug Quantity), and Data Element # 16
(Value of Property) must also be completed.
(Error Message 13068)
5) Data Element # 21 (Estimated Drug Quantity) must have a value
of "000000001.000" when "XX" = Not Reported is entered for
Data Element # 22 (Type Drug Measurement) and Data Element
# 16 (Value of Property) must be "1" = Unknown. Submission of
a Not Reported indication requires that a value of
"000000001.000" also be submitted as a quality assurance
check. Once the Type Drug Measurement has been determined,
a resubmission of the Incident would be done reflecting the
completed data.
(Error Message 13084)
6) If more than one code is entered, the same code cannot be
entered within the same category in Data Element # 22 (Type
Drug Measurement). In other words, cocaine cannot be reported
in grams and pounds (same weight category), but could be
reported in grams and liters (weight and capacity categories).
For the drug type of "U" = Unknown this does not apply; "U"
= Unknown can be entered only once.
(Error Message 13006)
DATA ELEMENT EDITS
59
RELEASE 2.1
Print Date: March 7, 2016
VICTIM SEGMENT EDITS
DATA ELEMENT # 23
VICTIM SEQUENCE NUMBER
1) Must be present -- cannot be blank.
(Error Message 15001)
2) Must be numeric entry (001 through 999) with zero left-fill. The
purpose of the field is to distinguish one victim from another.
(Error Message 15002)
3) Must be unique - cannot be duplicated
(Error Message 15051)
DATA ELEMENT # 24
OFFENSE CONNECTED to VICTIM SEQUENCE NUMBER
1) Must be present -- cannot be blank.
(Error Message 15001)
2) Must be a valid code.
(Error Message 15004)
3) If the Offense is a "Crime Against Person", and the offense is
connected to a victim, then Data Element # 25 (Type of Victim)
must be "I" = Individual or "L" = Law Enforcement Officer.
(Error Message 15064)
4) If the Offense is a "Crime Against Society", and the offense is
connected to a victim, then Data Element # 25 (Type of Victim)
must be "S" = Society.
(Error Message 15065)
5) Each victim sequence number entered must have a
corresponding Victim Segment.
(Error Message 15066)
6) When Data Element # 24 (Offense Connected to Victim
Sequence Number) relates to the offense of "13B" = Simple
Assault, there cannot be "major" injury codes which would
indicate an aggravated assault. The permissible codes are
"M" = Apparent Minor Injury and "N" = None.
(Error Message 15079)
DATA ELEMENT EDITS
60
RELEASE 2.1
Print Date: March 7, 2016
7) Each Segment # 20 must have a corresponding victim
segment.
(Error Message 10065)
DATA ELEMENT # 25
TYPE of VICTIM
1) Must be present -- cannot be blank.
(Error Message 15001)
2) Must be a valid code.
(Error Message 15004)
3) If the Offense is a "Crime Against Person", and the offense is
connected to a victim, then Data Element # 25 (Type of Victim)
must be "I" = Individual or "L" = Law Enforcement Officer.
(Error Message 15064)
4) If the Offense is a "Crime Against Society", and the offense is
connected to a victim, then Data Element # 25 (Type of Victim)
must be "S" = Society.
(Error Message 15065)
5) If the Offense is a "Crime Against Property", and the offense is
connected to a victim, then Data Element # 25 (Type of Victim)
cannot be "S" = Society. Type of Victim can be an “I”, “B”,
“F”, “G”, “R”, “O”, or “U”.
(Error Message 15067)
6) Crimes against society can only have one victim.
(Error Message 10080)
7) Victim type must be "L" = Law Enforcement Officer when
submitting LRS code 14:37.2.
(Error Message 22110)
DATA ELEMENT # 26
AGE of VICTIM
1) Must be present if Data Element # 25 (Type of Victim) is "I" =
Individual or "L" = Law Enforcement Officer.
(Error Message 15053)
2) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
DATA ELEMENT EDITS
61
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 15058)
3) If Data Element # 35 (Relationship of Victim to Offender)
contains a relationship of "SE" = Spouse, then the victim cannot
be less than 10 years old.
(Error Message 15050)
4) EXACT AGE:
A - Must be a valid code if alpha characters, i.e., NN, NB, or
BB.
(Error Message 15004)
B-
A single two-character age must be in first two positions
of the field. The third position must be blank.
(Error Message 15008)
5) ESTIMATED AGE:
A - Must be 2 numeric digits, and have a trailing "E".
(Error Message 15009)
B-
Age cannot be an estimate if Data Element # L26 (Date
of Birth of Victim) is entered, and Data Element # 3
(Incident Date/Hour) is an actual Incident date (i.e., not a
"R" Report date).
(Error Message 25010)
C-
The estimated age cannot be "00" = Unknown and have
a trailing "E".
(Error Message 15022)
6) Statutory Rape Victims age cannot be over 12.
(Error Message 15081)
DATA ELEMENT # L26
DATE of BIRTH of VICTIM
1) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). The
date cannot be greater than that entered within the "Month of
Tape" and "Year of Tape" field on the data record. For example,
if "Month of Tape and "Year of Tape are "06/1995," the date of
birth cannot contain any date 07/01/1995 or greater.
(Error Message 25030)
DATA ELEMENT EDITS
62
RELEASE 2.1
Print Date: March 7, 2016
2) Must be on or before Data Element # 3 (Incident Date/Hour).
(Error Message 25031)
3) If entered, and Data Element # 3 (Incident Date/Hour) contains
the actual incident date, then Data Element # 26 (Age of Victim-at the time of the incident) must be an exact age.
(Error Message 25010)
4) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
DATA ELEMENT # 27
SEX of VICTIM
1) Must be a valid code.
(Error Message 15004)
2) Must be present if Data Element # 25 (Type of Victim) is
Individual or "L" = Law Enforcement Officer.
(Error Message 15053)
"I" =
3) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
4) Data Element # 27 (Sex of Victim) must be "M" = Male or "F"
= Female to be connected to offense codes of "11A" =
Forcible Rape and "36B" = Statutory Rape.
(Error Message 15069)
DATA ELEMENT # 28
RACE of VICTIM
1) Must be a valid code.
(Error Message 15004)
2) Must be present if Data Element # 25 (Type of Victim) is
Individual or "L" = Law Enforcement Officer.
(Error Message 15053)
"I" =
3) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
DATA ELEMENT EDITS
63
RELEASE 2.1
Print Date: March 7, 2016
DATA ELEMENT # 29
ETHNICITY of VICTIM
1) Must be a valid code.
(Error Message 15004)
2) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
DATA ELEMENT # 30
RESIDENT STATUS of VICTIM
1) Must be a valid code.
(Error Message 15004)
2) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
DATA ELEMENT # 31
AGGRAVATED ASSAULT/HOMICIDE CIRCUMSTANCES and
LAW ENFORCEMENT OFFICERS KILLED/ASSAULTED (in the
line of duty) TYPE OF ASSIGNMENT
1) Must be a valid code.
(Error Message 15004)
2) If more than one code entered within Aggravated Assault/
Murder category, this cannot be a duplicate.
(Error Message 15006)
3) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on Master LIBRS/LRS Code Table of: 13A; 09A,
09B or 09C and Louisiana Revised Statute Number is one of the
following:
14:20
14:32
14:34.5
14:38.1
14:87.1
14:87.5/L
14:122/F
14:133.1/F
DATA ELEMENT EDITS
14:30
14:32.1/AA
14:37
14:39.1
14:87.2/F
14:93/F
14:129/A2F
14:404/Q
64
RELEASE 2.1
14:30.1
14:34
14:37.1
14:39.2
14:87.2/L
14:94/E
14:129.1/F
14:501
14:31
14:34.1
14:37.2
14:43.5
14:87.5/F
14:107.1/F
14:130.1/F
Print Date: March 7, 2016
Requirement 3
and Data Element # 24 (Offense Connected to Victim
Sequence Number) must relate to one of the above
offenses.
(Error Message 15019)
4) Value "10" = Unknown circumstances is mutually exclusive with
any other code -- no other code can be entered. Enter "10" only
if no other code applies.
(Error Message 15056)
5) No more than one circumstance category (i.e., Aggravated...,
Negligent..., Justifiable...) can be entered.
(Error Message 15056)
6) When Assault/Homicide Data Element # 31 is "08" = Other
Felony Involved, incident must have two (2) or more
offenses.
(Error Message 15080)
NOTE: This edit was formerly warning message #
13040.
7) Aggravated Assault cannot use "07" = Mercy Killing this
code does not relate to aggravated assault.
(Error Message 15062)
8) Enter up to two (2) codes for the Aggravated Assault, Murder
and Nonnegligent Manslaughter Circumstances if Data
Element # 6 has a NIBRS offense code as defined on Master
LIBRS/LRS Code Table of: 09A; or 13A and Louisiana Revised
Statute Number is one of the following:
14:30
14:30.1
14:31
14:32.1/AA
14:34
14:34.1
14:34.5
14:37
14:37.1
14:37.2
14:38.1
14:39.1
14:39.2
14:43.5
14:87.1
14:87.2/F
14:87.2/L
14:87.5/F
14:87.5/L
14:93/F
14:94/E
14:107.1/F
14:122/F
14:129/A2F
14:129.1/F
14:130.1/F
14:133.1/F
14:404/Q
Requirement 8
9) Enter only one (1) code for Negligent Manslaughter
Circumstances if Data Element # 6 has a NIBRS offense code
as defined on Master LIBRS/LRS Code Table of: 09B and
Louisiana Revised Statute Number is one of the following:
DATA ELEMENT EDITS
65
RELEASE 2.1
Print Date: March 7, 2016
14:32
14:501
Requirement 9
9a) If Data Element 31 is “40" = Child Abuse, then the victim
that is connected to this offense must have an age that
equals “NN,” “NB,” “BB,” “01-16,” or “01-16" with a
trailing E.
(Error Message 22120)
10) Enter only one (1) code for Justifiable Homicide
Circumstances if Data Element # 6 has a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of:
09Cand Louisiana Revised Statute Number is one of the
following:
14:20
Requirement 10
11) If "20" = Criminal Killed by Private Citizen or "21" = Criminal
Killed by Police Officer is entered, then Data Element 32
(Additional Justifiable Homicide Circumstances) and Law
Enforcement Officers Killed/Assaulted (in the line of duty)
Type of Activity must be entered.
(Error Message 15055)
12) When a Justifiable Homicide (09C) is reported, no other
offense may be reported in the Incident Report. These
would be submitted on other Incident Reports.
(Error Message 12066)
13) To enter code "02" = Assault on a Law Enforcement
Officer(s), Data Element # 25 must be "L" = Law
Enforcement Officer and Data Element # 6 must
be one of the following Louisiana Revised Statute
Numbers:
14:34
14:34.1
14:35
14:37
14:38
14:39.1
14:94/E
14:122/F
14:130.1/A
14:130.1/F
Requirement 13
DATA ELEMENT EDITS
66
RELEASE 2.1
14:34.2
14:37.1
14:39.2
14:129.1
14:133.1/F
14:34.5
14:37.2
14:43.5
14:129.1/F
Print Date: March 7, 2016
and Data Element # 24 (Offense Connected to Victim
Sequence Number) must relate to one of the above
offenses.
14) When LRS = 13A and Data Element # 25 (Type of Victim)
is "L" =Law Enforcement Officer must have two valid
codes, one of "02" = Assault on Law Enforcement Officer
and one code of "12-18" in Data Element # 31 and a valid
code of "K-U" in Data Element # 32.
(Error Message # 84302)
15) When LRS = 13B and Data Element # 25 (Type of Victim)
is "L" =Law Enforcement Officer must have two valid
codes, one of "02" = Assault on Law Enforcement Officer
and one code of "12-18" in Data Element # 31 and a valid
code of "K-U" in Data Element # 32.
(Error Message # 84502)
16) Must enter only one code "01" or "03-10" for Murder and
Manslaughter Circumstances for a Law Enforcement
Officer killed in the line of duty. Data Element # 25 must
be "L" = Law Enforcement Officer and Data Element # 6
must be one of the following Louisiana Revised Statute
Number:
14:30
14:30.1
14:87.1
14:87.2/L
Requirement 16
14:31
14:87.5/L
14:32.1/AA
17) When LRS = 09A and Data Element # 25 (Type of Victim)
is "L" = Law Enforcement Officer must have two valid
codes, one code "01" or "03-10" and one code of "12-18"
in Data Element # 31 and a valid code of "K-U" in Data
Element # 32.
(Error Message 84311)
18) Must enter code "30-34" for Negligent Manslaughter
Circumstances for a Law Enforcement Officer killed in the
line of duty. Data Element # 25 must be "L" = Law
Enforcement Officer and Data Element # 6 must be one of
the following Louisiana Revised Statute Numbers:
14:32
14:501
Requirement 18
DATA ELEMENT EDITS
67
RELEASE 2.1
Print Date: March 7, 2016
19) When LRS = 09B and Data Element # 25 (Type of Victim)
is "L" = Law Enforcement Officer must have two valid
codes, one code "30-34" and one code of "12-18" in Data
Element # 31 and a valid code of "K-U" in Data Element #
32.
(Error Message 84411)
20) Enter only one (1) code if a Law Enforcement Officer was
Killed or Assaulted in the line of duty. Louisiana Revised
Statute Numbers must be in Requirement 13, 16, and 18.
DATA ELEMENT # 32
ADDITIONAL JUSTIFIABLE HOMICIDE CIRCUMSTANCES and
LAW ENFORCEMENT OFFICERS KILLED/ASSAULTED (in the
line of duty) TYPE OF ASSIGNMENT
1) Must be a valid code.
(Error Message 15004)
2) If Data Element # 32 is entered, Data Element # 31 (Aggravated
Assault/Homicide Circumstances/Law Enforcement Officer
Killed/Assaulted (in the line of duty) Type of Assignment
Circumstances) must show a Justifiable Homicide (09C)
circumstance, i.e., code "20" or "21", if Type of Victim not
equal to “L” = Law Enforcement Officer.
(Error Message 15057)
3) When LRS = 13A and Data Element # 25 (Type of Victim) is
"L" =Law Enforcement Officer must have two valid codes,
one of "02" = Assault on Law Enforcement Officer and one
code of "12-18" in Data Element # 31 and a valid code of "KU" in Data Element # 32.
(Error Message # 84302)
4) When LRS = 13B and Data Element # 25 (Type of Victim) is
"L" =Law Enforcement Officer must have two valid codes,
one of "02" = Assault on Law Enforcement Officer and one
code of "12-18" in Data Element # 31 and a valid code of "KU" in Data Element # 32.
(Error Message # 84502)
5) When LRS = 09A and Data Element # 25 (Type of Victim) is
"L" = Law Enforcement Officer must have two valid codes,
one code "01" or "03-10" and one code of "12-18" in Data
Element # 31 and a valid code of "K-U" in Data Element # 32.
DATA ELEMENT EDITS
68
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 84311)
6) When LRS = 09B and Data Element # 25 (Type of Victim) is
"L" = Law Enforcement Officer must have two valid codes,
one code "30-34" and one code of "12-18" in Data Element #
31 and a valid code of "K-U" in Data Element # 32.
(Error Message 84411)
DATA ELEMENT # 33
TYPE of INJURY
1) Must be a valid code.
(Error Message 15004)
2) If more than one code entered, cannot be a duplicate.
(Error Message 15006)
3) Value "N" = None is mutually exclusive with any other value
entered, i.e., "N" is to be used only if no other code applies.
(Error Message 15007)
4) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on Master LIBRS/LRS Code Table of: 100; 11A,
11B, 11C, or 11D; 120; 13A or 13B; 210; or 90Z "Crimes
Against Person" and the Louisiana Revised Statute Number is
one of the following:
14:28.1
14:34.2
14:35
14:37.2
14:39
14:42/V
14:43/V
14:43.2/P
14:44
14:44.1/O
14:45.1
14:50.1
14:64.2
14:79
14:87.5/F
14:93.3
14:107.1/F
14:129.1/F
DATA ELEMENT EDITS
14:32.12
14:34.3
14:35.1
14:38
14:39.1
14:42.1/A
14:43.1/N
14:43.3
14:44.1
14:44.1/P
14:46
14:60
14:65
14:81
14:89.1
14:93.5
14:122/F
14:130.1/A
69
RELEASE 2.1
14:34
14:34.4
14:37
14:38.1
14:39.2
14:42.1/V
14:43.1/P
14:43.4
14:44.1/A
14:44.1/V
14:46.1
14:64
14:65.1/F
14:81.2
14:92.1
14:94/E
14:129/A2F
14:130.1/F
14:34.1
14:34.5
14:37.1
14:38.2
14:42/A
14:43/A
14:43.2/N
14:43.5
14:44.1/N
14:45
14:47
14:64.1
14:66
14:87.2/F
14:93/F
14:103/A1
14:129.1
14:133.1/F
Print Date: March 7, 2016
14:135
14:404/Q
14:136
14:511
14:286
14:512
14:404/J
Requirement 4
and Data Element # 24 (Offense Connected to Victim
Sequence Number) must relate to one of the above
offenses.
(Error Message 15019)
5) When Data Element # 24 (Offense Connected to Victim
Sequence Number) relates to the offense of "13B" = Simple
Assault, there cannot be "major" injury codes which would
indicate an aggravated assault. The permissible codes are
"M" = Apparent Minor Injury and "N" = None.
(Error Message 15079)
DATA ELEMENT # 34
OFFENDER NUMBER to be RELATED
1) Must be entered if Data Element # 6 has a NIBRS offense code
as defined on Master LIBRS/LRS Code Table of: 09A, 09B,
09C; 100; 11A, 11B, 11C, 11D; 120; 13A, 13B, 13C; 36A, 36B;
90Z "Crime Against Person" and Louisiana Revised Statute
Number is one of the following:
14:20
14:31
14:34
14:34.4
14:37
14:38.1
14:39.2
14:42/A
14:43/A
14:43.2/N
14:43.5
14:44.1/N
14:45
14:47
14:64.1
14:78
14:81
14:87.2/L
14:92.1
14:93.5
DATA ELEMENT EDITS
14:28.1
14:32
14:34.1
14:34.5
14:37.1
14:38.2
14:40
14:42/V
14:43/V
14:43.2/P
14:44
14:44.1/O
14:45.1
14:50.1
14:64.2
14:78.1
14:81.2
14:87.5/F
14:92.3
14:94/E
70
RELEASE 2.1
14:30
14:32.1/AA
14:34.2
14:35
14:37.2
14:39
14:40.1
14:42.1/A
14:43.1/N
14:43.3
14:44.1
14:44.1/P
14:46
14:60
14:65
14:79
14:87.1
14:87.5/L
14:93/F
14:103/A1
14:30.1
14:32.12
14:34.3
14:35.1
14:38
14:39.1
14:40.2
14:42.1/V
14:43.1/P
14:43.4
14:44.1/A
14:44.1/V
14:46.1
14:64
14:65.1/F
14:80
14:87.2/F
14:89.1
14:93.3
14:107.1/F
Print Date: March 7, 2016
14:122/F
14:122/T
14:122.1
14:129/A1
14:129/A2F
14:129/A2T
14:129.1/F
14:129.1/T
14:130.1/A
14:130.1/F
14:133.1/F
14:133.1/T
14:286 14:404/J
14:404/Q
14:501
Requirement 1
14:122.2
14:129.1
14:130.1/T
14:285
and Data Element # 24 (Offense Connected to Victim
Sequence Number) must relate to one of the above
offenses.
(Error Message 15059)
2) Must be numeric entry with zero left-fill if entered.
(Error Message 15002)
3) Data Element # 25 (Type of Victim) must be "I" = Individual or
"L" = Law Enforcement Officer for data to be entered.
(Error Message 15058)
4) If more than one number entered, this cannot be a duplicate.
(Error Message 15006)
5) "000" may only be entered if there is only one Offender Segment
submitted where nothing was known about identity and number
of offender(s).
(Error Message 15068)
6) The corresponding Offender Segment must be present.
(Error Message 10070)
7) When a victim is connected to a "Crime Against Person" or
Robbery Offense, all Offender Sequence Numbers, Data
Element # 36, must also be entered in Data Element # 34
(Offender Numbers to be Related). If the victim is related to
the offender in more than one way, use the closest
relationship.
(Error Message 10085)
DATA ELEMENT # 35
RELATIONSHIP of VICTIM to OFFENDER
1) Every offender indicated in Data Element # 34 (Offender Number
to be Related) requires an entry here except when the number is
"000" = Unknown. This field must be blank in instances when
"000" is entered.
DATA ELEMENT EDITS
71
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 15060)
2) Must be a valid code.
(Error Message 15004)
3) Husbands and wives (i.e., spouses) must be at least 10 year of
age.
(Error Message 15050, 14050)
4) The sex of the victim and/or offender must reflect the implied
relationship. The following relationships must reflect a specific
sex for the victim, offender, or both depending upon the
relationship:
Relationship
Sex Code
XS - Victim was Ex-Spouse
Different
SE - Victim was Spouse
Different
CS - Victim was Common-Law Spouse
Different
ES - Victim was Estranged Spouse
Different
HR - Homosexual
Same
VO - Victim was Offender
Same
BG - Victim was Boyfriend/Girlfriend
Different
XB - Victim was Ex-Boyfriend/Girlfriend Different
NM - Non-Married Live-In
Different
(Error Message 14053)
5) The age of the victim and/or the offender must reflect the implied
relationship.
Relationship
Victim Must be
CH - Victim was Child
Younger
PA - Victim was Parent
Older
GP - Victim was Grandparent Older
GC - Victim was Grandchild
Younger
VO - Victim was Offender
Same Age
BE - Victim was Babysitee (the baby)
Younger
SE - Victim was Spouse
at least 10 yrs.
ES - Victim was Estranged Spouse
at least 10 yrs.
CS - Victim was Common-Law Spouse
at least 10 yrs.
XS - Victim was Ex-Spouse
at least 10 yrs.
NM - Victim was Non-Married Live-In
at least 10 yrs.
(Error Message 14054)
6) Relationship cannot be entered when Data Element # 34
(Offender Number to be Related) is "000" = Unknown.
(Error Message 15068)
DATA ELEMENT EDITS
72
RELEASE 2.1
Print Date: March 7, 2016
7) When "VO" = Victim was Offender is entered, a minimum of two
(2) Victims and two (2) Offender Segments must be submitted.
"VO" indicates situations such as brawls and domestic disputes
where all of the participants in the incident were victims and
offenders of the same offense (i.e., assaults or double
murders where two people kill each other). In most cases,
each victim is also the offender; therefore, every victim record
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) are not also the offender(s) (i.e., a
victim who is not an offender would be an innocent
bystander in a barroom brawl or a child who is victimized as
a result of the parents domestic dispute).
(Error Message 15070)
8) When entered, "VO" = Victim was Offender can only be entered
once in a victim record and can refer to an offender only once.
Since "VO" points to himself/herself, a victim cannot be two
offenders.
(Error Message 15071, 15074)
9) When the related offender has "unknown" values entered for
age, sex and race, the relationship must be "RU" = Relationship
Unknown. This edit ensures a logical relationship., e.g., if
brother was entered, age, sex and race would not be unknown
values.
(Error Message 15072)
10) In a multiple offender incident, a victim cannot have a
relationship of "SE" = Spouse to more than one offender.
(Error Message 15075)
11) In a multiple victim incident, two or more victims cannot
have a victim relationship of "SE" = Spouse to the same
offender.
(Error Message 15076)
12) Must be entered if Data Element # 6 has a NIBRS offense
code as defined on Master LIBRS/LRS Code Table of:
09A, 09B, 09C; 100; 11A, 11B, 11C, 11D; 120; 13A, 13B,
13C; 36A, 36B; 90Z "Crime Against Person" and Louisiana
Revised Statute Number is one of the following:
14:20
14:31
DATA ELEMENT EDITS
14:28.1
14:32
73
RELEASE 2.1
14:30
14:32.1/AA
14:30.1
14:32.12
Print Date: March 7, 2016
14:34
14:34.1
14:34.4
14:34.5
14:37
14:37.1
14:38.1
14:38.2
14:39.2
14:40
14:42/A
14:42/V
14:43/A
14:43/V
14:43.2/N
14:43.2/P
14:43.5
14:44
14:44.1/N
14:44.1/O
14:45
14:45.1
14:47
14:50.1
14:64.1
14:64.2
14:78
14:78.1
14:81
14:81.2
14:87.2/L
14:87.5/F
14:92.1
14:92.3
14:93.5
14:94/E
14:122/F
14:122/T
14:129/A1
14:129/A2F
14:129.1/F
14:129.1/T
14:130.1/F
14:133.1/F
14:286
14:404/J
Requirement 12
14:34.2
14:35
14:37.2
14:39
14:40.1
14:42.1/A
14:43.1/N
14:43.3
14:44.1
14:44.1/P
14:46
14:60
14:65
14:79
14:87.1
14:87.5/L
14:93/F
14:103/A1
14:122.1
14:129/A2T
14:130.1/A
14:133.1/T
14:404/Q
14:34.3
14:35.1
14:38
14:39.1
14:40.2
14:42.1/V
14:43.1/P
14:43.4
14:44.1/A
14:44.1/V
14:46.1
14:64
14:65.1/F
14:80
14:87.2/F
14:89.1
14:93.3
14:107.1/F
14:122.2
14:129.1
14:130.1/T
14:285
14:501
This data element must be blank when "000" is entered
into Data Element # 34.
(Error Message 15059)
DATA ELEMENT EDITS
74
RELEASE 2.1
Print Date: March 7, 2016
OFFENDER SEGMENT EDITS
DATA ELEMENT # 36
OFFENDER SEQUENCE NUMBER
1) Must be present -- cannot be blank.
(Error Message 14001)
2) Must be numeric entry with zero left-fill. The purpose of the field
is to distinguish one offender from another and to identify the
situation where nothing was known about the number of
offenders or who they were. For example, a corpse was found in
a ditch and there were no eyewitnesses or other information that
would provide data about possible offenders. In that case, "000"
= Unknown would be entered. However, if five offenders were
seen running from the scene, then five offender records would
be submitted.
(Error Message 14002)
3) If the incident is exceptionally cleared, then "000" cannot be
entered. "000" indicates that nothing was known about the
offender(s) regarding number and any identifying information.
One of the criteria for exceptionally clearing an incident is that at
least one of the offenders be known.
(Error Message 14057)
4) For a Justifiable Homicide (09C) at least one of the offenders
must have "known" information for age, sex, and race.
Consequently, "000" is not valid as an offender sequence
number.
(Error Message 14059)
5) If the number is "000" = Unknown, no other Offender Segments
can be submitted.
(Error Message 14055)
6) Must be unique - cannot be duplicated.
(Error Message 14051)
7) When Data Element # 36 = "000", then Data Element # 8
must be "N" = Not Applicable and Data Element # 8A must
be "88" = None.
(Error Message 81400)
DATA ELEMENT # 37
DATA ELEMENT EDITS
AGE of OFFENDER (at the time the incident occurred)
75
RELEASE 2.1
Print Date: March 7, 2016
1) Must be present when Data Element # 36 (Offender Sequence
Number) is other than "000" = Unknown.
(Error Message 14001)
2) Cannot be entered when Data Element # 36 (Offender Sequence
Number) is "000" = Unknown.
(Error Message 14052)
3) When an incident is cleared exceptionally, at least one of the
offenders must have "known" values in age, sex, and race.
(Error Message 14058)
4) For a Justifiable Homicide (09C) at least one of the offenders
must have "known" information for age, sex, and race.
(Error Message 14059)
5) If Data Element # 35 (Relationship of Victim to Offender)
contains a relationship of "SE" = Spouse, then the offender
cannot be less than 10 years old.
(Error Message 14050)
6) EXACT AGE:
A - Must contain numeric entry of 00 -99
(Error Message 14056)
B-
A single two-character age must be in first two positions
of the field. The third position must be blank.
(Error Message 14008)
7) ESTIMATED AGE:
A - Must be 2 numeric digits, and have a trailing "E".
(Error Message 14009)
DATA ELEMENT # L37
DATA ELEMENT EDITS
B-
Age cannot be an estimate if Data Element # L37 (Date
of Birth of Offender) is entered, and Data Element # 3
(Incident Date/Hour) is an actual Incident date (i.e., not a
"R" Report date).
(Error Message 24010)
C-
The estimated age cannot be "00" = Unknown and have
a trailing "E".
(Error Message 14022)
DATE of BIRTH of OFFENDER
76
RELEASE 2.1
Print Date: March 7, 2016
1) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). The
data cannot be greater than that entered within the "Month of
Tape" and "Year of Tape" fields on the data record. For
example, if "Month of Tape" and "Year of Tape" are "06/1995,"
the date of birth cannot contain any date 07/01/1995 or greater.
(Error Message 24030)
2) Must be before Data Element # 3 (Incident Date/Hour).
(Error Message 24031)
3) If entered, and Data Element # 3 (Incident Date/Hour) contains
the actual incident date, then Data Element # 37 (Age of
Offender (at time of incident)) must be an exact age.
(Error Message 24010)
DATA ELEMENT # 38
SEX of OFFENDER
1) Must be present when Data Element # 36 (Offender Sequence
Number) is other than "000" = Unknown.
(Error Message 14001)
2) Must be a valid code.
(Error Message 14004)
3) Cannot be entered when Data Element # 36 (Offender Sequence
Number) is "000" = Unknown.
(Error Message 14052)
4) When an incident is cleared exceptionally, at least one of the
offenders must have "known" values in age, sex and race.
(Error Message 14058)
5) For a Justifiable Homicide (09C) at least one of the offenders
must have "known" information for age, sex and race.
(Error Message 14059)
6) For forcible rape (11A) or statutory rape (36B), one or more
of the offenders must have a different sex than the rape
victim.
(Error Message 14060)
DATA ELEMENT EDITS
77
RELEASE 2.1
Print Date: March 7, 2016
DATA ELEMENT # 39
RACE of OFFENDER
1) Must be present when Data Element # 36 (Offender Sequence
Number) is other than "000" = Unknown.
(Error Message 14001)
2) Must be a valid code.
(Error Message 14004)
3) Cannot be entered when Data Element # 36 (Offender Sequence
Number) is "000" = Unknown.
(Error Message 14052)
4) When an incident is cleared exceptionally, at least one of the
offenders must have "known" values in age, sex and race.
(Error Message 14058)
5) For a Justifiable Homicide (09C) at least one of the offenders
must have "known" information for age, sex and race.
(Error Message 14059)
DATA ELEMENT EDITS
78
RELEASE 2.1
Print Date: March 7, 2016
ARRESTEE SEGMENT EDITS
DATA ELEMENT # 40
ARRESTEE SEQUENCE NUMBER
1) Must be present--cannot be blank.
(Error Message 16001)
2) Must be numeric entry of 001 to 999 with zero left-fill.
(Error Message 16002)
3) Must be unique--cannot be duplicated.
(Error Message 26001)
4) Number of arrestees cannot be greater than number of
offenders.
(Error Message 16056)
DATA ELEMENT # L40
ARRESTEE NAME
None
DATA ELEMENT # 41
ARREST NUMBER / LOCAL BOOKING NUMBER for ARREST
1) Must be present--cannot be blank.
(Error Message 16001)
2) Must be left-justified with blank right-fill if under 12 characters in
length.
(Error Message 16016)
3) Valid character combinations can include A-Z, 0-9, and hyphens.
For example, 89-123-SC is valid, but 89+123*SC or 89-123 SC
is invalid.
(Error Message 16017)
4) Must be blank right-fill if under 12 characters in length. Cannot
have embedded "blanks" between the first and last character
entered.
(Error Message 16015)
DATA ELEMENT # 42
DATA ELEMENT EDITS
ARREST DATE
79
RELEASE 2.1
Print Date: March 7, 2016
1) Must be present--cannot be blank.
(Error Message 16001)
2) Each component of the date must be valid; that is, months must
be 01-12, days must be 01-31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). The
date cannot exceed the current date. The date cannot be
greater than that entered with the "Month of Tape" and "Year of
Tape" fields on the data record. For example, if "Month of Tape"
and "Year of Tape" are "06/1995", the arrest date cannot contain
any date 07/01/1995 or greater.
(Error Message 16005)
3) Cannot be earlier than Data Element # 3 (Incident Date/Hour).
(Error Message 16065)
4) Arrestee Segments (Segment 60) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot have
Data Element # 42 (Arrest Date) earlier than the Base Date.
This also applies to any subsequent "M" = Modify Submission of
a previously submitted "W" = Time-Window Submission.
(Error Message 16020)
DATA ELEMENT # 43
TYPE of ARREST
1) Must be present--cannot be blank.
(Error Message 16001)
2) Must be a valid code.
(Error Message 16004)
DATA ELEMENT # 44
MULTIPLE ARRESTEE SEGMENT INDICATOR
1) Must be present--cannot be blank.
(Error Message 16001)
DATA ELEMENT # 45
2) Must be a valid code.
(Error Message 16004)
LOUISIANA REVISED STATUTE NUMBER of ARREST
1) Must be present--cannot be blank
(Error Message 16001)
DATA ELEMENT EDITS
80
RELEASE 2.1
Print Date: March 7, 2016
2) Must be a valid code on Master LIBRS/LRS Code Table. This
code does not have to match one of the code(s) entered for Data
Element # 6 (Louisiana Revised Statute Number) within Offense
Segment(s) submitted in a Incident Report.
(Error Message 16004)
3) The Louisiana Revised Statute cannot be (14:20)--Justifiable
Homicide, because this offense does not result in a subsequent
arrest of the offender.
(Error Message 16070)
4) An incident cannot have arrests when Data Element # 6
(Louisiana Revised Statute Number) is 14:20 ("09C") =
Justifiable Homicide. A Justifiable Homicide never involves
an arrest of the offender (the person who committed the
justifiable homicide).
(Error Message 16069)
DATA ELEMENT # L45
ARREST CONNECTION to OFFENSE
1) Must be a valid offense sequence number. The offense segment
referred to in this data element must exist.
DATA ELEMENT # 46
ARRESTEE WAS ARMED WITH(at the time of arrest)
1) Must be present--cannot be blank.
(Error Message 16001)
2) Must be a valid code.
(Error Message 16004)
3) If more than one code entered, cannot be a duplicate.
(Error Message 16006)
4) Value "01" = Unarmed is mutually exclusive with any other value,
i.e., it is to be used only if no other code applies. Note: If the
arrestee was in possession of a toy or play weapon this
would be reported as being "01" = Unarmed.
(Error Message 16007)
5) The third character must be "A" = Automatic or blank.
(Error Message 16054)
DATA ELEMENT EDITS
81
RELEASE 2.1
Print Date: March 7, 2016
6) If the firearm is Automatic, add "A" = Automatic as the third
character of code; valid only with the following codes:
11 - Firearm (Type Not Stated)
12 - Handgun
13 - Rifle
14 - Shotgun
15 - Other Firearm
(Error Message 16055)
DATA ELEMENT # 47
AGE of ARRESTEE (at the time of the arrest)
1) Must be present--cannot be blank.
(Error Message 16001)
2) If age is under 17, then Data Element # 52 (disposition of
Arrestee Under 17) must be entered.
(Error Message 16052)
3) EXACT AGE:
A - Must contain numeric entry of 00-99.
(Error Message 16064)
B-
A single two-character age must be in first two positions
of the field. The third position must be blank.
(Error Message 16008)
C-
When the age is unknown, don't confuse "99" = Over 98
Years Old with "00" = Unknown. Whenever "99" is
entered, a warning message is produced.
(Warning Message 16041)
4) ESTIMATED AGE:
A - Must be two (2) numeric digits, and have a trailing "E" =
Estimated.
(Error Message 16009)
DATA ELEMENT EDITS
B-
Age cannot be an estimate if Data Element # L47
(Date of Birth of Arrestee) is entered, and Data
Element # 3 (Incident Date/Hour) is an actual
incident date (i.e., not a "R" = Report Date).
(Error Message 26010)
C-
The estimated age cannot be "00" = Unknown and have
a trailing "E".
82
RELEASE 2.1
Print Date: March 7, 2016
(Error Message 16022)
5) When Juvenile Qualifiers are used the age must be “01" “16" for a JU:RUN - Runaway Offense (90I), JU:UNG Ungovernable (90C), JU:CUR - Curfew (90B), or JU:TRU Truancy (90Z).
(Error Message 22100)
DATA ELEMENT # L47
DATE of BIRTH of ARRESTEE
1) AGE CANNOT BE ESTIMATED IF DATE OF BIRTH IS
KNOWN.
If the age is reported with trailing "E" = Estimated age in
Data Element # 47 (Age of Arrestee at the Time of Arrest)
and the agency also reports date of birth of arrestee (DE #
47) this incident would be rejected. If date of birth is
known, age cannot be estimated.
(Error Message 26010)
2) AGE CANNOT BE UNKNOWN IF DATE OF BIRTH IS
KNOWN.
If the age of an arrestee (at the Time of Arrest) is reported
as "00" = Unknown and Data Element # L47 (Date of Birth
of Arrestee) is also reported, this incident would be
rejected. If date of birth is known, age cannot be
unknown.
(Error Message 22105)
DATA ELEMENT EDITS
83
RELEASE 2.1
Print Date: March 7, 2016
DATA ELEMENT # 48
SEX of ARRESTEE
1) Must be present -- cannot be blank.
(Error Messages 16001)
2) Must be a valid code. Although "U" = Unknown is a valid code
for victim and offender sex, it is not valid for arrestees.
(Error Messages 16067)
DATA ELEMENT # 49
RACE of ARRESTEE
1) Must be present -- cannot be blank.
(Error Messages 16001)
2) Must be a valid code.
(Error Messages 16004)
DATA ELEMENT # 50
ETHNICITY of ARRESTEE
1) If entered, must be a valid code.
(Error Messages 16004)
DATA ELEMENT # 51
RESIDENT STATUS of ARRESTEE
1) If entered, must be a valid code.
(Error Messages 16004)
DATA ELEMENT # 52
DISPOSITION of ARRESTEE UNDER 17
1) Must be a valid code.
(Error Messages 16004)
2) Must be entered if arrestee age is under 17.
(Error Messages 16052)
3) Cannot be entered if arrestee age is 17 or over.
(Error Messages 16053)
4) Data Element # 52 was not entered, but Data Element #47
(Age of Arrestee) indicated an age for a juvenile. Note that
DATA ELEMENT EDITS
84
RELEASE 2.1
Print Date: March 7, 2016
when the age is for a juvenile, the disposition must be
entered.
(Error Message 16040)
DATA ELEMENT # L53
LOCATION of INCIDENT (Geographical Coordinates)
1) If entered, the field must contain 12 numeric places. No spaces
allowed.
(Error Message 20200)
DATA ELEMENT # L54
STATION/DIVISION/PRECINCT IDENTIFIER
None
DATA ELEMENT # L55
ARREST TRANSACTION NUMBER (ATN) for LOUISIANA
1) Must be present if fingerprints are submitted into the
Bureau of Identification of the Louisiana State Police.
DATA ELEMENT EDITS
85
RELEASE 2.1
Print Date: March 7, 2016
III. ERROR NUMBERS AND MESSAGES
ERROR NUMBERS AND MESSAGES
86
Print Date: March 7, 2016
RELEASE 2.1
ERROR NUMBERS AND MESSAGES
STRUCTURE CHECK ERRORS
ERROR
NUMBER
MESSAGE
10001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required on the Zero Reporting
Segment (Segment 01).
10003
MULTIPLE 00 SEGMENTS ENCOUNTERED. ONLY ONE PER
SUBMISSION ALLOWED. (LIBRS ONLY)
10015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS.
Zero Reporting Segment (Segment 01). Although Data Element 2
(Incident Number) should be entered with 12 zeroes, a pre-edit
found embedded blanks between the first and last significant
characters.
10016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Zero Reporting Segment (Segment 01). Although Data Element 2
(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.
10017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN,
AND/OR BLANKS
Zero Reporting Segment (Segment 01). Although Data Element 2
(Incident Number) should be entered with 12 zeroes, a pre-edit
discovered characters other than A-Z, 0-9, Hyphen, and/or Blanks
had been entered.
10050
SEGMENTS ARE OUT OF NUMERIC ORDER FOR THIS INCIDENT
ERROR NUMBERS AND MESSAGES
87
Print Date: March 7, 2016
RELEASE 2.1
All segments for an Incident Report must be in numeric order. In
this case, one was not. For example, an incident having segments
10, 20, 20, 30, 40, 40, 40, 50 must be written in that order, not as
10, 20, 20, 50, 30, 40, 40, 40.
10051
INVALID RECORD SEGMENT ON TAPE
Any record segment on the tape that is other than "00" through
"99" will generate an error.
10052
NOT A VALID ORI -- NOT ON ORI FILE
Data Element 1 (ORI Number) must be a valid 9-character NCIC
number.
10053
RECORD NOT ON FILE
A transaction was submitted to "M" = Modify an existing segment
on the State System data base. However, the record to be
modified was not on file.
The "modify" transaction implies that Exceptional Clearance,
Recovered Property, and/or Arrestee Segments were on file as
"window" records, not complete Incident Reports. Regardless, the
data segment to be modified was not in the State's file.
10055
CANNOT HAVE AN INITIAL INCIDENT RECORD WITHOUT STARTING
WITH RECORD SEGMENT 10
When an "I" = Incident Report is submitted, the first segment must
be the Administrative Segment (Segment 10). In this case, the first
record received for the incident was not the Administrative
Segment.
10056
INCIDENT ALREADY ON FILE -- PREVIOUSLY ADDED TO FILE ON
[mm/dd/yyyy]
ERROR NUMBERS AND MESSAGES
88
Print Date: March 7, 2016
RELEASE 2.1
An Incident Report was previously added to the State System data
base on the date shown within the error message, and is presently
on file. Another report was processed with the same ORI and
Incident Number, which resulted in this error.
10057
ACTION TYPE IS NOT VALID FOR THIS RECORD SEGMENT
The value of "I" = Incident Report, "A" = Add, "M" = Modify,
"W" = Time-Window Submission, and "D" = Delete must be
applicable to appropriate Segments (01 through 63) as shown
below:
ACTION VALID ONLY WITH THESE LEVELS
I
Segments 10, 20, 30, 31, 40, 41, 50, 51, 52, 60, 61, 62
A
01 = Zero Reporting Segment
60 = Arrestee Segment
61 = Arrestee Armed Segment
62 = Arrestee Statute Segment
M
10 = Administrative Segment
11 = Administrative Modification Segment
30 = Property Segment
31 = Property Description Segment
32 = Property Modification Segment*
60 = Arrestee Segment
61 = Arrestee Armed Segment
62 = Arrestee Statute Segment
63 = Arrestee Modification Segment*
W
10 = Administrative Segment
11 = Administrative Modification Segment
30 = Property Segment
31 = Property Description Segment
32 = Property Modification Segment*
60 = Arrestee Segment
61 = Arrestee Armed Segment
62 = Arrestee Statute Segment
63 = Arrestee Modification Segment*
D
01 = Zero Reporting Segment
10 = Administrative Segment
ERROR NUMBERS AND MESSAGES
89
Print Date: March 7, 2016
RELEASE 2.1
11 = Administrative Modification Segment
32 = Property Modification Segment
63 = Arrestee Modification Segment
*-Valid only when previously submitted as "W."
10059
ALL SEGMENTS ON MAGNETIC MEDIA MUST BE FROM SAME
STATE - STATE=[state]
All segments on the submitted magnetic media must be from the
same state for non-federal participants. This will be checked by
comparing the 2-character state abbreviation in Data Element 1
(ORI Number); all must have the same value.
10060
SUBMISSION DATE (C3) [MMDDYYYY] PRECEDES REPORTING
PERIOD (C4) IN POSITIONS 31-36 CONTAINING [MMYYYY]
10065
EACH SEGMENT 20 MUST HAVE A CORRESPONDING VICTIM
SEGMENT
Each Offense Segment submitted must have a Victim Segment(s)
pointing to it via Data Element 24 (Offense Connected to Victim
Sequence Number). In this case, no Offense Segment pointed to
the referenced Victim Segment. A Victim Segment cannot stand
alone; it must have an Offense Segment linked to it.
10070
THE CORRESPONDING OFFENDER RECORD MUST BE PRESENT
Data Element 34 (Offender Numbers To Be Related) had a value
that did not have a corresponding Offender Segment. For example,
if the field value shown in Data Element 34 was "015," an Offender
Segment did not exist with a value of "015" in Data Element 36
(Offender Sequence Number).
10071
CANNOT HAVE ARRESTS IF CLEARED EXCEPTIONALLY
Whenever an Exceptional Clearance is submitted in the
Administrative Segment (Segment 10), there can be no Arrestee
Segments (Segment 60) associated with the Incident Report. In
ERROR NUMBERS AND MESSAGES
90
Print Date: March 7, 2016
RELEASE 2.1
this instance, the incident had been exceptionally cleared, but there
were Arrestee Segments also submitted.
10072
RECOVERED PROPERTY MUST ALSO BE SUBMITTED AS STOLEN
Data Element 15 (Property Description) contains property that
was reported as recovered without also being reported as
stolen. Any property being reported as recovered must first
be reported as stolen. This edit does not apply for offenses
that allow “Recovered” property without first being “Stolen”
(does not apply to NIBRS offenses codes of 280 and 250). Nor
does it apply when property description “38" = Vehicle
Parts/Accessories is subsequently reported as “Recovered”
when a vehicle was stolen.
Ensure that the property description code was entered correctly.
Perhaps the stolen or recovered property "codes" were entered
incorrectly, or the recovered property had not originally been
reported as stolen.
10073
NUMBER OF RECOVERED VEHICLES CANNOT BE GREATER THAN
THE NUMBER STOLEN
When Data Element 18 (Number of Stolen Motor Vehicles) is 01 to
99, the number must be equal to or greater than the number
entered in Data Element 19 (Number of Recovered Motor
Vehicles).
10074
10075
PROPERTY SEGMENT (SEGMENT 30 & 31) 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, Property Segment(s) must also be submitted. In this
case, no Property Segments were submitted.
MISSING A MANDATORY RECORD SEGMENT FOR A COMPLETE
INCIDENT
When an "I" = Incident Report is submitted, the following segments
must be included: Administrative Segment, Offense Segment,
Victim Segment, Offender Segment and Offender Using
ERROR NUMBERS AND MESSAGES
91
Print Date: March 7, 2016
RELEASE 2.1
Segment/Gaming Motivation. One or more of these segments
was missing.
10076
PROPERTY SEGMENT (SEGMENTS 30 & 31) CANNOT EXIST WITH
OFFENSES SUBMITTED
A Property Segment (Segments 30 & 31) was submitted for an
Incident Report without an applicable "property" offense code.
Property Segments can only be submitted with offenses relating to
"Crimes Against Property," Kidnapping, Gambling, or Drug/Narcotic
offenses.
10077
NEED A PROPERTY LOSS CODE OF "1" OR "8" WHEN THIS
OFFENSE IS ATTEMPTED
If Data Element 7 (Offense Attempted/Completed) is "A" =
Attempted and Data Element 6 (Louisiana Revised Statute
Number) is a "Crime Against Property," Gambling, Kidnapping, or
Drug/Narcotic Offense. However, there is no Data Element 14
(Type Property Loss/Etc.) of "1" = None or "8" = Unknown.
10078
A VALID PROPERTY LOSS CODE DOES NOT EXIST FOR THIS
COMPLETE OFFENSE
If Data Element 6 (Louisiana Revised Statute Number) was a Crime
Against Property, Kidnapping, Gambling, or Drug/Narcotic Offense,
and Data Element 7 (Offense Attempted/Completed) was "C" =
Completed, a Property Segment (Segment 30 & 31) must be sent
with a valid code in Data Element 14 (Type Property Loss/Etc.).
10080
CRIMES AGAINST SOCIETY CAN ONLY HAVE ONE VICTIM
The Incident Report submission only contained offense(s) that were
"Crimes Against Society." When this is so, Data Element 25 (Type
of Victim) must be "S" = Society/Public, and only 1 victim can be
submitted. In this instance, more than 1 Victim Segment was
submitted.
ERROR NUMBERS AND MESSAGES
92
Print Date: March 7, 2016
RELEASE 2.1
10081
THIS PROPERTY LOSS CODE CANNOT EXIST WITH THE OFFENSES
SUBMITTED
Data Element 14 (Type Property Loss/Etc.) had a loss code that
was not applicable to any of the offenses submitted. Refer to
(Mandatories) for the correct values to use for each of the offenses.
10084
RECOVERED PROPERTY VALUE CANNOT BE GREATER THAN THE
VALUE WHEN STOLEN.
When Data Element 14 (Type Property Loss/Etc.) contains
Property Segments for both "7" = Stolen/Etc. and "5" = Recovered,
the recovered "property" cannot have value(s) greater than
corresponding value(s) reported stolen.
If this error appears for Property Description Vehicle
Parts/Accessories, the value exceeded the value of the stolen
vehicles.
10085
WHEN CONNECTED, EACH VICTIM MUST BE CONNECTED TO ALL
OFFENDERS
When a victim is connected to a "Crime Against Person" or
Robbery LRS Offense Code, all Offender Sequence Numbers
(Data Element 36) must be entered in Data Element 34
(Offender Numbers to be Related). If the victim is related to
the offender in more than one way, use the closest
relationship. In this case, the Victim Segment did not point to
all of the offenders.
10086
THE LAST 2 POSITIONS OF THE PARTICIPANT'S ORI ARE INVALID
A non-Federal participant must have "00" in positions 8 and 9 of
Data Element 1 (ORI Number). A Federal participant must use its
2-character code assigned by the UCR; no other participant's code
can be used. In this submittal, the last 2 positions were entered
incorrectly.
ERROR NUMBERS AND MESSAGES
93
Print Date: March 7, 2016
RELEASE 2.1
10087
"WINDOW" SEGMENTS ALREADY ON FILE WITH THIS INCIDENT
NUMBER
An Incident Report was submitted but was not added to the State
System data base. Already on file was either (1) a "Recovered"
Property Segment or (2) an Arrestee Segment.
There are several reasons this situation could occur. First, a
duplicate incident number might have been assigned. Second, the
participant previously submitted "Time-Window" segments and then
submitted the complete Incident Report. Last, during the annual
purge of 2-year old incidents, "Window" records were created. The
participant's computer was not programmed properly to account for
the purge process.
ERROR NUMBERS AND MESSAGES
94
Print Date: March 7, 2016
RELEASE 2.1
ZERO REPORTING SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
10090
ZERO REPORTING MONTH IS NOT 01-12
A Segment "00" was submitted that had an invalid reporting month
in positions 31-32. The data entered must be a valid month of 01
through 12.
10091
ZERO REPORTING YEAR IS INVALID
A Segment "00" was submitted that did not have four numeric
digits in positions 33-36.
10092
ZERO REPORTING INCIDENT NUMBER MUST BE ALL ZEROES
A Segment "01" was submitted, but the incident number entered
into positions 3-14 was not all zeroes.
10093
ZERO REPORTING MONTH/YEAR WAS PRIOR TO THE "BASE
DATE"
A Segment "00" was submitted with a month and year entered into
positions 31-36 that is earlier than January 1 of the previous year or
before the date the agency converted over to LIBRS.
10094
ZERO REPORTING MONTH/YEAR EXCEEDED MONTH/YEAR OF
TAPE
A Segment "00" was submitted with a month and year entered into
positions 31-36 that was later than the "Month of Tape" and "Year
of Tape" entered into positions 23-30.
10100
! ! ! ! WARNING ! ! ! ! INVALID DATA VALUE - - ORDINANCE NOT
CURRENTLY CLASSIFIED BY LIBRS
ERROR NUMBERS AND MESSAGES
95
Print Date: March 7, 2016
RELEASE 2.1
ADMINISTRATIVE SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
11001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
11004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within the LIBRS Code Table.
11005
DATE ENTERED MUST BE A VALID CALENDAR DATE
The data element in error contains a date that is not entered
correctly. Each component of the date must be valid; that is,
months must be 01-12, days must be 01-31, and year must include
the century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days). Also,
the date cannot exceed the current date.
The date cannot be later than that entered within the "Month of
Tape" and "Year of Tape" fields on the data record. For example, if
"Month of Tape" and "Year of Tape" are "06/1995," the date
entered cannot be 07/01/1995 or greater.
The error message will pinpoint what error occurred. For example,
DAT11: MONTH EXCEEDS 12 and DAT14: DAY EXCEEDS 31
are some of the "date" error messages that are displayed.
11015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
ERROR NUMBERS AND MESSAGES
96
Print Date: March 7, 2016
RELEASE 2.1
Data Element 2 (Incident Number) contained embedded blanks
between the first and last significant characters.
11016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Data Element 2 (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.
11017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9. HYPHEN,
AND/OR BLANKS
Data Element 2 (Incident Number) can only have character
combinations of A-Z, 0-9, Hyphen, and/or Blanks. For example, 89123-SC is valid, but 89+123*SC is invalid.
11018
DATE CANNOT BE ON OR AFTER THE INACTIVE DATE
[MMDDYYYY] OF THE ORI
When an ORI becomes inactive, no incident data may be submitted
to LIBRS with an incident date on or after that date. However,
adjustments to previously submitted data may be done.
11020
EXCEPTIONAL CLEARANCE DATE CANNOT PREDATE BASE DATE
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot have an
Exceptional Clearance Date (Data Element 5) earlier than the
"Time-Window Base Date. For any subsequent "M" = Modify of
a previously submitted "W" = Time-Window Submission, this
is also true.
11021
JUSTIFIABLE HOMICIDE (09C) IS NOT A VALID WINDOW OFFENSE
CODE
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot have a
ERROR NUMBERS AND MESSAGES
97
Print Date: March 7, 2016
RELEASE 2.1
Window LRS Offense Code (Data Element 6) of "09C" = Justifiable
Homicide. For any subsequent "M" = Modify of a previously
submitted "W" = Time-Window Submission, this is also true.
11051
REPORT INDICATOR MUST BE BLANK OR "R"
Within Data Element 3 (Incident date/hour) is a report indicator.
This field must be "blank" if the incident date is known. If the
incident date is unknown, then the report date would be entered
instead and must be indicated with an "R" in the Report Indicator
field within the Administrative Segment.
11052
INVALID HOUR ENTRY
If HOUR is entered within Data Element 3 (Incident Date/Hour), it
must be 00 through 23. If "00" = Midnight is entered, be careful that
the INCIDENT DATE is as if the time was 1 minute past midnight.
11053
VALUE ENTERED CONFLICTS WITH PRESENCE OF AN ENTRY IN
EXCEPTIONAL CLEARANCE DATE
Data Element 4 (Cleared Exceptionally) cannot be "N" = Not
Applicable if Data Element 5 (Exceptional Clearance Date) is
entered.
11054
CLEARED EXCEPTIONALLY CANNOT CONTAIN "N" WITH SEGMENT
ACTION TYPE "W"
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot contain an
"N" = Not Applicable in Data Element 4 (Cleared Exceptionally).
11055
CLEARANCE DATE [mmddyyyy] PREDATES INCIDENT DATE
[mmddyyyy]
Data Element 5 (Exceptional Clearance Date) is earlier than Data
Element 3 (Incident Date/Hour).
ERROR NUMBERS AND MESSAGES
98
Print Date: March 7, 2016
RELEASE 2.1
11056
AN ENTRY MUST BE MADE WHEN CLEARED EXCEPTIONALLY HAS
ENTRIES OF A - E
Data Element 5 (Exceptional Clearance Date) must be present if
the case was cleared exceptionally. Data Element 4 (Cleared
Exceptionally) had an entry of A - E; therefore, the date must also
be entered.
11057
MUST BE PRESENT FOR TIME-WINDOW SEGMENT
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission must contain Data
Elements 4 (Cleared Exceptionally) and 5 (Exceptional Clearance
Date). Both must be present to be a valid submission.
11058
OFFENSE CODE FIELD MUST HAVE ENTRY WITH SEGMENT
ACTION TYPE "W"
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission must have at least
one LRS Offense Code entered in the Window Offense code
section.
11059
ADMINISTRATIVE MODIFICATION SEGMENT NOT ALLOWED FOR
AN INCIDENT REPORT UNLESS TIME WINDOW SUBMISSION
11060
INCIDENT NOT ON FILE
Administrative Segments (Segments 10 & 11) submitted with a
Segment Action Type of "M" = Modify must already be on the State
file with Data Element 1 (ORI Number) and Data Element 2
(Incident Number).
11061
CANNOT MODIFY INCIDENT DATE THIS WAY -- ON FILE IS
[mmddyyyyrhh]
Administrative Segments ( Segment 10) submitted with a Segment
Action Type of "M" = Modify cannot change the date in Data
Element 3 (Incident Date/Hour) of Segments which were previously
submitted with a Segment Action Type of "I" = Incident Report.
ERROR NUMBERS AND MESSAGES
99
Print Date: March 7, 2016
RELEASE 2.1
11062
CANNOT MODIFY REPORT FLAG THIS WAY -- ON FILE IS
[mmddyyyyrhh]
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "M" = Modify cannot change the Report date
Indicator (position 51 of the segment) of Segments which were
previously submitted with a Segment Action Type of "I" = Incident
Report.
11063
CANNOT MODIFY INCIDENT HOUR THIS WAY -- ON FILE IS
[mmddyyyyrhh]
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "M" = Modify cannot change the hour in Data
Element 3 (Incident Date/Hour) of Segments which were previously
submitted with a Segment Action Type of "I" = Incident Report.
11064
CLEARED EXCEPTIONALLY FIELD MUST CONTAIN "N" WHEN
ARRESTEES WERE REPORTED
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "M" = Modify must have an "N" = Not Applicable in
Data Element 4 (Exceptional Clearance Indicator) when arrestees
were already present for the Incident Report.
11065
CANNOT BE BLANK OR EQUAL "N"
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "M" = Modify cannot have an "N" = Not Applicable in
Data Element 4 (Exceptional Clearance Indicator) when the
Incident was previously submitted as a "W" = Time-Window
Submission.
11066
CANNOT HAVE ENTRY IN EXCEPTIONAL CLEARANCE DATE IF
CLEARED EXCEPTIONALLY IS "N"
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "M" = Modify with an "N" = Not Applicable in Data
Element 4 (Exceptional Clearance Indicator) cannot have an entry
in Data Element 5 (Exceptional Clearance Date).
ERROR NUMBERS AND MESSAGES
100
2016
RELEASE 2.1
Print Date: March 7,
11067
DATE CANNOT BE BLANK FOR SEGMENT
Administrative Segments (Segment 10) submitted with a
Segment Action Type of "M" = Modify for a previously
submitted "W" = Time-Window Submission must have a date
in Data Element # 5 (Exceptional Clearance Date).
11069
TIME-WINDOW SEGMENT BEING MODIFIED MUST HAVE LOUISIANA
REVISED STATUE NUMBER
Administrative Modification Segments (Segment 11) submitted with
a Segment Action Type of "M" = Modify for a previously submitted
"W" = Time-Window Submission must have at least one LRS
Number in the Window Offense Code section (Positions 25 - 36 in
Segment 11 position).
11070
INCIDENT DATE CANNOT BE AFTER [yyyy] AND MONTH [mm] OF
TAPE
Data Element 3 (Incident Date/Hour) date was later than the year
and month that the magnetic media represents. For example, the
May, 1995 magnetic media cannot contain incidents happening
later than this date.
11071
INCIDENT DATE IS OUTSIDE THE BASE DATE CALCULATION
An Incident Report was submitted with a date entered into Data
Element 3 (Incident Date/Hour) that is earlier than January 1 of the
previous year, using the "Month of Tape" and "Year of Tape" as a
reference point.
For example, if the "Month of Tape" and "Year of Tape" contains a
value of "01/1996," but the incident date is 12/25/1994, the incident
will be rejected.
Note: The exception is when an exceptional clearance is being
submitted with a Segment Action Type of "W" = Time-Window
Submission. The incident date may be any "past" date, but cannot
be any earlier than January 1, 1950.
ERROR NUMBERS AND MESSAGES
101
2016
RELEASE 2.1
Print Date: March 7,
11072
INCIDENT DATE/HOUR FOR "I" RECORDS CANNOT PREDATE
01/01/1991
Data Element 3 (Incident Date/Hour) cannot be earlier than
01/01/1991. This is applied to all "I" = Incident Report submissions.
This beginning date will eliminate dates that are known to be
obviously incorrect since LIBRS(FBI) began accepting data on this
date.
11073
INCIDENT DATE CANNOT BE BEFORE DATE ORI WENT IBR
An Incident Report was submitted with Data Element 3 (Incident
Date/Hour) containing a date that occurred before the agency
converted over to LIBRS. Because of this, the record was rejected.
When an agency converts from Summary reporting to Incident
Based Reporting (IBR) or commences to report LIBRS data, no
data regarding an incident previously submitted under the
Summary reporting system can be submitted with an incident date
later than the date the agency commenced reporting, otherwise it
will be regarded as a duplicate submission and be rejected.
In other words, if the agency sends IBR data for the first time
on September 1995, monthly submittal, dates for incidents,
recovered property, and arrests must be within September.
The exception is when exceptional clearances occur for a preIBR incident. In this case, Data Element 3 (Incident Date/Hour)
may be earlier than September 1995, but Data Element 5
(Exceptional Clearance Date) must be within September 1995.
The State will reject data submitted for prior months.
Thereafter, all data coming from this agency must have dates
subsequent to the initial start date of September 1995, except
as mentioned previously. The summary system already
contains aggregate data for the months prior to LIBRS
conversion. Having the State accept LIBRS data for months
previously reported as "Summary Data" would cause duplicate
reporting within a month.
The State will maintain a table of start dates (base dates) for each
local agency. Except for the above example, the State will reject
data submitted with an Incident Date for months prior to the
agency's start date.
ERROR NUMBERS AND MESSAGES
102
Print Date: March 7, 2016
RELEASE 2.1
11074
EXCEPTIONAL CLEARANCE DATE PREDATES DATE ORI WENT IBR
[mmddyyyy]
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission or "M" = Modify
cannot have a date earlier than when the ORI converted to
Incident-Based Reporting (IBR). Data Element 5 (Exceptional
Clearance Date) was earlier.
11075
CANNOT CALCULATE BASE DATE FROM INCIDENT DATE
[mmddyyyy]
The Submission Date(C3), and the incident date must be valid
entries. The state software uses these to determine if the complete
incident should have been reported to the state, or if a subset of the
segments should have been submitted as "Time- Window"
submissions.
11076
INCIDENT DATE FOR WINDOW RECORDS CANNOT BE WITHIN
BOUNDARIES OF THE INCIDENT
Administrative Segments (Segment 10) submitted with a Segment
Action Type of "W" = Time-Window Submission cannot have a date
in Data Element 3 (Incident Date/Hour) which would be a valid date
for an Incident. For any subsequent "M" = Modify of a previously
submitted "W" = Time-Window Submission, this is also true.
11097
SEGMENT 11 MISSING (LIBRS ONLY)
ERROR NUMBERS AND MESSAGES
103
Print Date: March 7, 2016
RELEASE 2.1
ERROR NUMBERS AND MESSAGES
104
Print Date: March 7, 2016
RELEASE 2.1
OFFENSE SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
12001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
12002
CONTAINS NONNUMERIC ENTRY
Data Element 10 (Number of Premises Entered) was not a numeric
entry of 01-99.
12004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within LIBRS Code Table.
12006
ERROR - DUPLICATE VALUE =[value]
The data element in error is one that contains multiple data values.
When more than one code is entered, none can be duplicate
codes.
12007
ERROR - MUTUALLY EXCLUSIVE VALUE=[value]
The data element in error can have multiple data values and was
entered with multiple values. However, the entry shown between
the brackets in [value] above cannot be entered with any other data
value.
12015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
Data Element 2 (Incident Number) contained embedded blanks
between the first and last significant characters.
12016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
ERROR NUMBERS AND MESSAGES
105
Print Date: March 7, 2016
RELEASE 2.1
Data Element 2 (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.
12017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN,
AND/OR BLANKS
Data Element 2 (Incident Number) can only have character
combinations of A-Z, 0-9, Hyphen, and/or Blanks. For example, 89123-SC is valid, but 89+123*SC is invalid.
12019
DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
Data Element 12 (Type Criminal Activity) codes of "B", "C", "D", "E",
"I", "O", "P", "T", "U", or "X" can only be entered when Offense
Code is:
"250" = Counterfeiting/Forgery
"280" = Stolen Property Offenses
"35A" = Drug/Narcotics Violations
"35B" = Drug Equipment Violations
"39C" = Gambling Equipment Violations
"370" = Pornography/Obscene Material
"520" = Weapon Law Violations
"90A" = Bad Checks
"90Z" = Crimes Against Property
Data Element 12 (Gang Information) codes of "J", "G", and "N"
can only be entered when Offense Code is:
"09A" = Murder and Nonnegligent Manslaughter
"09B" = Negligent Homicide
"100" = Kidnapping/Abduction
"120" = Robbery
"11A" = Forcible Rape
"11B" = Forcible Sodomy
"11C" = Sexual Assault With An Object
"11D" = Forcible Fondling
"13A" = Aggravated Assault
"13B" = Simple Assault
"13C" = Intimidation
ERROR NUMBERS AND MESSAGES
106
Print Date: March 7, 2016
RELEASE 2.1
Data Element 13 (Type of Weapon/Force Involved) can only be
entered when Offense Code is:
"09A" = Murder and Nonnegligent Manslaughter
"09B" = Negligent Homicide
"09C" = Justifiable Homicide
"100" = Kidnapping/Abduction
"11A" = Forcible Rape
"11B" = Forcible Sodomy
"11C" = Sexual Assault With An Object
"11D" = Forcible Fondling
"120" = Robbery
"13A" = Aggravated Assault
"13B" = Simple Assault
"210" = Extortion
"520" = Weapon Law Violations
12051
INVALID CODE
Data Element 7 (Offense Attempted/Completed) must be a valid
code of A or C.
12052
OFFENSE CODE MUST BE BURGLARY WITH A LOCATION TYPE OF
14 OR 19 FOR DATA TO BE ENTERED
When Data Element 10 (Number of Premises Entered) is entered,
Data Element 9 (Location Type) must be "14" = Hotel/Motel/Etc. or
"19" = Rental Storage Facility, and Data Element 6 (LRS Offense
Code) must be "220" (Burglary).
12053
MUST BE PRESENT WHEN OFFENSE CODE IS 220
Data Element 11 (Method of Entry) was not entered, and must be
entered when Offense Code of "220" = Burglary is entered.
12054
MUST BE BLANK WHEN OFFENSE IS OTHER THAN BURGLARY
Data Element 11 (Method of Entry) only applies to Offense Code of
"220" = Burglary. Since a Burglary offense was not entered, the
"Method of Entry" should not have been entered.
ERROR NUMBERS AND MESSAGES
107
Print Date: March 7, 2016
RELEASE 2.1
12055
AUTOMATIC INDICATOR MUST BE BLANK OR "A"
In Data Element 13 (Type of Weapon/Force Involved), the third
character must be "A" = Automatic or blank. In this case, a value
other than the two mentioned was entered.
12056
OFFENSE CODES OF 09A, 09B, 09C, 13A, 13B, AND 13C MUST HAVE
ENTRY OF "C"
Data Element 7 (Offense Attempted/Completed) code must be
"C" = Completed if Data Element 6 (LRS Offense Code) is an
"Assault" or "Homicide."
12057
MUST BE PRESENT WITH AN OFFENSE CODE OF 220 AND A
LOCATION TYPE OF 14 OR 19
Data Element 10 (Number of Premises Entered) must be entered if
offense code is "220" (Burglary) and if Data Element 9 (Location
Type) contains "14" = Hotel/Motel/Etc. or "19"= Rental Storage
Facility.
12058
WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN "A" IN THE
AUTO INDICATOR
In Data Element 13 (Type of Weapon/Force Involved),"A" =
Automatic was the third character of code. It is valid only with
codes:
"11" = Firearm (Type Not Stated)
"12" = Handgun
"13" = Rifle
"14" = Shotgun
"15" = Other Firearm
A weapon code other than those mentioned was entered with the
"automatic" indicator. An automatic weapon is, by definition, a
firearm.
12065
INVALID WEAPON [weapon-code] WITH AN OFFENSE OF SIMPLE
ASSAULT (13B)
ERROR NUMBERS AND MESSAGES
108
Print Date: March 7, 2016
RELEASE 2.1
An Offense Segment (Segment 20) was submitted for "13B" =
Simple Assault. Accordingly, Data Element 13(Type
Weapon/Force Involved) can only have codes of "40" = Personal
Weapons, "90" = Other, "95" = Unknown, and "99" = None. All
other codes are not valid because they do not relate to a simple
assault.
12066
NO OTHER OFFENSE CAN BE SUBMITTED WITH A JUSTIFIABLE
HOMICIDE (09C) OFFENSE
When a Justifiable Homicide is reported, no other offense may be
reported in the Incident Report. These would be submitted on
another Incident Report.
12067
INVALID WEAPON [weapon-code] WITH AN OFFENSE OF [offense]
The homicide offense shown within the error message must have a
code in Data Element 13 (Type Weapon/Force Involved) other than
"99" = None. In this case, "None" was entered. Some type of
weapon/force must be used in a homicide offense.
12069
POSSIBLE CLASSIFICATION ERROR OF AGGRAVATED ASSAULT
"13A" CODED AS SIMPLE "13B"
A Simple Assault (13B) was submitted but Data Element 13
(Type Weapon/Force Involved) had a weapon code reflecting
an Aggravated Assault (13A) offense. Either the wrong
weapon code was entered or the offense should have been
classified as an Aggravated Assault (13A).
12090
OFFENSE CONNECTED TO A NON-EXISTENT VICTIM
PROPERTY SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
13001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
ERROR NUMBERS AND MESSAGES
109
Print Date: March 7, 2016
RELEASE 2.1
13002
CONTAINS NONNUMERIC ENTRY
Must be numeric entry with zero or blank left-fill and right-fill..
If Data Element 21 (Estimated Quantity) had the error, note that
any decimal fractional quantity must be expressed in thousandths
as three numeric digits. If no fractional quantity was involved, then
all zeroes would be entered.
13004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within the LIBRS Code Table.
13005
DATE ENTERED MUST BE A VALID CALENDAR DATE
Data Element 17 (Date Recovered) date components must be
valid; that is, months must be 01-12, days must be 01-31, and year
must include the century (i.e., 19xx, 20xx). In addition, days cannot
exceed maximum for the month (e.g., June cannot have 31 days).
Also, the date cannot be earlier than Data Element 3 (Incident
Date/Hour).
The date cannot be later than that entered within the "Month of
Tape" and "Year of Tape" fields on the data record. For example, if
"Month of Tape" and "Year of Tape" are "09/1995," the date
entered cannot be 07/01/1995 or greater.
13006
The error message will pinpoint what error occurred. For example,
DAT11: MONTH EXCEEDS 12 and DAT14: DAY EXCEEDS 31 are
some of the "date" error messages that are displayed.
ERROR - DUPLICATE VALUE=[value]
The data element in error is one that contains multiple data values.
When more than one code is entered, none can be duplicate
codes.
If more than one code is entered in Data Element 20 (Suspected
Drug Type), the same code cannot be entered within the same
"type measurement" category. In other words, cocaine cannot be
reported in grams and pounds (same weight category), but could
be reported in grams and liters (weight and capacity categories).
ERROR NUMBERS AND MESSAGES
110
Print Date: March 7, 2016
RELEASE 2.1
For the drug type "U" = Unknown, this does not apply; "U" =
Unknown can be entered once.
13007
CANNOT BE EARLIER THAN INCIDENT DATE/HOUR
Data Element 17 (Date Recovered) cannot be earlier than Data
Element 3 (Incident Date/Hour).
13008
DATE RECOVERED CANNOT BE AFTER SUBMISSION DATE.
Date Recovered (Data Element 17) cannot be after Submission
Date (Data Element C3).
13015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
Data Element 2 (Incident Number) contained embedded blanks
between the first and last significant characters.
13016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Data Element 2 (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.
13017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN,
AND/OR BLANKS
Data Element 2 (Incident Number) can only have character
combinations of A-Z, 0-9, Hyphen, and/or Blanks. For example, 95123-SC is valid, but 95+123*SC is invalid.
13019
DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
If Data Element 14 (Type of Property Loss) was entered, then it can
only be entered when Data Element 6 (Louisiana Revised Statute
Number) entries are:
ERROR NUMBERS AND MESSAGES
111
Print Date: March 7, 2016
RELEASE 2.1
"100" = Kidnapping/Abduction
"120" = Robbery
"200" = Arson
"210" = Extortion/Blackmail
"220" = Burglary/Breaking and Entering
"23A" = Pocket Picking
"23B" = Purse Snatching
"23C" = Shoplifting
"23D" = Theft From Building
"23E" = Theft From Coin Operated Machine or Device
"23F" = Theft From Motor Vehicle
"23G" = Theft of Motor Vehicle Parts or Accessories
"23H" = All Other Larceny
"240" = Motor Vehicle Theft
"250" = Counterfeiting/Forgery
"26A" = False Pretenses/Swindle/Confidence Game
"26B" = Credit Card/Automated Teller Machine Fraud
"26C" = Impersonation
"26D" = Welfare Fraud
"26E" = Wire Fraud
"270" = Embezzlement
"280" = Stolen Property Offenses
"290" = Destruction/Damage/Vandalism
"35A" = Drug/Narcotics Violations
"35B" = Drug Equipment Violations
"39A" = Betting/Wagering
"39B" = Operating/Promoting/Assisting Gambling
"39C" = Gambling Equipment Violations
"39D" = Sports Tampering
"510" = Bribery
"90A" = Bad Checks
"90Z" = Crime Against Property
13020
RECOVERED DATE CANNOT PREDATE BASE DATE
Property Segments (Segment 31) submitted with a Segment Action
Type of "W" = Time-Window Submission cannot have a Date
Recovered (Data Element 17) before the date which is calculated
using the base date technique (January 1 of the year prior to the
current year, or earlier than the date the agency converted to IBR).
For any subsequent "M" = Modify of a previously submitted "W" =
Time-Window Submission, this also applies.
ERROR NUMBERS AND MESSAGES
112
Print Date: March 7, 2016
RELEASE 2.1
13021
JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE CODE
Property Segments (Segments 30, 31, or 32) submitted with a
Segment Action Type of "W" = Time-Window Submission cannot
have a Window Offense Code (Data Element 6) of "09C" =
Justifiable Homicide. For any subsequent "M" = Modify of a
previously submitted "W" = Time-Window Submission, this also
applies.
13042
WARNING - PROPERTY DESCRIPTION (DATA ELEMENT 15) HAD
VALUE (DATA ELEMENT 16) THAT EXCEEDED THRESHOLD OF [$
value]
This is a warning message only.
Data Element 16 (Value of Property) contained a value that
exceeded assigned threshold amount. The participant should
check to see if the value entered was a data entry error, or if it is
correct. In addition to various thresholds assigned to particular
property descriptions, a warning message is always produced when
the value is $1,000,000 or greater.
For example, if the value of property was $12,000.99 but was
inadvertently entered as $1,200,099 in the computer record sent to
the State, a "warning" message is generated. In this case, the
cents were entered as whole dollars.
13043
WARNING - "280" OFFENSE HAS "RECOVERED" VEHICLE BUT
"240" DOESN'T SHOW "STOLEN"
This is a warning message only.
This warning is generated when a "280" Stolen Property Offense
and a "240" Motor Vehicle Theft are submitted that contain
questionable property reporting. When the incident contains a
"recovered" vehicle but does not also have a "stolen" vehicle, this
warning message is created. The incident should be reviewed and
if there was indeed a "stolen" vehicle, the incident should be
resubmitted reflecting both "stolen" and "recovered" vehicles.
13051
PROPERTY VALUE OF ZERO IS NOT ALLOWED
ERROR NUMBERS AND MESSAGES
113
Print Date: March 7, 2016
RELEASE 2.1
Data Element 16 (Value of Property) had a value of zero entered
for dependent code in Data Element 15 (Property Description); zero
value cannot be entered for this property description. If value
is unknown, enter a value of "1" dollar; otherwise, the value of the
property must be entered for the code.
Zero values must be entered for:
"09" = Credit/Debit Cards
"22" = Nonnegotiable Instruments
Zero values are optional for:
"77" = Other
"99" = (special category)
13052
DATA ELEMENTS 15 - 22 MUST BE BLANK WHEN PROPERTY LOSS
CODE = 1 OR 8
When this error occurs, data was found in one or more of the
referenced data elements. These data elements must be blank
based on other data element values that prohibit data being
entered in these data elements.
For example, if Data Element 14 (Type Property Loss/Etc.) is "8" =
Unknown, Data Elements 15-22 must be blank. If it is "1" = None
and offense is "35A", then Data Elements 15-19 and 21-22 must be
blank. If it is "1" = None and offense is not "35A," then Data
Elements 15-22 must be blank.
13053
PENDING INVENTORY MUST HAVE PROPERTY VALUE OF "1"
Data Element 15 (Property Description) was "88" = Pending
Inventory, but Data Element 16 (Value of Property) was not "1"
dollar. Determine which of the data elements was entered
incorrectly.
13054
DATA ELEMENT 15 WAS NOT ENTERED, BUT VALUE($) WAS
Data Element 16 (Value of Property) contained a value, but Data
Element 15 (Property Description) was not entered.
ERROR NUMBERS AND MESSAGES
114
Print Date: March 7, 2016
RELEASE 2.1
13055
PROPERTY LOSS CODE (DATA ELEMENT 14) MUST = 5
(RECOVERED) FOR DATA TO BE ENTERED
Data Element 14 (Type Property Loss/Etc.) must be "5" =
Recovered for Data Element 17 (Date Recovered) to be entered.
13056
PROPERTY DESCRIPTION (DATA ELEMENT 15) AND VALUE (DATA
ELEMENT 16) MUST BOTH EXIST IF DATA IS PRESENT
Data Element 17 (Date Recovered) was entered, but Data
Elements 15 (Property Description) and/or Data Element 16
(Property Value) were not entered.
13057
PROPERTY LOSS (14) MUST BE 7 WITH A MOTOR VEHICLE THEFT
OFFENSE CODE OR LRS = 14:67 OR 14:68 WITH PROPERTY
DESCRIPTION CODES OF “03", “05", “24, 28, OR “37" FOR DATA TO
BE ENTERED
Data Element 18 (Number of Stolen Motor Vehicles) was entered.
However, Data Element 14 (Type Property Loss/Etc.) "7" =
Stolen/Etc. was not entered, and/or Data Element 6 (LRS Offense
Code) of "240" = Motor Vehicle Theft or LRS = 14:67 or 14:68 with
Property Description Codes (Data Element 15) of “03", “05",
“24, 28, or “37" was not entered, and/or Data Element 7
(Offense Attempted/Completed) was "A" = Attempted.
13058
DATA MUST EXIST WITH A MOTOR VEHICLE THEFT OFFENSE
CODE OR LRS = 14:67 OR 14:68 WITH PROPERTY DESCRIPTION
CODES OF “03", “05", “24, 28, OR “37" AND A PROPERTY LOSS OF
7
Entry must be made for Data Element 18 (Number of Stolen Motor
Vehicles) when Data Element 6 (LRS Offense Code) is "240" =
Motor Vehicle Theft or LRS = 14:67 or 14:68 with Property
Description Codes (Data Element 15) of “03", “05", “24, 28, or
“37", Data Element 7(Offense Attempted/ Completed) is "C" =
Completed and Data Element 14 (Type Property Loss/Etc.) is
"7" = Stolen/Etc.
13059
ALL NONVEHICULAR PROPERTY DESCRIPTIONS WERE ENTERED
ERROR NUMBERS AND MESSAGES
115
Print Date: March 7, 2016
RELEASE 2.1
When Data Element 18 (Number of Stolen Motor Vehicles) is
entered, Data Element 15 (Property Description) must contain at
least one of the following vehicle codes:
"03" = Automobiles
"05" = Buses
"24" = Other Motor Vehicles
"28" = Recreational Vehicles
"37" = Trucks
When Data Element 19 (Number of Recovered Motor Vehicles) is
entered and is "01" through "99", Data Element 15 (Property
Description) must contain at least one of the following vehicle
codes:
"03" = Automobiles
"05" = Buses
"24" = Other Motor Vehicles
"28" = Recreational Vehicles
"37" = Trucks
13060
PROPERTY LOSS (14) MUST BE 5 WITH A MOTOR VEHICLE THEFT
OFFENSE CODE OR LRS = 14:67 OR 14:68 WITH PROPERTY
DESCRIPTION CODES OF “03", “05", “24, 28, OR “37" FOR DATA TO
BE ENTERED
Data Element 19 (Number of Recovered Motor Vehicles) was
entered. However, Data Element 14 (Type Property Loss/Etc.) "5"
= Recovered was not entered, and/or Data Element 6 (LRS Offense
Code) of "240" = Motor Vehicle Theft or LRS = 14:67 or 14:68 with
Property Description Codes (Data Element 15) of “03", “05",
“24, 28, or “37" was not entered, and/or Data Element 7 (Offense
Attempted/Completed) was "A" = Attempted.
13061
DATA MUST EXIST WITH A MOTOR VEHICLE THEFT OFFENSE
CODE OR LRS = 14:67 OR 14:68 WITH PROPERTY DESCRIPTION
CODES OF “03", “05", “24, 28, OR “37" AND A PROPERTY LOSS OF
5
Entry must be made for Data Element 19 (Number of Recovered
Motor Vehicles) when Data Element 6 (LRS Offense Code) is "240"
= Motor Vehicle Theft or LRS = 14:67 or 14:68 with Property
ERROR NUMBERS AND MESSAGES
116
Print Date: March 7, 2016
RELEASE 2.1
Description Codes (Data Element 15) of “03", “05", “24, 28, or
“37", Data Element 7 (Offense Attempted/Completed) is "C" =
Completed, Data Element 14 (Type Property Loss/Etc.) is "5" =
Recovered, and vehicle codes were recovered.
13064
WITH DATA ENTERED QUANTITY (DATA ELEMENT 21),
MEASUREMENT (DATA ELEMENT 22), AND VALUE (DATA ELEMENT
16) MUST BE PRESENT
When Data Element 6 (LRS Offense Code) is "35A" =
Drug/Narcotic Violations, 14 (Type Property Loss/Etc.) is "6" =
Seized, 15 (Type Property Loss/Etc.) is "10" = Drugs, and Data
Element 20 (Suspected Drug Type) are entered, Data Element 21
(Estimated Quantity), Data Element 22 (Type Measurement) and
Data Element 16 (Value of Property) must be entered.
13065
OFFENSE = 35A AND PROPERTY LOSS = 6 AND PROPERTY
DESCRIPTION = 10 MUST EXIST
Data Element 20 (Suspected Drug Type) was entered, but one or
more required data elements were not entered. Data Element 6
(LRS Offense Code) must be "35A" = Drug/Narcotic Violations,
Data Element 14 (Type Property Loss/Etc.) must be "6" = Seized,
and Data Element 15 (Property Description) must be "10" =
Drug/Narcotics.
There could be multiple underlying reasons causing this error to be
detected. One of them might be that Data Element 20 (Suspected
Drug Type) was entered by mistake. Perhaps the code entered in
Data Element 15 (Property Description) should have been "01" =
Aircraft, but by entering it as "10" = Drugs/Narcotic, someone
thought that Data Element 20 must be entered, etc.
13066
WITH DATA ENTERED DRUG TYPE (DATA ELEMENT 20), TYPE
MEASUREMENT (DATA ELEMENT 22), AND VALUE (DATA ELEMENT
16) MUST BE PRESENT
Data Element 21 (Estimated Quantity) was entered, but Data
Element 20 (Suspected Drug Type) and/or Data Element 22 (Type
Measurement) and/or Data Element 16 (Value of Property) were
not entered; all must be entered.
ERROR NUMBERS AND MESSAGES
117
Print Date: March 7, 2016
RELEASE 2.1
13067
DRUG TYPE MUST BE "E," "G," OR "K" FOR A VALUE OF "NP"
Data Element 22 (Type Measurement) was entered with "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 to limit "NP" = Number of Plants to the following
drugs:
DRUG
MEASUREMENT
E=Marijuana
G=Opium
K=Other Hallucinogens
NP
NP
NP
All other Data Element 22 (Type Measurement) codes are
applicable to any Data Element 20 (Suspected Drug Type) code.
13068
WITH DATA ENTERED DRUG TYPE (DATA ELEMENT 20), QUANTITY
(DATA ELEMENT 21), AND VALUE (DATA ELEMENT 16) MUST BE
PRESENT
Data Element 22 (Type Measurement) was entered, but Data
Element 20 (Suspected Drug Type), Data Element 21 (Estimated
Quantity) and/or Data Element 16 (Value of Property) were not
entered; all must be entered.
13070
MUST HAVE AN ENTRY WITH AN ACTION TYPE OF "W"(WINDOW)
Property Modification Segment (Segment 32) submitted with a
Segment Action Type of "W" = Time-Window Submission or "M" =
Modify must have a LRS Offense Code entered in positions 25 36.
13071
GAMBLING, KIDNAPPING, AND CRIMES AGAINST PROPERTY ARE
THE ONLY VALID OFFENSES
A Segment Action Type of "W" = Time-Window Submission or "M"
= Modify was submitted for "Recovered Property" on a Property
Modification Segment (Segment 32). When submitted, all
associated offense codes must be "Crimes Against Property,"
ERROR NUMBERS AND MESSAGES
118
Print Date: March 7, 2016
RELEASE 2.1
Kidnapping, or Gambling. In this instance, offense codes other
than those mentioned were submitted.
13072
DATA ELEMENTS 15-22 WERE ALL BLANK WITH THIS PROPERTY
LOSS CODE
If Data Element 14 (Type Property/Loss/Etc.) is "2" =Burned, "3" =
Counterfeited/Forged, "4" = Destroyed/Damaged/Vandalized, "5" =
Recovered, "6" = Seized, or "7" = Stolen/Etc., Data Elements 15-22
must have applicable entries in the segment.
13075
MANDATORY FIELD WITH THE PROPERTY LOSS CODE ENTERED
At least one Data Element 15 (Property Description) code must be
entered when Data Element 14 (Type Property Loss/Etc.) contains
Property Segments(s) for:
"2" = Burned
"3" = Counterfeited/Forged
"4" = Destroyed/Damaged/Vandalized
"5" = Recovered
"6" = Seized
"7" = Stolen/Etc.
13076
DUPLICATE PROPERTY SEGMENT ON MAGNETIC MEDIA (TYPE
LOSS = [loss-code])
When an 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 Data
Element 14 (Type Property Loss/Etc.).
13077
PROPERTY SEGMENT A-O-F ADDED ON [mmddyyyy] RECOVERY
DATE=[mmddyyyy]
A Property Modification Segment (Segment 32) was submitted with
a Segment Action Type of "W" = Time-Window Submission that
was already on the State's data base. Since the record was
Already-On-File (AOF), it cannot be added again in this manner.
Either delete and resubmit, or submit as a modify.
ERROR NUMBERS AND MESSAGES
119
Print Date: March 7, 2016
RELEASE 2.1
13078
ATTEMPT TO ADD OTHER THAN "RECOVERED" PROPERTY IS NOT
ALLOWED
A Segment Action Type of "W" = Time-Window Submission or "M"
= Modify was submitted for a Property Segment (Segment 30).
Accordingly, Data Element 14 (Type Property Loss/Etc.) must be
"5" = Recovered. In this instance, a code other than "5" =
Recovered was submitted.
13079
ATTEMPT TO MODIFY OTHER THAN "RECOVERED" PROPERTY IS
NOT ALLOWED
Property Segment (Segment 31) submitted with a Segment Action
Type of "M" = Modify must contain a "5" = Recovered in Data
Element 14 (Type Property Loss/Etc.).
13080
CANNOT MODIFY PROPERTY -- ADDED [mmddyyyy] DATA
ELEMENT 3 = [mmddyyyy]
Property Segments (Segment 32) submitted with a Segment Action
Type of "M" = Modify can only modify a Property Segment that was
previously submitted as a "W" = Time-Window Submission.
13081
CANNOT DELETE PROPERTY -- ADDED [mmddyyyy] DATA
ELEMENT 3 = [mmddyyyy]
Property Segments (Segment 30) submitted with a Segment Action
Type of "D" = Delete can only delete a Property Segment that was
previously submitted as a "W" = Time-Window Submission.
13084
WITH A MEASUREMENT OF "XX" (NOT REPORTED) DRUG
QUANTITY MUST = 1
Data Element 21 Estimated Quantity) did not have a value of "1"
where "XX" = Not Reported was entered for Data Element 22 (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
resubmission of the Incident Report would be done containing the
completed data.
ERROR NUMBERS AND MESSAGES
120
Print Date: March 7, 2016
RELEASE 2.1
13087
WITH A PROPERTY LOSS = 6 AND ONLY OFFENSE 35A CANNOT
HAVE DESCRIPTION 11
OR
WITH A PROPERTY LOSS = 6 AND ONLY OFFENSE 35B CANNOT
HAVE DESCRIPTION 10
To ensure that 35A-35B Drug/Narcotic Offenses are properly
reported, Data Element 15 (Property Description) of "11" = Drug
Narcotic Equipment is not allowed with only a 35A Drug/Narcotic
Violation.
Similarly, "10" = Drug/Narcotics is not allowed with only a 35B Drug
Equipment Violation.
However, in multiple "Crimes Against Property" offenses where one
offense is a 35A Drug/Narcotic violation and the other is, a 120
Robbery that involves "11" = Drug/Narcotic Equipment, it can be
entered. In this case, the above edit will be bypassed. Similarly,
"10" = Drugs/Narcotics can be entered along with a 35B Drug
Equipment Violation as long as that property is involved in the 120
Robbery.
13088
NUMBER STOLEN IS LESS THAN NUMBER OF VEHICLES CODES
More than one vehicle code was entered in Data Element 15
(Property Description), but the number stolen in Data Element 18
(Number of Stolen Motor Vehicles) was less than this number. For
example, if vehicle codes of "03" = Automobiles and "05" = Buses
were entered as being stolen, then the number stolen must be at
least 2, unless the number stolen was unknown ("00").
13089
NUMBER RECOVERED IS LESS THAN NUMBER OF VEHICLE CODES
More than one vehicle code was entered in Data Element 15
(Property Description), but the number recovered in Data Element
19 (Number of Recovered Motor Vehicles) was less than this
number. For example, if vehicle codes of "03" = Automobiles and
"05" = Buses were entered as being recovered, then the number
recovered must be at least 2, unless the number recovered was
unknown ("00").
ERROR NUMBERS AND MESSAGES
121
Print Date: March 7, 2016
RELEASE 2.1
13090
ILLOGICAL PROPERTY DESCRIPTION FOR THE OFFENSE(S)
SUBMITTED
A property code was entered in Data Element 15 (Property
Description) that was illogical for the property offense. Either the
offense was classified incorrectly in Data Element 6 (LRS Offense
Code) or the wrong property description code was entered. For
example, "18" = Livestock would be an illogical object of a
Larceny/Pocket-Picking offense.
Property offenses identified below cannot have illogical property
descriptions for stolen and/or recovered property. This includes
“Window” submissions of recovered property. When the offense
has fewer “allowable” values than “not allowed,” the allowable
values are shown instead. These are indicated by “YES” or “NO”
under the “Allowed” column. If multiple property offenses are
submitted in an incident and one or more property offenses not
listed below are present (e.g., embezzlement, etc.), then this edit is
bypassed.
Offense
Allowed
Property Descriptions
220 Burglary
240 Motor Vehicle Theft
NO
NO
NO
NO
NO
NO
NO
29-Structures-Single Occupancy
Dwelling
30-Structures-Other Dwellings
31-Structures-Commercial /
Business
32-Structures-Industrial /
Manufacturing
33-Structures-Public/Community
34-Structures-Storage
35-Structures-Other
23A Larceny/Pocket-Picking
23B Larceny/Purse-Snatching
NO
NO
NO
NO
NO
NO
NO
ERROR NUMBERS AND MESSAGES
01-Aircraft
03-Automobiles
04-Bicycles
05-Buses
12-Farm Equipment
15-Heavy Construction/Industrial
Equipment
18-Livestock
122
Print Date: March 7, 2016
RELEASE 2.1
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
24-Other Motor Vehicles
28-Recreational Vehicles
29-Structures-Single Occupancy
Dwelling
30-Structures-Other Dwellings
31-Structures-Commercial /
Business
32-Structures-Industrial /
Manufacturing
33-Structures-Public/Community
34-Structures-Storage
35-Structures-Other
37-Trucks
39-Watercraft
23C Larceny/Shoplifting
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
01-Aircraft
03-Automobiles
05-Buses
12-Farm Equipment
15-Heavy Construction/Industrial
Equipment
18-Livestock
24-Other Motor Vehicles
28-Recreational Vehicles
29-Structures-Single Occupancy
Dwelling
30-Structures-Other Dwellings
31-Structures-Commercial /
Business
32-Structures-Industrial /
Manufacturing
33-Structures-Public/Community
34-Structures-Storage
35-Structures-Other
37-Trucks
39-Watercraft
23D Larceny/Theft From Building
23E Larceny/Theft From Coin-Operated Machine or Device
23F Larceny/Theft From Motor Vehicle
23G Larceny/Theft of Motor Vehicle Parts/Accessories
NO
NO
NO
NO
ERROR NUMBERS AND MESSAGES
03-Automobiles
05-Buses
24-Other Motor Vehicles
28-Recreational Vehicles
123
Print Date: March 7, 2016
RELEASE 2.1
NO
NO
NO
29-Structures-Single Occupancy
Dwelling
30-Structures-Other Dwellings
31-Structures-Commercial /
Business
32-Structures-Industrial /
Manufacturing
33-Structures-Public/Community
34-Structures-Storage
NO
NO
35-Structures-Other
37-Trucks
NO
NO
NO
23H Larceny/All Other Larceny
NO
NO
NO
NO
NO
13091
03-Automobiles
05-Buses
24-Other Motor Vehicles
28-Recreational Vehicles
37-Truck
PROPERTY VALUE MUST BE ZERO FOR DESCRIPTION [property
description code]
Data Element 15 (Property Description) has a code that requires a
zero value in Data Element 16 (Value of Property). Either the
wrong property description code was entered or the property value
was not entered.
This edit was formerly error number 13040, a warning message. It
is now a fatal error.
13092
"35A" OFFENSE ENTERED AND "1 = NONE" ENTERED; MISSING
SUSPECTED DRUG TYPE (20)
An offense of "35A Drug/Narcotic Violations" and Data Element 14
(Type Property Loss/Etc.) with "1" = None were entered, but Data
Element 20 (Suspected Drug Type) was not submitted. Since a
drug seizure did not occur, the suspected drug type must also
be entered.
This edit was formerly error number 13041, a warning message. It
is now a fatal error.
OFFENDER SEGMENT ERRORS
ERROR NUMBERS AND MESSAGES
124
Print Date: March 7, 2016
RELEASE 2.1
ERROR
NUMBER
MESSAGE
14001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
14002
CONTAINS NONNUMERIC ENTRY
Data Element 36 (Offender Sequence Number) must contain
numeric entry (000 through 999) with zero left-fill.
14004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within LIBRS Code Table.
14008
EXACT AGE MUST BE IN FIRST TWO POSITIONS
Data Element 37 (Age of Offender) contained data but was not leftjustified. A single 2-character age must be in positions 1-2 of the
field.
14009
ESTIMATED AGE MUST HAVE "E" IN LAST POSITION
Data Element 37 (Age of Offender) must contain 2 numeric digits,
and have a trailing "E" if Age is Estimated
14015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
Data Element 2 (Incident Number) contained embedded blanks
between the first and last significant characters.
14016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Data Element 2 (Incident Number) must be left-justified with blank
right-fill. Since the number is less than 12 characters, it must begin
ERROR NUMBERS AND MESSAGES
125
Print Date: March 7, 2016
RELEASE 2.1
in position 1; one or more blanks were entered starting in position 1
followed by the data.
14017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN,
AND/OR BLANKS
Data Element 2 (Incident Number) can only have character
combinations of A-Z, 0-9, hyphen, and/or Blanks. For example, 89123-SC is valid, but 89+123*SC is invalid.
14022
ESTIMATED AGE CANNOT BE "00" UNKNOWN AND HAVE A
TRAILING "E".
Data Element 37(Age of Offender) was entered. Therefore,
Estimated age cannot be "00" = unknown and have a trailing "E".
14050
OFFENDER IS SPOUSE, BUT AGE IS LESS THAN 10
Data Element 35 (Relationship of Victim to Offender) contained a
relationship of "SE" = Spouse. When this is so, the age of the
offender cannot be less than 10 years.
14051
DUPLICATE OFFENDER SEGMENT ON TAPE
When an Incident Report is submitted, the individual segments
comprising the incident cannot contain duplicates. In this
case, 2 Offender Segments were submitted having the same
entry in Data Element 36 (Offender Sequence Number).
14052
CANNOT BE PRESENT WHEN OFFENDER NUMBER IS "000"
UNKNOWN
Data Element 37 (Age of Offender), Data Element 38 (Sex of
Offender), and Data Element 39 (Race of Offender) cannot be
entered when Data Element 36 (Offender Sequence Number) is
"000" = Unknown.
14053
SEX OF VICTIM AND OFFENDER DOES NOT REFLECT THE
RELATIONSHIP
ERROR NUMBERS AND MESSAGES
126
Print Date: March 7, 2016
RELEASE 2.1
Data Element 35 (Relationship of Victim to Offender) had a
relationship that was 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 offender was "SE" =
Spouse, then the victim's sex cannot be the same as the offender's
sex.
The following relationships must reflect either the "Same" or
"Different" sex codes depending upon this relationship:
14054
Relationship
Sex Code
XS = Victim was Ex-Spouse
SE = Victim was Spouse
CS = Victim was Common-Law Spouse
ES = Victim was Estranged Spouse
HR = Homosexual
VO = Victim was Offender
BG = Victim was Boyfriend/
Girlfriend
XB = Victim was Ex-Boyfriend/Girlfriend
NM = Non-Married Live-In
Different
Different
Different
Different
Same
Same
Different
Different
Different
AGE OF VICTIM AND OFFENDER DOES NOT REFLECT THE
RELATIONSHIP
Data Element 35 (Relationship of Victim to Offender) had a
relationship that was inconsistent with the offender's age. The age
of the victim and/or offender must reflect the implied relationship.
For example, if the relationship of the victim to offender was "PA" =
Parent, then the victim's age must be greater than the offender's
age.
The following relationships must be consistent with the Victim's age
in relation to the Offender's age:
Relationship
Victim's Age Is
CH = Victim was Child
PA = Victim was Parent
GP = Victim was Grandparent
GC = Victim was Grandchild
VO = Victim was Offender
BE = Victim was Babysittee (the baby)
Younger
Older
Older
Younger
Same Age
Younger
ERROR NUMBERS AND MESSAGES
127
Print Date: March 7, 2016
RELEASE 2.1
SE = Victim was Spouse
ES = Victim was Estranged Spouse
CS = Victim was Common-Law
Spouse
XS = Victim was Ex-Spouse
NM = Victim was Non-Married Live-In
14055
At least 10 yrs.
At least 10 yrs.
At least 10 yrs.
At least 10 yrs.
At least 10 yrs.
OFFENDER "000" EXISTS -- CANNOT SUBMIT MORE OFFENDERS
When multiple Offender Segments are submitted, none can contain
a "000" = Unknown value because the presence of "000" indicates
that the number of offenders was unknown. In this case, multiple
offenders were submitted but one of the segments contained the
"000" = Unknown value.
14056
OFFENDER EXACT AGE MUST BE NUMERIC DIGITS
Data Element 37 (Age of Offender) must contain numeric entry of
00 - 99.
14057
OFFENDER SEQUENCE NUMBER CANNOT BE UNKNOWN IF
INCIDENT CLEARED EXCEPTIONALLY
Data Element 36 (Offender Sequence Number) contained "000"
that indicates that nothing was known about the offender(s)
regarding number and any identifying information. In order to
exceptionally clear the incident, the value cannot be "000."
The incident was submitted with Data Element 4 (Cleared
Exceptionally) having a valid entry.
14058
AT LEAST ONE OFFENDER MUST HAVE KNOWN VALUES
None of the Offender Segments contained all "known" values for
AGE, SEX, and RACE. When an Incident is cleared exceptionally
(Data Element 4 contains a valid entry), one offender must have
all known values.
14059
OFFENDER DATA MUST BE PRESENT IF OFFENSE CODE IS 09C,
JUSTIFIABLE HOMICIDE
ERROR NUMBERS AND MESSAGES
128
Print Date: March 7, 2016
RELEASE 2.1
The incident was submitted with Data Element 6 (LRS Offense
Code) value 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, and
Race.
If Data Element 36 (Offender Sequence Number) contained "000"
(indicating that nothing was known about the offender(s) regarding
number and any identifying information), the incident is rejected
because one of the offenders must have "known" values.
14060
VICTIM'S SEX CANNOT BE SAME AS ALL OFFENDERS FOR
OFFENSES OF "11A" AND "36B"
One or more of the offender's sex must be different from that
of the victim's sex when the offense is Forcible Rape ("11A")
or Statutory Rape ("36B). Either the offense should be
something else or maybe the sex code of either the victim or
the offender(s) was entered incorrectly.
14061
SEGMENT 41 (OFFENDER USING) SEGMENT MISSING; OR, NO
SEGMENT 41 TO MATCH EXISTING SEGMENT 40
14070
BIAS MOTIVATION = 99 REQUIRES THAT AN OFFENDER AGE BE
ENTERED. AT LEAST ONE OFFENDER MUST BE COMPLETELY
KNOWN
ERROR NUMBERS AND MESSAGES
129
Print Date: March 7, 2016
RELEASE 2.1
VICTIM SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
15001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
15002
CONTAINS NONNUMERIC ENTRY
Must contain numeric entry with zero left-fill.
15003
MISSING VICTIM INJURY SEGMENT (SEGMENT 51)
15004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within LIBRS Code Table.
15005
MISSING VICTIM/OFFENDER SEGMENT (SEGMENT 52)
15006
ERROR - DUPLICATE VALUE=[value]
The data element in error is one that contains multiple data values.
When more than one code is entered, none can be duplicate
codes.
15007
ERROR - MUTUALLY EXCLUSIVE VALUE=[value]
Data Element 33 (Type Injury) can have multiple data values and
was entered with multiple values. However, the entry shown
between the brackets in [value] above cannot be entered with any
other data values.
15008
EXACT AGE MUST BE IN FIRST TWO POSITIONS
ERROR NUMBERS AND MESSAGES
130
Print Date: March 7, 2016
RELEASE 2.1
Data Element 26 (Age of Victim) contained data, but was not leftjustified. A single 2-character age must be in positions 1-2 of the
field.
15009
ESTIMATED AGE MUST HAVE "E" IN LAST POSITION
Data Element 26 (Age of Victim) must be 2 numeric digits, and
have a trailing "E" ,if it is Estimated.
15015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
Data Element 2 (Incident Number) contained embedded blanks
between the first and last significant characters.
15016
MUST BE LEFT-JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Data Element 2 (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.
15017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN,
AND/OR BLANKS
Data Element 2 (Incident Number) can only have character
combinations of A-Z, 0-9, Hyphen, and/or Blanks. For example, 89123-SC is valid, but 89+123*SC is invalid.
15019
DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
If Data Element 31 (Aggravated Assault/Homicide
Circumstances and Law Enforcement Officers Killed/Assaulted
(in the line of duty) Type of Assignment) was entered, then it
can only be entered when Data Element 24 (Offense Connected to
Victim Sequence Number) entry is connected to one of the
following offenses:
"09A" = Murder and Nonnegligent Manslaughter
"09B" = Negligent Homicide
ERROR NUMBERS AND MESSAGES
131
Print Date: March 7, 2016
RELEASE 2.1
"09C" = Justifiable Homicide
"13A" = Aggravated Assault
"13B" = Simple Assault (Only Simple Assaults that
pertain to Assaults on Law Enforcement
Officers.)
If Data Element 33 (Type Injury) was entered, then it can only be
entered when Data Element 24 (Offense Connected to Victim
Sequence Number) entry is connected to one of the following
offenses:
"100" = Kidnapping/Abduction
"11A" = Forcible Rape
"11B" = Forcible Sodomy
"11C" = Sexual Assault With An Object
"11D" = Forcible Fondling
"120" = Robbery
"13A" = Aggravated Assault
"13B" = Simple Assault
"210" = Extortion/Blackmail
"90Z" = Crime Against Person
15022
ESTIMATED AGE CANNOT BE "00" = UNKNOWN
Data Element 26 (Age of Victim) was entered. Therefore, the
estimated age cannot be "00" = Unknown and have a trailing "E".
15050
VICTIM IS SPOUSE, BUT AGE IS LESS THAN 10
Data Element 35 (Relationship of Victim to Offender) contained a
relationship of "SE" = Spouse. When this is so, the age of the
victim cannot be less than 10 years.
15051
VICTIM NUMBER ALREADY EXISTS
When an Incident Report is submitted, the individual segments
comprising the incident cannot contain duplicates. In this
case, 2 Victim Segments were submitted having the same
entry in Data Element 23 (Victim Sequence Number).
15053
MUST BE PRESENT WHEN VICTIM TYPE(25) = "I" or "L"
ERROR NUMBERS AND MESSAGES
132
Print Date: March 7, 2016
RELEASE 2.1
The Data Element associated with this error must be present when
Data Element 25 (Type of Victim) is "I" = Individual or "L" = Law
Enforcement Officer.
15055
ADDITIONAL JUSTIFIABLE HOMICIDE IS MANDATORY WITH A "20"
OR "21" ENTERED
Data Element 31 (Aggravated Assault/Homicide Circumstances
and Law Enforcement Officers Killed/Assaulted (in the line of
duty) Type of Assignment) contained:
"20" = Criminal Killed by Private Citizen
or
"21" = Criminal Killed by Police Officer,
but Data Element 32 (Additional Justifiable Homicide
Circumstance and Law Enforcement Officers Killed/Assaulted
(in the line of duty) Type of Activity) was not entered.
15056
ONLY ONE VALUE GREATER OR EQUAL TO "10" CAN BE ENTERED
Data Element 31 (Aggravated Assault/Homicide Circumstances
and Law Enforcement Officers Killed/Assaulted (in the line of
duty) Type of Assignment) was entered with 2 entries, but was
rejected for one of the following reasons:
8) Value "10" = Unknown Circumstances is mutually exclusive
with any other value.
2) More than one category (i.e., Aggravated..., Negligent...,
Justifiable...) was entered.
15057
WHEN DATA ELEMENT 32 IS ENTERED, DATA ELEMENT 31 MUST
EQUAL "20" OR "21" UNLESS TYPE OF VICTIM IS EQUAL TO “L” =
LAW ENFORCEMENT OFFICER.
Data Element 32 (Additional Justifiable Homicide
Circumstance and Law Enforcement Officers Killed/Assaulted
(in the line of duty) Type of Activity) was entered, but Data
Element 31 (Aggravated Assault/Homicide Circumstances and
Law Enforcement Officers Killed/Assaulted (in the line of duty)
ERROR NUMBERS AND MESSAGES
133
Print Date: March 7, 2016
RELEASE 2.1
Type of Assignment) did not reflect a "Justifiable Homicide"
Circumstance.
15058
VICTIM TYPE (DATA ELEMENT 25) MUST BE "I" OR "L" FOR DATA
TO BE ENTERED
The Data Element associated with this error cannot be entered
when Data Element 25 (Type of Victim) is not "I" = Individual or "L"
= Law Enforcement Officer.
15059
NEED A CRIME AGAINST PERSON OR ROBBERY FOR DATA TO BE
ENTERED
Data Element 34 (Offender Numbers To Be Related) was entered
but should only be entered if one or more of the offenses entered
into Data Element 24 (Offense Connected to Victim Sequence
Number) is connected to a "Crime Against Person" or is a Robbery
Offense (120). None of these type offenses were connected to
this victim.
15060
RELATIONSHIP MUST BE ENTERED WHEN AN OFFENDER NUMBER
(DATA ELEMENT 34) EXISTS
Corresponding Data Element 35 (Relationship of Victim to
Offender) data must be entered when Data Element 34 (Offender
Numbers To Be Related) is entered with a value greater than "000."
15061
VICTIM TYPE CANNOT EQUAL "S" WITH AN OFFENSE OF 220
Data Element 25 (Type of Victim) cannot have a value of "S" =
Society/Public when the offense is "220" = Burglary/Breaking and
Entering.
15062
INVALID AGGRAVATED ASSAULT/HOMICIDE FOR 13A OFFENSE
An Offense Segment (Segment 20) was submitted for "13A" =
Aggravated Assault. Accordingly, Data Element 31 (Aggravated
Assault/Homicide Circumstances and Law Enforcement
Officers Killed/Assaulted (in the line of duty) Type of
ERROR NUMBERS AND MESSAGES
134
Print Date: March 7, 2016
RELEASE 2.1
Assignment) 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 an aggravated assault.
15063
INVALID AGGRAVATED ASSAULT/HOMICIDE FOR 09C OFFENSE
When a Justifiable Homicide is reported, Data Element 31
(Aggravated Assault/Homicide Circumstances and Law
Enforcement Officers Killed/Assaulted (in the line of duty)
Type of Assignment) can only have codes of "20" = Criminal
Killed by Private Citizen or "21" = Criminal Killed by Police Officer.
In this case, another code other than the two mentioned was
entered.
15064
ENTRY FOR TYPE OF VICTIM MUST BE "I" OR "L" WHEN THIS
OFFENSE CODE IS CONNECTED TO THIS VICTIM
Data Element 24 (Offense Connected to Victim Sequence Number)
is connected to a "Crime Against Person," but Data Element 25
(Type of Victim) was not "I" = Individual or "L" = Law Enforcement
Officer.
15065
ENTRY FOR TYPE OF VICTIM MUST BE "S" WHEN THIS OFFENSE
CODE IS CONNECTED TO THIS VICTIM
Data Element 24 (Offense Connected to Victim Sequence Number)
is connected to a "Crime Against Society," but Data Element 25
(Type of Victim) was not "S" = Society.
15066
OFFENSE MUST BE SUBMITTED AS SEGMENT 20 RECORD IF
VICTIM IS CONNECTED
Each Victim Sequence Number entered into Data Element 24
(Offense Connected to Victim Sequence Number) must have the
Victim Sequence Number for the data value. In this case, the
Offense was connected to a Victim Sequence Number that was
not submitted. An Offense cannot be connected to a Victim
Sequence Number when the Victim Segment is not present.
ERROR NUMBERS AND MESSAGES
135
Print Date: March 7, 2016
RELEASE 2.1
15067
ENTRY FOR TYPE OF VICTIM CANNOT BE "S" WHEN THIS
OFFENSE CODE IS CONNECTED TO THIS VICTIM
Data Element 24 (Offense Connected to Victim Sequence Number)
is connected to a "Crime Against Property," but Data Element 25
(Type of Victim) was "S" = Society. This is not an allowable code
for "Crime Against Property" offenses.
15068
RELATIONSHIP CANNOT BE ENTERED WHEN RELATED TO
OFFENDER NUMBER "000"
Data Element 35 (Relationship of Victim to Offender) cannot be
entered when the number of offenders in Data Element 34
(Offender Number to be Related) is zero. Zero means that the
number of offenders was unknown; therefore, the relationship
cannot be entered.
15069
VICTIM SEX MUST BE "M" OR "F" FOR AN 11A OR 36B OFFENSE
Data Element # 27 (Sex of Victim) must be "M" = Male or "F" =
Female to be connected to offense codes of "11A" = Forcible
Rape and "36B" = Statutory Rape.
15070
WHEN "VO" RELATIONSHIP IS PRESENT, MUST HAVE TWO OR
MORE VICTIMS AND OFFENDERS
Data Elements 35 (Relationship of Victim to Offenders) had a
relationship of "VO" = Victim Was Offender. When this code is
entered, a minimum of 2 victim and 2 offender segments must be
submitted. In this case, only 1 victim and/or 1 offender segment
was submitted.
Because "VO" was entered on one or more of the victims, this
indicates situations such as brawls and domestic disputes. In the
vast majority of cases, each victim is also the offender; therefore,
every victim record 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) are not also the offender(s).
15071
ONLY ONE "VO" RELATIONSHIP PER VICTIM
ERROR NUMBERS AND MESSAGES
136
Print Date: March 7, 2016
RELEASE 2.1
Data Element 35 (Relationship of Victim to Offenders) had
relationships of "VO" = Victim Was Offender that pointed to multiple
offenders, which is an impossible situation. A single victim cannot
be 2 offenders.
15072
WHEN OFFENDER AGE/SEX/RACE ARE UNKNOWN, RELATIONSHIP
MUST BE "RU" = UNKNOWN
Data Element 35 (Relationship of Victim to Offender) had a
relationship to the offender that was not logical. In this case, the
offender was entered with "unknown" values for age, sex, and race.
Under these circumstances, the relationship must be entered as
"RU" = Relationship Unknown.
15074
ONLY ONE "VO" RELATIONSHIP CAN BE ASSIGNED TO A SPECIFIC
OFFENDER
Two or more Victim Segments had Data Element 35 (Relationship
of Victim to Offender) with a relationship of "VO" = Victim Was
Offender that pointed to the same offender.
15075
ONLY ONE "SE" RELATIONSHIP PER VICTIM
A Victim can only have one spousal relationship. In this
instance, the victim has a relationship of SE = Spouse to two
or more offenders.
15076
ONLY ONE "SE" RELATIONSHIP CAN BE ASSIGNED TO A SPECIFIC
OFFENDER
An Offender can only have one spousal relationship. In this
instance, two or more victims have a relationship of SE =
Spouse to the same offender.
15077
INVALID AGGRAVATED ASSAULT/HOMICIDE CIRCUMSTANCES
AND LAW ENFORCEMENT OFFICERS KILLED/ASSAULTED (IN THE
LINE OF DUTY) TYPE OF ASSIGNMENT FOR THIS LRS CODE
An Offense Segment was submitted with Data Element 24
(Offense Connected to Victim Sequence Number) having an
offense that did not have a permitted code for Data Element 31
ERROR NUMBERS AND MESSAGES
137
Print Date: March 7, 2016
RELEASE 2.1
(Aggravated Assault/Homicide Circumstances and Law
Enforcement Officers Killed/Assaulted (in the line of duty)
Type of Assignment). Only those circumstances listed in LIBRS
Guidelines and Specifications (Data Element and Data Values) are
valid for the particular offense.
15078
VICTIM CONNECTED TO AN INVALID COMBINATION OF OFFENSES
"Mutually Exclusive" offenses are ones that cannot occur to the
same victim by UCR definitions. 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:
A) Murder - Aggravated Assault, Simple Assault, and Intimidation
are all lesser included offenses of Murder. Negligent
Manslaughter is mutually exclusive.
B) Aggravated Assault - Simple Assault and Intimidation are
lesser included offenses of Aggravated Assault.
Note: Aggravated Assault is a lesser included offense of
Murder, Forcible Rape, Forcible Sodomy, Sexual Assault with
an Object, and Robbery.
C) Simple Assault - Intimidation is a lesser included offense of
Simple Assault.
Note: Simple Assault is a lesser included offense of Murder,
Aggravated Assault, Forcible Rape, Forcible Sodomy, Sexual
Assault with an Object, Forcible Fondling, and Robbery.
D) Intimidation - Intimidation is a lesser included offense of
Murder, Aggravated Assault, Forcible Rape, Forcible Sodomy,
Sexual Assault with an Object, Forcible Fondling, and Robbery.
E) Negligent Manslaughter - Aggravated Assault, Simple Assault,
and Intimidation are mutually exclusive offenses. Negligent
Manslaughter involves "...the killing of another person through
negligence." The Assault offenses are characterized by...
"unlawful attacks." Murder is mutually exclusive.
ERROR NUMBERS AND MESSAGES
138
Print Date: March 7, 2016
RELEASE 2.1
F) Forcible Rape - Aggravated Assault, Simple Assault,
Intimidation, and Forcible Fondling are lesser included offenses
of Forcible Rape.
Incest and Statutory Rape are mutually exclusive offenses and
cannot occur with Forcible Rape. The prior two offenses
involve consent, while the latter involves forced action against
the victim's will.
G) Forcible Sodomy - Aggravated Assault, Simple Assault,
Intimidation, and Forcible Fondling are lesser included offenses
of Forcible Sodomy.
Incest and Statutory Rape are mutually exclusive offenses and
cannot occur with Forcible Sodomy. The prior two offenses
involve consent, while the latter involves forced action against
the victim's will.
H) Sexual Assault with an Object - Aggravated Assault, Simple
Assault, Intimidation, and Forcible 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 the latter involves forced action
against the victim's will.
I)
Forcible Fondling - Simple Assault and Intimidation are lesser
included offenses of Forcible Fondling.
Incest and Statutory Rape are mutually exclusive offenses and
cannot occur with Forcible Fondling. The prior two offenses
involve consent, while the latter involves forced action against
the victim's will.
Note: Forcible Fondling is a lesser included offense of Forcible
Rape, Forcible Sodomy, and Sexual Assault with an Object.
J)
Incest - Forcible Rape, Forcible Sodomy, Sexual Assault with
an Object, and Forcible Fondling are mutually exclusive
offenses. Incest involves consent, while the four above-listed
offenses involve forced sexual relations against the victim's will.
ERROR NUMBERS AND MESSAGES
139
Print Date: March 7, 2016
RELEASE 2.1
K) Statutory Rape - Forcible Rape, Forcible Sodomy, Sexual
Assault with an Object, and Forcible Fondling are mutually
exclusive offenses. Statutory Rape involves consent, while the
four above-listed offenses involve forced sexual relations
against the victim's will.
L) Robbery - Aggravated Assault, Simple Assault, Intimidation,
and all theft offenses (including Motor Vehicle Theft) are lesser
included offenses of Robbery.
ERROR NUMBERS AND MESSAGES
140
Print Date: March 7, 2016
RELEASE 2.1
ERROR NUMBERS AND MESSAGES
141
Print Date: March 7, 2016
RELEASE 2.1
The following chart shows the LIBRS offenses that cannot occur to the same victim in the same incident. Each "X" on
the chart where offenses intersect denotes that those two offenses cannot occur to the same victim in an incident .
09A--Murder
X
X
X
X
X
09B--Negligent Manslaughter
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
120--Robbery
X
X
X
X
X
X
X
X
13A--Aggravated Assault
X
X
X
X
X
13B--Simple Assault
X
X
X
X
X
X
X
X
X
X
13C--Intimidation
X
X
X
X
X
X
X
X
X
X
23A--Pocket-Picking
X
23B--Purse Snatching
X
23C--Shoplifting
X
23D--Theft from Building
X
23E--Theft from Coin Machine
X
23F--Theft from Motor Vehicle
X
23G--Theft of Motor Vehicle Parts
X
23H--All Other Larceny
X
240--Motor Vehicle Theft
X
X
X
X
X
X
X
X
X
X
ERROR NUMBERS AND MESSAGES 142
Print Date: March 7, 2016
RELEASE 2.0
142
36B--Statutory Rape
X
36A--Incest
09C Justifiable Homicide cannot occur
with any other offense.
X
240--Motor Vehicle Theft
X
X
X
13B--Simple Assault
X
X
X
13A--Aggravated Assault
X
X
X
120--Robbery
X
X
X
11D--Forcible Fondling
36B--Statutory Rape
11C--Sexual Assault w/ Object
X
11B--Forcible Sodomy
X
11A--Forcible Rape
X
09B--Negligent Manslaughter
X
09A--Murder
36A--Incest
X
23G--Theft of Motor Vehicle
Parts
23H--All Other Larceny
X
23F--Theft from Motor Vehicle
X
23E--Theft from Coin Machine
11D--Forcible Fondling
23D--Theft from Building
11C--Sexual Assault w/ Object
23C--Shoplifting
X
23B--Purse Snatching
11B--Forcible Sodomy
23A--Pocket-Picking
X
13C--Intimidation
11A--Forcible Rape
ERROR NUMBERS AND MESSAGES
143
RELEASE 2.1
Print Date: March 7, 2016
ERROR NUMBERS AND MESSAGES
144
RELEASE 2.1
Print Date: March 7, 2016
15079
SIMPLE ASSAULT ("13B") CANNOT HAVE "MAJOR INJURIES"
A Simple Assault ("13B") was committed against a victim but the
victim had major injuries/trauma entered for Data Element 33 (Type
Injury). Either the offense should have been classified as an
Aggravated Assault ("13A") or the victim's injury should not have
been entered as major. The permissible codes for a Simple Assault
("13B") are "M" = Apparent Minor Injury and "N" = None.
15080
WHEN HOMICIDE/ASSAULT (DATA ELEMENT 31) IS "08," INCIDENT MUST
HAVE 2 OR MORE OFFENSES
Data Element 31 (Aggravated Assault/Homicide Circumstances and
Law Enforcement Officers Killed/Assaulted (in the line of duty) Type
of Assignment) had "08" = Other Felony Involved but the incident only
had one offense entered for Data Element 6 (LRS Offense Code). There
must be multiple offenses involved when the circumstance code is 08.
This edit was formerly error number 15040, a warning message. It is now
a fatal error.
15081
VICTIM'S AGE MUST BE LESS THAN [maximum for state] FOR
STATUTORY RAPE ("36B")
Among the states, the age at which a victim is considered a statutory rape
victim varies. The victim's age exceeded the maximum age possible for a
statutory rape in the state.
15096
EACH VICTIM SEQUENCE NUMBER ENTERED MUST HAVE A
CORRESPONDING VICTIM SEGMENT
ERROR NUMBERS AND MESSAGES
145
Print Date: March 7, 2016
RELEASE 2.1
ARRESTEE SEGMENT ERRORS
ERROR
NUMBER
MESSAGE
16001
MUST BE PRESENT -- MANDATORY FIELD
The data field must be entered; it is required.
16002
CONTAINS NONNUMERIC ENTRY
Data Element 40 (Arrestee Sequence Number) must be numeric
entry of 001 to 999 with zero left-fill.
16004
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within LIBRS Code Table.
16005
DATE ENTERED MUST BE A VALID CALENDAR DATE
Data Element 42 (Arrest Date) date components must be valid; that
is, months must be 01-12, days must be 01-31, and year must
include the century (i.e., 19xx, 20xx). In addition, days cannot
exceed maximum for the month (e.g., June cannot have 31 days).
Also, the date cannot exceed the current date.
The date cannot be later than that entered within the "Month of
Tape" and "Year of Tape" fields on the data record. For example, if
"Month of Tape" and "Year of Tape" are "06/1995," the date
entered cannot be 07/01/1995 or greater.
The error message will pinpoint what error occurred. For example,
DAT11: MONTH EXCEEDS 12 AND DAT14: DAY EXCEEDS 31
are some of the "date" error messages that are displayed.
16006
ERROR - DUPLICATE VALUE=[value]
Data Element 46 (Arrestee Was Armed With) contains multiple data
values. When more than one code is entered, none can be
duplicate codes.
16007
ERROR - MUTUALLY EXCLUSIVE VALUE=[value]
Data Element 46 (Arrestee Was Armed With) can have multiple
data values and was entered with multiple values. However, the
entry shown between the brackets in [value] above cannot be
entered with any other data value.
ERROR NUMBERS AND MESSAGES
146
Print Date: March 7, 2016
RELEASE 2.1
16008
EXACT AGE MUST BE IN FIRST TWO POSITIONS
Data Element 47 (Age of Arrestee) contained data, but was not leftjustified. A single 2-character age must be in positions 1-2 of the
field.
16009
ESTIMATED AGE MUST HAVE "E" IN LAST POSITION
Data Element 47 (Age of Arrestee) must be two (2) numeric digits,
and have a trailing "E" = Estimated.
16015
CANNOT HAVE EMBEDDED "BLANKS" BETWEEN FIRST AND LAST
NON-BLANK CHARACTERS
The data element in error contained embedded blanks between the
first and last significant characters.
16016
MUST BE LEFT JUSTIFIED -- BLANK DETECTED IN FIRST POSITION
Data Element 41 (Arrest Number/Local Booking Number for
Arrest) must be left-justified; one or more blanks were entered
starting in position 1 followed by the data.
16017
CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHEN
AND/OR BLANKS
Data Element 41 (Arrest Number/Local Booking Number for
Arrest) can only have character combinations of A-Z, 0-9, Hyphen,
and/or Blanks. For example, 89-123-SC is valid, but 89+123*SC is
invalid.
16020
ARREST DATE CANNOT PREDATE BASE DATE
Arrestee Segments (Segment 60) submitted with a Segment Action
Type of "W" = Time-Window Submission cannot have Data
Element 42 (Arrest Date) earlier than the Base Date.
This also applies to any subsequent "M" = Modify of a previously
submitted "W" = Time-Window Submission.
16021
JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE CODE
Arrestee Segments (Level 62) submitted with a Segment Action
Type of "W" = Time-Window Submission cannot have a LRS
Offense Code of "09C" = Justifiable Homicide. This is because by
ERROR NUMBERS AND MESSAGES
147
Print Date: March 7, 2016
RELEASE 2.1
definition a Justifiable Homicide never involves an arrest of the
offender (the person who committed the justifiable homicide).
This also applies to any subsequent "M" = Modify of a previously
submitted "W" = Time-Window Submission.
16022
ESTIMATED AGE CANNOT HAVE "00" = UNKNOWN
Data Element 47 (Age of Arrestee) was entered. Therefore, the
estimated age cannot be "00" = Unknown and have a trailing "E."
16040
WARNING - NO DISPOSITION FOR POSSIBLE JUVENILE ARRESTEE
Data Element 52 (Disposition of Arrestee Under 17) was not
entered, but Data Element 47 (Age of Arrestee) indicated an
age for a juvenile. Note that when an age is entered and the
age is a juvenile, then the disposition must be entered.
16041
WARNING - ARRESTEE HAD AN AGE OF 99 OR OLDER
Data Element 47 (Age of Arrestee) was entered with a value of 99
which means the arrestee was over 98 years old. Verify that the
submitter of data is not confusing the "99" = Over 98 Years Old with
"00" = Unknown.
16052
DISPOSITION MUST BE ENTERED WHEN AGE IS LESS THAN 17
Data Element 52 (Disposition of Juvenile) was not entered, but
Data Element 47 (Age of Arrestee) was under 17. Whenever an
arrestee's age indicates a juvenile, the disposition must be entered.
16053
FOR AGE GREATER THAN 16 DISPOSITION SHOULD NOT BE
ENTERED
Data Element 52 (Disposition of Juvenile) was entered, but Data
Element 47 (Age of Arrestee) was 17 or greater. Whenever an
arrestee's age indicates an adult, the juvenile disposition cannot be
entered because it does not apply.
16054
AUTOMATIC INDICATOR MUST BE BLANK OR "A"
Data Element 46 (Arrestee Was Armed With) did not have "A" =
Automatic or blank in the third position of field.
ERROR NUMBERS AND MESSAGES
148
Print Date: March 7, 2016
RELEASE 2.1
16055
WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN "A" IN THE
AUTO INDICATOR
In Data Element 46 (Arrestee Was Armed With), "A" = Automatic
was the third character of code. It is valid only with codes:
"11" = Firearm (Type Not Stated)
"12" = Handgun
"13" = Rifle
"14" = Shotgun
"15" = Other Firearm
A weapon code other than those mentioned was entered with the
"automatic" indicator. An automatic weapon is, by definition, a
firearm.
16056
THIS ARRESTEE EXCEEDED THE NUMBER OF OFFENDERS (nnn)
ON THE INCIDENT
An Incident Report was submitted with more arrestees than
offenders. The number (nnn) of offenders is shown within the
message. Resubmit the incident with additional Offender
Segments. This message will also occur if an arrestee was
submitted and Data Element 36 (Offender Sequence Number)
was "000" = unknown.
16057
VALID VALUES FOR WINDOW CLEARANCE INDICATOR ARE "Y" OR
"N"
Arrestee Segments (Segment 60) submitted with a Segment Action
Type of "W" = Time-Window Submission must have a "Y" or "N" in
the Window Clearance Indicator (position 101 of the Segment).
16058
MUST BE BLANK WHEN ACTION TYPE IS NOT "W" (WINDOW)
Arrestee Segments (Segment 60) submitted with a Segment Action
Type other than "W" = Time-Window Submission must have a
blank in the Window Clearance Indicator (position 101 of this
Segment) and no Arrestee Modification Segment (63) would be
submitted.
16059
AN OFFENSE MUST EXIST WHEN ACTION TYPE = "W" (WINDOW)
Arrestee Modification Segments (Segment 63) submitted with a
Segment Action Type of "W" = Time-Window Submission must
have at least one LRS Number entered in the Window Offense
Code Section (positions 25 - 36).
ERROR NUMBERS AND MESSAGES
149
Print Date: March 7, 2016
RELEASE 2.1
16060
INCIDENT REPORT NOT ON FILE
The initial Incident Number associated with the current submission
was not on the State's data base. The Arrestee Segment (Segment
60) submitted with a Segment Action Type of "A" = Add was
rejected because the incident was not on the State's data base.
16061
DUPLICATE ARRESTEE SEGMENT ON FILE -- ADDED ON
[mmddyyyy]
When an Incident Report or Segment Action Type of A = Add
[Arrestee] is submitted, the individual segments comprising the
incident cannot contain duplicates. In this case, two arrestee
segments have the same entry in Data Element 40 (Arrestee
Sequence Number).
16062
CANNOT DELETE AN ARREST WHEN INCIDENT REPORT ON FILE
A submission was made to delete an Arrest Segment from an
Incident Report currently active in the State's data base. The
request was rejected because Arrestee Segments (Segment 60)
submitted with a Segment Action Type of "D" = Delete must have
been previously submitted as a "W" = Time-Window Submission.
For some reason the participant's computer "thinks" that the State
has only "Time Window" arrest segments on file for the incident.
16063
CANNOT MODIFY AN ARREST WHEN INCIDENT REPORT ON FILE
A submission was made to modify an Arrest Segment on an
Incident Report currently active in the State's data base. The
request was rejected because Arrestee Segments (Segment 60)
submitted with a Segment Action Type of "M" = Modify must have
been previously submitted as a "W" = Time-Window Submission.
For some reason the participant's computer "thinks" that the State
has only "Time-Window" arrest segments on file for the incident.
16064
ARRESTEE AGE MUST BE NUMERIC DIGITS
Data Element 47 (Age of Arrestee) did not contain a numeric entry
of 00 - 99 for an exact age.
ERROR NUMBERS AND MESSAGES
150
Print Date: March 7, 2016
RELEASE 2.1
16065
ARREST DATE CANNOT BE BEFORE THE INCIDENT START DATE
Data Element 42 (Arrest Date) cannot be earlier than Data Element
3 (Incident Date/Hour). A person cannot be arrested before the
incident occurred.
16067
INVALID ARRESTEE SEX VALUE
Data Element 48 (Sex of Arrestee) did not contain a valid code of
"M" = Male or "F" = Female. Note that "U" = Unknown (if entered)
is not a valid sex for an arrestee.
16068
ARRESTEE RECORD PREVIOUSLY SUBMITTED WITH A "Y" IN THE
CLEARANCE BYTE
This error involves two or more Arrestee Segments (Level 60) in
the same incident, where two or more contained a "Y" in the
Window Clearance Indicator (position 101 of the Segment). Only
one of the arrests can have this indicator value of "Y."
These were submitted as "W" = Time-Window Submission
segments.
16069
NO ARRESTEE RECORDS ALLOWED FOR A JUSTIFIABLE
HOMICIDE
Incident Reports cannot have arrests when Data Element 6
(LRS Offense Code) is "09C" = Justifiable Homicide. This is
because by definition a justifiable homicide never involves an
arrest of the offender (the person who committed the
justifiable homicide).
16070
JUSTIFIABLE HOMICIDE CANNOT BE AN ARREST OFFENSE CODE
Data Element 45 (LRS Number of Arrest) was entered with "09C" =
Justifiable Homicide. This is not a valid arrest offense.
16080
SEGMENT 61 MISSING -- MUST HAVE ONE PER ARRESTEE
SEGMENT (LIBRS ONLY)
16081
SEGMENT 62 MISSING -- MUST HAVE AT LEAST ONE PER
ARRESTEE SEGMENT (LIBRS ONLY)
ERROR NUMBERS AND MESSAGES
151
Print Date: March 7, 2016
RELEASE 2.1
16099
SEGMENT 61 IS A REQUIRED SEGMENT WHEN SEGMENT 60
EXISTS (LIBRS ONLY)
ERROR NUMBERS AND MESSAGES
152
Print Date: March 7, 2016
RELEASE 2.1
SUBMISSION TRAILER SEGMENT ERRORS
19901
LAST LINE OR SEGMENT NOT 99 SEGMENT TYPE
19902
NUMBER OF SEGMENTS FIELD IN 99 SEGMENT IS NOT A VALID
NUMERIC FIELD
19903
NUMBER OF SEGMENTS ON SUBMISSION TRAILER DOES NOT
MATCH RECORD COUNT
ERROR NUMBERS AND MESSAGES
153
Print Date: March 7, 2016
RELEASE 2.1
LIBRS ERROR MESSAGES & EDITS
20000
MISSING SEGMENT 20 (OFFENSE)
Must have at least one offense for each incident.
20001
MUST BE PRESENT -- MANDATORY FIELD
This field must be present; it cannot be blank.
20002
INVALID DATA VALUE -- NOT ON LIBRS VALIDATION TABLE
The data within the referenced data element contains a value that
is not specified within LIBRS Code Table.
20004
SUBMISSION DATE MUST BE LATER THAN REPORTING PERIOD
Data Element C3 (Submission Date) must be later than Data
Element C4 (Reporting Period).
20010
MUST BE A VALID AGENCY
Data Element C2 (Submitting Agency) must be a valid agency.
20015
END OF SEGMENT MARKER EXPECTED -- END OF SEGMENT
MARKER NOT FOUND
Data Element C1 ( Segment Descriptor) must identify a segment of
proper length.
20025
DATE ENTERED MUST BE A VALID CALENDAR DATE
Each component of the date must be valid; that is, months must be
01-12, days must be 01-31, and year must include the century (i.e.,
19xx, 20xx). In addition, days cannot exceed maximum for the
month (e.g., June cannot have 31 days).
20026
REPORTING PERIOD CANNOT EXCEED THE DATE OF SUBMISSION
Data Element C4 ( Reporting Period) cannot be greater than Data
Element C3 (Submission Date).
ERROR NUMBERS AND MESSAGES
154
Print Date: March 7, 2016
RELEASE 2.1
20027
DATE OUT OF RANGE
20029
END OF SEGMENT MARKER, MUST BE EQUAL TO "ZZ"
Data Element C8(End of Segment Marker) must be equal to "ZZ".
20030
MUST BE 3 OR GREATER
Data Element C7 (Number of Segments Transferred) must be 3 or
greater.
20031
MUST BE EQUAL TO THE TOTAL NUMBER OF SEGMENTS WRITTEN
TO THE TAPE
Data Element C7( Number of Segments Transferred) must be
equal to the total number of Segments written to the tape.
20060
REPORTING PERIOD DATE CANNOT PRECEDE INCIDENT DATE
The state received an incident date that precedes the
Reporting Period Date (Data Element C4--MM/YYYY) being
submitted. This is an incident that has occurred in a future
month. An incident should not be reported during a reporting
period before it actually happened.
20200
MUST CONTAIN 12 NUMERIC PLACES.
If Data Element L53 (Location of Incident) is entered, the field must
contain 12 numeric places. No spaces are allowed.
22005
THIS LRS CODE MUST BE SUBMITTED WITH A SUBPART
This LRS code must be submitted with a subpart to identify
offense applicable.
22010
THIS LRS CODE MUST BE SUBMITTED WITH A SUBPART OR A
SUBPART WITH A QUALIFIER
This LRS code must be submitted with a subpart or a subpart
with a qualifier to define the offense applicable.
22015
WARNING-LRS SUBMITTED WITH A SUBPART AND NO QUALIFIER
ERROR NUMBERS AND MESSAGES
155
Print Date: March 7, 2016
RELEASE 2.1
This LRS was submitted with a subpart and no qualifier.
Check Master LIBRS/LRS Code Table to be sure the correct
offense is being reported.
22020
THIS LRS CODE MUST BE SUBMITTED WITH A QUALIFIER
This LRS must be submitted with a qualifier to identify offense
applicable.
22025
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS DRIVING UNDER THE INFLUENCE(90D)
If this LRS is submitted without a qualifier, it will be reported
as Driving Under the Influence (90D). If this is not the correct
offense, resubmit this LRS code with a qualifier.
22030
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS KIDNAPPING(100)
If this LRS is submitted without a qualifier, it will be reported
as Kidnapping(100). If this is not the correct offense, resubmit
this LRS code with a qualifier.
22035
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS PURSE-SNATCHING (23B)
If this LRS is submitted without a qualifier, it will be reported
as Purse-Snatching (23B). If this is not the correct offense,
resubmit this LRS code with a qualifier.
22040
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS A FAMILY OFFENSE NONVIOLENT (90F)
If this LRS is submitted without a qualifier, the offense will be
reported as Family Offense Nonviolent (90F). If this is not the
correct offense, resubmit this LRS code with a qualifier.
22045
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS ALL OTHER OFFENSE (90Z)
If this LRS is submitted without a qualifier, the offense will be
reported as All Other Offense (90Z). If this is not the correct
offense, resubmit this LRS with a qualifier.
ERROR NUMBERS AND MESSAGES
156
Print Date: March 7, 2016
RELEASE 2.1
22050
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER IS
REPORTED AS SIMPLE ASSAULT (13B)
If this LRS is submitted without a qualifier, the offense will be
reported as Simple Assault (13B). If this is not the correct
offense, resubmit this LRS with a qualifier.
22055
“WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER WILL BE
REPORTED AS ALL OTHER LARCENY-THEFT OFFENSE (23H)”. IF
THIS IS NOT THE CORRECT PROPERTY DESCRIPTION CODE,
RESUBMIT WITH CORRECT CODE
If LRS Code of 14:67 is submitted with no qualifier and DE # 15
is not equal to: "03", "05", "24", "28", "37", "38", or "04", then
the agency would receive a Warning Message.
22060
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE
#15 = "38" WILL BE REPORTED AS THEFT OF MOTOR VEHICLE
PARTS (23G). IF THIS IS NOT THE CORRECT PROPERTY
DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE
If LRS Code of 14:67 is submitted without a qualifier and
DE # 15 = "38", which equals Theft of Motor Vehicle Parts
(23G), then the agency would receive a Warning Message.
22065
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE
#15 = "03", "05", "24", "28", OR "37" WILL BE REPORTED AS
MOTOR VEHICLE THEFT (240). IF THIS IS NOT THE CORRECT
PROPERTY DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE
If LRS code of 14:67 is submitted without a qualifier and if DE
#15 = "03", "05", "24", "28", or "37", which equals Motor
Vehicle Theft (240), then the agency would receive this
Warning Message.
22070
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE
#15 = "04" WILL BE REPORTED AS THEFT OF A BICYCLE. IF THIS
IS NOT THE CORRECT PROPERTY DESCRIPTION CODE, RESUBMIT
WITH CORRECT CODE
If LRS code of 14:67 is submitted without a qualifier and DE
#15 = “04", which equals Theft of a Bicycle, then the agency
would receive this Warning Message.
ERROR NUMBERS AND MESSAGES
157
Print Date: March 7, 2016
RELEASE 2.1
22071
WARNING-THIS LRS SUBMITTED WILL BE REPORTED AS ALL
OTHER LARCENY-THEFT OFFENSE (23H). IF THIS IS NOT THE
CORRECT PROPERTY DESCRIPTION CODE, RESUBMIT WITH
CORRECT CODE.
If this LRS code of 14:68 is submitted and if DE #15 is not
equal to: “03", “05", “24", “28", or “37", then the agency would
receive this warning message.
22072
WARNING-THIS LRS SUBMITTED AND DE#15 = “03", “05", “24",
“28", OR “37" WILL BE REPORTED AS MOTOR VEHICLE
THEFT(240). IF THIS IS NOT THE CORRECT PROPERTY
DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE.
If LRS code of 14:68 is submitted and if DE #15 = “03", “05",
“24", “28", or “37", which equals Motor Vehicle Theft (240), the
agency would receive this warning message.
22075
MUST SUBMIT AN OFFENSE SEGMENT (SEGMENT 20) FOR EACH
VICTIM
It is necessary to submit an Offense Segment for each victim
in order to connect each offense to each Victim. Each Offense
Segment 20 has information on which Offense is connected to
Victim Sequence Number; this is the link between each
Offense and each Victim. If there is more than one Victim in an
Incident, each Victim must have an Offense Segment 20 to
identify which Offense they are connected to.
22080
SEGMENT 51 MISSING -- MUST BE PRESENT IF VICTIM TYPE IS “I”
OR “L” (LIBRS ONLY)
If Victim Type is “I” = Individual or “L” = Law Enforcement Officer,
Segment 51 must be present.
22081
SEGMENT 52 MISSING -- MUST BE PRESENT IF VICTIM TYPE IS “I”
OR “L” (LIBRS ONLY)
If Victim Type is “I” = Individual or “L” = Law Enforcement Officer,
Segment 52 must be present.
22085
IF LRS CODE APPENDED WITH "-A", "-C", "-I", "-S" , OR "-H" , DE #7
MUST BE "C" = COMPLETED
If LRS code of this offense appended with "-A", "-C", "-I",
“-S", or “-H”, this means the offense was an Inchoate of the
principle LRS offense shown in the first ten digits of DE # 6
ERROR NUMBERS AND MESSAGES
158
Print Date: March 7, 2016
RELEASE 2.1
and DE # 45. These modifiers for the LRS Code should always
be considered as "Completed", even if the principle LRS
offense was not. The offender completed the conspiracy, even
if the offense itself was not completed by the offender
conspiring with.
22086
ONLY ONE DASH “ - “ ALLOWED PER LRS OFFENSE
22100
AGE MUST BE "01" - "16" FOR JUVENILE OFFENSES
When Juvenile Qualifiers are used the age must be “01" - “16"
for a JU:RUN - Runaway Offense (90I), JU:UNG - Ungovernable
(90C), JU:CUR - Curfew (90B), or JU:TRU - Truancy (90Z).
22105
AGE CANNOT BE UNKNOWN IF DATE OF BIRTH IS KNOWN
If the age of an arrestee at the time of arrest is reported as "00"
= unknown and DE # L47(Date of Birth of Arrestee) is also
reported, this incident would be rejected. If Date of Birth is
known, age cannot be unknown.
22110
VICTIM TYPE MUST BE "L" = LAW ENFORCEMENT OFFICER WHEN
USING THIS LRS CODE
Victim Type must be "L" = Law Enforcement Officer when
using LRS Code of 14:37.2.
22115
MUST BE PRESENT IF LRS CHARGE OF ARREST IS A FELONY
If Louisiana Revised Statute that the arrestee is charged
with at the time of an arrest (Data Element 45) is a felony, this
Data Element (Data Element L55) must have a valid code.
Indicator of “F” on the Master LIBRS/LRS Code Table indicates
which LRS codes are identified as felony charges.
22120
AGE DOES NOT INDICATE CHILD IS THE VICTIM CONNECTED TO
THIS OFFENSE
If Data Element 31 is "40" = Child Abuse, then the victim that
is connected to this offense must have an age that equals
"NN," "NB," "BB," "01-16," or "01-16" with a trailing E.
22125
WARNING-THIS LRS SUBMITTED WITHOUT A QUALIFIER WILL BE
REPORTED AS MURDER AND NONNEGLIGENT MANSLAUGHTER
(09A)
ERROR NUMBERS AND MESSAGES
159
Print Date: March 7, 2016
RELEASE 2.1
If this LRS is submitted without a qualifier, the offense will be
reported as Murder and Nonnegligent Manslaughter (09A). If
this is not the correct offense, resubmit this LRS code with a
qualifier.
23001
ONLY ONE SEGMENT 30 PER INCIDENT PER TAPE ALLOWED
23201
SECOND CHARACTER MUST BE "X" OR BLANK
When Data Element 20 (Suspected Drug Type) is entered, the
second character must be "X" or Blank.
23210
DECIMAL POINT EXPECTED BUT NOT FOUND
23220
DE # 18 MUST BE BLANK IF OFFENSE NOT EQUAL TO 240
Data Element # 18 must be left blank if the LRS Offense is not
reported as a Motor Vehicle Theft (240) or hard coded edit
based on Data Element # 15 (Property Description) does not
list one of the following Motor Vehicle codes as Stolen
property: “03", “05", “24", “28" or “37"
23230
DE # 19 MUST BE BLANK IF OFFENSE NOT EQUAL TO 240
Data Element # 19 must be left blank if the LRS Offense is not
reported as a Motor Vehicle Theft (240) or hard coded edit
based on Data Element # 15 (Property Description) does not
list one of the following Motor Vehicle codes as Recovered
property: “03", “05", “24", “28" or “37"
24001
MUST BE UNIQUE -- CANNOT BE DUPLICATED
24010
AGE CANNOT BE ESTIMATED IF DATE OF BIRTH AND INCIDENT
DATE IS KNOWN
Age cannot be an estimate if Data Element L37 (Date of Birth of
Offender) is entered, and Data Element 3 (Incident Date/Hour) is an
actual Incident Date (i.e., not a "R" Report Date).
24030
DATE ENTERED MUST BE A VALID CALENDAR DATE
Each component of the date must be valid; that is, months must be
01-12, days must be 01-31, and year must include the century (i.e.,
19xx, 20xx). In addition, days cannot exceed maximum for the
ERROR NUMBERS AND MESSAGES
160
Print Date: March 7, 2016
RELEASE 2.1
month (e.g., June cannot have 31 days). The data cannot be
greater than that entered within the "Month of Tape" and "Year of
Tape" fields on the data record. For example, if "Month of Tape"
and "Year of Tape" are "06/1995," the date of birth cannot contain
any date 07/01/1995 or greater.
24031
MUST BE BEFORE INCIDENT DATE AND HOUR
Data Element L37(Date of Birth of Offender) must be before Data
Element 3 (Incident Date/Hour).
25001
DUPLICATE OFFENSE SEGMENT ON TAPE
When an Incident Report is submitted, the individual segments
comprising the incident cannot contain duplicates. In this case, 2
Offense Segments were submitted having the same entry in Data
Element L6 (Offense Sequence Number).
25010
AGE CANNOT BE ESTIMATED IF DATE OF BIRTH AND INCIDENT
DATE IS KNOWN
Age cannot be an estimate if Data Element L26 (Date of Birth of
Victim) is entered, and Data Element 3 (Incident Date/Hour) is an
actual Incident date (i.e., not a "R" Report date).
25020
CONFLICT EXISTS BETWEEN VICTIM DATE OF BIRTH AND VICTIM
AGE
25030
DATE ENTERED MUST BE A VALID CALENDAR DATE
Each component of the date must be valid; that is, months must be
01-12, days must be 01-31, and year must include the century (i.e.,
19xx, 20xx). In addition, days cannot exceed maximum for the
month (e.g., June cannot have 31 days). The date cannot be
greater than that entered within the "Month of Tape" and "Year of
Tape" field on the data record. For example, if "Month of Tape" and
"Year of Tape" are "06/1995," the date of birth cannot contain any
date 07/01/1995 or greater.
25031
MUST BE ON OR BEFORE INCIDENT DATE AND HOUR
Data Element L26 (Date of Birth of Victim) must be on or before
Data Element 3 (Incident Date/Hour).
25202
DUPLICATE VICTIM SEQUENCE NUMBERS FOUND
ERROR NUMBERS AND MESSAGES
161
Print Date: March 7, 2016
RELEASE 2.1
26001
DUPLICATE ARRESTEE SEGMENT ON FILE -- ADDED ON
[mmddyyyy]
When an Incident Report or Segment Action Type "A" = Add
[Arrestee] is submitted, the individual segments comprising the
incident cannot contain duplicates. In this case, 2 arrestee
segments had the same entry in Data Element 40 ( Arrestee
Sequence Number).
26010
AGE CANNOT BE ESTIMATED IF DATE OF BIRTH IS KNOWN
If the age is reported with a trailing "E" = Estimated Age in DE
#47 (Age of Arrestee at the time of arrest) and the agency also
reports Date of Birth of Arrestee (DE # L47), this incident
would be rejected. If Date of Birth is known, Age cannot be
estimated.
26201
ARREST CONNECTION TO OFFENSE CANNOT BE FOUND
26202
ARREST CONNECTION TO OFFENSE FOUND DUPLICATE OFFENSE
SEQUENCE NUMBERS (DATA ELEMENT L45)
ERROR NUMBERS AND MESSAGES
162
Print Date: March 7, 2016
RELEASE 2.1