Reprocessing ATLAS data

We are only human. Mistakes are made, and up until a certain point in time, the system accommodates changes. However, there are measures of control in place to ensure changes can only be made to the point data is communicated externally and confirmed. As long as the communication is not finalized the data in ATLAS can be changed, whereby the normal process again validates this 'new' data.

For example. In the below scenario we do a tranfser from one ship to another. Intially the Commodity code used was expired and nolonger existing. At the Pre-check, the point in time where the operator indicates final checks are done and he will start the physical operation, customs declarations are sent based on business rules. In this case a so-called Presentation of Notification was sent to Customs and rejected on the basis of the fact that the Commodity code is nolonger existing. This blocks the User from continuing, where the Notification of Presentation is showing red in the CMS overview screen. Going into the details shows the nature of the rejection. 

The User can go back in ATLAS and change the Commodity code to the correct one and re-initiate the Pre-check. Now the Transaction is reprocessed with the correct data. 

The initial Notofication of Presentation rejected can be found under the unlinked declarations under our Monitoring.

Here you can always find back the history.