Describes the requested action for an item or order: create, change, or cancel. Description of the type of request being issued. Comments related to the request. The qualifier indicates the amount to which the percentage is applied to derive the allowance/charge amount. The amount of the charge. Currency of the charge should be identified elsewhere in the document. The qualifier indicates the amount to which the percentage is applied to derive the charge amount. A free-form description of the additional charge. The amount of the allowance in the currency identified by currencyIdentifier. The qualifier indicates the amount to which the percentage is applied to derive the allowance amount. A free-form description of the allowance. For programmatic management of currency, use codes specified by ISO 4217-1995. Basic information for any document: unique document identifier, creation date, status (original or copy), transaction type, and language of the transaction. The creation date of the transaction referred to by this element. Format is CCYY-MM-DD. The time on creationDate that the document was created. Format is HH:MM:SS. For programmatic management of language, use language codes specified by ISO 639-1988. Describes a location where items might be shipped or received A piece identification number uniquely identifes a single piece in a transaction. When used, there is normally one PIN 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. One or more individual piece identification numbers. The data type is string to accommodate alphanumeric characters. One or more ranges of contiguous numbers. Floating point quantity type with unit of measure. Replaces measurementType (v1.1). Unit of measure implied by the value field The actual size value Generic container for reference numbers (assumed to be identifying documents of various types) and an associated document date. Note: this element should not be used to hold a unique transaction number for the current transaction (the so-called "primary key"); that number is normally found in the "id" attribute of the "document" element. Specifies an actual or estimated ship date. Specifies a quantity of items to ship, a location to ship to, and various shipment dates. The location is defined by a reference to a shipToParty element. Quantity to be shipped to this location. ID of shipToType element within PO header that corresponds to this shipTo location. 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. Identifies the data content in systemReferenceValue in a way that facilitates automated processing by the receiving party's computer system. For example, if the receiving party's computer system requires an indicator of how the receiving system is to record the financial impact of the transaction, it might use a system reference description of "FiscalBookIdentifier" The value that corresponds to the accompanying system reference description. For example, a value corresponding to a system reference description of "FiscalBookIdentifier" might be "2002" Describes terms under which payment is made and discount may be taken. Discount amount in the currency of the invoice (identified by the currencyIdentifier element). Discount percent is optional because it is considered to be informational only. Currently the only value this element may hold is "EOM" It may be extended to accommodate any date that can be more precisely described by a phrase or abbreviation than by any of the other choices in this group. The date by which payment is due if discount is to be earned. The day of the month (e.g., 21) by which payment is due if discount is to be earned. The next occurence of this day (whether this month or next) is the target date. Payment must be received by the discount basis date plus this many days if the discount is to be earned. A human-readable description of the terms, e.g., "2% in 10 days, net 30 days" Methods of payment acceptable to the seller. When the payment is due. Values are commonly used terms but really correlate to before (CBD), on (COD), or after delivery (Credit), or never (NoCharge). A due date should not be used unless timeOfPayment is "Credit". Currently the only value this element may hold is "EOM" It may be extended to accommodate any date that can be more precisely described by a phrase or abbreviation than by any of the other choices in this group. The date by which payment is due. The day of the month (e.g., 6) by which payment is due. The next occurence of this day (whether this month or next) is the target date. Payment must be eceived by the net basis date plus this many days. Used by termsType. Format is date (CCYY-MM-DD). Used by termsBasisDateType. The date the transaction is created by the sender. Conforms to ISO-8601 format: CCYY-MMDDTHH:MM:SS