ABAPilot Community Trial

SAP ECC & on-premise S/4HANA · 30-day assisted MCP evaluation

See the ABAPilot Community Trial workflow in 34 seconds.

Test an AI-assisted ABAP workflow on your own SAP sandbox

Evaluate ABAPilot without an SAP BTP or ADT dependency for this connection path. Inspect authorised custom code, investigate a known SAP error, and complete a controlled change, syntax-check, activation, test and reset loop in one isolated laboratory report.

Your SAP system, SAP credentials and business programs remain under your control. Crimson provides the individual Portal trial entitlement.

Request an assisted 30-day trial

Installation guide and Z objects on GitHub · MCP connector on npm

What the trial is designed to prove

The Community Trial answers three buying questions with evidence from your own sandbox:

  1. Can your network, SAP identity and security model support ABAPilot?
  2. Can an MCP assistant understand authorised custom ABAP and investigate a real SAP error?
  3. Can it complete a small, controlled change and test loop inside an isolated Z report?

What you can evaluate

  • Connectivity: confirm the connected SAP system, client and user.
  • Repository context: read authorised Z/Y reports, includes, classes, function modules and function groups.
  • DDIC context: inspect Z/Y table and structure metadata.
  • Bounded custom data: query capped Z/Y table samples with projected fields and one validated filter.
  • Error investigation: resolve pasted or screenshot-transcribed text through T100 and find candidate calls in authorised custom code.
  • Change planning: analyse bounded active source without modifying SAP.
  • In-memory validation: syntax-check candidate ABAP without saving it.
  • Isolated change loop: apply, activate, test and reset a change only in ZABP_TRIAL_LAB.

The public connector exposes 13 MCP tools. Customer repository objects and business data remain read-only. The laboratory can save, activate and execute only the fixed, resettable ZABP_TRIAL_LAB report.

Recommended 60–90 minute evaluation

  1. Run sap_ping to prove the identity and network path.
  2. Read one representative Z class or function group with sap_read_object.
  3. Diagnose an error your developer already understands with sap_diagnose_error and compare the result with the known answer.
  4. Inspect ZABP_TRIAL_LAB, propose a small rule change, syntax-check it, apply it and run the fixed functional tests.
  5. Reset the laboratory and verify its baseline.
  6. If the workflow is useful, scope a paid-product PoC around one real sandbox change with the broader ATC, ABAP Unit, activation, documentation and transport capabilities.

Watch the Community Trial walkthrough

A short introduction to the trial, with an example prompt and a result from a sandbox test. English narration and captions.

Watch the walkthrough on YouTube

How to get started

  1. Request Portal trial access. Send your SAP release, preferred MCP client and the workflow you want to evaluate. Do not send passwords or licence keys.
  2. Install in your own sandbox. Import the Z objects with abapGit and configure the dedicated trial HTTP service.
  3. Configure the published connector. Use Node.js and a client that supports local stdio MCP servers.
  4. Connect with your own SAP identity. The Portal key controls trial entitlement; your SAP user still controls SAP access.
  5. Run the scorecard. Use a representative custom object, a known error and the isolated laboratory.
npx -y -p @abapilot/community-trial@latest abapilot-trial-configure

Before you install

You need an SAP ECC or on-premise S/4HANA development or sandbox system, an administrator able to import and activate the Z objects and HTTP service, appropriate SAP authorisations, and outbound HTTPS access to the ABAPilot Portal. The connector requires HTTPS for the SAP endpoint by default because it sends SAP Basic credentials on each call. An isolated private sandbox without HTTPS requires the explicit ABAPILOT_ALLOW_INSECURE_HTTP=true opt-in and must never be exposed over the public internet or a shared network. Your administrator may also need to configure certificate trust.

Frequently asked questions

Do I connect to Crimson’s SAP system?

No. You install the trial in your own SAP system and use your own SAP user. Crimson provides the individual Portal trial account.

Do I need BTP or ADT?

No. This connection path uses its dedicated SAP HTTP service. BTP and ADT are not prerequisites.

Is the trial read-only?

Customer repository objects and business data are read-only. Persistent changes are permitted only in the resettable ZABP_TRIAL_LAB report. The laboratory blocks business-data writes, transactions, files, dynamic execution, external calls and all DO/WHILE loops.

What happens after 30 days?

When the Portal entitlement expires or is revoked, trial operations are denied. The trial does not automatically delete customer-owned SAP objects; your administrator controls removal.

Is the source available?

Yes. The Community Trial repository and MCP connector are public so your team can inspect the implementation and boundaries before installation.

Does this replace a full product PoC?

No. The Community Trial proves connectivity, controls, developer adoption and a bounded interaction model. A commercial PoC evaluates one real customer change with the broader ABAPilot toolset.

Bring one known ABAP workflow

Tell us the SAP release, preferred MCP client, one representative custom object and one known error. We will help define a focused first test and document the outcome.

Request trial access

Continue evaluating ABAPilot

Compare the deployment and governance options on the SAP ABAP MCP Server comparison, or review the complete ABAPilot platform for end-to-end development, functional support and controlled SAP operations.