<to do: rewrite, modernise>
- Incidents - implementation
- Incidents - description
An incident occurs when some handlings do not match with expectations of the system. For example a quantity delivered of 490 when the system expected a quantity of 500.
An incident can be created manually or automatically.
the following subjects will be described:
Automatic Incident types
Incident type | Description |
---|---|
Stock Difference | Quantities of a Handling Unit have changed during storage. |
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. |
Internal Customs goods difference | Customs filled in by the LSP does not comply with handling unit goods. |
External CMR Difference | The CMR attached to handling units by an external party does not comply with the handling units. |
External Customs goods difference | Customs filled in by an external party does not comply with handling unit goods. |
Damage Stock | Stock has been damaged, could be the issue if a quantity is changed. |
Damage on outbound | Outbound handling units are (partly) damaged |
Damage on inbound | Inbound handling units are (partly) damaged |
Status of incidents
Status | Description |
---|---|
Open | After an incident has been created it is assigned the status open |
Partially approved | If more than one value has been changed and only one or a few of these is approved |
Approved | All changes have been approved |
Partially declined | If more than one value has been changed and only one or a few of these are declined |
Declined | All changes have been declined |
Cancel | An open incident can be cancelled, if it has any other status it cannot be cancelled. |