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

sap-sm13

Read VBHDR and join VBERROR over VBKEY to surface SM13 update-task failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill identifies and surfaces SM13 update-task failures by reading VBHDR and correlating them with VBERROR to provide actionable diagnostics.

Core Features & Use Cases

  • Reads VBHDR within a specified date window and retrieves corresponding VBERROR entries to surface failure details.
  • Emits a unified evidence event per update, highlighting failed ones (severity E) for quick triage.
  • Works standalone or as part of the sap-diagnose workflow to improve MTTR for SAP update incidents.

Quick Start

Provide a saved SAP profile via /sap-login and run the skill to generate diagnostic evidence for SM13 update failures.

Frequently Asked Questions about sap-sm13

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

FAQPage Schema
How do I diagnose SM13 update-task failures in SAP?▼

Diagnosing SM13 update-task failures involves reading VBHDR and correlating it with VBERROR via RFC to surface failure details. This process highlights failed updates with severity E for quick triage and analysis.

What is the best way to surface failed SAP updates for analysis?▼

Surfacing failed SAP updates is best achieved by emitting a unified evidence event per update, correlating VBHDR with VBERROR. This highlights severity E failures, providing actionable diagnostics to improve MTTR for SAP update incidents.

Do I need SAP NCo 3.1 and PowerShell to read VBHDR and VBERROR?▼

Yes, reading VBHDR and VBERROR requires SAP NCo 3.1 and a Windows PowerShell environment. Additionally, you must configure a saved SAP profile via /sap-login to enable the RFC connection.

Can I use this SM13 diagnostic tool as part of a broader SAP workflow?▼

Yes, this SM13 diagnostic tool operates standalone or integrates with the sap-diagnose workflow. It emits evidence events for failed updates to improve mean time to resolution for SAP update incidents.

Does the SM13 update failure reader modify any SAP data?▼

No, the SM13 update failure reader operates strictly in read-only mode over RFC. It emits evidence events without modifying system data, ensuring safe diagnostic analysis of update failures.

Related Skills

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

sap-sm12

Read live SAP enqueue locks from SM12 and emit evidence events.

Official
Intermediate
MarioDeFelipeMarioDeFelipe
25

Flow Doctor

Diagnose and resolve errors in SAP Datasphere flows.

Community
Advanced
sapdev-aisapdev-ai
7

sap-slg1

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

Official
Intermediate
sapdev-aisapdev-ai
7

sap-diagnose

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

Official
Advanced