Understand and improve your custom ABAP from your IDE.
ABAPilot by Crimson Consulting connects AI coding assistants to SAP ECC and on-premise S/4HANA through MCP. Use SAP context to explain, review and document existing ABAP, and support code generation from the IDE you already use.
Start with a live ABAP workflow demo. We agree the system prerequisites, available tools and scope before a customer trial.
Start with the ABAP your team maintains
Understanding unfamiliar custom code takes more than a plausible explanation. Start with the source and dictionary objects in your SAP system, then review the assistant’s findings against that evidence.
Learn table names (EKKO, BSIK, LFA1…)
Know which fields to join
Wait 3 days for IT to run a report
Export to Excel and VLOOKUP everything
Watch an end-to-end ABAP change
See Claude and ABAPilot update ABAP code, run 14 unit tests in SAP, and revise the technical specification and test scenarios in a three-minute IDE walkthrough.
Watch on YouTube with chapters · English narration and on-screen captions.
From request to reviewed change
- Define the change. Give Claude the request and a reusable lifecycle skill with mock documentation templates.
- Implement and validate. Enhance a sandbox copy of an existing ABAP report, validate against live SAP, and run 14 passing ABAP Unit tests.
- Update the documentation. Revise the technical specification and test scenarios, then review the code and document changes together.
The original report remains unchanged. Manual and integration checks that were not run are documented separately. This is a recorded sandbox demonstration with AI-generated narration and waiting intervals edited out.
Watch the earlier SAP ECC developer demo
A recorded sandbox workflow is a starting point for evaluation. Confirm the release, enabled operations and review steps for your own environment.
SAP context in your existing development workflow
ABAPilot connects a compatible MCP client to source code, dictionary definitions and supported operations in SAP ECC and on-premise S/4HANA. The connector runs outside SAP and communicates over HTTPS with a licensed ABAP backend exposed through SICF.
No ADT or Eclipse is required. Your SAP team still needs to agree release compatibility, backend installation, permissions and network access.
Architecture and prerequisites · Client setup guide
Verified on four existing SAP connections: our checks on 9 September 2026 covered metadata and dispatcher-source reads plus valid and invalid syntax probes across SAP_BASIS 700, 750, 757 and 758. See exact component versions, results and coverage limits. These first-party checks cover the listed operations, not full workflow or all-release compatibility.
Why ABAPilot
A connection path without ADT
Connect through a licensed ABAP backend and SICF HTTPS service. Agree compatibility and installation requirements with your SAP team.
Source and dictionary context
Retrieve existing code and dictionary definitions to support explanations, documentation and reviews.
Built around custom ABAP
Evaluate workflows on SAP ECC and on-premise S/4HANA using a program your team already maintains.
Your compatible AI client
Use a supported MCP client and choose its model configuration. Review the data returned to the client and provider.
Public MCP connector
The local stdio connector runs outside SAP and forwards supported requests to the licensed backend over HTTPS.
Clear licensing boundaries
The public connector is MIT-licensed. The SAP backend is a separate commercial product; agree client, model and deployment costs.
Questions to bring to your first demo
- Explain this existing program and identify the source objects used.
- Which dictionary definitions should we check before changing it?
- Draft documentation that a developer can verify.
- Review this proposed change and suggest checks.
A separate use case: business-data questions
This recording illustrates the in-system query interface. Discuss data scope, enabled operations and verification separately from a developer trial.
A demonstrated query workflow does not establish compatibility or authorization behavior for every deployment.
From explanation to a reviewed change
Use system context to support the work your developers already do. The assistant proposes explanations and changes; your team reviews the evidence and runs the checks supported by the deployed backend.
AI-assisted code review
Ask for a first-pass review with source references. Have a developer assess findings and run the agreed checks.
Documentation drafts
Generate explanations and documentation from retrieved source and dictionary context, then verify them against the system.
Your development process
Use repository instructions, review steps and tests supported by your client and backend. Instructions guide the assistant; they do not guarantee compliance.
Code proposals and validation
Draft a change with clear acceptance criteria. Review it and run syntax checks and tests before approving the result.
For developers: the open-source MCP connector
Inspect the public connector and its tool catalog. Installation also requires a licensed SAP backend, an agreed endpoint and a compatible MCP client. Verify enabled tools and SAP permissions before a trial.
Live session against the published npm package. The connector is MIT-licensed and inspectable on GitHub before you ever point it at a system.
Compare the workflow and prerequisites
SAP’s ADT MCP tools and ABAPilot use different connection paths. Compare them against the same task, backend release, enabled operations and total cost. SAP’s MCP tooling and licensed Joule capabilities have distinct requirements.
Agree the controls before a trial
SAP identity and permissions
Agree the identity and enabled operations. Verify allowed and denied requests on the installed backend before broadening access.
Log attribution
Confirm which requests are logged, which identity is recorded and how your team will review the deployed logs.
Enabled operations
Agree the endpoints available to the trial. Test the deployed restrictions rather than inferring them from a client setting.
Writes and data handling
The catalog includes read and write tools. Check validation for each enabled operation and review the full client/model data path.
Explore the public connector on GitHub, hear the founder explain the architecture in podcasts and technical articles, or watch the ECC workflow. These materials describe the product and demonstrated examples; they are not independent customer productivity studies.
Frequently Asked Questions
What is ABAPilot?
ABAPilot by Crimson Consulting connects AI coding clients to SAP context through a public MCP connector and a separate licensed ABAP backend. It supports explanation, review, documentation and available development operations.
Does ABAPilot require ADT or Eclipse?
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.
Which SAP systems can I evaluate it for?
ABAPilot targets 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.
Is the npm connector the complete product?
No. The connector is MIT-licensed; the SAP backend is a separate commercial product. Agree backend licensing, installation and client or model costs before a trial.
Does a local connector keep all SAP data local?
Not by itself. Tool results may reach the AI client or model provider. Review the complete data path, storage and provider configuration.
Is every write automatically validated?
No. The connector catalog includes validated and low-level write operations. Restrict enabled endpoints and verify their validation behavior, permissions and logging on the deployed backend.
Bring one ABAP workflow to a demo
Choose an existing program your team needs to understand, review or document. In a 30-minute demo, we discuss the workflow and prerequisites for a trial.