rules.abaplint.org/classic_exce...

Sankt Patrick

looks like a drive by automated PR

Package structure in #ABAP ? If the bulk of the code is located in a single package, perhaps its worth to take a look on how to move objects to make it more clear where different responsibilities are located?

abapGit below, using abaplint.app with updated insights,

abaplint.app/stats/abapGi...

We keep enhancing #abapGit

Here's a nice link to see what was added recently (since we tagged PRs more thoroughly). It's mostly support for new object types but there are some other goodies, too, that you might not know about:

github.com/abapGit/abap...

I always think of this guy,

ABAP: Don't do concurrent changes to the same object Some objects in ABAP supports doing concurrent changes in different transports, e.g.

Check out my latest article: #ABAP: Don't do concurrent changes to the same object www.linkedin.com/pulse/abap-d... via @LinkedIn

Open-source #ABAP had a very strong 2025

Now there are over 5000 devs and 10000 repositories listed publicly on GitHub 🎉

Let’s make 2026 even bigger. Share more, use more, live more ABAP

PS: AI loves open source, too 😉

stardev.io/languages/abap

Og slet ikke så farligt som kalenderlys

maybe we'll be able to switch off the downport step, making the execution run a lot faster

The ABAP track on Exercism now has over 20,000 students!

😲👍

What an incredible success. @larshvam.bsky.social and several contributors made it possible 🎉

exercism.org/tracks/abap

Give it a try, solve some exercises, and if you want a challenge contribute a new exercise or two 😄

#abaplint 2.114.0 published with new rule rules.abaplint.org/index_comple... #ABAP #SAP

New feature in #abapGit:

From the "New Online Repo" dialog, you can jump to a new dialog for creating a GitHub repository without having to visit github-com 😀

As always, you can get the latest version at github.com/abapGit/abap...

There are huge, interconnected bubbles in tech, along with defense and space tech, and they could all pop at anytime. Happy Friday!

sorry 😅🤠

the ##NEEDED in line 18 annoys me the most, as the variable is used in the next line

If you couldn't attend my presentation today about Open Sourcing Joule for Consultants with MCP Server at #SITMUC you can download here my presentation:
raw.githubusercontent.com/marianfoo/ma...

Agenda of the SAP Inside Track Munich 2025 - http://sitmuc.de/2025-1/

Can't join #sitMUC 2025 on site? Join the MS Teams Stream at teams.microsoft.com/meet/3542917... - Agenda at sitmuc.de/2025-1/ #SAP #SAPCommunity

SAP #AI #ABAP

ABAP: Now is the perfect time to start using abapGit and GitHub Its never been a better time to start using abapGit and GitHub for ABAP development, below is my list of the most important reasons for usage, Transparency Put your ABAP code on GitHub, and your entir...

Now is the perfect time to start using abapGit and GitHub #ABAP #SAP #GitHub #abapGit www.linkedin.com/pulse/abap-n...

has anyone created a CDS View editor for SAP GUI yet? ie using cl_gui_textedit #ABAP #SAP

it looks like a promptfluencer 🤪

yea, the agents are clever enough to act on feedback provided by the linter

and act on unit test results too

#ABAP

Agentic ABAP AI should be off stack? Back in the SAP TechEd 2023 Executive Keynote, SAP demonstrated the ability to have an AI generate objects and "and of cause, this is all written to ABAP transports". And I was like, nah, then we need...

Check out my latest article: Agentic ABAP AI should be off stack? #ABAP www.linkedin.com/pulse/agenti... #ABAP

SAP really needs to create more transparency as to what is exactly released on which version, and what/if there are changes

This is Flemming, he happily wears signs as a champ. 12/10

Sustainable + scalable + isolated ABAP Continuous Integration GitHub introduced hosted runners with 96 vCPU and 384 GB RAM back in April. This should be enough to spin up a S/4 HANA system on GitHub Actions for continuous integration.

www.linkedin.com/pulse/sustai... #ABAP

🤯

I'm sure customers have many enhancements in the worst category, which have had zero problems over the last 10 upgrades. Just looking at the technology(which is what the new whitepaper does), doesnt tell the full story regarding upgrade stability

keep the code at whatever level, just #keepTheCoreMoving towards a nicer setup. Ie. I find it more important to have an overview of what is missing vs. creating wrappers that is basically legacy before they are created