SAFER Table Layout
SAFER Table Layout
SAFER Table Layout |
|
||
|---|---|---|---|
SAFER Table Layout |
|
||
Frequently Asked Questions
SAFER Error Codes Issued by XML Transactions
Error messages below, classified as terminal or warnings, are violations of SAFER business rules.
Each message has a code number, a text body (enclosed in quotes) and notes.
Error Messages - associated data not processed further
0 "Passed business rules"
Placeholder value for the code that actually writes out the messages;
code zero causes "Passed business rules" to appear in the log
1 "Older than existing data"
Record sent is older than existing data
2 "Duplicate records for a VIN and State"
A vehicle registration for the same VIN and state already exists
3 "Duplicate records for a State and License Plate"
A vehicle registration for the same license plate number and state
already exists in the database
4 "No proration record for vehicle reporting state"
Vehicle registration is lacking at least one proration record
5 "Duplicate keys within transaction"
Multiple records with the same key values were sent within a
single transaction
6 "Vehicle registration does not exist"
Transponder Id was sent for a vehicle that has no registration
7 "Referenced carrier record does not exist"
Carrier e-screen record references a non-existant carrier
8 "No country exists for jurisdiction in lookup table"
Vehicle inspection record references a country that is not listed
in the countries lookup table
9 "No street or PO Box information was provided in address"
IFTA, IRP, or FLEET transaction is lacking a street or PO box
10 "Existing PRISM registration cannot be updated by IRP"
An IRP vehicle registration cannot update an existing PRISM registration
11 "IFTA account for carrier already exists for jurisdiction"
IFTA License record is for a carrier that has an existing IFTA
registration within the same jurisdiction
12 "IRP account for carrier already exists for jurisdiction"
IRP Account record is for a carrier that has an existing IRP
registration within the same jurisdiction
13 "Multiple prorations found for intrastate IRP registration"
An intrastate vehicle registration may only send a proration for
the sending jurisdiction. The violating record sent multiple prorations.
14 "Transponder ID is already associated with another VIN"
Transponder ID already associated with another VIN.
15 "CARRIER_ACTION does not validate to the carrier-vehicle action lookup table"
Carrier-action does not exist in the database car_veh_action_lookup table
16 "JURISDICTION_ACTION does not validate to the jurisdiction action lookup table"
Jurisdiction-action does not exist in the jurisdiction_action_lookup table
17 "JURISDICTION_CODE/ACTIVITY_CODE combination does not validate to the
jurisdiction participation lookup table"
Jurisdiction-code/activity-code combination does not exist in
the jurisdiction_participation table
18 "Non-unique name-types within a base record group"
Non-unique name-type within base record group
19 "Non-unique address-types within a name group"
Non-unique address-type within name group
Warning Messages - associated data may be included in database
-1 "Referenced IFTA Account does not exist"
IFTA account referenced in IRP account record does not exist
-2 "Referenced IRP Account does not exist"
IRP account referenced in IRP Fleet record does not exist
-3 "Referenced IRP Fleet does not exist"
IRP fleet referenced in vehicle registration does not exist
Untrapped Database Messages in Log
If untrapped (caused by conditions unanticipated by the code) errors
occur, they usually emanate from the database. All Oracle-origin
error messages in the log cause the entire input file's data to be
rejected. All the messages have these common features:
"Error in SQL command: " where is the text of the SQL command
that caused the error.
"Error message: ORA-" where NNNNN is a 5-digit code that corresponds
to Oracle error condition numbers. The SQL text and error number are
important diagnostic tools that should be listed in the test result report.