Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_create_dtp

Create and activate a Data Transfer Process (DTP) for an existing transformation in SAP BW/4HANA. Supports optional field filtering and multi-step transformation chains.

Instructions

Create a new DTP (Data Transfer Process) for an existing Transformation and activate it. The DTP name is server-generated. Optionally set a filter on one source field (Equal operator). After creation the DTP is activated automatically. IMPORTANT: Before calling this tool, always check the full transformation chain. Single-step chain (e.g. ADSO->ADSO): use trfn_name only. Two-step chain (e.g. ADSO->TRCS->ADSO): use trfn_name for the first transformation and trfn_name_2 for the second; source_name/source_type = the start object, target_name/target_type = the end object. Omitting trfn_name_2 in a two-step chain causes a persistent HTTP 500 error. Use bw_get_transformation or bw_xref to determine the chain before creating the DTP. DataSource source: set source_type "RSDS" and pass source_system (the DataSource source system). source_name is then the plain DataSource name; the tool builds the RSDS compound source key internally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNoDevelopment package (default "$TMP").
trfn_nameYesTechnical name of the existing Transformation (UUID-like key).
descriptionNoOptional DTP description text (default: empty).
source_nameYesSource object name (e.g. "SOURCE_NAME").
source_typeYesSource object type (e.g. "ADSO", "TRCS", "RSDS"). Use "RSDS" for a DataSource source — source_system is then required.
target_nameYesTarget object name (e.g. "TARGET_NAME").
target_typeYesTarget object type (e.g. "ADSO"). Use "IOBJ" to load into an InfoObject; the loaded sub-object (attributes / texts / hierarchies) is selected with target_object_subtype.
trfn_name_2NoOptional second transformation in a multi-step chain. Include when the DTP spans two transformations (e.g. ADSO→TRCS→ADSO).
filter_fieldNoField name to filter on. Requires filter_dta_name and filter_value.
filter_valueNoFilter value for the Equal selection (e.g. "PL_001").
source_systemNoSource system name of the DataSource. Required when source_type is "RSDS".
filter_dta_nameNoInternal dtaName for the filter field.
target_object_subtypeNoInfoObject sub-object to load into. Only applies when target_type is "IOBJ". ATTR (default) = attributes/master data (IOBJA), TEXT = texts (IOBJT), HIER = hierarchies (IOBJH). Must match the sub-object the transformation chain targets.
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses key behaviors: server-generated name, automatic activation, filter restrictions (Equal operator only, one field), two-step chain logic, and IOBJ sub-object handling. It omits authorization requirements or whether it overwrites existing DTPs, but the level of detail is high.

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 long but well-structured, starting with the core action, then detailing parameters and special cases, and ending with important warnings. Every sentence adds value, though a more bulleted format could improve scannability.

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 (13 parameters, no output schema), the description is thorough. It covers prerequisites, parameter interdependencies, special cases (two-step chain, RSDS, IOBJ), and an explicit error warning. No essential information is missing.

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

Parameters5/5

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

Schema description coverage is 100%, yet the description adds substantial meaning beyond the schema: explains auto-generation of DTP name, the Equal-only filter constraint, the two-step chain parameter interplay, and the RSDS compound key construction. This provides vital context for correct parameter usage.

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 creates and activates a DTP for a transformation, specifying the resource and action. It differentiates from siblings like bw_get_dtp, bw_run_dtp, and bw_update_dtp by detailing creation-specific constraints and prerequisites.

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

Usage Guidelines5/5

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

The description provides explicit guidance: check transformation chain before use, distinguish single-step vs two-step, warn about omitting trfn_name_2 causing errors, and recommend using bw_get_transformation or bw_xref. It also covers DataSource source with RSDS and the need for source_system. This is comprehensive and actionable.

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/dnic-dev/bw-modeling-mcp'

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