Register of Vehicle Operating Records (SK only)

Automatic sending of information about the vehicle's mileage to the Register of Vehicle Operating Records, according to the applicable Slovak legislation.
Mandatory information (VIN, number of km) and additional information (Registration number of the vehicle, Registration number, Commercial name of the vehicle, Date of first registration) are sent to RPZV only for vehicles that will have the flag Used Financed Object = YES in the OC and the Send to RPZV = YES field in the Group of Catalogue Cards table.

Sending is carried out by:

• When updating the number of km or the number of the body – manually by the user via the Send to RPZV button

Sending data to RPZV from the Financed Object Card

The send button is located on the item card in the Actions tab and is active only if the detailed contract status in the "Send to RPZV" field has value = YES

When sending, the OC will check whether the financed object meets the following parameters:

• The group of the catalogue card of the financed object has the value = YES in the field "Send to RPZV" and

• Does the Financed Object field Used Financed Object (19014) have a value = YES

If the object meets these conditions, the OC continues to check the mandatory fields before sending it

• Chassis No. (VIN) of the financed object

• Initial Mileage from Financed Object

If the fields are not filled in, the OC will display the following error messages:

• "The Chassis No. (VIN) field must have a value (Must not be zero or empty) in the Financed Object table: Number = XY"

• "The Initial Mileage field must have a value (Cannot be zero or empty) in the table Financed Object: Number = XY"

Note (XY... = contract number)

If the fields are filled in (the value in the field < > 0), the process will be as follows:

• OC creates an entry in the RPZV Query Log

• Using webservice, it sends a query to RPZV

• If it is set in OC Check VIN on the RPZV Settings tab and the entered VIN is not correct, the OC will display the following return messages:

  • "The VIN number is not correctly decoded or is not in the database. Please check the first 9 characters of the VIN number."

  • "The calculation of the checked digit is not OK, the vehicle with the given VIN was not manufactured. Check the documentation and/or the vehicle."
    and at the same time writes the message to the RPZV log. After confirming OK on the message, OC will display the message:

  • "Successfully sent to RPZV."

• If it is set in OC Check KM on the RPZV Settings tab and the entered KM are not within the tolerance that the register allows, the OC will display a return message:

  • "The entered KM is not in accordance with the register."
    and writes the message to the RPZV log. After confirming OK on the message, OC will display the message:

  • "Successfully sent to RPZV."

• If the object meets the parameters, the data is sent to the registry and the system writes the response to the RPZV Log and displays the message:

  • "Successfully sent to RPZV."

• If an attempt is made to send the same number of km twice, the system writes the management to the RPZV log and displays the return message:
  o "Error sending to RPZV: Duplicate record."

RPZV Log

The log can be displayed from the item card in the Related tab.

After clicking, the system opens the RPZV log, which is filtered to the given number of the financed object. Data about sending to the RPZV service are written into the table and at the same time responses from the RPZV service are written here.

Field:

• Financing Contract No

  • . The number of the financing contract on which the financed object for which the entry in the register was sent is located

• Financed Object No

  • . The number of the object for which the entry in the register was sent

• First Registration Date

  • The date of the first registration, which is extracted from the First Registration Date field from the Financed Object

• Object Handover Date

  • The object handover date that is retrieved from the Object Handover Date field from the Financed Object

• Date

  • Date of sending data to RPZV

• Time

  • The time at which the data were sent to RPZV

• Result

  • Information about whether the query submission was successful and whether an error was identified on the registry side in the data

  • . The result can have the following values:

    • Success

    • Error

• Error Description

  • Manage the result of the identified error on the registry side

• Chassis No. (VIN)

  • VIN No. of the Financed Object

• Kilometers The

  • number of km that is sent to the register, the information is downloaded from the Initial Mileage field from the Financed Object

• Created the

  • ID of the user who created the record, used the function to send the data to RPZV

• User Name

  • The user's first and last names are written according to the ID in the Created By field

• Error

  • message if the VIN number is incorrect

• Message 2

  • If KM Check is set, it will write here information if the KM value is in an interval that the register tolerates. If the specified km:

    • are not in the succession of the registry history, but are within the allowed interval,

      • it writes the message "The value is in the interval."

    • They are not in the sequence of the registry history, and at the same time they are not in the allowed interval

      • Writes the message "Registry non-compliance."

      • The user will also be notified of the discrepancy by a message

• Id

  • Unique record number assigned by the registry, which is sent to the registry in case of record update

• Entry No

  • . The sequential number of the record in the table.