<xsd:element name="fromRole" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">In general, the fromRole identifies the sender of the message, for the order request, the fromRole identifies the Buyer.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="GlobalDocumentFunctionCode" type="GlobalDocumentFunctionCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">Possible values are: - 'Request' in case of an initial purchase order. - 'Change' in case of a change or delete on an existing purchase order</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="accountName" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">(Company) Name of the buying party.</xsd:documentation></xsd:annotation></xsd:element>
Buyer's reference /account number at the seller.This should be a GLN (Global Location Number, formerly known as EAN address code).
Diagram
Type
xsd:string
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="AccountNumber" minOccurs="0" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Buyer's reference /account number at the seller. This should be a GLN (Global Location Number, formerly known as EAN address code).</xsd:documentation></xsd:annotation></xsd:element>
This element holds the invoicing information of the buyer for this order.The billTo element specifies where the invoice needs to be send. The billTo address is uniquely identified by the billTo GLN.One buying organization can have multiple billTo addresses.
<xsd:element name="billTo" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">This element holds the invoicing information of the buyer for this order. The billTo element specifies where the invoice needs to be send. The billTo address is uniquely identified by the billTo GLN. One buying organization can have multiple billTo addresses.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="comments" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">Only available for backwards compatibility of previous versions. Please use the remarks section instead?</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="remarks" minOccurs="0" type="RemarksType"><xsd:annotation><xsd:documentation xml:lang="EN">Use this multi line segment for header level comment lines or other information that can not be entered elsewhere.</xsd:documentation></xsd:annotation></xsd:element>
Conditional:- 'Work Order' in case of direct shipment (drop-ship or fulfillment order).- 'Contract' in case of a special bid order when not in lines.- 'Quote' in case of a special deal order when not in lines.- 'Ultimate Customer Order' in case of a License Order when not in lines.- 'Purchase Order' in case of an order with GlobalDocumentFunctionCodeType 'Change'.Optional:- 'Project when not in lines'
<xsd:element name="DocumentReference" minOccurs="0" maxOccurs="unbounded" type="DocumentReferenceType"><xsd:annotation><xsd:documentation source="V3.1">Conditional: - 'Work Order' in case of direct shipment (drop-ship or fulfillment order). - 'Contract' in case of a special bid order when not in lines. - 'Quote' in case of a special deal order when not in lines. - 'Ultimate Customer Order' in case of a License Order when not in lines. - 'Purchase Order' in case of an order with GlobalDocumentFunctionCodeType 'Change'. Optional: - 'Project when not in lines'</xsd:documentation></xsd:annotation></xsd:element>
This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'.Possible values are:- 'Add' (One or more lines are added to original OrdReq by the Buyer)- 'Change' (One or more lines are changed (quantity/price/deldate) or deleted from original OrdReq by the Buyer, or Delivery Address is changed)- 'Delete' (All order lines are deleted from original OrdReq by Buyer)
<xsd:element name="GlobalPurchaseOrderStatusCode" minOccurs="0" type="GlobalPurchaseOrderStatusCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'. Possible values are: - 'Add' (One or more lines are added to original OrdReq by the Buyer) - 'Change' (One or more lines are changed (quantity/price/deldate) or deleted from original OrdReq by the Buyer, or Delivery Address is changed) - 'Delete' (All order lines are deleted from original OrdReq by Buyer)</xsd:documentation></xsd:annotation></xsd:element>
The default value for this field = 'Standard'.Depending on the selling party the following types can be used (Check with Onetrail):- 'Special Bid Order'.- 'Special Deal Order'.- 'Reservation Order'- 'Consigned Order'- 'Planning Order'- 'High Priority Order'- 'Renewal Order'- 'New License Order'- 'PriceAndAvailabilityCheck' (Full PO check without order placement, supported by very limited Sellers)
<xsd:element name="GlobalPurchaseOrderTypeCode" maxOccurs="unbounded" type="GlobalPurchaseOrderTypeCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">The default value for this field = 'Standard'. Depending on the selling party the following types can be used (Check with Onetrail): - 'Special Bid Order'. - 'Special Deal Order'. - 'Reservation Order' - 'Consigned Order' - 'Planning Order' - 'High Priority Order' - 'Renewal Order' - 'New License Order' - 'PriceAndAvailabilityCheck' (Full PO check without order placement, supported by very limited Sellers)</xsd:documentation></xsd:annotation></xsd:element>
Depending on the selling party this element can be used to specify special shipping conditions (Delivery Types). Check with Onetrail for more detail if needed.
Diagram
Type
xsd:string
Properties
content:
simple
minOccurs:
0
maxOccurs:
unbounded
Source
<xsd:element name="GlobalShippingServiceLevelCode" minOccurs="0" maxOccurs="unbounded" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Depending on the selling party this element can be used to specify special shipping conditions (Delivery Types). Check with Onetrail for more detail if needed.</xsd:documentation></xsd:annotation></xsd:element>
This element can be used to specify packing instructions in consultation with the selling party..
Diagram
Type
xsd:string
Properties
content:
simple
minOccurs:
0
Source
<xsd:element name="PackListRequirements" minOccurs="0" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN" source="V3.2">This element can be used to specify packing instructions in consultation with the selling party..</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="CarriageCharge" minOccurs="0" maxOccurs="unbounded" type="CarriageChargeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element can be used to specify carriage charge conditions in consultation with the selling party.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="comments" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">Only available for backwards compatibility of previous versions. Please use the remarks section on line level instead?</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="remarks" minOccurs="0" type="RemarksType"><xsd:annotation><xsd:documentation xml:lang="EN">Use this multi line segment for line level comment lines or other information that can not be entered elsewhere.</xsd:documentation></xsd:annotation></xsd:element>
Conditional:- 'Contract' in case of a special bid order when not in header.- 'Quote' in case of a special deal order when not in header.- 'Ultimate Customer Order' in case of a License Order when not in header.Optional:- 'Project when not in header'
<xsd:element name="DocumentLineReference" minOccurs="0" maxOccurs="unbounded" type="DocumentLineReferenceType"><xsd:annotation><xsd:documentation source="V3.1">Conditional: - 'Contract' in case of a special bid order when not in header. - 'Quote' in case of a special deal order when not in header. - 'Ultimate Customer Order' in case of a License Order when not in header. Optional: - 'Project when not in header'</xsd:documentation></xsd:annotation></xsd:element>
This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'.Possible values are:- 'Accept' (Line is unchanged from original OrdReq by Buyer)- 'Add' (Line is added to original OrdReq by Buyer)- 'Change' (Line is changed from original OrdReq by Buyer)- 'Delete' (Line is deleted from original OrdReq by Buyer)
<xsd:element name="GlobalPurchaseOrderStatusCode" minOccurs="0" type="GlobalPurchaseOrderStatusCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'. Possible values are: - 'Accept' (Line is unchanged from original OrdReq by Buyer) - 'Add' (Line is added to original OrdReq by Buyer) - 'Change' (Line is changed from original OrdReq by Buyer) - 'Delete' (Line is deleted from original OrdReq by Buyer)</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="isDropShip" type="AffirmationIndicatorType"><xsd:annotation><xsd:documentation xml:lang="EN">'Yes' in case of a direct shipment (drop-ship or fulfillment), otherwise 'No'.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="isLicence" minOccurs="0" type="AffirmationIndicatorType"><xsd:annotation><xsd:documentation xml:lang="EN">'Yes' in case of a Licence order, otherwise 'No'. For care-pack orders this flag can be set to 'No'.</xsd:documentation></xsd:annotation></xsd:element>
Buyer's order line number.Not all sellers can register this number in their back-end application(s).
Diagram
Type
xsd:string
Properties
content:
simple
Source
<xsd:element name="LineNumber" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Buyer's order line number. Not all sellers can register this number in their back-end application(s).</xsd:documentation></xsd:annotation></xsd:element>
This field is always positive and does not contain a decimal separator.For the Technical Services Industry (TI) the quantity needs to be converted to a whole number and the unit of measure changed accordingly.I.e.: 1,5 MTR becomes 150 CMT.
Diagram
Type
xsd:nonNegativeInteger
Properties
content:
simple
Source
<xsd:element name="ProductQuantity" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="EN">This field is always positive and does not contain a decimal separator. For the Technical Services Industry (TI) the quantity needs to be converted to a whole number and the unit of measure changed accordingly. I.e.: 1,5 MTR becomes 150 CMT.</xsd:documentation></xsd:annotation></xsd:element>
All Onetrail TPN™ Sellers must accept orders with at least their internal product identification (SKU).Manufacturer part numbers, EAN product numbers and buyer part numbers are optional to accept for sellers.The Manufacturer part number and SKU must be used by buyers.
<xsd:element name="ProductIdentification" type="ProductIdentificationType"><xsd:annotation><xsd:documentation xml:lang="EN">All Onetrail TPN™ Sellers must accept orders with at least their internal product identification (SKU). Manufacturer part numbers, EAN product numbers and buyer part numbers are optional to accept for sellers. The Manufacturer part number and SKU must be used by buyers.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="proprietaryInformation" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">This element will hold the product description.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="tradeItemModification" minOccurs="0" maxOccurs="unbounded" type="TradeItemModificationType"><xsd:annotation><xsd:documentation xml:lang="EN">For future use in TI (technical services industry) sector.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="requestedEvent" minOccurs="1" maxOccurs="unbounded" type="requestedEventType"><xsd:annotation><xsd:documentation xml:lang="EN">In this element you can specify a requested delivery date or -period for a specific order line.</xsd:documentation></xsd:annotation></xsd:element>
Use the following GlobalTransportEventCodes:- 'RequestedDelivery'.- 'EarliestDelivery'.- 'LatestDelivery'- 'Ship'.For next day delivery the current date needs to be specified.
<xsd:element name="TransportationEvent" type="TransportationEventType"><xsd:annotation><xsd:documentation xml:lang="EN">Use the following GlobalTransportEventCodes: - 'RequestedDelivery'. - 'EarliestDelivery'. - 'LatestDelivery' - 'Ship'. For next day delivery the current date needs to be specified.</xsd:documentation></xsd:annotation></xsd:element>
The order line unit price excluding VAT can be specified in this element.In consultation with the selling party this element can be used to verify the pricing agreements and reject the order if the price differs (too much).
<xsd:element name="requestedUnitPrice" minOccurs="0" type="AmountType"><xsd:annotation><xsd:documentation xml:lang="EN">The order line unit price excluding VAT can be specified in this element. In consultation with the selling party this element can be used to verify the pricing agreements and reject the order if the price differs (too much).</xsd:documentation></xsd:annotation></xsd:element>
The shipTo segment specifies where goods need to be send.One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller.A warehouse order must have a shipTo GLN and NO shipTo address details.A drop-ship order must have full address details and NO shipTo GLN.
<xsd:element name="shipTo" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="EN">The shipTo segment specifies where goods need to be send. One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller. A warehouse order must have a shipTo GLN and NO shipTo address details. A drop-ship order must have full address details and NO shipTo GLN.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="ExtendedPartnerDescriptionType"><xsd:sequence><xsd:element name="PhysicalAddress" minOccurs="0" type="PhysicalAddressType"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="totalLineItemAmount" minOccurs="0" type="AmountType"><xsd:annotation><xsd:documentation xml:lang="EN">The order line total price excluding VAT must be specified in this element. It's the multiplication of requestedUnitPrice by OrderQuantity.</xsd:documentation></xsd:annotation></xsd:element>
In this element you can specify a delivery date or -period for the whole order.This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Request' and optional in case of an order with GlobalDocumentFunctionCodeType 'Change'.
<xsd:element name="requestedEvent" minOccurs="0" maxOccurs="unbounded" type="requestedEventType"><xsd:annotation><xsd:documentation xml:lang="EN">In this element you can specify a delivery date or -period for the whole order. This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Request' and optional in case of an order with GlobalDocumentFunctionCodeType 'Change'.</xsd:documentation></xsd:annotation></xsd:element>
The SecondaryBuyer segment is used for Carepack orders. It describes the end-user details for the Carepack end-user.When ordering Carepack products the 'IsLicence' flag can be set to 'No'.
<xsd:element name="SecondaryBuyer" minOccurs="0" type="ExtendedPartnerDescriptionType"><xsd:annotation><xsd:documentation xml:lang="EN">The SecondaryBuyer segment is used for Carepack orders. It describes the end-user details for the Carepack end-user. When ordering Carepack products the 'IsLicence' flag can be set to 'No'.</xsd:documentation></xsd:annotation></xsd:element>
The shipTo segment specifies where goods need to be send.One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller.A warehouse order must have a shipTo GLN and NO shipTo address details.A drop-ship order must have full address details and NO shipTo GLN.
<xsd:element name="shipTo"><xsd:annotation><xsd:documentation xml:lang="EN">The shipTo segment specifies where goods need to be send. One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller. A warehouse order must have a shipTo GLN and NO shipTo address details. A drop-ship order must have full address details and NO shipTo GLN.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="ExtendedPartnerDescriptionType"><xsd:sequence><xsd:element name="PhysicalAddress" minOccurs="0" type="PhysicalAddressType"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element>
<xsd:element name="thisDocumentGenerationDateTime" type="DateTimeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element specifies the date this message is created.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:element name="toRole" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">In general, the toRole identifies the recipient of the message, for the order request, the toRole identifies the seller.</xsd:documentation></xsd:annotation></xsd:element>
<xsd:complexType name="Pip3A4PurchaseOrderRequestType"><xsd:sequence><xsd:element name="fromRole" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">In general, the fromRole identifies the sender of the message, for the order request, the fromRole identifies the Buyer.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="Authentication" type="AuthenticationType"/><xsd:element name="GlobalDocumentFunctionCode" type="GlobalDocumentFunctionCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">Possible values are: - 'Request' in case of an initial purchase order. - 'Change' in case of a change or delete on an existing purchase order</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PurchaseOrder" type="PurchaseOrderType"/><xsd:element name="thisDocumentGenerationDateTime" type="DateTimeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element specifies the date this message is created.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="thisDocumentIdentifier" type="ProprietaryDocumentIdentifierType"/><xsd:element name="toRole" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">In general, the toRole identifies the recipient of the message, for the order request, the toRole identifies the seller.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="PurchaseOrderType"><xsd:sequence><xsd:element name="AccountDescription" minOccurs="0" type="AccountDescriptionType"/><xsd:element name="comments" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">Only available for backwards compatibility of previous versions. Please use the remarks section instead?</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="remarks" minOccurs="0" type="RemarksType"><xsd:annotation><xsd:documentation xml:lang="EN">Use this multi line segment for header level comment lines or other information that can not be entered elsewhere.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DocumentReference" minOccurs="0" maxOccurs="unbounded" type="DocumentReferenceType"><xsd:annotation><xsd:documentation source="V3.1">Conditional: - 'Work Order' in case of direct shipment (drop-ship or fulfillment order). - 'Contract' in case of a special bid order when not in lines. - 'Quote' in case of a special deal order when not in lines. - 'Ultimate Customer Order' in case of a License Order when not in lines. - 'Purchase Order' in case of an order with GlobalDocumentFunctionCodeType 'Change'. Optional: - 'Project when not in lines'</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GlobalPurchaseOrderStatusCode" minOccurs="0" type="GlobalPurchaseOrderStatusCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'. Possible values are: - 'Add' (One or more lines are added to original OrdReq by the Buyer) - 'Change' (One or more lines are changed (quantity/price/deldate) or deleted from original OrdReq by the Buyer, or Delivery Address is changed) - 'Delete' (All order lines are deleted from original OrdReq by Buyer)</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GlobalPurchaseOrderTypeCode" maxOccurs="unbounded" type="GlobalPurchaseOrderTypeCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">The default value for this field = 'Standard'. Depending on the selling party the following types can be used (Check with Onetrail): - 'Special Bid Order'. - 'Special Deal Order'. - 'Reservation Order' - 'Consigned Order' - 'Planning Order' - 'High Priority Order' - 'Renewal Order' - 'New License Order' - 'PriceAndAvailabilityCheck' (Full PO check without order placement, supported by very limited Sellers)</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="governmentContractIdentifier" minOccurs="0" type="ProprietaryDocumentIdentifierType"/><xsd:element name="OrderShippingInformation" minOccurs="0" type="OrderShippingInformationType"/><xsd:element name="ProductLineItem" maxOccurs="unbounded" type="ProductLineItemType"/><xsd:element name="purchaseOrderIdentifier" type="ProprietaryDocumentIdentifierType"><xsd:annotation><xsd:documentation xml:lang="EN">Purchase order number.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="requestedEvent" minOccurs="0" maxOccurs="unbounded" type="requestedEventType"><xsd:annotation><xsd:documentation xml:lang="EN">In this element you can specify a delivery date or -period for the whole order. This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Request' and optional in case of an order with GlobalDocumentFunctionCodeType 'Change'.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="SecondaryBuyer" minOccurs="0" type="ExtendedPartnerDescriptionType"><xsd:annotation><xsd:documentation xml:lang="EN">The SecondaryBuyer segment is used for Carepack orders. It describes the end-user details for the Carepack end-user. When ordering Carepack products the 'IsLicence' flag can be set to 'No'.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="shipTo"><xsd:annotation><xsd:documentation xml:lang="EN">The shipTo segment specifies where goods need to be send. One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller. A warehouse order must have a shipTo GLN and NO shipTo address details. A drop-ship order must have full address details and NO shipTo GLN.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="ExtendedPartnerDescriptionType"><xsd:sequence><xsd:element name="PhysicalAddress" minOccurs="0" type="PhysicalAddressType"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element><xsd:element name="totalAmount" minOccurs="0" type="AmountType"><xsd:annotation><xsd:documentation xml:lang="EN">Total order amount excl. VAT.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LicenceOrder" minOccurs="0" type="LicenceOrderType"/></xsd:sequence></xsd:complexType>
<xsd:complexType name="AccountDescriptionType"><xsd:sequence><xsd:element name="accountName" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">(Company) Name of the buying party.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="AccountNumber" minOccurs="0" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Buyer's reference /account number at the seller. This should be a GLN (Global Location Number, formerly known as EAN address code).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="billTo" type="roleType"><xsd:annotation><xsd:documentation xml:lang="EN">This element holds the invoicing information of the buyer for this order. The billTo element specifies where the invoice needs to be send. The billTo address is uniquely identified by the billTo GLN. One buying organization can have multiple billTo addresses.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="OrderShippingInformationType"><xsd:sequence><xsd:element name="GlobalShipmentTermsCode" minOccurs="0" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">For future use.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GlobalShippingServiceLevelCode" minOccurs="0" maxOccurs="unbounded" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Depending on the selling party this element can be used to specify special shipping conditions (Delivery Types). Check with Onetrail for more detail if needed.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="PackListRequirements" minOccurs="0" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN" source="V3.2">This element can be used to specify packing instructions in consultation with the selling party..</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GlobalSpecialFulfillmentRequestCode" maxOccurs="unbounded" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">- 'Complete' (One delivery per order) - 'Partial' (Backorders are allowed)</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="CarriageCharge" minOccurs="0" maxOccurs="unbounded" type="CarriageChargeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element can be used to specify carriage charge conditions in consultation with the selling party.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="ProductLineItemType"><xsd:sequence><xsd:element name="comments" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">Only available for backwards compatibility of previous versions. Please use the remarks section on line level instead?</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="remarks" minOccurs="0" type="RemarksType"><xsd:annotation><xsd:documentation xml:lang="EN">Use this multi line segment for line level comment lines or other information that can not be entered elsewhere.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="DocumentLineReference" minOccurs="0" maxOccurs="unbounded" type="DocumentLineReferenceType"><xsd:annotation><xsd:documentation source="V3.1">Conditional: - 'Contract' in case of a special bid order when not in header. - 'Quote' in case of a special deal order when not in header. - 'Ultimate Customer Order' in case of a License Order when not in header. Optional: - 'Project when not in header'</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="GlobalProductUnitOfMeasureCode" type="GlobalProductUnitOfMeasureCodeType"/><xsd:element name="GlobalPurchaseOrderStatusCode" minOccurs="0" type="GlobalPurchaseOrderStatusCodeType"><xsd:annotation><xsd:documentation xml:lang="EN">This element is mandatory in case of an order with GlobalDocumentFunctionCodeType 'Change'. Possible values are: - 'Accept' (Line is unchanged from original OrdReq by Buyer) - 'Add' (Line is added to original OrdReq by Buyer) - 'Change' (Line is changed from original OrdReq by Buyer) - 'Delete' (Line is deleted from original OrdReq by Buyer)</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="isDropShip" type="AffirmationIndicatorType"><xsd:annotation><xsd:documentation xml:lang="EN">'Yes' in case of a direct shipment (drop-ship or fulfillment), otherwise 'No'.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="isLicence" minOccurs="0" type="AffirmationIndicatorType"><xsd:annotation><xsd:documentation xml:lang="EN">'Yes' in case of a Licence order, otherwise 'No'. For care-pack orders this flag can be set to 'No'.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="LineNumber" type="xsd:string"><xsd:annotation><xsd:documentation xml:lang="EN">Buyer's order line number. Not all sellers can register this number in their back-end application(s).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="OrderQuantity" type="OrderQuantityType"/><xsd:element name="ProductIdentification" type="ProductIdentificationType"><xsd:annotation><xsd:documentation xml:lang="EN">All Onetrail TPN™ Sellers must accept orders with at least their internal product identification (SKU). Manufacturer part numbers, EAN product numbers and buyer part numbers are optional to accept for sellers. The Manufacturer part number and SKU must be used by buyers.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="proprietaryInformation" minOccurs="0" type="FreeFormTextType"><xsd:annotation><xsd:documentation xml:lang="EN">This element will hold the product description.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="tradeItemModification" minOccurs="0" maxOccurs="unbounded" type="TradeItemModificationType"><xsd:annotation><xsd:documentation xml:lang="EN">For future use in TI (technical services industry) sector.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="requestedEvent" minOccurs="1" maxOccurs="unbounded" type="requestedEventType"><xsd:annotation><xsd:documentation xml:lang="EN">In this element you can specify a requested delivery date or -period for a specific order line.</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="requestedUnitPrice" minOccurs="0" type="AmountType"><xsd:annotation><xsd:documentation xml:lang="EN">The order line unit price excluding VAT can be specified in this element. In consultation with the selling party this element can be used to verify the pricing agreements and reject the order if the price differs (too much).</xsd:documentation></xsd:annotation></xsd:element><xsd:element name="shipTo" minOccurs="0"><xsd:annotation><xsd:documentation xml:lang="EN">The shipTo segment specifies where goods need to be send. One buying organization can have multiple shipTo addresses (warehouses) which need to be registered at the seller. A warehouse order must have a shipTo GLN and NO shipTo address details. A drop-ship order must have full address details and NO shipTo GLN.</xsd:documentation></xsd:annotation><xsd:complexType><xsd:complexContent><xsd:extension base="ExtendedPartnerDescriptionType"><xsd:sequence><xsd:element name="PhysicalAddress" minOccurs="0" type="PhysicalAddressType"/></xsd:sequence></xsd:extension></xsd:complexContent></xsd:complexType></xsd:element><xsd:element name="totalLineItemAmount" minOccurs="0" type="AmountType"><xsd:annotation><xsd:documentation xml:lang="EN">The order line total price excluding VAT must be specified in this element. It's the multiplication of requestedUnitPrice by OrderQuantity.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="requestedQuantityType"><xsd:sequence><xsd:element name="ProductQuantity" type="xsd:nonNegativeInteger"><xsd:annotation><xsd:documentation xml:lang="EN">This field is always positive and does not contain a decimal separator. For the Technical Services Industry (TI) the quantity needs to be converted to a whole number and the unit of measure changed accordingly. I.e.: 1,5 MTR becomes 150 CMT.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>
<xsd:complexType name="requestedEventType"><xsd:sequence><xsd:element name="TransportationEvent" type="TransportationEventType"><xsd:annotation><xsd:documentation xml:lang="EN">Use the following GlobalTransportEventCodes: - 'RequestedDelivery'. - 'EarliestDelivery'. - 'LatestDelivery' - 'Ship'. For next day delivery the current date needs to be specified.</xsd:documentation></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType>