Connect your SAP to the AI you already use.
ABAPilot connects business and technical teams to their SAP landscape. Ask business questions, investigate the details, understand custom code and prepare reports with context from your own system.
Use the ABAPilot app, Microsoft Teams through Copilot Studio, or a compatible MCP client. Start with a real workflow and agree the SAP system, user permissions, enabled tools and data handling for your deployment.
Built by an SAP PartnerEdge partner
Crimson Consulting participates in the SAP PartnerEdge program, Build engagement model. ABAPilot supports governed AI-assisted workflows for SAP ECC, SAP CRM and SAP S/4HANA environments.
One SAP connection. Useful across your teams.
For the people working with SAP data and the people maintaining the system behind it.
For business teams
Ask. Investigate. Get the report.
Explore purchasing, finance and sales questions. Follow the evidence to documents and items, then take the retrieved result into your next decision.
For SAP teams
Understand. Troubleshoot. Build with context.
Connect code, dictionary definitions and operational evidence to help developers, consultants and support teams investigate and deliver.
What would you ask SAP?
Start with a question in your own words. Follow the answer to the documents, data or code behind it.
Finance & accounting
“How much did we pay this supplier this year?”
Then ask
“Compare it with last year. Which invoices explain the difference?”
Purchasing
“Which purchase orders are still awaiting delivery?”
Then ask
“Show the outstanding items by supplier and export the results as CSV.”
Sales
“Which customer orders are still open?”
Then ask
“Explain what “open” means here, then break the results down by month.”
SAP operations
“Why did this job fail last night?”
Then ask
“Read the job log, check the related dump and show the relevant source code.”
ABAP development
“What does this custom class do?”
Then ask
“Which objects depend on it? Draft documentation and suggest tests for a change.”
Access & audit review
“Which roles grant supplier maintenance and payment release?”
Then ask
“Show the authorization definitions and flag potential conflicts for review.”
Ask → Follow up → Verify the source → Take the result with you.
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.
Follow the question all the way to the data.
Start with a business name or question. Discover relevant SAP records, investigate exceptions and produce an output your team can use.
Purchasing investigations
Find suppliers by name, confirm ambiguous matches and explore purchase orders with their items.
Finance and sales analysis
Agree the question, business definitions and authorized sources for your pilot.
Reports you can take away
CSV, spreadsheets and charts grounded in the retrieved dataset, with explicit coverage and completeness.
Evidence for review
Document references, a defined scope and visibility into missing information. Audit findings still require appropriate business review.
Example: from a supplier name to a usable report
“Find the latest POs from this supplier. Include the items and give me a CSV.”
- Resolve the supplier and confirm ambiguous or misspelled matches.
- Retrieve the authorized headers and items for the agreed scope.
- Export the captured dataset and state its completeness and limits.
This is an illustrative workflow, not a customer result or a live SAP query.
Work with the system. Understand its context.
Give compatible AI tools access to the source, metadata and supported operations your team needs for a real investigation.
Understand custom development
Read source, explore dependencies and prepare documentation.
Investigate operational problems
Bring available dumps, jobs and logs into the troubleshooting conversation.
Prepare and validate changes
Review proposals, run supported SAP checks and document the result.
Fit your delivery process
Use your team’s review, approval and transport process for enabled actions.
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.
Your workspace. Your SAP context.
Choose the ABAPilot app or a supported integration. Available capabilities and identity setup are agreed for each deployment.
ABAPilot app
A focused SAP workspace with conversations, tool activity and downloadable results together.
Teams & Copilot
Bring supported SAP workflows into Microsoft Teams through a configured Copilot Studio agent.
MCP & developer tools
Connect compatible AI assistants and development environments to supported SAP tools.
Define access. Verify the boundaries.
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.
SAP identity and authorization
Validate user mapping and SAP-side checks for the sources and operations you enable.
Available tools and actions
Apply capability policies alongside SAP permissions. Verify validation, approval controls and log attribution for enabled actions.
The full data path
Review what reaches the client and chosen AI provider, including masking, exports, storage and retention.
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.
Try ABAPilot on your own SAP sandbox
The Community Trial lets an evaluator read authorised custom objects, inspect table metadata and capped samples, diagnose SAP errors, syntax-check proposed ABAP and complete a controlled apply, test and reset workflow in the isolated ZABP_TRIAL_LAB report. Install the Z objects with abapGit and the MCP connector from npm, then request 30-day Portal access.
Use your own SAP system and credentials. See the trial guide for prerequisites and limits.
Questions to bring to your first demo
- Find a supplier and investigate recent purchase orders with their items.
- 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.
Frequently Asked Questions
What is ABAPilot?
ABAPilot by Crimson Consulting connects business and technical teams to SAP context through its app, configured Teams integration or compatible MCP clients, backed by a licensed ABAP backend. It supports business investigation, reporting, code understanding and available development operations, subject to the deployed tools and user permissions.
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 workflow. See what changes.
Bring a purchasing question, an unfamiliar program or a support investigation. In a 30-minute demo, we define the outcome and prerequisites for a measured pilot.