Chat
On-call specialist: a question about a transaction, table, customizing or process, answered on the spot, without opening the system.
- Works without SAP GUI Scripting
- Explains path, table and config
First it answers in the chat, like an SAP solution architect. Then it enters your session and navigates live: it opens the transaction, fills in the fields and reads the result in front of you.
You're in control: consult without touching anything, or execute only what you approve · Zero storage: we use your session
The axis4sap family
From quick answers without SAP open to execution with approval. You choose how far the agent goes.
On-call specialist: a question about a transaction, table, customizing or process, answered on the spot, without opening the system.
Enters your session and reads the environment live: master data, reports, documents, chains. Read-only; the gate denies writes by construction.
Acts for real: creates cost centers, posts, creates purchase orders, with step-by-step approval by default, or automatic when you enable it. You set the level of autonomy.
Axis Assessment · the report
Not a panel of blinking lights. A navigable report: verdict, risks with evidence, what you don't need to touch, and where to start.
Run by the axis4sap team, with scope defined together: read-only in your environment, report delivered in days.
Every point walked, one by one. Compliance is a result too.
Every circuit was measured, not assumed.
The environment is operational and stable: it sustains the monthly close with no recurring incidents and the transactional base is solid. What deserves attention is not what is broken, it is what runs with no owner. Three critical settings have been in production since go-live with no review and no formal owner. None is blocking today, but two of them, purchase-order release strategy and open accounting periods, carry fiscal and audit impact potential if they reach the next annual close as they are. The recommendation is to handle items A1 and A2 in the next four weeks and absorb the rest into the quarterly roadmap.
Screen evidence in ME2M / EKKO: 73% of orders with no release strategy applied (144k of 197k). The approval limits exist in policy, not in the system.
Recommendation: enable the release strategy aligned to the policy's approval limits, starting with the highest-value bands. Control becomes enforced by the system, not by trust.
Screen evidence in OB52: period variant open from 2019 to 9999 for all company codes, allowing back-posting in already-closed fiscal years.
Recommendation: restrict the opening to the current period and set a monthly OB52 review routine. It closes the improper-posting window without impacting the month's operation.
Screen evidence in FD32 / KNKK: 62% of partners under credit management with a limit of zero (undefined). The engine exists, the ruler does not.
Recommendation: set limits by risk class and enable the automatic block above the limit. Credit management then actually protects the receivable.
A good report also says what you do not need to touch. These points were checked and are healthy:
Adjust the OB52 variant to the current period and set a monthly review. Closes the most immediate audit exposure, with low effort.
Start with the highest-value bands, aligning the policy's approval limits with the system's control.
Register limits by risk class and enable the automatic block above the limit.
Period restriction (OB52) and release strategy on the highest-value bands. Immediate control gains.
Release strategy extended to all bands and credit limits by risk class.
Assign a formal owner to each critical setting and create a semi-annual review routine, so "no owner" does not happen again.
100% fictional data. The real report reflects the customizing and settings of your own environment.
A1 · purchasing approval limits: Procurement defines the approval policy. A3 · credit limits: Finance and Sales define the risk ruler. Boardroom decisions, not tickets.
A2 · OB52: Accounting defines the posting window; the FI functional adjusts the period variant.
The configuration of all three (release strategy, limits and period variant) are objective functional tasks: straight to the backlog.
The report says whose each action is, before saying what to do.
The #1 argument
It is not a data policy: it is how the product is built. We use your session while you are connected. There is no database where your SAP screens are stored.
Before you start
Live navigation depends on a native SAP GUI feature. The chat does not.
| Requirement | Chat | Cowork |
|---|---|---|
| SAP GUI installed (Windows) | Not required | Required |
| SAP GUI Scripting enabled | Not required | Required |
| SAP user with read access | Not required | Required |
| Write permission | Not required | Not required |
Writing (creating purchase orders, cost centers, postings) belongs to Execution mode, which is not part of the Early Access.
Parameter sapgui/user_scripting (RZ11): enabled by the Basis/infra team; coordinate with them before activating.
In SAP GUI Options, check "Enable scripting". One click.
Reopen the session and Cowork starts operating. Nothing is installed on the server.
Free Early Access: Axis Chat + Axis Cowork in consult mode (read-only). Execution (creating purchase orders, cost centers, postings) is not included. 200 questions + up to 100 navigations.
We got your details. Someone from the team will reach out soon.
Questions every skeptic asks
No. We work on your session while it is active. No screen, table or credential from your environment is stored, replicated or reused; when the session ends, nothing remains on the axis4sap side.
In consult mode, no: it is read-only, with no technical path to write: the gate denies saving. In execution mode (not included in Early Access), only what you approve, step by step; you set the level of autonomy and can stop at any time.
No. Access happens via SAP GUI Scripting on your own desktop, like one more user navigating the screen. Nothing is installed on the server or in the SAP environment.
It does not replace it. It accelerates it. It delivers in days the mapping that usually takes weeks of manual work, so consulting (internal or external) starts from a ready diagnosis, not from scratch. It is run by the axis4sap team, with scope defined together.
Cowork depends on SAP GUI Scripting being enabled. If it is not yet, the Chat keeps working normally, with no dependency on SAP GUI.
Axis Chat and Axis Cowork in consult mode (read-only), with 200 questions and up to 100 navigations. Execution (creating orders, cost centers and postings) is not included in this phase.