Creating a purchase order

Uwaga:  SunSystems is extremely customizable as outlined in About this Help. This topic covers all fields available to the Purchase Order Entry function. You may find, therefore, that your form does not cover all of these fields, they may be in a different order or they may be called different names.

You can customize your form so that after you have entered an order line, the focus moves to the next new line so it is ready to be entered. You can do this using the Control Properties in Form Designer, that is, if the Next action is defined as the default Action using Form Designer, then pressing Enter or Return will process the current line and move the focus to the next line.

To create a purchase order use Purchase Order Entry (POE). The form contains header information which applies to all the lines on the order, and purchase order lines for entering individual transaction lines. Your system may have been set up to preset fields on both the line and the header. This simplifies the entry process for repeat information. Once the purchase order lines have been created they are processed further using the options available on the Action menu. They can also be defined as scheduled orders, or called off from a blanket contract. A purchase order can be put on hold at any stage, which prevents further processing until the Release option is selected.

Uwaga: 
  • The purchase type specifies how the order is processed. For example, the stage it must reach before it can be approved or invoiced.
  • Where fields refer to static data, the data must already have been set up. For example, a supplier code must have been defined using Supplier (SUS).

The Purchase Order Entry (POE) form contains the following:

  • Purchase Order Header
  • Purchase Order Lines - General Details
  • Item
  • Payment
  • Pricing
  • Analysis
  • Confirmation Details
  • Receiving Ordered Items
  • Delivery
  • Purchase Requisitioning
  • Purchase Order Actions
  • Purchase Order Lines Actions
  • Characteristics.