SAP Business One sales orders, drafted from customer POs and checked row by row.

Someone on your team opens a sales order, picks the customer, types the buyer's PO number into Customer Ref. No. and sets a delivery date. On the Contents tab they add a row per item, often by the customer's own catalog number, and Business One fills in a unit price from wherever its pricing finds one first. Then they check the ship-to on the Logistics tab and choose Add, unless an approval procedure turns the order into a draft first.

For the test, AI reads copies of POs your team has already entered and drafts each as a Business One sales order, header, rows and logistics, with the reason for every value. Nothing is added to your company database. Your reviewer sets each draft beside the saved sales order and marks the differences.

The header, and a document type that can't be mixed. The buyer's PO number usually goes in Customer Ref. No., and the Delivery Date set in the header copies down to every row once the user confirms the prompt. A sales document is either Item or Service type, and SAP's help is plain that one document can't hold both, so a PO for parts plus a labor charge becomes two documents unless the service is set up as an item. Status matters as well: an order still Unapproved can't be drawn into a delivery, and only an Open document can be copied to a target document. The draft fills the header the way your team does, names the document type, and flags every PO that mixes the two.

BP catalog numbers decide what the desk can pick. Customer part numbers live in Business Partner Catalog Numbers, under Inventory and Item Management, entered per customer on the BP tab or per item on the Items tab. With Use BP Catalog Number in Documents selected, a new sales document for that customer shows a BP Catalog No. column in place of Item No., and SAP's help adds a catch: the only items available in that document are the ones with catalog numbers defined. An item the buyer orders for the first time won't come up until someone extends the list. The draft shows the catalog number as printed, the item it maps to, and every row with no catalog entry yet, so a person adds the entry before the order is keyed.

The order Business One searches for a price. SAP's training sets the sequence: a Specific blanket agreement for that customer and item first, then special prices for the business partner, where customer, item and unit of measure must all match, then discount groups, then period and volume discounts, and last the price list on the customer's master data. Special prices sit under Inventory, Price Lists, Special Prices, with separate windows for period discounts and volume discounts, and a price list itself may be calculated from a base price list times a factor. Users check what a customer paid last time with the Last Prices Report, opened from the row with Ctrl+Tab. Each draft names the step that should price each row and the price it should land on, beside the PO's figure, and lists the rows where the two disagree.

Approval procedures and credit warnings. With Activate Approval Procedures on, an approval template can stop a sales order and keep it as a draft: SAP's help says the person entering it is told approval is needed first, the authorizer approves or rejects it from the Messages/Alerts Overview window, and only an approved draft becomes a regular document. A template fires always, or when any one of its terms is met, such as Deviation from Credit Limit, Deviation from Commitment, Gross Profit % or Discount %. Separately, General Settings can check the credit limit and the commitment limit, which also counts undeposited checks, whenever a sales order, delivery, A/R invoice or pick list is added, and the help describes that result as a warning. The draft says which template term each order would meet and which customers would raise a credit warning, for your reviewer to check against what happened.

Ship-to addresses, blanket agreements, and your reviewer. A customer can carry many Ship to addresses, each named by an Address ID and one set as default, and the Logistics tab takes the default unless someone picks another. Rows can carry a ship-to of their own, a field hidden until Form Settings shows it, yet copying that order to a delivery still makes one delivery. Sales blanket agreements are Items or Monetary and General or Specific; only an Approved agreement can be used, Business One links rows to a valid one automatically, a Specific agreement's price beats the customer's pricing while a General one's doesn't, and SAP allows one approved agreement per customer and item for the same period. The draft names the Address ID and the agreement each row should carry, with the open quantity left after it. Your reviewer looks hardest at catalog matches, price sources and agreement links, since those set what the customer is billed.

Once the drafts meet the success criteria, incoming POs get the same drafting for about 30 days.

A person on your team approves, edits or turns back each draft before a sales order is added in SAP Business One, and your own approval procedures still apply there. Whoever looks after your Business One system decides how approved drafts arrive: retyped, or loaded with tools your company or its SAP partner already uses. Your reviewer keeps the same scoring sheet all month.