agentmods.dev

sap-payment-run-debug

A guided troubleshooting process for failed F110 payment runs in SAP, where F110 creates scheduled payments to vendors.

In plain words
What is it for?
Use it to investigate missing invoices, blocked payments, incorrect vendor bank details, payment-method settings, house-bank configuration, and DME file errors.
Why use it?
It checks the payment process in stages, from vendor records and payment rules through bank selection and electronic bank-file creation, helping isolate where the failure occurs.

Command

18 2d ago A scan 55 tokens original MIT
View the source file BoxLogoDev/sapstack
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-payment-run-debug
Clone the repo
git clone --depth 1 https://github.com/BoxLogoDev/sapstack
Per session 55 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,109 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.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.01109
Opus 5 $0.00028 $0.00554
Sonnet 5 $0.00011 $0.00222
Haiku 4.5 $0.00006 $0.00111

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

Security

Grade A, and why

sap-payment-run-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-payment-run-debug.md · 115 lines

How it starts

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

F110 Payment Run 디버그

입력: $ARGUMENTS

🎯 목표

F110 지급실행 실패 시 파라미터부터 DME 생성까지 단계별 원인 탐색.

진단 순서

Step 1. Run 상태 확인

  1. F110 → Status 탭: Proposal / Payment / Printout 단계별 상태
  2. S_P99_41000099: Payment Run 로그
  3. 체크:
    • Proposal 미실행?
    • Proposal 실행했으나 "No items selected"?
    • Payment 단계에서 DME 생성 실패?

Step 2. 벤더 마스터 확인

  • XK03 / BP (S/4): 벤더 조회
  • LFB1.ZWELS: 지급방법 (payment method) 등록 여부
  • LFB1.ZAHLS: 지급 블록 해제 상태
  • LFBK: 은행 정보 (IBAN, 계좌번호, Swift)
  • 체크:
    • 한국 국내 계좌는 IBAN 대신 은행코드+계좌번호
    • 국세청 세금계산서용 사업자등록번호 (STCD1)

Step 3. Open Items 선택 조건

  • FBL1N: 벤더 Open Items
  • 체크:
    • Due date가 Run date 이내인가?
    • Payment block 없는가?
    • Special GL indicator가 선택에서 제외됐는지?
    • Document 분할 설정 — 일부만 지급 대상일 수 있음

Step 4. 지급방법 & House Bank

  • FBZP: 전체 Payment 설정
    • Paying company codes: 지급 회사코드 설정
    • Payment methods in country: 국가(KR) 내 지급방법 (C=수표, T=이체)
    • Payment methods in company code: 회사코드별 활성화
    • Bank determination:
      • Ranking order
      • Amounts (한도)
      • Accounts (하우스뱅크 + Account ID)
      • Available amounts
      • Value date

Step 5. House Bank / Bank Account

  • FI12 (ECC) / NWBC → Bank Account Management (S/4):
    • House bank ID
    • Account ID
    • Bank key (한국 은행 코드 — 국민/신한/우리/하나 등)
  • 체크:
    • Bank account balance 적정한가 (FF.5 — Bank Statement)
    • Outgoing payments 계정 매핑

Step 6. Payment Medium (DME)

  • DMEE: DME Engine Tree
  • 한국 특화:
    • KEB 국민은행 전용 포맷 커스텀 사례 다수
    • 은행별 XML/Flat file 구조 다름
    • 환경은행 ACH (자동이체) 연동 시 별도 Tree
  • 체크:
    • Payment method에 DMEE format 할당됐는지
    • OBPM1/OBPM4 — Payment Medium Format 설정

Step 7. 환율 / 통화

  • OBA1: 환율 유형
  • 체크:
    • KRW 외 통화 지급 시 환율 적용일
    • FF_5 / F.05 환율 변환 검증

Step 8. 한국 특화

  • 원천세 (Withholding Tax):
    • 벤더 마스터에 WT type 등록 (LFBW)
    • 지급 시 자동 원천 분개 확인
  • 전자세금계산서 역방향: 벤더 매입 송장이 e-Tax Invoice 기반이면 승인번호 검증
  • K-IFRS: 지급 관련 분개가 IFRS 공시 대상인지

Step 9. 감사 흔적

  • F110 → Additional logs: 상세 로그
  • SM21: 시스템 로그
  • K-SOX: 지급실행자 ≠ 승인자 로그

Read the full file on GitHub · 115 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. 2d ago First seen · 115 lines · 55 tokens per session scan A 7f0996cc5e3f

Subscribe to this mod's changes

sap-payment-run-debug is a command published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,109 once invoked, about $0.0003 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.

Data and AIDebuggingResearchabapai-agentsclaude-codedeveloper-toolserpllm-skills
Related

Other commands, from other repositories

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

eval-improve

Work the eval-loop corpus — rank failure clusters, fix the top actionable defect, validate against held-out, open a PR.

dynamics365ninja/d365fo-mcp-server · 25 tokens

eval-run

Run an eval case end-to-end on the VM (implement → build → score → record → roll back). VM/full-mode only.

dynamics365ninja/d365fo-mcp-server · 27 tokens

research-l2

Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…

Gixsy95/abap_wiki · 111 tokens

ingest-l0

L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.

Gixsy95/abap_wiki · 59 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