SORTOI: SO Sales Order Import
The SO Sales Order Import business object lets you add a new sales order and change or cancel an existing sales order.
Multiple orders can be passed to this object with any combination of the add, cancel and change requests. The input for each order is made up of header information and individual detail lines.
Properties
| Syspro Module | Sales Orders |
| Class | Transaction |
| Methods | Post |
| Functional Area | Sales Orders Primary Posting |
| Initial version released | Syspro 6.1 |
Input XML
The .XML and .XSD input files indicate the parameters schema and an instance of an XML document for this business object.
SORTOI.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2023 SYSPRO Ltd.-->
<!--
This is an example XML instance to demonstrate
use of the Sales Order Transaction Posting Business Object
-->
<SalesOrders xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="SORTOI.XSD">
<Parameters>
<InBoxMsgReqd>Y</InBoxMsgReqd>
<Process>IMPORT</Process>
<CustomerToUse/>
<WarehouseListToUse>E,FG</WarehouseListToUse>
<UseCustomerSalesWarehouse></UseCustomerSalesWarehouse>
<TypeOfOrder>ORD</TypeOfOrder>
<OrderStatus>1</OrderStatus>
<MinimumDaysToShip>4</MinimumDaysToShip>
<AllowNonStockItems>Y</AllowNonStockItems>
<AcceptOrdersIfNoCredit>Y</AcceptOrdersIfNoCredit>
<AcceptEarlierShipDate>N</AcceptEarlierShipDate>
<OperatorToInform>ADMIN</OperatorToInform>
<CreditFailMessage>No credit available</CreditFailMessage>
<ValidProductClassList>SPEC,BA,FGC</ValidProductClassList>
<ShipFromDefaultBin>N</ShipFromDefaultBin>
<AllowDuplicateOrderNumbers>Y</AllowDuplicateOrderNumbers>
<CheckForCustomerPoNumbers>Y</CheckForCustomerPoNumbers>
<AllowInvoiceInformationEntry/>
<AlwaysUsePriceEntered/>
<AllowZeroPrice/>
<AllowChangeToZeroPrice></AllowChangeToZeroPrice>
<AddStockSalesOrderText>N</AddStockSalesOrderText>
<AddDangerousGoodsText>N</AddDangerousGoodsText>
<UseStockDescSupplied/>
<ValidateShippingInstrs/>
<AllocationAction></AllocationAction>
<IgnoreWarnings>N</IgnoreWarnings>
<AddAttachedServiceCharges></AddAttachedServiceCharges>
<StatusInProcess></StatusInProcess>
<StatusInProcessResponse></StatusInProcessResponse>
<WarnIfCustomerOnHold>N</WarnIfCustomerOnHold>
<AcceptKitOptional>N</AcceptKitOptional>
<AllowBackOrderForPartialHold></AllowBackOrderForPartialHold>
<AllowBackOrderForSuperseded></AllowBackOrderForSuperseded>
<OverrideCustomerBackOrder></OverrideCustomerBackOrder>
<UseMasterAccountForCustomerPartNo></UseMasterAccountForCustomerPartNo>
<ApplyLeadTimeCalculation></ApplyLeadTimeCalculation>
<ApplyParentDiscountToComponents>N</ApplyParentDiscountToComponents>
<AllowManualOrderNumberToBeUsed>N</AllowManualOrderNumberToBeUsed>
<ReserveStock></ReserveStock>
<ReserveStockRequestAllocs></ReserveStockRequestAllocs>
<AllowBackOrderForNegativeMerchLine>N</AllowBackOrderForNegativeMerchLine>
<PutEntireQuantityOnNewLoadWhenChanged>N</PutEntireQuantityOnNewLoadWhenChanged>
<MinimumChargeLineZero>N</MinimumChargeLineZero>
<UpdateWhLast>N</UpdateWhLast>
<ConfirmQuote>N</ConfirmQuote>
<IncludeDimensionAnalysis>N</IncludeDimensionAnalysis>
</Parameters>
</SalesOrders>Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2023 SYSPRO Ltd.-->
<!--
Schema for the Sales Order Transaction Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="AcceptKitOptional">
<xsd:annotation>
<xsd:documentation>This option is only relevant if Single Level bills are in use. If set to 'Y' then any stock item that is a kit item, and has optional components will be accepted. If set to 'N' (the default), then it will be rejected. If set to 'E' then any optional component in a kit item will be iexcluded from the kit.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AcceptOrdersIfNoCredit">
<xsd:annotation>
<xsd:documentation>Specifies if sales orders are allowed to be accepted if the customer has failed the credit check (Y - Yes, N - No). If not specified this defaults to the e.net solutions settings against the operator.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AcceptEarlierShipDate" default="N">
<xsd:annotation>
<xsd:documentation>Specifies if sales orders are allowed to be accepted if the requested ship date supplied is earlier than the default ship date. Defaults to 'N'. Valid values are 'N' and 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AddStockSalesOrderText" default="N">
<xsd:annotation>
<xsd:documentation>Specifies if standard sales order text associated with any stock item is to be added to the sales order with the appropriate merchandise line. The default is N (no text to be added).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AddDangerousGoodsText" default="N">
<xsd:annotation>
<xsd:documentation>Specifies if dangerous goods text associated with any stock item is to be added to the sales order with the appropriate merchandise line. The default is N (no text to be added).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AddAttachedServiceCharges">
<xsd:annotation>
<xsd:documentation>Use of this element affects the processing of service charges attached to a stock code. It is only considered for the addition of a stocked detail line. Valid entries are 'Y' (Yes), add all service charges found, 'N' (No), do not add service charges, 'M' (Mandatory), add only charges which are not marked for review in order entry. Default is 'N'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="M"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllocationAction">
<xsd:annotation>
<xsd:documentation>Specifies whether merchandise lines are to be allocated or placed on back order. Valid entries are 'F' - allocate only if full order quantity is available, 'B' - place whole line on back order, 'A' - allocate available quantity if less than order quantity, and place the remainder on back order. If blank or not entered, 'F' is assumed. If set to 'B' (Back order), then the parameter 'ShipFromDefaultBin' is ignored. Note that any items which are kit items, lot traceable or serialised will still be placed on back order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="F"/>
<xsd:enumeration value="B"/>
<xsd:enumeration value="A"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowBackOrderForNegativeMerchLine">
<xsd:annotation>
<xsd:documentation>Allow negative merchandise line to be added with quantity in back order</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowBackOrderForPartialHold">
<xsd:annotation>
<xsd:documentation>Specifies if a merchandise line is to be accepted in back order for a stock item that has been placed on partial hold. Valid entries are N - No (the default), and 'Y' - Yes</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowBackOrderForSuperseded">
<xsd:annotation>
<xsd:documentation>Specifies if a merchandise line is to be accepted in back order for a stock item that has been superseded. Valid entries are N - No (the default), and 'Y' - Yes</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowChangeToZeroPrice">
<xsd:annotation>
<xsd:documentation>This parameter controls the use of price on a changed merchandise line only. If set to 'Y', and the element 'Price' contains zero, then the price on that line will be changed to zero. Valid entries are 'N' - No, and 'Y' Yes. The default is no.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowDuplicateOrderNumbers" default="N">
<xsd:annotation>
<xsd:documentation>Specifies whether duplicate order numbers are allowed to be entered (Y - Yes, N - No, A - Always). There is a SYSPRO option which forces a check for duplicate customer purchase order numbers. An entry of A - Always for this parameter will over-ride the SYSPRO option, and no checks will be made for duplicates at all. If the SYSPRO option is not selected, then this parameter is used to specify if duplicate order numbers are acceptable for the same customer - an entry of Y - Yes will mean that the same order number can be used more than once for a specific customer. If the SYSPRO check is in force, then the only relevant entry is A - Always.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="A"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowInvoiceInformationEntry" default="N">
<xsd:annotation>
<xsd:documentation>Specifies whether invoice information (invoice number and invoice date) may be entered for an order that is defined as ready to invoice, status 8 (Y - Yes, N - No). If set, this overrides any other SYSPRO configuation rules for supplying invoice numbers. </xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowManualOrderNumberToBeUsed">
<xsd:annotation>
<xsd:documentation>This parameter allows the company option for adding Sales Order Numbers to be over-ridden. If set to 'Y', then an order number can be given in the SalesOrder element when adding an order. If an order number is supplied, then it must not exist in SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowNonStockItems">
<xsd:annotation>
<xsd:documentation>Specifies whether non-stocked lines are allowed to be entered as detail lines on the sales order (Y - Yes, N - No, S Specify) . If not set this defaults to the e.net solutions setting against the operator. Note that the e.net soltions setting can only be allowed or not allowed. If the element 'AllowNonStockItems' is set to 'S', then a new non-stocked detail line must include the element 'NonStockedLine' with a value of 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AllowZeroPrice" default="N">
<xsd:annotation>
<xsd:documentation>Specifies that the price supplied on the detail line on the sales order may be zero (Y - Yes, N - No). This only applies if the parameter AlwaysUsePriceEntered is set to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AlwaysUsePriceEntered" default="N">
<xsd:annotation>
<xsd:documentation>Specifies that the price supplied on the detail line on the sales order is to be used instead of any price calculated using the SYSPRO configuration parameters(Y - Yes, N - No). </xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ApplyLeadTimeCalculation">
<xsd:annotation>
<xsd:documentation>Set this element to 'Y' to apply the lead time calculation to the ship date of a line in a scheduled order where there is insufficient quantity to ship the entire line. This parameter is ignored if the AllocationAction is B - place line in back order. This calculation is not applied if a specfic date is given in the detail line element 'LineShipDate'</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ApplyParentDiscountToComponents">
<xsd:annotation>
<xsd:documentation>Only applicable to a stocked line that is for a parent of kit type 'K'. If set to 'Y', then any percentage discount specified on that line will be used in each one of the components, and will over-ride any discount calculated on the component price. This only applies when adding a line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CheckForCustomerPoNumbers">
<xsd:annotation>
<xsd:documentation>This element controls the checking of customer purchase orders against new orders. If set to 'Y' (the default), then the element 'CustomerPoNumber' must be supplied when adding a sales order. If set to 'N', then the element may be missing, or may be blank. If set to 'C' (customer) then the check is based on the setting of the SYSPRO Customer Maintenance option 'Customer purchase order number mandatory'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CreditFailMessage" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The message to be returned if the customer fails the credit check.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CustomerToUse">
<xsd:annotation>
<xsd:documentation>If no customer code exists in the sales order header and no sender code in the transmission header this becomes a mandatory entry. This must be a valid SYSPRO customer and they must be set as an EDI customer.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IgnoreWarnings" default="N">
<xsd:annotation>
<xsd:documentation>Specifies if warnings are to be ignored (Y - if the warnings are to be ignored, N - warnings will be returned as errors in the XML returned, W - warnings will be returned as warnings in the XML returned). An example of a warning is if margin checking is required, and the new or changed merchandise line fails the margin check, you may want the warning supplied.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="W"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InBoxMsgReqd" default="N">
<xsd:annotation>
<xsd:documentation>Write an entry to the ADMMSG file for the logged in operator (N or blank - No, Y - Yes). This message is made available in the Orders Created Externally option of SYSPRO. </xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value=""/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MinimumDaysToShip">
<xsd:annotation>
<xsd:documentation>This is the minimum number of days before an order can be shipped. If this is not supplied the e.net solutions configuration against the operator is used. If this is not present the default is 0.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OperatorToInform">
<xsd:annotation>
<xsd:documentation>This is the operator to inform when a new order is created. This must be a valid SYSPRO operator code. If not supplied then the "operator to inform about new orders placed" option in the e.net solutions configuration against this operator will be used. If this is not set then the operator who is attempting to create the sales order will be informed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderStatus">
<xsd:annotation>
<xsd:documentation>This indicates the status that will be applied to the new order (1, 4,8 or S). If no status is provided the status against this operator in the e.net solutions configuration is used. If this is not present the default of 1 is used. A status of 'S' indicates that the order is to be placed straight into suspense, so that operator activity is required in the SYSPRO system before the order can be released. If the type of order requested is 'BIL' (billing), then this parameter is ignored, and the order status is set to 8 - to invoice.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="1"/>
<xsd:enumeration value="4"/>
<xsd:enumeration value="8"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OverrideCustomerBackOrder">
<xsd:annotation>
<xsd:documentation>Specifies if a merchandise line is to be accepted in back order even if the customer is not allowed back orders. Valid entries are N - No (the default), and 'Y' - Yes</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Parameters">
<xsd:annotation>
<xsd:documentation>This contains the parameters</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="InBoxMsgReqd" minOccurs="0"/>
<xsd:element ref="Process" minOccurs="0"/>
<xsd:element ref="CustomerToUse" minOccurs="0"/>
<xsd:element ref="WarehouseListToUse" minOccurs="0"/>
<xsd:element ref="UseCustomerSalesWarehouse" minOccurs="0"/>
<xsd:element ref="TypeOfOrder" minOccurs="0"/>
<xsd:element ref="OrderStatus" minOccurs="0"/>
<xsd:element ref="MinimumDaysToShip" minOccurs="0"/>
<xsd:element ref="AllowNonStockItems" minOccurs="0"/>
<xsd:element ref="AcceptOrdersIfNoCredit" minOccurs="0"/>
<xsd:element ref="AcceptEarlierShipDate" minOccurs="0"/>
<xsd:element ref="OperatorToInform" minOccurs="0"/>
<xsd:element ref="CreditFailMessage" minOccurs="0"/>
<xsd:element ref="ValidProductClassList" minOccurs="0"/>
<xsd:element ref="ShipFromDefaultBin" minOccurs="0"/>
<xsd:element ref="AllowDuplicateOrderNumbers" minOccurs="0"/>
<xsd:element ref="CheckForCustomerPoNumbers" minOccurs="0"/>
<xsd:element ref="AllowInvoiceInformationEntry" minOccurs="0"/>
<xsd:element ref="AlwaysUsePriceEntered" minOccurs="0"/>
<xsd:element ref="AllowZeroPrice" minOccurs="0"/>
<xsd:element ref="AllowChangeToZeroPrice" minOccurs="0"/>
<xsd:element ref="AddStockSalesOrderText" minOccurs="0"/>
<xsd:element ref="AddDangerousGoodsText" minOccurs="0"/>
<xsd:element ref="UseStockDescSupplied" minOccurs="0"/>
<xsd:element ref="ValidateShippingInstrs" minOccurs="0"/>
<xsd:element ref="AllocationAction" minOccurs="0"/>
<xsd:element ref="IgnoreWarnings" minOccurs="0"/>
<xsd:element ref="AddAttachedServiceCharges" minOccurs="0"/>
<xsd:element ref="StatusInProcess" minOccurs="0"/>
<xsd:element ref="StatusInProcessResponse" minOccurs="0"/>
<xsd:element ref="WarnIfCustomerOnHold" minOccurs="0"/>
<xsd:element ref="AcceptKitOptional" minOccurs="0"/>
<xsd:element ref="AllowBackOrderForPartialHold" minOccurs="0"/>
<xsd:element ref="AllowBackOrderForSuperseded" minOccurs="0"/>
<xsd:element ref="OverrideCustomerBackOrder" minOccurs="0"/>
<xsd:element ref="UseMasterAccountForCustomerPartNo" minOccurs="0"/>
<xsd:element ref="ApplyLeadTimeCalculation" minOccurs="0"/>
<xsd:element ref="ApplyParentDiscountToComponents" minOccurs="0"/>
<xsd:element ref="AllowManualOrderNumberToBeUsed" minOccurs="0"/>
<xsd:element ref="ReserveStock" minOccurs="0"/>
<xsd:element ref="ReserveStockRequestAllocs" minOccurs="0"/>
<xsd:element ref="AllowBackOrderForNegativeMerchLine" minOccurs="0"/>
<xsd:element ref="PutEntireQuantityOnNewLoadWhenChanged" minOccurs="0"/>
<xsd:element ref="MinimumChargeLineZero" minOccurs="0"/>
<xsd:element name="UpdateWhLast" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element indicates whether to update the warehouse stock after adding all sales order lines. This is used to improve performance. Valid values are 'Y' and 'N' (default).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="1"/>
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="ConfirmQuote" minOccurs="0"/>
<xsd:element ref="IncludeDimensionAnalysis" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Process" default="Validate">
<xsd:annotation>
<xsd:documentation>This is the process to follow (Validate - validate contents only, Import - validate the contents and import only if there are no errors).
If there are any errors the whole document is returned with all errors found. The errors will appear at the end of the section in which the error occurred, such as the StockLine section.
The last entry in the XML returned from a validation process will be the ValidationStatus element which will have a sub-element of Status. This will contain either Successful or Failed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Validate"/>
<xsd:enumeration value="validate"/>
<xsd:enumeration value="VALIDATE"/>
<xsd:enumeration value="Import"/>
<xsd:enumeration value="import"/>
<xsd:enumeration value="IMPORT"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReserveStock">
<xsd:annotation>
<xsd:documentation>This element is only relevant if the SO Option to allow reserving of stock is selected. If set to 'Y', then any attempt to allocate stock for a line will result in it being reserved, and not shipped. If set to 'N', then any attempt to allocate stock will result in it being shipped. If the element is not supplied, then the SYSPRO company setting will be used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReserveStockRequestAllocs">
<xsd:annotation>
<xsd:documentation>This element is only relevant if the SO Option to allow reserving of stock is selected, and stock is being reserved not shipped. If set to 'Y', then any lot bin or serial item can only be reserved using the ship rules. If set to 'N', then a lot , serial or bin item can be reserved as detail allocations are not required. If the element is not supplied, then the SYSPRO company setting will be used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrders">
<xsd:annotation>
<xsd:documentation>This is the root element</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="Parameters"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromDefaultBin" default="N">
<xsd:annotation>
<xsd:documentation>Specifies whether stocked lines are to be shipped from the default bin (Y - Yes, N - No). This parameter is only relevant if multiple bins are in use, and the warehouse on the sales order line required multiple bins. If not set and multiple bins are in use, and the warehouse on the sales order line requires multiple bins , then stocked lines will be placed on back order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StatusInProcess">
<xsd:annotation>
<xsd:documentation>This parameter is only intended for use when the business object is called from scripting while processing a sales order with the SYSPRO Sales Order Entry program. It should be set to 'Y' in those circumstances, and will allow the business object to access the sales order that is currently held by SYSPRO. The only activity allowed is to add a line to the order. If this parameter is set to 'Y' under any other circumstances, then the results will be unpredictable.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StatusInProcessResponse">
<xsd:annotation>
<xsd:documentation>This element is only relevant if the StatusInProcess element is set to 'Y'. If used, it indicates that a full repsonse on the successful processing of the order is required in the output XML.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value=""/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TypeOfOrder" default="ORD">
<xsd:annotation>
<xsd:documentation>This indicates which type of order to create. The possible values are ORD - normal order, FWD - forward order, SCH - scheduled order, IBT - inter branch transfer, BIL - billing. If not provided the e.net solutions settings against the operator are used. If this is also not defined, the default is ORD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ORD"/>
<xsd:enumeration value="FWD"/>
<xsd:enumeration value="SCH"/>
<xsd:enumeration value="IBT"/>
<xsd:enumeration value="BIL"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseCustomerSalesWarehouse">
<xsd:annotation>
<xsd:documentation>If set to 'Y', then the default warehouse for a stocked line will be taken from the sales warehouse against the customer. If that warehouse is blank, then the normal rules for establishing a warehouse will be followed. A warehouse supplied against the detail line will always take precedence.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseMasterAccountForCustomerPartNo">
<xsd:annotation>
<xsd:documentation>This paramter is used to decide how the element 'CustomersPartNumber' in a merchandise line is checked for a sub-account. If used, it will over-ride the equivalent SYSPRO company option. Valid entries are N - No the default - 'CustomersPartNumber' is checked against the stock codes for the customer, A - Always - always check the stock codes against those for the master account, C - Check - first check the customer stock codes, and if not found, check the stock codes for the master account</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="A"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseStockDescSupplied" default="N">
<xsd:annotation>
<xsd:documentation>Specifies that the contents of the element StockDescription supplied for an added detail line must be used instead of the description from the Item Master. Valid entries are N - No, and Y - Yes (default is N)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ValidateShippingInstrs" default="N">
<xsd:annotation>
<xsd:documentation>Specifies the validation that must be applied to the shipping instructions (Element 'ShippingInstrs' within 'OrderHeader'). Valid entries are N - No, and Y - Yes. This parameter is only used if the SYSPRO option to use coded shipping instructions is in use. If it is in use, then setting this parameter to Y (Yes) will force the entry in 'ShippingInstrs' to be validated against the table of Shipping Instructions in SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ValidProductClassList" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The list of valid product classes for this customer. If this list is supplied, the e.net Product Class Security is ignored.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="WarehouseListToUse" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The list of warehouses to use. If there is no warehouse supplied on the individual stock lines or on the order header, a warehouse will be selected from this list, provided that the stock code is stocked in that warehouse. These are processed from left to right.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="WarnIfCustomerOnHold" default="N">
<xsd:annotation>
<xsd:documentation>Use this element to affect the action taken when a customer is on hold. The default is 'N', which means that an order placed for a customer on hold will be rejected. If set to 'Y', then the fact that a customer is on hold will be treated as a warning, and the setting of the paramter 'IgnoreWarnings' will be used to determine if the order is reported as an error, a warning or accepted.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PutEntireQuantityOnNewLoadWhenChanged" default="N">
<xsd:annotation>
<xsd:documentation>Use this element when Load Planning is in use. If the quantity on the detail line is changed, should the entire quantity be on a new load, or just the portion not allocated. Default = N - Only portion not allocated will be on new load. Y - Entire quantity will be put on to new load.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MinimumChargeLineZero" default="N">
<xsd:annotation>
<xsd:documentation>This parameter only applies when the order customer has a minimum order value set. If a minimum order line is to be added to the order, and this flag is 'Y', then the minimum charge will be set to zero value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UpdateWhLast">
<xsd:annotation>
<xsd:documentation>This element indicates whether to update the warehouse stock after adding all sales order lines. This is used to improve performance. Valid values are 'Y' and 'N' (default). Pleae note that this only applies when adding a new order.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ConfirmQuote">
<xsd:annotation>
<xsd:documentation>This element is only set to 'Y' if called from Quotation Confirmation, to be used when validating quote if creating sales order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="1"/>
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value=" "/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IncludeDimensionAnalysis" default="N">
<xsd:annotation>
<xsd:documentation>This option determines whether to use dimension analysis against the entity. If set to 'Y' then dimension analysis will be applied against the entity when capturing at source. If set to 'N' then GL dimensions will be applied when posting to general ledger. If the source is not linked to any dimension categories and dimension priorities are set to ledger code, then GL dimensions will always be applied. The default is 'N'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>The DOC.XML and DOC.XSD files indicate the schema and an instance of an XML document for this business object.
SORTOIDOC.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2025 SYSPRO Ltd. -->
<!--
This is an example XML instance to demonstrate
use of the Sales Order Transaction Posting Business Object
-->
<SalesOrders xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="SORTOIDOC.XSD">
<TransmissionHeader>
<TransmissionReference>00000000000003</TransmissionReference>
<SenderCode />
<ReceiverCode>HO</ReceiverCode>
<DatePrepared>2006-11-04</DatePrepared>
<TimePrepared>11:55</TimePrepared>
</TransmissionHeader>
<Orders>
<OrderHeader>
<CustomerPoNumber>C1000</CustomerPoNumber>
<OrderActionType>A</OrderActionType>
<NewCustomerPoNumber />
<Supplier />
<Customer>000010</Customer>
<OrderDate>2006-11-04</OrderDate>
<InvoiceTerms>0</InvoiceTerms>
<Currency>$</Currency>
<ShippingInstrs>Ship via Hong Kong</ShippingInstrs>
<ShippingInstrsCode>R</ShippingInstrsCode>
<CustomerName>The SYSPRO Outdoors Company</CustomerName>
<ShipAddress1>This is the alternate delivery address 1</ShipAddress1>
<ShipAddress2>This is the alternate delivery address 2</ShipAddress2>
<ShipAddress3>This is the alternate delivery address 3</ShipAddress3>
<ShipAddress3Locality>This is the delivery address 3 location</ShipAddress3Locality>
<ShipAddress4>This is the alternate delivery address 4</ShipAddress4>
<ShipAddress5>This is the alternate delivery address 5</ShipAddress5>
<ShipPostalCode>90210</ShipPostalCode>
<ShipGpsLat>12.123456</ShipGpsLat>
<ShipGpsLong>123.123456</ShipGpsLong>
<LanguageCode></LanguageCode>
<Email>Sender001@Sender001.com</Email>
<OrderDiscPercent1>2.50</OrderDiscPercent1>
<OrderDiscPercent2>1.50</OrderDiscPercent2>
<OrderDiscPercent3>1.00</OrderDiscPercent3>
<Warehouse>E</Warehouse>
<SpecialInstrs>Handle with care</SpecialInstrs>
<SalesOrder>221124</SalesOrder>
<OrderType>1</OrderType>
<MultiShipCode />
<ShipAddressPerLine />
<AlternateReference />
<Salesperson>100</Salesperson>
<Branch />
<Area />
<RequestedShipDate>2006-12-20</RequestedShipDate>
<InvoiceNumberEntered />
<InvoiceDateEntered />
<OrderComments />
<Nationality />
<DeliveryTerms />
<ShippingLocation></ShippingLocation>
<TransactionNature />
<TransportMode />
<ProcessFlag />
<RegimeCode />
<PortOfDispatch />
<TaxExemptNumber />
<TaxExemptionStatus />
<GstExemptNumber />
<GstExemptionStatus />
<ApplyWithholdingTax />
<CompanyTaxNumber />
<ShipAddressPerLineTax>H</ShipAddressPerLineTax>
<CancelReasonCode />
<DocumentFormat />
<State />
<CountyZip />
<City />
<DeliveryRouteAction>N</DeliveryRouteAction>
<DeliveryRoute></DeliveryRoute>
<InvoiceWholeOrderOnly />
<DispatchWholeOrderOnly />
<SalesOrderPromoQualifyAction>W</SalesOrderPromoQualifyAction>
<SalesOrderPromoSelectAction>A</SalesOrderPromoSelectAction>
<GlobalTradePromotionCodes>GLACC,GLFREE</GlobalTradePromotionCodes>
<GlobalFreeGoodsSelection>
<GlobalFreeGoodsPromotion>GLFREE</GlobalFreeGoodsPromotion>
<GlobalFreeGoodsStock>A101</GlobalFreeGoodsStock>
</GlobalFreeGoodsSelection>
<POSSalesOrder></POSSalesOrder>
<IncludeInMrp>Y</IncludeInMrp>
<PriceGroupLevel>C</PriceGroupLevel>
<PriceGroup>PG1</PriceGroup>
<ExchangeRateFixed>N</ExchangeRateFixed>
<ExchangeRate></ExchangeRate>
<eSignature />
</OrderHeader>
<OrderDetails>
<StockLine>
<CustomerPoLine>1</CustomerPoLine>
<LineActionType>A</LineActionType>
<LineCancelCode />
<StockCode>B100</StockCode>
<StockDescription>Bicycle</StockDescription>
<Warehouse>FG</Warehouse>
<CustomersPartNumber>FF334221</CustomersPartNumber>
<OrderQty>5</OrderQty>
<OrderUom>EA</OrderUom>
<Price>400</Price>
<PriceUom>EA</PriceUom>
<PriceCode />
<PriceGroupRule>0001</PriceGroupRule>
<Catalog />
<CatalogLineNumber />
<AlwaysUsePriceEntered />
<Units />
<Pieces />
<ProductClass />
<LineDiscPercent1>0.5</LineDiscPercent1>
<LineDiscPercent2>0</LineDiscPercent2>
<LineDiscPercent3>0</LineDiscPercent3>
<AlwaysUseDiscountEntered>N</AlwaysUseDiscountEntered>
<CustRequestDate>2006-12-20</CustRequestDate>
<CommissionCode />
<LineShipDate />
<LineDiscValue>0</LineDiscValue>
<LineDiscValFlag />
<OverrideCalculatedDiscount />
<UserDefined>USER</UserDefined>
<NonStockedLine />
<NsProductClass>NSPR</NsProductClass>
<NsUnitCost />
<UnitMass />
<UnitVolume />
<StockTaxCode />
<StockNotTaxable />
<StockFstCode />
<StockNotFstTaxable />
<StockWhtCode />
<AllocationAction />
<ConfigPrintInv />
<ConfigPrintDel />
<ConfigPrintAck />
<TariffCode />
<LineMultiShipCode />
<SupplementaryUnit>N</SupplementaryUnit>
<SupplementaryUnitsFactor />
<SupplementaryUnitsMethod>M</SupplementaryUnitsMethod>
<ReserveStock />
<ReserveStockRequestAllocs />
<TradePromotionCodes>BIKEACCR,FREE1</TradePromotionCodes>
<FreeGoodsSelection>
<FreeGoodsPromotion>FREE1</FreeGoodsPromotion>
<FreeGoodsStock>B100</FreeGoodsStock>
</FreeGoodsSelection>
<IncludeInMrp>Y</IncludeInMrp>
<DeliveryLoad>
<DeliveryRouteCode></DeliveryRouteCode>
<DeliveryDate></DeliveryDate>
<DeliverySequence></DeliverySequence>
</DeliveryLoad>
<Intrastat>
<IntrastatExempt>Y</IntrastatExempt>
<TriangulationRole></TriangulationRole>
<DispatchState></DispatchState>
<DestinationState></DestinationState>
<CountryOfOrigin></CountryOfOrigin>
</Intrastat>
</StockLine>
<CommentLine>
<CustomerPoLine>2</CustomerPoLine>
<LineActionType>A</LineActionType>
<Comment>Ensure saddle is color coded</Comment>
<AttachedLineNumber>1</AttachedLineNumber>
<CommentType />
</CommentLine>
<MiscChargeLine>
<CustomerPoLine>3</CustomerPoLine>
<LineActionType>A</LineActionType>
<LineCancelCode />
<MiscChargeValue>78.56</MiscChargeValue>
<MiscChargeCost>20.00</MiscChargeCost>
<MiscQuantity>3</MiscQuantity>
<MiscProductClass>_OTH</MiscProductClass>
<MiscTaxCode>A</MiscTaxCode>
<MiscNotTaxable />
<MiscFstCode>B</MiscFstCode>
<MiscNotFstTaxable />
<MiscWhtCode />
<MiscDescription>Sundry Items</MiscDescription>
<MiscChargeCode />
<MiscTariffCode />
<MiscSvcChargePrice />
<ConfigPrintInv />
<ConfigPrintDel />
<ConfigPrintAck />
</MiscChargeLine>
<FreightLine>
<CustomerPoLine>4</CustomerPoLine>
<LineActionType>A</LineActionType>
<LineCancelCode />
<FreightValue>19.00</FreightValue>
<FreightCost>12.00</FreightCost>
<FreightTaxCode>A</FreightTaxCode>
<FreightNotTaxable />
<FreightFstCode>B</FreightFstCode>
<FreightNotFstTaxable />
<FreightWhtCode />
</FreightLine>
</OrderDetails>
</Orders>
</SalesOrders>Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2024 SYSPRO Ltd.-->
<!--
Schema for the Sales Order Transaction Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="AllocationAction">
<xsd:annotation>
<xsd:documentation>Specifies whether merchandise lines are to be allocated or placed on back order. If used, this element will override the parameter entry, AllocationAction. Valid entries are 'F' - allocate only if full order quantity is available, 'B' - place whole line on back order, 'A' - allocate available quantity if less than order quantity, and place the remainder on back order. If blank or not entered, 'F' is assumed. If set to 'B' (Back order), then the parameter 'ShipFromDefaultBin' is ignored. Note that any items which are kit items, lot traceable or serialised will still be placed on back order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="F"/>
<xsd:enumeration value="B"/>
<xsd:enumeration value="A"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AlternateReference">
<xsd:annotation>
<xsd:documentation>This is the alternate key to be used when creating the sales order. It must comply with the type of default alternate key defined in Sales Orders Setup (i.e. Branch, Geographic Area or Warehouse). If Alternate Key is mandatory and this element is not supplied, the alternate key will be set to the default alternate key. If there is no default, it will be rejected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AlwaysUseDiscountEntered">
<xsd:annotation>
<xsd:documentation>If this element is set to 'Y' and a discount is entered, the discount is applied to the price for the line. Defaults to 'N'. This option is only applicable when adding a new line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AlwaysUsePriceEntered">
<xsd:annotation>
<xsd:documentation>Specifies that the price supplied in the element 'Price" on this detail line is to be used instead of any price calculated using the SYSPRO configuration parameters(Y - Yes, N - No). If not supplied, then the contents of the parameter 'AlwaysUsePriceEntered' will be used. This is only relevant for a new line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Area">
<xsd:annotation>
<xsd:documentation>This is the geographic area for this sales order. If supplied it must be valid. If not supplied the geographic area is picked up from the customer account.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AttachedLineNumber">
<xsd:annotation>
<xsd:documentation>This is the detail line number to which the comment line is attached.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Branch">
<xsd:annotation>
<xsd:documentation>This is the branch for this sales order. If supplied it must be valid. If not supplied the branch is picked up from the customer account.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CancelReasonCode">
<xsd:annotation>
<xsd:documentation>This element is only required if the sales order has an OrderActionType of 'D' - delete. If the SYSPRO setup option to retain analysis details for cancelled order lines is selected, then the contents of this element must be a valid Cancel Reason code within SYSPRO. It can contain 1 to 6 alphanumeric characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Catalog">
<xsd:annotation>
<xsd:documentation>If using Pricing by Price Groups and adding a new stocked line, you can supply a valid sales catalog to select a price.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CatalogLineNumber">
<xsd:annotation>
<xsd:documentation>If using Pricing by Price Groups and adding a new stocked line, you can supply a valid sales catalog line to select a specific price for the stock code. This element is mandatory when the Catalog element is supplied, and cannot be zeroes</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="City">
<xsd:annotation>
<xsd:documentation>This is the city code that is part of the extended tax code that will be used for the order. It must make up a valid extended tax code if entered. If not supplied, then the SYSPRO rules for obtaining the extended tax code will be used.
Note: The Extended tax code field is only displayed if your nationality code is defined as USA and either the AVP sales tax system is required or you require tax by advanced geocodes (Tax Options Setup).
Format is 3 character alphanumeric (Advanced geocodes) or 2 characters alphanumeric (AVP sales tax).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Comment">
<xsd:annotation>
<xsd:documentation>This is the comment. The format is 100 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CommentLine">
<xsd:annotation>
<xsd:documentation>This element specifies that the sub-elements make up a detail sales order line for a comment line.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="CustomerPoLine"/>
<xsd:element ref="LineActionType"/>
<xsd:element ref="Comment"/>
<xsd:element ref="AttachedLineNumber" minOccurs="0"/>
<xsd:element ref="CommentType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CommentType" default="I">
<xsd:annotation>
<xsd:documentation>The comment type specifies whether the comment is for the order only, or for both order and invoice. The valid entries are 'O' (Order only), and 'I' (Invoice and Order) and blank. The default is 'I' . This is only used when adding a new comment line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="O"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CommissionCode">
<xsd:annotation>
<xsd:documentation>If entered, this is used to override the commission code against the price code, or in the setup. If entered, it is cehcked to be a valid commission code in SYSPRO, and is treasted as a warning if not valid.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CompanyTaxNumber">
<xsd:annotation>
<xsd:documentation>This is the customer's company tax registration number. If it is not supplied, the company tax registration number from the Customer Master table is used. The element can contain up to 15 alphanumeric characters. Although the element is only meaningful for a taxable order, if suppllied it will be used, regardless of the type of order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ConfigPrintInv">
<xsd:annotation>
<xsd:documentation>This element is only relevant when the business object is called by the Product Configurator, and will be ignored at any other time. It determines whether the product configurator line will be printed on an invoice. Valid entries are 'Y' (print), 'N' (do not print). If not supplied or left blank, then 'Y' is assumed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ConfigPrintDel">
<xsd:annotation>
<xsd:documentation>This element is only relevant when the business object is called by the Product Configurator, and will be ignored at any other time. It determines whether the product configurator line will be printed on a delivery note. Valid entries are 'Y' (print), 'N' (do not print). If not supplied or left blank, then 'Y' is assumed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ConfigPrintAck">
<xsd:annotation>
<xsd:documentation>This element is only relevant when the business object is called by the Product Configurator, and will be ignored at any other time. It determines whether the product configurator line will be printed on an order acknowledgement. Valid entries are 'Y' (print), 'N' (do not print). If not supplied or left blank, then 'Y' is assumed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CountyZip">
<xsd:annotation>
<xsd:documentation>This is the county or zip code that is part of the extended tax code that will be used for the order. It must make up a valid extended tax code if entered. If not supplied, then the SYSPRO rules for obtaining the extended tax code will be used.
Note: The Extended tax code field is only displayed if your nationality code is defined as USA and either the AVP sales tax system is required or you require tax by advanced geocodes (Tax Options Setup).
Format is 5 character alphanumeric (AVP sales tax) or 4 characters alphanumeric (Advanced geocodes).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Currency">
<xsd:annotation>
<xsd:documentation>The currency code used for the values within this order. If this is not present the currency code held against the relevant customer within SYSPRO is used. If present, then it must match the currency against the relevant customer, and must be a valid curreny code within SYSPRO. The format is 3 characters, alphanumeric. This element is ignored for a changed order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustRequestDate" type="xsd:date">
<xsd:annotation>
<xsd:documentation>This is the date that the customer has requested shipment of this detail line. The format is CCYY-MM-DD. If no date is supplied for a new detail line, then it is calculated as today's date plus MinimumDaysToShip from the supplied parameter file. If there is no MinimumDaysToShip entry then the SYSPRO field Minimum Number of Days To Ship against the operator code is added to today's date. If RequestedShipDate is supplied, a check is made that it is at least MinimumDaysToShip (or Minimum Number of Days To Ship if MinimumDaysToShip is not in the parameter file) days in to the future. If this date is supplied for a changed line, it is used to update only the customer request date.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Customer">
<xsd:annotation>
<xsd:documentation>The customer code will be used if the SenderCode element is empty. If Customer is supplied this customer account must not be on hold. If multiple customers are allowed for sub-accounts, this customer must be attached as a sub-account of SenderCode. The format is 7 characters, alphanumeric or numeric depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomerName">
<xsd:annotation>
<xsd:documentation>This is the customer name to appear against the sales order. If this is left blank it will default to the customer name held against the customer account within SYSPRO. The format is 50 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomerPoLine">
<xsd:annotation>
<xsd:documentation>For a new order, this will be the line number from the customer's original order, and may not relate to the sales order line number within SYSPRO as comment or components may be added automatically, in which case multiple lines may be present for each line. If the LineActionType is C or D (change or cancel) this entry is mandatory, and refers to the actual line number on the order. This can be from 1 to 9999.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomerPoNumber">
<xsd:annotation>
<xsd:documentation>The use of this element is based on the setting of the parameter 'CheckForCustomerPoNumbers'. If the parameter is set to 'Y' (the default), then the element 'CustomerPoNumber' must be supplied when adding a sales order. If set to 'N', then the element may be missing, or may be blank. If set to 'C' (customer) then the check is based on the setting of the SYSPRO Customer Maintenance option 'Customer purchase order number mandatory'.. If the order is for a sub-account that has a store number,and the element is blank, then the store number will be used as the customer purchase order number. If the SYSPRO configuration is set so that duplicate purchase order numbers are not allowed, the order will be rejected if this purchase order number already exists. If duplicate purchase order numbers are allowed, but this purchase order number already exists for this customer it will be rejected. There is a parameter 'AllowDuplicateOrderNumbers' which will override the check for duplicate purchase order numbers against the same customer, as long as the SYSPRO configuration is set so that duplicate purchase order numbers are allowed. The format is up to 30 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomersPartNumber">
<xsd:annotation>
<xsd:documentation>If the value of the element StockCode is blank, and this element contains a value, a check is made against the customer/stock code cross-reference file to see if this part number is valid for this customer. If it is, the matching SYSPRO stock code is used for the stock code in sales orders.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DatePrepared" type="xsd:date">
<xsd:annotation>
<xsd:documentation>This is the date that this document was produced and is for reference purposes only. If not supplied it will default to the run date. The format is CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DeliveryDate">
<xsd:annotation>
<xsd:documentation>This is the delivery date for the delivery load. Valid only when Load Planning is in use.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliveryLoad">
<xsd:annotation>
<xsd:documentation>This element specifies the sub elements that make up the delivery load for the detail line.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="DeliveryRouteCode" minOccurs="0"/>
<xsd:element ref="DeliveryDate" minOccurs="0"/>
<xsd:element ref="DeliverySequence" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DeliveryRouteAction" default="N">
<xsd:annotation>
<xsd:documentation>This is only relevant if load planning is in use. 'N', the default - No delivery route required, 'E', use delivery route entered in element 'DeliveryRoute', 'C', use delivery route from customer, 'X', remove exisitng delivery route from order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="X"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliveryRoute">
<xsd:annotation>
<xsd:documentation>Only relevant if load planning is in use. It is used in conjunction with the element 'DeliveryRouteAction'. If entered, and DeliveryRouteAction is 'E', then it must be a valid delivery route code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliveryRouteCode">
<xsd:annotation>
<xsd:documentation>Only relevant if load planning is in use. It is the Delivery Route Code for the delivery load of the detail line. If used it must be a valid delivery route code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliverySequence">
<xsd:annotation>
<xsd:documentation>Only relevant if load planning is in use. It is the Delivery Sequence for the delivery load of the detail line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliveryTerms">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The delivery terms code is optional, but if entered is up to 3 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DocumentFormat">
<xsd:annotation>
<xsd:documentation>This is the document format number to be used when printing the document on SYSPRO. If entered, it must be in the range 0 to 9, A - Z, a-z. If not entered, then the code from the customer will be used. If there is no code on the customer, zero is assumed.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Email">
<xsd:annotation>
<xsd:documentation>This is the e-mail address to be stored against the sales order. The format is 255 characters, alphanumeric. To clear existing email address when changing an order, use the text {blank} or {BLANK}.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="eSignature">
<xsd:annotation>
<xsd:documentation>If required, this element must contain a GUID, for the eSignature system to accept the transaction as having been authenticated. The GUID format is in the format {36303032-3330-3031-3038-323434363433}, where the numbers can be replaced with any character. It is up to the developer to have requested a password to protect the transaction. An example is that a GUID associated with the act of entering a valid password could be obtained and presented.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightCost">
<xsd:annotation>
<xsd:documentation>This is the cost of the freight entry. The format is 12.2 either positive or negative. The negative sign can either precede or follow the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightFstCode">
<xsd:annotation>
<xsd:documentation>This is the Canadian Federal Sales Tax code to be assigned to this freight charge. If the Canadian FST system is in use and a tax code is present, it must be valid within SYSPRO. The format is 3 character, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightLine">
<xsd:annotation>
<xsd:documentation>This element specifies that the sub-elements make up a detail sales order line for a Freight line.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="CustomerPoLine"/>
<xsd:element ref="LineActionType"/>
<xsd:element ref="LineCancelCode" minOccurs="0"/>
<xsd:element ref="FreightValue" minOccurs="0"/>
<xsd:element ref="FreightCost" minOccurs="0"/>
<xsd:element ref="FreightTaxCode" minOccurs="0"/>
<xsd:element ref="FreightNotTaxable" minOccurs="0"/>
<xsd:element ref="FreightFstCode" minOccurs="0"/>
<xsd:element ref="FreightTariffCode" minOccurs="0"/>
<xsd:element ref="FreightNotFstTaxable" minOccurs="0"/>
<xsd:element ref="FreightWhtCode" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="FreightWhtCode">
<xsd:annotation>
<xsd:documentation>This is the withholding tax code to be assigned to the Freight charge. If this is present, and the Withholding tax system is in use at point of capture, it must be a valid SYSPRO withholding tax code. The format is 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightNotFstTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default FST (Canadian tax system) status of the freight detail line. If the order is subject to FST, then setting this element to 'Y' will cause the line to have no FST applied. The element may contain 'Y' (not taxable) or blank (default).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightNotTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default tax status of the freight detail line. If the order is subject to sales tax, then setting this element to 'Y' will cause the line to have no sales tax applied. The element may contain 'Y' (not taxable) or blank (default).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightTaxCode">
<xsd:annotation>
<xsd:documentation>This is the tax code to be assigned to the freight charge. If this is present it must be a valid SYSPRO tax code. The format is 3 character, alphanumeric.When using Descriptive Tax Codes, a descriptive tax code must be provided.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightValue">
<xsd:annotation>
<xsd:documentation>This is the value of the freight charge. The format is 12.2 either positive or negative. The negative sign can either precede or follow the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreightTariffCode">
<xsd:annotation>
<xsd:documentation>This only applies if EC Vat is in use. If entered, the contents will be used as the tariff code for the line.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="GstExemptNumber">
<xsd:annotation>
<xsd:documentation>This is the customer's Gst exemption number. If it is not supplied, the Gst exemption number from the Customer Master table is used. The element can contain up to 15 alphanumeric characters. Although the element is only meaningful for a Gst exempt order where Canadian tax is in force, if supllied it will be used, regardless of the type of order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GstExemptionStatus">
<xsd:annotation>
<xsd:documentation>This is used to override the GSTstatus of the customer if Canadian tax is required. If not given or blank the GSTstatus of the customer is used for a new order. It can be used to change the GSTstatus of an existing order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ApplyWithholdingTax">
<xsd:annotation>
<xsd:documentation>This is used to override the Withholding tax status of the customer. Valid options are "Y" - Yes, apply withholding tax and "N" - No, do not apply witholding tax. If not defined the Company tax option will be used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InvoiceDateEntered">
<xsd:annotation>
<xsd:documentation>The invoice date may only be supplied if the sales order is to be created in a status of 8. It may only be supplied if the SYSPRO configuration rules allow it to be supplied, or if the parameter AllowInvoiceInformationEntry is set. The format is CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InvoiceNumberEntered">
<xsd:annotation>
<xsd:documentation>The invoice number may only be supplied if the sales order is to be created in a status of 8. It may only be supplied if the SYSPRO configuration rules allow it to be supplied, or if the parameter AllowInvoiceInformationEntry is set. The entry must follow the SYSPRO configuration rules for the type of invoice number.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InvoiceTerms">
<xsd:annotation>
<xsd:documentation>This element contains the invoice terms code for the transaction. If it is not present the invoice terms code for the relevant customer is obtained from SYSPRO. The format is 2 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InvoiceWholeOrderOnly">
<xsd:annotation>
<xsd:documentation>This element is used in conjunction with the SYSPRO customer rule 'Invoice whole orders only' . This element may be used to over-ride the rule for an individual order only. it may only be used if the operator has authority to do this.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DispatchWholeOrderOnly">
<xsd:annotation>
<xsd:documentation>This element is used in conjunction with the SYSPRO customer rule 'Dispatch whole orders only'. An operator may use this element to override the rule for an individual order only and may only use it if they have authority to do so.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineActionType" default="A">
<xsd:annotation>
<xsd:documentation>The action to be performed for this order line. The action can be: A - Add a sales order line, C - Change an existing sales order line, D - Cancel the sales order line. If the OrderActionType is A for a new order, all the detail lines must contain a LineActionType of A.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="D"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineCancelCode">
<xsd:annotation>
<xsd:documentation>This element is only required if the detail line has a LineActionType of 'D' - delete. If the SYSPRO setup option to retain analysis details for cancelled order lines is selected, then the contents of this element must be a valid Cancel Reason code within SYSPRO, or the element 'CancelReasoncode' within the order header must contain a valid Cancel Reason code. It can contain 1 to 6 alphanumeric characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineDiscPercent1">
<xsd:annotation>
<xsd:documentation>The first line discount percentage to be applied to this sales order line. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will be ignored if the customer is subject to contract pricing, unless the 'AlwaysUseDiscountEntered' or the 'OverrideCalculatedDiscount' tags have been set to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineDiscPercent2">
<xsd:annotation>
<xsd:documentation>The second line discount percentage to be applied to this sales order line. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will be applied after LineDiscPercent1. This will be ignored if the customer is subject to contract pricing, unless the 'AlwaysUseDiscountEntered' or the 'OverrideCalculatedDiscount' tags have been set to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineDiscPercent3">
<xsd:annotation>
<xsd:documentation>The third line discount percentage to be applied to this sales order line. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will be applied after LineDiscPercent1 and LineDiscPercent2. This will be ignored if the customer is subject to contract pricing, unless the 'AlwaysUseDiscountEntered' or the 'OverrideCalculatedDiscount' tags have been set to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineDiscValFlag">
<xsd:annotation>
<xsd:documentation>This flag is used to determine the usage of the contents of the element 'LineDiscValue'. When 'LineDiscValue' is non zero, then an entry of 'U' means the value is to be applied as a unit discount. When 'V' or space (the default), then the value is applied as a value discount.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="V"/>
<xsd:enumeration value="U"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineDiscValue">
<xsd:annotation>
<xsd:documentation>This is the discount value to be applied to this detail line. The format is 12.2 positive or negative, and the negative sign can precede or follow the value. If this value is not entered, the type of discount for the line is assumed to be a chain discount. This will only be used if the customer is not subject to contract pricing. The elememt 'LineDiscValflag' is used to decide if the discount is a unit or a value discount.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineMultiShipCode">
<xsd:annotation>
<xsd:documentation>This is only applicable when the order header element 'ShipAddressPerLine' is set to 'Y'. If entered it must be a valid address code for the customer.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LineShipDate">
<xsd:annotation>
<xsd:documentation>This is the expected ship date of this detail line. The format is CCYY-MM-DD. If no date is supplied for a new detail line, then it is taken from the contents of the element CustRequestDate which itself may have been calculated. If it is supplied for a changed line, then it is used to update only the line ship date. If it is supplied, and the parameter 'AcceptEarlierShipDate' is set to 'Y', then this date may be before the ship date on the header.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscChargeCost">
<xsd:annotation>
<xsd:documentation>This is the cost of the miscellaneous charge. The format is 12.2 either positive or negative. The negative sign can either precede or follow the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscChargeLine">
<xsd:annotation>
<xsd:documentation>This element specifies that the sub-elements make up a detail sales order line for a Miscellaneous Charge line.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="CustomerPoLine"/>
<xsd:element ref="LineActionType"/>
<xsd:element ref="LineCancelCode" minOccurs="0"/>
<xsd:element ref="MiscChargeValue" minOccurs="0"/>
<xsd:element ref="MiscChargeCost" minOccurs="0"/>
<xsd:element ref="MiscQuantity" minOccurs="0"/>
<xsd:element ref="MiscProductClass" minOccurs="0"/>
<xsd:element ref="MiscTaxCode" minOccurs="0"/>
<xsd:element ref="MiscNotTaxable" minOccurs="0"/>
<xsd:element ref="MiscFstCode" minOccurs="0"/>
<xsd:element ref="MiscNotFstTaxable" minOccurs="0"/>
<xsd:element ref="MiscWhtCode" minOccurs="0" />
<xsd:element ref="MiscDescription" minOccurs="0"/>
<xsd:element ref="MiscChargeCode" minOccurs="0"/>
<xsd:element ref="MiscTariffCode" minOccurs="0"/>
<xsd:element ref="MiscSvcChargePrice" minOccurs="0"/>
<xsd:element ref="ConfigPrintInv" minOccurs="0"/>
<xsd:element ref="ConfigPrintDel" minOccurs="0"/>
<xsd:element ref="ConfigPrintAck" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="MiscChargeValue">
<xsd:annotation>
<xsd:documentation>This is the value of the miscellaneous charge. The format is 12.2 either positive or negative. The negative sign can either precede or follow the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscDescription">
<xsd:annotation>
<xsd:documentation>This is the description to appear with the miscellaneous charge. The format is 100 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscWhtCode">
<xsd:annotation>
<xsd:documentation>This is the withholding tax code to be assigned to the miscellaneous charge. If this is present, and the Withholding tax system is in use at point of capture, it must be a valid SYSPRO withholding tax code. The format is 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscFstCode">
<xsd:annotation>
<xsd:documentation>This is the Canadian Federal Sales Tax code to be assigned to the miscellaneous charge. If the Canadian FST system is in use and a tax code is present, it must be valid within SYSPRO. The format is 1 character, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscNotFstTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default FST (Canadian tax system) status of the miscellaneous charge detail line. If the order is subject to FST, then setting this element to 'Y' will cause the line to have no FST applied. The element may contain 'Y' (not taxable) or blank (default).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscNotTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default tax status of the miscellaneous charge detail line. If the order is subject to sales tax, then setting this element to 'Y' will cause the line to have no sales tax applied. The element may contain 'Y' (not taxable) or blank (default).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscProductClass">
<xsd:annotation>
<xsd:documentation>This is the product class to be updated with the sales quantity and cost values for the miscellaneous charge. This is a mandatory element, unless a standard code is provided. The product class must be valid within SYSPRO. The format is 20 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscQuantity">
<xsd:annotation>
<xsd:documentation>If using service charges, this is the quantity of the services charges. The format is 12.6positive or negative, where the negative sign can precede or follow the value.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscTaxCode">
<xsd:annotation>
<xsd:documentation>This is the tax code to be assigned to the miscellaneous charge. If this is present it must be a valid SYSPRO tax code. The format is 3character, alphanumeric.When using Descriptive Tax Codes, a descriptive tax code must be provided.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscChargeCode">
<xsd:annotation>
<xsd:documentation>This element is used to select a standard service charge on which to base the miscellaneous line. It is only relevant when a line is added. If entered, it must represent a standard SYSPRO service charge code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MiscTariffCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This only applies if EC Vat is in use. If entered, the contents will be used as the tariff code for the line.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MiscSvcChargePrice">
<xsd:annotation>
<xsd:documentation>The price of the Service Charge. Will only be used if MiscChargeCode is not blank. The format is 10.5.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MultiShipCode">
<xsd:annotation>
<xsd:documentation>The contents of this element can be used to select one of the predefined multiple ship to addresses against this customer. The format is 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Nationality">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The nationality code if entered must be valid against the table of nationality codes in SYSPRO. If not entered, it will default to the nationality against the customer. The format is up to 3 characters alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NewCustomerPoNumber">
<xsd:annotation>
<xsd:documentation>This is only relevant if changing an order. This element is used to allow the existing customer purchase order number on a sales order to be changed. If the SYSPRO configuration is set so that duplicate purchase order numbers are not allowed, the change will be rejected if this purchase order number already exists. If duplicate purchase order numbers are allowed, but this purchase order number already exists for the customer it will be rejected. There is a parameter 'AllowDuplicateOrderNumbers' which will override the check for duplicate purchase order numbers against the same customer, as long as the SYSPRO configuration is set so that duplicate purchase order numbers are allowed. The format is up to 30 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NonStockedLine">
<xsd:annotation>
<xsd:documentation>This element is used in conjuction with the parameter 'AllowNonStockedItems'. When the parameter is set to 'S' (specify), then this element is used to determine if a line is for a non-stocked item. Valid entries are 'Y' (yes, a non-stocked line), or blank, the default. This element is normally only relevant for line action type 'A' - add, and will be ignored for other actions. the exception is cancelling a non-stocked line where the non-stocked code is also a valid stocked code. Then the flag must be set to 'Y', and the parameter to 'S'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value=""/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NsProductClass">
<xsd:annotation>
<xsd:documentation>This is the product class to be used for the item if it is non-stocked. If it is a non-stocked item this element is mandatory when adding and must be a valid entry within SYSPRO. When changing a non-stocked item, leaving this field out will use the current product class against the line. The format is 20 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NsUnitCost">
<xsd:annotation>
<xsd:documentation>This is the unit cost of the non-stocked item. The format is 10.5 positive.The element is only relevant for a non-stocked line.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UnitMass">
<xsd:annotation>
<xsd:documentation>This is the unit mass of the merchandise item. The format is 12.6 positive. If this is not given for a stocked line, the unit mass of the inventory item is used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UnitVolume">
<xsd:annotation>
<xsd:documentation>This is the unit volume of the merchandise item. The format is 12.6 positive. If this is not given for a stocked line, the unit volume of the inventory item is used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderActionType" default="A">
<xsd:annotation>
<xsd:documentation>The action to be performed for this order header. The action can be A - Add a sales order, C - Change an existing sales order, D - Cancel the sales order. If adding a sales order header, all detail lines must have an A for LineActionType. If changing an order, the individual order lines may be added, changed or cancelled. If Cancelling an order, all detail lines will be cancelled.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="D"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderComments">
<xsd:annotation>
<xsd:documentation>Order comments can be added as one or more strings. The maximum length of a single string is 400 characters. If a single string is more than 100 characters, it will be broken into more than one line at an appropriate place. The maximum total size of the order comments is 4 lines each of 100 characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderDate" type="xsd:date">
<xsd:annotation>
<xsd:documentation>This is the date the order was placed. The format is CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OrderDetails">
<xsd:annotation>
<xsd:documentation>This element contains the elements that make up the order detail line information. It can contain StockLine (for stocked lines), CommentLine (for comment lines), MiscChargeLine (for lines containing miscellaneous charges) and FreightLine (for lines relating to freight charges).</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="StockLine" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="CommentLine" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="MiscChargeLine" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="FreightLine" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="OrderDiscPercent1">
<xsd:annotation>
<xsd:documentation>The first order discount percentage to be applied to the sales order. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will only be used if a configuration option is set.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderDiscPercent2">
<xsd:annotation>
<xsd:documentation>The second order discount percentage to be applied to the sales order. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will be applied after OrderDiscPercent1. This will only be used if a configuration option is set.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderDiscPercent3">
<xsd:annotation>
<xsd:documentation>The third order discount percentage to be applied to the sales order. This can be up to 100.00, positive or negative. The negative sign can precede or follow the value. This will be applied after OrderDiscPercent1 and OrderDiscPercent2. This will only be used if a configuration option is set.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderHeader">
<xsd:annotation>
<xsd:documentation>This element contains the elements that make up the order header information for a sales order.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="CustomerPoNumber" minOccurs="0"/>
<xsd:element ref="OrderActionType" minOccurs="0"/>
<xsd:element ref="NewCustomerPoNumber" minOccurs="0"/>
<xsd:element ref="Supplier" minOccurs="0"/>
<xsd:element ref="Customer" minOccurs="0"/>
<xsd:element ref="OrderDate" minOccurs="0"/>
<xsd:element ref="InvoiceTerms" minOccurs="0"/>
<xsd:element ref="Currency" minOccurs="0"/>
<xsd:element ref="ShippingInstrs" minOccurs="0"/>
<xsd:element ref="ShippingInstrsCode" minOccurs="0"/>
<xsd:element ref="CustomerName" minOccurs="0"/>
<xsd:element ref="ShipAddress1" minOccurs="0"/>
<xsd:element ref="ShipAddress2" minOccurs="0"/>
<xsd:element ref="ShipAddress3" minOccurs="0"/>
<xsd:element ref="ShipAddress3Locality" minOccurs="0"/>
<xsd:element ref="ShipAddress4" minOccurs="0"/>
<xsd:element ref="ShipAddress5" minOccurs="0"/>
<xsd:element ref="ShipPostalCode" minOccurs="0"/>
<xsd:element ref="ShipGpsLat" minOccurs="0"/>
<xsd:element ref="ShipGpsLong" minOccurs="0"/>
<xsd:element name="LanguageCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is the language code for the address/document, if you have the Multi language documnet printing option switched on</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="Email" minOccurs="0"/>
<xsd:element ref="OrderDiscPercent1" minOccurs="0"/>
<xsd:element ref="OrderDiscPercent2" minOccurs="0"/>
<xsd:element ref="OrderDiscPercent3" minOccurs="0"/>
<xsd:element ref="Warehouse" minOccurs="0"/>
<xsd:element ref="SpecialInstrs" minOccurs="0"/>
<xsd:element ref="SalesOrder" minOccurs="0"/>
<xsd:element ref="OrderType" minOccurs="0"/>
<xsd:element ref="MultiShipCode" minOccurs="0"/>
<xsd:element ref="ShipAddressPerLine" minOccurs="0"/>
<xsd:element ref="AlternateReference" minOccurs="0"/>
<xsd:element ref="Salesperson" minOccurs="0"/>
<xsd:element ref="Branch" minOccurs="0"/>
<xsd:element ref="Area" minOccurs="0"/>
<xsd:element ref="RequestedShipDate" minOccurs="0"/>
<xsd:element ref="InvoiceNumberEntered" minOccurs="0"/>
<xsd:element ref="InvoiceDateEntered" minOccurs="0"/>
<xsd:element ref="OrderComments" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Nationality" minOccurs="0"/>
<xsd:element ref="DeliveryTerms" minOccurs="0"/>
<xsd:element name="ShippingLocation" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The shipping location is optional, but if entered is up to 10 alphanumeric characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="TransactionNature" minOccurs="0"/>
<xsd:element ref="TransportMode" minOccurs="0"/>
<xsd:element ref="ProcessFlag" minOccurs="0"/>
<xsd:element name="RegimeCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The regime code is optional, but if entered is up to 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PortOfDispatch" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The port of dispatch is optional, but if entered is up to 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="TaxExemptNumber" minOccurs="0"/>
<xsd:element ref="TaxExemptionStatus" minOccurs="0"/>
<xsd:element ref="GstExemptNumber" minOccurs="0"/>
<xsd:element ref="GstExemptionStatus" minOccurs="0"/>
<xsd:element ref="ApplyWithholdingTax" minOccurs="0" />
<xsd:element ref="CompanyTaxNumber" minOccurs="0"/>
<xsd:element ref="ShipAddressPerLineTax" minOccurs="0"/>
<xsd:element ref="CancelReasonCode" minOccurs="0"/>
<xsd:element ref="DocumentFormat" minOccurs="0"/>
<xsd:element ref="State" minOccurs="0"/>
<xsd:element ref="CountyZip" minOccurs="0"/>
<xsd:element ref="City" minOccurs="0"/>
<xsd:element ref="DeliveryRouteAction" minOccurs="0"/>
<xsd:element ref="DeliveryRoute" minOccurs="0"/>
<xsd:element ref="InvoiceWholeOrderOnly" minOccurs="0"/>
<xsd:element ref="DispatchWholeOrderOnly" minOccurs="0"/>
<xsd:element ref="SalesOrderPromoQualifyAction" minOccurs="0"/>
<xsd:element ref="SalesOrderPromoSelectAction" minOccurs="0"/>
<xsd:element ref="GlobalTradePromotionCodes" minOccurs="0"/>
<xsd:element name="GlobalFreeGoodsSelection" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>This must be supplied for each qualifying Global Free goods promotion that uses a list of stock codes for the free goods stock code.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="GlobalFreeGoodsPromotion">
<xsd:annotation>
<xsd:documentation>This must be a qualified promotion for the line selected. The code is a maximum of 10 characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalFreeGoodsStock">
<xsd:annotation>
<xsd:documentation>Provide the stock code to be applied to the free goods promotion. This stock code should be part of the list defined for the promotion specified in GlobalFreeGoodsPromotion.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element ref="POSSalesOrder" minOccurs="0"/>
<xsd:element name="IncludeInMrp" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is the flag to which you can choose to Include/Exclude the sales order header from the MRP Calculation. Y/N (Yes/No). Default = Y.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="PriceGroupLevel" minOccurs="0"/>
<xsd:element ref="PriceGroup" minOccurs="0"/>
<xsd:element ref="ExchangeRateFixed" minOccurs="0"/>
<xsd:element ref="ExchangeRate" minOccurs="0"/>
<xsd:element ref="eSignature" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SupplementaryUnitsFactor">
<xsd:annotation>
<xsd:documentation>This entry only applies if the line is a stocked or non-stocked line, and the line requires the use of supplementary units for EC Vat reporting. If supplied, it must be a positive number with up to 6 decimal places.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderQty">
<xsd:annotation>
<xsd:documentation>The quantity of the item that the customer is ordering, in the unit of measure entered in OrderUom. If LineType is A, the OrderQty element is mandatory. If the LineType is C, this is the new quantity to use (ie. the existing order quantity is replaced with this value). The format is 12.6 positive or negative, with either a preceding or following negative. If Multiple Bins are installed, if the stock item is serialized, lot traceable or kit type or if there is not enough stock, the quantity ordered will automatically be placed in back order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderType">
<xsd:annotation>
<xsd:documentation>The contents of this element will update the order type field on the sales order. The order type field is a user-defined means of categorizing sales orders. If the SYSPRO configuration option specifies that OrderType must be valid, the order type will be validated. If not supplied the default order type is used. If no default is present then an error is returned. The format is 2 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderUom">
<xsd:annotation>
<xsd:documentation>The unit of measure for OrderQty for the item. This is mandatory for each new StockLine entry. It will be ignored on a change stock line, as the unit of measure cannot be changed on an existing line. This must be a valid unit of measure within SYSPRO. The format is 10 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Orders">
<xsd:annotation>
<xsd:documentation>This node contains all the information required to add, change or delete a slaes order. It can appear multiple times</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="OrderHeader"/>
<xsd:element ref="OrderDetails" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="OverrideCalculatedDiscount">
<xsd:annotation>
<xsd:documentation>If this element is set, then the discount entered agains tthe line (even if zero) will be used in preference to any calcualted order level discounts for the product class and customer if the customer is set up to use order discounts by product class. The default is 'N'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Pieces">
<xsd:annotation>
<xsd:documentation>If the detail line is a merchandise line, and the stock code is a unit-qty type stock code and the OrderQty element is not supplied, the quantity of the detail line must be supplied as units and pieces. At least one of these elements must be supplied. Both elements must be of the same sign. If processing a change or a deletion, then a quantity is not required.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Price">
<xsd:annotation>
<xsd:documentation>The price of the item in the unit of measure PriceUom. Depending on the SYSPRO configuration options this price will normally be calculated during the import and updated if necessary the format is 10.5.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PriceCode">
<xsd:annotation>
<xsd:documentation>The price code can be supplied for a stocked item only. If entered, it must be a valid price code for the stocked item. It will be considered after the price element, but before using the standard SYSPRO pricing mechanism.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PriceUom">
<xsd:annotation>
<xsd:documentation>The unit of measure that the Price refers to. This is a mandatory field if Price contains an entry. This entry must be a valid price unit of measure within SYSPRO. The format is 10 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PriceGroup">
<xsd:annotation>
<xsd:documentation>If using Pricing by Price Groups and adding a new order, you can supply a valid price group.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PriceGroupLevel">
<xsd:annotation>
<xsd:documentation>If using Pricing by Price Groups and adding a new order, you can supply a valid price group level. If not supplied, the company default will be applied.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:minLength value="0"/>
<xsd:maxLength value="1"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="B"/>
<xsd:enumeration value="F"/>
<xsd:enumeration value="L"/>
<xsd:enumeration value="G"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PriceGroupRule">
<xsd:annotation>
<xsd:documentation>If using Pricing by Price Groups and adding a new stocked line, you can supply a valid price group rule.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExchangeRateFixed" default="N">
<xsd:annotation>
<xsd:documentation>This element is only valid if foreign currency customer.
Valid values are 'Y' and 'N' (default).
If set to 'Y', you can enter an exchange rate to be applied to the sales order, which will not be affected by fluctuating exchange rates.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="1"/>
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ExchangeRate">
<xsd:annotation>
<xsd:documentation>This element is only valid if foreign currency customer and 'ExchangeRateFixed' is set to 'Y'.
You can enter an exchange rate to be applied to the sales order, which will not be affected by fluctuating exchange rates.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ProcessFlag">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The process flag is optional, but if entered is 1 numeric containing 0-9.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ProductClass">
<xsd:annotation>
<xsd:documentation>This is the product class for this sales order line. It is only relevant for a merchandise line. If supplied it must be valid. If not supplied the product class is picked up from the stock item. If the item is non-stocked, then the product class will be taken form the element NsProductClass first.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReceiverCode">
<xsd:annotation>
<xsd:documentation>This is the EDI code for the organization (up to 40 characters, alphanumeric), and is for reference purposes only.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RequestedShipDate" type="xsd:date">
<xsd:annotation>
<xsd:documentation>This is the date that the customer has requested shipment of the whole order. The format is CCYY-MM-DD.
If no date is supplied then it is calculated as today's date plus MinimumDaysToShip from the supplied parameter file. If there is no MinimumDaysToShip entry then the SYSPRO field Minimum Number of Days To Ship is added to today's date.
If RequestedShipDate is supplied and AcceptEarlierShipDate in the parameter file is set to 'N', a check is made that it is equal to or greater than the date calculated above.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReserveStock">
<xsd:annotation>
<xsd:documentation>This element is only relevant if the SO Option to allow reserving of stock is selected. If set to 'Y', then any attempt to allocate stock for a line will result in it being reserved, and not shipped. If set to 'N', then any attempt to allocate stock will result in it being shipped. If the element is not supplied, then the parameter ReserveStock will be used, or the SYSPRO company setting will be used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReserveStockRequestAllocs">
<xsd:annotation>
<xsd:documentation>This element is only relevant if the SO Option to allow reserving of stock is selected, and stock is being reserved not shipped. If set to 'Y', then any lot bin or serial item can only be reserved using the ship rules. If set to 'N', then a lot , serial or bin item can be reserved as detail allocations are not required. If the element is not supplied, then the parameter ReserveStock will be used, or the SYSPRO company setting will be used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrder">
<xsd:annotation>
<xsd:documentation>The sales order number to use. If the OrderActionType is A (Add) and SYSPRO is NOT set up to use automatic sales order numbering, this number will become the sales order number. If the OrderActionType is either C or D (for change or cancel) the sales order number must be supplied. The format is maximum 20 characters, either numeric or alphanumeric, depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrders">
<xsd:annotation>
<xsd:documentation>This is the root element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="TransmissionHeader" minOccurs="0"/>
<xsd:element ref="Orders" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Salesperson">
<xsd:annotation>
<xsd:documentation>This is the salesperson responsible for this sales order. If supplied it must be valid. If not supplied the salesperson is picked up from the customer account.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SenderCode">
<xsd:annotation>
<xsd:documentation>This is the code referring to the sending trading partner. Within SYSPRO you can set up trading partners and give them a code. This code is used to identify them so most of the normal information does not need to be passed. If there is an entry for SenderCode it must be valid. If this code is not supplied then the Customer element customer code will be used. If this is not present then the "Customer to Access" against the operator code is used. If this is also not present the "Customer to Use" code in the supplied parameter file is used. This field is up to 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddress1">
<xsd:annotation>
<xsd:documentation>This is the first line of the delivery address to appear against the sales order. If this and all other address lines are left blank the full address will be taken from the customer account. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddress2">
<xsd:annotation>
<xsd:documentation>This is the second line of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddress3">
<xsd:annotation>
<xsd:documentation>This is the third line of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddress3Locality" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This is the locality of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ShipAddress4">
<xsd:annotation>
<xsd:documentation>This is the fourth line of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddress5">
<xsd:annotation>
<xsd:documentation>This is the fifth line of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 40 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddressPerLine">
<xsd:annotation>
<xsd:documentation>This may be set to 'Y' to indicate that merchandise lines may contain a ship address code that differs from the order ship address code. All lines and associated lines with the same code will be used to produce a separate delivery note.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipGpsLat" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This is the geo location latitude of the delivery address to appear against the sales order. The format is 2.6, positive or negative.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ShipGpsLong" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This is the geo location longitude of the delivery address to appear against the sales order. The format is 3.6, positive or negative.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ShipPostalCode">
<xsd:annotation>
<xsd:documentation>This is the postal code line of the delivery address to appear against the sales order. To remove this line from an existing address when changing an order, use the text {blank} or {BLANK}.The format is 10 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShippingInstrs">
<xsd:annotation>
<xsd:documentation>This contains any shipping instructions that are to be placed against the order. The format is 50 characters, alphanumeric. If the SYSPRO option to use coded shipping instructions is in use then any entry here will be used to over-ride the description against the code. To clear existing shipping instructions when changing an order, use the text {blank} or {BLANK}.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShippingInstrsCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation> If the SYSPRO option to use coded shipping instructions is in use and this element is populated, then the table of Shipping Instructions in SYSPRO is read, and the description used on the header, unless the element ShippingInstrs is populated, which will cause the description to be over-ridden. If the parameter 'ValidateShippingInstrs' is set to 'Y' then this element can contain only a valid shipping code - it may be blank for a changed order.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SpecialInstrs">
<xsd:annotation>
<xsd:documentation>This contains any special instructions that are to be placed against the order. The format is 50 characters, alphanumeric. To clear existing special instructions when changing an order, use the text {blank} or {BLANK}.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="State">
<xsd:annotation>
<xsd:documentation>This is the state code that is part of the extended tax code that will be used for the order. It must make up a valid extended tax code if entered. If not supplied, then the SYSPRO rules for obtaining the extended tax code will be used.
Note: The Extended tax code field is only displayed if your nationality code is defined as USA and either the AVP sales tax system is required or you require tax by advanced geocodes (Tax Options Setup).
Format is 2 character alphanumeric. If the three extended tax entries are left blank, the whole extended tax code will default to that on the customer master.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockCode">
<xsd:annotation>
<xsd:documentation>SYSPRO sales orders can be entered using either the company's stock code (StockCode) or the customer's part number (CustomersPartNumber). If the company's StockCode element is non-blank, a check is made to see if this is a valid stock code, and if it is, it is used. If the company's stock code is either blank or invalid, the CustomersPartNumber element is read and a check is done for the customer/stock code combination using the cross-reference file. If this is a valid part number for the customer, it is used. If the customer's part number is either invalid, or does not exist, a check is made to see if non-stocked lines are allowed. If they are then the line is accepted. The stock item must not be on hold.
If the stock code is under the control of ECC and it is not of type S (for Stock) it will be rejected. If it is type S the line is accepted.
If the action is change, and the stock code is provided, it is used to validate that the line selected for change is the correct line.
The format is 30 characters, numeric or alphanumeric depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockDescription">
<xsd:annotation>
<xsd:documentation>If the customer's part number is missing and the content of StockCode is not valid a check is made to see if non-stocked lines are allowed. If they are, the contents of this element are used as the description of the non-stocked item. The format is 50 characters, alphanumeric.
If the line is a new valid stocked line, and the parameter 'UseStockDescSupplied' is set to 'Y', and the contents of this element are not blank, then the contents of this element are used instead of the description from the Item Master.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockFstCode">
<xsd:annotation>
<xsd:documentation>This is the Canadian Federal Sales Tax code to be assigned to the stock line. If this is present, and the Canadian tax system is in use, it must be a valid SYSPRO tax code. The format is 3 character, alphanumeric. If the setup option 'Sales Order setup - Tax/um - allow changes to tax code for stocked items' is not selected, then any entry in this element will be rejected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockWhtCode">
<xsd:annotation>
<xsd:documentation>This is the WithholdingTax code to be assigned to the stock line. If this is present, and the Withholding tax system is in use at point of capture, it must be a valid SYSPRO withholding tax code. The format is 5 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockLine">
<xsd:annotation>
<xsd:documentation>This element specifies that the sub-elements make up a detail sales order line for a stocked or non-stocked item.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="CustomerPoLine" minOccurs="0"/>
<xsd:element ref="LineActionType"/>
<xsd:element ref="LineCancelCode" minOccurs="0"/>
<xsd:element ref="StockCode" minOccurs="0"/>
<xsd:element ref="StockDescription" minOccurs="0"/>
<xsd:element ref="Warehouse" minOccurs="0"/>
<xsd:element ref="CustomersPartNumber" minOccurs="0"/>
<xsd:element ref="OrderQty" minOccurs="0"/>
<xsd:element ref="OrderUom" minOccurs="0"/>
<xsd:element ref="Price" minOccurs="0"/>
<xsd:element ref="PriceUom" minOccurs="0"/>
<xsd:element ref="PriceCode" minOccurs="0"/>
<xsd:element name="PriceGroupRule" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="4"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Catalog" minOccurs="0"/>
<xsd:element name="CatalogLineNumber" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="4"/>
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="AlwaysUsePriceEntered" minOccurs="0"/>
<xsd:element ref="Units" minOccurs="0"/>
<xsd:element ref="Pieces" minOccurs="0"/>
<xsd:element ref="ProductClass" minOccurs="0"/>
<xsd:element ref="LineDiscPercent1" minOccurs="0"/>
<xsd:element ref="LineDiscPercent2" minOccurs="0"/>
<xsd:element ref="LineDiscPercent3" minOccurs="0"/>
<xsd:element ref="AlwaysUseDiscountEntered" minOccurs="0"/>
<xsd:element ref="CustRequestDate" minOccurs="0"/>
<xsd:element ref="CommissionCode" minOccurs="0"/>
<xsd:element ref="LineShipDate" minOccurs="0"/>
<xsd:element ref="LineDiscValue" minOccurs="0"/>
<xsd:element ref="LineDiscValFlag" minOccurs="0"/>
<xsd:element ref="OverrideCalculatedDiscount" minOccurs="0"/>
<xsd:element ref="UserDefined" minOccurs="0"/>
<xsd:element ref="NonStockedLine" minOccurs="0"/>
<xsd:element ref="NsProductClass" minOccurs="0"/>
<xsd:element ref="NsUnitCost" minOccurs="0"/>
<xsd:element ref="UnitMass" minOccurs="0"/>
<xsd:element ref="UnitVolume" minOccurs="0"/>
<xsd:element ref="StockTaxCode" minOccurs="0"/>
<xsd:element ref="StockNotTaxable" minOccurs="0"/>
<xsd:element ref="StockFstCode" minOccurs="0"/>
<xsd:element ref="StockNotFstTaxable" minOccurs="0"/>
<xsd:element ref="StockWhtCode" minOccurs="0" />
<xsd:element ref="AllocationAction" minOccurs="0"/>
<xsd:element ref="ConfigPrintInv" minOccurs="0"/>
<xsd:element ref="ConfigPrintDel" minOccurs="0"/>
<xsd:element ref="ConfigPrintAck" minOccurs="0"/>
<xsd:element ref="TariffCode" minOccurs="0"/>
<xsd:element ref="LineMultiShipCode" minOccurs="0"/>
<xsd:element name="SupplementaryUnit" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates whether supplementary units apply to the sales order line. (Y - Yes, N - No).
Note: This is only relevent if the EC VAT system is in use.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="SupplementaryUnitsFactor" minOccurs="0"/>
<xsd:element name="SupplementaryUnitsMethod" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This entry only applies if the line is a stocked or non-stocked line, and the line requires the use of supplementary units for EC Vat reporting. (M - Multiply, D - Divide).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="M"/>
<xsd:enumeration value="D"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="ReserveStock" minOccurs="0"/>
<xsd:element ref="ReserveStockRequestAllocs" minOccurs="0"/>
<xsd:element ref="TradePromotionCodes" minOccurs="0"/>
<xsd:element name="FreeGoodsSelection" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>This must be supplied for each qualifying Free goods promotion that uses a list of stock codes for the free goods stock code.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FreeGoodsPromotion">
<xsd:annotation>
<xsd:documentation>This must be a qualified promotion for the line selected. The code is a maximum of 10 characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FreeGoodsStock">
<xsd:annotation>
<xsd:documentation>Provide the stock code to be applied to the free goods promotion. This stock code should be part of the list defined for the promotion specified in FreeGoodsPromotion.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="IncludeInMrp" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is the flag to which you can choose to Include/Exclude the sales order line from the MRP Calculation. Y/N (Yes/No). Default = Y.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="DeliveryLoad" minOccurs="0"/>
<xsd:element ref="Intrastat" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StockNotFstTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default FST (Canadian tax system) status of the stock detail line. If the order is subject to FST, then setting this element to 'Y' will cause the line to have no FST applied. The element may contain 'Y' (not taxable) or blank (default). If the setup option 'Sales Order setup - Tax/um - allow changes to tax code for stocked items' is not selected, and the merchandise line is a stocked line, then an entry of 'Y' in this element will be rejected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockNotTaxable">
<xsd:annotation>
<xsd:documentation>This element is used to override the default tax status of the stock detail line. If the order is subject to sales tax, then setting this element to 'Y' will cause the line to have no sales tax applied. The element may contain 'Y' (not taxable) or blank (default). If the setup option 'Sales Order setup - Tax/um - allow changes to tax code for stocked items' is not selected, and the merchandise line is a stocked line, then an entry of 'Y' in this element will be rejected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockTaxCode">
<xsd:annotation>
<xsd:documentation>This is the tax code to be assigned to the stock line. If this is present it must be a valid SYSPRO tax code. The format is 3 character, alphanumeric. If the setup option 'Sales Order setup - Tax/um - allow changes to tax code for stocked items' is not selected, then any entry in this element will be rejected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Supplier">
<xsd:annotation>
<xsd:documentation>This element is currently for reference purposes only. The format is 15 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TariffCode">
<xsd:annotation>
<xsd:documentation>If entered, the contents will be used as the tariff code for the sales order line for both stocked and non-stocked. If not entered, then the tariff code from the inventory master will be used when adding a stocked line. If EC Vat is in operation, and a tariff code is required, then a blank tariff code will be treated as a warning.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TaxExemptNumber">
<xsd:annotation>
<xsd:documentation>This is the customer's tax exemption number. If it is not supplied, the tax exemption number from the Customer Master table is used. The element can contain up to 30 alphanumeric characters. Although the element is only meaningful for an exempt order, if suppllied it will be used, regardless of the type of order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TaxExemptionStatus">
<xsd:annotation>
<xsd:documentation>This is used to override the tax status of the customer. If not given or blank the tax status of the customer is used for a new order. It can be used to change the tax status of an existing order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="O"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TimePrepared">
<xsd:annotation>
<xsd:documentation>This is the time that the orginal document was prepared and is for reference purposes only. If not supplied it defaults to the run time. The format is HH:MM in the 24 hour clock.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TransactionNature">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The transaction nature code is optional, but if entered is up to 3 numeric digits.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TransmissionHeader">
<xsd:annotation>
<xsd:documentation>The transmission header holds information used to track documents.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="TransmissionReference" minOccurs="0"/>
<xsd:element ref="SenderCode" minOccurs="0"/>
<xsd:element ref="ReceiverCode" minOccurs="0"/>
<xsd:element ref="DatePrepared" minOccurs="0"/>
<xsd:element ref="TimePrepared" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="TransmissionReference">
<xsd:annotation>
<xsd:documentation>This reference is for reference purposes only (up to 14 characters, alphanumeric).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TransportMode">
<xsd:annotation>
<xsd:documentation>This is only relevant for orders placed where the SYSPRO option 'EC Vat system required' is selected. The mode of transport code is optional, but if entered is up to 2 numeric digits.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Units">
<xsd:annotation>
<xsd:documentation>If the detail line is a merchandise line, and the stock code is a unit-qty type stock code and the OrderQty element is not supplied, the quantity of the detail line must be supplied as units and pieces. At least one of these elements must be supplied. Both elements must be of the same sign. If processing a change or a deletion, then a quantity is not required.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UserDefined">
<xsd:annotation>
<xsd:documentation>This is for use by the user, and is not validated. The format is 4 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Warehouse">
<xsd:annotation>
<xsd:documentation>If the warehouse is supplied on the detail line, that is used. If it is not valid then an error is returned. If there is no warehouse against the detail line then the warehouse against the header is used. If this is invalid an error is returned. If there is no warehouse entry against the header the warehouse in the supplied parameter file is used.
If the warehouse record in the parameter file is invalid an error is returned. If there is no warehouse record in the parameter file then the Distribution Warehouse held against the stock code is used. If this is not present then the Warehouse To Use against the stock code is used.
The format is 10 characters, alphanumeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrderPromoQualifyAction">
<xsd:annotation>
<xsd:documentation>This is the action to be applied when qualifying trade promotions. This element is used in conjunction with the element 'SalesOrderPromoSelectAction'.
If 'SalesOrderPromoQualifyAction' is 'W', then the whole order is taken, and all lines are submitted for checking, and all qualifying promotions will be applied, or reapplied to the order.
If 'SalesOrderPromoQualifyAction' is 'S', then only merchandise lines with the 'TradePromotionsCodes' node are submitted for checking, and all qualifying promotions for them will be applied, or reapplied to the order.
'Sales OrderPromoSelectionAction' is only applicable when 'SalesOrderPromoQualityAction' is 'W'. If 'SalesOrderPromoSelectAction' is 'A' (all lines), it has the same effect as selecting 'Requalify' in Sales Order Entry, with the TP setup options 'Automatically select line promotions' and 'Automatically select global promotions' set on. Any line or global promotion codes supplied will be ignored.
If 'SalesOrderPromoSelectAction' is 'S' (selected lines), then only lines containing the 'TradePromotionCodes' element are considered for selection.
The specific promotions required may be provided for the relevant sales order lines. If no promotion codes are given for a selected line, then all promotions for that line are marked as selected. If the GlobalTradePromotionsCodes is supplied, then only those entered will be selected. If the element is supplied, but no codes, then all global promotions for the order are marked as selected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="W"/>
<xsd:enumeration value="S "/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrderPromoSelectAction">
<xsd:annotation>
<xsd:documentation>This is the action to be applied when selecting trade promotions. This element is used in conjunction with the element 'SalesOrderPromoQualifyAction', and is only applicable when 'SalesOrderPromoQualifyAction' is 'W'.
If 'SalesOrderPromoSelectAction' is 'A' (all lines), it has the same effect as selecting 'Requalify' in Sales Order Entry, with the TP setup options 'Automatically select line promotions' and 'Automatically select global promotions' set on. Any line or global promotion codes supplied will be ignored. .
If 'SalesOrderPromoQualifyAction' is 'S', then only merchandise lines with the 'TradePromotionsCodes' node are submitted for checking, and all qualifying promotions for them will be applied, or reapplied to the order.
'Sales OrderPromoSelectionAction' is only applicable when 'SalesOrderPromoQualityAction' is 'W'. If 'SalesOrderPromoSelectAction' is 'A' (all lines), it has the same effect as selecting 'Requalify' in Sales Order Entry, with the TP setup options 'Automatically select line promotions' and 'Automatically select global promotions' set on. Any line or global promotion codes supplied will be ignored.
If 'SalesOrderPromoSelectAction' is 'S' (selected lines), then only lines containing the 'TradePromotionCodes' element are considered for selection.
The specific promotions required may be provided for the relevant sales order lines. If no promotion codes are given for a selected line, then all promotions for that line are marked as selected. If the GlobalTradePromotionsCodes is supplied, then only those entered will be selected. If the element is supplied, but no codes, then all global promotions for the order are marked as selected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="A"/>
<xsd:enumeration value="S"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalTradePromotionCodes">
<xsd:annotation>
<xsd:documentation>This must be a list of qualified global promotions for the order selected. Each code is a maximum of 10 characters, separated by a comma.
If the element SalesOrderPromoSelectAction is 'A', then this is ignored.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalFreeGoodsSelection" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This must be supplied for each qualifying Global Free goods promotion that uses a list of stock codes for the free goods stock code.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TradePromotionCodes">
<xsd:annotation>
<xsd:documentation>This must be a list of qualified promotions for the line selected. Each code is a maximum of 10 characters, separated by a comma.
If the element SalesOrderPromoSelectAction is 'A', then this is ignored.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalFreeGoodsPromotion">
<xsd:annotation>
<xsd:documentation>This must be a qualified promotion for the line selected. The code is a maximum of 10 characters.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalFreeGoodsStock">
<xsd:annotation>
<xsd:documentation>Provide the stock code to be applied to the free goods promotion. This stock code should be part of the list defined for the promotion specified in GlobalFreeGoodsPromotion.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipAddressPerLineTax">
<xsd:annotation>
<xsd:documentation>This element indicates which tax code must be used if ship address is per line. Valid values are 'H' - Tax code from header ship address area or 'L' - Tax code from line ship address area. If not supplied, defaults to 'H'. It only applies if tax by geographic area.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="H"/>
<xsd:enumeration value="L"/>
<xsd:enumeration value=" "/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="POSSalesOrder" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The Sales Order number allocated by SYSPRO Point of Sale. This is only available if the SYSPRO Point of Sale system is currently in use, and a new sales order is being added.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Intrastat">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="0">
<xsd:element ref="IntrastatExempt" minOccurs="0"/>
<xsd:element ref="TriangulationRole" minOccurs="0"/>
<xsd:element ref="DispatchState" minOccurs="0"/>
<xsd:element ref="DestinationState" minOccurs="0"/>
<xsd:element ref="CountryOfOrigin" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="IntrastatExempt">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TriangulationRole" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DispatchState" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DestinationState" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CountryOfOrigin" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Annotation goes here.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>Output XML
The OUT.XML indicates a sample of the XML returned by this business object.
SORTOIOUT.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2023 SYSPRO Ltd.-->
<!--
This is an example XMLOut instance to demonstrate
use of the Sales Order Transaction Posting Business Object
-->
<SalesOrders Language="05" CssStyle="" DecFormat="2" DateFormat="01" Version="6.0.007" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="SORTOIOUT.XSD">
<Order>
<CustomerPoNumber>BAY001-A</CustomerPoNumber>
<SalesOrder>002196</SalesOrder>
<OrderActionType>A</OrderActionType>
<BackOrderComment>One or more lines have been placed on back order for sales order '002196'</BackOrderComment>
<WarningMessages>
<WarningDescription>Line 0001 for stock code 'B100' was placed on back order</WarningDescription>
<WarningDescription>Trade promotions have been processed for sales order '002196'</WarningDescription>
</WarningMessages>
</Order>
<StatusOfItems>
<ItemsProcessed>000001</ItemsProcessed>
<ItemsRejectedWithWarnings>000000</ItemsRejectedWithWarnings>
<ItemsProcessedWithWarnings>000001</ItemsProcessedWithWarnings>
</StatusOfItems>
</SalesOrders>Prerequisites
No prerequisites are required to use this business object.
Limitations
No limitations apply to this business object.
Copyright © 2026 Syspro PTY Ltd.