Shipment authorization
List of errors that can occur in the AE register.
| Code | Error Description | Resolution |
|---|---|---|
| -3 | Driver 1 is not authorized | The registration of the professional profile of the chosen driver has not been released. You must select another driver, or check the status of their registration profile using the sgrConsultaPF or Clipas NET method, and if necessary request a profile search. |
| -4 | Driver 2 is not authorized | |
| -5 | It is not possible to use a trailer | A trailer license plate is being entered in the trailer fields, but the type of vehicle entered in the nrplacacavalo field does not allow the use of a trailer (e.g. truck). |
| -6 | It is necessary to inform the license plate of the trailer | Filling in the Trailer field has been configured as mandatory for the client. In this case, a trailer license plate must be entered. If there is no need to enter the trailer, the account manager should be asked to make a change to the risk management rule. |
| -7 | The trailer plate 1 is not a trailer | The vehicle is not registered as a Carreta vehicle type. To view the registered vehicle type, use the sgrConsultaVeic method. |
| -8 | Vehicle is not authorized | The vehicle is not registered. It is necessary to inform another vehicle, or check the registration status using the sgrConsultaVeic or Clipas NET method, and if necessary, request a new registration search. |
| -9 | Truck is not authorized | The truck's registration is not authorized. It is necessary to inform another trailer, or check the registration status using the sgrConsultaVeic or Clipas NET method and, if necessary, request a new registration search. |
| -10 | It is mandatory to inform the route | Filling in the Route field has been configured as mandatory for the customer. In this case, the desired route must be found using the sgrListRoutes method. The method requires an origin and destination city, so you need to check that these have been entered correctly. If you don't need to use a route, you should ask your account manager to make a change to the risk management rule. |
| -11 | For this trip, it is mandatory for the vehicle to have a tracking device on file | The risk management/logistics rule selected for the trip requires the vehicle to have tracking equipment on file. It is necessary to check the vehicle's registration using the sgrConsultaVeic method and update the data. |
| -12 | Risk Management Rule not found | It was not possible to find a risk management/logistics rule that matches the data sent to generate the AE. In this case, it must be validated that the products reported on the trip are within the list returned by the sgrListProducts method. The total value of the trip must be within a management rule registered with Opentech. |
| -13 | The value of the cargo is greater than that allowed in the Risk Management Rule | The total value of the cargo informed to generate the shipment authorization is greater than the total value of the insurance policy. If necessary, the account manager should be asked to change the value in the risk management rule. |
| -15 | There is no Risk Management Rule for the informed product | The indicated product is not included in any risk management/logistics rule or the informed value is higher or lower than the defined rules. If necessary, the account manager should be asked to change the risk management rule. |
| -20 | It is mandatory to enter the horse's license plate | The Horse field cannot be left blank. To perform a query for registered vehicles, you can use the sgrConsultaVeic method. |
| -21 | It is mandatory to enter a driver | The Driver 1 field cannot be left blank. The document (CPF) of a driver must be filled in. To perform a query for the registered professional, you can use the sgrConsultaPF. |
| -22 | It is compulsory to enter a customer | You must fill in the Customer field with their code. If you don't have this code, you can request it by emailing [email protected]. |
| -23 | It is mandatory to inform the carrier | You must fill in the Carrier field, with the code of the desired company returned by the sgrListaTransportadoras method. |
| -24 | It is mandatory to inform the city of origin | You must fill in the field referring to the city of origin, using the code returned by the sgrListCities method. |
| -25 | It is mandatory to enter the destination city | You must fill in the field for the destination city, using the code returned by the sgrListCities method. |
| -26 | The estimated end date/time is less than the estimated start date/time | The estimated end date of the trip must be equal to or greater than the estimated start date. |
| -27 | The estimated start date/time is invalid (15 minutes less than the current one) | It was not allowed in the GR rule to generate retroactive estimated start dates. It must be changed to a date/time that is greater than or up to 15 minutes before the current time. If you need to change the rule, you must ask your account manager. |
| -28 | The estimated start date/time is invalid (7 days greater than the current date) | It is not possible to enter trips with an estimated start date greater than 7 days from the current date. A closer date must be entered. |
| -29 | The estimated end date/time is invalid. (Trip duration greater than 60 days) | It is not possible to enter trips with an estimated end date greater than 60 days from the date entered for the estimated start date. |
| -30 | The Boarding Authorization could not be generated. Try again | This error may be caused by an incorrect parameter, the field to be corrected will be indicated in the returnDataset property. This means you need to check the parameters and run the method again. The error may also have been caused by a timeout or dropped connection. In this case, you should send the parameters, along with the issue time and customer code, to the following e-mail address: [email protected] so that the error can be validated. |
| -31 | City of origin not registered | No city was found with the code entered. You must fill in the field for the city of origin, using the code returned by the sgrListaCidades method. |
| -32 | Destination city not registered | No city was found with the code entered. The field for the destination city must be filled in, using the code returned by the sgrListCities method. |
| -33 | Carrier entered is invalid | No carrier was found with the code entered. The field must be filled in with the code returned by the sgrListaTransportadoras method. If the carrier itself is carrying out the integration, the customer code informed by Opentech can be passed in. |
| -34 | Route entered is invalid | No active route was found with the code entered. The desired route must be found using the sgrListRoutes method. |
| -35 | Tracking company entered is invalid | No tracking company was found with the code entered. The desired code must be consulted using the sgrListCompaniesTracking method. |
| -61 | City not registered | No city was found with the code entered. The city field must be filled in using the code returned by the sgrListaCidades method. |
| -80 | License plates entered are identical | The license plate entered for the horse or trailer is repeated. It is necessary to enter different license plates in each field. |
| -81 | Horse not registered | The vehicle/trailer entered has not been located. It must be registered, following the steps in VEHICLE CONSULTATION AND REGISTRATION. |
| -82 | Truck 1 not registered | |
| -83 | Truck 2 not registered | |
| -84 | Drivers entered are identical | The same driver has been entered in fields 1 and 2. Different documents must be entered for each field. |
| -85 | Driver 1 not registered | The driver entered has not been located. The driver must be registered following the steps in DRIVER CONSULTATION AND REGISTRATION. |
| -86 | Driver 2 not registered | |
| -87 | It is mandatory to select at least one stopover point | The stopover registration has been configured as mandatory for the client's risk management/logistics rule. The trip cannot be registered without having at least one point, and the information needed for registration is in the sgrPointTripSupport class. If there is no need to use stopping points, the account manager should be asked to make a change to the risk management rule. |
| -88 | Not allowed to use trailer 1 | The vehicle filled in the Horse field is not configured with the “horse” type. Therefore, the trailer cannot be filled in. If you need to fill in a trailer, you must select another vehicle, or check the vehicle's registration using the sgrConsultaVeic or Clipas NET method and update the data. |
| -89 | It is not allowed to use trailer 2 | |
| -90 | The Carreta 2 license plate is not a carreta | The vehicle entered in the Carreta 2 field is not registered with the correct type. It is necessary to enter a vehicle of the Carreta type. |
| -91 | There is a maintenance schedule for the Horse. It will not be possible to generate the Shipment Authorization. | The horse entered has been scheduled for maintenance. Another horse must be chosen for the trip. By consulting the vehicle using the sgrConsultaVeic method, you can check in advance that it is not undergoing maintenance. |
| -92 | There is a maintenance schedule for the truck. It will not be possible to generate the Shipment Authorization. | The trailer has been scheduled for maintenance. Another trailer must be chosen for the trip. By consulting the vehicle using the sgrConsultaVeic method, you can check in advance that it is not undergoing maintenance. |
| -93 | You must provide at least one document | You must provide at least one document in order to create the Shipment Authorization. If you don't need to fill in the documents, ask your account manager to change the registration. |
| -94 | Driver 1 is suspended | Informed driver is suspended. It is necessary to choose another driver, or check their registration profile using the sgrConsultaPF or Clipas.Net methods, which already tell you if the profile is under suspension. If necessary, you can request a profile search. |
| -95 | Driver 2 is suspended | |
| -96 | This operation is not allowed to use this tracking technology! | The tracking company is not linked to the client. You must search for another company using the sgrListCompaniesTracking method. If you have any questions about the companies released or a request to release a company, please contact your account manager. |
| -97 | Shipper entered is invalid | No shipper was found with the code entered. You must fill in the field with the desired company code returned by the sgrListaEmbarcadores method. In the case of Shipper, you can enter the code provided by Opentech. |
| -98 | Driver 1 not authorized, MOPP expiration date less than trip end date! | Driver informed has expired MOPP. It is necessary to choose another driver or update the registration via Clipas. If in doubt, ask your account manager for help. |
| -99 | Driver 2 not authorized, MOPP expiration date less than trip end date! | |
| -100 | Driver 1 does not have the required driver's license to drive the horse! | Driver informed does not have the required driver's license to drive a horse. It is necessary to choose another driver or change the registration via Clipas. If you have any questions, please ask your account manager for help. |
| -101 | Driver 2 does not have the CNH Category required to drive the Horse! | |
| -102 | Driver 1 does not have the Driver's License required to drive a vehicle with a trailer! | Driver informed does not have the Driver's License required to drive a vehicle with a trailer. It is necessary to choose another driver or change the registration via Clipas. If you have any questions, we recommend that you ask your account manager for help. |
| -103 | Driver 2 does not have the Driver's License Category required to drive a trailer! | |
| -104 | Driver 1's driver's license has expired or will expire before the trip is due to end! | Driver informed has or will expire before the trip is due to end. It is necessary to choose another driver or change the registration via Clipas. If you have any questions, we recommend that you ask your account manager for help. |
| -105 | Driver 2's driver's license has expired/or will expire before the trip is due to end! | |
| -106 | Trip already registered! | There is already a trip registered with the parameters entered. To register a new trip, you need to change the parameter values (driver code, vehicle code, etc.). |
| -107 | Informed city of origin is not the same as the city of origin of the route! | It is necessary to check that the selected route is correct and that the code of the city of origin of the route is the same as the code of the informed city of origin. To check this code, use the sgrListCitiesRoute method. |
| -108 | Destination city entered is not the same as the route's destination city! | The destination city code entered must be the same as the destination city code in the route record. To check this code, use the sgrListCitiesRoute method. |
| -109 | Truck 1 was not Informed | The Truck 2 field was filled in without having indicated the first truck. If only one trailer is to be entered, it must be entered in the Trailer 1 field. |
| -142 | The estimated start date/time is invalid. (6 hours less than the current time) | You must change it to a date/time that is greater than or up to 6 hours before the current time. |
| For this trip, it is mandatory that the second tracker exists in the vehicle's registration | A horse has been selected that does not have both trackers configured, as required by the GR rule. It is necessary to select another vehicle to make the trip. | |
| For this trip, it is mandatory that an electronic lure is created. | The electronic lure data has not been entered, as required by the customer's GR rule. It is necessary to fill in the lures parameter. | |
| For this trip, it is mandatory that there is XX quantity of electronic lures registered. | The required quantity of electronic lures has not been linked, as required by the customer's GR rule. It is necessary to fill in the lures parameter, respecting the defined minimum number of records |