Structure / Table of Contents

Transcription

1 Structure / Table of Contents Counter No Tag St MaxOcc Level Content UNB M 1 0 Interchange header UNG M Functional group header UNH M 1 0 Message header BGM M 1 0 Beginning of message DTM M 1 1 Date/time/period RFF C Client Supplied Reference ID/Related Document 0170 SG3 C 9 1 Port of Release/Government Details GOR M 1 1 Governmental requirements LOC C 1 2 Port of Release/Inspection Location 0200 SG4 C 9 2 PGA Contact CTA M 1 2 Contact information COM C 3 3 Communication contact 0230 SG5 C 1 1 Notice Reason Code STS M 1 1 Status 0290 SG7 C 98 1 Notice Recipient NAD M 1 1 Notice Recipient 0380 SG9 C Issued/Modified LPCOs DOC M 1 1 Document/message details 0550 SG13 C 1 1 Free Text Requests/Errors/Instructions RCS M 1 1 Notice Originator FTX M 99 2 Request Details 0690 SG17 C 99 1 Error Details ERC M 1 1 Application error information 0710 SG18 C ERP ERP M 1 2 Error point details 1320 SG32 C 1 1 Conveyance Arrival Date/Location TDT M 1 1 Transport information 1490 SG34 M 1 2 Port of Report LOC M 1 2 Port of Report SEQ M 1 3 Sequence details 1880 SG41 C Container Details EQD M 1 2 Equipment details SEQ M 1 3 Sequence details UNS M 1 0 Section control HYN M 1 0 Hierarchy information UNS M 1 0 Section control UNT M 1 0 Message trailer UNE M 1 0 Functional group trailer UNZ M 1 0 Interchange trailer ; 3.3; D4 Date: 08/10/2014 Page: 1 / 34

2 Segments UNB M 1 0 Interchange header UNB S001 Syntax identifier 010 M M 0001 Syntax identifier 1 M a4 M a4 Code identification of the Agency controlling syntax. Please note that the CBSA does NOT support the entire UNOC character set. Due to technical limitations, the CBSA only supports the UNOA character set with the sole addition of the "@" symbol. The UNOC code value is provided here to allow TCPs to process CBSA messages without character set exception handling. UNOC UN/ECE level C 0002 Syntax version number 2 M n1 M n1 Version number of the syntax. 3 Version 3 S002 Interchange sender 020 M M 0004 Sender identification 3 M an..35 M an..35 Name/coded representation of the recipient. (CBSA Network ID) 0007 Partner identification code qualifier 4 C an..4 C an..4 S003 Interchange recipient 030 M M 0010 Recipient identification 5 M an..35 M an..35 Name/coded representation of the sender. (Client s Network ID) 0007 Partner identification code qualifier 6 C an..4 C an..4 S004 Date/time of preparation 040 M M 0017 Date of preparation 7 M n6 M n6 Generated by Translator 0019 Time of preparation 8 M n4 M n4 Generated by Translator 0020 Interchange control reference 050 M an..14 M an..14 Unique Reference Number assigned by the sender. Note the size of the entire interchange message cannot exceed 4MB UNB+UNOC:3+CBSANETID:ZZ+CLIENTNETID:ZZ :1553+X' ; 3.3; D4 Date: 08/10/2014 Page: 2 / 34

3 UNG M Functional group header UNG 0038 Functional group identification 010 M an..6 M an..6 GOVCBR Identification of the one type of message in the Functional Group 020 M M S006 Application sender's identification 0040 Sender identification 2 M an..35 M an..35 Client's Transmission Site CCR = Canada Customs Response S007 Application recipient's 030 M M identification 0044 Recipient's identification 3 M an..35 M an..35 Defined by client Partner identification code 4 C an..4 O an..4 Application Receiver ID Qualifier (Optional) qualifier S004 Date/time of preparation 040 M M 0017 Date of preparation 5 M n6 M n6 Generated by Translator 0019 Time of preparation 6 M n4 M n4 Generated by Translator 0048 Functional group reference 050 M an..14 M an..14 Unique Reference Number assigned by the sender. number 0051 Controlling agency 060 M an..2 M an..2 Agency controlling the message type. UN UN/CEFACT S008 Message version 070 M M 0052 Message version number 9 M an..3 M an..3 Version number of the message type. D Draft version/un/edifact Directory 0054 Message release number 10 M an..3 M an..3 Release number of the message type. 13A Release A UNG+GOVCBR+CCR+IIDT: : UN+D:13A' ; 3.3; D4 Date: 08/10/2014 Page: 3 / 34

