sap-document-object

Convert ABAP objects into specification documents with RFC-derived DDIC texts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill produces a formal specification document for an existing ABAP object — the inverse of the /sap-gen-abap spec-to-code flow — and upgrades the /sap-explain-object dossier by reusing its comprehension engine, enriching with RFC-derived data (DDIC texts, key fields, message texts) and rendering a sectioned deliverable.

Core Features & Use Cases

  • Reuses explain-object's comprehension map to produce a customer-grade specification.
  • Enriches the deliverable with RFC-backed DDIC details, message texts, and callers, when available.
  • Renders the result as Markdown (.md), Word (.docx), or a filled specification workbook (.xlsx) for sign-off.

Quick Start

Provide an ABAP object name (or an existing explain-output folder) and request the spec output in one of the supported formats.

Frequently Asked Questions about sap-document-object

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

FAQPage Schema
How do I generate a formal specification document from an existing ABAP object?

To generate a specification from an ABAP object, use the workflow to reverse-engineer existing code into a review-ready document, enriching it with RFC-derived DDIC texts, key fields, and message texts for formal sign-off.

Can I export ABAP documentation to Word or Excel for sign-off?

Yes, you can export ABAP documentation to Word or Excel for sign-off. The skill renders the formal specification output as Markdown, Word (.docx), or a filled Excel (.xlsx) workbook to facilitate the review process.

How does RFC enrichment work for ABAP DDIC texts and message texts?

RFC enrichment for ABAP DDIC texts and message texts works by connecting to a pinned SAP login to retrieve data dictionary details, key fields, and message texts, which are then injected into the formal specification document.

Do I need to run the explain-object workflow before generating an ABAP specification?

Yes, you must run the sap-explain-object workflow beforehand. It generates the required map.json, source.txt, and dossier.md files, and requires a pinned SAP login and access to the object's source.

What is the best way to reverse-engineer ABAP code into a customer-grade specification?

The best way to reverse-engineer ABAP code into a customer-grade specification is to reuse the explain-object comprehension map, enriching it with RFC-backed DDIC details, callers, and message texts to produce a sectioned deliverable ready for review.

What are the limitations of generating specs from ABAP objects without RFC access?

Without RFC access to a pinned SAP login, the specification generation loses its ability to enrich the document with DDIC texts, key fields, message texts, and caller information, resulting in a less detailed deliverable based solely on source code analysis.