Half the work in an SAP shop is not a question. It is a task with a shape: orders to raise, quotations to confirm, requisitions to place. It arrives as an email, a WhatsApp message, a spreadsheet somebody already keeps, a PDF order form, and somebody retypes it into SAP.
Automating that is not hard. Taking forty WhatsApp messages and producing forty sales orders is extraction plus a create call, and it demos beautifully.
It is also the half that does not matter.
Why the phrase frightens the right people
Say “bulk creation” to an SAP controller and watch what they hear. Not forty orders raised quickly. They hear forty orders raised without anybody looking, because in their experience that is what the phrase has always meant: a background job, a nightly interface, an integration that posts and reports afterwards.
They are not being obstructive. They are pattern-matching correctly on how bulk operations have historically worked, and the pattern is that volume and human review are treated as a trade.
Any product using the phrase inherits that assumption and has to answer it in the same breath. Answering it three scrolls down is answering it after the reader has already decided.
Volume changes the approval, not whether there is one
The position worth holding is narrow and it is not a compromise: batching changes how many approvals a person gives at once and what they see when they give it. It does not change whether anybody is asked.
A batch of two hundred lines is still two hundred writes into your ERP. The write path has no automatic branch, not a branch that is disabled, or gated behind a permission somebody could grant in a hurry. There is nowhere in the flow for an unapproved write to happen, which is a different kind of guarantee from a rule that says it should not.
That is the easy part to state and it is not sufficient on its own, because an approval a person cannot actually perform is a rubber stamp with an audit trail.
The hard part is making two hundred lines reviewable
One write gets read. Two hundred get skimmed, and a system that produces an unreviewable batch and then collects a signature has built a governance theatre rather than a governance control.
So the burden lands on the presentation, and it is three things.
Every line shows what it was drawn from. Not “sales order for customer 4711” but the message, the row, the paragraph of the email that produced it. A reviewer checking a suspicious line should not have to go and find the source; the line should carry it. This is the same argument as printing a figure’s source: provenance is what makes a thing checkable rather than trusted, and it is as true of a write as of a number.
The unusual lines surface. A batch sorted by arrival order hides its own outliers. The one order with a quantity an order of magnitude off the others, the one with a date in the past, the one for a customer over their credit limit: those are what the review is for, and they should not be discoverable only by reading all two hundred.
Anything unreadable is held out and listed. This is the one people get wrong. A message the system could not parse is not a message it should make its best guess at. It comes out of the batch and appears separately, because a silently invented line and a silently dropped one are both worse than a short batch somebody can see is short. The failure mode to avoid is the one where both ends of the system agree the work is complete and it is not.
What this rules out
Stating the position honestly means stating what it costs.
You cannot use this to run an unattended overnight interface. If your requirement is that orders appear in SAP without a person in the loop, this is the wrong tool, and you want an integration, which is a perfectly reasonable thing to want, built by people who will make you write down what happens when it posts something wrong.
What you get instead is the retyping gone and the review kept. That is a smaller claim than the one the phrase “bulk creation” usually makes, and it is the one that survives the conversation with whoever owns your change control.