Blog Posts Process Analysis

Requirements – Sales Order Processing (SO)

Blog: Biz-Performance, David Brown

Sales Order Processing (SO)

1.1 General requirements

(a)
The following order types will be supported:
  • quotation,
  • proforma,
  • repeat order,
  • back order,
  • forward order,
  • order with call-offs,
  • direct invoice/credit note.
(b)
The following data will be stored for each customer:
  • customer code,
  • customer name,
  • customer VAT registration number,
  • customer type (category),
  • five line invoice address plus postcode (many per customer with one default address),
  • country code of customer,
  • five line delivery address plus postcode and country (many per invoice address with one default address),
  • country code for delivery address,
  • default delivery warehouse,
  • sales representative,
  • telephone number,
  • fax number,
  • telex number,
  • payment terms,
  • delivery instructions (per delivery address).
(c)
Stock will be held in multiple warehouses.
(d)
Each customer will allocated to a particular warehouse at delivery address level, and which can be over-ridden during order entry.
(e)
Each warehouse will have multiple bins, with some stock being at more than one bin location.
(f)
The system will maintain a customer/ product discount matrix.
(g)
The system will maintain a file of promotional prices, being customer/ product discount matrices for specific time periods.
(h)
It will be possible to override the prices displayed when the order is input.
(i)
It will be possible to override the line discount percentage when the order is input.
(j)
It will be possible to suppress printing the discount on invoices, i.e. show the net price only.
(k)
It will be possible to bar customers from buying certain product ranges (to prevent customers buying another customer’s own brand goods).
(l)
An expected delivery date will be held for each order line.
(m)
It will be possible to add the following to invoices:
  • free-type text,
  • standard text,
  • fixed charges,
  • charges based on order value,
  • charges based on order weight/ volume,
  • non-stocked product lines,
  • additional discount based on total value.
  • basis of value,
  • type of sale,
  • mode of transport,
(n)
It will be possible to suppress the printing of the above.
(o)
It will be possible to suppress the printing of lines containing components on invoices.
(p)
Foreign currency will be supported by the system. The unit price will be converted to the foreign currency at the current exchange rate.
(q)
There will be no restriction on the number of lines on an order.
(r)
The field size for unit prices will be 999,999.99.
(s)
The field size for quantities will be 9,999,999.
(t)
Sales order processing will have links to the following systems:
  • stock control, for the allocation of stock,
  • sales ledger for posting invoices,
  • project costing, for posting revenue,
  • sales analysis,
  • general ledger, for revenue (unless dealt with elsewhere in system).

1.2 Order input

(a)
Multiple order lines will be contained on a single screen.
(b)
To assist with input there will be an alphanumeric search facility on customer name.
(c)
To assist with input there will be an alphanumeric search facility on product description.
(d)
If it is possible to create a new customer record during order entry, their credit limit will default to zero.
(e)
During order entry it will be possible to make enquiries on customers and products.
(f)
The field for the customer’s own order reference will be 30 alphanumeric characters and be printed on delivery notes and invoices.
(g)
There will be a field for comments on the order entry screen, but these will not appear on documents.
(h)
There will be an option to allocate less stock than is ordered even if there is stock available.
(i)
If a particular order line is out of stock, the system will offer:
  • an alternative product,
  • an alternative warehouse.
(j)
The system will allow for the allocation of stock that is not yet available, thus creating negative free stock.
(k)
If insufficient stock is available, there will be options to:
  • back order the whole order line,
  • allocate available stock and back order the remainder,
  • allocate available stock and drop the remainder of the order line,
  • drop the entire order line.
(l)
If an item is out of stock it will be possible to select an appropriate message to appear on output documents.
(m)
As order lines are input it will be possible to monitor the weight/volume of the order.
(n)
There will be a field for the input of delivery instructions. These may be customer delivery address specific.
(o)
It will be possible to combine multiple deliveries on one order.
(p)
The number of labels required for delivery documentation will be input at the end of the order.
(q)
User-defined analysis codes such as sales representative or customer type will be picked up at order entry time from the customer record, and applied to each order for sales analysis purposes.
(r)
During order input it will be possible to insert/amend/delete/add lines.
(s)
It will be possible to record item serial numbers against each order line after picking as a means of tracking individual stock items so that returns under warranty can be validated.
(t)
A customer record can be set to accept no new orders.
(u)
The order will be stopped at the start of the order entry if the outstanding balance and existing orders exceed the credit limit.
(v)
The order will be stopped if the outstanding balance, existing orders and the new order together exceed the credit limit.
(w)
Only the credit controller will be able to release stopped orders for further processing.
(x)
When credit notes are input, the operator will be able to select whether:
  • stock quantities will be increased,
  • stock quantities will not be increased.
(y)
Forward orders, repeat orders and call-offs will be automatically released as current orders based on due date.
(z)
Quotations and pro-formas will be converted to current orders when accepted.
(aa)
Back orders will be released when stock becomes available, using the following methods:
  • manual on an order by order basis,
  • automatically using customer priority, due date or order date,
  • when a current order for the same customer is processed.
(ab)
It will be possible to put orders and order lines on hold to prevent further processing.

1.3 Sales order cycle

(a)
The following processing cycle will be followed, but may be customised if required:
  • input/create the order,
  • print acknowledgements where required,
  • print picking lists,
  • print delivery notes,
  • print delivery labels,
  • deliveries (or despatches) confirmed by calling up the order,
  • print the invoices after confirmation,
  • print specific invoices without confirmation stage (i.e. direct invoicing),
  • post to sales ledger, general ledger and sales analysis files.

1.4 Data output

1.4.1 Enquiries

(a)
Screen enquiries will be made on orders by the following routes:
  • by order number,
  • by product line,
  • by customer,
  • by due date.
(b)
In each instance, enquiries may be restricted to individual or combinations of transactions.
(c)
It will be possible to enquire on the status of each order line as it passes through the system, and to review the documents printed to date.

1.4.2 Documents

(a)
The following user-definable documents will be printed by the system:
  • quotations,
  • proformas,
  • acknowledgements,
  • picking lists,
  • despatch/delivery notes,
  • labels,
  • invoices,
  • credit notes.
(b)
The delivery note reference will appear on labels.
(c)
Picking lists may be printed for single or multiple deliveries.
(d)
Picking lists will group stock requirements by product for multiple deliveries.
(e)
Picking lists will be printed for stock transfers and issues.
(f)
Picking lists will be printed at the relevant stock location.
(g)
Picking lists will be sorted by bin location.
(h)
Invoices will be printed with standard user-definable messages.
(i)
It will be possible to reprint all of a document print run, or ones for individual orders.

1.4.3 Reports

(a)
Outstanding order reports may be selected and sorted using the following fields:
  • customer,
  • product line,
  • commodity code,
  • product group,
  • order type,
  • order date,
  • due date,
  • warehouse,
  • sales representative,
  • order number,
  • margin.
(b)
The information appearing on order reports will include:
  • quantity – net mass, weight in kilogrammes,
  • quantities – other units,
  • gross sales values,
  • net sales values.
(c)
The content of reports on orders will be user-defined and may be changed at run-time.

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="https://www.businessprocessincubator.com/content/requirements-sales-order-processing-so/?feed=html" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples

BPMN.org

XPDL.org

×