io.github.fr0ster/mcp-abap-adt

NPM · @MCP-ABAP-ADT/CORE · SCANNED AUG 3

MCP server for SAP ABAP ADT: repository analysis and CRUD for RAP and classic ABAP

Available components

+22 this week 67 67 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security89

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (206 of 207), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (206 of 207), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 9 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability65

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 22728 tokens (~110/item across 205 items; 205 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage97

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
92% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mcp-abap-adt/core

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add fr0ster-mcp-abap-adt -- npx -y @mcp-abap-adt/core

# add to Codex CLI

codex mcp add fr0ster-mcp-abap-adt -- npx -y @mcp-abap-adt/core

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr0ster-mcp-abap-adt": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mcp-abap-adt/core"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add fr0ster-mcp-abap-adt --command npx --arg -y --arg @mcp-abap-adt/core

# ~/.hermes/config.yaml

mcp_servers:
  fr0ster-mcp-abap-adt:
    command: "npx"
    args: ["-y", "@mcp-abap-adt/core"]

// mcp.json

{
  "mcpServers": {
    "fr0ster-mcp-abap-adt": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/core"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +61
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 −14
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
31 Jul 26 +14
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −61
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
29 Jul 26 +41
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
28 Jul 26 −19
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
27 Jul 26 45

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@mcp-abap-adt/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 206 packages

206 packages in the resolved dependency tree · 191 deprecated · 63 stale · 1 without a linked repository.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 205 exposed · ~22,728 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

ActivateBehaviorDefinition ~103

Activate a RAP behavior definition. Use after CreateBehaviorDefinition or UpdateBehaviorDefinition if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Behavior definition name (root entity, e.g., ZI_MY_ENTITY).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateClass ~97

Activate an ABAP class. Use after CreateClass or UpdateClass if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
class_name	string	yes	Class name (e.g., ZCL_MY_CLASS).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateDataElement ~103

Activate an ABAP data element. Use after CreateDataElement or UpdateDataElement if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
data_element_name	string	yes	Data element name (e.g., ZDT_MY_ELEMENT).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateDdl ~101

Activate a CDS view. Use after CreateDdl or UpdateDdl if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
ddl_name	string	yes	DDL source name (e.g., ZVW_MY_VIEW).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateDomain ~97

Activate an ABAP domain. Use after CreateDomain or UpdateDomain if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
domain_name	string	yes	Domain name (e.g., ZDM_MY_DOMAIN).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateFunctionGroup ~103

Activate an ABAP function group. Use after CreateFunctionGroup or UpdateFunctionGroup if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
function_group_name	string	yes	Function group name (e.g., Z_FG_TEST).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateFunctionModule ~119

Activate an ABAP function module. Use after UpdateFunctionModule if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
function_group_name	string	yes	Function group name (e.g., Z_FG_TEST).
function_module_name	string	yes	Function module name (e.g., Z_FM_TEST).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateInterface ~97

Activate an ABAP interface. Use after CreateInterface or UpdateInterface if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
interface_name	string	yes	Interface name (e.g., ZIF_MY_INTERFACE).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateMetadataExtension ~100

Activate a CDS metadata extension. Use after CreateMetadataExtension or UpdateMetadataExtension if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Metadata extension name (e.g., ZC_MY_EXTENSION).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateObjects ~93

Activate one or multiple ABAP repository objects. Use after Create/Update when objects remain inactive, or for group activation of related objects (e.g., domains + data elements + tables together). Works with any object type.

Input Output Examples

Name	Type	Req	Description
objects	array	yes	Array of objects to activate. Each object must have 'name' and 'type'.
preaudit	boolean	—	Request pre-audit before activation. Default: true

No output schema declared.

No examples provided.

ActivateServiceBinding ~101

Activate an ABAP service binding. Use after CreateServiceBinding or UpdateServiceBinding if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Service binding name (e.g., ZSB_MY_SERVICE).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateServiceDefinition ~101

Activate an ABAP service definition. Use after CreateServiceDefinition or UpdateServiceDefinition if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Service definition name (e.g., ZSD_MY_SERVICE).
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

No output schema declared.

No examples provided.

ActivateStructure ~97

Activate an ABAP structure. Use after CreateStructure or UpdateStructure if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.
structure_name	string	yes	Structure name (e.g., ZST_MY_STRUCTURE).

No output schema declared.

No examples provided.

ActivateTable ~97

Activate an ABAP table. Use after CreateTable or UpdateTable if the object remains inactive.

Input Output Examples

Name	Type	Req	Description
session_id	string	—	Session ID from GetSession. If not provided, a new session will be created.
session_state	object	—	Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.
table_name	string	yes	Table name (e.g., ZTB_MY_TABLE).

No output schema declared.

No examples provided.

CheckBehaviorDefinition ~50

Perform syntax check on an ABAP behavior definition (BDEF). Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
name	string	yes	BehaviorDefinition name (e.g., ZI_MY_BDEF).

No output schema declared.

No examples provided.

CheckClass ~124

Perform syntax check on an ABAP class. Can check existing class (active/inactive) or validate hypothetical source code. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
class_name	string	yes	Class name (e.g., ZCL_MY_CLASS).
source_code	string	—	Optional: source code to validate. If provided, validates hypothetical code without creating object. Must include complete CLASS DEFINITION and IMPLEMENTATION sections.
version	string	—	Version to check: 'active' (last activated) or 'inactive' (current unsaved). Default: active.

No output schema declared.

No examples provided.

CheckDataElement ~48

Perform syntax check on an ABAP data element. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
data_element_name	string	yes	Data element name (e.g., ZDE_MY_ELEMENT).

No output schema declared.

No examples provided.

CheckDdl ~112

Perform syntax check on an ABAP CDS view. Can check existing view (active/inactive) or validate hypothetical DDL source. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
ddl_name	string	yes	CDS view name to check, passed as ddl_name (e.g., ZI_MY_VIEW).
ddl_source	string	—	Optional: DDL source code to validate instead of the saved version.
version	string	—	Version to check: 'active' or 'inactive'. Default: inactive.

No output schema declared.

No examples provided.

CheckDomain ~44

Perform syntax check on an ABAP domain. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
domain_name	string	yes	Domain name (e.g., ZDM_MY_DOMAIN).

No output schema declared.

No examples provided.

CheckFunctionGroup ~50

Perform syntax check on an ABAP function group. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
function_group_name	string	yes	Function group name (e.g., ZFGRP_MY_GROUP).

No output schema declared.

No examples provided.

CheckFunctionModule ~84

Perform syntax check on an ABAP function module. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
function_group_name	string	yes	Function group name containing the function module.
function_module_name	string	yes	Function module name (e.g., Z_MY_FUNCTION).
version	string	—	Version to check: 'active' or 'inactive'. Default: active.

No output schema declared.

No examples provided.

CheckInterface ~44

Perform syntax check on an ABAP interface. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
interface_name	string	yes	Interface name (e.g., ZIF_MY_INTERFACE).

No output schema declared.

No examples provided.

CheckMetadataExtension ~51

Perform syntax check on an ABAP metadata extension (DDLX). Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Metadata extension name (e.g., ZC_MY_DDLX).

No output schema declared.

No examples provided.

CheckPackage ~57

Perform syntax check on an ABAP package. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
package_name	string	yes	Package name (e.g., ZMY_PACKAGE).
super_package	string	yes	Super package name (parent package).

No output schema declared.

No examples provided.

CheckStructure ~102

Perform syntax check on an ABAP structure. Can check existing structure (active/inactive) or validate hypothetical DDL code. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
ddl_code	string	—	Optional: DDL source code to validate instead of the saved version.
structure_name	string	yes	Structure name (e.g., ZST_MY_STRUCTURE).
version	string	—	Version to check: 'active' or 'inactive'. Default: inactive.

No output schema declared.

No examples provided.

CheckTable ~106

Perform syntax check on an ABAP table. Can check existing table (active/inactive) or validate hypothetical DDL code. Returns syntax errors, warnings, and messages.

Input Output Examples

Name	Type	Req	Description
ddl_code	string	—	Optional: DDL source code to validate instead of the saved version.
table_name	string	yes	Table name (e.g., ZMCP_MY_TABLE).
version	string	—	Version to check: 'active', 'inactive', or 'new'. Default: new.

No output schema declared.

No examples provided.

CreateBehaviorDefinition ~190

Operation: Create. Subject: BehaviorDefinition. Will be useful for creating behavior definition. Create a new ABAP Behavior Definition (BDEF) in SAP system. Creates the behavior definition object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate after creation. Default: true
description	string	—	Description
implementation_type	string	yes	Implementation type: 'Managed', 'Unmanaged', 'Abstract', 'Projection'
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
name	string	yes	Behavior Definition name (usually same as Root Entity name)
package_name	string	yes	Package name
root_entity	string	yes	Root Entity name (CDS View name)
transport_request	string	—	Transport request number

No output schema declared.

No examples provided.

CreateBehaviorImplementation ~168

Create a new ABAP behavior implementation class for a behavior definition. Creates the object in initial state. Use UpdateBehaviorImplementation to set implementation code afterwards.

Input Output Examples

Name	Type	Req	Description
behavior_definition	string	yes	Behavior Definition name (e.g., ZI_MY_ENTITY). The behavior definition must exist.
class_name	string	yes	Behavior Implementation class name (e.g., ZBP_MY_ENTITY). Must follow SAP naming conventions (typically starts with ZBP_ for behavior implementations).
description	string	—	Class description. If not provided, class_name will be used.
package_name	string	yes	Package name (e.g., ZOK_LOCAL, $TMP for local objects)
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateCdsUnitTest ~123

Create a CDS unit test class with CDS validation. Creates the test class in initial state.

Input Output Examples

Name	Type	Req	Description
cds_view_name	string	yes	CDS view name to validate for unit test doubles.
class_name	string	yes	Global test class name (e.g., ZCL_CDS_TEST).
description	string	—	Optional description for the global test class.
package_name	string	yes	Package name (e.g., ZOK_TEST_PKG_01, $TMP).
transport_request	string	—	Transport request number (required for transportable packages).

No output schema declared.

No examples provided.

CreateClass ~209

Operation: Create. Subject: Class. Will be useful for creating class. Create a new ABAP class in SAP system. Creates the class object in initial state.

Input Output Examples

Name	Type	Req	Description
abstract	boolean	—	Mark class as abstract. Default: false
class_name	string	yes	Class name (e.g., ZCL_TEST_CLASS_001).
create_protected	boolean	—	Protected constructor. Default: false
description	string	—	Class description (defaults to class_name).
final	boolean	—	Mark class as final. Default: false
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LAB, $TMP).
superclass	string	—	Optional superclass name.
transport_request	string	—	Transport request number (required for transportable packages).

No output schema declared.

No examples provided.

CreateDataElement ~493

Operation: Create. Subject: DataElement. Will be useful for creating data element. Create a new ABAP data element in SAP system. Creates the data element object in initial state.

Input Output Examples

Name	Type	Req	Description
data_element_name	string	yes	Data element name (e.g., ZZ_E_TEST_001). Must follow SAP naming conventions.
data_type	string	—	Data type (e.g., CHAR, NUMC) or domain name when type_kind is 'domain'.
decimals	number	—	Decimal places. Usually inherited from domain.
description	string	—	Data element description. If not provided, data_element_name will be used.
heading_label	string	—	Heading field label (max 55 chars). Applied during update step after creation.
length	number	—	Data type length. Usually inherited from domain.
long_label	string	—	Long field label (max 40 chars). Applied during update step after creation.
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
medium_label	string	—	Medium field label (max 20 chars). Applied during update step after creation.
package_name	string	yes	Package name (e.g., ZOK_LOCAL, $TMP for local objects)
search_help	string	—	Search help name. Applied during update step after creation.
search_help_parameter	string	—	Search help parameter. Applied during update step after creation.
set_get_parameter	string	—	Set/Get parameter ID. Applied during update step after creation.
short_label	string	—	Short field label (max 10 chars). Applied during update step after creation.
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.
type_kind	string	—	Type kind: 'domain' (default), 'predefinedAbapType', 'refToPredefinedAbapType', 'refToDictionaryType', 'refToClifType'. If not specified, defaults to 'domain'.
type_name	string	—	Type name: domain name (when type_kind is 'domain'), data element name (when type_kind is 'refToDictionaryType'), or class name (when type_kind is 'refToClifType')

No output schema declared.

No examples provided.

CreateDdl ~186

Operation: Create. Subject: DDL source. Will be useful for creating a DDL source. Create a new CDS View or Classic View in SAP system. Creates the DDL source object in initial state. Use UpdateDdl to set DDL source code.

Input Output Examples

Name	Type	Req	Description
ddl_name	string	yes	DDL source name (e.g., ZOK_R_TEST_0002, Z_I_MY_VIEW).
description	string	—	Optional description (defaults to ddl_name).
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LAB, $TMP for local objects)
transport_request	string	—	Transport request number (required for transportable packages).

No output schema declared.

No examples provided.

CreateDomain ~374

Operation: Create. Subject: Domain. Will be useful for creating domain. Create a new ABAP domain in SAP system. Creates the domain object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	(optional) Activate domain after creation (default: true)
conversion_exit	string	—	(optional) Conversion exit routine name (without CONVERSION_EXIT_ prefix)
datatype	string	—	(optional) Data type: CHAR, NUMC, DATS, TIMS, DEC, INT1, INT2, INT4, INT8, CURR, QUAN, etc.
decimals	number	—	(optional) Decimal places (for DEC, CURR, QUAN types)
description	string	—	(optional) Domain description. If not provided, domain_name will be used.
domain_name	string	yes	Domain name (e.g., ZZ_TEST_0001). Must follow SAP naming conventions.
fixed_values	array	—	(optional) Array of fixed values for domain value range
length	number	—	(optional) Field length (max depends on datatype)
lowercase	boolean	—	(optional) Allow lowercase input
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	—	(optional) Package name (e.g., ZOK_LOCAL, $TMP for local objects)
sign_exists	boolean	—	(optional) Field has sign (+/-)
transport_request	string	—	(optional) Transport request number (e.g., E19K905635). Required for transportable packages.
value_table	string	—	(optional) Value table name for foreign key relationship

No output schema declared.

No examples provided.

CreateFunctionGroup ~212

Create a new ABAP function group in SAP system. Function groups serve as containers for function modules. Uses stateful session for proper lock management.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate function group after creation. Default: true. Set to false for batch operations.
description	string	—	Function group description. If not provided, function_group_name will be used.
function_group_name	string	yes	Function group name (e.g., ZTEST_FG_001). Must follow SAP naming conventions (start with Z or Y, max 26 chars).
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LAB, $TMP for local objects)
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateFunctionInclude ~130

