Integration with Seatruck Ferries added
Integration with Seatruck Ferries is now also available
This edi connection works via a webservice.
General improvements to crossing orders module
- Crossing orders has been added to the automatic "clean ups".
- For the Seatruck Ferries API, it was required to add a "category" to the crossing provider vehicle type codes. The category codes are defined in the $dd database, so it's not something you can change, but you will see the category being mentioned in the look up fields in Transpas. It will also be used in the Finnlines / Grimaldi connections (that was hard-coded at first).
- For the Relation reference kinds, a default "Reference type" has been added: "Destin8 badge".
Destin8 is a UK Port community system. A releation reference with type "Destin8 badge" can be used to define the 3-character Destin8 badge code of a relation. That code will be used in some crossing bookings, for the Nominated Agent and Release party. - If you change the Crossing Provider on a Crossing Provider Account, you will get an "Are you sure you want to change ..." question, to confirm your change.
This change might be required for an implementation of a new API for an existing connection. A trigger has beed added to CrossingProviderAccount for updating the technical numbers of the vehicle type code settings. - The table valued function dbo.FindCrossingOrder has been updated to facilitate changing from an old EDI to a new EDI for the same Crossing Provider Account.
Improvements P&O integration
Improvements to the P&O integration:
- Updated to API v40_1
- Multiple CHED / GGB references per consignment are now possible
- Added seal numbers into the customs information functionality. And document types for BE & NL departure.
- ICS2 changes have been implemented (Seller, Buyer, HSCode)
Improvements Eurotunnel integration
Improvements to the Eurotunnel integration:
- Multiple CHED / GGB references per shipment are now also possible.
- Improved the functionality to determine the country names. It now works via option table 23, without defining anything at the EDI Provider.
Improvements CLdN / Cobelfret integration
Improvements to the CLdN / Cobelfret integration:
- Updated to API version 17.8
- "Nominated Agent" can be specified for UK arrival bookings. This will be the Destin8 badge code (relation reference) of the Import customs broker.
- For unaccompanied bookings with UK arrival, the Destin8 badge code (relation reference) of the Release Haulier will also incuded in the booking.
- CLdN added new routes and as a consequence the requirements for VGM data changed. The booking action has been updated to facilitate this.
- ICS2 changes have been implemented
- Improved "HOLD" feedback descriptions
- Consignment references and CRN (for Belgium, if available) will become visible under "External shipment references"
- Improved status processing for "request rejected" feedback, including error info.
Improvements DFDS integration
Improvements to the DFDS integration
- "Clearing Agent" can be specified for UK arrival bookings. This will be the Destin8 badge code (relation reference) of the Import customs broker.
- All ICS2 additions have been implemented
Improvements Stena Line integration
Improvements to the Stena Line integration
- "Nominated Agent" can be specified for UK arrival bookings. This will be the Destin8 badge code (relation reference) of the Import customs broker.
Integration with the new Stena Line REST API added
In the new API, the necessary changes for ICS2 are integrated.
- It is a new API according to latest safety recommendations
- Arrival & Gate Exit statuses are now also available
- A new option has been added to the "External information" action, for listing active bookings in Stena Lines system (including references and vehicle descriptions).
Edit charter description for "begin" resources
It is now also possible to edit charter descriptions for "begin" resources via a right-mouse click, just as for "end" resources.
Improvements Finnlines / Grimaldi integration
Improvements to the Finnlines / Grimaldi integration
- Changed by Finnlines / Grimaldi: multiple drivers can now be sent in one booking. We also integrated this in Transpas.
- They also improved the response to a "new" booking, which reduces the amount of requests and request time. The functionality in Transpas has been modified to make use of this.
A2B ferry integration updated to accomodate ICS2 changes
The A2B ferry integration has been updated to A2B "version 2.0".
There have been some improvements to the http requests and xml responses via FTP. New requirements due to ICS2 are integrated into this new version.
Issue with large utf-8 encoded message parts solved in e-mail client. Connection closed gracefully 'error'.
PTV developer support for route calculation and geocoding built-in
PTV developer support built-in, which will replace the PTV xServer in the future.
https://developer.myptv.com/en
This integration brings a number of changes.
First there are 2 main settings to switch from xServer to PTV developer.
For geocoding (locating coordinates for addresses) this can be found in the "System parameters" screen field "Geocoding provider"
And for routing (getting distances, traveling times, toll and so on) this can be found in the "Company" screen on the first tabsheet "General" field "Routing provider"
In order make a correct calculation for CO2 emissions and toll prices there a several new field added on vehicle level and on vehicle profile.
Also some already existing fields have new options available.
Engine type
Enum: "COMBUSTION" "ELECTRIC" "HYBRID"
The engine type of the vehicle. When changing the engine type further parameters must be specified to define a valid vehicle and to obtain proper results. For a hybrid or an electric vehicle electricityType and averageElectricityConsumption must be specified, for a hybrid vehicle additionally the hybridRatio.
This and all dependent parameters cannot be used with a model of an electric vehicle, because all applicable parameters are automatically provided by the model. Please refer to the concept to see specifically which parameters are not compatible and automatically set from the vehicle model.
Relevant for toll, emissions.
Fuel type
Enum: "GASOLINE" "DIESEL" "COMPRESSED_NATURAL_GAS" "LIQUEFIED_PETROLEUM_GAS" "LIQUEFIED_NATURAL_GAS" "CNG_GASOLINE" "LPG_GASOLINE" "ETHANOL" "NONE"
The fuel type of the vehicle. The fuel types CNG_GASOLINE and LNG_GASOLINE are used for dual-fuel vehicles, therefore the dualFuelRatio has to be specified. These fuel types cannot be used with hybrid vehicles.
Supported for engineType COMBUSTION and HYBRID. Relevant for emissions.
Fuel consumption
The average fuel consumption of the vehicle. Depending on the fuelType [l/100km] for liquid fuel types or [kg/100km] for gaseous fuel types.
Supported for engineType COMBUSTION or HYBRID. Relevant for emissions.
Bio fuel ratio
The ratio of biofuel to conventional fuel [%], i.e. 10 for E10 with 10% biofuel.
Supported for engineType COMBUSTION or HYBRID and only for the fuel types GASOLINE, DIESEL, CNG_GASOLINE and LNG_GASOLINE. Relevant for emissions.
Duel fuel ratio
Ratio of CNG or LPG usage from the total amount of fuel consumption.
Supported for engineType COMBUSTION with fuelType CNG_GASOLINE or LPG_GASOLINE. Relevant for emissions.
Emission class
Enum: "NONE" "EURO_0" "EURO_1" "EURO_2" "EURO_3" "EURO_4" "EURO_5" "EURO_EEV" "EURO_6" "EURO_6C" "EURO_6D_TEMP" "EURO_6D" "EURO_6E" "EURO_7"
The emission standard of the vehicle valid in the European Union. This parameter is not only important for proper toll and emission calculation, there are also low-emission zones which can be entered only if the vehicle has a proper emission standard. In contrast to explicit approvals like environmental badges or vehicle registrations the emission standard is automatically considered when entering such low-emission zones.
Values different from NONE are supported for engineType COMBUSTION and HYBRID. Relevant for routing, toll, emissions.
Emission technology
This field is no longer needed in PTV developer.
Carbon dioxide emission
Not needed for PTV developer, can be used for making manual calculations.
Electricity type
Enum: "BATTERY" "HYDROGEN_FUEL_CELL" "NONE"
The electricity type of the vehicle.
Supported for engineType ELECTRIC or HYBRID. Relevant for emissions.
Electricity consumption
The average electricity consumption of the vehicle [kWh/100km].
Supported for engineType ELECTRIC or HYBRID. Relevant for emissions.
Hybrid ratio
Electric energy usage ratio from the total amount of energy consumed by the vehicle.
Supported for engineType HYBRID. Relevant for emissions.
CO2 emission class
he CO2 emission class valid in the European Union. See also the Directive 1999/62/EC of the European Parliament and of the Council on the charging of heavy goods vehicles for the use of certain infrastructures, Article 7ga.
Must be 1 for combustion and hybrid vehicles with any emissionStandard, 2-4 for combustion and hybrid vehicles with emissionStandard of at least EURO_6, and 5 for electric vehicles.
Relevant for toll.
Low emission zone class
This field is no longer needed for PTV developer.
Diesel particle filter
This field is no longer needed for PTV developer. Use particle reduction class instead.
Particle reduction class
Enum: "PMK_0" "PMK_1" "PMK_2" "PMK_3" "PMK_4" "NONE"
The particle reduction class (Partikelminderungsklasse) according to 'Anlage XIV zu ยง 48 StVZO' (German law). This value is present for compatibility reasons and does not influence any of the results.
Supported for engineType COMBUSTION and HYBRID.
When the fields above a not specified the values are taken from the vehicle profile which is assigned to the vehicle / plangroup / company.
The vehicle profile roughly contains the same fields as on vehicle level.
One of the most important changes are the predefined PTV profiles which are completely changed in comparison with xServer.
For more information about these profiles please see:
https://developer.myptv.com/en/documentation/data-api/concepts/profiles
Tranpas used "EUR_TRAILER_TRUCK" as default when nothing is specified.
Furthermore the emissions can now be seen withing the routeplanner / trip map view.
Financial date income bases on real loading or unloading date
The company setting "Financial date transport income" has 2 new options
-
Real loading date of shipment
-
Real unloading date of shipment
When no real dates are available then the planned date is used.
PTV developer support for route calculation and geocoding built-in
Financial date income bases on real loading or unloading date
The company setting "Financial date transport income" has 2 new options:
- Real loading date of shipment
- Real unloading date of shipment
When no real dates are available then the planned date is used.
Column transportkind added to function SI_SalesInvoiceTable
Field "inactive" added to surcharge rulesets
User access group field added on invoice group level
When a user access group is specified on an invoice group, this group can only be accessed by members of this group.
Emission fields added to sales invoice functions
Fields for COe emissions were added to the funtion SI_SalesInvoiceTable().
[CO2eTankToWheel] FLOAT
[CO2eWellToWheel] FLOAT
Expressed in kilograms.
Mobile communication - Remove delivery statuses on canceled activities
Delivery statuses will be removed now when an activity is canceled by the driver on a Trimble device.
Planning - Length, width and height fields on carrier ruleset
Conditional fields added for length, width and height on carrier ruleset rules.
Sales invoicing - Alphanumeric debtornumbers are shown on invoice now
When using alphanumeric debtornumbers, these weren't printed on the invoice by default. This is fixed now.
Route planning - Vehicle technical max. weight field added
A field added to the vehicle profiles for "Vehicle technical max. weight".
For more information see the last chapter on:
https://developer.myptv.com/en/documentation/routing-api/concepts/toll-routing