LIBRS Specifications Documentation

This document contains information about the Segments, Data Elements, Requirements, Errors, and Warnings that LIBRS uses in the validation of Incident Data.


General Format


The LIBRS Flat File is a space-delimited file generated by following the requirements in this document. Each section of this document outlines individual Segments. Each Segment is an individual lines in the LIBRS Flat File that contain varying information about the incident. Those bits of information are bound by the LIBRS Data Elements and their definitions/available values.

The information from an RMS needs to be output to the LIBRS Flat File in the exact specifications that are listed in this document. If not, a number of errors will occur. These errors and their common causes and resolutions can be found on the Data Elements Defintions page.

In the event that no incident data is present for submission, the LIBRS Flat File should contain two Segments followed by a blank line (three lines in total):

Submission Header (00)


*** Indicated Cells are either New or Modified Data Elements beginning with LIBRS Spec 2.5 ***

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 00 1-2 2 N
C3 Submission Date 23-30 8 D
C2 Submitting Agency 3-22 20 A
C4 Reporting Period 31-36 6 D
C10 Software ID 37-41 5 A/N
C11 Software Version 42-51 10 A/N
C12 LIBRS Spec Indicator ***New*** 52-54 3 A/N
** Future Expansion Buffer 55-56 2 A
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** A/N


IMPORTANT: The LIBRS Spec Indicator, C12, is new to LIBRS 2.5, and indicates which LIBRS Specification is to be used by WinLIBRS when validating a data submission. Only two values are accepted: “2.5” or “2.2” indicating the data being submitted conforms to LIBRS Spec 2.5 or 2.2.


Segment 00 Errors and Explanations

Error Number Error Message Explaination of Error
10090 ZERO - REPORTING MONTH IS NOT 01 - 12 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 Segment 00 did not have four numeric digits in positions 33-36.
10093 ZERO - REPORTING MONTH / YEAR WAS PRIOR TO THE ‘BASE DATE’ The month and year entered into positions 31-36 was later than the “Month of Submission” and “Year of Submission” entered into positions 23-30.
10094 ZERO - REPORTING MONTH / YEAR EXCEEDED MONTH / YEAR OF TAPE The month and year entered into positions 31-36 was later than the “Month of Submission” and “Year of Submission” entered into positions 23-30.
90038 INVALID LIBRS SPEC A Segment 00 with a Reporting Period year later than “2019” MUST have spec indicator “2.5” in the positions 52-54.


Administrative (10)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 10 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
L53 Location of Incident (Geographical Coordinates) 25-36 12 A/N
L54 Station/Division/Precinct Identifier 37-42 6 A
3 Incident Date/Hour 43-53 11 A
4 Cleared Exceptionally 54 1 A
5 Exceptional Clearance Date 55-62 8 D
** Future Expansion Buffer 63-82 20 A
C8 End of Segment Marker 83-84 2 A
C9 Padding 85-150 ** A/N


Segment 10 Errors and Explanations

Error Number Error Message Explaination of Error
10055 CANNOT HAVE AN INITIAL INCIDENT RECORD WITHOUT STARTING WITH RECORD SEGMENT 10 First segment, after the Submission Header, in a data submission MUST be an Administrative Segment (10).
10075 MISSING A MANDATORY RECORD SEGMENT FOR A COMPLETE INCIDENT When an Action Type of Incident Report (‘I’) is submitted, the following segments MUST be included:
  • 10 - Administrative Segment
  • 20 - Offense Segment
  • 40 - Offender Segment
  • 41 - Offender Using Segment/Gaming Motivation
  • 50 - Victim Segment
One or more of these segments was missing.


Administrative Modification (11)


For Time-Window Submissions, ONLY.

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 11 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number 25-36 12 A
** Future Expansion Buffer 37-56 20 A
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** A/N


Segment 11 Errors and Explanations

Error Number Error Message Explaination of Error
11060 INCIDENT NOT ON FILE Administrative Segment (10 and 11) submitted with an Action Type of ‘M’ (MODIFY) must already be on file with ORI Number (Data Element No. 1) and Incident Number (Data Element No. 2).
11069 TIME WINDOW SEGMENT BEING MODIFIED MUST HAVE LOUISIANA REVISED STATUTE NUMBER Segment 11 does not have an LRS Number associated with it.


Offense (20)


