An AI assistant created a sales order and its outbound delivery in a live SAP ECC 6 system from two typed requests. It tested the order in SAP first, saved nothing until the user said OK, and both documents were then checked in SAP GUI. This is session 2 of the SAP without SAP GUI series. It shows how to create a sales order in SAP with AI while SAP's own checks stay in charge. Session 1 covered reading data.
The request
The user typed one sentence: "Create a sales order for Smith Inc.: 2 Pump PRECISION 103, delivery today. Test it first and wait for my OK."
There is no order type, sales area, material number or plant in that sentence. A person entering this in VA01 would supply those from memory. The assistant had to find them in SAP.
The test run: nothing is saved
The assistant ran the order as a test in SAP. The test passed with no errors, and nothing was saved. It then showed what it was about to create:
- Customer: Smith Inc. LLC, Maywood, in the US sales area, in USD
- Item: 2 × Pump PRECISION 103 (P-103)
- Requested delivery: 11 November 2026
- Order type: standard order
Then it stopped and waited.
The ambiguity it caught
Before asking for the OK, the assistant pointed out something the user had not mentioned. SAP held a second customer record with the same name, set up for a European sales area in EUR, and several materials were called "Pump PRECISION 103".
It explained which ones it had picked and why: the US customer and material P-103, because they matched each other's sales area and plant. It invited the user to say so if a different customer or material was meant.
Nobody scripted that step. It is what a careful colleague does before posting an order, and it is the reason to test first. A wrong customer on a sales order is cheap to fix before saving and expensive after.
The OK
The user replied: "Ok, create."
Only then did the order exist. SAP created and confirmed standard order 19229 for Smith Inc. LLC: 2 pieces of Pump PRECISION 103, requested delivery 11 November 2026, net value 7,602.00 USD.
The delivery
The next request was shorter, and this time the user gave the go-ahead in the same sentence: "Now create delivery, confirmed to create immediately."
SAP created outbound delivery 80018945 for sales order 19229, for the full quantity of 2 pieces, with delivery date 11 November 2026.
Asked for the details of both documents, the assistant read them back from SAP: the order was fully delivered, and the delivery was open and not yet picked. It named the next steps, picking and posting goods issue.
Checking in SAP GUI
The video then leaves the assistant and opens SAP GUI, because a claim about SAP should be checked in SAP.
| Where | What it shows |
|---|---|
| VA03, display sales order | Order 19229, Smith Inc. LLC, net value 7,602.00 USD |
| VL03N, display outbound delivery | Delivery 80018945, 2 pieces of Pump PRECISION 103 |
| Document flow | Order 19229 and delivery 80018945, linked |
The documents are ordinary SAP documents. They were created through the same standard functions SAP uses when a person enters the order, under the user's own SAP user.
Why the pattern matters: check, post, verify
Writing into SAP is where most teams get nervous, and they should. The session shows the three steps that make it acceptable:
- Check. A test run in SAP, where SAP offers one, before anything is saved.
- Post. Only on an explicit commit. A role can also be read-only, with no way to write at all.
- Verify. A read-back from SAP after posting, so the answer describes what SAP holds, not what the assistant intended.
SAP's own validations run exactly as they do from the transaction. The order is created through the standard BAPI, so pricing, availability, the credit check, incompletion rules and any custom checks in the system all apply. If SAP blocks the order, the assistant gets the same message a user would see, and reports it.
Every step is logged in SAP with the user, the object, the time, the request and the response. The security page lists every control.
Next in the series
Session 3 will cover master data: creating materials by asking.