4 UNH M 1 0 Message header UNH 0062 Message reference number 010 M an..14 M an..14 Unique Reference Number assigned by the sender. S009 Message identifier 020 M M 0065 Message type 2 M an..6 M an..6 Identification of the message type. GOVCBR Government cross border regulatory message 0052 Message version number 3 M an..3 M an..3 Version number of the message type. D Draft version/un/edifact Directory 0054 Message release number 4 M an..3 M an..3 Release number of the message type. 13A Release A 0051 Controlling agency 5 M an..2 M an..2 Agency controlling the message type. UN UN/CEFACT 0068 Common access reference 030 C an..35 C an..35 This field indicates which notice type was used to produce the message. SWI131 This IID response is aligned with v1.31 of the SWI ECCRD (published on March ) SWI210 This IID response is aligned with v2.1 of the SWI ECCRD (published on July ) ECRD40 E-Manifest Customs Reponse DRAFT Message D4.0 version UNH+1234+GOVCBR:D:13A:UN+ECRD40' ; 3.3; D4 Date: 08/10/2014 Page: 4 / 34

5 BGM M 1 0 Beginning of message BGM C002 Document/message name 010 C M 1001 Document name code 1 C an..3 M an..3 CBSA Message Type This element provides the overall type of message that is being transmitted. The following qualifiers indicate the specific response or notice that is being transmitted by the CBSA. 23 Status information A CBSA-initiated message indicating that some event affecting a previously submitted document status has occurred. Please refer to SG5 for information on each potential status that could be issued. 312 Acknowledgement message Positive application acknowledgement message provided in response to an inbound submission. This indicates the inbound transaction has successfully passed all validation verifications. No error codes will be present. 313 Application error message Negative application acknowledgement message provided in response to an inbound submission. This is primarily due to the submission of a document that fails CBSA validation. Other situations that can generate this status include a "blocking" SWI-RFI (that is, a request for additional information from a PGA that must be fulfilled by a resubmission of a document). SG17 and SG13 may both contain detailed information in this situation. 961 General response (Customs) This qualifier indicates that a functional acknowledgement (either positive or negative) of syntactical accuracy of the transaction submitted is being provided. Please refer to SG5 to determine whether or not this is a positive (the message was syntactically correct) or negative (the message contained one or more syntax errors outlined in SG13). 962 Document response (Customs) This is a warning for situations which may be cause for concern. Details of any information requests can be found in SG13, and warnings can be found in SG17. Examples could include: insufficient review time warning, or a PGA warning message informing clients of insufficient documentation. ; 3.3; D4 Date: 08/10/2014 Page: 5 / 34

