| source |
<complexType name="invoiceLineType">
<sequence>
<element name="invoicedItem" type="fnItem:itemIdentifierType" minOccurs="0">
<annotation>
<documentation>Item identification information.</documentation>
</annotation>
</element>
<element name="invoicedQuantity" minOccurs="0">
<annotation>
<documentation>The quantity invoiced on this invoice line.</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="fnBase:quantityType">
<sequence minOccurs="0">
<element name="shipToLocation" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>The sum of all quantities specified here should equal the "value" attribute on element invoicedQuantity. The shipToID refers to an entry in the shipTo element on the header. The date attributes will normally not be used on an invoice; they are used on an Order Acknowledgement to allow acknowledgement of multiple shipments on a single acknowledgement.</documentation>
</annotation>
<complexType>
<complexContent>
<extension base="fnBase:shipToLocationType">
<sequence minOccurs="0">
<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="invoicedAmount" type="fnBase:monetaryAmountType" minOccurs="0">
<annotation>
<documentation>Unit price, exclusive of allowances and additional charges.</documentation>
</annotation>
</element>
<element name="invoiceLineAllowance" type="fnBase:discountOrAllowanceType" minOccurs="0" maxOccurs="unbounded"/>
<element name="invoiceLineAdditionalCharge" type="fnBase:additionalChargeType" minOccurs="0" maxOccurs="unbounded"/>
<element name="invoiceLineReferenceNumber" type="fnBase:referenceNumberType" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Any of a number of references revelent to this invoice line, such as the buyer's PO line number, buyer's sales order (for special orders), PO acknowledgement number, etc. An optional associated document date is also accommodated.</documentation>
</annotation>
</element>
<element name="quantityOrdered" type="fnBase:quantityType" minOccurs="0"/>
<element name="invoiceLineSystemReference" 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> |