*** Indicated Cells are either New or Modified Data Elements beginning with LIBRS Spec 2.5 ***

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 20 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
L6 Offense Sequence Number 25-27 3 N
6 Louisiana Revised Statute Number 28-39 12 A
7 Offense Attempted/Completed 40 1 A
24 Offense Connected to Victim Sequence Number 41-43 3 N
9 Location Type 44-45 2 N
10 Number of Premises Entered 46-47 2 A/N
11 Method of Entry 48 1 A
12 Type of Criminal Activity/Gang Information No. 1 49 1 A
12 Type of Criminal Activity/Gang Information No. 2 50 1 A
12 Type of Criminal Activity No. 3 51 1 A
13 Type of Weapon/Force Involved No. 1 52-54 3 A
13 Type of Weapon/Force Involved No. 2 55-57 3 A
13 Type of Weapon/Force Involved No. 3 58-60 3 A
N6 Agency Supplied NIBRS Code ***New*** 61-63 3 A
70 Inchoate ***New*** 64 1 A
** Future Expansion Buffer 65-80 16 A
C8 End of Segment Marker 81-82 2 A
C9 Padding 83-150 ** A/N


Note: Submit one Offense Segment for *each* LRS Code, and one for *each* Victim in an Incident.


Segment 20 Errors and Explanations

Error Number Error Message Explaination of Error
22075 MUST SUBMIT AN OFFENSE SEGMENT(SEGMENT 20) FOR EACH VICTIM Each victim must be tied to an offense.


Property (30)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 30 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
18 Number of Stolen Motor Vehicles 25-26 2 A/N
19 Number of Recovered Motor Vehicles 27-28 2 A/N
** Future Expansion Buffer 29-48 20 A
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** A/N


Segment 30 Errors and Explanations

Error Number Error Message Explaination of Error
10074 PROPERTY RECORD(SEGMENT 30 & 31) MUST EXIST WITH THIS OFFENSE Property Segments (30 and 31) must exist when an Incident Report (Action Type = ‘I’) is submitted with an Offense Segment (20) whose LRS is a ‘Crime Against Property’. Kidnaping (100), Gambling (39A thru 39D), or Drug/Narcotic (35A thru 35B) Offenses also have this same Property Segment requirement.
10076 PROPERTY RECORD(SEGMT 30 & 31) CANNOT EXIT WITH OFFENSES SUBMITTED Only offenses that are ‘Crimes Against Property’, Kidnaping (100), Gambling (39A thru 39D), or Drug/Narcotic (35A thru 35B) can be submitted with Property Segments.


Property Description (31)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 31 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
14 Type of Property Loss / Etc. 25 1 N
15 Property Description Type 26-27 2 A/N
16 Value of Property 28-36 9 N
17 Date Recovered 37-44 8 D
20 Suspected Drug Type 45-46 2 A
21 Estimated Drug Quantity 47-59 13 A/N
22 Type Drug Measurement 60-61 2 A
P1 Property Sequence Number 62-64 3 N
** Future Expansion Buffer 65-81 17 A
C8 End of Segment Marker 82-83 2 A
C9 Padding 84-150 ** A/N


Segment 31 Errors and Explanations

Error Number Error Message Explaination of Error
13043 WARNING - ‘280’ OFFENSE HAS ‘RECOVERED’ VEHICLE BUT ‘240’ DOESN’T SHOW ‘STOLEN’ When the same property is Stolen (Type of Property Loss = ‘7’) and Recovered (Type of Property Loss = ‘5’) within the same incident, then the two Property Description Segments (31) that are submitted must use the same property sequence number (P1).
90018 PROPERTY MUST HAVE A VALID RELATIONSHIP TO AT LEAST ONE OFFENSE All properties submitted within an incident MUST be related to at least one Offense.


Property Modification (32)


For Time-Window Submissions, ONLY.

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 32 1-2 2 N
C5 Action Type (“W” or “M”, only) 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number 25-36 12 A
** Future Expansion Buffer 37-56 20 A
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** A/N


Segment 32 Errors and Explanations

Error Number Error Message Explaination of Error
13071 GAMBLING, KIDNAPPING, AND CRIMES AGAINST PROPERTY ARE THE ONLY VALID OFFENSE A Time-Window submission (Action Type of ‘W’) or Modify submission (Action Type = ‘M’) was submitted for ‘Recovered Property’ on a Property Modification Segment (32).
When submitted, all LRS codes must be Crimes Against Property, Kidnaping (100), or Gambling (39A thru 39D). In this instance offense codes other than those mentioned were submitted.
13077 PROPERTY SEGMENT A - O - F ADDED ON [MMDDYYYY] RECOVERY DATE = [MMDDYYYY] Property Segment A-O-F (already on file) added on (MMDDYYYY) Recovery Date = (MMDDYYYY)


