SalesOrder
This component runs the Sales Order Entry (SOE) function and allows you to set up and maintain sales order header information which applies to all the lines on the order and sales order lines for entering individual transaction lines.
This component also provides various methods that allow you to progress sales orders through certain stages. If doing so, you must ensure that sales orders are at the correct stage in order to be processed. For example, you cannot invoice a sales order unless it is available for invoicing.
There are three ways to improve performance of sales order imports:
-
Restricting the payload - the payload definition for sales orders is composed of all data items that are used within Order Fulfilment. As your SunSystems installation may not use all available data items, you can reduce the time taken to process sales orders by ensuring that your payloads only include those data items that you wish to work with.
- Reduce the number of processing options in SunSystems. If you are importing sales orders from an external application you can set up a particular sales type that does not carry out the various calculations, validations and lookups that would normally happen. For example, you might ensure that credit checking and inventory allocation do not occur at order entry. These can significantly increase the time taken to process a giorder entry. These can significantly increase the time taken to proces a given Sales Order.
- Ensure that any line numbers are in numerical order, as disordered line numbers will impact performance. If both the User Line Number (SalesOrder.Line.LineNumber) and the System Line Number (SalesOrder.Line.SalesOrderLineNumber) are provided, then the User Line Number is used.
Creating new orders line using the 'End of Document' preset type will not work, because an empty line is required to insert the new lines information. However, the empty line is not present if this preset type has been used.