| source |
<complexType name="lineItemType">
<annotation>
<documentation>Furniture line item extension used as base for quotes and POs</documentation>
</annotation>
<sequence>
<element name="productID" type="fnItem:itemIdentifierType">
<annotation>
<documentation>Identification of product to be purchased.</documentation>
</annotation>
</element>
<element name="requestedQuantity">
<annotation>
<documentation>Quantity of above item to be purchased.</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="fnBase:quantityType">
<sequence>
<element name="shipToLocation" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>The sum of all quantities specified here should equal the "value" attribute on element requestedQuantity. The shipToID refers to an entry in the shipTo element on the header. The date attributes allow request for multiple shipments on a single order.</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="fnBase:shipToLocationType">
<sequence>
<element name="markForLocation" type="fnBase:markForLocationType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>The sum of all quantities specified here should equal the "quantity" attribute of the immediately enclosing shipToLocation element. The markForID refers to an entry in the markFor element on the header.</documentation>
</annotation>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
</element>
<element name="pieceIdentification" type="fnBase:pieceIdentificationNumberType" minOccurs="0">
<annotation>
<documentation>A piece identification number uniquely identifes a single piece in a transaction. When used, there is normally one piece ID number for each and every piece in the transaction. They may be buyer assigned or seller assigned. These numbers are NOT associated with a particular destination location.</documentation>
</annotation>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
</element>
<element name="unitPrice">
<annotation>
<documentation>Discounts, surcharges and price for one unit.</documentation>
</annotation>
<complexType>
<sequence>
<element name="discount" type="fnBase:discountOrAllowanceType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Discount used in calculating the total price</documentation>
</annotation>
</element>
<element name="surcharge" type="fnBase:additionalChargeType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Surcharge included in the price for the item.</documentation>
</annotation>
</element>
<element name="price" type="fnBase:monetaryAmountType">
<annotation>
<documentation>Unit price of this item including discounts, surcharges and options.</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="extendedPrice" minOccurs="0">
<annotation>
<documentation>Extended discounts, surcharges, and item price.</documentation>
</annotation>
<complexType>
<sequence>
<element name="extDiscount" type="fnBase:discountOrAllowanceType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Discount used in calculating the total price</documentation>
</annotation>
</element>
<element name="extSurcharge" type="fnBase:additionalChargeType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Surcharge included in the price for the item.</documentation>
</annotation>
</element>
<element name="extPrice" type="fnBase:monetaryAmountType">
<annotation>
<documentation>Extended price of this item including discounts, surcharges and options.</documentation>
</annotation>
</element>
</sequence>
</complexType>
</element>
<element name="lineSystemReference" 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>
<attribute name="lineItemNumber" type="positiveInteger" use="required"/>
<attribute name="comment" type="string" use="optional">
<annotation>
<documentation>General comments about the item.</documentation>
</annotation>
</attribute>
<attribute name="requestedSerialNumber" type="string" use="optional">
<annotation>
<documentation>Buyer requests this serial number be attached to the item prior to shipping.</documentation>
</annotation>
</attribute>
</complexType> |
