Build on ABAP
Before you build, check what is there. If you find something close, think about contributing to it. If you find nothing, start building.
Check what is there
Search by the use case, not by a package name: the same need often sits under a capability you would not guess. The capability map and Browse hold everything in ABAP.
What gets built on ABAP
Found something? Contribute
Where an artifact does most of what you need, a fix, a test or a page of documentation reaches everyone who already uses it. Read where it stops and its open and closed issues first: someone may have asked already. Then contribute to a project. These are the places where evidence or a second hand counts most.
Not known yet
- Get RAP patterns that match the target system
Not known yet for abap-skills, 3 of 4 artifacts cover it
- Let an agent change ABAP in an on-premise system
Not known yet for ADT MCP Server, 6 of 7 artifacts cover it
- Work on ABAP with an agent and no system connection
Not known yet for sapskills, 5 of 7 artifacts cover it
One artifact stands
- Async processingABAP-PRC
- AttachmentsAttachmentCommentODataService
- Authorizationsap-usi-authority-check
- CachingABAP-CACHE-BOX
- Data privacyDST
- Database connectorsSAP HANA
- Fiori annotationsrap-ext
- Key-user adaptationonurakca/SAPUI5-Adaptation-Project-Downloader
- Launchpad pluginsgenerator-ui5-ts-flp-plugin
- Seed dataabapFaker
- Statistical analysisABAP Statistical Tools
- Transactional modelAnyTabUpdateTask
Nothing there? Build
Use cases no recorded artifact covers, and capabilities with no artifact in ABAP. Unmapped means the atlas holds nothing, not that nothing exists: search once more, then build an abapgit project.
Use cases nothing covers
Every assessed use case in ABAP has an artifact that covers it.
Capabilities with no artifact
Read in the atlas
Extensibility
- Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)Walks through adding a custom "Repayment" tab to the Customer Master (XD01/XD02/XD03) using SAP's TAXI framework: an append structure on table KNB1, a subscreen built in SE80, and two BAdI implementations — CUSTOMER_ADD_DATA and CUSTOMER_ADD_DATA_CS — registered through SPRO. The BAdIs are the released extension points that keep the tab upgrade-safe without modifying standard code, the developer-extension half of the capability's tiered model.Divya_palem, published 2026-06-01
- Extending Standard S/4 HANA OData API'sExtending Standard S/4 HANA OData API'sWalks through extending a standard S/4HANA OData API with a custom field, preferring OData V4 over V2 for its closer OASIS compliance and simpler service enablement, then tracing the extensibility objects documented for the entity before touching any code. The custom field reaches the API by layering three CDS view extensions — extendView on I_Product, extendViewEntity on R_ProductTP and on A_Product_3 — following the projection chain down to where the base table is first selected, built in ABAP Development Tools for Eclipse.JuanDK78, published 2026-04-08
- Clean Core maturity and the new Extensibility LevelsClean Core maturity and the new Extensibility LevelsSets out SAP's Clean Core Level concept, the successor to the 3-Tier Development Model, which grades extensibility by how upgrade-safe it is rather than by where it runs: Level A covers on-stack extensions on released RAP and CDS views plus side-by-side apps on BTP, Level B covers upgrade-stable classic APIs listed in the Cloudification Repository, Level C covers internal-object use flagged through SAP's Changelog for SAP Objects, and Level D covers direct modifications and implicit enhancements that ABAP Test Cockpit checks must block. Choosing between an on-stack and a side-by-side implementation is left to the SAP Application Extension Methodology, and the official Level classifications are filed under SAP Note 3578329.EmilianoAyub, published 2025-12-19
- S/4HANA公有云版的内部ABAP拓展S/4HANA公有云版的内部ABAP拓展Argues that S/4HANA Cloud public edition's in-app ABAP extensibility is still real ABAP development, just under stricter rules: developer extensions require ABAP Development Tools rather than SAP GUI transactions, data models are defined as CDS views instead of SE11 tables, business logic is a RAP behavior definition instead of a function module, and service exposure is an auto-generated OData service from a Service Definition instead of a hand-built RFC/BAPI. The piece walks a worked example — a Fiori app that triggers the Purchase Requisition API — through CDS, RAP, OData activation on SAP Gateway, and authorization via business catalogues, and frames the whitelist of released APIs and CDS views as upgrade-safety rather than a restriction.ArthurYang, published 2025-11-24
Source control
- Claude ported ABAP functions to new APIClaude ported ABAP functions to new APIA first-person account of using Claude Code, driven through the sapcli command line, to install and repair RFC function modules that let a CI pipeline control abapGit and gCTS remotely, rather than treating git as a way to read ABAP source. Instead of trusting a local checkout, Claude read the abapGit login manager class and queried the target system's own type catalogue through sapcli, then used what it found to update a renamed API method and swap a TABLES parameter's structure for the table type BAPIRET2_T.jakub_filak, published 2026-03-16
- Patterns for using LLMs in ABAP developmentPatterns for using LLMs in ABAP developmentLars Hvam compares eight ABAP development setups: assistance in SE80 or Eclipse, virtual files and MCP over ADT, a centrally managed MCP service, sandboxes, local Git, Git with read-only system context, and temporary ABAP systems for development and CI. The overview describes where source changes, review and system access happen, including abapGit synchronization and abaplint checks. It is dated March 2026; its risk, cost and autonomy ratings are the writer’s assessments.