ABAPilot lets business and technical teams ask questions, investigate the details, understand custom code and prepare reports, using context from their own SAP ECC or on-premise S/4HANA system.
For the people working with SAP data and the people maintaining the system behind it.
Ask, investigate, get the report.
Explore purchasing, finance and sales questions. Follow the evidence to documents and items, then take the result into your next decision.
Understand, troubleshoot, build with context.
Connect code, dictionary definitions and operational evidence to help developers, consultants and support teams investigate and deliver.
Start with a question in your own words, then follow the answer to the documents, data or code behind it.
You ask
How much did we pay this supplier this year?
Then
Compare it with last year. Which invoices explain the difference?
Illustrative prompts, not live results. Available answers depend on the connected SAP system, enabled tools and your permissions. Access reviews identify potential issues for validation; they do not certify segregation of duties.
The connector carries no business logic. Every operation runs inside your SAP system, under the rules you set there.
On your network
Inside your SAP system
/ABAPILOT/CONFIG lists the live endpoints. Remove one and that tool stops working, with no client change.S_TABU_DIS and S_DEVELOP are enforced, not reimplemented./ABAPILOT/AUDIT records the user, timestamp and parameters.The result then returns to your AI client, so it may reach the model provider you chose. Review that data path for your deployment, including masking, exports, storage and retention.
In three minutes, Claude and ABAPilot update ABAP code in a sandbox copy of an existing report, run 14 unit tests in SAP, and revise the technical specification and test scenarios.
A recorded sandbox demonstration with AI-generated narration and waiting intervals edited out. The original report stays unchanged, and manual and integration checks that were not run are documented separately.
A focused SAP workspace with conversations, tool activity and downloadable results together.
Bring supported SAP workflows into Microsoft Teams through a configured Copilot Studio agent.
Connect compatible AI assistants and development environments to supported SAP tools. Read the setup guide
Start with a named-user pilot, an agreed tool scope and evidence of permitted and denied requests. Expand with controls validated for your SAP landscape.
The Community Trial lets you read authorised custom objects, inspect table metadata and capped samples, diagnose SAP errors and syntax-check proposed ABAP. You also complete a controlled apply, test and reset workflow in an isolated report.
Install the Z objects with abapGit and the connector from npm, then request 30-day portal access.
Install the connector
npx -y abapilotThis does not install the SAP backend, which is licensed separately.
We ran first-party checks on four SAP connections on 9 September 2026, across SAP_BASIS 700, 750, 757 and 758. They covered metadata and source reads plus syntax probes, not full workflows or every release.
ABAPilot by Crimson Consulting connects business and technical teams to SAP context through its app, a configured Teams integration or compatible MCP clients, backed by a licensed ABAP backend. What it can do in your system depends on the deployed tools and user permissions.
No. The connector runs outside SAP and connects over HTTPS to its own ABAP backend exposed through SICF. Backend installation, permissions and network access are still required.
SAP ECC and on-premise S/4HANA. Confirm the exact release, backend version and required operations before installation. Managed private cloud needs a separate provider check, and the backend is not offered for S/4HANA Public Cloud or ABAP Cloud.
No. The connector is MIT-licensed, and the SAP backend is a separate commercial product. Agree backend licensing, installation, and client or model costs before a trial.
Not by itself. Tool results may reach the AI client or model provider. Review the complete data path, storage and provider configuration.
No. The connector catalog includes validated and low-level write operations. Restrict enabled endpoints and verify their validation, permissions and logging on the deployed backend.
No, they cover different landscapes. Read the comparison to see which fits your release.
Contact us with your SAP release, the systems and developers you want to include, your preferred AI client and one workflow to evaluate. Please don't send passwords, tokens or confidential source code.
What works on ECC today, what to govern and how to evaluate safely.
Define the behaviour, review the diff, run SAP checks and hand over the documentation.
How the connection path works, and what you still need to agree with your SAP team.
Bring a purchasing question, an unfamiliar program or a support investigation. In 30 minutes, in English or Spanish, we define the outcome and prerequisites for a measured pilot.