Property/Offense (33)

*** Indicated Cells are either New or Modified Data Elements beginning with LIBRS Spec 2.5 ***

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 33 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
P1R Property Sequence Number Reference ***Modified*** 25-27 3 A
L6R Offense Sequence Number Reference ***Modified*** 28-30 3 A
** Future Expansion Buffer 31-50 20 A
C8 End of Segment Marker 51-52 2 A
C9 Padding 53-150 ** A/N


The Property/Offense Segment is used to connect incident property (stolen, retrieved, etc.) to an offense. This connection, or relationship, is established using the Property Sequence Number (Data Element P1) and the Offense Sequence Number (Data Element L6).

This Segment *is optional* in the sense that if it is missing LIBRS will interpret properties to offenses automatically using a cross product (EG all offenses are associated with all properties). Depending on the Offenses in the Incident, this can cause LIBRS to infer properties to incompatible Offenses.

LIBRS uses the NIBRS Code of the Offenses to determine if it should apply properties to them to minimize the cases that this happens in. However, there are some NIBRS Codes that include both 'Crimes Against People' and 'Crimes Against Property' Offenses (EG: 13B Contains both LRS 14:35 (Simple Battery - Crime Against Person) as well as LRS 14:60 (Aggravated Burglary - Crime Against Property)) that break this assumption.

Successful Segment 33 Inference Example

An incident is submitted with a NIBRS 23H ‘Crime Against Property’ Offense, as well as a NIBRS 11A ‘Crime Against Person’ Offense, along with one or more properties that are intended to be linked to the 23H Offense. Since NIBRS 11A has no related Offenses that are a ‘Crime Against Property’, if Segment 33 is missing LIBRS knows that it should not apply the properties to the 11A Offense. As a result, LIBRS will only infer the properties to be related to the 23H Offense, successfully validating the Incident submission.

Unsuccessful Segment 33 Inference Example

An incident is submitted with a NIBRS 23H ‘Crime Against Property’ Offense, as well as a NIBRS 13B ‘Crime Against Person’ Offense, along with one or more properties that are intended to be linked to the 23H Offense. Since 13B has some offenses that are ‘Crime Against Property’, if Segment 33 is missing LIBRS cannot know that it shouldn’t apply the properties to the 13B Offense. As a result, LIBRS will interpret all properties to be related to all offenses, which in this case will throw validation errors.


Segment 33 Errors and Explanations

Error Number Error Message Explaination of Error
90023 DUPLICATE - A PRIOR PROPERTY OFFENSE SEGMENT ALREADY EXISTS WITH THE SAME SEQUENCE NUMBERS Each Property/Offense segment submitted MUST have UNIQUE COMBINATIONS of Property Sequence Number References (P1R) to Offense Sequence Number References (L6R).

Offenses are allowed to be related to many properties and properties are allowed to be related to many offenses.

However, Property/Offense segments CANNOT be submitted relating a single Property to a Single Offense multiple times, that is NO duplicate combinations of Sequence Numbers.


INVALID Combinations of NIBRS Offense Codes and Property Descriptions

There are a number of illogical combinations for various NIBRS Offense Codes (Data Element 6) having certain Property Descriptions (Data Element 15). For example, it is illogical for Purse Snatching (NIBRS Code 23B) to be connected to property having a Property Description data value of Aircraft (01) or Livestock (18).

The table below shows invalid combinations of NIBRS Offense Codes and Property Descriptions. X’s on this table represent that the combination of the Property Description and NIBRS Code are incompatible and should NOT be used together.

Invalid Property Descriptions 220 23A 23B 23C 23D 23E 23F 23G 23H 240
01   X X X            
03   X X X X X X X X  
04   X X              
05   X X X X X X X X  
12   X X X            
15   X X X            
18   X X X            
24   X X X X X X X X  
28   X X X X X X X X  
29 X X X X X X X X   X
30 X X X X X X X X   X
31 X X X X X X X X   X
32 X X X X X X X X   X
33 X X X X X X X X   X
34 X X X X X X X X   X
35 X X X X X X X X   X
37   X X X X X X X X  
39   X X X            
78   X X              


