TopicTitle & DetailsRelase MonthTypeID
Customer order management and pricing
Possible loss of manually adjusted tariff quantity on sub-contracting tour order (FTL) after the date change on the transport order


Under certain circumstances the change of load/unload date on transport order could lead to the loss of manual tariff quantity on sub-contracting tour order (FTL). The issue was especially happening when the load (or unload) data was changed on the transport order (that was already dispatched in the tour with some sub-contracting tour (FTL) order, with some manually adjusted tariff quantity) and user activated "Keep existing contract - Sub-contracted order" and "Recalculate now: Sub-contracting order" parameters on the the change date dialog. The issue was corrected and the adjusted tariff quantity on the sub-contracting tour order (FTL) is not anymore reinitialized to the default value.

2021-04New feature78950
Customer order management and pricing
Adding 'Status term invoice' to the customer account


Via previously existing 'Status term invoice' functionality it is possible to affect when transport order shall reach the invoiceable status. Previously, the status term invoice was initialized to the transport order header either from the delivery terms or from the main TMS parameters.
Newly, the status term invoice can be initialized also from the customer account.

Following status term invoice general determination logic was used (for 'non-shipment builder' transport orders), top priority first:
- Status term invoice is determined from the transport delivery terms
- Status term invoice is determined from the customer account
- Status term invoice is determined from the main TMS parameters

For the shipment builder based transport orders, the status term invoice is determined from the transport delivery terms (that are provided by the 'Transport delivery term' mapping, see task 80977 in this release).

2021-04New feature81560
Dispatching and confirmation
Resource absence/unavailability registration


Newly it is possible to specify a resource absence/unavailability (eg. truck is in garage for maintenance etc.), which is then also reflected in the GPB 'Resource Dispatching' screen. The resource absence/unavailability setup happens in the 'Resource assignment' form (accessible in main menu -> CAPcargo Transport -> Inquiries -> Resources -> Resource assignment).

To switch on/off the visualization of resource absence/unavailability in GPB, a new checkbox filter 'Show Unavailability' was added to the GPB 'Resource Dispatching' screen.

2021-04New feature52928
Dispatching and confirmation
Enhancement of the empties management (introducing company identification data and pallet docket number, for the pallet docket SSRS report)


The pallet docket SSRS report was enhanced by new additional fields (by company identification data and by pallet docket number).
Pallet docket number represents an identification of the empties record transaction, for external purposes.

The parameterization of number sequences for pallet docket number (for various combinations of 'Unit Empties' & 'Movement type') and also the definition of the company identification data happens in the main 'Transport parameters', under new menuitem 'Empties identification data' (in 'General' tab page of main TMS parameters).

2021-04New feature77425
Dispatching and confirmation
Enhancement of the new tour creation dialog (introducing different sources for the tour start & end addresses)


Newly, during the creation of the new tour, it is possible to specify from which source the tour start & end addresses shall be initialized from. Possible sources:
- From route/zone
- From dispatch sector
- From motor vehicle home depot
- From trailer home depot

Following tour creation methods were enhanced:
- Dialog for manual tour creation
- Dialog for tour creation via drag & drop from the GPB 'Transport orders /-legs' screen (of from map screen) to both GPB gantt screens

Please note:
- The dialog for the tour creation via drag & drop to both GPB gantt screens is newly launched only when users hold the "CTRL" key while performing the drag & drop.

2021-04New feature78487
Dispatching and confirmation
Alignment of the date filtering between GPB 'Transport orders /-legs' screen and D365 'Dispatch light - Transport legs' form


Previously, it could happen that when users set the same date filters on GPB 'Transport orders /-legs' screen and D365 'Dispatch light - Transport legs' form, the result could differ (ie. the amount of filtered transport leg could be different). This was happening because the D365 form was using slightly different logic (D365 form was applying the date filter only to the load date of transport legs), whereas the filtering in the GPB screen was applying the date filter both to the transport leg load & unload date. The date filtering on D365 form form was enhanced, to match the date filtering on the GPB screen.

