EDIFACT Guide to GPO message abort at exit of a MRN German Port Order. EDIFACT Guide G P O

Transcription

1 EDIFACT Guide G P O (Abort at exit of an MRN to cancelled GPO order considering the processes for the customs export procedure ATLAS AES) A joint adventure of the ports Bremen/Bremerhaven and Hamburg Version: 2.4 E Function Name Signature on Date Created by C. Wegner on Checked by on Released by on Print File Distributor GPO EDIFACT Abmeldenachricht MRN V2.4e.doc dbh, DAKOSY Effective: Version 2.4 E Page 1 of 25

2 Amendment table Version Amendment type Amended by, date 1.00 Creation of the document ZAPP AES AG Revision; Segment AUT removed Amendments in connection with AES Relase Chr. Wegner Release Layout~;corrections of examples, correctionuns Chr. Wegner (0081 -> D/S) Renaming of the document Chr. Wegner Addition of EORI, cf. SG 6 (2)/NAD, S. 20 J. Diettrich Released by, date ZAPP AES AG Chr.Wegner F. Schwanke This document was created with the word processing programme Microsoft Word The programme GEFEG.FX by GEFEG from Berlin was used for the compilation of the EDIFACT-specific diagrams and tables. Effective: Version 2.4 E Page 2 of 25

3 Table of contents 1 Preface Introduction to version Introduction to version Explanations to the message structure Message composition scheme Explanations to the segment representation Structure of the interchange and description of the service segments Structure of the interchange UNA segment Service String Advice UNB segment Interchange header UNZ segment Interchange trailer GPO shortage in quantity message description of used segments and segment groups Example to GPO message abort at exit Example Deregistration of a MRN...25 Effective: Version 2.4 E Page 3 of 25

4 1 Preface Representatives of the port managements Hamburg and Bremen/Bremerhaven instructed their data processing service providers, the and dbh Datenbank Bremische Häfen AG, Bremen DAKOSY Datenkommunikationssystem AG, Hamburg to create an EDIFACT message, in order to guarantee the standardized data transmission of port order and quay application information (shipping note, port document, etc.) at the ports Bremen/Bremerhaven and Hamburg. The transport sector expects substantial rationalisation benefits for all involved companies by the creation of a standardized interface for the assignment of quay services. This guide describes the shortage in quantity messages to GPO orders in the customs declaration procedure ATLAS AES. (see also ) The descriptions to the GPO are composed of various documents, that either are subsets of the GPO message IFTMIN or represent further processes of the EDI scenario GPO: GPO EDIFACT V1.2.doc as standardized port order for port services, GPO EDIFACT AES V1.1.doc and GPO EDIFACT AES2 V1.1.doc in order to represent different processes in the context of the declaration procedure ATLAS AES; GPO EDI rules and scenarios incl. descriptions of the EDIFACT messages CONTRL and APERAK and GPO EDIFACT AES status messages. Shortage in quantities must be reported by the presentor, if less items are delivered and loaded than specified in the export declaration (AM) incl. cancellation of a whole MRN. The reason behind the shortage doesn t matter for this. Shortage in quantity messages meaning the cancellation of positions- are also required, if delivery of the goods to the port is delayed, which might obstruct the exportation procedure of already delivered consignments, since the customs permission for exportation won t be granted until all goods of a MRN have been arrived at port. The absence of goods positions or packages will be reported to AES, i.e. it will be exactly specified what won t be loaded, in relation to the MRN data. The decreased quantity of packages (in case of shortage in quantity) must be indicated where required, in order that every position is completely qualified in the end. A shortage in quantity must be sent not until after the forwarding of a presentation notification, just as the qualification of packages, Effective: Version 2.4 E Page 4 of 25

