You ask. It operates your SAP.

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.

AXISChat + Cowork Consult
SAP GUI · liveuser session · read-only

You're in control: consult without touching anything, or execute only what you approve · Zero storage: we use your session

The axis4sap family

Three modes, one assistant.

From quick answers without SAP open to execution with approval. You choose how far the agent goes.

Axis Chat

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
Included in Early Access
Axis Cowork · consult

Cowork Consult

Enters your session and reads the environment live: master data, reports, documents, chains. Read-only; the gate denies writes by construction.

  • Navigates transactions and follows chains
  • Nothing is changed in your SAP
Included in Early Access
Axis Cowork · execution

Cowork Execution

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.

  • Step-by-step approval
  • Stop button always available
Not included in Early Access

Axis Assessment · the report

What an SAP solution architect would write about your environment.

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.

107points analyzed
100%coverage
15findings requiring action
Read-
only
read mode
41 compliant 24 require action 1 highest severity 41 verified, no findings

Every point walked, one by one. Compliance is a result too.

Every circuit was measured, not assumed.

REPORT · Production environment (ECC / S/4HANA) · Modules FI · CO · MM · Basis Illustrative example

Executive verdict

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.

2high risks
1medium risk
0blocking today
4 wksrecommended window

Prioritized risks

A1High severity

Purchase orders without a release strategy applied

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.

A2High severity · audit risk

Accounting periods open longer than necessary

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.

A3Medium severity

Customers under credit management with no limit set

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.

What's healthy

A good report also says what you do not need to touch. These points were checked and are healthy:

  • Bank clearing accounts net to the cent: debit = credit across the 7 accounts of the circuit; the largest moved R$ 4.2 bn on each side.
  • Dual-GAAP parallelism confirmed: BR GAAP in the leading ledger and IFRS in a parallel ledger, with its own measurement verified down to fixed assets.
  • Monthly close on schedule: no out-of-flow period reopening in the half-year.
  • Fixed assets on full New Asset Accounting: reconciliation guaranteed by architecture; subledger × G/L divergence impossible by design.

Where to start

Week 1
Restrict the open periods (A2).

Adjust the OB52 variant to the current period and set a monthly review. Closes the most immediate audit exposure, with low effort.

Weeks 2 to 4
Apply the purchase-order release strategy (A1).

Start with the highest-value bands, aligning the policy's approval limits with the system's control.

Week 4+
Set credit limits (A3).

Register limits by risk class and enable the automatic block above the limit.

Roadmap

Month 1

A2 + first bands of A1: low effort, high return

Period restriction (OB52) and release strategy on the highest-value bands. Immediate control gains.

Month 2

Full A1 + A3: coverage

Release strategy extended to all bands and credit limits by risk class.

Quarter

Continuous governance

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.

Business decision these are meetings, not tickets

A1 · purchasing approval limits: Procurement defines the approval policy. A3 · credit limits: Finance and Sales define the risk ruler. Boardroom decisions, not tickets.

Accounting + functional the close window

A2 · OB52: Accounting defines the posting window; the FI functional adjusts the period variant.

Technical execution straight to backlog

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

Zero storage.

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.

Your SAP GUI sessionactive connection, as your user
axis4sapreads, cross-references and answers on the spot
Session endednothing was stored

Before you start

What you need

Live navigation depends on a native SAP GUI feature. The chat does not.

RequirementChatCowork
SAP GUI installed (Windows)Not requiredRequired
SAP GUI Scripting enabledNot requiredRequired
SAP user with read accessNot requiredRequired
Write permissionNot requiredNot required

Writing (creating purchase orders, cost centers, postings) belongs to Execution mode, which is not part of the Early Access.

Enable SAP GUI Scripting in three steps

1On the serverBasis
TransactionRZ11
Parametersapgui/user_scripting
ValueTRUE

Parameter sapgui/user_scripting (RZ11): enabled by the Basis/infra team; coordinate with them before activating.

2On the clientYour desktop
Opções > Accessibility & Scripting > Scripting
Enable scripting
Notify on connection
Notify on attach

In SAP GUI Options, check "Enable scripting". One click.

3DoneConfirmation
Scripting active
Reopen the SAP GUI session
Cowork now recognizes the connection

Reopen the session and Cowork starts operating. Nothing is installed on the server.

Start free

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.

0questions
0navigations

Questions every skeptic asks

Before you trust, question.

Do you keep my data after the session ends?

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.

Can the agent change something in my SAP by mistake?

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.

Do I need to install anything on the SAP server?

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.

Does the Assessment replace traditional consulting?

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.

Does it work with any SAP GUI version?

Cowork depends on SAP GUI Scripting being enabled. If it is not yet, the Chat keeps working normally, with no dependency on SAP GUI.

What exactly is in the free Early Access?

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.