sap-dev-status

Perform read-only RFC health checks on SAP dev artefacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only health checks for the artefacts managed by sap-dev-init, enabling quick validation of SAP development artefacts without making any changes.

Core Features & Use Cases

  • Checks artefacts including transport requests, development packages, function groups, the wrapper FM Z_GENERIC_RFC_WRAPPER_TBL and its DDIC parameter structures, the wrapper table type, and the ZCMRUPDATE_ADDON_TABLE utility program.
  • Emits one parseable line per artefact plus a summary line to help operators decide next steps; can be auto-invoked as a pre-flight for other sap-dev skills.

Quick Start

Invoke the skill to perform a read-only pre-flight health check on the SAP dev artefacts.

Frequently Asked Questions about sap-dev-status

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

FAQPage Schema
How do I perform a read-only health check on SAP development artefacts?

A read-only SAP dev health check inspects artefacts like transport requests, development packages, function groups, and the Z_GENERIC_RFC_WRAPPER_TBL function module via RFC. It emits one parseable line per artefact plus a summary line to guide next steps.

What is a pre-flight validation for SAP transport requests and function groups?

Pre-flight validation for SAP transport requests and function groups is a read-only check that verifies the existence and health of development artefacts before executing further operations. It reports per-artefact status lines and a summary without making any system changes.

Do I need SAP NCo 3.1 installed to run RFC pre-flight checks on SAP dev artefacts?

Yes, you need SAP NCo 3.1 (32-bit, .NET 4.0) installed in the GAC to run RFC pre-flight checks on SAP dev artefacts. This connector provides the underlying RFC communication framework required to query the SAP system read-only.

Can I validate the Z_GENERIC_RFC_WRAPPER_TBL function module and DDIC structures without modifying them?

Yes, you can validate the Z_GENERIC_RFC_WRAPPER_TBL function module, its DDIC parameter structures, and wrapper table types without modifying them. The health check performs read-only RFC checks and reports status, ensuring no changes are made to the SAP system.

What SAP development artefacts are covered by a pre-flight health check?

A pre-flight health check covers transport requests, development packages, function groups, the wrapper FM Z_GENERIC_RFC_WRAPPER_TBL, its DDIC parameter structures, the wrapper table type, and the ZCMRUPDATE_ADDON_TABLE utility program. Each artefact receives an individual status line.

Why is my SAP dev health check not working with a 64-bit SAP NCo installation?

SAP dev health checks require the 32-bit version of SAP NCo 3.1 targeting .NET 4.0, installed in the GAC. A 64-bit SAP NCo installation will not satisfy this constraint, preventing the read-only RFC checks from executing correctly against the SAP artefacts.