2021-04New feature79926
Dispatching and confirmation
Horizontal scrolling synchronization in GPB 'Resources' screen


Previously, in the GPB 'Resources' screen, the horizontal scrolling of resources was independent both for 'Available' & 'Planned' sections. This was not too user friendly (as users had to scroll in two horizontal bars) and was improved. The horizontal scrolling for both 'Available' & 'Planned' sections is newly synchronized, hence dispatchers always see the same scope for 'Available' & 'Planned' resources.

2021-04New feature79977
Dispatching and confirmation
Small GUI enhancement of the default date filter, when GPB 'Resources' screen is switched into 'Manual date' mode


In the GPB 'Resources' screen, when switching to 'Manual date' mode, the date filter was previously set to some default (ie. historical) date. Newly, when GPB 'Resources' screen is switched to 'Manual date' mode, the today date is used as a default date filter.

2021-04New feature79980
Dispatching and confirmation
Adding more processes on the GPB 'Transport orders /-legs' screen to the individual transport leg refresh mechanism


In the last release, a functionality for individual transport leg refresh was introduced to the GPB 'Transport orders /-legs' screen (which allowed to perform a selective refresh of an individual record rather than the refresh of all records in the grid). But only several processes were enhanced to benefit from the selective refresh. By this task, following processes are also newly enhanced:
- Release to warehouse
- Generate tour from transport leg
- Remove part delivery
- Delete order from dispatching
- (Un-) Docking
- Rough scheduling (transport legs)

2021-04New feature81158
Dispatching and confirmation
More more friendly insertion of the new tour stop in both GPB gantt screens


In both GPB gantt screens, it was possible to insert a new tour stop (via a context menu, when using the right mouse button between two tour stops). The complication was that users had to do a right click (to open a context menu) very near to the horizontal black line between the tour stops (which typically shows the driving distance and time). The functionality was enhanced, now user doesn't have to click near the horizontal black line but can click anywhere in the white space between the two tour stops.

2021-04New feature81268
Dispatching and confirmation
Performance driven enhancement of the GPB gantt screen automated refresh (level specific refresh)


