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
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.
There are multiple ways an incident can be created automatically.
Close a handling unit
Set in Stock
Set out of Stock
Transfer Handling Unit
Adjust Handling Unit
Set Plan/Actual Data
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 type | Description | Testcases |
|---|---|---|
| Stock Difference | Quantities 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. | |
| Internal CMR Difference | The CMR attached by the Logistic service provider does not comply with the handling units. | Not tested yet |
| Internal Customs Goods Difference | Goods information in customs declaration that was sent to Fiton does not comply with handling unit goods. | Not tested yet |
| External CMR Difference | The CMR attached to handling units by an external party does not comply with the handling units. | Not tested yet |
| External Customs Goods Difference | Goods information in customs declaration does not comply with handling unit goods. | Not tested yet |
| Damage Stock | Stock has been damaged, | TES-1585 - Getting issue details... STATUS |
| Damage On Outbound | Outbound handling units are (partly) damaged This incident type cannot be created because there is no damage option on outbound. | Not tested yet |
| Damage On Inbound | Inbound handling units are (partly) damaged | TES-610 - Getting issue details... STATUS |
| Add/Delete HU After Customs Declaration | Goods are added or removed after a customs declaration has been done. | TES-2052 - Getting issue details... STATUS |
| Air Order Planning Difference | Portal supplier changes air order data in accept order screen. | TES-1612 - Getting issue details... STATUS |
| Barge Order Planning Difference | Portal supplier changes barge order data in accept order screen. | TES-1612 - Getting issue details... STATUS |
| Rail Order Planning Difference | Portal supplier changes rail order data in accept order screen. | TES-1612 - Getting issue details... STATUS |
| Transport Order Planning Difference | Portal supplier changes transport/trucking order data in accept order screen. | TES-1612 - Getting issue details... STATUS |
| Vessel Order Planning Difference | Portal supplier changes vessel order data in accept order screen. | TES-1612 - Getting issue details... STATUS |
| Credit Invoice | Create credit invoice. | |
| Cancel Customs Declaration | Customs declaration is cancelled. For this you need a working Fiton interface | Not tested yet |
| Difference In Customs Information | Customs information is changed for goods that are already in stock/set out of stock. | TES-1253 - Getting issue details... STATUS |
| Difference In Weight | Weight values are changed when setting goods in stock. | Not tested yet |
| Difference In Storage Weight | Weight values are changed when adjusting goods that are in storage. | TES-1291 - Getting issue details... STATUS |
| Validate Goods Before Closing | Validate goods information before setting goods in/out of stock. | TES-1504 - Getting issue details... STATUS |
| Difference In Transport Order Actual Data | Confirmed 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 Date | Difference 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 Date | Difference 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 Supplier | Order is declined by supplier |