Operation: Create. Subject: FunctionInclude. Will be useful for creating function group include. Create a new ABAP include within an existing function group. Creates the include in initial state.

Input Output Examples

Name	Type	Req	Description
description	string	—	Optional description for the include
function_group_name	string	yes	Parent function group name (e.g., ZTEST_FG_001)
include_name	string	yes	Include name (e.g., LZTEST_FG_001F01).
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateFunctionModule ~147

Operation: Create. Subject: FunctionModule. Will be useful for creating function module. Create a new ABAP function module within an existing function group. Creates the function module in initial state.

Input Output Examples

Name	Type	Req	Description
description	string	—	Optional description for the function module
function_group_name	string	yes	Parent function group name (e.g., ZTEST_FG_001)
function_module_name	string	yes	Function module name (e.g., Z_TEST_FUNCTION_001). Must follow SAP naming conventions (start with Z or Y, max 30 chars).
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateInterface ~183

Operation: Create. Subject: Interface. Will be useful for creating interface. Create a new ABAP interface in SAP system. Creates the interface object in initial state.

Input Output Examples

Name	Type	Req	Description
description	string	—	Interface description. If not provided, interface_name will be used.
interface_name	string	yes	Interface name (e.g., ZIF_TEST_INTERFACE_001). Must follow SAP naming conventions (start with Z or Y).
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LAB, $TMP for local objects)
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateMessageClass ~188

