Skip to main content
Glama

UpdateDataElement

Update an existing ABAP data element by replacing all its properties. Supports domain, predefined, and reference types. Handles locking and activation.

Instructions

Update an existing ABAP data element in SAP system.

Workflow:

  1. Gets domain info (if type_kind is 'domain') to extract dataType/length/decimals

  2. Acquires lock on the data element

  3. Updates data element with provided parameters (complete replacement)

  4. Unlocks data element

  5. Optionally activates data element (default: true)

  6. Returns updated data element details

Supported type_kind values:

  • domain: Based on ABAP domain (requires type_name = domain name)

  • predefinedAbapType: Direct ABAP type (requires data_type, length, decimals)

  • refToPredefinedAbapType: Reference to ABAP type (requires data_type, length, decimals)

  • refToDictionaryType: Reference to another data element (requires type_name = data element name)

  • refToClifType: Reference to class (requires type_name = class name)

Note: All provided parameters completely replace existing values. Field labels are truncated to max lengths (10/20/40/55).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lengthNoLength - for predefinedAbapType or refToPredefinedAbapType
activateNoActivate data element after update (default: true)
decimalsNoDecimals - for predefinedAbapType or refToPredefinedAbapType
data_typeNoData type (CHAR, NUMC, etc.) - for predefinedAbapType or refToPredefinedAbapType
type_kindNoType kind: domain, predefinedAbapType, refToPredefinedAbapType, refToDictionaryType, refToClifTypedomain
type_nameNoType name: domain name, data element name, or class name (depending on type_kind)
descriptionNoNew data element description
search_helpNoSearch help name
package_nameYesPackage name (e.g., ZOK_LOCAL, $TMP for local objects)
field_label_longNoLong field label (max 40 chars)
data_element_nameYesData element name to update (e.g., ZZ_TEST_DTEL_01)
field_label_shortNoShort field label (max 10 chars)
set_get_parameterNoSet/Get parameter ID
transport_requestNoTransport request number (e.g., E19K905635). Required for transportable packages.
field_label_mediumNoMedium field label (max 20 chars)
field_label_headingNoHeading field label (max 55 chars)
search_help_parameterNoSearch help parameter
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: locking/unlocking, activation default (true), complete replacement semantics, and field label truncation. The workflow steps provide transparent insight into operations.

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

Conciseness4/5

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

The description is well-structured with a clear workflow and list of type_kind values. It is somewhat verbose but each sentence serves a purpose. Slight wordiness prevents a 5.

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

Completeness5/5

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

Given the tool's complexity (17 params, conditional logic), the description covers workflow, parameter dependencies, and side effects. No output schema exists, but return value is mentioned. Completeness is high.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by linking type_kind to required parameters and explaining truncation rules, going beyond schema descriptions.

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?

The description clearly states it updates an existing ABAP data element, distinguishing it from create/delete siblings. It enumerates supported type_kind values and provides a workflow, making the purpose unmistakable.

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?

The description explains when to use different type_kind values and notes behavior like complete replacement and transport requirements. However, it does not explicitly contrast with CreateDataElement or other update tools, leaving some ambiguity about alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChinhHN-DEV/abap-mcp-adt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server