6 IID - Specific Status: 965 Tax calculation/confirmation response (Customs) For goods subject to Canadian supply management (quotas), this message indicates whether an application (or reference to) a low duty rate was successful. Please refer to SG5 for more information in this situation Code list identification code 2 C an..17 N Not used 3055 Code list responsible 3 C an..3 N Not used agency code 1000 Document name 4 C an..35 C an..35 C106 Document/message identification 020 C M 1004 Document identifier 5 C an..70 M an..70 CBSA Reference Number Unique Document Identifier from the document that triggered the response message. For a Release message this will be the 14-digit client-supplied transaction number submitted with the original release. For a Cargo or House Bill message, this will be the carrier code plus the Cargo Control Number Version identifier 6 C an..9 M an Revision identifier 7 C an..6 M an..3 For House Bill Close Message, this number will appear as the carrier code of the freight forwarder, followed by the Previous Cargo Control Number. The number in a sequence of multiple outbound response messages triggered by a single event. Examples: If this is the third in a series of 5 messages in response to a single event, the number displayed will be "3". If there is only one outbound response message for the event, the number displayed will be "1". The total number outbound response messages triggered by a single event. Examples: If there are a total of 5 messages in response to a single event, the number displayed will be "5". If there is only one outbound response message for the event, the number displayed will be "1" Message function code 030 C an..3 M an..3 CBSA Message Function, coded Indicate response message function CBSA Message Function, coded 11 Response BGM+312::: XXXXXXXXXXX:1:1+11' ; 3.3; D4 Date: 08/10/2014 Page: 6 / 34

7 DTM M 1 1 Date/time/period DTM C507 Date/time/period 010 M M 2005 Date or time or period 1 M an..3 M an..3 9 Processing date/time function code qualifier 2380 Date or time or period text 2 C an..35 M an..17 Response Date/Time Date/Time of the outbound response notice from CBSA in Eastern Time 2379 Date or time or period format code 3 C an..3 M an CCYYMMDDHHMMSS DTM+9: :204' ; 3.3; D4 Date: 08/10/2014 Page: 7 / 34

8 RFF C Client Supplied Reference ID/Related Document RFF C506 Reference 010 M M 1153 Reference code qualifier 1 M an..3 M an..3 Only one AGO (from the Primary Notify Party) or AFM (the Notice Recipient) will be transmitted per message. AGO Sender's reference to the original message This qualifier will be sent to the primary recipient (original submitter) of the message. If this qualifier is present, then 1154 will contain the transactional reference present on the original inbound transaction at location RFF.1154 using qualifier ABO. No other RFF segments will appear if AGO is transmitted. ACE Related document number If this qualifier is present, then 1154 will contain the related reference to another document. For example the CCN that is related to a release. The RFF segment will repeat if there are multiple related documents Reference identifier 2 C an..70 M an..60 Secondary Business Identifier Secondary Business ID based on the source document. It is used only for an AGO-qualified instance of this segment. CBSA Related Reference Number The Reference ID of the related document. Only provided when not quoted on the primary document. Example of Related Reference ID: Transaction number of the PARS where a MATCHED or Document Not On File notice of a related CCN is sent to a carrier This segment contains business references that the recipient can use to link this response to an original transmission in their system, or trade chain partner's system. The Secondary Business ID of the Primary Notify Party is returned to the originator of the related inbound message, as transmitted on the inbound RFF.ABO (Originator's reference). Used to indicate the related trade document(s). For Example, if the inbound transmission is a non-consolidated CCN and STS Status Code = 0001 Matched, then the Related Number will be a Release transmission. RFF+ACE:2XXXCCN' RFF+AGO:SECONDARY BUSINESS ID' ; 3.3; D4 Date: 08/10/2014 Page: 8 / 34

9 0170 SG3 C 9 1 Port of Release/Government Details For CBSA purposes this segment indicates the Port of Release. This segment group also provides a list of all PGAs, and potentially contact information, that were involved in making a compliance decision on this shipment for the purpose of following up directly with each PGA if necessary GOR M 1 1 Governmental requirements GOR 8323 Transport movement code 010 C an..3 N Not used C232 Government action 020 C M 9415 Government agency identification code 2 C an..3 M an..3 Government Details This element indicates which government party is involved in the notice. 1 CFIA (Canadian Food Inspection Agency) 3 DFATD (Department of Foreign Affairs, Trade and Development) 5 Customs 12 HC (Health Canada) 13 TC (Transport Canada) 20 DFO (Department of Fisheries and Oceans) 21 NRCan (Natural Resources Canada) 22 EC (Environment Canada) 23 PHAC (Public Health Agency of Canada) 24 CNSC (Canadian Nuclear Safety Commission) 9411 Government involvement 3 C an..3 N Not used code 9417 Government action code 4 C an..3 N Not used 9353 Government procedure code GOR++5:::4' 5 C an..3 C an..3 This segment will not appear if CBSA is provided in Future Use: This field is intended to allow PGAs to communicate to TCPs when special inspection arrangements (that may have been communicated through the SG3. LOC segment in the original IID) have been completed from the GoC side. 4 Inspection arrangements completed ; 3.3; D4 Date: 08/10/2014 Page: 9 / 34

10 0170 SG3 C 9 1 Port of Release/Government Details For CBSA purposes this segment indicates the Port of Release. This segment group also provides a list of all PGAs, and potentially contact information, that were involved in making a compliance decision on this shipment for the purpose of following up directly with each PGA if necessary LOC C 1 2 Port of Release/Inspection Location LOC 3227 Location function code qualifier 010 M an..3 M an..3 For customs notices this segment indicates the port where the goods were released. 23 Port of release 22 Customs clearance location Future Use: This segment will also allow PGAs to confirm the site selected for prearranged examinations. 87 Place/port of conveyance initial arrival 172 Reporting location C517 Location identification 020 C C 3225 Location identifier 2 C an..35 C an4 CBSA port code will be provided here(see ) for fulsome list). Future Use: This segment will also allow PGAs to confirm the site selected for pre-arranged examinations. Port of Report CBSA office code for port of report CBSA office code for port of Report- used for Status Code = Reported Port of Release CBSA office code for port of Release- used for Status Code = Released Port of Arrival CBSA office code for port of arrival - used for Status Code = Arrived C519 Related location one identification 030 C C 3223 First related location identifier 3 C an..35 C an4 CBSA sublocation code will be provided here(see Appendix G2 for fulsome list) Code list identification code 4 C an..17 N Not used 3055 Code list responsible 5 C an..3 N Not used agency code 3222 First related location name 6 C an..70 C an..70 This segment will not appear if CBSA port is provided. Future Use: Examination Location Name If the inspection site is not a coded CBSA port or sublocation, a text description of the location will be provided in this field. Alternatively, this field can be used to ; 3.3; D4 Date: 08/10/2014 Page: 10 / 34