Operation: Create. Subject: Message Class (MSAG). Create a new ABAP message class (T100) shell. Individual messages are added afterwards with CreateMessageClassMessage. Message classes are not activated.

Input Output Examples

Name	Type	Req	Description
description	string	—	(optional) Short description. If not provided, message_class_name is used.
master_language	string	—	(optional) Master/original language (e.g. "EN", "DE"). Defaults to the session language (SAP_LANGUAGE) or EN.
message_class_name	string	yes	Message class name (e.g., ZMY_MSGS). Must follow SAP naming conventions.
package_name	string	yes	Package name (e.g., ZMY_PKG, $TMP for local objects).
transport_request	string	—	(optional) Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateMessageClassMessage ~184

Operation: Create. Subject: a single message inside a Message Class (MSAG). Add a message (number + text) to an existing ABAP message class (T100). The parent class must exist first (CreateMessageClass).

Input Output Examples

Name	Type	Req	Description
description	string	—	(optional) Long description for the message.
message_class_name	string	yes	Parent message class name (e.g., ZMY_MSGS).
msgno	string	yes	Message number (e.g., "001").
msgtext	string	yes	Message text. May contain placeholders &1 &2 &3 &4 (or &).
self_explanatory	boolean	—	(optional) Mark the message as self-explanatory (no long text needed). Default: false.
transport_request	string	—	(optional) Transport request number. Required for transportable objects.