Offender (40)

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 40 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
36 Offender Sequence Number 25-27 3 N
37 Age of Offender 28-30 3 A
L37 Date of Birth of Offender (LIBRS Only) 31-38 8 D
38 Sex of Offender 39 1 A
39 Race of Offender 40 1 A
8A Bias Motivation / Bias Crime Type 41-42 2 A
39A Ethnicity of Offender 43 1 A
** Future Expansion Buffer 44-62 20 A
C8 End of Segment Marker 63-64 2 A
C9 Padding 65-150 ** A/N


Segment 40 Errors and Explanations

Error Number Error Message Explaination of Error
90008 FOR STATUTORY RAPE OFFENSES WHERE OFFENDER IS AT LEAST TWO YEARS BUT LESS THAN FOUR YEARS OLDER THAN THE VICTIM, THE ASSOCIATED OFFENSE IS REQUIRED TO BE REPORTED AS MISDEMEANOR CARNAL KNOWLEDGE OF A JUVENILE (14:80.1). A Statutory Rape (NIBRS Code 36B) MUST be classified as a MISDEMEANOR (LRS 14:80.1 Misdemeanor Carnal Knowledge of a Juvenile) if the Offender is at least two (2), but less than four (4) years older than the Victim.
90011 MISDEMEANOR CARNAL KNOWLEDGE OF A JUVENILE (14:80.1) OFFENSES ARE APPLICABLE ONLY WHEN THE OFFENDER IS AT LEAST TWO YEARS BUT LESS THAN FOUR YEARS OLDER THAN THE VICTIM A Statutory Rape (NIBRS Code 36B) MUST be classified as a FELONY (LRS 14:80 Carnal Knowledge of a Juvenile) if the Offender is four (4) or more years older than the Victim
90013 STATUTORY RAPE OFFENSES REQUIRE OFFENDERS TO BE AT LEAST TWO YEARS OLDER THAN THEIR VICTIMS The Offender must be two years older than the Victim in order for the offense to qualify as Statutory Rape.


Offender Using/Gaming Motivation (41)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 41 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
36 Offender Sequence Number 25-27 3 N
8 Offender Suspected of Using / Gaming Motivation 28 1 A
** Future Expansion Buffer 29-48 20 A
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** A/N


Segment 41 Errors and Explanations

None



Victim (50)


*** Indicated Cells are either New or Modified Data Elements beginning with LIBRS Spec 2.5 ***

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 50 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
25 Victim Type 28 1 A
26 Age (At Time of Incident) 29-31 3 A
L26 Date of Birth (LIBRS Only) 32-39 8 D
27 Sex 40 1 A
28 Race 41 1 A
29 Ethnicity 42 1 A
30 Resident Status 43 1 A
31 Aggravated Assault / Homicide Circumstance No. 1 ***Modified*** 44-45 2 N
31 Aggravated Assault / Homicide Circumstance No. 2 ***Modified*** 46-47 2 N
31 Aggravated Assault / Homicide Circumstance No. 3 *No Longer In Use* 48-49 ~~2~~ ~~N~~
32 Additional Justifiable Homicide Circumstance ***Modified*** 50 1 A
25A Type of Officer Activity/Circumstance ***New*** 51-52 2 N
25B Officer Assignment Type ***New*** 53 1 A
25C Officer ORI, Other Jurisdiction ***New*** 54-62 9 A
** Future Expansion Buffer 63-68 6 A
C8 End of Segment Marker 69-70 2 A
C9 Padding 71-150 ** A/N


Segment 50 Errors and Explanations

None



Victim Injury (51)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 51 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
33 Injury Type 28 1 A
** Future Expansion Buffer 29-48 20 A
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** A/N


Segment 51 Errors and Explanations

Error Number Error Message Explaination of Error
22080 SEGMENT 51 MISSING–MUST BE PRESENT IF VICTIM TYPE IS ‘I’ OR ‘L’ Segment 51 must be present if Victim Type is ‘I’ (Individual) or ‘L’ (Law Enforcement Officer) and if offense is applicable.


Victim/Offender Relation (52)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 52 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
34 Offender Number to be Related 28-30 3 N
35 Relationship of Victim to Offender 31-32 2 A
** Future Expansion Buffer 33-52 20 A
C8 End of Segment Marker 53-54 2 A
C9 Padding 55-150 ** A/N


Segment 52 Errors and Explanations

