| source |
<complexType name="shipmentType">
<sequence>
<element name="document" type="fnBase:documentType" minOccurs="0">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="actionRequestIndicator" type="fnBase:actionRequestIndicatorType" minOccurs="0">
<annotation>
<documentation>Specifies that the transaction is either new, a change to, or cancellation of a previous ship notice.</documentation>
</annotation>
</element>
<element name="documentStructure" minOccurs="0">
<annotation>
<documentation>Specifies the structure of this ASN document for the benefit of the receiving party's programmatic processing of the document.</documentation>
</annotation>
<complexType>
<attribute name="documentStructureQualifier" use="optional">
<simpleType>
<restriction base="string">
<enumeration value="Shipment"/>
<enumeration value="ShipmentOrder"/>
<enumeration value="ShipmentOrderItem"/>
<enumeration value="ShipmentOrderItemPack"/>
<enumeration value="ShipmentOrderPack"/>
<enumeration value="ShipmentOrderPackItem"/>
</restriction>
</simpleType>
</attribute>
</complexType>
</element>
<element name="shipmentReferenceNumber" type="fnBase:referenceNumberType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="shipDate" type="fnBase:shipDateType">
<annotation>
<documentation>The date that physical movement did or will take place.</documentation>
</annotation>
</element>
<element name="buyer" type="fnParty:partyIdentificationType" minOccurs="0">
<annotation>
<documentation>The buyer of the goods being shipped.</documentation>
</annotation>
</element>
<element name="seller" type="fnParty:sellerIdentificationType" minOccurs="0">
<annotation>
<documentation>The seller of the goods being shipped.</documentation>
</annotation>
</element>
<element name="carrier" type="fnParty:carrierIdentificationType" minOccurs="0">
<annotation>
<documentation>Identifies the carrier of the goods being shipped.</documentation>
</annotation>
</element>
<element name="shipFrom" type="fnParty:partyIdentificationType" minOccurs="0">
<annotation>
<documentation>The party/location from which goods will ship or have shipped.</documentation>
</annotation>
</element>
<element name="shipTo" type="fnParty:shipToPartyType">
<annotation>
<documentation>The party/location to which goods will be shipped.</documentation>
</annotation>
</element>
<element name="markFor" type="fnParty:shipToPartyType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="productCategory" type="fnBase:noteType" minOccurs="0">
<annotation>
<documentation>Indicates the predominant product content in the shipment.</documentation>
</annotation>
</element>
<element name="shipmentQuantity" type="fnASN:shipmentQuantityType" minOccurs="0">
<annotation>
<documentation>Destination, distribution, and summary physical information about the packs or items in this shipment.</documentation>
</annotation>
</element>
<element name="shipmentMethod" type="fnASN:shipmentMethodType" minOccurs="0">
<annotation>
<documentation>Air, Motor, Ocean, Rail.</documentation>
</annotation>
</element>
<element name="container" minOccurs="0">
<annotation>
<documentation>Container may be a rail car, a trailer, a ship container, or any other enclosed, sealable shipment medium.</documentation>
</annotation>
<complexType>
<sequence>
<element name="containerNumber">
<annotation>
<documentation>The number identifying this rail car, trailer, etc.</documentation>
</annotation>
</element>
<element name="sealNumber" minOccurs="0">
<annotation>
<documentation>The seal number for this coontainer.</documentation>
</annotation>
</element>
<element name="containerDimensions" type="fnItem:dimensionsType" minOccurs="0"/>
</sequence>
</complexType>
</element>
<element name="freightTerms" minOccurs="0">
<annotation>
<documentation>Collect, PrePaid, ThirdParty.</documentation>
</annotation>
<simpleType>
<restriction base="string">
<enumeration value="Collect"/>
<enumeration value="PrePaid"/>
<enumeration value="ThirdParty"/>
</restriction>
</simpleType>
</element>
<element name="shipmentSystemReference" type="fnBase:systemReferenceType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="specialInstructions" type="fnBase:noteType" minOccurs="0" maxOccurs="unbounded"/>
<element name="order" type="fnASN:orderType" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType> |
