onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewABAP, RAP and ABAP Cloud

New in ABAP

7 days30 days90 daysAll time
In the last 90 days
3releases185added to the atlas45new pieces of content120revisions
Change
Kind
Origin
Domain: 2
Clear all
353 changes
DayCapability
Domain Operations & RuntimeDomain Developer Experience

Today
26 changes
Cloud ALM Link for ADTadded to the atlasEclipse plugin linking ABAP transports to SAP Cloud ALM featuresIDE extension,
SAP TCode Runneradded to the atlasVS Code sidebar that opens SAP transactions through WebGUIIDE extension,
ABAP Cloud readinesscore coverage revisedReassessed against the graph (check:capabilities): the state changed, so the block now says what the added providers do, as kinds with the defining ones linked.Capability,
Browsing table datacore coverage revisedReassessed against the graph (check:capabilities): the note described the providers as SAP GUI programs only, and browser apps, an IDE extension and a desktop editor have arrived; the state stays core-and-community.Capability,
Show 22 more
Calling a service by handcore coverage revisedReassessed against the graph (check:capabilities): abap-odata-test arrived after the block was assessed and changes the kinds of community answer; the state stays core-and-community.Capability,
Change promotioncore coverage, id, ecosystems, name revisedPublic feedback issue #9. The ABAP name is kept in framing_by_ecosystem.abap; the default name and description now state the cross-door concern.Capability,
Code formattingcore coverage revisedReassessed against the graph (check:capabilities): the abap2UI5 playground provides this capability and the text never named it; ABAP FS named for the kind of VS Code integration.Capability,
Code reviewcore coverage revisedReassessed against the graph (check:capabilities): providers that arrived after the 2026-09-13 assessment (abapTimeMachine, abapOpenReview, a transport review app) shape the answer; state unchanged, core-and-community.Capability,
Configurationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): config-management arrived as a provider after the block was last looked at; the state stays core-and-community.Capability,
Debuggingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): seven ABAP providers newer than the block were never named. State stays core-and-community.Capability,
Driving the SAP GUIcore coverage revisedReassessed against the graph (check:capabilities): removed the count and the popularity wording, and named the kinds, including batch input (jrgkraus-tool-bi) and SAP's sample, which the text never named.Capability,
Editor supportcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the providers behind the UI5 door are SAP's (UI5 Language Assistant, and SAP Build Code and SAP Web IDE Full-Stack, which serve ui5). The community SAPUI5 Extension is an entry in the graph but has no provides edge to this capability.Capability,
Extensibilitycore coverage revisedReassessed against the graph (check:capabilities): a provider of a second kind, a discovery report for existing enhancement points, arrived after the block was last assessed and the text never named it. State unchanged (core-and-community).Capability,
Finding a transaction codecore coverage revisedReassessed against the graph (check:capabilities): sapgui arrived as a second kind, one that reads the system's own menu, and the prose counted entries.Capability,
Generatorscore coverage, coverage by ecosystem, framing by ecosystem revisedReassessed against the graph (check:capabilities): the atlas holds these entries, so the links point at them and not at their repositories (docs/WRITING.md section 4).Capability,
IDE provisioningcore coverage revisedReassessed against the graph (check:capabilities): eclipsadt-o-mat arrived after the last look and the text never named it; state unchanged.Capability,
Knowing the maintenance status of a releasecore coverage, coverage by ecosystem revisedui5-task-check-eocp, from public feedback issue #6, is the first independent provider on the UI5 door, beside SAP's SAPUI5 version overview.Capability,
Local developmentcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted providers and claimed an absence about who has built something, which goes stale as providers arrive.Capability,
Loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the state is now community-only and the block needed to say what the community adds.Capability,
Model visualisationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): abapGraph and abap-search-tools-ui arrived after the ABAP block was last looked at and the text never named them. No state changed.Capability,
Searching code in a systemcore coverage revisedReassessed against the graph (check:capabilities): the note named no kind of provider, and five providers newer than the 2026-09-14 assessment shape the answer. State unchanged.Capability,
Seed datacore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact provides seed-data for the UI5 door; the two tools the sentence named provide ui5-testing. The core stays present on the sourced what_core_does. The tools stay on the graph under ui5-testing.Capability,
Source controlcore coverage revisedReassessed against the graph (check:capabilities): providers added since 2026-08-31 change the kinds the community adds beyond the in-system git client; the state stays core-and-community.Capability,
Static analysiscore coverage revisedReassessed against the graph (check:capabilities): the block named none of the providers that arrived after 2026-08-31. State unchanged, core-and-community still matches the providers.Capability,
Telemetrycoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removes a universal claim about the providers that goes stale as they arrive.Capability,
Unit testingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted the artifacts and said they were in staging; both are in the graph now and are named.Capability,
Yesterday
1 change
ABAP Syntax Highlightingadded to the atlasVS Code syntax highlighting for .abap filesIDE extension,
Mon 19
11 changes
ABAP Call Hierarchyadded to the atlasEclipse plugin showing the call hierarchy of ABAP membersIDE extension,
ABAP Code Searchadded to the atlasEclipse plugin searching ABAP sources from the search dialogIDE extension,
ABAP Development Tools for VS CodepublishedA Devtoberfest 2026 session on ABAP Development Tools for VS Code: where the extension sits after the ABAP Workbench and ABAP Development Tools for Eclipse, the ADT language server both editors share, and what the releases since May 2026 cover. The demo installs the extension, creates a destination, opens, creates and activates objects, runs ATC and ABAP Unit, and names the object types, domains among them, for which a developer still goes to Eclipse or SAP GUI. It also opens the extension's settings to turn on the ADT MCP Server and shows the tools a chat can call, with the object search and source code search tools listed as planned.Talk,
ABAP Search and Analysis Toolsadded to the atlasEclipse plugin for ABAP object search and CDS view analysisIDE extension,
Show 7 more
ABAP Tagsadded to the atlasEclipse plugin for tagging ABAP repository objectsIDE extension,
SAP BAIP, ABAP environment – How to build partner solutions and get them certifiedpublishedA Devtoberfest 2026 session on the two ways a partner ships an ABAP Cloud solution built on SAP BTP ABAP environment, which the session calls the ABAP environment of SAP Business AI Platform: software delivery, where an add-on product is published with the solution ID from SAP Store onboarding and the customer discovers and deploys it into their own system, and service delivery, where the partner operates the same add-on as a multi-tenant SaaS and a new version is deployed rather than published again. That is the ABAP environment edge; the static analysis edge rests on the quality steps shown in the landscape portal, where the Manage Continuous Testing app released with 2608 runs an ATC check variant against a configured system on a recurrence pattern, beside test product version builds and managed test tenants. The second half walks through the SAP Integration and Certification Center process and the three BTP certification options open to an add-on product.Talk,
ABAP Select Converterflavors, description, links revisedThe flavor rests on the page's own "It is primarily used to migrate existing code to ABAP Cloud."; nothing on either page places the tool in standard ABAP. The page's "Additional infos" link was read for the first time and is now links.docs: it states the beta and lists what the converter supports and does not, which replaces the earlier "nothing for a batch of statements", a limit read off what the form does not show. The my-ide-actions sentence now follows that repository's own words, "The basis is the SwH tool" and the security table's "SELECT Converter | Software-Heroes API | -> Full SELECT Statement", and calls it an IDE Action rather than a package, which is the type that entry carries.Web tool,
Cloudification Repository Viewerflavors revisedThe documentation's Introduction places what the viewer shows in one flavor: "The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer." Neither page states a standard ABAP use, so that flavor is left unstated.Web tool,
Editor supportecosystems revisedUI5 Language Assistant, SAP's VS Code extension for UI5 XML views and manifest.json, and the SAPUI5 Extension by iljapostnovs were staged in intake-20261019-bestofui5 with this concern as their best fit, and the capability was not open on the UI5 door. The UI5 reading comes from the UI5 Language Assistant README.Capability,
Loggingecosystems revisedSRBJSLogger and openui5-error-collector were staged in intake-20261019-bestofui5 with no capability edge, because this capability was not open on the UI5 door. The UI5 reading comes from the sap/base/Log API documentation and the OpenUI5 Logging and Tracing page.Capability,
Seed dataecosystems revisedvscode-ui5-odata-mock-generator and openui5-smart-mockserver were staged in intake-20261019-bestofui5 under ui5-testing; the first one's drafter noted that seed-data fit better but was not open on the UI5 door. The UI5 reading comes from the OpenUI5 mock server pages and SAP's ui5-middleware-fe-mockserver README.Capability,
Sun 18
1 change
SAP S/4HANA Cloud: Scheduling Background Jobs Using Application Job TemplatespublishedWalks through moving S/4HANA Cloud and ABAP Environment job scheduling off ECC's SUBMIT and JOB_OPEN/JOB_SUBMIT/JOB_CLOSE pattern onto the Application Job Framework: a job template built from an ABAP class that implements IF_APJ_DT_EXEC_OBJECT and IF_APJ_RT_EXEC_OBJECT, then scheduled through the Manage Application Job Templates Fiori app or programmatically with CL_APJ_RT_JOB_SCHEDULING_API's SCHEDULE_JOB method. The resulting job is tracked in the Monitor Application Jobs app, where status, logs and failed runs are reviewed.Blog,
Sat 17
34 changes
@abap2ui5/linteradded to the atlasCommand-line checker for abap2UI5 app classes and their viewsCLI,
abap2UI5 for VS Codeadded to the atlasVS Code extension to preview, activate and lint abap2UI5 appsIDE extension,
abap2UI5 headless frontendadded to the atlasDrives abap2UI5 app classes from ABAP Unit testsPackage,
abap2UI5 Layout Editoradded to the atlasDrag-and-drop UI5 view editor that writes an abap2UI5 app classWeb tool,
Show 30 more
abap2UI5 Playgroundadded to the atlasIn-browser ABAP editor beside the abap2UI5 app it buildsWeb tool,
admin-cockpitadded to the atlasUsage, error and response-time monitor for abap2UI5App,
app-templateadded to the atlasStarter repository for an abap2UI5 app with CI and agent setupSample,
Clean-Core.ioadded to the atlasHosted workspace redrawing custom ABAP as BPMN and grading itWeb tool,
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successorsWeb tool,
config-managementadded to the atlasTheme, CSS and CSP settings of abap2UI5 pages kept in tablesApp,
sapguiadded to the atlasThirty classic transactions rebuilt as abap2UI5 appsApp,
se16nadded to the atlasTable content browser in abap2UI5, for ABAP Cloud and on premiseApp,
web-abap2UI5added to the atlasabap2UI5 transpiled to JavaScript and run in a browser tabWeb tool,
abap-adt-apireleased 9.0.01 content item in the atlas was written against an earlier version. Nothing is recorded about what changed.Package,
ABAP - Create dumpexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
AI-enabled administration: Automating log analysis with generative AI hubexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Browsing table datadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Calling a service by handdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Capturing Background Job Errors in SAP Using the Application Log (SLG0/SLG1)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Change promotiondescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Cloudification Repository Viewerrequires, connects revisedSAP's Cloudification Repository entered the graph, so the repository this reads is a node rather than a name in a sentence. Both edges rest on the viewer's own documentation: the repository "lists released standard APIs that can be used to build the TIER 1 layer", and the Repository field is a "Selection of the different release statuses that are made available by SAP in different JSON files". No protocol, direction or condition: the documentation states none.Web tool,
Code reviewdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Debugging in ABAP Development Tool (Part 1)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Driving the SAP GUIdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Explore SAP Fiori elements for ABAP developersexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Talk,
IDE provisioningdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Model visualisationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BAIP, ABAP environment: Monitoring and troubleshootingexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Scheduling a Background Job for the BDC Session Method Using RSBDCSUBexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Searching code in a systemdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Source controlname, description revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Static analysisdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Unit testingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Fri 16
3 changes
Hammer Core Servicesadded to the atlasABAP-side component for the Hammer editorApp,
open-steamgateadded to the atlasLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemApp,
Tools for abapGitadded to the atlasHelper programs around abapGitApp,
Thu 15
9 changes
@abaplint/transpileradded to the atlasTranspiles ABAP to JavaScript to run on Node.jsBuild tool,
express-icf-shimadded to the atlasShim running an ABAP ICF handler behind an Express 4.x serverPackage,
How to Create an Application Job (APJ) in SAP S/4HANA ABAP — With Single Values & Select OptionspublishedWalks through implementing an Application Job end to end on the ABAP door: a class implements IF_APJ_RT_EXEC_OBJECT for runtime execution and IF_APJ_DT_EXEC_OBJECT to define parameters, covering both single-value parameters and select options, then registers the class as a job catalog entry and template in ADT for scheduling through the Application Jobs Fiori app. Frames Application Jobs as the class-based, ADT-defined successor to the classic SM36/SM37 background job transactions.Blog,
How to extend ABAP Test Cockpit on SAP BTP for custom use casespublishedWalks through the released, C1-contract APIs and CDS views for extending ABAP Test Cockpit on SAP BTP: the single entry point CL_SATC_API=>CREATE_API_FACTORY, reading a run's findings and headers through SATC_API_FINDINGS and SATC_API_RESULT_HEADERS, starting synchronous local ATC runs for a transport, approving or rejecting exemptions programmatically, configuring approver responsibility areas without a UI, and implementing a custom check through IF_CI_ATC_CHECK. Code snippets show each API in use, including the CDS views that join ATC results to the Custom Code Migration app's own findings.Blog,
Show 5 more
open-abap-baladded to the atlasApplication logging for ABAP transpiled to JavaScript on Node.jsPackage,
open-abap-coreadded to the atlasCore ABAP artifacts for code transpiled by @abaplint/transpilerPackage,
Local developmentcore coverage, coverage by flavor, framing by flavor, facets revisedNine options answered this capability with nothing to compare them by, and they are not variants of one tool: the first question a reader has is which part of the local stack an option starts. The two flags separate the hybrid-testing helpers, where cds bind states that only the location of the credentials is stored on the machine and @sang2x/captools states that it writes the resolved VCAP_SERVICES into default-env.json.Capability,
Telemetrycore coverage, coverage by flavor, framing by flavor, framing by ecosystem, facets revisedThree questions the sources answer differently for the CAP options and that change which one a reader reaches for: which signals it produces, where it can send them, and whether the application has to write code for a signal of its own. Scoped to the CAP door; the ABAP and BTP options were not assessed in this pass.Capability,
Unit testingcore coverage, coverage by flavor revisedTwo staged options state abap-cloud and provide this capability; the gate reads them as providers once this capability is revised.Capability,
Wed 14
6 changes
Capturing Background Job Errors in SAP Using the Application Log (SLG0/SLG1)publishedWalks through ABAP's Application Log framework for recording errors from a background job that has no screen to show them on: defining an Object and Sub-object in SLG0, then building the log in code with BAL_LOG_CREATE, adding a free-text or message-class entry with BAL_LOG_MSG_ADD_FREE_TEXT or BAL_LOG_MSG_ADD, and persisting it with BAL_DB_SAVE so it survives after the job finishes. The worked example is a report inserting student records into a custom table, scheduled via SM36 and reviewed afterwards in SLG1, filtered by the Object and Sub-object that created it.Blog,
Scheduling a Background Job for the BDC Session Method Using RSBDCSUBpublishedWalks through uploading data with GUI_UPLOAD, building a BDC session with BDC_OPEN_GROUP, BDC_INSERT and BDC_CLOSE_GROUP, then scheduling the standard program RSBDCSUB as a background job with JOB_OPEN, SUBMIT ... VIA JOB and JOB_CLOSE so the session processes without manual SM35 intervention. Shows the resulting job's status and spool read back through SM37, the way a reader confirms afterwards that a scheduled job actually ran.Blog,
Driving the SAP GUInormative relevance revisedThe GUI servers' boundaries each restated the policy in the atlas's own words; it belongs to the concern, sourced to the policy.Capability,
kts982/mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
Show 2 more
mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
sapgui.mcpdescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
Mon 12
7 changes
abap-transport-reviewadded to the atlasTransport release check gated by GitHub pull request approvalApp,
pam-mcp-serveradded to the atlasLocal MCP server on support status from an SAP PAM exportMCP server,
SAP Support Radaradded to the atlasBrowser app checking SAP product support status from a PAM exportWeb tool,
abap-transport-reviewentry revisedEntered by intake from the repository README and the repository's own facts. Placed on the ABAP door in the standard-abap flavor only, because the README states the tools are classic ABAP using the CTS_REQUEST_CHECK BAdI, background jobs and the cluster table INDX, "none of which is part of ABAP Cloud".App,
Show 3 more
Knowing the maintenance status of a releaseentry revisedDrafted with sap-support-radar and pam-mcp-server, the first umbrella artifacts (ADR-0063), which had no concern to attach to: mcp-servers is serving an application one built, agent-systems-access reaches into a running SAP system, and documentation is first-party docs made searchable. On the ABAP, CAP and UI5 doors because each has a published SAP answer of its own: the Product Availability Matrix, capire's release schedule and the SAPUI5 version overview. BTP is left out: its services name plans and regions rather than releases, and no page was read that states a maintenance period for one. core-only on every door because SAP publishes the answer and no door holds an option of its own; the umbrella entries count into no door's coverage by construction.Capability,
pam-mcp-serverentry revisedStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.MCP server,
SAP Support Radarentry revisedStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.Web tool,
Sun 11
12 changes
AI-enabled administration: Automating log analysis with generative AI hubpublishedA log analysis tool for incident work, built in SAP Business Application Studio with the generative AI hub feature, which SAP AI Core ships as its LLM integration by its own documentation: it automates root-cause analysis over system errors and masks sensitive data. SAP's abstract states the tool's jobs and not how the hub is called, what the masking covers or which model answers. A TechEd 2026 session (Wednesday 28 October, Berlin), with no speaker listed in the catalogue at the time of writing, written here from SAP's abstract; the recording is not yet published.Talk,
AI-first, API-first: What changes when AI becomes the userpublishedWhat changes in an architecture when an AI agent is the caller: AI-first and API-first principles, SAP's API governance, extensibility and the composable enterprise, with lessons the speaker draws from SAP's and other enterprise AI initiatives. The extensibility edge rests on the abstract naming extensibility as a principle and nothing more specific; no API, product or tool is named, so the talk is attached to the broadest concern it touches. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Tomasz Wilk, written here from SAP's abstract; the recording is not yet published.Talk,
Build agentic SAP extensions with Google CloudpublishedGoogle Cloud's architectures for agentic AI apps on SAP with a clean core: SAP Business AI Platform, SAP S/4HANA and SAP Business Data Cloud joined with BigQuery, Gemini and Google's Agent Development Kit. The abstract names zero-copy data agents, developer API workflows and ABAP extensions for AI integration, the last of which is the Extensibility concern; Business Data Cloud is the one atlas entry it names, and how any piece connects to another is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Ekaterina Kruse, Ian Moria and Stany Winkler, written here from SAP's abstract; the recording is not yet published.Talk,
Deploy, review, break, fix: Govern cloud transports with agility and AIpublishedFive BTP services in one delivery chain, as the abstract lays it out: a transport is triggered in SAP Content Agent Service, tested in SAP Cloud Transport Management, its failure is raised by SAP Alert Notification service for SAP BTP and remediated by a SAP Joule agent with SAP Automation Pilot, and SAP Cloud Logging keeps the history for root-cause analysis. The chain from alert to remediation is the operations automation concern; what the Joule agent decides on its own is not in the abstract. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Biser Simeonov, Daniel Funkert, Sven Rullmann and Thorsten Sandfuchs, written here from SAP's abstract; the recording is not yet published.Talk,
Show 8 more
Explore SAP Fiori elements for ABAP developerspublishedSAP Fiori elements for an ABAP developer who now builds the UI as well as the RAP business object behind it, the transactional model of ABAP Cloud, in SAP Business Application Studio; the abstract calls the UI side new territory for that developer, and a Fiori elements app is rendered from the service's Fiori annotations rather than hand-written UI code. The abstract names the tool and the stack and does not say which floorplan or annotations are shown. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Björn Schulz, written here from SAP's abstract; the recording is not yet published.Talk,
Extending SAP Autonomous SuitepublishedExtensibility across SAP Autonomous Suite: AI-enabled development in SAP Build solutions, the ABAP Cloud model among them, as the way extensions are designed, generated and deployed, and a direction for making extensions ready for agentic AI. The abstract names the suite, SAP Build and the ABAP Cloud model and no single feature, so the edges are to Extensibility, the concern, and to SAP Build Code, the SAP Build solution held here in which Joule generates and deploys development; which other SAP Build solutions the session shows is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Alexander Rother and Khaled MUSILHY, written here from SAP's abstract; the recording is not yet published.Talk,
From intent to extension: Joule and the future of solution extensibilitypublishedHow Joule turns natural-language intent into extensions across SAP Autonomous Suite: intent-based agent extensions, enriching the agents SAP delivers, packaging options for partners and what SAP calls a harmonised extensibility experience. The edges are to SAP Joule, which does the translating, and to Extensibility, the concern; the abstract names the directions and no feature that ships today. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Amitha Kamath, Oren Shatil and Richard Kuba, written here from SAP's abstract; the recording is not yet published.Talk,
Navigating the road map for SAP Cloud ERP: Today, next, and beyondpublishedSAP's near-term and long-term plans for SAP Cloud ERP by theme: embedded AI, process automation, lifecycle management and extensibility, with timelines and adoption paths toward what SAP calls the Autonomous Enterprise. SAP Cloud ERP has no artifact here, so the edges are to the two concerns the road map names, Extensibility and Process automation; the abstract names no product or feature under either, and whether its process automation is SAP Build Process Automation is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin; also TM815V, virtual), presented by Lawrence Martin and Sasa Markovic, written here from SAP's abstract; the recording is not yet published.Talk,
SAP BAIP, ABAP environment: Monitoring and troubleshootingpublishedMonitoring and troubleshooting a side-by-side application written in the ABAP Cloud model on SAP BTP ABAP environment, which SAP's title calls SAP BAIP, ABAP environment, and which the abstract files under a clean core strategy at level A: the environment's technical monitoring tools for the monitoring half, and ABAP Development Tools for Eclipse for the troubleshooting half, the debugging concern. The abstract names the environment and the Eclipse tools, leaves the monitoring tools unnamed, and does not say what is shown of either. A TechEd 2026 hands-on session (Thursday 29 October, Berlin), presented by Frank Jentsch, Robert Werlich, Steffen Siegmund and Wolfgang Woehrle, written here from SAP's abstract; the recording is not yet published.Talk,
The journey with clean core continues for SAP Cloud ERP PrivatepublishedClean core in SAP S/4HANA Cloud Private Edition as it stands in 2026: what is new in extensibility, new capabilities in the dashboard for the RISE with SAP Methodology, how AI helps make custom code compliant with clean core, and new guidance on data, integration and clean core in relation to SAP's API policy. The edges are to Extensibility, the concern the session is about, and to ABAP Cloud readiness, the concern behind making custom code compliant; the abstract names no tool for either and the dashboard is not held here. A TechEd 2026 session (Wednesday 28 October, Berlin; also TM108V, virtual), presented by Markus Goebel and Olga Dolinskaja, written here from SAP's abstract; the recording is not yet published.Talk,
Use change and deployment management in an ABAP environment with confidencepublishedSAP Cloud Transport Management with SAP Cloud ALM as the governed way to move changes from a cloud-optimised ABAP environment into production: the abstract says the session sets out the process, where it differs from classic transport mechanisms, the current state of every content type it carries, and an outlook on deploying agents through it, which is the transport management concern on the cloud side. What each content type covers, and when agent deployment arrives, is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Moritz Gysler and Sven Rullmann, written here from SAP's abstract; the recording is not yet published.Talk,
What's next in extensibility for SAP Autonomous SuitepublishedAgent-driven extensibility across SAP Autonomous Suite as SAP sees it ahead: what is coming for making extensions ready for agentic AI and how SAP's assistants are meant to help with it. The edge is to Extensibility, the concern; the abstract names no assistant, no feature and no date. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Alexander Rother and Oren Shatil, written here from SAP's abstract; the recording is not yet published.Talk,
Sat 10
1 change
Clean Core Measurementadded to the atlasReports Clean Core ATC results per system as Level A to D KPIsApp,
Fri 9
1 change
Unleashing ABAP Potential: An introduction to Extension Libraries (XCO)publishedIntroduces ABAP's Extension Libraries (XCO), a library framework that puts reusable functionality behind one interface. The post places it as part of the ABAP RESTful Application Programming Model but versatile enough for other ABAP contexts, and says it works in both on-premise ABAP and the ABAP environment on SAP Business Technology Platform. It walks through a worked Logging example: xco_log=>factory->create_new_log opens a log keyed by object, subobject and external ID, logger->add_message appends a typed message, and logger->add_last_symsg attaches a problem class and level of detail for later traceability.Blog,
Sun 4
3 changes
Clean Core IndexpublishedDescribes a company-built KPI, the Clean Core Index, that scores existing custom ABAP code by object type — reports, function modules, SAPScript/Smartforms, ATC S/4 readiness-check findings, user exits and modifications — each weighted by a severity the author sets for redesign effort and upgrade risk, with counts read off CDS views built for the purpose. The index is the author's own definition rather than an official one and does not by itself certify public-cloud readiness, but tracking it weekly shows where custom code still blocks a move to ABAP Cloud and lets progress be read per module or per object type.Blog,
eclipsADT-o-matadded to the atlasPowerShell wizard installing Eclipse with ADT and pluginsCLI,
eclipsADT-o-matentry revisedEntered by intake from the repository README and description.CLI,
Sat 3
3 changes
ABAP's Parallel Processing Frameworks: Practical Guide to Performance Tuning of Mass Data ProcessingpublishedSurveys ABAP's two parallel processing technologies, asynchronous RFC (aRFC) and the queued, exactly-once background RFC (bgRFC), and the six frameworks built on top of them, SPTA, SHDB, CL_ABAP_PARALLEL, the Background Processing Framework, the Parallel Processing Framework and the Mass Data Framework, each by its own entry point: a function module, a factory class or a Customizing transaction. A Qualitative Weight and Summ matrix then compares the frameworks across criteria such as package creation, load balancing and documentation quality, stated as the author's own subjective scoring for one project rather than a ranking.Blog,
Debugging in ABAP Development Tool (Part 1)publishedA walkthrough of the ABAP Debugger inside ABAP Development Tools: setting a toggle (hard) breakpoint versus a soft breakpoint that only fires once a session is already active, running up to four debugging sessions on the same program, reading the call stack, and debugging an update function module. It also covers watchpoints with their recent and current values, conditional and user-specific breakpoints, activating and deleting breakpoints, and adding variables such as SY-INDEX to the variables tab.Blog,
Enhancing Standard BAPIs: When and How to Do ItpublishedWalks through why a standard BAPI needs enhancing — a missing field, an extra validation, logic before or after the call, or a performance tweak — and five ways ABAP offers to do it: a BAdI found in SE18/SE19, an append structure for extra fields, a classic user exit wired through SMOD/CMOD, a wrapper function module copied from the original, or an implicit enhancement when no other extension point exists. Each technique gets its own steps, and two carry a short ABAP code example.Blog,
Fri 2
3 changes
Clean Core清洁核心概况介绍publishedExplains Clean Core as SAP's architecture methodology for decoupling custom code from standard code, and walks through the A-D grading SAP uses for a single extension's cleanliness: D for direct modification of standard tables, programs, classes or functions, or disallowed patterns such as implicit enhancements; C for internally developed functions calling unreleased APIs; B for using only SAP's classic or released APIs (BAPI, ALV Grid, BAdI); A for side-by-side extensions reached only through released interfaces onto the SAP Build extension suite. It lays out a six-step roadmap for reaching Clean Core — inventorying existing extensions, setting a reduction target, surveying SAP's extension routes (SAP GUI SE80, Fiori custom fields and logic, BTP high/low-code, workflow/RPA), writing a decision tree, splitting new development from legacy migration, and reviewing periodically — while noting that in-app development is not inherently unclean and that real decisions should weigh ROI rather than follow the theory absolutely.Blog,
S/4HANA公有云版的内部ABAP拓展publishedArgues 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.Blog,
Taking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP ToolspublishedWalks through how SAP's standard path classifies custom ABAP extensions into Clean Core Levels A through D, running ABAP Test Cockpit against the Cloudification Repository's release status for each SAP object an extension touches, then feeding results into the RISE with SAP Methodology Dashboard in SAP Cloud ALM. Contrasts that with Project Kernseife, an open-source custom ATC check that lets a team override SAP's classification with project-specific rules, define its own successor objects (including custom wrappers), and expose a Score and Potential Score per finding through a CDS view for prioritizing cleanup — at the cost of owning and maintaining that classification. States which situations favor each: Kernseife where the standard rules are too rigid for the project's reality, the standard dashboard where cross-system comparability and low maintenance effort matter more.Blog,
Thu 1
2 changes
abapthemesadded to the atlasThree colour themes for ABAP source in ADT for EclipseIDE extension,
abapwuluadded to the atlasRefreshes the where-used list for objects in one packageCLI,

