Learning ABAP is not particularly difficult if you know other programming languages.
Let ABAP and ABAP OO be distinguished first. ABAP is an old, procedural language, and ABAP OO is its extension to classes.
ABAP has the usual control structures, such as if-then-else or loop. Its syntax is a bit used (I found the particularly annoying part about putting or missing spaces in front of the brackets), but definitely doable. There are some structures that you donβt find in C ++ and C #, for example, grouping functions in functional groups that have their own local variables, so if you call something that is in another function group, everything can become messy. But overall, if you understand the scope and namespace, this should not be a problem.
I found ABAP OO quite simple compared to ABAP because it basically only added classes / packages that I knew from C ++ / C # before.
To get to know them, I would suggest the following for someone who is new to ABAP and wants to learn about DEEP (see more functional aspects below):
-Prepare yourself a proper ABAP book, for example. something from SAP Press
-Don't read it yet
-start with a web course or a simple book, on the principle of "learn ABAP in 24 hours"
standard coding
- if you code, you will inevitably ask yourself: "How does it work and what?" is PERFORM using pass-by-reference or pass-by-value to pass arguments? "See these questions in your ABAP book.
- perhaps in a few months you will be quite familiar with the language that you can read in the book without falling asleep
Just a caution: itβs good to know ABAP programming, but even if you donβt think that other SAP technologies consist of (for example, workflows or PDF forms that have nothing to do with ABAP), there are still many structures that differ in their logic . So, even if you know C ++, knowing the Win32 framework does not mean that you can start pushing code under UNIX, knowing that ABAP does not mean that you can work productively in a specific module right away. Unfortunately, SAP modules tend to use different structures, some of which are more commonly used than others.
If you do not want to have a deep knowledge of ABAP, but want to understand SAP modules functionally, you should consider using the products themselves in addition to programming and studying functional aspects.
I am afraid that there really is no quick way to find out how SAP World works; you need a little technical, functional and architectural knowledge for this, and since the modules are so different from all these aspects, it takes a long time until you can get an extensive overview of everything. But even with technical and some functional knowledge, you would be on the way; as the saying goes, "at SAP no one expects you to know everything."