sap-sm12

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Read live enqueue lock entries from SM12 and emit one evidence event per lock for auditing and troubleshooting, without altering system data.

Core Features & Use Cases

  • Read ENQUEUE_READ to fetch current locks from the enqueue table in a controlled, read-only fashion.
  • Emit structured evidence events per lock to support audit trails and incident analysis.
  • Operate standalone or as part of the sap-diagnose workflow against a specified SAP system and time window.

Quick Start

Use the sap-sm12 skill to read current enqueue locks and emit evidence events.

Frequently Asked Questions about sap-sm12

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

FAQPage Schema
How do I read live SM12 enqueue lock entries for an SAP audit?

You can read live SM12 enqueue lock entries by calling the RFC-enabled ENQUEUE_READ interface to fetch current locks from the enqueue table in a controlled, read-only fashion without altering system data.

What do I need to connect PowerShell to SAP and read SM12 locks?

To read SM12 locks you need a saved SAP login profile, PowerShell with the SAP NCo libraries installed, and an RFC-enabled ENQUEUE_READ interface or a generic fallback wrapper if the standard interface is unavailable.

Can I use this approach to capture SAP enqueue data for incident troubleshooting?

Yes, reading the enqueue table emits one structured evidence event per lock, providing an audit trail and supporting incident analysis across a specified SAP system and time window.

What is the best way to automate SM12 lock evidence collection without modifying the SAP system?

Use a read-only PowerShell script that calls ENQUEUE_READ to fetch current locks and emit structured evidence events per lock, ensuring no system data is altered during the audit or debugging process.

Why does my SM12 lock reading script fail when the ENQUEUE_READ interface is unavailable?

If the RFC-enabled ENQUEUE_READ interface is unavailable the script must fall back to a generic wrapper, and without PowerShell and the SAP NCo libraries the connection cannot be established at all.