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 Solution elements � the recipient MSA has correctly received the sent Information Exchange; � it has already completed the actions pursuant to it or it commits itself to complete these actions. This response has the drawback to add a part of traffic into the Common Domain network. Therefore it has not been made systematic and is reserved to very essential business processes. Appendix B gives the list of the Information Exchanges to be covered by a business acknowledgement. Example: If a report of receipt is sent by the MSA of destination to the MSA of dispatch. This is of high importance for the economic operators and deserves a specific detection mechanism. So, an MSA of dispatch receiving a validated report of receipt should acknowledge the receipt of the report of receipt as soon as it has received and identified it. 5.1.7 PR07: Follow-up ‘open’ information If a business process is not completed in due time, a movement may remain in an unsolved state (that is to say, it will never reach a final state such as delivered, cancelled…). To reduce the risk that a movement remains indefinitely open, detection of such cases is necessary. The FESS [R6] provides for some mechanisms to be implemented at international level; it is highly recommended that Member States complete them at national level. Example: If a report of receipt is not submitted by the expected date of delivery, the MSA of dispatch sends a signal to the consignor and to the MSA of destination so that they undertake relevant actions, to establish where and in which state the goods are and to remind the relevant actor that recovery actions are necessary. 5.2 Administrative procedures AP01 Enquire on information AP04 Broadcast information on unavailability AP05 Perform internal controls AP06 Take a business decision AP07 Transfer issue to support AP08 Exchange information outside EMCS Administrative procedures serve the following purposes: � further document an exception after it has been detected; � refer to any procedure which leads to a decision about how to proceed further: asking for more information, asking for a correction; this includes enquiries (if more information is needed) or sharing of information (if other concerned parties must be informed). ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 30 of 53
DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Solution elements In general, when an exception is fully documented, this normally leads to a business decision resulting in the application of a fallback and/or a recovery solution. 5.2.1 AP01: Enquire on information If expected information is not received by an organisation at a specific location, this organisation will enquire on the whereabouts of the missing information. By organisation, one must understand any MSA or any economic operator. This may be achieved, where possible, by using the standard functionality of EMCS such as remote consultation of movement data (UC2.51, UC2.52) or administrative cooperation (UC3.07), but getting information may have to be achieved outside EMCS. Example: If, upon validation of an e-AAD, the excise number of an economic operator is found not existing, it is the responsibility of the consignor to query his partner to get the correct information. 5.2.2 AP04: Broadcast information on unavailability Whenever an actor is unable to communicate with other actors or to perform some functions, that actor should notify that unavailability to its partners, preferably announcing the anticipated time to recover. This allows, in particular, planning interruption of services for maintenance purpose. For what concerns the communication over the Common Domain, this is achieved through a particular use case (UC0.07). It is recommended that each MSA provides for administrative procedures to manage the planned unavailability of economic operators. Example 1: If a given MSA plans an interruption of a part of EMCS functions, it must notify the other Administrations through UC0.07; consequently, the other MSAs have then to take the relevant fallback provisions such as to enqueue all messages they would have to send and adapt the management of deadlines consequently. Example 2: A given MSA may provide that, whenever an economic operator observes that he will not be in a position to submit nor receive electronic messages for a given period, he must notify this to the MSA so that it can take the relevant provisions. This may be a prerequisite for an economic operator using the fallback forms without prior attempt of electronic submission (which does not exempt him from further electronic recovery). 5.2.3 AP05: Perform internal controls Each MSA applies administrative procedures to analyse exceptions after they have occurred, and to determine their cause. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 31 of 53
Page 1 and 2: OWNER DG TAXUD ISSUE DATE 01/12/200
Page 3 and 4: DG TAXUD - EXCISE COMPUTERISATION P
Page 29: DG TAXUD - EXCISE COMPUTERISATION P
Page 53: DG TAXUD - EXCISE COMPUTERISATION P

Fallback and Recovery Specification (FRS)

Create successful ePaper yourself

Delete template?

Save as template?