Manufacturing / SAP order automation
SAP sales order automation
Mirage Metrics writes email and PDF orders into SAP Business One through the Service Layer, as at Biodéal, or into S/4HANA and ECC, for teams still keying them into VA01. 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.
WHICH INTERFACE
Which SAP interface should an order automation write through?
SAP ships several ways to create a sales order from outside. Which one fits depends on your release, on whether you want a draft or a final order, and on what your SAP team already operates. Every row is a standard SAP interface; no custom ABAP is involved in any of them.
| SAP release | Interface | What it gives | Fits when |
|---|---|---|---|
| SAP Business One (HANA or SQL Server since 10.0) | Service Layer (OData) | A sales order, or a draft a person adds as an order; a preview without creating; business partner catalog numbers, price lists, stock by warehouse | The production deployment at Biodéal; most teams start with drafts |
| S/4HANA | Sales order OData API | A sales order created through the API SAP documents for integrations | Your SAP team prefers an API it can monitor and version |
| S/4HANA or ECC | BAPI_SALESORDER_CREATEFROMDAT2 | A sales order created through the standard BAPI, with the same checks VA01 applies | An ECC landscape, or an integration layer that already calls BAPIs |
| S/4HANA or ECC | ORDERS IDoc | The order as an inbound IDoc, processed like an EDI order, with SAP's IDoc monitoring and reprocessing | You already run EDI through IDocs and want email orders in the same queue |
Mirage has no S/4HANA or ECC deployment in production yet, and says so. The reading and matching layer is the same for every row; only the write differs.
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
FAQ
Frequently asked questions
Put a layer in front of SAP that reads incoming orders, resolves customers and materials against your SAP master data, and creates the sales order through a standard interface: the Service Layer on Business One, or the sales order API, a BAPI or an ORDERS IDoc on S/4HANA and ECC. The order lands in SAP as if it had been keyed in VA01.
Yes, through the same interfaces any integration uses. The AI part is reading an order that no two customers format the same way and deciding what it means; the SAP part is a standard API call. At Biodéal it has created 2,943 orders in SAP Business One since July 2025.
Yes. Everything runs outside SAP and writes through interfaces SAP already ships, so there is no custom ABAP, no modification to your system and nothing to redo at the next upgrade. Your SAP team only has to open the interface and create a technical user.
Both. The production deployment today is on Business One; on S/4HANA and ECC the order is created through the API, BAPI or IDoc your SAP team prefers. The reading and matching layer is the same.
Either. Through the Service Layer, the agent can create the sales order directly or save it as a draft that a person checks and adds as an order. Most teams start with drafts and switch to direct creation customer by customer. At Biodéal, orders are created in SAP Business One through the Service Layer, with about 7% flagged for a person to check.
Leave them on EDI. Their IDocs keep flowing as they do today; this covers the orders that arrive as email and PDF.
Most deployments go live in 4 to 6 weeks, then run in parallel for the first two weeks to confirm accuracy before full cutover.
A fixed-price pilot on a batch of your real orders first, so you see the result before committing. After that, an annual subscription priced by volume, quoted in the first conversation.