11 further qualify the existing port or sublocation provided in other fields. Future Use: Inspection Location details have not been implemented. LOC :::WEST PADDOCK' ; 3.3; D4 Date: 08/10/2014 Page: 11 / 34

12 0200 SG4 C 9 2 PGA Contact This segment may be used by PGAs to provide a contact who has knowledge of this particular shipment CTA M 1 2 Contact information CTA 3139 Contact function code 010 C an..3 C an..3 IC Information contact C056 Contact details 020 C C 3413 Contact identifier 2 C an..17 N Not used 3412 Contact name 3 C an..256 C an..70 PGA Contact Name Party to contact for follow up inquiries if required. CTA+IC+:CONTACT NAME' ; 3.3; D4 Date: 08/10/2014 Page: 12 / 34

13 0200 SG4 C 9 2 PGA Contact This segment may be used by PGAs to provide a contact who has knowledge of this particular shipment COM C 3 3 Communication contact COM C076 Communication contact 010 M M 3148 Communication address identifier 1 M an..512 M an..50 Communication Details The phone/fax/ contact of a PGA Communication means type code 2 M an..3 M an..3 TE Telephone EM Electronic mail FX Telefax Communication Detail Type The available methods to contact a PGA for further information. COM :TE' ; 3.3; D4 Date: 08/10/2014 Page: 13 / 34