5 upcoming for exportation. Shortage in quantities may as well be reported by indicating container numbers; container-related MRN s, positions and pack ID s are then being determined by means of the communication systems DBH/DAKOSY. Every shortage in quantity message, which does not satisfy the above mentioned criteria, will be rejected with an APERAK. You may as well use this message in connection with the classical procedures GM01 and DY01 to indicate a shortage in quantity! 1.1 Introduction to version 2 The net weight provides the basis for shortage in quantity, so no longer the number of packages anymore. This information won t be extracted out of the GPO-message "Mindermenge"/ shortage in quantity anymore (with the ATLAS AES-release for Hamburg port), but out of port interfaces presentation notification GM01, HDS and GPO- Hafenauftrag/ port order. The separate GPO-shortage in quantity message is just required to interrupt an already started exportation procedure to a complete MRN, though not in sense of a cancellation, but to indicate the non-loading at time of the message. This deregistered MRN may be provided again at any customs office of second stage anytime, the surrender of goods is retained. If the goods aren t to be exported, even the MRN has to be deleted by the presentor. 1.2 Introduction to version 2.3 This guide was renamed in order to improve the transparency of the functionality of several guides. The naming shortage in quantity message was misleading since the current message is solely used to abort the already ongoing presentation procedure at the customs office of exit in order to present the goods at another European customs office of exit again. The MRN reverts to the status surrender with the abort at exit. The abort at exit in ZAPP AES requires the prior cancellation of the ZAPP reference (DY01, GM01, GPO). Effective: Version 2.4 E Page 5 of 25

6

7 2 Explanations to the message structure The following table illustrates the structure of the used EDIFACT-message CUSDEC (D.96B). Only used segments, incl. repetition limits compared to the standard, are shown. Structure/ Index Ser. no. Tag Stat. Occ. Contents 01 UNB M 1 INTERCHANGE HEADER 02 UNH R 1 MESSAGE HEADER 03 BGM M 1 Beginning of message SG1 R 1 RFF 04 RFF R 1 MRN SG6 R 1 NAD 05 NAD M 1 TIN of the forwarder SG6 R 1 NAD 06 NAD M 1 Presentor/ forwarder 07 UNS M 1 SECTION CONTROL 08 UNS M 1 SECTION CONTROL 09 UNT M 1 MESSAGE TRAILER 10 UNZ M 1 INTERCHANGE TRAILER Effective: Version 2.4 E Page 7 of 25

8 3 Message composition scheme Only used segments are shown. Level 0 UNB M 1 1 UNH R 1 2 BGM M 1 3 UNS M 1 7 UNS M 1 8 UNT M 1 9 UNZ M 1 10 Level 1 SG1 R 1 RFF R 1 4 SG6 R 1 NAD M 1 5 SG6 R 1 NAD M 1 6 Effective: Version 2.4 E Page 8 of 25

9 4 Explanations to the segment representation The segments are represented according to a consistent scheme. The first (main-) column EDIFACT, with its three subcategories, describes the structure of the used EDIFACT-message. The first column indicates the identifier/ number of the respective composit or data element, the second column indicates the corresponding meaning and the third column refers to the usage and format. The second (main-) column Application / application, with its three subcategories, describes how respective composits and data elements have to be used for the GPO. The first column ST = status means: M (Mandatory) or R (Required) If a composit or data element is already marked as mandatory field (M= mandatory) in the actual EDIFACT-message, the M is going to be carried over in this column. Elsewise the R = Required denotes a required field, from the application s point of view. D (Depending) Data units have to be sent under certain conditions, which are either described in the column Verwendung/Hinweise (use/references) or derive from the application case. Segment group 32 (dangerous goods information), for instance, has got the status D, because the application depends on whether the position/ item is marked as dangerous good or not. Effective: Version 2.4 E Page 9 of 25

10 C (Conditional/Optional) The transfer of data units is left to the sender s own device. In case of doubt alternative arrangements may be agreed between sender and receiver. X (not used) Composits or data elements, which are identified like this, are not being used. The second column contains examples of respective data elements and the third column provides important information for the usage, like e.g.: code indications, port relevant and specific regulations or format restrictions. Effective: Version 2.4 E Page 10 of 25

11 5 Structure of the interchange and description of the service segments 5.1 Structure of the interchange The physical interchange is being limited by the segments UNB and UNZ. UNA UNB Service String Advice Interchange header UNH Message header GPO Status data UNT UNH Message trailer Message header GPO Status data UNT Message trailer UNH Message header GPO Status data UNT Message trailer UNZ Interchange trailer Effective: Version 2.4 E Page 11 of 25

