Daily E-Crash Load Report - Revision history

Admin at 18:15, 4 December 2025

2025-12-04T18:15:53Z

← Older revision		Revision as of 14:15, 4 December 2025
Line 13:		Line 13:
	A typical load report looks like the one below.   "No rows selected" means that there were no load errors.   No action is needed by the agency.		A typical load report looks like the one below.   "No rows selected" means that there were no load errors.   No action is needed by the agency.

	Daily E-crash Load Report NEW FORMS - ~~Orlando~~ PD		Daily E-crash Load Report NEW FORMS - XXXXXX PD

	Daily E-crash Load Statistics for 23-Apr-2024		Daily E-crash Load Statistics for 23-Apr-2024

Admin: /* Load Errors */

2025-07-17T20:20:18Z

Load Errors

← Older revision		Revision as of 16:20, 17 July 2025
Line 59:		Line 59:
	:4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.		:4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		::HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

	:Check to verify that the crash that got rejected is indeed an update.   Once you have confirmed that the crash is an update, your agency administrator should forward the load email with the error to [mailto:crashrecords@flhsmv.gov crashrecords@flhsmv.gov].   Let them know that the crash is not a duplicate and request that they push it through as an update.   ''You must include what exactly was changed/updated.''   For instance, "The update changes the injury severity code from Incapacitating to Fatal." or "The agency case number and crash location have been changed."		:Check to verify that the crash that got rejected is indeed an update.   Once you have confirmed that the crash is an update, your agency administrator should forward the load email with the error to [mailto:crashrecords@flhsmv.gov crashrecords@flhsmv.gov].   Let them know that the crash is not a duplicate and request that they push it through as an update.   ''You must include what exactly was changed/updated.''   For instance, "The update changes the injury severity code from Incapacitating to Fatal." or "The agency case number and crash location have been changed."

Admin at 20:19, 17 July 2025

2025-07-17T20:19:41Z

← Older revision		Revision as of 16:19, 17 July 2025
Line 58:		Line 58:

	:4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.		:4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

Admin at 20:18, 17 July 2025

2025-07-17T20:18:41Z

← Older revision		Revision as of 16:18, 17 July 2025
Line 49:		Line 49:
	DUP_CHECK = this is a duplicate crash report		DUP_CHECK = this is a duplicate crash report

	This error occurs for the following reasons:		:This error occurs for the following reasons:

	1. The original report has already been submitted to HSMV.		:1. The original report has already been submitted to HSMV.

	2. The HSMV number has already been used by another agency.		:2. The HSMV number has already been used by another agency.

	3. An Update was submitted with no changes.		:3. An Update was submitted with no changes.

	4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.		:4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

Admin at 20:14, 13 September 2024

2024-09-13T20:14:12Z

← Older revision		Revision as of 16:14, 13 September 2024
Line 57:		Line 57:
	3. An Update was submitted with no changes.		3. An Update was submitted with no changes.

	4. The Update is submitted, but ~~the~~ changes ~~that are~~ made ~~cause~~ the system to think it's a completely different crash.		4. The Update is submitted, but several changes were made, causing the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

Admin at 20:12, 13 September 2024

2024-09-13T20:12:34Z

← Older revision		Revision as of 16:12, 13 September 2024
Line 59:		Line 59:
	4. The Update is submitted, but the changes that are made cause the system to think it's a completely different crash.		4. The Update is submitted, but the changes that are made cause the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   ~~This~~ DUP_CHECK error ~~happens~~ when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		:HSMV performs what they call a "sanity check" when reports are submitted.   The DUP_CHECK error may happen when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

	:Check to verify that the crash that got rejected is indeed an update.   Once you have confirmed that the crash is an update, your agency administrator should forward the load email with the error to [mailto:crashrecords@flhsmv.gov crashrecords@flhsmv.gov].   Let them know that the crash is not a duplicate and request that they push it through as an update.   ''You must include what exactly was changed/updated.''   For instance, "The update changes the injury severity code from Incapacitating to Fatal." or "The agency case number and crash location have been changed."		:Check to verify that the crash that got rejected is indeed an update.   Once you have confirmed that the crash is an update, your agency administrator should forward the load email with the error to [mailto:crashrecords@flhsmv.gov crashrecords@flhsmv.gov].   Let them know that the crash is not a duplicate and request that they push it through as an update.   ''You must include what exactly was changed/updated.''   For instance, "The update changes the injury severity code from Incapacitating to Fatal." or "The agency case number and crash location have been changed."

Admin: /* Load Errors */

2024-09-13T20:10:06Z

Load Errors

← Older revision		Revision as of 16:10, 13 September 2024
Line 48:		Line 48:

	DUP_CHECK = this is a duplicate crash report		DUP_CHECK = this is a duplicate crash report

			This error occurs for the following reasons:

			1. The original report has already been submitted to HSMV.

			2. The HSMV number has already been used by another agency.

			3. An Update was submitted with no changes.

			4. The Update is submitted, but the changes that are made cause the system to think it's a completely different crash.

	:HSMV performs what they call a "sanity check" when reports are submitted.   This DUP_CHECK error happens when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.		:HSMV performs what they call a "sanity check" when reports are submitted.   This DUP_CHECK error happens when enough has changed on a crash update that the HSMV system kicks it back as a duplicate instead of processing it as an update.

Admin: /* Load Errors */

2024-05-28T15:33:45Z

Load Errors

← Older revision		Revision as of 11:33, 28 May 2024
Line 70:		Line 70:

	OWNER_STATE = NO   NO is not a valid value		OWNER_STATE = NO   NO is not a valid value
	STATE_OF_REGISTRATION = NO is not a valid value		:NO was entered in the address State field for the Owner in the Vehicle section on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.
	:NO was entered in the State field on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.		:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.

			STATE = NO   NO is not a valid value

			:NO was entered in the address State field in the Driver, Passenger, or Non Motorist section section on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.
			:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.

			STATE_OF_REGISTRATION = NO   NO is not a valid value
			:NO was entered in the tag State field in the Vehicle section on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.
	:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.		:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.

Admin: /* Load Errors */

2024-05-28T15:26:37Z

Load Errors

← Older revision		Revision as of 11:26, 28 May 2024
Line 69:		Line 69:
	:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.		:Contact TraCS Support for assistance with getting the crash corrected and resubmitted.

	OWNER_STATE = NO NO is not a valid value		OWNER_STATE = NO   NO is not a valid value
	STATE_OF_REGISTRATION = NO is not a valid value		STATE_OF_REGISTRATION = NO is not a valid value
	:NO was entered in the State field on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.		:NO was entered in the State field on the crash.   NO is no longer a choice in the State field but you may see this error if the officer has completed an Update to an older crash report.

Admin: /* Load Errors */

2024-05-28T15:23:07Z

Load Errors

← Older revision		Revision as of 11:23, 28 May 2024
Line 60:		Line 60:
	:Contact TraCS Support for assistance with getting the original and update crashes submitted.		:Contact TraCS Support for assistance with getting the original and update crashes submitted.

	INJURY_SEVERITY = 4 4 is an invalid value for a short form crash report		INJURY_SEVERITY = 4   4 is an invalid value for a short form crash report
	:Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types.   If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially.   See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.		:Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types.   If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially.   See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.
	:If an officer updates a Short Form and changes the change the Injury Severity from None to any of the other injury types, it will be rejected by HSMV.		:If an officer updates a Short Form and changes the change the Injury Severity from None to any of the other injury types, it will be rejected by HSMV.