1. Purchase Business Setup (PBS) - Gives you one online function to set up rules and controls for the whole purchase activity in your organization. You may need, for example, to set valid accounting periods or rules for budget checking.

2. Purchase Types Setup (PTS) - Allows you to define different types of purchase transactions used in your system. For example, you can define how a purchase order is processed, the stages it passes through, and the document formats it uses.

  2.a. Defining Stages for the Purchase Type - From the Action menu within Purchase Types Setup, select Purchase Stage.
  2.b. Defining Values for the Purchase Type - From the Action menu within Purchase Types Setup, select Purchase Value.
  2.c. Assigning Purchase Presets to the Purchase Type - From the Action menu within Purchase Types Setup, select Purchase Order Assign Preset.
3. Purchase Order Presets (POPS) -  are used to predefine some or all of the entries in a Purchase Type for purchase orders. They are intended to speed up the entry of a purchase transaction, particularly where the data entered is frequently repeated. It also allows you to automate data entry, and so improve accuracy.
4. Transaction References Setup (TRS) - Each type of transaction, for example, a purcahse order or a movement order, needs a unique reference number, which must be set up before the transaction can be processed. You can define the layout and content of transaction references depending on your requirements.
5. Approval Tables Setup (ATS) - Defines approval mechanisms for purchase transactions in your system. These can be set up to enforce approval at the order entry stage, the invoice entry stage, or both. These settings can specify Data Access Groups to have the authority to approve, for example, specific amounts, quantities, items, projects, or cost centres. You can also specify whether their approval limit applies to the value of an individual line, or to the whole order or invoice.
6. Ledger Interface (LIS) - is used to configure the journal transfer from SunSystems Order Fulfilment to SunSystems Financials. Different types of journal can be generated by Order Fulfilment and posted into Financials to reflect different Order Fulfilment transactions and processing stages.
7. Ledger Interface Account Recognition Codes (LIARC) - you to refer to an account code that has been entered elsewhere in a SunSystems module. These codes can be used on SunSystems Order Fulfilment transactions and in the Ledger Interface (LIS) to refer to the particular account.
8. Reason Codes Setup (RCS) - Reasons Codes are used throughout SunSystems to provide explanations. For example, why a Location is shown as locked, or why an order has been cancelled.
9. Unit of Measure Labels Setup (UOM)  - Units of Measure are units that are applied to items in order to quantify them. Units of Measure Labels describe these units. For example, bottles, cans, crates or pallets.
10. Formula Designer (FUD) - is a SunSystems Order Fulfilment application which allows you to create and maintain formulae referenced by value labels associated with order transaction lines.
11. Inspection Codes Setup (INC) - Inspection Codes are a means of attaching a set of simple inspection instructions to an item, which need to be completed at the goods receipt stage of the purchasing process. For example, if the item is clothing, an inspector may wish to check for finishes on seams and buttons
12. Value Labels Setup (VLS) - Value Labels are used to handle amounts in Order Fulfilment, such as quantities and prices, that need to be entered or calculated, stored and reported. They are used for calculations, reporting, approvals, Price Books and Landed Costs.