No output schema declared.

No examples provided.

CreateMetadataExtension ~144

Operation: Create. Subject: MetadataExtension. Will be useful for creating metadata extension. Create a new ABAP Metadata Extension (DDLX) in SAP system. Creates the metadata extension object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate after creation. Default: true
description	string	—	Description
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
name	string	yes	Metadata Extension name
package_name	string	yes	Package name
transport_request	string	—	Transport request number

No output schema declared.

No examples provided.

CreatePackage ~296

Create a new ABAP package in SAP system. Packages are containers for development objects and are essential for organizing code.

Input Output Examples

Name	Type	Req	Description
application_component	string	—	Application component (optional, e.g., BC-ABA)
description	string	—	Package description. If not provided, package_name will be used.
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_TEST_0002). Must follow SAP naming conventions (start with Z or Y for customer namespace).
package_type	string	—	Package type: 'development' (default) or 'structure'
record_changes	boolean	—	Enable change recording for the package. Required for transportable packages. Default: false.
software_component	string	—	Software component (e.g., HOME, ZLOCAL). If not provided, SAP will set a default (typically ZLOCAL for local packages).
super_package	string	yes	Parent package name (e.g., ZOK_PACKAGE). Required for structure packages.
transport_layer	string	—	Transport layer (e.g., ZE19). Required for transportable packages.
transport_request	string	—	Transport request number (e.g., E19K905635). Required if package is transportable.

No output schema declared.

No examples provided.

CreateServiceBinding ~285

Operation: Create. Subject: ServiceBinding. Will be useful for creating service binding. Create a new ABAP service binding in SAP system. Creates the service binding object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate service binding after create. Default: true.
binding_variant	string	—	Service binding variant. ODATA_V4_UI = OData V4 for Fiori Elements, ODATA_V4_WEB_API = OData V4 Web API, ODATA_V2_UI = OData V2 for Fiori Elements, ODATA_V2_WEB_API = OData V2 Web API.
description	string	—	Optional description. Defaults to service_binding_name when omitted.
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	ABAP package name.
response_format	string	—	—
service_binding_name	string	yes	Service binding name.
service_definition_name	string	yes	Referenced service definition name.
service_name	string	—	Published service name. Default: service_binding_name if omitted.
service_version	string	—	Published service version. Default: 0001.
transport_request	string	—	Optional transport request for transport checks.

No output schema declared.

No examples provided.

CreateServiceDefinition ~230

Operation: Create. Subject: ServiceDefinition. Will be useful for creating service definition. Create a new ABAP service definition in SAP system. Creates the service definition object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate service definition after creation. Default: true.
description	string	—	Service definition description. If not provided, service_definition_name will be used.
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LOCAL, $TMP for local objects)
service_definition_name	string	yes	Service definition name (e.g., ZSD_MY_SERVICE). Must follow SAP naming conventions (start with Z or Y).
source_code	string	—	Service definition source code (optional). If not provided, a minimal template will be created.
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateStructure ~226

