| source |
<complexType name="itemType">
<sequence>
<element name="itemInformation">
<annotation>
<documentation>Descriptive, physical, and handling information about this item.</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="fnItem:itemIdentifierType">
<sequence minOccurs="0">
<element name="subItem" type="fnItem:itemIdentifierType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>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).</documentation>
</annotation>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
</element>
<element name="itemReferenceNumber" type="fnBase:referenceNumberType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="itemQuantity" type="fnASN:itemQuantityType" minOccurs="0">
<annotation>
<documentation>Destination, distribution, and summary physical information about the items in this order or pack (context sensitive).</documentation>
</annotation>
</element>
<element name="itemSystemReference" 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>
</sequence>
</complexType> |
