8 10 15/04/2005 Implementing QA verification comments. Re-submitted for Acceptance to Taxation and Customs Union DG. I/R ECS & NCTS Appendices 0 10 05/03/2007 Restructure of DDNTA into DDNA with separate volumes for Common and specific Customs Domains. I All 0 20 23/03/2007 Implementing internal review comments. Submitted for review to Taxation and Customs Union DG. I/R As Required 1 00 09/05/2007 Implementing QA review comments. Submitted for acceptance to Taxation and Customs Union DG. I/R As Required 1 10 11/05/2007 Implementing verification comments. Re-submitted for acceptance to Taxation and Customs DG. I/R As Required 2 00 28/09/2007 Implement ECG Review comments. Submitted for acceptance to Taxation and Customs DG. I/R As Required 2 10 17/02/2008 DDCOM update for ICS domain Submitted for review to Taxation and Customs Union DG. I/R As Required 3 00 19/02/2008 Implementing review comments. Submitted for acceptance to Taxation and Customs Union DG. I/R As Required 3 10 09/06/2008 Incorporating RFA 816 functionality. Submitted for review to Taxation and Customs Union DG. I/R Section II:, IV.2, VIII.2.17, VIII.4.12 4 00 25/06/2008 Implementing review comments. Submitted for acceptance to Taxation and Customs Union DG. I/R As Required 4 10 28/10/2008 Incorporating RFA 848 functionality for the incorporation of EOS in DDCOM. Implementing DDNA KEL v0.18. Implementing calls INC0807.109564 and INC0809.111672. Submitted for review to Taxation and Customs Union DG. I/R Section I.1.1, I.1.2, I.1.8, II.2.1.1, V.2, V.3.1, V.4, VII.4, VII.5.1, VII.5.2, VII.5.6, VII.5.7, VIII.2.6, VIII.2.17, VIII.4.10 5 00 18/11/2008 Implementing review comments. I/R As Required
Submitted for review to Taxation and Customs Union DG. 7 00 01/02/2010 Implementing review comments. Submitted for acceptance to Taxation and Customs Union DG. I,R As Required 7 10 15/04/2010 Implementing ECG review comments. Submitted for review to Taxation and Customs Union DG. I,R As Required 8 00 20/04/2010 Implementing verification comments. Submitted for acceptance to Taxation and Customs Union DG. I,R As Required 9 00 28/02/2011 Project and contractual data is updated. Aligned with KEL 0.23 and review comments implemented. Submitted for review&acceptance to Taxation & Customs DG. I/R Sections: VII.3, I.1.8, I.3, V.2.1.1.1, VII.6.1 9 10 01/02/2012 Project and contractual data updated. Aligned with KEL 0.24. Submitted for review to Taxation and Customs Union DG. I/R Sections: I.1.8.4, I.3.1.1, I.3.2, V.2.1.2.1.2, V.2.1.2.2 10 00 22/02/2012 The review comments are implemented. Submitted for acceptance to Taxation and Customs Union DG. I/R As Required 10 01 26/03/2012 Aligned with KEL 0.23a. Sent to the internal and language review. I/R Sections: I.1.8.5, V.2.1.2.1.1, V.2.1.2.2 10 10 30/03/2012 Comments from the internal and language review are implemented. Submitted for review to Taxation and Customs Union DG. I/R As Required 10 50 27/04/2012 Submitted for acceptance to Taxation and Customs DG. I 6 10 60 24/07/2012 Project and contractual data updated. Aligned with KEL 0.25. WARNING: This and the next version do NOT include the changes for KEL v0.24a. Submitted for review to Taxation and Customs Union DG. I/R Sections: I.1.8.7, I.3.2, VII.1.2 11 00 20/08/2012 The review comments are implemented. I/R Page 71
transition is performed and the message B is sent. Please note that only the IE numbers shall be used in the state transitions. In the example above (which is part of the State Transition Diagram for the Office of Export up to the release of movement), the transition from “Accepted” to “Declaration under amendment” is triggered by the reception of a Declaration Amendment (IE513) message and if the Declaration Amendment is “invalid”. As a result, an Amendment Rejection IE505 message is sent back from Office of Export to the Trader. When multiple messages are sent as a consequence of an event, a dot sign will separate these multiple messages (“.”). This dot sign needs to be understood as a logical AND. Data Dictionary The data dictionary, contained within this DDNA, defines: Data Items; Data Groups; Code lists (sets of discrete values). A number of naming and spelling conventions and rules have been maintained for these throughout this DDNA. Data Items Every name shall start with a capital (uppercase) letter. name can contain letters, digits, and a number of additional characters: the space character, the brackets “(“ and “)”, the ampersand character “&”, the underscore “_”, and the slash character “/”. No other characters are allowed. Within the name, lowercase letters preferably be used (except for the first character and except for abbreviations that will always be in uppercase). Data Groups Every name shall start with a letter. Every name can contain letters, digits, and a number of additional characters: the space character, the brackets “(“ and “)”, the ampersand character “&”, the underscore “_”, and the slash “/”. No other characters are allowed. Only uppercase letters are allowed. Code lists The same rules as for Data Items will apply.
IE412 and IE919. In addition different URIs will be also available for downloads related to each Customs system. Figure 14: Downloading from CS/MIS Uploading to CS/MIS In to perform an upload the user sends the data to the CS/MIS application (IE070 in the example below). The (NA local) file to be uploaded is chosen through the GUI. Different URIs will be available at CS/MIS for upload of IE411 and IE912. In addition different URIs will be also available for uploads related to each Customs system. Figure 15: Uploading an IE070 CS/MIS manual mode of operation A browser interface enables the download of an and an IE412 in a manner similar to the CS/RD application. Distinct download links will be available for each Customs system. Message exchanges with CS/MIS via CCN/CSI This section deals with the IE411, the CCN/CSI technical statistics, the CCN/CSI audit files and the exchange of MRN Follow up queries and responses. Sending IE411 data to CS/MIS The IE411 message has EDIFACT or XML as its format and is either sent to the CS/MIS application across CCN/CSI or it is manually uploaded on CS/MIS Web interface. CS/MIS at ITSM has a dedicated address on the CCN/CSI network and a dedicated queue for capturing the business statistics. If the message is sent to the CS/MIS application across CCN/CSI, in the message descriptor the value ‘CSIMQMT_DATAGRAM’ must be used for the data element ‘MsgType’.
The following may be used to deal with the “Obj” queue contents: Class of verbs Verb Usage queue HL_mq_close() Mandatory. write in queue HL_mq_put() Mandatory (see also VIII.2.14 however). read from queue HL_mq_browse Mandatory delete from queue HL_mq_delete Mandatory. A message must have been successfully read and processed before deleting. 28: CSI verbs for queue access It is the responsibility of the application to organise the reading from a receiving queue in order to avoid loss of messages. Putting a message into a queue: HL_mq_put() CSILONG HL_mq_put( CSIMQHCONN Conn, CSIMQHOBJ ObjDesc, CSIMQMD *MsgDesc, CSIMQPMO *PutMsgOpts, CSIDD *DataIn, CSIQOS *QoS, CSILONG *ReturnCode, CSILONG *ReasonCode ); Value of argument “Conn” is identical to the one obtained from HL_mq_conn(). Value of argument “Obj” is identical to the one obtained from HL_mq_open(). Argument “MsgDesc” points to a CSIMQMD structure that was prepared as explained in paragraph VIII.2.1. The values present in this structure a successful call of the HL_mq_put() are not to be considered. Argument “DataIn” points to a CSIDD structure that was prepared as explained in paragraph VIII.2.2. Argument “QoS” points to a CSIQOS structure that was prepared as explained in section VIII.2.6. Argument “PutMsgOpts” is to be initialised with the statements: Define a static variable s_DefMQPMO of type CSIMQPMO initialised with constant values: CSIMQPMO s_DefMQPMO = {CSIMQPMO_DEFAULT}; Each time the HL_mq_put() verb will be used, define and initialise dynamically a variable s_MQPMO of type CSIMQPMO by using the static variable s_DefMQPMO :