What is sap-cpi-iflow-debug?

A command for diagnosing SAP CPI iFlows, which are cloud-based workflows that move and transform messages between systems. It checks message arrival, data mapping, memory use, certificates, connections, and retry status.

Debugging sender adapters, schemas, type conversions, Groovy scripts, large payloads, BTP certificates, Cloud Connector links, receiver endpoints, and message reprocessing.

It gives a structured way to narrow down why a workflow is not processing messages, fails during mapping, runs out of memory, or cannot connect. It also identifies when failed messages can be retried or need manual action.

sap-cpi-iflow-debug — Command by BoxLogoDev

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.

agentmods

npx agentmods add commands/boxlogodev/sapstack/sap-cpi-iflow-debug

Clone the repo

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

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 614 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00035	$0.00614
Opus 5	$0.00017	$0.00307
Sonnet 5	$0.00007	$0.00123
Haiku 4.5	$0.00003	$0.00061

Measured 2d ago against content hash 2ab53524b86e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sap-cpi-iflow-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 2d 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-cpi-iflow-debug.md · 88 lines

What it actually says

/sap-cpi-iflow-debug — CPI iFlow 종합 디버그

사용 시점

iFlow가 메시지를 처리 안 함
매핑 오류로 fail
메모리 초과
인증서 만료 알림
메시지 재처리 필요

진단 단계

Step 1: Sender Adapter

Adapter type 정확 (REST·SFTP·OData 등)
Polling 스케줄 활성
인증 (OAuth·Basic·Cert) 유효
Allowed endpoint URL

Step 2: 메시지 도착

Monitor → Messages → 최근 N건
다음 분류:
- Completed (성공)
- Retry (재시도 중)
- Failed (영구 실패)
- Escalated (수동 개입 필요)

Step 3: 매핑 검증

Mapping step에서 실패 시:
- Source schema 비교 — 모든 필드 존재?
- Target schema 필수 필드 채움?
- Type conversion (String → Integer, Date)
- Groovy script syntax 에러?

Step 4: 메모리·성능

단일 메시지 크기 (예: 10MB+ 시 위험)
Splitter 추가 권장
Streaming 모드 활성화

Step 5: 인증서·연결

BTP Keystore에서 인증서 만료일 확인
Cloud Connector GREEN
Receiver endpoint reachable

Step 6: 재처리

실패 메시지 선택 → Retry 또는 Edit Payload 후 Reprocess
대량 재처리: Manage Messages → Filter → Bulk action

흔한 패턴

증상	원인
메시지 안 도착	Sender adapter / Polling / Auth
매핑 fail	Schema mismatch / Required field
Memory exceeded	Large payload / No splitting
Cert expired	BTP Keystore 갱신 안 함
Receiver fail	Cloud Connector / Endpoint

Output

### iFlow 정보
- iFlow: [name]
- Tenant: [region]
- 실패 메시지 ID: [...]

### 진단 결과
- Stage: [Sender/Mapping/Receiver]
- Root Cause: ...
- Sample error: ...

### 해결책
1. ...
2. ...

### Prevention
- 모니터링 알림 설정
- 인증서 갱신 30일 전 알림

참조

plugins/sap-integration-cloud/skills/sap-integration-cloud/SKILL.md
agents/sap-integration-cloud-consultant.md

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.

2d ago First seen · 88 lines · 35 tokens per session scan A 2ab53524b86e

Subscribe to this mod's changes

sap-cpi-iflow-debug is a command published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 614 once invoked, about $0.0002 per session on Opus 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.

Backend and APIs Debugging abap ai-agents claude-code developer-tools erp llm-skills

eval-author

Draft a new eval case (eval/cases/ .json) + scaffold its golden folder, goldenpending until captured on the VM.

dynamics365ninja/d365fo-mcp-server · 28 tokens

ingest-l1

L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…

Gixsy95/abap_wiki · 86 tokens

sap-cpi-iflow-debug