sap-transport-debug

sap-transport-debug is a command for Claude Code from BoxLogoDev/sapstack. It costs 37 tokens per session (1,430 once invoked), scanned A, original, MIT.

A command guide for diagnosing failed SAP STMS transports. STMS is SAP's system for moving development changes between systems; the guide covers transport status, logs, return codes, and common dependency problems.

In plain words
What is it for?
Use it to inspect transport logs, interpret return codes, investigate Dictionary activation failures, Korean short-text issues, cross-client dependencies, and missing transport objects.
Why use it?
It turns a failed import into a structured investigation and helps distinguish warnings from errors that require intervention.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to inspect transport logs, interpret return codes, investigate Dictionary activation failures, Korean short-text issues, cross-client dependencies, and missing transport objects.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/boxlogodev/sapstack/sap-transport-debug
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/BoxLogoDev/sapstack

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sap-transport-debug

README.md
[![agentmods](https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-transport-debug/github.svg)](https://agentmods.dev/commands/boxlogodev/sapstack/sap-transport-debug)
Your own site
<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-transport-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-transport-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sap-transport-debug

Your own site · 80×15
<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-transport-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-transport-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.01430
Opus 5.5 $0.00015 $0.00572
Sonnet 5.5 $0.00007 $0.00286
Haiku 4.5 $0.00004 $0.00143

Measured 1mo ago against content hash 074f18729c05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sap-transport-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/sap-transport-debug.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

STMS Transport 디버그 파이프라인

입력: $ARGUMENTS

🎯 목표

Transport Request(TR) import 실패 시 체계적으로 원인을 추적하고 수정합니다. 한국 현장에서 흔한 한글 Short Text 이슈부터 cross-client 의존성까지 커버합니다.

🔒 안전 규칙

  • 운영 환경(PRD)으로 강제 push 금지
  • tp force 옵션은 최후의 수단
  • 의존 객체 미포함 시 추가 TR 생성 권장

Step 1. TR 상태 확인

  1. STMS → Import Queue → 대상 시스템 선택
  2. 대상 TR 찾기 → 상태 확인:
    • 대기 (queued)
    • 진행 중 (in progress)
    • 실패 (error)
  3. SE09/SE10: Transport Organizer에서 TR 상세
  4. Return Code (RC):
    • 0~4: OK/Warning (무시 가능)
    • 6: Warning (검토 권장)
    • 8: Error (원인 분석 필수)
    • 12: Critical (시스템 점검)
    • 16+: Severe (수동 개입)

Step 2. tp 로그 분석

위치: /usr/sap/trans/log/

파일 내용
ALOG<YY>.<SID> 전체 액션 로그
ULOG<YY>.<SID> 사용자 작업
SLOG<YY>.<SID> Short log (헤더)
<STEP>_<TR>.log Step별 상세

주요 Step 로그

  • DICT_<TR>.log: DDIC Dictionary 활성화
  • DIEX_<TR>.log: Data Dictionary Export
  • GEN_<TR>.log: 프로그램 생성
  • DARG_<TR>.log: Distribute ABAP Runtime Globals

명령어 (OS 레벨, BC 권한 필요)

cd /usr/sap/trans/log
ls -lt | head   # 최신 로그
grep -i error <logfile>

Step 3. Import 에러 유형별 진단

Error Type A: DDIC 활성화 실패

  • Dictionary 객체 (Table/Structure/Data Element) 의존성 문제
  • SE11: 해당 객체 활성화 시도
  • 의존 객체가 다른 TR에 있으면 순서 조정

Error Type B: Program Generation 실패

  • ABAP 소스 오류
  • SE80: 객체 열어서 구문 확인
  • SLIN: Extended program check

Error Type C: 한글 Short Text 변환 실패 (한국 현장 빈번)

  • 증상: CONVERSION_ERROR 또는 CODEPAGE_CONVERT
  • 원인:
    • Non-Unicode → Unicode 전환 미완료
    • tp 버전 mismatch
    • NLS_LANG 미설정 (Oracle)
  • 해결:
    • SAP Note 2452523 확인
    • tp kernel upgrade
    • NLS_LANG=KOREAN_KOREA.AL32UTF8 설정

Error Type D: Cross-client 의존성

  • 100번 client에서 개발 → 200번 client에 import 시 실패
  • Customizing TR이 Workbench TR과 분리
  • SCC1: Client-specific copy

Error Type E: Object Lock (다른 TR 소유)

  • 같은 객체가 다른 TR에 잠김
  • SE03 → Object Directory Entry
  • Owner TR release 후 재import

Step 4. 복구 옵션

4-1. Re-import (동일 TR)

  • STMS → Queue → Request 선택 → Import Again
  • 오류가 해소되었을 경우

Read the full file on GitHub · 174 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 174 lines · 37 tokens per session scan A 074f18729c05

Subscribe to this mod's changes

sap-transport-debug is a command published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 1,430 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.