Sales Order Control

Sales Order Control contains the basic parameters that determine how the system processes sales orders. Additional financial setup parameters are established in Sales Order Accounting Control.

Controls how the system determines the number of items available to allocate. The calculation is the same for all items and sites:

• 1 calculates the quantity available for a new order (including released work orders) by subtracting the quantity already allocated to other orders (determined by the number in the Allocate Sales Order lines due in Days field)

• 2, 3, and 4 are not time-sensitive and allocate all quantities demanded against the total demand in the system, including MRP

Determines the allocation window for sales orders. 0 indicates no allocations. The system only attempts to allocate order lines with a due date within the range defined by this field. For orders due outside the range, Quantity Allocated defaults to 0 regardless of available quantity

Determines how the system handles shortage situations:

• No: Quantity Allocated defaults to Quantity Ordered even if a sufficient quantity to allocate does not exist

If there is no quantity available to allocate, Quantity Allocated defaults to 0

Specifies whether detail allocations are made during order entry. Detail allocations function to assign specific inventory lot/serial numbers and locations to be shipped on an order.

The default value displays and can be changed on each line item

Note: The system automatically generates detail allocations when sales order, distribution order, or RMA packing lists and work order picklists print.

Enter Yes to activate ATP calculation functions for order line-item processing.

Enter the number of days from the current system date that the system should consider when determining ATP.

If you use ATP for family items, review field help for which formula to use.

Enter Yes to calculate the promise date automatically for order-line items. When this field is Yes and you have set up delivery times in Delivery Transit Time Maintenance, the system calculates promise dates.

Note: Entering a promise date manually in the order header frame prevents the system from calculating a promise date for order lines when you enter the lines. However, if you subsequently modify the due date on a line, the system recalculates the promise date when this field is Yes.

Specifies whether only lines with allocated quantities should print from the Sales Order Packing List function:

• Yes: Only line items with a non-zero quantity allocated are printed. This is normally set to Yes when allocations are being used. This enables the sales desk, not the shipping clerk, to control shipments since only allocated quantities print on the packing list, which tells the shipping department what to ship. This process requires that you use packing lists to communicate shipping priorities.

• No: All lines with a non-zero open quantity are printed, regardless of the quantity allocated

Packing lists for sales orders, service engineer orders, and RMA issue lines can be printed using Sales Order Packing List. A number of other fields affect how allocations occur:

Note: If you do not use packing lists, you can choose not to use allocations. Allocations can be turned off by setting Allocate SO Lines due in Days to zero, Limit Alloc to Avail to Allocate to No, and Pick Only Allocated Lines to No. For RMAs, Allocate Days must be set to zero in RMA/RTS Control and for SEOs, Allocate SEO Lines Due in Days must be set to zero in Engineer Order Control.

See Print Only Lines to Pick.

Indicates whether confirmed orders are normally printed. Yes does not prevent sales orders from being printed but sets the default for a new sales order. Sales Order Print only prints sales orders with the print field set to Yes

Indicates whether booking history is maintained. When it is set to Yes, the system keeps an audit trail of all incoming sales orders, including new orders added or existing orders changed. A record is kept in transaction history and identified as type ORD-SO with the item, order quantity, price, cost, date, userid, and other information. You can review this information using booking inquiries and reports

Detailed transaction history can be reviewed using Transactions Detail Inquiry (3.2.1.1)

Example: With booking history, a transaction history record is kept for all additions and changes. If you enter a line item with a quantity of 100 but you meant to enter a quantity of 10, the system tracks the booking for the initial quantity of 100. When you correct the mistake, the system creates two more booking history entries, one for -100 and another for the correct quantity of 10. Therefore, you may end up with many booking history records

Important: Examine the booking history reports available and decide whether you really plan to use them before you consume space with booking history.

The usual number of calendar days elapsing between the date the order is entered and the date it is scheduled to ship to the customer location. If orders are shipped immediately, this field can be left as zero

• When you first enter an order, the due date defaults to the system date plus the shipping lead time, indicating the normal quoted shipping date. The operator can manually change the sales order due date. It is useful for ensuring that promised delivery dates are reasonable

Indicates whether comments are normally entered on each sales order header. Information associated with the header of an order usually applies to the entire order and prints at the top of the order

This setting does not control whether comments can be entered, but determines the default that displays whenever you enter an order

Indicates whether comments are normally entered on each order line. Information associated with the line of an order usually applies to a specific line item and prints following that line

The default method for entering sales order and invoice line items. Values must be S or M:

• Single: You can display and maintain detailed information for each line item. The default is Single

• Multi: You can enter basic information such as item, quantity, and price for up to 12 lines on a single screen. Dates, site, location, tax status, and GL accounts simply default

You can change the method at any time during order entry, and flip back and forth between single and multiple line format

Note: When you first implement QAD Enterprise Applications, use single-line entry mode. It requires only one additional keystroke per line and gives you much more functionality.

Specify the next batch number to be assigned when you run Invoice Post and Print. When assigning a batch number, the system uses the current value, then increments the field by one.

When you post invoices, the system associates the batch number with all the invoices posted at the same time. The customer invoice record includes the batch for reference and it can be used for searches and reporting.

Establishes identifiers for Sales Orders and Invoices. The system updates Next Sales Order as orders are created

Determines the relationship with these modules. Set to Yes to integrate with Accounts Receivable, Sales Analysis, and Trade Management

Indicates whether orders are normally entered as confirmed and determines the default when a new sales order is entered, but it can be changed

Confirmed orders are allocated, consume forecast, and create demands for material planning. Unconfirmed orders do not. They are not considered firm orders until a separate Sales Order Confirmation function is processed.

Note: In a high volume order entry environment, you can choose to enter all orders as unconfirmed and confirm them later in batch. It allows orders to be entered quickly with less processing during order entry. But order promising will be more difficult because allocations do not take place until the order is confirmed.