Abap Developer

A self-contained ABAP coding assistant. It does not depend on the user's wiki-knowledge/ library — every reference and template lives inside this skill so it works the same in any workspace.

When to use

Load this skill whenever the user asks to:

• write a new ABAP report, include, function module, class, or interface
• generate ALV grid output (classic / OO / SALV)
• develop a selection screen, dialog screen (Dynpro), or tabstrip control
• send e-mail with plain body, HTML, or attachment (BCS / SO_NEW_DOCUMENT_ATT_SEND_API1)
• build or call a SOAP Web Service (Proxies / cl_http_client)
• build or call an OData service via SEGW
• call a BAPI / RFC / standard function module
• implement a BAdI / User Exit / Enhancement Spot / Implicit/Explicit enhancement
• create or drive a Smart Form (SSF_FUNCTION_MODULE_NAME)
• optimize Open SQL, internal-table operations, or runtime
• diagnose a runtime error / Dump (ST22) and propose a fix
• review or refactor existing ABAP for style / 7.4+ new syntax

Do not load this skill for: pure business-process questions unrelated to code, non-ABAP languages, or pure configuration tasks (those belong in the user's wiki-knowledge/).

Workflow Decision Tree

Match the user's request to one branch, then load the matching reference(s) and template(s).

User request
├── "报表 / 列表 / ALV / SALV"           → alv-patterns.md + templates/alv-*.abap
├── "选择屏幕 / 屏幕 / Dynpro"           → screen.md
├── "查询数据 / 内表 / SQL / 性能"       → data-processing.md
├── "日期 / 时间 / 工作日 / 月末"        → date-time.md
├── "发邮件 / 邮件 / 附件"              → email.md + templates/email-with-attachment.abap
├── "SmartForms / 打印 / 表单"          → smartforms.md + templates/smartform-driver.abap
├── "SOAP / WebService / Proxy"         → webservice-soap.md
├── "OData / SEGW / Fiori"              → odata-segw.md
├── "BAdI / User Exit / 增强 / Spot"    → enhancement.md
├── "BAPI / RFC / 标准 FM 调用"         → bapi-call.md + templates/bapi-call.abap
├── "RFC 异步 / aRFC / bgRFC / 跨系统"  → templates/rfc-async.abap
├── "IDoc / 物料分发 / ALE / 主数据推送" → templates/idoc-outbound.abap
├── "批量导入 / 替代 LSMW / 主数据批导" → templates/lsmw-replacement.abap
├── "Dump / 异常 / ST22 / 报错"         → exception-dump.md
├── "代码风格 / 命名 / 评审"            → code-style.md
├── "入门 / 新人 / 这 skill 怎么用"     → assets/intro.md
└── general ABAP syntax questions       → syntax-quick-ref.md

When the request is ambiguous, ask the user to confirm the branch before producing code. When the request clearly spans multiple branches, read the references in the order above (left wins on conflicts).

How to use this skill

1. Identify the branch via the decision tree.
2. read the matching references/<topic>.md file(s) — these contain the canonical patterns, pitfalls, and the file name of the asset template to use.
3. Compose the answer by citing the reference section (e.g. "Following `alv-patterns.md § OO ALV basic pattern …"). Output a single, compilable code block unless the user asked for explanation only.
4. When the reference points at a template file (assets/templates/<name>.abap), copy that template as the starting skeleton and adapt it; do not rewrite from scratch.
5. For each code block produced, include a brief § checklist (variables → events → main → subroutines/methods) so the user can verify placement.
6. After delivering, if a new pitfall or pattern emerged, write back to references/ — but do so by editing only the matching reference file; never edit WIKI-SCHEMA.md or other skills.

Output Conventions

• Indentation: 2 spaces. Always.
• Variable naming: prefix by type — see code-style.md § Naming.
• All examples assume Unicode system (abap_true / abap_false, string for character, i for integer).
• Write ABAP 7.4+ whenever possible (CONV, CORRESPONDING, VALUE, REDUCE, FILTER, table expressions itab[ key = … ], DATA(ls_), FIELD-SYMBOLS inline). For < 7.4 systems, note the fallback in a comment.
• Wrap each subroutine/ method body in """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" separators only when the file has 3+ sections; not required for small templates.

Reference Index

Asset Index

Templates live under assets/templates/. Each template ships in two formats:

Copy-then-adapt whichever file matches your target environment.

入门读物：

Resources

references/

Authoritative ABAP knowledge, one topic per file. read them in context when matching a branch above. Keep them lean — code blocks only when the pattern is non-obvious; otherwise just the spec.

assets/templates/

Boilerplate .abap files. Copy into the user's workspace, then adapt variable names / fields / logic. Do not echo them into chat; cite the relative path.

scripts/

Internal utilities maintained by the skill itself; not user-facing:

• scripts/build_index.py — regenerate references/README.md, assets/README.md, and the .md mirrors of every .abap template. Run after adding or editing any template.
• scripts/prepare_publish.py — build a SkillHub-uploadable release zip (drops .abap files, keeps the .md mirrors, calls skill-creator package_skill.py).

Publishing to SkillHub

1. Run python scripts/prepare_publish.py from the skill root.
   This writes dist/abap-developer.zip (the .md-only version) and dist/staging/abap-developer/ (auditable staging tree).
2. Upload dist/abap-developer.zip to <https://skillhub.cn/dashboard/publish>.
3. See PUBLISH.md for the full step-by-step.

```