Total number of packs on the shipment or order, or the number of items on the order or in a pack (context sensitive). The sum of all quantities specified here should equal the "quantity" attribute of the enclosing unitsShipped element. The markForID refers to an entry in the markFor element on the header. Aggregate measurements for all associated units. Having two sets of dimensions allows defining English and Metric measurements. Total number of packs or items ordered on the shipment or order (context sensitive). Descriptive, physical, and handling information about this item. Subitems are used when the retailer has ordered an item that is really known to the manufacturer as multiple items (e.g., the retailer orders a bed that the manufacturer knows as a headboard, footboard, and rail). Any of a number of references revelent to this item, such as purchase order line number, serial number, etc. An optional associated document date is also accommodated. Destination, distribution, and summary physical information about the items in this order or pack (context sensitive). A system reference facilitates automated processing of the document by including data elements that are not necessarily part of a standard transaction but are required or desired by the computer systems of the trading partners. Effective use of system references requires pre-arrangement between trading partners. NOTE: this structure should not be used for data that is otherwise accommodated within a transaction schema. Any of a number of references revelent to this order, such as buyer's purchase order number, invoice number, sales order number, etc. An optional associated document date is also accommodated. Destination, distribution, and summary physical information about the "packs" in this order. True if this shipment represents a partial shipment (i.e., non-completion) of the order, otherwise false. A system reference facilitates automated processing of the document by including data elements that are not necessarily part of a standard transaction but are required or desired by the computer systems of the trading partners. Effective use of system references requires pre-arrangement between trading partners. NOTE: this structure should not be used for data that is otherwise accommodated within a transaction schema. Information about the items on this order. May be a carton, a shrink-wrapped bundle, or any other container of product. Information on the item(s) in this pack. Although a pack will generally contain only one kind of item, this structure allows different items in a pack. May be a carton, a shrink-wrapped bundle, or any other container of product. Uniquely identifies the pack. The number of items in the pack. Total number of packs on the shipment or order, or the number of items on the order or in a pack (context sensitive). The sum of all quantities specified here should equal the "quantity" attribute of the enclosing unitsShipped element. The markForID refers to an entry in the markFor element on the header. Aggregate measurements for all associated units. Having two sets of dimensions allows defining English and Metric measurements. Total number of packs or items ordered on the shipment or order (context sensitive). id represents a unique invoice number; type represents the transaction type (e.g., "856"). For programmatic management of language, use language codes specified by ISO 639-1988. This normally mandatory element is optional because not all manufacturers and shippers will generate an ASN number, instead possibly favoring some other identifier, such as bill of lading number. Specifies that the transaction is either new, a change to, or cancellation of a previous ship notice. Specifies the structure of this ASN document for the benefit of the receiving party's programmatic processing of the document. Any of a number of references revelent to this shipment, such as bill of lading number, carrier reference number, etc. An optional associated document date is also accommodated. Note: the ASN number and date are stored in the "document" element. The date that physical movement did or will take place. The buyer of the goods being shipped. The seller of the goods being shipped. Identifies the carrier of the goods being shipped. The party/location from which goods will ship or have shipped. The party/location to which goods will be shipped. Mark-For parties are parties, generally entities within the buying organization, to whom goods are routed after physical receipt of goods by the ship-to party. Indicates the predominant product content in the shipment. Destination, distribution, and summary physical information about the packs or items in this shipment. Air, Motor, Ocean, Rail. Container may be a rail car, a trailer, a ship container, or any other enclosed, sealable shipment medium. The number identifying this rail car, trailer, etc. The seal number for this coontainer. Collect, PrePaid, ThirdParty. A system reference facilitates automated processing of the document by including data elements that are not necessarily part of a standard transaction but are required or desired by the computer systems of the trading partners. Effective use of system references requires pre-arrangement between trading partners. NOTE: this structure should not be used for data that is otherwise accommodated within a transaction schema.