14 0230 SG5 C 1 1 Notice Reason Code This segment group contains more detailed "sub-status" codes for messages that require further qualification beyond the qualifier at the BGM level. This segment group is currently only populated for BGM.1001 qualifiers of { 23, 961, 965 } STS M 1 1 Status STS C601 Status category 010 C N 9015 Status category code 1 M an..3 N Not used C555 Status 020 C M 4405 Status description code 2 M an..3 M an..3 Required for syntax purposes 2 Done 1131 Code list identification code 3 C an..17 N Not used 3055 Code list responsible 4 C an..3 N Not used agency code 4404 Status description 5 C an..35 M an..35 Notice Reason Code The code provided in this field indicates what type of status is being conveyed in this message to further qualify the type described in CBSA Message Type element. For example, it provides additional information based on the Notice Type, e.g. for Completeness Status Notice this would tell the client Matched, Not Matched etc. The code provided in this field indicates what type of status (the "sub-status") is being conveyed in this message to further qualify the type described in BGM.1001: The following codes are used with BGM.1001 type 23 only. For a detailed list, please refer to Code Table XXX Matched Matched is a completeness status notice that indicates that a specific trade document is linked to all of its directly related trade documents Not matched A document is captured but is missing one or more related documents. This can also occur if a related document is now considered not in good standing (e.g., a related cargo was cancelled) Cargo Complete Cargo Complete is a new completeness status notice that indicates that a non-consolidated primary cargo document has been transmitted to the CBSA and accepted. If consolidated, it indicates that all of the ; 3.3; D4 Date: 08/10/2014 Page: 14 / 34

15 related secondary cargo (i.e. House Bills) is transmitted as well. ; 3.3; D4 Date: 08/10/ Document Package Complete Document Package Complete is a new completeness status notice that indicates that a primary cargo document and all its related trade documents have been transmitted to the CBSA and accepted. This applies to both consolidated and non-consolidated cargo and includes House Bills Document Not on File Document Not on File is a new completeness status notice that indicates to a carrier that a cargo control number containing the carrier s carrier code was quoted on a trade document which has been submitted. This could be e.g. a release or ATD, but note that Document Not on File would not relate to a conveyance quoting a CCN that is not on file Reported The Reported notice is a status notice which provides information regarding the status on a submitted document post/at arrival Arrived The Arrived notice is a status notice that informs clients that their cargo and/or conveyance has arrived at its Port of Destination Released The Released notice informs clients that their goods have cleared CBSA processing Authorized to Deliver The Authorized to Deliver notice that informs clients that their CSA goods can be delivered to the intended recipient Held for CBSA Informs clients that cargo is being held for further determination/processing and cannot be released. The following codes are used with BGM.1001 type 961 only. C001 Positive functional acknowledgement The inbound transmission was syntactically correct and a positive functional acknowledgement message is being provided in response. No error codes will be present. C002 Negative functional acknowledgement One or more syntax errors were found in the submitted document and a negative functional acknowledgement message is being provided in response. Detailed information for each error can be found in SG13.FTX. The following codes are used with BGM.1001 type Page: 15 / 34

16 965 only. S003 Preferential quota rate accepted The tariff quota rate referred to by the IID has been accepted by the PGA responsible for supply management of the commodity. This can be a result of many business processes including, but not limited to: a shipment-permit application being successful, a permit reference (whether GIP or not) being deemed appropriate or an alternative quota quantity application being successful. S004 Preferential quota rate rejected The tariff quota rate referred to by the IID has been rejected by the PGA responsible for supply management of the commodity. Please refer to SG17 for more detailed error codes surrounding this rejection. If uncorrected before then, the default tariff rate(s) will apply when this IID is acquitted. STS++2:::0001' ; 3.3; D4 Date: 08/10/2014 Page: 16 / 34