Operation: Create. Subject: Structure. Will be useful for creating structure. Create a new ABAP structure in SAP system. Creates the structure object in initial state.

Input Output Examples

Name	Type	Req	Description
activate	boolean	—	Activate structure after creation. Default: true. Set to false for batch operations (activate multiple objects later).
description	string	—	Structure description. If not provided, structure_name will be used.
fields	array	yes	Array of structure fields
includes	array	—	Include other structures in this structure
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LOCAL, $TMP for local objects)
structure_name	string	yes	Structure name (e.g., ZZ_S_TEST_001). Must follow SAP naming conventions.
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateTable ~169

Operation: Create. Subject: Table. Will be useful for creating table. Create a new ABAP table in SAP system. Creates the table object in initial state.

Input Output Examples

Name	Type	Req	Description
description	string	—	Table description for validation and creation.
master_language	string	—	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
package_name	string	yes	Package name (e.g., ZOK_LOCAL, $TMP for local objects)
table_name	string	yes	Table name (e.g., ZZ_TEST_TABLE_001). Must follow SAP naming conventions.
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable packages.

No output schema declared.

No examples provided.

CreateTransport ~112

Create a new ABAP transport request in SAP system for development objects.

Input Output Examples

Name	Type	Req	Description
description	string	yes	Transport request description (mandatory)
owner	string	—	Transport owner (optional, defaults to current user)
target_system	string	—	Target system for transport (optional, e.g., 'PRD', 'QAS'). If not provided or empty, uses 'LOCAL'
transport_type	string	—	Transport type: 'workbench' (cross-client) or 'customizing' (client-specific)

No output schema declared.

No examples provided.

CreateUnitTest ~96

Start an ABAP Unit test run for provided class test definitions. Returns run_id for status/result queries.

Input Output Examples

Name	Type	Req	Description
context	string	—	Optional context string shown in SAP tools.
duration	object	—	—
risk_level	object	—	—
scope	object	—	—
tests	array	yes	List of container/test class pairs to execute.
title	string	—	Optional title for the ABAP Unit run.

No output schema declared.

No examples provided.

DeleteBehaviorDefinition ~91

Delete an ABAP behavior definition from the SAP system. Includes deletion check before actual deletion. Transport request optional for $TMP objects.

Input Output Examples

Name	Type	Req	Description
behavior_definition_name	string	yes	BehaviorDefinition name (e.g., Z_MY_BEHAVIORDEFINITION).
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable objects. Optional for local objects ($TMP).

No output schema declared.

No examples provided.

DeleteBehaviorImplementation ~92

Delete an ABAP behavior implementation from the SAP system. Includes deletion check before actual deletion. Transport request optional for $TMP objects.

Input Output Examples

Name	Type	Req	Description
behavior_implementation_name	string	yes	BehaviorImplementation name (e.g., Z_MY_BEHAVIORIMPLEMENTATION).
transport_request	string	—	Transport request number (e.g., E19K905635). Required for transportable objects. Optional for local objects ($TMP).

No output schema declared.

No examples provided.

DeleteCdsUnitTest ~59

Delete a CDS unit test class (global class).

Input Output Examples

Name	Type	Req	Description
class_name	string	yes	Global test class name (e.g., ZCL_CDS_TEST).
transport_request	string	—	Transport request number (required for transportable packages).

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug