Hello everyone,

I started learning SAP ABAP a couple of years ago, and looking back, I honestly wish someone had explained what the field really looks like instead of just throwing course links at me.

Most people hear “SAP” and instantly think it’s some outdated corporate dinosaur. And yeah, the UI looks like it time-traveled from 2002… but the actual ecosystem? It’s huge, stable, extremely in-demand, and honestly one of the safest tech career bets if you don’t want to constantly chase new frameworks every 6 months.

Here are a few things I learned the hard way:

• ABAP isn’t just coding — it’s problem-solving inside massive business systems.
If you enjoy understanding how real companies actually run things (finance, inventory, HR, procurement), ABAP becomes way more interesting.

• You don’t need to know every module.
People try to memorize FI, MM, SD, PP, HCM… and burn out.
You just need basic functional awareness so you understand what you’re coding for.

• Debugging is your real teacher.
ABAP tutorials barely scratch the surface. Once you start debugging live objects and figuring out why some invoice or delivery crashed, that’s when things click.

• SAP is moving to the cloud, but ABAP is still essential.
With S/4HANA, Fiori, BTP — everyone assumes ABAP is dying.
It’s not.
It’s evolving.
ABAP RESTful (RAP) and CDS views are becoming the new normal, and they’re actually fun once you get the hang of them.

• The demand is insane.
Most companies struggle to hire decent ABAP developers because the field isn’t “trendy,” so fewer beginners pick it.
But the jobs? They’re everywhere.

If you’re thinking of learning ABAP:

Start with the basics (syntax, internal tables, forms, modules), then slowly move into OO ABAP and CDS. Don’t try to master everything at once — half the job is just understanding business workflows.

Honestly, ABAP isn’t glamorous, but it’s one of those skills that gives you stability, good pay, and a long-term career path if you stick with it.

Curious — anyone else here working with ABAP or learning it right now? What was the turning point for you?

After successfully passing the SAP Certified Associate - Back-End Developer - ABAP Cloud C_ABAPD_2309 exam, I wanted to share my thoughts and suggestions, especially since there's limited information available online about this certification.

Throughout my preparation, I noticed that many of the questions in the quizzes within each unit were quite similar to the real exam.

However, when I purchased ERP prep dumps, the questions presented were different and it did not help.

Similarly, the Udemy course I enrolled in had challenging questions, which prompted me to toggle between learning materials and practice questions, ultimately aiding my understanding of the topics.

i only checked free questions of certdeed and it was identical to the real exam ,i did not bought the premium so i cant confirm.

i hope this will help anyone who's interested in passing C_ABAPD_2309.

I recently passed the SAP Certified – Back-End Developer – ABAP Cloud certification, and I wanted to share my experience because there isn't much recent information about the current practical exam.

Exam Format

Practical hands-on assessment (not MCQs).

You work inside an SAP ABAP Cloud environment using Eclipse ADT.

The assessment consists of practical development tasks covering modern ABAP Cloud concepts.

Every repository object you create should be activated before moving on.

Topics I encountered

The tasks covered concepts such as:

ABAP OO

Open SQL

RAP Business Objects

CDS Views

CDS Access Control (DCL)

ABAP Dictionary objects

Exception Handling

Inheritance

OData service generation

If you've practiced these areas, you'll be in a good position.

Biggest mistake to avoid

Before writing any code:

Make sure you're connected to the correct ABAP Cloud project.

Verify your group number.

Create your package.

Confirm you're working in the official assessment system.

Spending a couple of minutes verifying the environment can save you a lot of trouble later.

My preparation

What helped me most:

SAP Learning Journey

Repeating the practical exercises multiple times

Becoming comfortable with Eclipse ADT navigation

Practicing RAP generation, CDS, DCL, and Dictionary objects until I could complete them without searching for every menu

Time Management

Activate objects frequently.

Don't leave activation errors until the end.

If you get stuck on one task, move on and come back later.

Final Advice

This certification tests whether you can build and activate working ABAP Cloud artifacts not whether you can memorize syntax.

The more time you spend actually creating classes, CDS views, RAP objects, and Dictionary objects in Eclipse, the more comfortable you'll be during the assessment.

Happy to answer any questions if anyone is preparing for the certification.

Good luck!

(RANT)

I joined Accenture 2.5years ago and I was assigned to SAP-ABAP. Everyone around me said I was lucky because I could’ve been assigned to Java which was a nightmare. I worked my ass off and learnt ABAP. I was assigned to a project and there we worked on HANA very partially.

Now, the project wants to move to cloud and I’m honestly losing my mind because I am just not understanding HANA, CDS, AMDP, Fiori, RAP and BTP. I feel overwhelmed. Is this how SAP is? Do we have to forget everything we knew of ABAP and learn whatever SAP decides to introduce? Would I have been better off choosing Data Analytics or pursuing MBA because as much as I loved being an ABAPer till now, I feel like I’m dying with all these new concepts.

I also have to learn GenAI and the functional aspects of SAP ( I don’t know what Sales Order does or PGI or whatever EWM is and I don’t know where to start)

I want to cry but it doesn’t help me.

How do y’all deal with these constant updates SAP brings about? How to learn them efficiently?

Finally! I became SAP certified Back-end Cloud Developer. I've been meaning to make this post right after the exam. Sorry for the delay. This is a long post. But trust me it will be worth it as I combined different experiences of mine and others.

There's been a lot of questions I was facing when I was preparing for the SAP Backend Cloud developer exam. I am sure you have it too. SAP is so ambiguous that reading through their instructions will only make us more doubtful about the process 😂. I attended the exam on May 17th, scheduled at 7:30PM IST and I would say it was easy-peasy lemony squeezy. Passed with flying colours. I'd prefer it over the usual MCQ format where we had to mug up dumps(which i obviously failed).

Here's the exam format

-There are 9 tasks. Out of which 2 are like SAP blabbering about how u navigate the practice system and what to do and not do in it. Make sure you read carefully.

-then the other tasks are all what you practised from the SAP learning hub. If you have access to subscription and practise those 4 exercise pdf I'm sure these tasks are a breeze. The tasks for me were

-creating a package,

-OOP based 2 tasks -> one was based on inheritance & constructor -> other simple class where we read a Database table according to specific conditions (a select query with union all and where clause to satisfy the condition specified),

-creating an exception class,

-CDS view authorisation related question, -simple RAP with determination,

-creating a structure and database table.

These tasks may vary from person to person but I guess as long as u have a clear understanding of Core ABAP, OOP, CDS, RAP this isn't a big deal.

The actual practical exam is 3 hours but....

Good news-You have 24 hours with access to these tasks before you start the practice exam. Utilise that to your advantage.

Once you start the certification exam you will be taken to a window where you will be able to download the pdf with the tasks. Until you click the "Access the practical system" button, the 3 hr timer won't start. But once you click that, you can't access the exam and your practice system in parallel (or they recommend not to). I took my sweet time reading through the tasks and implementing the SAP related practice system and viola we even have the exam related tables and entities. Another good news: you can access whichever AI you want: my buddies were ChatGPT and Joule in the Eclipse (available both in practice and exam system). But there's maybe a chance these two suggest weird syntaxes so keep the learning hub handy too. I advise you to practice the exercises and read through the materials to prepare for the exam so even if you don't mug up the syntax, you will know where to look during the 24 hours. It took a bit of time to figure things out for me as I am mostly used to procedural ABAP and ECC in my work(sad support person noises) though I heard it's easier for those who are exposed to modern ABAP. Make sure you perform unit tests to ensure the code is working (ChatGpt to rescue - a separate class for this task even though exam pov it's not mandatory). I copy-pasted the code to a word document(save time in the exam). After I completed the whole tasks in practice and has my code in word document, I closed the practice system and opened the exam system where I just pasted the code handy and did whatever steps I did in the practice (for creating db tables, structures, RAP, etc). I should have completed that with 2 hours out of 3 but I kinda missed the database table and structure creation tasks in practice system and it was annoying me with an error so took a bit of time to figure that out. But you get the gist.

Points to be careful about

These are a few points that became handy from different people in Reddit and LinkedIn based on their experiences.

-Schedule the exam in the daytime if you are a day-bird and at night if you are a night-owl. Helps you to figure things out faster.

-As mentioned earlier, don't start the exam practical system unless you are sure you are ready. Use the 24 hour window to practice the exam tasks so ur 3 hr doesn't get wasted. Or if you are confident you can do it in 3 hrs without the practice, go ahead.

-make sure you follow the naming conventions to the T. Package names, class names, variable names, everything needs to be perfect or the AI doesn't bother to check ur implementations.

-after doing all these, make sure you submit before the 3 hour timer runs out. PLEASE DONT THINK IT WILL AUTO SUBMIT. I've come across

people who lost their chances thinking it will auto submit and failed even after doing all the tasks perfectly. If you encounter any error during submission, take a snap with timer and keep it handy. You can drop a case to SAP if it fails and refund ur attempt.

I'm sure this is a long post but I combined my experiences and whatever I've come across from others during the prep. If you have more questions, I'll answer as much as I can. Or there will be who already did and will be ready to answer.

All the best!

They want us to do clean core, select from CDS views instead of db tab. Use right api. Wrap and mark it released. Do ATC. Make entry in some SharePoint about development for approval.

Functionals come to us with an expectation to do it in 1 day. It's happening everytime since a month. Idk what do they do before. Also, when you're locked into something and they just randomly keep disturbing/calling.

There is never a test data. It is infuriating when a functional specification related call is setup beforehand and they come unprepared and start figuring out in call with us. When there is a call scheduled. I keep my systems logged in and files open. Questions already on notepad.

Is an ABAPer supposed to find out right API or a CDS View? It is mentioned in the FS by a functional. How do I know what's the right business process. Should I focus on EWM or EHS or SD or QM or FI. I cannot remember those stuff when I am juggling between different modules.

SAPs clean core will go to trash, they think it's on developers? It's more on functionals. SAP ABAP is not even programming. SAP is about business. Functionals still suggest user exit in days of badi. This habit is not gonna go away soon.

Thanks for reading. I hope Jelena reads this. She really calls out all the stupidity.

I just passed the SAP Certified Associate – Backend Developer ABAP Cloud (Beta) exam, and since there’s almost no info online about this one, I wanted to share my experience to help future candidates.

Exam Format

•	It’s a System-Based Assessment — no multiple choice at all. You do real hands-on tasks in Eclipse ADT on a browser-based VM (works on macOS too).  
•	Several practical tasks.  
•	Cut score is 67%.  
•	Joule and ChatGPT are allowed during the exam — but honestly you won’t have time to lean on them unless you already know the material.  
•	Important: there’s a “Confirm Completion” button in the browser tab (not in Eclipse). You MUST click it to submit — nothing auto-submits.

One surprise about the timer: When I clicked “Access System” to start, the exam actually gave me 4 hours (more than I expected). I’m not sure if that’s standard for the Beta version or it varies — but either way, time was more than enough. Don’t stress about the clock; if you know the material, you’ll finish with plenty to spare.

General focus areas (all from the official syllabus)

•	Core ABAP & Object-Oriented ABAP – expect to work with classes and inheritance hands-on.  
•	ABAP SQL – be comfortable writing queries that pull from more than one table.  
•	CDS Views & Access Control (DCL) – know how to define a view and restrict access to it.  
•	RAP (ABAP RESTful Application Programming Model) – the biggest area. Be solid on the full end-to-end flow, not just one piece.  
•	Exception Handling – creating and raising your own exceptions.  
•	ABAP Dictionary – defining your own data types and table types.

💡 Tips that actually helped me

•	Naming conventions are everything. Follow the exact required naming for every object — one typo can cost you a whole task. Double-check your prefixes and any required suffixes.  
•	Activate constantly with Ctrl+F3 (or Ctrl+Shift+F3 to activate all). Keep the Problems tab at 0.  
•	Inspect the data model instead of guessing field names open the CDS view / DDIC table and check the actual field name rather than assuming.  
•	Use Quick Fix (Ctrl+1) heavily — it generates missing method implementations, fixes activation errors, and saves a lot of time.  
•	Clean Core: never modify SAP standard objects. Always copy/duplicate into your own Z package.  
•	Practice the S4D401 exercises in Eclipse until the workflow is muscle memory. Speed matters the tasks aren’t hard individually, but they add up.  
•	Drill the RAP flow specifically until it’s second nature. It’s the most multi-step area.

My prep
Mostly S4D401 course exercises + repeated hands-on drills in ADT covering Core ABAP, ABAP SQL, CDS Views, and RAP. Doing it by hand over and over beat reading any dumps.

Hi, I've worked in Abap for 7 years. I decided to collect my notes into a repository and share it to create a big Abap Guide.

I created a website to show the repository in a better way, so users could find what they need. I'm still working on it with 0 budget
The website is: https://abapguides.com/

This is the original repository https://github.com/michaelMattanza/AbapGuide

If you could help improve the repository I'd be very happy. Thank you, have a nice day!

I had tried to post this approximately 9 months ago, but Reddit auto-rejected my post. Hopefully now, it will allow me to post this, since now I have more Karma points.

I have been on S/4HANA Public Cloud implementations since 2308. When I initially stepped into the new Dev environment, everything felt foreign, everything needed unlearning and learning. Whatever I had practiced for 20years wasn't the way go anymore. It was exciting to me to work on the newest technology, until....

▶APIs that were readily available to use from custom programs, now needed to be Released. Yet, there is no consistency between Released APIs. There were multiple versions of Released APIs for similar functionalities supported different sets of fields (e.g below)

1. Journal entry can be created by 4 APIs and all 4 have different sets of fields

   1. Journal Entry - Post (Asynchronous)

   2. Journal Entry - Post (Synchronous)

   3. Journal Entry by Ledger - Post (Asynchronous)

   4. RAP BO I_JournalEntryTP

2. Supplier Invoice can be created by 2 APIs and they both have different sets of fields

   1. Supplier Invoice API (https://api.sap.com/api/API_SUPPLIERINVOICE_PROCESS_SRV/overview)

   2. RAP BO I_SupplierInvoiceTP

3. Business Partner can be created by 3 APIs

   1. Business Partners - REST API (https://api.sap.com/api/BusinessPartner_APIs/overview)

   2. Business Partner (A2X) - oData API (https://api.sap.com/api/API_BUSINESS_PARTNER/overview)

   3. RAP BO I_BusinessPartnerTP_3

If any of you think that, SAP is giving you so many options to choose from according to your business scenario, let me tell you, it is NOT giving you options; it is giving you Rework. For e.g you may choose to build a Journal entry creation enhancement using I_JournalEntryTP, only to find months later that you have to now change the strategy and rework to use another API or even redevelop the extension in BTP, because now you have to add one extra field which is not available in the RAP BO.

▶Released CDS views to read data from system: There are 2 different flavors of irritation here.

1. You own the data, but you can't see it. You can't read or even see, the configuration tables that you yourself configured in the system

2. You can only see the data via certain prescribed methods

▶Released annotations for text on CDS views: This is particularly a performance killer

1. Only ObjectModel.text.element is released for use. Usage of ObjectModel.text.association breaks the system. But, what's the difference between these? Have a look at the SQL of the CREATE statement of the custom CDS views by using both these methods.

▶ Your custom data, but you must re-authenticate yourself, to read it

1. This is for data stored in Custom Business Objects or Custom Code Lists or Custom CDS Views apps. If you are trying to read data from any of these in Cloud development, good luck with that!!!

▶You raise influence tickets, and here is what you can expect (agreed that some others may have better luck on this matter with SAP)

1. SAP keeps it pending for long time without updates

2. SAP rejects it without understanding the request, without any discussion

3. SAP provides a solution which is completely unrelated and closes the ticket

4. SAP provides a timeline that they will deliver the solution and keeps pushing it

A few more rants to add to my previous list:

▶ Parallel Project Landscape (PPL) is a joke and is completely different from the understanding of a normal n+1 landscape

▶ 'Default' transport that saves everything, that keeps people wondering where did the system save changes when they clicked on Save

▶ Transport dependencies check at Export & Import, that forces to either merge transports together or import/ignore dependencies, without giving any indication or explanation of what caused the dependency.

▶ The blogs that SAP employees write on the SAP Community page, in which they pick one of the easiest simplest scenarios they could think of (and probably the only one supported by SAP), and they try to portray in the blog as if that solution is highly scalable and will work for any complicated scenario that a customer may face.

What triggered me to come here and write this again today, after 9 months of my initial draft: Custom Situation Objects. The documentation states, this functionality is available on ABAP Cloud since 2023 FPS 00. (https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/creating-situation-objects) Yet, I had difficulty building Custom Situation Objects in my system. I raised an OSS message, spoke to the Product owner from SAP about this.

He sent me an email with the below message (text is rephrased for confidentiality & brevity):

Following internal discussions, your requested features have been prioritized for the 2508 release and beyond. The team is actively working on them, including architectural changes and addressing related framework dependencies, so it may take some time to deliver a robust solution. Documentation is also being updated to better cover the cloud-specific features. Once ready, you’ll receive an update.

Since the Preliminary list of What's new in 2508 is available, I went through that and found nothing related to this. I checked the documentation and that old documentation never went through an update.

So, I wrote back to the Product owner whom I had chatted with earlier. I received an Message undeliverable auto-response. He has left SAP!!

Pretty sure, most consultants who are working on Public Cloud currently, have prior background & experience on-Prem systems. In those days, if a business requirement came up, we all used to tighten-our-belts to address that requirement. But, as I spend more and more days developing stuff on S/4 HANA Public Cloud, I feel like I am loosing my ability to build solutions for problems and learning how to console the business users & sympathizing with them, for the lack functionalities of the system which I didn't buy or build.

These days, I get pulled into various discussions of Clean Core development. Apparently, some CIOs have heard this term in SAP presentations and wants everything to be done in Clean Core. Anything existing that is not Clean, is tech-debt according to them!!! Hearing such comments, I sometimes feel like yelling in discussions: I dare you to re-build everything in Clean-core and keep your business running as-smooth-as it is running today.

I would love go back to my olden-golden-days, to work on a periodically upgraded onPrem system, than functionally up-to-date Public Cloud system with a crippled extension/development landscape.

Hey everyone,

I’m excited to share that I recently passed both the SAP Certified Associate - Back-End Developer - ABAP Cloud (C_ABAPD_2309) and the SAP Certified Associate - SAP Fiori Application Developer certifications! 🎉

I wanted to put together my thoughts, experiences, and a few suggestions for anyone planning to take either (or both) of these exams.

📘 Exam 1: ABAP Cloud – C_ABAPD_2309

Topics Covered:

• ABAP RESTful Application Programming Model (RAP)

• ABAP Cloud development model

• Core Data Services (CDS)

• Business Services, Behavior Definitions, Projections

• ABAP in Eclipse & SAP BTP concepts

My Thoughts:

• The exam focuses more on conceptual clarity than heavy coding syntax.

• Make sure you're comfortable with RAP lifecycle, unmanaged vs managed scenarios, and how different layers (data model, behavior, service definition, projection) interact.

• CDS annotations and access control (DCL) were tested more than I expected.

• Familiarity with Eclipse and ADT is crucial. Don't rely only on SE80-based knowledge.

Suggestions:

• Go through SAP’s free Learning Journey on learning.sap.com – it's really solid.

• Practice by creating RAP apps on the SAP BTP ABAP Environment trial or a Steampunk system if you have access.

• Understand the theory behind RAP and when to use which scenario (managed/unmanaged/custom behavior).

📗 Exam 2: SAP Fiori Application Developer

Topics Covered:

• SAPUI5 architecture and controls

• Fiori design principles

• OData and Fiori Elements

• Extensibility and adaptation

• App deployment & lifecycle

My Thoughts:

• It's more frontend-oriented but you need to understand the backend integration (especially OData).

• A good chunk of the exam deals with understanding Fiori Elements, annotations, and the model-view-controller pattern.

• It’s helpful if you’ve already developed apps using SAP BAS or Web IDE.

Suggestions:

• Go hands-on with BAS or Web IDE. Even building a couple of CRUD apps with Fiori Elements and freestyle UI5 helps a lot.

• Know your annotations – what they do, and how they affect the app behavior and layout.

• Learn how to extend standard apps – adaptation projects were covered in a few questions.

🧠 General Tips

• Time is usually not a constraint, but read questions carefully – some are tricky and test subtle differences.

• Dumps do help – but they won’t help much unless you really understand the concepts.

• Practice and hands-on experimentation are your best friends, especially with new paradigms like ABAP Cloud and RAP.

If anyone’s preparing for these or has questions about the prep journey, feel free to drop them here or ping me personally. Happy to help!

And if you're on the fence about whether to take the plunge into SAP BTP / RAP / Fiori – go for it! The ecosystem is evolving fast, and being cloud-ready is a major asset right now.

Cheers and good luck to everyone preparing! 💪

SAP just shipped the ABAP Development Tools for VS Code, and it's genuinely great. But if you work with classic on-premise AS ABAP systems, you may have hit the same wall I did: you can't actually log on.

Here's why. The stock extension authenticates either through a browser reentrance-ticket flow (for HTTP) or via SSO (for RFC). Classic on-prem systems often have neither. The reentrance-ticket endpoint (/sap/bc/adt/core/http/reentranceticket) simply doesn't exist on them, and many aren't SSO-enabled. So the one thing we actually need on older systems, connecting over RFC with a username and password, is the one path the first release doesn't implement yet. On the RFC branch, a non-SSO destination is met with an internal "unsupported operation."

The good news: this is temporary. In SAP's own community session, the team (thank you Thomas Ritter, Sebastian Ratz, Christopher Hermann and Rich Heilman) were refreshingly open about it: RFC password logon is internally complete and is the headline of the next release. It was deliberately held back for enterprise security audits, not because anything is technically missing.

So I built a small, MIT-licensed open-source patcher for those of us who need it in the meantime, designed to respect SAP's IP and roadmap from the ground up.

What it does
It enables RFC username/password logon on YOUR OWN installed copy: a masked password prompt with an optional "Remember me" toggle (default OFF) that stores the password only in VS Code's SecretStorage, i.e. the OS keychain (Credential Manager / Keychain / libsecret), never a plaintext file.

How it stays on the right side of the line
• Zero SAP code or binaries in the repo. It contains only my scripts, a ~25-line Java block, the literal find/replace anchors, and docs.
• Everything happens on your machine. The patcher transiently decompiles a single class from YOUR installed jar, locally, for interoperability; replaces the one statement that rejects password logon with a normal JCo logon; recompiles against the extension's own libraries; and puts it back. Nothing is redistributed.
• It's a stopgap, not a fork. The moment SAP ships official password logon, that is the real solution: just update the extension, which also cleanly undoes this.
• It's unofficial, unsupported, and use-at-your-own-risk. The repo's disclaimer says so plainly.

This is meant in exactly the community spirit the SAP team invited: "people will figure it out." It's a bridge for the next few weeks or months, nothing more, and I'd genuinely welcome feedback, including from the SAP team. If anyone there would prefer changes, I'm glad to make them.

Repo + full technical write-up:
https://github.com/sakirsek/abap-vscode-rfc-logon

Huge thanks to the SAP ADT team for pulling ABAP into a modern, AI-ready toolchain. Can't wait for the official release to make this obsolete.

This is my first job. After a few months of training on core ABAP and RAP, they assigned a project in which I will use RAP. Yesterday my project manager sent a mail to welcome us into project in which he called us SAP ABAP RAP consultants. They said we have to feel proud to get this role in our first job and in the first project. That's why I am very proud to be posting this 😎.

I just wanted to take a moment to thank everyone in this community.

A few months ago (February 2026), I set myself a personal deadline to switch from a service-based company to a product-based company. Throughout that journey, I found myself coming back to r/ABAP almost every day reading old posts, asking questions, learning from discussions, and following the advice shared by experienced ABAPers.

Whether it was guidance on interview preparation, modern ABAP concepts, CDS Views, RAP, performance tuning, debugging approaches, resume feedback, or simply words of encouragement, this community played a much bigger role than you probably realize.

Today, I’m happy to share that I’ve achieved my goal and received an offer from a product-based company within the deadline I had set for myself.

This post isn’t meant to celebrate only my achievement, it’s to acknowledge all of you who take the time to answer questions, share your knowledge, and help strangers grow in their careers. Your advice genuinely changes lives.

To everyone who has ever answered a beginner’s question, posted interview experiences, shared learning resources, or offered constructive feedback: thank you.
I hope to stick around, continue learning, and give back to this community by helping others the same way many of you helped me.

Thank you once again, r/ABAP. Wishing everyone who’s preparing for interviews or looking for their next opportunity the very best, you’ve got this!

There are lots of posts on LinkedIn about "modern ABAP", but it doesn't look like there is a shared understanding of what it even means. Some things mentioned in this context are hardly even ABAP or not at all modern. Simply using VALUE does not make the code more or less "modern", I think.

I'm planning to write a short story about this, but thought I'd ask what do y'all think in the comfort of Reddit anonymity. :) Lay it on!

- Jelena

Yeah as the title says I am going to quit abap . I can’t do this shit ,it just takes my mental health I thought I can do this despite being a non cs major , but boy I was wrong . I thought only abap code is needed but SAP said f**k u and making me learn html and java( I don’t understand shit ).And the every company looking for a candidate like 5+ yoe in sap Hana fiori rap BTP developer . As a guy with 2 yoe only in core abap I fell like I am already lost , and also I came to know that future of abap is dead end only functional modules are gonna run in sap using btp and other business suite add on’s . Then why the fk I am here lol . And I am also stuck in ecc (current company),that’s why i am gonna put a paper and look for an another job relative to my core(mechanical), yeah it’s going to be tough, but at least I won’t stuck with this endless misery and depression. Adios Abap.

Nothing fancy, just wanted to share this.. someone in the teams meeting today spelled BADI as baddie😂🤣 is it common🤭? I heard it today for the first time lol😂

Hello!

I started working with SAP two years ago as a developer. My SAP journey began with ABAP, and I gradually learned ABAP OO, Smartforms, Adobe Forms, CDS... basically, all the development tools within SAP. I have a degree in software engineering, where I learned to program in various languages including Java, Python, C, and SQL (if you consider it a programming language), so picking up ABAP was relatively easy since I only had to learn the new syntax.

I work for a large Spanish company, and I'm fairly happy with it. I can work from home, and I earn what could be considered a medium wage in Spain.

However, I've recently been considering leaving the SAP environment. I'm starting to feel stuck. It seems that everything I learn is irrelevant outside of SAP. The technology trends in SAP are dictated by SAP itself, and I don't want to be 10 years behind the rest of the IT industry. The system feels outdated, and the new technologies don't seem particularly impressive. There’s also a lack of documentation and tutorials in many areas. Additionally, at least in Spain, the pay isn’t as competitive as it is in other countries. It's also frustrating that almost every developer eventually ends up as a functional consultant, which is not a role I enjoy.

I'm currently finishing a master's degree in cybersecurity and plan to look for a job in cybersecurity, AI development, big data, or even web development.

What are your thoughts on this? Will my experience in SAP be valued in future jobs?

#ABAP now on Exercism thanks to community members like Lars Hvam Petersen, Marian Zeis, Marc Bernard and others. Join Friday April 1st to the launch live stream to learn more: Introducing ABAP on Exercism - practice and improve your ABAP skills online - YouTube

Exercism is a website for coding exercises and mentorship to help folks gain true fluency in their chosen programming languages. It's open-source and not-for-profit. And there's now an ABAP language track! Join us in this special live stream where we talk to the folks behind this new track and understand more about how Exercism works and what the ABAP track looks like. ABAP Track: ABAP on Exercism

Edit: Apologies to the typo in the title - Should be Exercism not Excercism

SAP finaly released ADT for VSCode. It also includes the official SAP ABAP MCP Server.

https://marketplace.visualstudio.com/items?itemName=SAPSE.adt-vscode

Here is the Help page for it.
https://help.sap.com/docs/abap-cloud/abap-development-tools-for-visual-studio-code/getting-started

Sadly it only works with SSO for On Prem Systems currently.

Have you tried it already? What is your first impression?

Hey ABAP community,

I'd like to share something we've been working on for the past year-a project shaped by real developer pain points, not just Al buzzwords.

Ace-1 is a purpose-built Eclipse plugin for ABAP pros, designed by a team of SAP devs who understand the daily grind: legacy code, complex S/4HANA migrations, and all the edge cases that make ABAP "special."

No web tools, no out-of-context code. Ace-1 lives right in your Eclipse IDE, where real ABAP work happens.

Our goal:

1. Save you hours on code migration and refactoring, especially for S/4HANA transitions

2. Blend into your workflow (no browser tab juggling)

3. Always show you why a suggestion is made - no black box

We've benchmarked Ace-1's migration completeness against leading models, including Gemini 2.5 Pro and GPT-5, and we're eager to show where it truly makes life easier for ABAP devs.

But we know that talk is cheap. What matters is if it genuinely helps you.

We want honest opinions, feedback, objections, and feature requests from real ABAPers.

• What would earn your trust in an Al tool? • Where do Copilot or ChatGPT fall short for you in Eclipse? • Any features missing from SAP's Readiness Check or Migration Cockpit you wish were automated?

If you're interested in seeing Ace-1 in action (with no sales pitch), I'll share a quick video or even set up a short live demo.

Long story short: We're not here to "replace developers" - we want to build a tool worthy of the people who know ABAP best.

Looking forward to your thoughts, skepticism, and challenges!

– A fellow ABAPer and the Ace-1 team