17 0290 SG7 C 98 1 Notice Recipient NAD M 1 1 Notice Recipient NAD 3035 Party function code qualifier 010 M an..3 M an..3 Notice Recipient Type The Client Type of the recipient of the notice. This will contain one of the following qualifiers indicating to what type of party this is directed: IM Importer CB Customs broker CA Carrier FW Freight forwarder WH Warehouse Operator C082 Party identification details 020 C M 3039 Party identifier 2 M an..35 M an..15 Mandatory if segment is provided Notice Recipient The client to whom the outbound transmission from CBSA is directed. When AFM qualifier is used, this field contains the CBSA identifier of the party that is to receive the electronic notification, for example an automated status notification. The Notice Recipient information identifies the party to whom the notice is directed. NAD+CA+2XXX' The following information will be supplied in this field for each respective Notice Recipient type identified in 1156: CA/FW 4-character CBSA carrier code. CB 5-digit Account Security Number. WH 4-digit CBSA Sub-location/Warehouse code. IM 15-digit CRA Business Number. ; 3.3; D4 Date: 08/10/2014 Page: 17 / 34

18 0380 SG9 C Issued/Modified LPCOs The IID (Integrated Import Declaration) supports the electronic application for, or modification of, a limited number of LPCOs (licenses, permits, certificates and other documents). This segment group contains all LPCOs that were successfully granted, or had modifications successfully performed to, as a result of an IID submission DOC M 1 1 Document/message details DOC C002 Document/message name 010 M M 1001 Document name code 1 C an..3 M an Related document Required for syntax purposes (mandatory trigger segment) 1131 Code list identification code 2 C an..17 C an..17 Canadian Document Type One of the following LPCO identifiers will be provided: One of the following LPCO identifiers will be provided: 2001 DFATD - Clothing & Textiles - Clothing & Textiles Shipment-Specific Permit 2003 DFATD - Agriculture Products - Agriculture Products Shipment-Specific Permit Electronic permit modifications are only supported by DFATD at this time. C503 Document/message details 020 C M 1004 Document identifier 3 C an..70 M an..40 LPCO Reference Number The unique identification number for this LPCO that distinguishes it from others of the same type will be provided here. DOC+916:2001+9XXX1234' For newly-granted DFATD shipment-specific permits, this field will contain the permit number (EICS-II Reference Number), which can be used in subsequent IID submissions. For Documented Alternative Quota Quantity modifications requested, this field will contain the permit number (EICS-II Reference Number) which had the modifications performed to. ; 3.3; D4 Date: 08/10/2014 Page: 18 / 34

19 0550 SG13 C 1 1 Free Text Requests/Errors/Instructions This segment group is populated under the following circumstances: 1. When the inbound transmission fails to pass syntax validation by the CBSA message translator. 2. When providing Special Instructions from the inbound release document. 3. When a PGA or the CBSA has requested that additional information be provided for a message. If multiple PGAs have issued requests, multiple messages will be used instead of adding additional occurances to this group RCS M 1 1 Notice Originator RCS 7293 Sector area identification 010 M an..3 M an Government code qualifier C550 Requirement/condition identification 020 C M 7295 Requirement or condition 2 M an..17 M an Service provider determined service description identifier 1131 Code list identification code 3 C an..17 N Not used 3055 Code list responsible agency code 4 C an..3 M an..3 Government Details This element indicates which government party is involved in the notice. 1 CFIA (Canadian Food Inspection Agency) 3 DFATD (Department of Foreign Affairs, Trade and Development) 5 CBSA 12 HC (Health Canada) 13 TC (Transport Canada) 20 DFO (Department of Fisheries and Oceans) 21 NRCan (Natural Resources Canada) 22 EC (Environment Canada) 23 PHAC (Public Health Agency of Canada) 24 CNSC (Canadian Nuclear Safety Commission) Indicate whether the CBSA or identified PGA has sent the request for additional information Required for syntax purposes (mandatory trigger segment) RCS+15+1::5' ; 3.3; D4 Date: 08/10/2014 Page: 19 / 34

