Customer POs drafted as SX.e sales orders, order type and warehouse included.

Someone opens Sales Order Entry, picks the order type, enters the customer and the PO number, and checks the ship-to and warehouse that came up by default. Then come the lines: products from your file, a nonstock or two for things you don't carry, and a price from whichever record SX.e finds first. If the order trips a hold, it waits until someone with the right security releases it.

For the test, AI does that reading on copies of POs your desk has already entered and writes each one up the way SX.e holds an order: header settings, product lines, nonstock lines and the hold it would land on, with a reason for each choice. It enters nothing in SX.e. Your reviewer sets each draft beside the saved order and marks every field that differs.

The order type sets what happens to stock. Infor's help lists the types Sales Order Entry offers, and they behave differently. A stock order reserves stock when it is entered; a counter sale commits it on the spot. A future order waits for its requested ship date to convert, and a standing order creates a fresh order each time its ship date criteria come around. Future, blanket, blanket release, standing and quote orders all sit at stage 0, Entered, and are never invoiced themselves. Operators see only the types that Limit Order Type in SA Operator Setup allows, and some companies rename the stock order and counter sale labels. The draft names the order type your desk would choose, in your own labels, and quotes what on the PO pointed to it.

Header defaults that are easy to accept without looking. When Require Purchase Order # is set on a customer, the PO number can't be left blank, and the Duplicate Customer PO's setting either refuses a reused number or allows it with a warning that lists the orders already carrying it. A ship-to has to exist for that customer and can't have a closed date. The warehouse comes from Customer Setup, Customer Ship To Setup or the operator's own setup, and the ship via from the customer or the ship-to, sometimes locked so nobody can change it. The draft shows which record supplied each default, so your reviewer can tell a decision from a default nobody questioned, and it flags any PO that names a closed ship-to.

Nonstock lines and what they set in motion. When a buyer asks for something your product file doesn't carry, the nonstock window takes a description, vendor, product line, cost and price, and an NCNR box marks the item non-cancellable or non-returnable. Infor's help is blunt about cost: give a nonstock a price without a cost and the order can't be invoice processed. Create Purchase Order ties a purchase order to the line and needs a vendor. Item Type decides what the nonstock leaves behind: Create As Catalog, Create As Order As Needed Non-Stock, or Review For Inventory, which raises an Event Manager event for someone to look at. The draft fills those fields from your sample and vendor list, suggests the item type your desk used on similar lines, and marks every nonstock that has no cost.

Which price record wins. SX.e prices a line from the price and discount records kept in PD Pricing Setup, searched across eight levels that run from Customer/Product at level 1 to Product Price Type at level 8, with customer price types, product lines, product categories and rebate types in between. Infor's help notes that records tied to a customer and a ship-to are hit before records for the customer alone, and any record can carry an ending date. A quote can even be copied into a customer's type 1 pricing record. So the price a buyer writes can be right for one ship-to and wrong for the next. The draft names the record level it expects to price each line, sets that price beside the PO, and lists every line where the two disagree.

Holds, and what your reviewer watches. The order's Approval field reads y when the order is approved, and any other value means it is on hold; with operational hold codes it stays n until every code is cleared, and nobody types in that field directly. Operators carry approval limits by order type on order total and margin, and Infor's help says trimming lines to get under a limit leaves the approval status unchanged. A stock order or blanket release under the minimum margin goes on margin hold by itself, and once an order reaches stage 3, Shipped, it has to be unshipped before Sales Order Entry can change it. Your reviewer, often the order desk lead or whoever manages SX.e security, looks hardest at order types, nonstock costs and expected holds, because those decide whether an order moves at all.

When the drafts meet the success criteria, the same job runs on incoming POs for about 30 days.

A person on your desk approves, corrects or returns each draft before an order exists in SX.e, and order types, nonstock ties and hold releases stay their decisions. How approved drafts reach SX.e is up to whoever runs your system: keyed by hand, or loaded with tools your company already has. Your reviewer keeps scoring on the same sheet all month.