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

sap-slg1

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Read-only SLG1 application-log headers (BALHDR) are scanned over RFC to surface problem-bearing logs and counts of Abort/Error/Warning messages, helping incident responders identify root causes quickly.

Core Features & Use Cases

  • Reads BALHDR via RFC to identify problem-bearing logs within a given time window.
  • Emits structured evidence compatible with the shared diagnose contract for incident workups.
  • Integrates with the /sap-diagnose flow and supports filtering by date, user, and window to narrow investigation scope.

Quick Start

Provide an anchor path and optional date/window filters to start scanning SLG1 logs via RFC.

Frequently Asked Questions about sap-slg1

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

FAQPage Schema
How do I read SAP SLG1 application logs over RFC for incident analysis?▼

The Skill scans BALHDR application-log headers over RFC to identify problem-bearing logs within a specified time window, emitting structured evidence for incident workups.

Can I filter SAP application logs by user and date window during incident workups?▼

Yes, SAP application logs can be filtered by date, user, and time window to narrow the investigation scope during incident workups and isolate root causes.

What SAP login profile is required to retrieve SLG1 logs via RFC?▼

A saved SAP login profile and a working RFC connection are required to access the target SAP system and retrieve SLG1 application-log headers.

Does this approach extract detailed SLG1 message texts or only log headers?▼

This approach reads read-only SLG1 application-log headers (BALHDR) to surface problem-bearing logs and message counts, rather than extracting full detailed message texts.

How do SLG1 logs help diagnose failures in SAP goods movement and billing processes?▼

SLG1 logs contain Abort, Error, and Warning messages that point to failures in SAP processes such as goods movement, billing, or interfaces, helping incident responders identify root causes.

What is the best way to surface error counts in SAP BALHDR logs during incident response?▼

Scanning BALHDR application-log headers over RFC surfaces counts of Abort, Error, and Warning messages, helping incident responders identify problem-bearing logs quickly.

Related Skills

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

sap-sm37

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

Official
Intermediate
redhat-etredhat-et
1

investigate-incident

Investigate platform incidents by gathering evidence and generating root cause documentation.

Official
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-rfc-wrapper-fm

Invoke non-RFC-enabled SAP function modules via Z_GENERIC_RFC_WRAPPER_TBL.

Official
Advanced