20 0550 SG13 C 1 1 Free Text Requests/Errors/Instructions This segment group is populated under the following circumstances: 1. When the inbound transmission fails to pass syntax validation by the CBSA message translator. 2. When providing Special Instructions from the inbound release document. 3. When a PGA or the CBSA has requested that additional information be provided for a message. If multiple PGAs have issued requests, multiple messages will be used instead of adding additional occurances to this group FTX M 99 2 Request Details FTX 4451 Text subject code qualifier 010 M an..3 M an..3 AAO Error description (free text) This qualifier indicates an error on the inbound transmission. A subsequent transmission will be required to resolve the situation. AFL Review comments This qualifier indicates an issue or concern that may cause compliance activities or consequences postborder if not rectified by a subsequent version of the inbound document being submitted. SIN Special instructions Special Instructions from the inbound release document Free text function code 020 C an..3 N Not used C107 Text reference 030 C N 4441 Free text description code 3 M an..17 N Not used C108 Text literal 040 C M 4440 Free text 4 M an..512 M an..512 Note/Special Instruction Additional information based on the Notice Type Information in a free text format, if necessary, for comment or special instruction. (E.g. for an RFI this might provide additional information as to why a client is receiving an RFI.) For BGM Type 961, functional reject text will appear in the following format: Multiple occurrences are used to provide multiple lines of information for complex requests. FTX+AAO+++DATA ELEMENT IN ERROR OR BSO TEXT' FTX+AAO+++SEGMENTUNS-BYTE OFFSET67:MAND SEG MISSING FTX+AFL+++OFFICER TEXT' For BGM Type 23, STS Code 0013(Released), Delivery Instructions from the inbound release document. For BGM Type 962, free text entered by a PGA or CBSA officer describing issue(s), concern(s), or errors with the inbound transmission. ; 3.3; D4 Date: 08/10/2014 Page: 20 / 34

21 0690 SG17 C 99 1 Error Details This segment group will NOT appear on positive response messages. For application errors, location details will not be present within the ERP segment. The determination of which field generated a given error message in the inbound document can be determined by mapping the error code provided in the ERC segment with the error messages & fields provided in the latest Error & Warning Code List. This response will only support up to 50 error codes ERC M 1 1 Application error information ERC C901 Application error detail 010 M M 9321 Application error code 1 M an..8 M an..8 External error code This field contains a standardized CBSA error (or warning) code. Please refer to the latest Error & Warning Code List published by the CBSA at ZZZ = Syntax reject ERC+0A0' ; 3.3; D4 Date: 08/10/2014 Page: 21 / 34

22 0710 SG18 C ERP This segment group contains an occurrence for each line and field to which the error code in SG17.ERC.9321 applies to ERP M 1 2 Error point details ERP C701 Error point details 010 C M 1049 Message section code 1 C an..3 C an..3 2 Detail section Future Use: This numeric field indicates what segment group of the original IID this error or warning refers to. E.g., if the error occurred at the commodity-level LPCO group (SG121), this field will have the value "121". If a value of "0" is provided, this indicates that the error occurred in one of the header segments Message item identifier 2 C an..35 C an..35 Unique Message Reference Number from UNH 0062 Future Use: A short text string describing the details of the error encountered Message sub-item identifier 3 C n..6 C n Administration 21 Enforcement 22 Conformance 28 Batch Error 29 Data Error Future Use: The exact element number or tag which generated this error/warning (e.g., 7081 for Item Characteristic located in SG117. IMD.7081) C853 Error segment point details 020 C M 9166 Segment tag identifier 4 C an..3 C an..3 Future Use: The tag or name of the segment (e.g., IMD, GIN etc.) in which the element that triggered this error or warning was found Sequence position identifier 5 C an..10 C an..10 Future Use: The occurrence in which this error appeared in the segment group provided in element 1049, starting with 1 as the first occurrence and incremented by 1 per occurrence. This number is unrelated to any values provided in SEQ or LIN segments in the IID Sequence identifier source code 6 C an..3 C an..3 Future Use: The sub position, or "place", of the element in which the error occurred. This is used to distinguish elements when segments contain multiple segments with the same tag (e.g., SG117.GIN contains segments at places 2, 3, and 4, so if an error occurred on the third one, this field would contain a "4"). ; 3.3; D4 Date: 08/10/2014 Page: 22 / 34

