SAP stays.
The workplace gets rebuilt.
New interfaces for people, secure access for agents. We build lean web and mobile interfaces for exactly the SAP processes a role needs, with AI agents built in. Permissions and approvals stay in SAP.
- S/4HANA and ECC
- Permissions stay in SAP
- You own the code
Strong as a system. Painful as a workplace.
In many companies, people outside the SAP core team work with SAP every day: on the shop floor, in service, in the business units. For them, every transaction is a hurdle.
for one order, of which the role needs a handful. The rest gets guessed, copied or asked of purchasing.
Once submitted, the request disappears. Follow-ups happen by email and phone.
Two colleagues know how it's done right. When they're out, the process stalls.
SAP GUI and Fiori are built for clicks. AI agents need controlled access, and there is none.
Four developments coming together.
Clean core
SAP itself recommends building extensions next to the core via released APIs instead of inside the system. That is exactly how we work.
ECC maintenance ends 2027
Many face the S/4HANA question. A dedicated interface decouples users from the migration and moves along when the system behind it changes.
Interfaces got cheap
With AI-assisted development, a tailored interface costs a fraction of what it used to. Standard software is no longer automatically the economical choice.
Agents need access
The big AI vendors are building new workspaces for company data. For SAP to be part of that, it needs a secure bridge with logging and approvals.
An interface for people. An entry point for agents.
We build every SAP function once, in a connection layer. Your employees' interface and the AI agents use the same function, with the same permissions.
- Only the fields and steps a role needs
- Suggestions from previous transactions
- Status instead of guesswork, on mobile too
- Plain-language messages instead of SAP error codes
- One sentence becomes a pre-filled transaction
- Summaries and anomalies for approvers
- Voice agent with live answers from SAP
- Every action logged, critical ones only with approval
Where it pays off first.
Three typical processes in mid-sized companies. Which one comes first for you, we decide together in the check.
From request to approval
- today
- Purchase requisition with many fields, account assignment, material numbers. Afterwards, nobody knows where the approval is stuck.
- new
- A form with only the role's fields, suggestions from past orders, approval status, mobile approval.
- agent
- "200 pieces like last month" becomes a pre-filled requisition. Approvers get a summary and anomalies.
- rule
- The agent prepares, nothing is created until you say yes.
- measured
- Time per order, follow-up questions, approval lead time
Report a breakdown
- today
- A phone call or a note, someone enters the notification later. Information gets lost on the way.
- new
- Mobile app: machine via QR code, photo, short description, notification status and machine history.
- agent
- A voice message becomes a structured notification with damage pattern and priority, plus a hint at similar past breakdowns.
- rule
- Normal priority is created directly, "very high" only after a technician approves.
- measured
- Time from breakdown to notification, completeness
Voice agent with SAP knowledge
- today
- For "Where is my delivery?" someone searches order and delivery while the customer waits on the line.
- new
- A voice agent answers status requests around the clock, live from SAP. Complex cases go to your team with a summary.
- agent
- Reads orders, deliveries and open items. Hands over to a human when needed.
- rule
- Read only, everything logged. Changes later only with approval.
- measured
- Share of calls answered automatically, waiting time
Thinking further: "Show me purchasing volume per supplier last quarter" as an answer or a live dashboard. The same layer makes it possible.
Built next to SAP, not into it.
A dedicated connection layer with two entry points. SAP remains the leading system, unchanged.
OData throughout
The layer only talks to released interfaces. For ECC, the required functions are exposed as OData services.
Sign-in as usual
Single sign-on via your identity provider, usually Microsoft Entra ID. The user identity is passed through to SAP. No shared technical user.
No copy of your data
We store no SAP business data, only logs. Runs on your premises or in an EU cloud, on SAP BTP if you prefer.
Two approvals, clearly separated.
Business rules: who may do what up to which amount. Stays unchanged in SAP and applies to people and agents alike.
In front of it, for agents only: may the agent trigger this action, or does a human need to approve? Every call is logged with a timestamp.
More about tokyn.trail →- Agents never access SAP directly, always through tokyn.trail.
- SAP checks every individual user's permissions, as it does today.
- Write actions are protected against double execution.
- Development and testing run against your test or QA system, never production.
No new system. No per-seat license.
| Custom Fiori development | Low-code platform | tokyn studio | |
|---|---|---|---|
| License cost per user | none | ongoing | none |
| Agents built in | no | partly | from day one |
| Logging and approvals for agents | no | no | tokyn.trail |
| You own the code | yes | no | yes |
| Development inside SAP | yes | partly | no, next to it |
Start small. Decide freely after each stage.
SAP workplace check
We map one process with your users and measure clicks, time and sources of error. In parallel we check interfaces and licensing.
Clickable prototype, go/no-go recommendation, binding fixed-price offer for the pilot
Pilot
One use case goes live with one user group: connection layer, single sign-on, interface. Optionally a first agent with tokyn.trail.
Live process, metrics before and after
Expansion
More processes and roles on the same layer. Each additional process gets cheaper because the foundation is in place.
More roles and business areas
Operations
Monitoring, automated tests after SAP updates, adjustments and tokyn.trail in production.
Stable processes, even after updates
For everything inside SAP we work with an experienced SAP partner: interfaces, authorizations, basis and licensing advice. You get both from one source.
Which SAP process annoys you most?
Tell us about your process in a free intro call. Afterwards you'll know whether a check is worth it.