sap-se21

Create, check, or delete SAP development packages via SE21 GUI scripting.

7|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-se21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-se21
Source: https://github.com/sapdev-ai/sap-dev/tree/main/plugins/sap-dev-core/skills/sap-se21
Command: npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-se21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation, verification, and removal of SAP development packages in SE21 by driving the live SAP GUI session, reducing manual GUI steps and risks.

Core Features & Use Cases

  • RFC pre-check for package existence using RFC_READ_TABLE on TDEVC to avoid unnecessary GUI steps
  • GUI-driven creation that assigns a Transport Request via /sap-transport-request
  • Safe deletion path with explicit user confirmation and TADIR integrity checks

Quick Start

Create SAP SE21 packages through GUI scripting in an active SAP session.

Frequently Asked Questions about sap-se21

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the limitations of automating SE21 package management through GUI scripting?

Limitations include requiring an active SAP GUI session with scripting enabled and pre-configured credentials. The automation is bound by SE21 GUI constraints and requires explicit user confirmation for deletions to ensure TADIR integrity.

How do I automate creating SAP development packages in SE21?

Automate SAP development package creation by driving the SE21 GUI scripting interface within an active SAP GUI session. The Skill validates package existence via RFC_READ_TABLE on TDEVC, then drives SE21 to create the package and delegates Transport Request resolution automatically.

Do I need SAP GUI scripting enabled to manage transport requests for packages?

Yes, SAP GUI scripting enabled is required to manage packages and transport requests. The Skill operates within an active SAP GUI session, using scripting to drive SE21 and assigning Transport Requests via the delegated transport request component.

How does the Skill check if an SAP package already exists before using SE21?

The Skill performs an RFC pre-check for package existence by calling RFC_READ_TABLE on the TDEVC table. This validates whether the SAP development package exists before driving SE21 GUI scripting, avoiding unnecessary GUI steps.

Can I safely delete SAP development packages using SE21 GUI scripting?

Yes, you can safely delete SAP development packages using SE21 GUI scripting. The deletion path requires explicit user confirmation and includes TADIR integrity checks to ensure safe removal with comprehensive error reporting.

What are the limitations of automating SE21 package management through GUI scripting?

Limitations include requiring an active SAP GUI session with scripting enabled and pre-configured credentials. The automation is bound by SE21 GUI constraints and requires explicit user confirmation for deletions to ensure TADIR integrity.