skills.rest
sapdev-ai
sapdev-aiOFFICIAL
Explore all skills by this author →
GitHub

sap-sm37

Retrieve SAP SM37 background-job data via RFC and emit diagnostic evidence per job.

7|1|Updated May 11, 2026
Search Tags:#evidence#diagnose#rfc#background-jobs#incident-analysis#sm37#tbtco
One-click install
npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-sm37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-sm37
Source: https://github.com/sapdev-ai/sap-dev/tree/main/plugins/sap-dev-core/skills/sap-sm37
Command: npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-sm37

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reads background-job status from SAP SM37 (TBTCO) over RFC and emits one structured diagnose evidence event per job within a defined window, enabling rapid incident analysis and audit trails for aborted jobs.

Core Features & Use Cases

  • Reads SAP SM37 job data over RFC and emits per-job diagnose evidence events in the specified window.
  • Flags aborted jobs as high-signal events to accelerate incident investigation.
  • Supports anchor-based windows and optional user/job filters for targeted diagnostics.

Quick Start

Run the skill with a configured SAP login profile and a target window to generate diagnostic evidence for background jobs.

Frequently Asked Questions about sap-sm37

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

FAQPage Schema
How do I retrieve SAP SM37 background job data over RFC for incident analysis?▼

To retrieve SAP SM37 background job data over RFC, you can use a tool that reads TBTCO job status and emits structured diagnostic evidence per job within a specified time window. This enables rapid incident analysis for aborted jobs.

Do I need a saved SAP login profile to diagnose SM37 background jobs?▼

Yes, you need a saved SAP login profile and a functioning RFC connection to the target SAP system. These prerequisites allow the diagnostic tool to authenticate and retrieve SM37 job data over the network.

Can I filter SAP SM37 job diagnostics by specific user or job name?▼

Yes, you can filter SAP SM37 job diagnostics by specific user or job name. This allows you to perform targeted diagnostics and emit structured evidence events only for the background jobs matching your criteria within the window.

What is the best way to flag aborted SAP background jobs for audit trails?▼

The best way to flag aborted SAP background jobs for audit trails is to read SM37 job status over RFC and emit high-signal diagnostic evidence events. This flags aborted jobs specifically to accelerate incident investigation.

How does anchor-based windowing work for SAP SM37 job diagnostics?▼

Anchor-based windowing for SAP SM37 job diagnostics works by defining a specific time range around an anchor point. The tool reads background job data within this window and emits one structured diagnose evidence event per job.

Related Skills

Explore More Software Engineering Skills→
sapdev-aisapdev-ai
7

sap-slg1

Read SAP SLG1 application-log headers over RFC to surface ABORT, ERROR, and WARNING entries.

Official
Intermediate
fsollafsolla

observability-and-instrumentation

Instrument application code with structured logging, RED/USE metrics, and distributed tracing.

Community
Advanced
sapdev-aisapdev-ai
7

sap-diagnose

Consolidate evidence from read-only SAP readers and rank root-cause hypotheses.

Official
Advanced
sapdev-aisapdev-ai
7

sap-transport-request

Resolve or create modifiable SAP transport requests via GUI or RFC/BDC paths.

Official
Advanced