Tue 29
5 changes
Hammeradded to the atlasNative macOS code editor for ABAP and CDSDesktop app,
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIpublishedWalks through pulling SAP Cloud ALM's Outbound Logs, Metrics and Traces APIs — OAuth 2.0 client-credentials auth, protobuf-encoded OTLP payloads, and the guardrails needed against its rate limits and 24 GB/30-day retention baseline — plus SAP LogServ's infrastructure logs, into Google BigQuery for multi-year, cross-domain storage. A time-window SQL join then correlates ABAP exceptions, health metrics, infrastructure events and ITSM tickets, with the joined record passed to Vertex AI (Gemini) to draft a structured incident dossier.Blog,
ui5-tcode-finderadded to the atlasBrowser page searching SAP transaction codesWeb tool,
Finding a transaction codeentry revisedA browser tool for searching transaction codes had nowhere to attach, and the nearest nodes are all about something else: browsing table data is the rows a system holds rather than the way into a task, GUI automation drives screens rather than finding them, abap-classic-ui builds them, and documentation is what to read. Named on the ABAP door because a transaction code is an entry point of a classic SAP system, and marked not-applicable in ABAP Cloud, where there is no SAP GUI and so no command field to enter one into. The coverage rests on SAP's own documentation for the in-session routes; nobody has surveyed what else answers this from outside a system, which is why the relationship is unassessed.Capability,
Show 1 more
ui5-tcode-finderentry revisedStaged with the capability Finding a transaction code, drafted in the same batch because the corpus held no concern for it. ecosystem: abap is a placement rather than a stated fact: the repository is an OpenUI5 and TypeScript application, but its subject is the transaction codes of a classic SAP system and the only stack its features name is SAP GUI for HTML. serves_ecosystems: ui5 rests on the overview sentence naming the T-Codes a UI5 or Fiori project needs. use_as: reference because it is consulted at its own address rather than installed into a project.Web tool,
Sun 27
6 changes
Configurationcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Capability,
Debuggingcore coverage revisedPackage pass 2026-09-27: the paragraph named one of the four SAP packages and cited the plugins index only; cds debug and the Java developer dashboard were cited nowhere.Capability,
Feature togglescore coverage revisedcapire audit 2026-09-27: the Feature Toggles guide documents toggled features as built into both runtimes, with the production toggle provider left to the project, which is exactly what the one community option supplies. The capability had no core paragraph and no source.Capability,
Local developmentcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Capability,
Show 2 more
Loggingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
Telemetrycore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
Fri 25
2 changes
AVEdescription revisedNeither "Simple Data Explorer" nor "SDE" appears in this README, and VERTEX's own README now states "Nothing but this repository's src/ has to be installed", so the claim that VERTEX needs Simple Data Explorer on the system is unsupported. The replacement rests on this README's own sentence: the version history, the diff and the saved code review, "including approving, declining and commenting on a block", are available in Eclipse ADT and in VS Code through VERTEX. "has no blame yet" was a claim about VERTEX that this README does not carry and that was not re-verified against VERTEX; it is dropped rather than restated.App,
Simple Data Explorerdescription revisedThe README no longer says this repository holds the ADT resources VERTEX reads through: two commits on 2026-09-18 removed the ADT resources section and the construction-phase note, leaving only "The table grid with its select-options, the join builder and the pivot are available in Eclipse ADT and in VS Code through VERTEX". VERTEX's own README now states "Nothing but this repository's src/ has to be installed" and that of the former /zsde/ prefix "that hub is gone". The replacement keeps what this README still states and drops the dependency claim neither README supports. ADT.md is still in the repository and still describes the resources under /sap/bc/adt/zsde/ in the present tense, which conflicts with both READMEs and is left for an editor.App,
Wed 23
1 change
Clean Core maturity and the new Extensibility LevelspublishedSets 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.Blog,
Tue 22
1 change
off-stack-abapadded to the atlasDemonstration of off-stack ABAP development on Node.jsSample,
Mon 21
2 changes
Multi-Origin Service Testing and Troubleshooting in SAP GatewaypublishedWalks through testing a multi-origin OData service in SAP Gateway by passing the $system parameter against a System Alias defined in /IWFND/MAINT_SERVICE, verified with the SAP Gateway Client (/IWFND/GW_CLIENT) and from outside the system with a browser or Postman. Covers three recurring failures — an ignored $system, a 500 from an unconfigured RFC destination or inactive backend service, and a 403 from a missing backend authorization — and how to confirm which alias and backend a request actually hit with /IWFND/TRACES.Blog,
vscode-tabl-ddicadded to the atlasVS Code syntax highlighting for .tabl.ddic table definitionsIDE extension,
Fri 18
15 changes
@arc-mcp/adt-lsadded to the atlasTypeScript SDK over SAP's headless adt-ls language serverPackage,
050: Clean Core Measurement (Preview)publishedWalks through Clean Core Measurement (CCM), an open-source tool for tracking ABAP Cloud readiness across a system landscape: a dashboard showing Cloud Ready and Upgrade Stable status and a Technical Debt Score per system, runs recorded under administration, and a process area where custom APIs not released by SAP can be documented and excluded from the score. Reporting breaks the score down to individual objects, the unreleased APIs behind them, and which team or product cluster carries the most outstanding work.Blog,
ABAP remote filesystemadded to the atlasVS Code extension editing ABAP systems over ADT as a filesystemIDE extension,
abap_trial_dockeradded to the atlasScripts running the ABAP Developer Edition in DockerCLI,
Show 11 more
abap-adt-apiadded to the atlasJS/TS client for the ADT resources of an ABAP systemPackage,
abapcdsgrammaradded to the atlasANTLR4 grammar, lexer and parser for ABAP CDSPackage,
abapfs_extensionsadded to the atlasABAP objects enabling ADT updates on systems older than 7.51Package,
abapgraphadded to the atlasABAP library for creating Graphviz graphsPackage,
abapPrettyadded to the atlasCommand-line ABAP pretty printer over ADTCLI,
ActiveControl Transport form creatoradded to the atlasVS Code extension automating ActiveControl transport formsIDE extension,
adt-bundle-builderadded to the atlasWindows build packaging Eclipse with ADT as a portable IDEBuild tool,
CCM - Calculate Key FigurespublishedExplains how the Clean Core Measurement (CCM) project turns ABAP Test Cockpit findings into the Technical Debt Score shown on its Clean Core Dashboard: messages from the ABAP_CLEAN_CORE_READINESS check are weighted by severity level (B/C/D) and summed per object, while the object's overall classification follows its highest message level rather than the point total. Covers where the calculation can be tuned — configurable weights, an exemption process, and additional metrics for documented but unreleased API use — and how the resulting score and classification drive the object list and per-object processing views.Blog,
Graphviz-browseradded to the atlasStatic page drawing Graphviz graphs for the ABAP debugger extensionWeb tool,
personal-application-studioadded to the atlasTheia distribution with ABAP and UI5 support as a Docker imageDesktop app,
urbani-saplinkadded to the atlasSE16 clone shipped as SAPlink filesApp,
Thu 17
1 change
abap-adt-cliadded to the atlasCLI that pulls and pushes ABAP packages as local files over ADTCLI,
Wed 16
7 changes
A Handy Custom Report to Scan SAP CDS Views for Usage of Search StringspublishedA custom SE38 report, ZSCAN_CDS_VIEWS, reads each Z-prefixed CDS view's DDL source through the function module /ABEX/SEFW_MOD_CVA_HANA and scans it for a list of search strings, listing the view and matching code line in an ALV grid. The author built it because ABAP Development Tools for Eclipse's ABAP Source Search, the code search SAP ships, is unwieldy for scanning many custom views at once or searching several strings together.Blog,
ABAP - Create dumppublishedShows how to terminate an ABAP program on purpose with RAISE SHORTDUMP — from a freshly created exception instance, or one already caught in a TRY/CATCH where continuing no longer makes sense — so a hard-to-diagnose failure leaves a dump behind instead of running on silently. The second half reads that dump back in ABAP Development Tools for Eclipse: the Feed Reader notification, the compressed view against the classic ST22-style view, and sections such as Active Calls and Source Code Extract, the same ADT troubleshooting path debugging places alongside the ABAP Debugger for ABAP Cloud.Blog,
ABAP Select Converteradded to the atlasConverts classic Open SQL SELECTs to released CDS entitiesWeb tool,
Cloudification Repository Vieweradded to the atlasBrowser form over SAP's Cloudification Repository for ABAP CloudWeb tool,
Show 3 more
abap-cloud-loggerreleased 2.0.0Examples that keep writing to a logger after free( ), or display a log with zcl_cloud_logger_view_alv.Package,
ABAP Select Converterentry revisedEntered from software-heroes.com's tools page. artifact_type web-tool is new to the schema as of this run, added for exactly this shape: a hosted, no-install utility rather than a package, CLI or BTP service.Web tool,
Cloudification Repository Viewerentry revisedEntered from software-heroes.com's tools page, as the first artifact_type web-tool in the corpus alongside xexer-abap-select-converter, xexer-cds-field-mapping, xexer-odata-batch-creator and xexer-xlf-translator.Web tool,
Tue 15
8 changes
ABAP Development Tools for Eclipseadded to the atlasSAP's Eclipse plugins for ABAP development over ADTPackage,
ADT resourcesadded to the atlasHTTP endpoint under /sap/bc/adt exposing ABAP development objectsPlatform,
Claude ported ABAP functions to new APIpublishedA 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.Blog,
Object Release State in Cloudification Repository Viewer for Clean Core ExtensibilitypublishedWalks through the five release states the Cloudification Repository Viewer assigns to an object — Released, Deprecated, Classic API, Not to be Released, and No API — and what each means for ABAP Cloud readiness: the clean core level it maps to and the ATC check priority it triggers. Explains why the same object can carry two states at once, such as a Classic API that later also becomes Released, and why the check has to be run against the specific release being developed on rather than assumed to hold across releases.Blog,
Show 4 more
SAP BTP ABAP environmentadded to the atlasABAP runtime on BTP for the ABAP Cloud modelService,
SAP Cloud Transport Managementadded to the atlasMoves MTA archives and content between SAP BTP accountsService,
Editor supportecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the editor is a hosted service rather than a language server or an Eclipse plugin, which is what the CAP and ABAP framings describe.Capability,
VERTEXrequires revisedPointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.IDE extension,
Mon 14
117 changes
abaKadded to the atlasLibrary for managing ABAP constants from registered sourcesPackage,
ABAP Cloud LoggerpublishedWraps ABAP Cloud's cl_bali_* Application Log classes in ZCL_CLOUD_LOGGER, an open-source, MIT-licensed logger installed via abapGit. One fluent entry point takes free text, sy-msg-style messages, exceptions, BAPIRET2 tables or arbitrary data serialised to JSON, and multiton instances keyed on object/subobject/external number let unrelated code share a logger without passing instances around. It adds sticky per-iteration context, built-in timing, and a readable trail of the cx_bali_runtime errors the class swallows internally.Blog,
ABAP development tools for Visual Studio Code is now available on the VS Code marketplace!publishedAnnounces the marketplace release of ABAP development tools for Visual Studio Code, an extension that works against any ABAP system already reachable from ADT for Eclipse and is focused on RAP UI service development, so the Fiori/SAPUI5 frontend and the ABAP backend can be built in the same tool. It ships a built-in ADT MCP Server, disabled by default and switched on from the extension settings, and points readers to a documentation template for capturing ABAP-specific rules in a project's AGENTS.md file for chat agents such as Microsoft Copilot.Blog,
ABAP Development Tools for VS Codeadded to the atlasSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsPackage,
Show 113 more
ABAP development under the Clean Core paradigm: From BAPIs to BO and CDSpublishedSAP's Level Based Clean Core classification (2025) grades ABAP APIs A through D by cloud readiness, and this piece uses the S/4HANA Cloudification Repository's own count — of 3,847 BAPI function modules for SAP Cloud ERP Private, only 23 are Level A — to show how much Classic API (Level B) code needs to move to RAP business objects instead. A worked Bank Master example matches each BAPI to its EML statement or ABAP CDS SELECT equivalent, and states when that move is actually required: mandatory once on SAP Public Cloud, optional but advisable on Private Cloud/On-Premise as BAPIs stop gaining new fields.Blog,
ABAP_DATABASE_MANAGERadded to the atlasABAP report running custom SQL queries into an ALV gridApp,
abap_db_preparatoradded to the atlasReplays stored database snapshots in ABAP unit testsPackage,
abap_debugger_object_graph_extensionadded to the atlasABAP debugger extension drawing objects as a Graphviz graphApp,
ABAP_LOGGINGadded to the atlasObject-oriented wrapper around the Business Application LogPackage,
abap-call-hierarchyadded to the atlasADT backend for the ABAP Call Hierarchy Eclipse pluginPackage,
abap-cloud-loggeradded to the atlasChainable logger for ABAP Cloud around CL_BALI_LOGPackage,
abap-code-search-toolsadded to the atlasIn-system ABAP source search by string or regular expressionPackage,
abap-db-browseradded to the atlasSAP GUI browser for tables, views, CDS views and joinsApp,
abap-dynamic-assignmentadded to the atlasFramework for runtime parameters, ranges and value mappings in ABAPPackage,
abap-feature-toggleadded to the atlasFeature toggle for ABAP read via is_active on view ZFEAT_TOGGLEPackage,
abap-fluentdadded to the atlasFluentd client in ABAP for sending log lines to a collectorPackage,
abap-fm-loggeradded to the atlasLogger storing RFC function module call parameters as JSONPackage,
abap-gencustadded to the atlasGeneric customizing table and reader for ad hoc ABAP parametersPackage,
abap-logadded to the atlasABAP logging library with one interface across output targetsPackage,
abap-log-exporteradded to the atlasExports Business Application Log entries to Graylog or LokiApp,
ABAP-Loggeradded to the atlasLogging library for ABAP over the Application LogPackage,
abap-message-loggeradded to the atlasMessage logger for ABAP Cloud that saves to the Application LogPackage,
abap-metricsadded to the atlasSoftware-engineering metrics for an ABAP class or packageApp,
abap-metrics-provideradded to the atlasExposes ABAP stack metrics to a monitoring toolApp,
ABAP-Object-Visualizeradded to the atlasDebugger script exporting an object hierarchy as GraphvizApp,
abap-odata-testadded to the atlasABAP client for calling and asserting on OData servicesPackage,
abap-opentelemetryadded to the atlasOTLP serialisation of traces, metrics and logs in ABAPPackage,
abap-point-gateadded to the atlasFramework activating custom ABAP enhancements through a Fiori appPackage,
abap-prometheusadded to the atlasPrometheus client for ABAP, installed with abapGitPackage,
abap-search-toolsadded to the atlasADT backend for the ABAP Search and Analysis Tools pluginPackage,
abap-senchaadded to the atlasBDD/TDD assertion library for ABAP Unit, styled after Chai.jsPackage,
abap-system-fieldsadded to the atlasInjectable wrapper for SY fields and date functions in ABAP CloudPackage,
abap-tags-backendadded to the atlasADT backend for the ABAP Tags Eclipse pluginPackage,
abap-test-containeradded to the atlasGitHub-hosted test data container for ABAP CloudPackage,
abap-tvarvcadded to the atlasHelper class for reading TVARVC parameters and select-optionsPackage,
abap-unit-runneradded to the atlasApplication job that runs and schedules ABAP Unit tests in the cloudApp,
abap-utesthelpadded to the atlasHelper classes for ABAP Unit tests and test doublesPackage,
abapCovadded to the atlasUploads ABAP Unit code coverage to codecov.ioApp,
abapFakeradded to the atlasFake data generator for ABAPPackage,
AbapGeneratoradded to the atlasABAP transaction generating an MVC-style project from a templateGenerator,
abapGitServeradded to the atlasGit server implemented in ABAP for abapGit clientsApp,
abapify/promiseadded to the atlasPromise and async/await implementation for ABAPPackage,
abaplint-Ext-for-abapGitadded to the atlasShows abaplint results inside abapGitPackage,
abaplint-sci-clientadded to the atlasABAP client surfacing abaplint checks in Code Inspector and ATCPackage,
abapOpenChecksadded to the atlasOpen-source rule pack for SAP Code Inspector and ATCPackage,
abapOpenReviewadded to the atlasSAP GUI code review tied to transport releaseApp,
ABAPParallelizationServiceadded to the atlasFramework for running ABAP work units in parallel tasksPackage,
abapTimeMachineadded to the atlasShows a whole ABAP object as it stood at a past versionApp,
abapToCadded to the atlasSAP GUI transaction for one-click transports of copiesApp,
adash-servicesadded to the atlasBackend exposing ABAP Unit runs and coverage over REST and ODataPackage,
alwinvandeput/zscv_search_cds_viewsadded to the atlasIn-system search tool for CDS viewsApp,
aqoadded to the atlasABAP application options as a structure with a generated editorPackage,
assertadded to the atlasFluent assertion helper for ABAP Unit testsPackage,
ATC-Best-Practice-Guideadded to the atlasATC check classes accompanying DSAG's ATC best-practice guideSample,
BenjaminWeisheit/ABAP-2-CODE-CHARTAadded to the atlasConverts ABAP code metrics into Code Charta's JSON formatPackage,
bothzoli/ABAP-IoC-Containeradded to the atlasInversion-of-control container for ABAPPackage,
boy0korea/ZWD_CODE_SCANNERadded to the atlasCode scanner for Web Dynpro ABAPApp,
bryanmcain/zcode_scanneradded to the atlasEnhancement extending ECC's code scanner to more object typesPackage,
By-passing function modules in aunitspublishedWalks through registering a function module as a test double with CL_FUNCTION_TEST_ENVIRONMENT inside an ABAP Unit test class: class_setup names the function module to replace, an input configuration matches on the importing parameters, and an output configuration sets what the double returns before the calling class is asserted against it. The Function Test Double Framework is presented as ABAP Unit's way of testing code that calls a function module — procedural, without a class's native test-double support — without triggering the database, RFC or BAPI calls the real function module would make.Blog,
cacamber-BDD-for-ABAPadded to the atlasBDD framework turning Given/When/Then into ABAP Unit stepsPackage,
codepageadded to the atlasPolyfill for CL_ABAP_CODEPAGE under Clean CorePackage,
coreline/ZDDIC_FINDERadded to the atlasFinder for ABAP Dictionary objectsApp,
COROUTINES4ABAPadded to the atlasCoroutine framework for ABAP with awaitable resultsPackage,
dbg_value_statementadded to the atlasDebugger script generating a VALUE statement for a variableGenerator,
dump_infoadded to the atlasDisplays the variables of ABAP short dumpsApp,
Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)publishedWalks 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.Blog,
Featuretoggleadded to the atlasFeature toggle framework for ABAP with a UI5 GUIPackage,
furkancosgun/Transport-Management-Tooladded to the atlasUploads, downloads and imports ABAP transport requests as filesApp,
furkancosgun/ZWARPadded to the atlasAdds a program's dependent objects to a transport requestApp,
gladiusadded to the atlasABAP project for learning the ABAP Unit Test FrameworkSample,
mockAadded to the atlasA free mocking framework for ABAP, published under the Apache License 2.0.Package,
mockup_loaderadded to the atlasLoader of Excel-prepared ABAP unit test data, with stub generationPackage,
my-ide-actionsadded to the atlasCollection of ABAP Development Tools IDE ActionsIDE extension,
pokrakam/abapDevSysInitadded to the atlasABAP report setting up a new ABAP Developer Edition or trial systemApp,
qttadded to the atlasTool mapping BEx queries to the transport requests carrying themApp,
regression_testadded to the atlasSnapshot testing library for ABAP, from debugger or unit testPackage,
RFC_TOOLSadded to the atlasA wrapper class for calling asynchronous RFC function modules in parallel from ABAP, one instance per parallel task.Package,
sap-russia/ZRS_ABAP_SOURCE_SCANadded to the atlasA report that searches code inside modifications and enhancements without depending on SAP HANA.App,
SAP-samples/abap-platform-application-jobsadded to the atlasRAP sample scheduling a class as a background application jobSample,
sap-usi-logging-apiadded to the atlasObject-oriented wrapper around SAP's Application Log (SLG1)Package,
SAP2Mooseadded to the atlasAn ABAP program that extracts model data from a system as a SOMIX model, for Moose2Model to draw as a dependency diagram.App,
Source Code Finderadded to the atlasReport searching ABAP source in methods, enhancements, DTPs and moreApp,
striezl/VariScanadded to the atlasSearch over ABAP program variants for a value or patternCLI,
swixfort/Sdw.Abap.Diadded to the atlasA dependency-injection container for ABAP: register classes or interfaces, then resolve an object with its dependencies already constructed.Package,
The Future of ABAP is Here: VS Code ADT, Zero-Config MCP, and AI Co-pilotspublishedA walkthrough of ABAP Development Tools for VS Code's general-availability release: connecting to an on-premise or BTP ABAP system, editing classes, CDS and RAP objects, and turning on the extension's built-in ADT MCP Server. Enabled, it lets a co-pilot such as GitHub Copilot or SAP Joule for Developers, ABAP AI capabilities read code, trace dependencies, and run ABAP Unit and ATC checks against the real system rather than guessing from training data.Blog,
tool-biadded to the atlasChained-call builder for ABAP batch input transactionsPackage,
trm-serveradded to the atlasServer-side component of TRM for importing and exporting transportsPackage,
upDOWNciadded to the atlasUploads and downloads Code Inspector check variants as XMLApp,
Vise_for_ABAPadded to the atlasA characterisation-test helper: ZCL_VISE=>GRIP records a field's value once and fails a later run if it has changed.Package,
ZABAP_SAP_ENHANCEMENTSadded to the atlasReport listing user-exits, BAdIs and enhancement spots of a programApp,
zconcurrency_apiadded to the atlasParallel task library for ABAP over the SPTA frameworkPackage,
ZCTS_BROWSERadded to the atlasReport creating transports of copies without a new versionApp,
ZTCTadded to the atlasA transport checking tool that analyses ABAP transports at object level before they move to production, determining a safe order and flagging risks.App,
zthreadadded to the atlasThreading library for ABAP modelled on Java's Thread and RunnablePackage,
ztoadadded to the atlasOpen SQL editor for ABAP with ALV outputApp,
ZUML_DIAGRAMadded to the atlasABAP program drawing UML class diagrams through PlantUMLApp,
ABAP Cloud readinesscoverage by flavor, framing by flavor revisedThe classic-side reading (readiness assessment of existing code, e.g. the ATC_CLOUD_READINESS check variant) does not carry over unchanged: inside ABAP Cloud the same restriction is a standing constraint on new code rather than a migration gate.Capability,
Browsing table datacoverage by flavor revisedADT's Data Preview over released CDS view entities is the ABAP Cloud replacement for SE16, which does not exist there since SAP GUI is unavailable; none of the three independent providers on this capability state abap-cloud support.Capability,
Calling a service by handcoverage by flavor revisedADT's Service URL link, GET only, is the one way to call a RAP OData service by hand in ABAP Cloud; SAP Gateway Client needs SAP GUI, which ABAP Cloud systems do not have, and ODAPU, the one independent provider on this capability, states no flavor.Capability,
Change promotioncoverage by flavor revisedABAP Cloud's transport story is SAP's own: gCTS through the Manage Software Components app in the BTP ABAP environment, and Export/Import Software Collection in S/4HANA Cloud Public Edition. The one provider found on the ABAP door for this capability, abapToC's ZTOC transaction, is a classic transport-of-copies tool built as an SAP GUI transaction and states no flavor, so no community option is present in ABAP Cloud.Capability,
Code reviewcoverage by flavor revisedADT is confirmed as ABAP Cloud's own development environment and gCTS as its transport mechanism, and no ABAP-ecosystem provider of this capability states the abap-cloud flavor, so the flavor reads core-only rather than derived.Capability,
Configurationecosystems revisedWidened to ABAP: greltel/abap-dynamic-assignment, raketenstart-abap/abap-tvarvc, jrgkraus/abap-gencust, abapinho/abaK and bizhuka/aqo keep parameters and constants out of ABAP code, as wrappers around TVARVC or replacements for it.Capability,
Debuggingcoverage by flavor revisedAssessed for the ABAP Cloud flavor: SAP's own troubleshooting guidance for RAP apps places the ABAP Debugger inside ABAP Development Tools, and the only ABAP-door provider in the corpus, Smart Debugger, states standard-abap only and runs in the SAP GUI New Debugger, not ADT — so no provider states abap-cloud and the core is SAP's own.Capability,
Driving the SAP GUIcoverage by flavor revisedSAP's own ABAP Cloud documentation states there is no access to SAP GUI in the SAP BTP ABAP environment or SAP S/4HANA Cloud Public Edition, both of which mandate ABAP Cloud, and none of the four ABAP-door providers of this capability states abap-cloud support — all four state only standard-abap.Capability,
Editor supportecosystems revisedWidened to ABAP: Xexer/my-ide-actions adds IDE actions to ADT, and DevEpos/abap-tags-backend and DevEpos/abap-call-hierarchy are the ABAP backends of two Eclipse plugins. The description lost its CDS wording, which moved to framing_by_ecosystem.cap.Capability,
Extensibilitycoverage by flavor revisedExtensibility in ABAP Cloud is defined by the platform itself — released extension points, RAP, and ADT-only tooling — rather than by any single artifact; no artifact in the abap door states abap-cloud as a provider of capability:abap-extensibility.Capability,
Feature togglesecosystems revisedWidened to ABAP: btc-ag/Featuretoggle and raketenstart-abap/abap-feature-toggle turn features in ABAP code on and off at runtime, each with a screen to switch them.Capability,
Generatorsecosystems revisedAbapGenerator scaffolds ABAP objects from a template package. Thirteen UI5 Community repositories generate UI5 projects or add to one: Easy-UI5 and its npm init wrapper, generators for apps, libraries, controls and tooling extensions, and create-wdi5 and generator-ui5-wdi5, which add wdi5 to an existing app.Capability,
Job schedulingecosystems revisedSAP-samples/abap-platform-application-jobs schedules a class as an application job from an action on a RAP business object and shows the job's status and log in the app. It answers the concern on the ABAP door.Capability,
Local developmentecosystems revisedabapDevSysInit sets up a new ABAP Developer Edition or trial system from one report: the user profile, the GitHub certificates and destination, abapGit standalone, and the repositories to pull.Capability,
Loggingecosystems revisedNine repositories log from ABAP: six wrap the application log or its ABAP Cloud API, one logs function module calls to its own table, and two send entries to Fluentd, Graylog or Loki.Capability,
Model visualisationecosystems, description revisedThe description named only a CDS model and .cds files, which is false on the ABAP door added the same day. The ABAP half and 'source file' are the only change.Capability,
Seed dataecosystems revisedabapFaker generates localised fake names, addresses and other values in ABAP for development and tests, so the concern has an answer behind the ABAP door.Capability,
Source controlcoverage by flavor, framing by flavor revisedThe classic-ABAP paragraph does not hold here: ABAP Cloud splits source control into two mechanisms with different scopes, per the same SAP-docs pages.Capability,
Static analysiscoverage by flavor revisedNo provider of this capability states the abap-cloud flavor: ACE and code pal for ABAP state only standard-abap, and abaplint-Ext-for-abapGit, abaplint and @abapify/acds state no flavor at all — while ATC's own ABAP_CLOUD_DEVELOPMENT_DEFAULT check variant is SAP's documented default for the SAP BTP ABAP environment.Capability,
Telemetryecosystems revisedabap-metrics-provider, abap-opentelemetry and abap-prometheus export metrics and OpenTelemetry data from an ABAP system; SAP-samples/teched2025-CS261 monitors an instrumented BTP application through SAP Cloud ALM and SAP Cloud Logging.Capability,
Unit testingcoverage by flavor revisedNo artifact in the abap door states abap-cloud as a provider of capability:abap-unit-testing; ABAP Unit and its test double frameworks are part of the language and ADT tooling, and SAP's own RAP400 workshop and the abap-cheat-sheets unit-test examples both exercise them from a BTP ABAP Environment ABAP Cloud project, doubling only the released CDS entities and tables a RAP business object depends on.Capability,
Sun 13
33 changes
abap-platform-yyadded to the atlasDemo RTTI-style library for the ABAP Environment, built to show APACKSample,
abapgit-commitlintadded to the atlasabapGit user exits checking commit messages against repository rulesPackage,
ACEadded to the atlasSAP GUI tool for static analysis of ABAP call flow and code metricsApp,
AVEadded to the atlasSAP GUI version explorer and code reviewer for transport requestsApp,
Show 29 more
How to Scan Custom ABAP for Security Issues in Eclipse (Step-by-Step)publishedWritten by someone who works on the tool, this is a setup walkthrough for the RedRays ABAP Scanner Eclipse plugin: get a demo API key, install the plugin via an update site, point it at a backend, and scan an ABAP object from the Project Explorer. Findings for SQL/ADBC injection, OS command execution, path traversal, missing AUTHORITY-CHECK and similar are grouped by severity with a CVSS score and an automated exploitability check, and a REST API extends the same scan to a CI/CD allow/block gate on a transport.Blog,
HR_DMEadded to the atlasRead-only SAP GUI report listing where HCM object data is storedApp,
ODAPUadded to the atlasUI5 app for OData test requests and ABAP Push ChannelsApp,
Recommendations for Wrapper Interface DesignpublishedWalks through designing a wrapper interface that encapsulates a classic BAPI (BAPI_USER_GET_DETAIL) behind a C1-released interface, so the code released for ABAP Cloud stays limited to types and structures ABAP Cloud can actually access. Covers when a non-released SAP structure can still be referenced safely, when it cannot, and how the API_CONSISTENCY and API_COMPATIBILITY ATC checks catch the difference before an upgrade breaks it.Blog,
SAP-samples/abap-platform-bgpf-appl-log-events-side-effectsadded to the atlasRAP sample with bgPF, business events and side effectsSample,
SAP-samples/abap-platform-ccm-workshopsadded to the atlasWorkshop material on adapting custom ABAP code for S/4HANASample,
SAP-samples/abap-platform-jakadded to the atlasJSON-to-ABAP conversion library sample showing what APACK can doSample,
SAP-samples/abap-platform-nominated-apis-consumptionadded to the atlasTier 2 wrapper pattern for consuming a nominated API from RAPSample,
SAP-samples/abap-platform-rap-transactional-outbox-with-bgpfadded to the atlasTransactional outbox pattern in ABAP Cloud with bgPFSample,
SAP-samples/abap-platform-rap620added to the atlasWorkshop on a side-by-side S/4HANA extension on BTP ABAP EnvironmentSample,
SAP-samples/abap-platform-rap630added to the atlasWorkshop on developer extensibility of released RAP business objectsSample,
SAP-samples/abap-platform-rap630-extadded to the atlasExtension project for the RAP630 developer-extensibility workshopSample,
SAP-samples/abap-platform-rap640added to the atlasWorkshop on wrapping a non-released SAP API for use in ABAP CloudSample,
SAP-samples/cloud-abap-rapadded to the atlasRAP business object that generates other RAP business objectsSample,
SAP-samples/cross-stack-partner-reference-extensionadded to the atlasCross-stack extension pairing on-stack RAP with a side-by-side CAP appSample,
SAP-samples/joule-gui-automation-and-integrationadded to the atlasJoule capabilities driving SAP GUI sessions via Business ClientSample,
SAP-samples/on-stack-partner-reference-extensionadded to the atlasLoyalty Hub on-stack RAP extension for S/4HANA Cloud Public EditionSample,
SAP-samples/s4hana-gcts-badiadded to the atlasBAdI wiring the transport organizer to gCTS on task releaseSample,
SAP-samples/teched2025-DT260added to the atlasTechEd 2025 workshop modernising a classic app to ABAP CloudSample,
SAP-samples/teched2025-DT261added to the atlasTechEd 2025 workshop extending an SAP-delivered RAP business objectSample,
SAP-samples/teched2025-DT266added to the atlasTechEd 2025 workshop on troubleshooting ABAP Cloud extensionsSample,
Simple Data Exploreradded to the atlasMulti-window SAP GUI explorer for tables, views and CDS SQL viewsApp,
Smart Debuggeradded to the atlasSAP GUI debugger script recording steps so execution can run backwardsApp,
sql-consoleadded to the atlasBrowser-based SQL console built on abap2UI5App,
VERTEXadded to the atlasADT extension for Eclipse and VS Code showing three SAP GUI toolsIDE extension,
Configurationname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Debuggingecosystems revisedWidened rather than forked: debugging an ABAP program is the same concern, so the node's description became the cross-ecosystem sentence, the CAP wording moved to framing_by_ecosystem.cap, and ABAP got its own framing and coverage. Done so Smart Debugger (staged in intake-20260913-ysichov) can provide it.Capability,
Generatorsname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Seed dataname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Fri 11
4 changes
Job schedulingcoverage by ecosystem revisedThe core schedules tasks on its event queues: alpha in Node.js from the May 2025 release, cron and singleton tasks in @sap/cds 9.9.0, and CAP Java in 5.0.0. The 2026-09-09 assessment missed it.Capability,
kts982/mcp-sap-guidescription revisedCorrected against the README: 'HTTP transport (for team/remote use, binds to localhost)', with 'Unattended multi-user production orchestration' under Not yet available.MCP server,
mcp-sap-guidescription revisedCorrected against the README: it works from coordinates and screenshots and never mentions the Scripting API. 'Still the most used' was an unsourced popularity claim (hard rule 1); 'the first' is now the GitHub creation date, 2025-02-19, against the other GUI servers.MCP server,
ROSAdescription revisedCorrected against the README: 'The previously hosted public instance (on Railway) has been retired'.MCP server,
Thu 10
11 changes
kts982/mcp-sap-guiadded to the atlasMCP server for SAP GUI for Windows via the Scripting APIMCP server,
mcp-sap-guiadded to the atlasMCP server working SAP GUI by screen coordinatesMCP server,
ROSAadded to the atlasMCP server answering whether SAP objects are released for ABAP CloudMCP server,
sapgui.mcpadded to the atlasMCP server driving SAP GUI and Web GUI for end-to-end testingMCP server,
Show 7 more
SAPient MCPadded to the atlasSAP GUI automation MCP server built on RoboSAPiensMCP server,
Driving the SAP GUIentry revisedFour artifacts drive SAP's own UI and the corpus had no concern for them — filing them on agent access to your code would have been wrong, because none of them reads an object or knows what ADT is. Named on the ABAP door because the GUI is the ABAP system's UI.Capability,
kts982/mcp-sap-guientry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
mcp-sap-guientry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
ROSAentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
sapgui.mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
SAPient MCPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
Wed 9
2 changes
code pal for ABAPadded to the atlasATC and Code Inspector checks for Clean ABAPPackage,
Loggingecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Capability,
Tue 8
1 change
@abapify/acdsprovides revisedPlaced on data modelling because it deals in ABAP CDS definitions. Reading the capability again moved it: acds does not help you define data, it parses definitions somebody else wrote into a typed AST — which is the substrate static analysis is built on, and it lives in the adt-cli repository. The mistake surfaced when repointing a CAP package away from the ABAP capability left this one holding it alone.Package,
Mon 7
1 change
@abapify/acdsadded to the atlasParser for ABAP CDS DDL source with a typed ASTPackage,
Sun 6
1 change
Transitioning Architectures from SAP NetWeaverpublishedA community contribution from Glencore, an SAP customer, on what replaces NetWeaver-based products as their standard maintenance ends in 2027: the scenarios where NetWeaver-era solutions fall short — integration with cloud-based landscapes, extensibility — and the successor options per use case, pointing at SAP's product availability matrix and note 1648480 for the official successors. Customer-authored, so the framing is a migration decision rather than a product description.Reference architecture,
Tue 1
1 change
Seed datacore coverage revisedWrong since mid-2024 and nobody had checked. It said generated volumes were community territory; cds add data has generated volumes since @sap/cds-dk 7.9.0. Found by doing the version-history pass — which is the argument for that pass in one line.Capability,

Mon 31
10 changes
abap-file-formatsadded to the atlasSAP's specification for serialising ABAP objects to filesPractice,
abapGitadded to the atlasGit client written in ABAP that runs inside the systemApp,
abaplintadded to the atlasStatic analysis for ABAP source outside a systemCLI,
Configurationcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Show 6 more
Debuggingcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Editor supportcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Local developmentcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Loggingcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Seed datacore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Telemetrycore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Capability,
Wed 5
1 change
abap-dynamic-assignmentreleased 2.0.0Adds the authorization object ZDA_VAR (fields ACTVT, ZDA_PROG), the authorization class ZDA and a DCL role on the root view entity.Package,
The last 90 days. Older changes stay in each entry's history.
AtomJSON