sap-stms

Move released SAP transport requests across DEV, QAS, and PRD landscapes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Moves released SAP transport requests across the DEV → QAS → PRD landscape and reports their import status.

Core Features & Use Cases

  • Read-Only Status: Inspect the target system queue to locate TRs and their route position.
  • Logs & Verification: Read import logs and map RC codes to verdicts to confirm success or failure.
  • Gated Import & Import-All: Perform controlled, gated imports for individual TRs or whole queues with strict production safeguards.

Quick Start

Import a released TR into a target SID with proper gating using sap-stms, e.g., sap-stms import <TR> --to <SID>.

Frequently Asked Questions about sap-stms

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

FAQPage Schema
How do I automate SAP transport request imports across DEV, QAS, and PRD systems?

You can automate SAP transport request imports by moving released TRs across the DEV → QAS → PRD landscape with gated imports and RFC-based validations, then reporting their import status.

Can I check SAP transport queue status without triggering an actual import?

Yes, you can perform read-only status checks to inspect a target system queue, locate specific transport requests, and view their route position without triggering an import.

What is the best way to enforce production gating during SAP transport imports?

The best way to enforce production gating is by using controlled, gated imports for individual transport requests or whole queues with strict production safeguards and release readiness validations.

Do I need SAP GUI scripting to move transport requests across system landscapes?

Yes, moving transport requests across system landscapes relies on SAP GUI scripting and RFC-based validations to execute imports and enforce release readiness checks.

Why are my SAP transport queue-wide imports failing in the target system?

Queue-wide imports may fail due to release readiness checks or production gating violations; inspect the import logs and map the RC codes to verdicts to identify the specific failure cause.