Introduction

An incident occurs when the outcome is different from the expected result.

The first example is when some handlings do not match with expectations of the system. The delivered quantity is 490 when the system expected a quantity of 500. 

Another example is that the Transport would collect the goods on the 2nd of January, while the Transport actually arrived on the 1st of January.

An incident can be created manually or automatically, and it can be closed automatically or manually.


Subjects

Manually

Incidents can be manually added on page 'Incidents'. Incident Types with App Incident Type 'Manual' can be selected here. The incident data is filled in based on the incident type and can be edited. 

The creation date will be inserted automatically once the incident is saved. 

Automatically

There are multiple ways an incident can be created automatically. 

  1. Close a handling unit

    1. Set in Stock

    2. Set out of Stock

  2. Transfer Handling Unit

  3. Adjust Handling Unit

  4. Set Plan/Actual Data

  5. Scan the Order using Transport In- Out Mobile or Transport Order Arrival.

An incident will be created if the original values of the handling unit are changed. This can be the unit, the carrier, the quantity or the weight. 

When an incident is created on a Handling Unit the status of the Handling Unit chages to 'Incident' and the icon of an eye will show in the column 'Info'. The eye indicates that there is an incident with status Open. Hovering over the icon will show additional information about the incident. 

Incident information can be checked by opening page 'Incidents' and opening the incident or by using the To Do 'Check Incident Data'. This will display the incident information, the original information and the actual values. The changes in the actual values are marked in red. 

The To Do 'Process Incident Changes' can be used to process the incident. The incident data, original and actual values are shown. The incident is processed when the incident is accepted and the actual values will be shown on the Handling Unit.

The incident also can be declined. When the incident is declined the values are set back to the original values and the Handling Unit will not be closed. 

Canceling an incident will restore all original values. 

A complete overview of all incident can be found in the menu below 'Incidents'. Incidents on a Handling Unit are shown on the tabpage 'Incidents' in a handling unit and incidents per dossier in the tabpage  'Incidents' in the dossier. 



Incident Dashboard

Automatic Incident Types

Incident typeDescriptionTestcases
Stock DifferenceQuantities of a Handling Unit have changed during storage.

TES-1875 - Getting issue details... STATUS

Inbound Difference

The planned values of the handling unit do not match with the values when setting the goods in stock.

TES-646 - Getting issue details... STATUS
TES-1291 - Getting issue details... STATUS
TES-1710 - Getting issue details... STATUS

Internal CMR DifferenceThe CMR attached by the Logistic service provider does not comply with the handling units.Not tested yet
Internal Customs Goods DifferenceGoods information in customs declaration that was sent to Fiton does not comply with handling unit goods.Not tested yet
External CMR DifferenceThe CMR attached to handling units by an external party does not comply with the handling units.Not tested yet
External Customs Goods DifferenceGoods information in customs declaration does not comply with handling unit goods.Not tested yet
Damage StockStock has been damaged,

TES-1585 - Getting issue details... STATUS

Damage On OutboundOutbound handling units are (partly) damaged

This incident type cannot be created because there is no damage option on outbound.
Not tested yet
Damage On InboundInbound handling units are (partly) damaged

TES-610 - Getting issue details... STATUS

Add/Delete HU After Customs DeclarationGoods are added or removed after a customs declaration has been done.

TES-2052 - Getting issue details... STATUS

Air Order Planning DifferencePortal supplier changes air order data in accept order screen.

TES-1612 - Getting issue details... STATUS

Barge Order Planning DifferencePortal supplier changes barge order data in accept order screen.

TES-1612 - Getting issue details... STATUS

Rail Order Planning DifferencePortal supplier changes rail order data in accept order screen.

TES-1612 - Getting issue details... STATUS

Transport Order Planning DifferencePortal supplier changes transport/trucking order data in accept order screen.

TES-1612 - Getting issue details... STATUS

Vessel Order Planning DifferencePortal supplier changes vessel order data in accept order screen.

TES-1612 - Getting issue details... STATUS

Credit InvoiceCreate credit invoice.

TES-1351 - Getting issue details... STATUS
TES-1915 - Getting issue details... STATUS

Cancel Customs DeclarationCustoms declaration is cancelled.

For this you need a working Fiton interface
Not tested yet
Difference In Customs InformationCustoms information is changed for goods that are already in stock/set out of stock.

TES-1253 - Getting issue details... STATUS

Difference In WeightWeight values are changed when setting goods in stock.Not tested yet
Difference In Storage WeightWeight values are changed when adjusting goods that are in storage.

TES-1291 - Getting issue details... STATUS

Validate Goods Before ClosingValidate goods information before setting goods in/out of stock.

TES-1504 - Getting issue details... STATUS

Difference In Transport Order Actual DataConfirmed data in Transport Order Arrival Departure screen has been changed.

TES-1616 - Getting issue details... STATUS

Difference Between Transport Order Plan Date And Updated Plan DateDifference between old planned activity date and new activity date is more than allowed

TES-935 - Getting issue details... STATUS

Difference Between Transport Order Plan Date And Actual DateDifference between old planned activity date and new actual activity date is more than allowed

TES-935 - Getting issue details... STATUS

Transport Planning Declined By Portal SupplierOrder is declined by supplier

TES-1037 - Getting issue details... STATUS
TES-1612 - Getting issue details... STATUS


Status of Incidents

StatusDescription
OpenAfter an incident has been created it is assigned the status open
Partially approvedIf more than one value has been changed and only one or a few of these is approved
ApprovedAll changes have been approved
Partially declinedIf more than one value has been changed and only one or a few of these are declined
DeclinedAll changes have been declined
CancelAn open incident can be cancelled, if it has any other status it cannot be cancelled.