PurchaseOrder

Note: This Help contains hyperlinks that are enabled when the Help is accessed within the application. However, if you have accessed this Help via the SunSystems Web portal, hyperlinks are not enabled.

This component allows you set up and maintain purchase orders and runs the Purchase Order Entry (POE) function.

This component also provides various methods that allow you to progress purchase orders through certain stages. If doing so, you must ensure that purchase orders are at the correct stage in order to be processed.

Note: Depending on how your purchase type stages have been set up, some component methods may not be relevant.

There are three ways to improve performance of purchase order imports:

Restricting the payload - the payload definition for purchase orders is composed of all data items that are used within order fulfillment. As your SunSystems installation may not use all available data items, you can reduce the time taken to process purchase 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 Purchase Orders from an external application you can set up a particular purchase type that does not carry out the various calculations, validations and lookups that would normally happen. For example, you might ensure that budget checking and inventory allocation do not occur at order entry. These can significantly increase the time taken to process a given Purchase Order.

Ensure that line numbers are in numerical order as disordered line numbers will impact performance. If both the User Line Number (PurchaseOrder.PurchaseOrderLine.UserLineNumber) and the System Line Number (PurchaseOrder.PurchaseOrderLine.LineNumber) are provided, then User Line Number is used.

Note: SunSystems is unable to export purchase orders that have more than 33 value labels defined on them.

Note: We do not support the import of Purchase Orders using a 'Start of Document', 'Line' or 'End of Document' preset type. 'Start of Document' and 'Line' preset types can cause inconsistency in the line numbers. For example, when importing a new Purchase Order using a 'Start of Document' preset type, the order is created with a preset line, then imported into a Purchase Type that also creates a preset line.

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.