Previously, when the refresh was performed automatically in both GPB gantt screens, the system always refreshed all three levels at once (ie. tour, tour stops, resource allocations). Such 'all level' refresh is actually not needed, in case the dispatching action affects only a certain level (eg. the assignment of the carrying resource doesn't need to refresh the main tour gantt in level 1 etc.). The intelligence of GPB automated refresh was improved, to refresh only the level that is affected by the dispatching action.

2021-04New feature81364
Dispatching and confirmation
Performance driven enhancement of the shipment builder dispatching tasks


Shipment builder dispatching tasks represent an important aspect of the tour planning, with possible performance impact (due to the complexity of the underlaying operations). Hence it shall be possible to launch such tasks also via periodic batch processing (which runs on the better performing server side), also such tasks shall typically not block the user sessions. To support the periodic batch processing, following enhancements were done:
- Release to warehouse - the existing release to warehouse in batch functionality has to be improved. If the batch processing is set to YES on the release to warehouse dialog, then the system generates a batch job per tour.
- Complete tour execution - newly it is possible to run complete tour execution also via batch processing. So when the complete tour execution button is pressed (in GPB or in D365), then a dialog pops up, where the user can decide whether to process the tour in batch. As the complete tour execution is enabled only for the single selected tour, only one batch job per tour is created. The batch tasks then represent each active sub-process of the complete tour execution (ie. transport order synchronization, confirmation of outbound shipments, packing slip posting & direct confirmation of the tour). The batch tasks are process sequentially (next is started only when previous successfully finished). In case of an error, the already executed batch tasks are not rolled back.

2021-04New feature81526
Dispatching and confirmation
New feature: package label ZPL printing


The package labels can be newly printed also via Zebra Programming Language standard (ZPL). The menuitems 'Print labels ZPL' are available on following places:
- on Package management forms
- directly on Transport order form
- directly on both GPB gantt screens
- directly on D365 'Dispatch light - Tours' form

The 'Print labels ZPL' menuitems are also enabled for record multi-selection.

2021-04New feature81570
Driver App
Driver app support for Zebra TC57

The CAPcargo driver app was originally designed (and tested) for barcode scanning via a 'built-in' camera, such as a phone camera. The app is technologically open to allow other input devices. In this task a support for barcode scanning via embedded laser hardware is introduced. This feature was tested with a 'Zebra TC57' and DataWedge 8.1. We expect the feature work with other devices from the Zebra device range, but has so far not been tested. Contact CAPcargo for more information about the device setup.



2021-04New feature64563
Driver App
Deprecated functionality: 'Dispatching information' on the TMS address (in driver app)


Previously, the 'Dispatching information' was deprecated in the TMS (was replaced by the work instruction framework), but the driver app was not adjusted, hence was still showing the 'Dispatching information'. The driver app is now also adjusted, the 'Dispatching information' is not anymore transmitted to the driver app.

2021-04New feature80811
Driver App
Product details of the trade orders were added to the information details section in the driver app


In the driver app, on the loading and unloading activities either the transport order number or the package id is displayed. Trade order related information is only shown on the details screen (which pops up when the loading/unloading activity tile is pressed). However, on the details screen, only the following information details was previously available:
- Customer
- Address name
- Trade order id
- Trade order line number

This enhancement adds to the information detail section also the identification of product that is loaded into / unloaded from the vehicle.

2021-04New feature80903
Driver App
Better handling of the situation where driver app feedback contains some reason code (that is not existing in the D365)


In rather theoretical example (when in productive use), while quite possible when testing the features, it could happen that the feedback from the driver app contained some reason codes that were actually not existing in the D365. Previously, when such constellation happened, the driver app activity feedback was marked as completed, but the tour confirmation data was not confirmed (eg. tour activities were not confirmed) and it was not directly clear why. Newly, such driver app activity feedback is marked by flag 'Manual processing needed', with error message 'Unknown reason code'.

2021-04New feature81342
Driver App
Enhancement of the load/unload activity sorting in the driver app


Previously, it could happen that the load/unload activity sorting in the driver app did not exactly correspond to the tour stop sorting in the D365 (as different sorting criteria were used). The sorting discrepancy might have been encountered when tour stop sequence was modified (or tour stops were split/merged) before the tour was released to driver app.
The sorting logic was unified, the driver app now follows the same sorting as the tour stops in D365.

2021-04New feature81433
Driver App
Direct barcode scanning (with physical barcode scanner) in the driver app without opening the scanning dialog


If the driver app device has a physical barcode scanner, it's now possible to start scanning barcodes directly in the activity list screen (after swiping "Arrived") instead of opening the barcode scanning dialog via action menu.

This feature is still in progress, and there is a known issue which is caused by the imperfection in the Flutter framework (which is used for communication with physical barcode scanners): if any text input dialog is opened (such as Skip activity, Claim) this "dialog-free" scanning stops working until the app is minimized and opened again. However at least Zebra TC-57 device seems to not suffer from this issue.

2021-04New feature81704
Integrations
New data entity: TAL Instruction activity rules


New data entity 'TAL Instruction activity rules' was added to the system, it is now possible to import or export TMS instruction activity rules.

2021-04New feature79136
Master data
New feature of address geo-coding via image


Previously, geo-coding of addresses could be done ether manually (by entering geo coordinates on address level), or by using the function 'Geo-code selected address' that uses the PTV xServer interface to get the geo-coordinates of the selected address, or by geo-coding from map pin. This task introduces a fourth option - geo-coding via image.
Newly it is possible to obtain the geo-coordinates also from the uploaded image/photo (ie. the geo-coordinates are extracted from the EXIF image meta data). So it is possible to geo-code a location by making a picture of the location (with the camera that supports storing the GPS geo-coordinates in EXIF image meta data) and simply upload the image to the D365. Resulting geo-coordinates are then saved to the 'Global address book' address details, with flag 'Protect Geo-coordinates'. The menuitem 'Geo-coding - Image' is also available directly on the TMS Address form.
The uploaded image will be also saved as an attachment to the address details (in the Global address book), if 'Attach image to address' functionality is activated in the main TMS Transport parameters.

2021-04New feature79649
Master data
Improve the classification of the resources with zero capacity definition


Previously, the interpretation of various types of vehicles was not straightforwardly clear when setting up the 'Fitting' or 'Non-Fitting' filtering in the GPB 'Resources' screen. Especially the distinguishing of following resource parameterization was problematic:
- when trailer resource has zero capacity defined for certain transport type
- when motor vehicle resource has zero capacity defined for certain transport type

Therefore following terminology unification was adopted:
- If a vehicle is a motor vehicle and has a zero capacity defined in the vehicle capacity, then it's considered a 'pulling tractor' vehicle unit in GPB 'Resources' screen, meaning it will ignore a capacity check, since it's just a tractor/pulling vehicle.
- If a vehicle is a trailer and has a zero capacity defined in the vehicle capacity, then it's considered a 'loading bridge' vehicle unit in GPB 'Resources' screen, meaning it will ignore a capacity check, since it's just a bridge to put other load devices upon it.

To improve the user knowledge (when setting up a new capacity for vehicles), following enhancements were done:
- New menuitem 'New (for no-cap. vehicle)' on the vehicle capacity form (when launched both from vehicle & vehicle type forms), to create a 'pulling tractor' or 'loading bridge' capacity specification (depending whether the vehicle is a motor vehicle or a trailer).
- New information field was added to the vehicle capacity form, so that user can immediately see whether the current capacity parameterization fulfills the 'pulling tractor' or 'loading bridge' characteristic (that are always interpreted as 'Fitting' on the GPB 'Resources' screen, because the capacity checks are skipped), or is the regular capacity based resource.

2021-04New feature81182
Master data
Two enhancements of the address 'Geo-coding - Map' feature


Several enhancements were done to the recently introduced 'Geo-coding - Map' feature:
- The 'Geo-coding - Map' feature didn't previously use the D365 address details, for visualization of the initial pin. So when no geo-coordinates were previously defined for an address, the 'Geo-coding - Map' initial pin was placed to [0,0] geo-coordinates, which was not user friendly, as user has to scroll & zoom to wished location, to be able to place a map pin. Newly, when no geo-coordinates are stored on the address, the address details (eg. street name, street number, city, zip code, country) are used to visualize the initial pin on the map.
- The map visualization component sometimes didn't load all map tiles and users had to adjust the map window (to load the remaining tiles). The issue was corrected and all map tiles are now loaded at once.

2021-04New feature81377
Shipment Builder
Several enhancement in the area of direct delivery of the trade order
Following enhancement were done, in the area of direct delivery of the trade order:


- Transport delivery term creation - delivery terms on the transport order were previously D365 standard delivery terms, which was not sufficient for TMS purposes (as delivery terms on the transport order do not necessarily have to be the same as the delivery terms on the trade order), also was limiting for the cross-company transportation (where the transportation is done by different D365 legal entity than the trade order is created). So newly the transport order is using a separate new entity of 'Transport delivery terms'. For transport orders (that are generated via shipment builder) the transport delivery terms are initialized from new mapping table (accessible in main menu -> CAPcargo Trade & Distribution -> Setup -> Transport delivery term mapping)
- Filter for direct delivery - GPB 'Transport orders /-legs' screen filtering is enhanced to include also the direct delivery related transport legs. So when the user filters by Sales or Purchase order (via the 'Shipment building area' filter, transport order which are created based on the direct delivery are also newly shown in the grid
- Validation of the direct delivery trade order changes - all relevant changes in the whole direct delivery chain are newly blocked in case there is a CAPcargo shipment already created.

IMPORTANT:
- Related data migration task 81294 does *NOT* generate the default mapping of D365 standard delivery terms (that are used on the trade orders) into transport delivery terms (that are used on the transport orders). Such default mapping has to be done after the release installation and before the shipment builder is used in the daily routines.
Without the transport delivery mapping being in place, the shipment builder processes might lead to unexpected data constellations (eg. shipment lots are removed from existing shipments etc.).

2021-04New feature80977
Customer order management and pricing
Batch for time & distance calculation of transport order sometimes ended with error


The error "Cannot edit a record in Transport orders (CIRTRASalesTable). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record" was sometimes encountered during the periodic task 'Time & distance calculation transport order'. The issue was corrected and error is not encountered anymore.

2021-04Bug64528
Customer order management and pricing
No detection of conflicts (that were related to the unload of transport order) during conflict analysis on the transport order form


The conflict analysis (when launched from the transport order form) was previously not detecting the conflicts that were related to the unload address. The issue was corrected and the conflict analysis now detect the conflict both for load & unload addresses.

2021-04Bug81089
Customer order management and pricing
Wrong display of packages in the track & trace status view, for transport orders that were created from the D365 trade orders


Previously, when the transport order was created from the D365 trade orders, the track & trace status view (launched from the transport order) showed all packages in the system (ie. even the packages that were connected to entirely different transport orders). The issue was corrected, the track & trace status view now shows only the packages that are related to the transport order.

2021-04Bug81106
Dispatching and confirmation
''Object reference not set to an instance of an object.' error in conflict analysis


When opening the conflict analysis form, an error 'Object reference not set to an instance of an object.' was sometimes encountered. The issue was especially happening when some vehicle based qualification was used on the transport address. The issue was corrected and vehicle based qualifications on transport address are now detected correctly.

2021-04Bug79377
Dispatching and confirmation
Printing of package labels printed only the label for the first selected package


Previously, it was not possible to print labels for multiple-selected packages (in the package management forms), system printed the label just for the first selected package. The issue was corrected and labels are now printed for all selected packages.

2021-04Bug81076
Dispatching and confirmation
Wrong name of the parameter in the 'Print labels' dialog


Label correction in the package label printout dialog (that can be launched from several places in the TMS, eg. from tour dispatching or from package management etc.). Parameter for selective pallet label printing was renamed from 'Print labels' to 'Only packages marked for printing'.

2021-04Bug81108
Dispatching and confirmation
Paging counter of filtered records in the GPB 'Transport orders /-legs' screen was sometimes not actualized automatically


The paging counter of filtered records in the GPB 'Transport orders /-legs' screen was sometimes not actualized automatically. So for example when dispatchers had 20 records shown in the grid (ie. transport legs) on one page (out of total 25 records), then when part delivery transport leg was removed (via 'Remove part delivery'), the resulting paging counter was previously showing 20 records out of 24 records. Which was not correct, as the paging counter should show 19 records out of 24 records. The issue was corrected.

2021-04Bug81149
Dispatching and confirmation
'GPB - Tour Dispatching' menuitems and 'Go to tour (GPB)' process parameters were sometimes not working in D365 forms/dialogs (or were working with a delay)


The menuitems (and process parameters) for opening a tour in GPB from D365 forms/dialogs were previously sometimes performing with a delay (or not working at all). The issues were corrected.

2021-04Bug81151
Dispatching and confirmation
No possibility to filter transport leg via SCM statuses, when shipment builder licence configuration key was deactivated


SCM status based filtering of the transport legs was previously possible only when 'Shipment builder (based on WHSLoadLine)' license configuration key was activated. Without the shipment builder license configuration key, the SCM statuses were not managed on the transport legs (thus also the SCM filtering was not possible). The issue was corrected, the SCM status management is now independent to the shipment builder configuration key and can be used also in projects that are not using shipment builder for transport order creation.

2021-04Bug81256
Dispatching and confirmation
Error 'Object reference not set to an instance of an object.' on the GPB 'Tour Dispatching' screen


Error 'Object reference not set to an instance of an object.' was previously sometimes encountered on the GPB 'Tour Dispatching' screen. This was especially happening when users launched the inquiry for 'Statistics cost/revenue split (posted)'. The issue was corrected.

2021-04Bug81266
Dispatching and confirmation
Unhandled error could be triggered on the GPB 'Tour Dispatching' screen


Unhandled error (ie. system stack trace error) was sometimes reported by the system in GPB 'Tour Dispatching' screen. This was especially happening when several users extended the tour duration (by drag & drop of the tour end) on the same tour, in the same moment. The behavior was improved, instead of unhandled error system now informs via "Buffer 'Tour: XYZ' changed by another user!".

2021-04Bug81274
Dispatching and confirmation
Filtering via owner in GPB 'Resource Dispatching' was not reliable when owner was changed on the tour


Previously, when changing the owner of the tour, the owner filtering in GPB 'Resource Dispatching' was not reliable (ie. the resources were not shown when owner filter was applied). The issue was corrected.

2021-04Bug81279
Dispatching and confirmation
The qualification count was sometimes showing unreliable figures in the qualification overview


In the tour qualification overview, the qualification count (appearing as number in brackets, in the header of each tab title) was sometimes not showing reliable data. This was especially happening for the provided employee qualifications. The issue was fixed and qualification count works correctly now.

2021-04Bug81305
Dispatching and confirmation
Missing drivers when filtering for exact tour in the GPB 'Resource Dispatching' screen


Previously, when filtering the exact tour in the GPB 'Resource Dispatching' screen then in certain data constellations the filtered tour was shown without assigned resources (especially drivers were sometimes missing). The issue was corrected and assigned resources are now also shown when filtering the exact tour in GPB 'Resource Dispatching' screen.

2021-04Bug81334
Dispatching and confirmation
Correction of several labels in the cross-docking form


Several labels (and help labels) were corrected in the filter section in the cross-docking form, the form filters should be more understandable now. The adjustment was only on GUI level, with no change to the form functionality.

2021-04Bug81481
Dispatching and confirmation
Error 'BOX API can't be used from non-interactive sessions' was sometimes encountered in both GPB gantt screens


The issue was especially happening when 'Offer non-unique assignment' was activated in the 'Assign carrying resource' process parameters in main TMS Transport parameters. The issue was corrected.

2021-04Bug81773
Dispatching and confirmation
''Loading data' spinning icon in the tour stop section in the GPB 'Resource Dispatching' screen after drag & drop of orders from the map


When multiple orders/transport legs were planned into the new tour (by drag & drop from the GPB map screen to 'Resource Dispatching' screen), then the new tour was correctly created but the tour stop section was not refreshed (ie. the level 3 refresh 'loading data' icon was stuck and manual tour refresh had to be performed). The issue was fixed and the tour stop level 3 refresh is performed correctly now.

2021-04Bug81964
Driver App
In certain parameterization constellation it could happen that the tour was not entirely confirmed (in D365) while all activities were finished in the driver app


The issue was especially happening when 'Barcode scan (Address area)' activity was activated but no activity area was provided on transport orders in the tour. The issue was corrected and the address area tour activities are generated only when the the transport order provide an address area.

2021-04Bug80585
Driver App
Missing load activity in the driver app, after merging the tour stops


When the dispatchers merged several tour stops together, this could cause that the load activity sometimes disappeared in the driver app. The issue was corrected and load activity doesn't disappear anymore in the driver app, after the tour stop merging.

2021-04Bug80702
Driver App
Triplicated warning dialog when dispatcher tries to put to dispatching a tour that was previously released to driver app


When putting back to dispatching a tour (that was previously already released to the driver app), system warns user that the tour has been already released to driver app. The issue was that such warning dialog sometimes triplicated. This was happening especially when the mobil app parameter 'Driver acceptance before tour start' was set to 'Not needed'. The issue was corrected and the warning dialog is displayed only once.

2021-04Bug81180
Driver App
Negative activity duration in D365 tour confirmation, when confirmation was done via package barcode scanning in the driver app


When the loading activity was confirmed in the driver app by scanning the package barcode, the related activity in the D365 tour confirmation was sometimes updated incorrectly (ie. causing a negative day duration). The issue was corrected and doesn't occur anymore.

2021-04Bug81496
Driver App
Blocking 'grey screen' in the tour stop list in the driver app


Previously, in certain constellations in driver app, it was possible to encounter an irrecoverable 'grey screen' in the tour stop list. The issue was blocking the driver app users from further actions, as it could not be easily overcome (even the entire driver app re-installation with app data removal didn't help). The issue was especially happening after creating order claims (and also after some other actions in the driver app). The issue was corrected and the 'grey blocking screen' should not be encountered anymore.

2021-04Bug82018
Integrations
Several fields were missing in the 'TAL Import process' data entity


Following fields were added to the 'TAL Import process' data entity:
- Package unit
- Identification type
- Create default package

2021-04Bug80449
Integrations
In certain cases the transport order update (via EDI) was failing


Previously, it could happen that the transport order could not get updated by the EDI 'update' message, the transport order update failed with errors 'Transport order XYZ can't be generated due to existing errors' and 'Imported order XYZ isn't transformed to a transport order!'. The issue was happening especially when customer account on EDI 'update' message was represented by an external code, as the search for the 'to-be-updated' transport order was done before the 'translation' of external codes into D365 customer accounts. The issue was corrected and the search for the 'to-be-updated' transport order newly happens only after the 'translation' of external codes into D365 customer accounts.

2021-04Bug81511
Other / General
Data migration task - to generate the transport delivery terms from the D365 standard delivery terms


Data migration task for 80977.

Data migration task creates the transport delivery terms from the D365 standard delivery terms.

IMPORTANT:
* The data migration task does *NOT* generate the default mapping of D365 standard delivery terms (that are used on the trade orders) into transport delivery terms (that are used on the transport orders). Such default mapping has to be done after the release installation and before the shipment builder is used in the daily routines.
Without the transport delivery mapping being in place, the shipment builder processes might lead to unexpected data constellations (eg. shipment lots are removed from existing shipments etc.)

2021-04Data conversion81294
Other / General
Data migration task - to add the transport delivery term value to the shipment & shipment lot criteria


Data migration task for 80977.

Data migration task adds the transport delivery term value to the shipment & shipment lot criteria.

2021-04Data conversion81435
Driver App
KNOWN ISSUE: Load / unload confirmation doesn't confirm anything when 'One load/unload per tour stop' is used (='grouped' load/unload activity)


If 'One load/unload per tour stop' feature is used (it's controlled by a No/Yes field on Transport Type), individual orders/packages are not sent as separate activities to Driver app. Instead there's only one Load and/or Unload activity on the tour stop. Confirming this activity is expected to confirm all Load/Unload orders on that tour stop, but in CAP17 release it's not working.

Changes that were made to fix bug 80702 (Missing load activity in the driver app, after merging the tour stops) caused the issue.

Therefore 'One load/unload per tour stop' should not be used before installing the upcoming 10.0-CAP18.0 release ('June release').

2021-04Known issue82135
Dispatching and confirmation
KNOWN ISSUE: Vehicles not being in a vehicle group are not supposed to be used in GPB


By design, only D365 resources (WrkCtr) existing as CAP vehicles and being part of a CAP vehicle group are supposed to be used in GPB. Like this, we don't need to load too many data of resources which are not relevant for TMS. - This works well in RS, where vehicles are shown by vehicle group.

We found, that currently in Gantt-Screen-Resource (GSR) also vehicles which are not in a vehicle group are listed; this is wrong according to the current design. Since GPB does not pre-load the needed master data of such vehicles, dispatching orders to such vehicles (by new function drag&drop from OS to GSR) can lead to corrupt data and unstable situations, due to missing detail data .

Specific example:
By moving a tour from Res 1 to Res2, where Res2 is not in a vehicle-group, it happens, that a resource leg is created without WrkCtrID, because those detail/master data were missing.

CAPcargo will improve this limitations in a future release, also taking into account the feature of manual dispatching in D365 (Dispatch Light).

2021-04Known issue81929