Messages for communication between freight forwarders and cross-docking, handling agent warehouses Message envelope, like Edifact UNB ID for the complete message, usually a technical identifier Message creation time. It is usually not required to update this time stamp when you restart the message. May not be in the future. Mutually agreed code of this messages sender Mutually agreed code of the intended recipient Same shipment may only be included once Advice of a master or super-house manifest for the warehouse The identifier of the master or super-house shipment with regard to the interface, may be a technical ID. Advice of a truck arrival at the warehouse The identifier of this advice with regard to the interface, may be a technical ID. The party delivering the goods (usually trucking company) The party ordering the delivery of the goods (usually the export agent of the contained consignments) The party where the goods are to be delivered Time intervals for pickup and delivery. Total values of all goods contained in this advice Details about the consignments in this advice Shipment data, air-freight specific. Include either exportAgent or importAgent The identifier of this shipment with regard to the interface, may be a technical ID. Commodity description, e.g. spare parts No duplicate SHCs allowed Documentation of a take-in into the warehouse The identifier of this receipt with regard to the interface, may be a technical ID. May not be in the future This is typically the trucking company / haulier This optional address identifies the party on whose behalf of the deliveringParty is delivering the cargo. Example: Peter (deliveringParty) owns a trucking company and is doing a milk-run for a local forwarding company (deliveringPartyCustomer). For air cargo security purposes we need to keep track of these kinds of constellations. Commodity description, e.g. spare parts Documentation of a take-out out of the warehouse The identifier of this take-out with regard to the interface, may be a technical ID. This is typically the trucking company / haulier Commodity description, e.g. spare parts Result of an air cargo security screening The identifier of this screening report, may be a technical ID. May not be in the future Instructions for building ULDs ID of the shipment ULDs should be built for. We do not support multi-master ULDs for now. Same shipment may only be included once While technically valid, name1-name3 and street1-street3 should be used consecutively, i.e. do not use street3 if the street2 element is is omitted. Use ISO-3166-2 codes, e.g. WA for Washington State, USA Use ISO-3166-1 alpha 2 code, e.g. AT for Austria EU Cargo DB of Known Consignors, Regulated Agents, ACC3. IDs look like this: DE/RA/11111-22 Economic Operators Registration and Identification number. I.e. customs ID used across the European Union, e.g. DE12345670000 IATA agent number, e.g. 22-1-7777777-1 Address number in TMS, WMS, etc. Physical file name, e.g. "myFile001.txt" Logical file name, e.g. "DN 47110815" Denotes the type of document from a business perspective rather than a technical one. If not mutually agreed otherwise between parties exchanging the documents it is recommended to use UN Edifact 1001 document name codes in format 'unedifact-nnn'. (See https://service.unece.org/trade/untdid/d16a/tred/tred1001.htm for reference). UN Edifact documents known by Scope 21.8ff: 49 (Damage certification), 105 (Purchase order), 173 (Authorisation to plan and ship orders), 271 (Packing list), 340 (Shipping instructions), 380 (Commercial invoice), 530 (Insurance certificate), 530 (Insurance policy), 550 (Insurance declaration sheet (bordereau)), 588 (Transport Means Security Report), 610 (Forwarding instructions), 632 (Goods receipt), 700 (Waybill), 703 (House waybill), 705 (Bill of lading), 714 (House bill of lading), 737 (Proof of delivery), 740 (Air waybill), 741 (Master air waybill), 861 (Certificate of origin), 890 (Dangerous goods declaration), 916 (Related document) Additional documentTypes known by Scope: 'accountsPayable', 'certificate', 'customsDocument', 'customsAssessment', 'image', 'scopeDocument' (Document type to be used for outgoing document messages only. Indicates that the document was created by Scope.) 'uploadedDocument' (Document type to be used for outgoing document messages only. Indicates that the document was uploaded to Scope.). Deprecated (use unedifact-nnn instead): 'certificateOfOrigin' -> unedifact-861, 'commercialInvoice' -> unedifact-380, 'packingList' -> unedifact-271, 'proofOfDelivery' -> unedifact-737, 'other' -> unedifact-916, Use standard MIME types, e.g. "application/pdf" or "image/png" This is usually not required for PDF documents or images. Use the Preferred MIME Name of the character set, e.g. "US-ASCII", "ISO-8859-1" Base64 encoded content. White-space will be ignored. Use IATA codes, e.g. "DIPL", "LFSM" IATA 606 package identifier, which consists of the IATA Air Waybill number (without any spaces or hyphens) followed by a zero (0) and a four-digit running counter. E.g. 1296666666601234 Package identifier assigned by the forwarder. This typically contains a reference to the House Waybill, but forwarders are free to use whatever scheme they prefer. Package identifier assigned by the shipper. This should be a real identifier (e.g. NVE-SSCC), not only some textual marking. Any other markings on the package Codes according to UNECE/CEFACT Trade Facilitation Recommendation No.21 ID for this consignment, eg. a transport order reference. Instruct warehouse to use specific equipment The used specific equipment Total values of all goods contained in this ULD Main Deck Loading only Nose Door Loading only ULD height below 160 cm ULD height between 160 cm and 244 cm ULD height above 244 cm Results of a ULDs build ID of the shipment ULDs is built for. We do not support multi-master ULDs for now. The ULD Build order ID this result is related to