SAP® AI live demo: CMR consignment note in 11 minutes
One sentence. One form.
-
Spec
-
Meeting 1
-
Meeting 2
-
Meeting 3
-
One sentence
Everyone talks about AI in SAP®. Few show it. So we show it – where the daily work happens: in SAP® GUI. Part 4 of the series by Josef Lenz, founder of 24-LOG.
The AI builds.
The consultant decides.
The test
One sentence instead of a requirements spec
"Get me the current CMR consignment note from the web and build a print program with Smart Forms and test data."
-
Where the daily work happens
In warehouses, shipping halls and plants, daily work means SAP® GUI: custom transactions, buttons, forms. Fiori is coming, the GUI is staying.
-
First read, then build
The agent researches the structure of the CMR consignment note online and asks five questions. Nothing has been created yet.
-
Plan after just over three minutes
Object by object: structure for the test data, form with Smart Forms, print program.
-
GO first, then the system
The second key: only after the consultant's GO does the agent create anything.
-
About eleven minutes
After about eleven minutes, form, print program and test data are in the system.
-
Four copies, ready to print
In the end, the consignment note is complete – all four copies.
The video
The full story
The video shows the whole way from the sentence to the finished consignment note – recreated from the real session log, the times are real. Below, the whole series, newest part first.
-
Part 4 · SAP® AI live demo: CMR consignment note in 11 minutes
One sentence is enough: a finished consignment note with print program and test data.
-
What belongs in an AI chat and what doesn’t.
-
Part 2 · How Second Key came about
25 years of SAP® and why there are two keys in the lock today.
-
Part 1 · The AI builds. The consultant decides.
How we develop SAP® applications today.
What remains
The AI builds. The consultant decides.
The agent may do a lot, but not everything. It presents a plan, every change is visible, and nothing goes into the system without the consultant's GO.
And next
-
Requirements by voice
Second Key is already listening: requirements by voice instead of keyboard.
-
A phone number
Next, it gets a phone number. If a button is missing in the warehouse, a call is enough.
-
The GO stays with the consultant
No matter where the call comes from: nothing goes into the system without the consultant's GO.
-
A plan before every change
Object by object: what the agent wants to create is clear beforehand.
-
Only GO counts
A small "go" is not enough. Only the consultant's GO opens the system.
-
Stop on deviation
If it deviates from the plan, it stops and asks. Every time.
-
ABAP and RAP
Reports, enhancements, interfaces – and RAP with Fiori/UI5.
-
Dynpros and GUI status
With flow logic, buttons and menus – for SAP® GUI in daily work.
-
Forms
Smart Forms and Adobe Forms, including print program – as in this demo.
-
Own package
Everything is created in its own package, cleanly separated.
-
The customer's release
Checked against the customer's release – not against our development system.
-
Instead of a spec
Everything you would otherwise need a requirements spec, three alignment rounds and a lot of coffee for.
Contact
Unlock your full SAP® potential now
Get to know us – in a first conversation, we identify where the greatest potential in your logistics lies.
Josef Lenz
Managing Director