SAP architecture
Quick answer
Around the core sit the gateway (for RFC/external communication), and mechanisms like RFC, BAPI, IDoc and ALE that let SAP talk to other SAP and non-SAP systems, the subject of the architecture and integration modules.
Key takeaways
- On the application layer, user requests are handled by work processes of different types (dialog, background, update, enqueue…
- An SAP system is made of instances, each a set of work processes and memory on a server.
- Presentation layer: what the user sees, SAP GUI or, increasingly, the Fiori web UX in a browser.
- Watch out: Confusing the tiers, presentation is not where business logic runs.
The three tiers
- Presentation layer: what the user sees, SAP GUI or, increasingly, the Fiori web UX in a browser.
- Application layer: one or more application servers running the ABAP (and, in S/4HANA, some Java/BTP) work processes that execute business logic.
- Database layer: the single database holding all data, HANA for S/4HANA, or traditional databases for older systems.
Work processes and the dispatcher
On the application layer, user requests are handled by work processes of different types (dialog, background, update, enqueue, spool) coordinated by a dispatcher. This division is why SAP can serve interactive users and heavy batch jobs on the same system without one starving the other.
Instances and scaling
An SAP system is made of instances, each a set of work processes and memory on a server. You scale by adding application-server instances behind message-server-based load balancing, all sharing one database. This is horizontal scaling of the application tier, much like other enterprise systems.
Integration components
Around the core sit the gateway (for RFC/external communication), and mechanisms like RFC, BAPI, IDoc and ALE that let SAP talk to other SAP and non-SAP systems, the subject of the architecture and integration modules.
Common pitfalls
- Confusing the tiers, presentation is not where business logic runs.
- Ignoring work-process types, misconfigured ratios cause bottlenecks.
- Assuming one server, production systems are multi-instance.
Want to learn this properly?
Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.
Check your understanding
Which statement is true of SAP architecture?
- A. This division is why SAP can serve interactive users and heavy batch jobs on the same system without one…
- B. Conditional logic, IF, CASE and logical expressions, lets ABAP make decisions.
- C. The vocabulary of SAP, in plain language.
Show answer
A. This division is why SAP can serve interactive users and heavy batch jobs on the same system without one…
Covered in the “Work processes and the dispatcher” section of this lesson.
Which of these also applies to SAP architecture?
- A. Wrong tool for the integration style.
- B. An SAP system is made of instances, each a set of work processes and memory on a server.
- C. Cramming without hands-on skill.
Show answer
B. An SAP system is made of instances, each a set of work processes and memory on a server.
Covered in the “Instances and scaling” section of this lesson.
Which part of the Learn SAP curriculum covers SAP architecture?
- A. Getting started
- B. SAP projects
- C. SAP glossary
Show answer
A. Getting started
This lesson sits in the Getting started section of the Learn SAP course.