abap-config-mcp

Activate ABAP Object

abap_activate

Idempotent

Activates a saved ABAP object by compiling it and making it executable, releasing any prior write lock automatically before activation.

Instructions

Activate an ABAP object — compiles it and makes it executable (equivalent to F8/Activate in the ABAP workbench). If the object is currently locked by a prior write_abap_object_source or set_text_elements call, the lock is released automatically before activation. The object must have been written/saved first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "abap_activate"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	ADT URL of the ABAP object to activate (e.g. /sap/bc/adt/programs/programs/Z_MY_PROG)
`preaudit`	No	Run pre-activation ATC checks before activating. Default: false
`connectionId`	No	SAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.16.0Nov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, idempotent, non-destructive, open-world. The description adds genuinely new behavior: an object locked by a prior write_abap_object_source or set_text_elements call has that lock released automatically before activation. It does not say what happens on compile errors or whether the release occurs if activation fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its meaning, then side effects, then the prerequisite. No filler or restated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation-style tool with no output schema, the description covers the prerequisite and the lock side effect, which is what an agent most needs to call it safely. It omits the result of a failed compile, which an agent would want to know when deciding whether to follow up with check_inactive_objects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so url, preaudit and connectionId are already documented in the schema. The description adds only the ordering constraint that the object must be saved first, not any new detail about preaudit's ATC semantics or the connectionId choice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb and resource ('Activate an ABAP object') plus a plain-language gloss ('compiles it and makes it executable') and a workbench analogy (F8/Activate). The mention of write_abap_object_source and set_text_elements as the operations that precede it separates activation from authoring.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States a hard prerequisite ('The object must have been written/saved first') and implies the workflow position after a write. It stops short of naming the batch sibling abap_activate_multiple or saying when to prefer it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server