23 ERP+2:1:29+X:X:1' ; 3.3; D4 Date: 08/10/2014 Page: 23 / 34

24 1320 SG32 C 1 1 Conveyance Arrival Date/Location TDT M 1 1 Transport information TDT 8051 Transport stage code qualifier Required for syntax purposes (mandatory trigger segment) TDT+3' 010 M an..3 M an..3 3 At arrival ; 3.3; D4 Date: 08/10/2014 Page: 24 / 34

25 1490 SG34 M 1 2 Port of Report Group SG34 is used only with BGM type code 23 (Released) LOC M 1 2 Port of Report LOC 3227 Location function code 010 M an..3 M an Place/port of conveyance initial arrival qualifier C517 Location identification 020 C M 3225 Location identifier 2 C an..35 M an..4 Port of Report CBSA office code for port of report LOC ' ; 3.3; D4 Date: 08/10/2014 Page: 25 / 34

26 1490 SG34 M 1 2 Port of Report Group SG34 is used only with BGM type code 23 (Released) SEQ M 1 3 Sequence details SEQ 1229 Action code 010 C an..3 C an..3 4 No action Required for syntax purposes (Mandatory trigger segment) SEQ+4' ; 3.3; D4 Date: 08/10/2014 Page: 26 / 34

27 1880 SG41 C Container Details This segment appears when status type is Held for CBSA EQD M 1 2 Equipment details EQD 8053 Equipment type code 010 M an..3 M an..3 CN Container qualifier C237 Equipment identification 020 C C 8260 Equipment identifier 2 C an..17 C an..17 EQD+CN+ABCU ' ; 3.3; D4 Date: 08/10/2014 Page: 27 / 34

28 1880 SG41 C Container Details This segment appears when status type is Held for CBSA SEQ M 1 3 Sequence details SEQ 1229 Action code 010 C an..3 C an..3 SEQ+1' ; 3.3; D4 Date: 08/10/2014 Page: 28 / 34

29 UNS M 1 0 Section control UNS 0081 Section identification 010 M a1 M a1 D Header/detail section separation Required for syntax purposes (mandatory trigger segment) UNS+D' ; 3.3; D4 Date: 08/10/2014 Page: 29 / 34

30 HYN M 1 0 Hierarchy information HYN 7173 Hierarchy object code qualifier Required for syntax purposes (mandatory trigger segment) HYN+3' 010 M an..3 M an..3 3 No hierarchy ; 3.3; D4 Date: 08/10/2014 Page: 30 / 34

31 UNS M 1 0 Section control UNS 0081 Section identification 010 M a1 M a1 S Detail/summary section separation Required for syntax purposes (mandatory trigger segment) UNS+S' ; 3.3; D4 Date: 08/10/2014 Page: 31 / 34

32 UNT M 1 0 Message trailer UNT 0074 Number of segments in the message 010 M n..6 M n..6 Number of segments in message, includes UNH and UNT 0062 Message reference number 020 M an..14 M an..14 Unique Reference Number assigned by the sender. (Same number as supplied in UNH 0062) UNT ' ; 3.3; D4 Date: 08/10/2014 Page: 32 / 34

33 UNE M 1 0 Functional group trailer UNE 0060 Number of messages 010 M n..6 M n..6 Number of messages (UNH-UNT) included in the functional group Functional group reference number 020 M an..14 M an..14 Unique Reference Number assigned by the sender. Same number as supplied in UNG UNE ' ; 3.3; D4 Date: 08/10/2014 Page: 33 / 34

34 UNZ M 1 0 Interchange trailer UNZ 0036 Interchange control count 010 M n..6 M n..6 Number of functional groups (UNG-UNE) included in the interchange Interchange control reference 020 M an..14 M an..14 Unique reference number assigned by sender. Same number as supplied in UNB UNZ+1+X'