Fallback and Recovery Specification (FRS)

More documents

Recommendations

Info

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Specific provisions during the rollout of EMCS There are two possible combinations: � a simple sequence of use cases UC2.44 and UC2.46, both being in the same Member State of dispatch/export; for what concerns the Migration Period 1, either the consignor is in FS0 and the current paper AAD continues being used, or he is in FS1, hence the MSA is in FS1 and the whole process may be completed electronically; � a more complex sequence involving UC2.01 in the MSA of dispatch and UC2.43 and UC2.46 in the MSA of export; these two MSAs are most frequently the same one, but they can be different as well; so, the following concerns exclusively the case where the MSA of export is different from the MSA of dispatch. When the MSA of dispatch is in FS1 then an e-AAD is likely to be electronically submitted, however the MSA of export may be still in FS0 hence unable to achieve the electronic exportation use case. Such a combination must then be prevented. This may be detected at validation either of the submitted e-AAD, or of a change of destination. A guideline of the PSS (GP 5) provides that each MSA must be permanently informed in which Functional Stage each other MSA is. So, a temporary checking is to be inserted in the validation process of UC2.01 and of UC2.05, to reject any destination at export of which Functional Stage is FS0. The rejection is then sent back to the consignor who, possibly with the assistance of his national support, may find another Member State where export may be completed, normally the MSA of dispatch itself. 8.1.3 Unavailability of the control report Currently, the results of a control are to be registered in box A of the AAD document. That AAD is planned to disappear as soon as there is an e-AAD, i.e. as soon as the consignor is able to submit it (FS1). However, the electronic control report is not included in FS1 but only in FS2. This makes that, from the time where the consignor may submit an e-AAD (FS1) to the time where all Member States are in FS2, there will be situations where a control officer is unable to register the results. Consequently, a temporary fallback scenario is proposed, based on the fallback control form of the paper fallback system. 8.1.4 Unavailability of the event report The registration of an event report is not included in FS1 but only in FS2. Contrary to the control report, the event report is a new feature of EMCS and its registration may be delayed until the involved MSAs are in FS2. Temporary fallback solutions are however described for the cases where only a part of these MSAs are in FS2. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 52 of 53
DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Specific provisions during the rollout of EMCS 8.1.5 Interruption of a movement The interruption of a movement is not included in FS1 but only in FS2. However the business need exists both at business level and at technical level where there is no business way to close a movement. A specific exception addressing the permanent unavailability of the interruption use case is therefore defined. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 53 of 53
Page 1 and 2: OWNER DG TAXUD ISSUE DATE 01/12/200
Page 3 and 4: DG TAXUD - EXCISE COMPUTERISATION P
Page 51: DG TAXUD - EXCISE COMPUTERISATION P

Fallback and Recovery Specification (FRS)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?