Manufacturing / SAP order automation
SAP sales order automation
SAP sales order automation for teams still keying customer orders into VA01 or Business One by hand. Send us a batch of real orders and within a week you see each one as the sales order SAP would receive, with sold-to, ship-to, material and quantity resolved, and every doubtful line flagged.
Writing orders to SAP Business One at Biodéal since July 2025.
The reality
In most SAP shops, VA01 is still where email orders go to be retyped. EDI covers the large accounts through IDocs; everyone else sends a PDF, and a customer service rep copies the sold-to party, material numbers and quantities across, one screen at a time.
What Mirage does
Email to SAP order entry
Mirage sits in front of SAP, not inside it. It reads the order, resolves it against your SAP master data and creates the sales order through an interface SAP already provides.
SAP order entry without ABAP
Orders are created through standard interfaces: the Service Layer on SAP Business One; on S/4HANA and ECC, the sales order OData API, BAPI_SALESORDER_CREATEFROMDAT2 or an ORDERS IDoc. No custom ABAP, no change to your SAP core, nothing to carry through an upgrade.
Your master data, kept in sync
Customer and material masters are read from SAP and kept in sync, so a customer's own part number resolves to your material, and the sold-to and ship-to parties resolve from the name and delivery address on the order.
Anything uncertain stops at a person
A line SAP would accept but your team would not, such as an unknown material or a unit that does not match the price, is held back with the reason, while the rest of the order is created.
SAP Business One: how the order is written
The production deployment writes to SAP Business One through the Service Layer, SAP's OData interface for Business One, available on SAP HANA and, since release 10.0, on Microsoft SQL Server. Four choices to settle with your SAP partner before the first order.
A draft to review, or a final order
The Service Layer can create the sales order directly, or save it as a draft that a person opens, checks and adds as an order, and it can preview an order without creating it. Most teams start with drafts and move a customer or an order type to direct creation once it has passed. If you use approval procedures, check with your partner how they apply to orders created through the integration.
Your customers' own part numbers
Business One keeps business partner catalog numbers: each customer's own code for your items. The agent reads them with your price lists, special prices and unit of measure groups, so a line written in the customer's terms becomes your item, unit and price. Stock by warehouse is read when an order needs an availability check.
A dedicated user, and a licence check
The integration logs in as its own Business One user, never as a person's, and its session times out after 30 idle minutes by default. SAP's licence guide treats access through another system as indirect access that your contract has to cover: confirm it with your SAP partner before the pilot.
Limits to plan for
A user-defined field created during the project is visible to the Service Layer only after the Service Layer restarts. A transaction cannot span several requests, so the agent checks for an existing order with the same customer reference before writing, which makes a retry harmless. Since FP 2602, the Service Layer can also send a webhook when an order is created.
The output
VA01 automation, field by field
| Field | On the purchase order | In the SAP sales order | Status |
|---|---|---|---|
| Sold-to party | Buyer name and VAT number | Customer 100482 | Matched |
| Ship-to party↳ The purchase order carried no ship-to number. Its delivery address matched one of the customer's three ship-to parties exactly. | Delivery address, gate 3 | Ship-to 100482-02 | Matched by address |
| Item 10 | Ref. 88-120-B, 40 | Material 4000217, 40 PC | Cross-reference |
| Item 20↳ Two active materials share the same description. Rather than pick one, the line is held with both candidates, and the other items are still created. | Bearing 6204 2RS, 12 | Two active materials match | Sent to a person |
Proof
SAP order intake integration, in production
At Biodéal, an organic dairy distributor, Mirage creates sales orders in SAP Business One through the Service Layer.
Biodéal
48 seconds median from email received to order ready in SAP
2,943 orders created automatically, from 113 distinct customers
Customers matched exactly, then fuzzily, then by address, with cascading discounts applied
SAP sales order automation, on your own orders
Send us a batch of real customer orders and tell us your SAP release. Within a week you get each one back as a sales order, field by field, with what we would hold flagged.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ
Frequently asked questions
Also on this site