Error Number Error Message Explaination of Error
22081 SEGMENT 52 MISSING–MUST BE PRESENT IF VICTIM TYPE IS ‘I’ OR ‘L’ Segment 52 must be present if Victim Type is ‘I’ (Individual) or ‘L’ (Law Enforcement Officer) and if offense is applicable.


Arrestee (60)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 60 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrest Sequence Number 25-27 3 N
41 Arrest Number/Local Booking Number for Arrest* 28-39 12 A
L55 Arrest Transaction Number 40-54 15 A/N
L40 Arrestee Name 55-74 20 A
42 Arrest Date 75-82 8 D
43 Arrest Type 83 1 A
44 Multiple Arrestee Segment Indicator 84 1 A
47 Age (At Time of Arrest) 85-87 3 A
L47 Date of Birth 88-95 8 D
48 Sex 96 1 A
49 Race 97 1 A
50 Ethnicity 98 1 A
51 Resident Status 99 1 A
52 Disposition of Arrestee Under 17 100 1 A
C6 Clearance Indicator (to be used for Time Window Submission only) 101 1 A
** Future Expansion Buffer 102-118 17 A
C8 End of Segment Marker 119-120 2 A
C9 Padding 121-150 ** A/N


Segment 60 Errors and Explanations

Error Number Error Message Explaination of Error
16058 MUST BE BLANK WHEN ACTION TYPE IS NOT ‘W’ (WINDOW) Clearance Indicator (DE C6) must be Blank (G) when Action Type is not ‘W’ (Time-Window).


Arrestee Armed (61)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 61 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrestee Sequence Number 25-27 3 N
46 Arrestee Armed With at Time of Arrest 28-30 3 A
** Future Expansion Buffer 31-50 20 A
C8 End of Segment Marker 51-52 2 A
C9 Padding 53-150 ** A/N


Segment 61 Errors and Explanations

None



Arrestee Statute (62)


*** Indicated Cells are either New or Modified Data Elements beginning with LIBRS Spec 2.5 ***

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 62 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrestee Sequence Number 25-27 3 N
45 Louisiana Revised Statute Number of Arrest 28-39 12 A
L45 Arrest Connection to Offense 40-54 15 A
N45 Agency Supplied NIBRS Code ***New*** 55-57 3 A
** Future Expansion Buffer 58-74 17 A
C8 End of Segment Marker 75-76 2 A
C9 Padding 77-150 ** A/N


Segment 62 Errors and Explanations

Error Number Error Message Explaination of Error
16060 INCIDENT REPORT NOT ON FILE The Incident Number associated with the current submission was not found in LIBRS database.
The Arrestee Segment submitted with an Action Type of ‘A’ (Add an Arrest) was rejected because the incident is not on the LIBRS database.


Arrestee Modification (63)


For Time Window Submissions, ONLY

Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 63 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number of Incident 25-36 12 A
** Future Expansion Buffer 37-56 20 A
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** A/N


Segment 63 Errors and Explanations

Error Number Error Message Explaination of Error
16059 AN OFFENSE MUST EXIST WHEN ACTION TYPE = ‘W’(WINDOW) LRS (6) MUST exist when Action Type is ‘W’ (Time-Window).


Submission Trailer (99)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 99 1-2 2 N
C7 Number of Segments Transferred 3-8 6 N
C8 End of Segment Marker 9-10 2 A
C9 Padding 11-150 ** A/N


Segment 99 Errors and Explanations

Error Number Error Message Explaination of Error
19901 LAST LINE OR SEGEMENT NOT 99 SEGMENT TYPE Last line in data submission NOT Segment Type 99 (Submission Trailer).
19902 NUMBER OF SEGMEMTS FIELD IN 99 SEGMENT IS NOT A VALID NUMERIC FIELD Number of Segments Transferred field (Data Element C7) in Submission Trailer is NOT a valid numeric field.
19903 NUMBER OF SEGMENTS ON SUBMISSION TRAILER DOES NOT MATCH RECORD COUNT Number of Segments Transferred (Data Element C7) in Submission Trailer Segment does not match Record Count for data submission.


Zero Record (01)


Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 01 1-2 2 N
2 Incident Number - All Zeroes "000000000000" 3-14 12 N
C8 End of Segment Marker 15-16 2 A
C9 Padding 17-150 ** A/N


Segment 01 Errors and Explanations

Error Number Error Message Explaination of Error
10092 ZERO - REPORTING INCIDENT NUMBER MUST BE ALL ZEROES A Segment 01 was submitted, but the Incident Number (Data Element 2) entered into positions 3-14 was not all zeroes.