12 5.2 UNA segment Service String Advice Segment: 1 UNA Variant no.: 1 Status: R Max.occ.: 1 Service String Advice EDIFACT UNA UNA1 M an1 COMPONENT DATA ELEMENT SEPARATOR UNA2 M an1 DATA ELEMENT SEPARATOR UNA3 M an1 DECIMAL NOTATION UNA4 M an1 RELEASE INDICATOR UNA5 M an1 RESERVED FOR FUTURE USE UNA6 M an1 SEGMENT TERMINATOR GPO comment: Example S Use/references UNA : R + R, R? R R R Blank/space The use of separators shown in the example is recommended. UNA:+,? ' Effective: Version 2.4 E Page 12 of 25

13 5.3 UNB segment Interchange header Segment: UNB Ser.no..: 1 Level: 0 Status: M Max. occ.: 1 Variant no: 1 Interchange header Description: Interchange header EDIFACT Application Description St Format St Example Use/references S001 Syntax identifier M M 0001 Syntax identifier M a4 M +UNOC UNOC = UN/ECE character set C 0002 Syntax version number M n1 M :3 3 = Version 3 S002 Interchange sender M M 0004 Sender identification M an..35 M The usage of the DAKOSY participant code is recommended. The usage of other identifications are also possible. S003 Interchange recipient M M 0010 Recipient identification M an..35 M +DAK Forwardings within a transmission can only be indicated for Bremen/ Bremerhaven or Hamburg. A mix for the mentioned ports within a transmission (UNB -UNZ) is not possible. DAK = DAKOSY S004 Date/time of preparation M M 0017 Date of preparation M n6 M Time of preparation M n4 M : Interchange control reference M an..14 M +GPO001 This reference must be assigned uniquely. S005 Recipients reference/password X 0022 Recipients reference/password X Application reference X Processing priority code X Acknowledgement request X Communications agreement id X Test indicator C n1 C +1' 1 = Interchange is a test Only specified in case of test interchange. Comment: UNB+UNOC: DAK :1452+GPO ' Effective: Version 2.4 E Page 13 of 25

14 5.4 UNZ segment Interchange trailer Effective: Version 2.4 E Page 14 of 25

15 Segment: UNZ Ser.no..: 149 Level: 0 Status: M Max. occ.: 1 Variant no.: 1 Interchange trailer Description: Interchange trailer EDIFACT Application Description St Format St Example Use/references 0036 Interchange control count M n..6 M +1 Number of messages 0020 Interchange control reference M an..14 M +GPO001' Reference no. as in UNB/0020 Comment: UNZ+1+GPO001' Effective: Version 2.4 E Page 15 of 25

16 6 GPO shortage in quantity message description of used segments and segment groups Segment: UNH Ser.no..: 2 Level: 0 Status: R Max. occ.: 1 Variant no.: 1 Message header Description: Message header EDIFACT Application Description St Format St Example Use/references 0062 Message reference number M an..14 R +1 This reference must be assigned uniquely S009 Message identifier M M 0065 Message type M an..6 R +CUSDEC CUSDEC = Customs declaration 0052 Message version number M an..3 R :D D = Draft version 0054 Message release number M an..3 R :96B 96B = Release B 0051 Controlling agency M an..2 R :UN UN = UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) 0057 Association assigned code C an..6 R :DEGPO1' DEGPO1 = GPO AES (Germ an Port Order for the transmission of quay orders ff in the customs declaration procedure AES) Comment: UNH+1+CUSDEC:D:96B:UN:DEGPO1' Effective: Version 2.4 E Page 16 of 25

17 Segment: BGM Ser.no..: 3 Level: 0 Status: M Max. occ.: 1 Variant no.: 1 Beginning of message Description: Beginning of message EDIFACT Application Description St Format St Example Use /references C002 Document/ Message name C R 1001 Document name code C an..3 R = cargo declaration (departure) Generic term for documents/ messages which contain particulars (requested from customs administration) about the loading, carried with industrial means of transport (cargo); sometimes also referred to as presentation notification, here in the sense of the nonpresentation. C106 Document message C R identification 1004 Document identifier C an..35 R +BGM reference 1056 Version C an..9 R :GPO01' Comment: BGM+833+BGM Referenz:GPO01' Effective: Version 2.4 E Page 17 of 25

18 Group: SG1 Status: R Max.occ.: 1 RFF Variant no.: 1 Only the abort at exit may be reported within the transmission to a MRN. Segment: RFF Ser.no..: 4 Level: 1 Status: R Max. occ.: 1 Variant no.: 1 References Description: MRN EDIFACT Application Description St Format St Example Use/references C506 Reference M R 1153 Reference code qualifier M an..3 M +ED 1154 Reference identifier C an..35 R : 07DE E0' Comment: Transmission of MRN to be aborted at exit. RFF+ED: 07DE E0' Attention, modified format: ZAPP = an18 Number of export declaration = MRN, MRN an18 (year (00-99) (n2) Country id DE' (a2) Office number ATLAS (n4) Serial number (n8) Technical procedure code E' (a1) Check digit (n1) Effective: Version 2.4 E Page 18 of 25

19 Group: SG6 Status: R Max. occ.: 1 NAD Variant no: 1 Segment: NAD Ser.no..: 5 Level: 1 Status: M Max. occ.: 1 Variant no.: 1 Name and address Description: TIN of the forwarder EDIFACT Application Description St Format St Example Use/references 3035 Party function code qualifier M an..3 M +RL Format an2 C082 Party identification details C R 3039 Party identifier M an..35 M ' Format n7 TIN (customs number) of the sender Comment: NAD+RL ' Effective: Version 2.4 E Page 19 of 25

20 Group: SG6 Status: R Max. occ.: 1 NAD Variant no: 2 Segment: NAD Ser.no..: 5 Level: 1 Status: M Max. occ.: 1 Variant no.: 1 Name and address Description: EORI of the forwarder EDIFACT Application Description St Format St Example Use/references 3035 Party function code qualifier M an..3 M +RL Format an2 C082 Party identification details C R 3039 Party identifier M an..35 M E Identifier E for EORI C058 Name and address C R 3124 Name and address line M an..35 M +DE EORI an Name and address line C an..35 O : 0000 Branch no. (n4) Comment: NAD+RL+E+DE :0000' Effective: Version 2.4 E Page 20 of 25

21 Group: SG6 Status: R Max. occ.: 1 NAD Variant no: 3 Segment: NAD Ser.no.: 6 Level: 1 Status: M Max. occ.: 1 Variant no: 1 Name and address Description: Presentor/forwarder EDIFACT Application Description St Format St Example Use/references 3035 Party function code qualifier M an..3 M +MS Format an2 C082 Party identification details C R 3039 Party identifier M an..35 M +DAK' DAKOSY participant code Comment: NAD+MS+DAK' Effective: Version 2.4 E Page 21 of 25

22 Segment: UNS Ser.no.: 7 Level: 0 Status: M Max. occ.: 1 Variant no.: 1 Section control Description: Section control EDIFACT Application Description St Format St Example Use/references 0081 Section identifier, coded M a1 M +D' Comment: UNS+D' Effective: Version 2.4 E Page 22 of 25

23 Segment: UNS Ser.no.: 8 Level: 0 Status: M Max. occ.: 1 Variant no: 2 Section control Description: Section control EDIFACT Application Description St Format St Example Use/references 0081 Section identifier, coded M a1 M +D' Comment: UNS+S' Effective: Version 2.4 E Page 23 of 25

24 Segment: UNT Ser.no.: 9 Level: 0 Status: M Max. occ.: 1 Variant no: 1 Message trailer Description: Message trailer EDIFACT Application Description St Format St Example Use/references 0074 Number of segments in the M n..6 M +24 Format n..6 message 0062 Message reference number M an..14 M +1' Format n..6 Comment: UNT+8+1' Effective: Version 2.4 E Page 24 of 25

25 7 Example to GPO message abort at exit 7.1 Example Deregistration of a MRN Ser.no. Name Example 1 UNB UNB+UNOC: DAK :1452+GPO ' 2 UNH UNH+1+CUSDEC:D:96B:UN:DEGPO1' 3 BGM BGM+833+BGM Referenz:GPO01' SG1 4 RFF RFF+ED:10DE E0' SG6 5 NAD NAD+RL ' SG6 6 NAD NAD+MS+DAK' 7 UNS UNS+D' 8 UNS UNS+S' 9 UNT UNT+8+1' 10 UNZ UNZ+1+ GPO001' Effective: Version 2.4 E Page 25 of 25