what is presentation layer in sap abap

Sap R/3 Architecture Tutorial

What is SAP R/3?

SAP R/3 is a 3 tier architecture consisting of 3 layers

• Presentation
• Application

In simple words, it’s a client server architecture.

• R signifies Real-time system
• 3 represents – 3-tier architecture.

User’s PC:- Users can access SAP system in two ways:-

• Through SAP GUI
• Through Web browser

It’s called front-end. Only the front-end is installed in the user’s PC not the application/database servers.

Front-end takes the user’s requests to database server and application servers.

Application Servers: – Application server is built to process business-logic. This workload is distributed among multiple application servers. With multiple application servers, the user can get the output more quickly.

Application server exists at a remote a location as compared to the location of the user PC.

Database Server: – Database server stores and retrieves data as per SQL queries generated by ABAP and Java applications.

Database and Application may exist on the same or different physical location.

Understanding different SAP layers

Presentation Layer

The Presentation Layer contains the software components that make up the SAPgui (graphical user interface). This layer is the interface between the R/3 System and its users. The R/3 System uses the SAPgui to provide an intuitive graphical user interface for entering and displaying data.

The presentation layer sends the user’s input to the application server, and receives data for display from it. While a SAPgui component is running, it remains linked to a user’s terminal session in the R/3 System.

Application Layer

The Application Layer consists of one or more application servers and a message server. Each application server contains a set of services used to run the R/3 System. Theoretically, you only need one application server to run an R/3 System. In practice, the services are distributed across more than one application server. The message server is responsible for communication between the application servers. It passes requests from one application server to another within the system. It also contains information about application server groups and the current load balancing within them. It uses this information to assign an appropriate server when a user logs onto the system.

Database Layer:

The Database Layer consists of a central database system containing all of the data in the R/3 System. The database system has two components – the database management system (DBMS), and the database itself. SAP has manufactured its own database named Hana but is compatible with all major databases such as Oracle. All R/3 data is stored in the database. For example, the database contains the control and customizing data that determine how your R/3 System runs. It also contains the program code for your applications. Applications consist of program code, screen definitions, menus, function modules, and various other components. These are stored in a special section of the database called the R/3 Repository, and are accordingly called repository objects. R/3 repository, objects are used in ABAP workbench.

Understanding the components of SAP R/3 3-tier Architecture

• Message Server: It handles communication between distributed Dispatchers in ABAP system .
• Dispatcher Queue: Various work process types are stored in this queue.
• Dispatcher: It distributes requests to the work processes.
• Gateway: It enables communication between SAP system and between SAP system and external systems .

• Memory-pipes: It enables communication between ICM and ABAP work processes.
• Message Server: It handles java dispatchers and server processes. It enables communication within java runtime environment.
• Enqueue Server: It handles logical locks that are set by the executed Java application program in a server process.
• Central Services: Java cluster requires a special instance of the central services for managing locks and transmitting messages and data. Java cluster is a set of processes that work together to build the reliable system. Instance is group of resources such as memory, work processes and so on.
• Java Dispatcher: It receives the client requests and forwards to the server process .
• SDM: Software Deployment Manager is used to install J2EE components.
• Java Server Processes: It can processes a large number of requests simultaneously.
• Threading: Multiple Processes executes separately in the background, this concept is called threading.
• ICM: It enables communication between SAP system and HTTP, HTTPS, SMTP protocol. It means by entering system URL in the browser you can access SAP from browser also.

One more component is JCO. JCO is used to handle communication between java dispatcher and ABAP dispatcher when system is configured as ABAP+Java.

How the SAP Logon Process works?

Step 1) Once a user clicks on the SAP system from GUI, the user request is forwarded to Dispatcher.

Step 2) Request is stored in Request queues first. Dispatcher follows First in First out rule. It will find free work process and if available will be assigned.

Step 3) As per user request, particular work process is assigned to user. For example, when user login to the system then Dialog work process is assigned to the user. If user runs a report in background then background work process is assigned to the user. When some modifications are done at database level then update workprocess is assigned. So as per user’s action workprocess is assigned.

Step 4) Once user is assigned the dialog workprocess then user authorizations, user’s current setting are rolled in to work-process in shared memory to access user’s data. Once dialog step is executed then user’s data is rolled out from workprocess. Thus shared memory will be cleaned and other user’s data can be saved in shared memory area. Dialog step means the screen movements. In a transaction, when a users jumps from one screen to other the process is called a dialog step.

Step 5) First work process will find the data in the buffer. If it finds data in buffer then there is no need to retrieve data from database. Thus response time is improved and this process is called hit. If it does not find the data in buffer then it will find the data in database and this process is called miss. Hit ratio should be always higher than miss ratio. It improves the performance of system .

Step 6) Other requested data is queried from the database and once the process is complete, the result is sent back to GUI via dispatcher.

Step 7) At the end user’s data is removed from shared memory so the memory will be available to other users. This process is called roll-out.

You Might Like:

• SAP Learning Hub
• SAP Full Form
• SAP Working
• History of SAP
• SAP SuccessFactors
• SAP Business Suite
• SAP Business One
• SAP Interview Corner

SAP R/3 Architecture

• Introduction to SAP R/3 Architecture

SAP R/3 (Systems, Applications, and Products in Data Processing) is an enterprise resource planning (ERP) software system developed by the German company SAP SE. It plays a vital role in managing business processes and resources efficiently. The architecture of SAP R/3 is designed to provide a structured framework for organizations to manage their data, applications, and user interfaces. In this article, we will explore the definition and various components of SAP R/3 architecture.

Table of Content

Definition of SAP R/3 Architecture

Sap r3 meaning, layers of sap r/3 architecture, why r/3 architecture, componenets of sap r/3 architecture:, sap r/3 architecture work processes, what is the presentation layer in sap r/3 architecture, what is the application layer in sap r/3 architecture, what is the database layer in sap r/3 architecture.

SAP R/3 architecture is a multi-tiered structure that comprises three main layers: the Presentation Layer, the Application Layer, and the Database Layer. This architectural model enables organizations to integrate and streamline their business processes and data management effectively. with SAP R/3, we are moving our resources from mainframe computing to the three-tier architecture of the presentation, Application, and database layer.

SAP R/3 Architecture diagram

SAP R3, often referred to as SAP R/3, SAP stands for Systems, Applications, and Products in Data Processing , and R stands for Real-Time Data Processing . The “3” in R/3 represents the three-tier architecture , consisting of the Presentation Layer, Application Layer, and Database Layer, which collectively form the foundation of SAP R/3 systems.

• The Presentation Layer: The Presentation Layer is the topmost tier in the SAP R/3 architecture and is responsible for providing user interfaces for interacting with the system. It serves as the gateway for users to access and interact with SAP applications.Users interact with the system through graphical user interfaces (GUI) or web interfaces. These interfaces make it easy for users to input data, view reports, and navigate the system. The Presentation Layer ensures a user-friendly experience, offering features like drag-and-drop functionality and real-time data display.
• The Application Layer: The Application Layer is the middle tier of the SAP R/3 architecture. It houses the business logic and application programs that execute various business processes. This layer is responsible for processing user requests, performing data validation, and executing application logic. It ensures that business processes run smoothly and efficiently.Application servers handle the communication between the Presentation Layer and the Database Layer. This separation of layers improves system performance and scalability.
• The Database Layer: The Database Layer is the lowest tier in the SAP R/3 architecture and is responsible for storing and managing data. It stores all the business data, configuration settings, and user information.Databases like SAP HANA, Oracle, or Microsoft SQL Server are commonly used in the Database Layer. They are designed to handle large volumes of data efficiently and ensure data integrity.The Application Layer interacts with the Database Layer to retrieve, update, and manage data as needed to support business operations.

SAP R/3 architecture offers several advantages, some of them are mentioned below:

• Scalability: The multi-tiered architecture allows organizations to scale individual layers independently, providing flexibility and accommodating growing business needs.
• Performance: T he separation of layers optimizes system performance, as the workload is distributed among Presentation, Application, and Database Layers.
• Reliability : The architecture’s modularity ensures that a failure in one layer does not necessarily affect the others, improving system reliability.
• Security: Security measures can be implemented at each layer, enhancing data protection and system access control.
• Customization : Organizations can tailor the SAP R/3 system to their specific business requirements, thanks to the flexibility of the architecture.
• Message server: It is responsible for managing the conversation between different dispatchers in SAP System.
• Gateway: It is responsible for communication between SAP systems and different external systems.
• Dispatcher : It distributes the request to the different work processes.
• Dispatcher Queue : Various work process types are stored in this queue.

Within the Application Layer, SAP R/3 architecture employs the concept of work processes. Work processes are responsible for executing tasks such as dialog processing, background processing, and update processing. This modular approach allows for efficient multitasking and improved system performance.

The Presentation Layer, often referred to as the front-end layer, is a crucial component of SAP R/3 architecture. It serves as the interface through which users interact with the SAP system. Here, we will explore the Presentation Layer in more detail.

The Purpose of the Presentation Layer in SAP R/3:

• User Interaction : The primary purpose of the Presentation Layer is to provide a user-friendly interface for interacting with SAP applications. This layer acts as the bridge between the user and the underlying SAP system, offering graphical user interfaces (GUI) or web-based interfaces.
• Data Input and Display: Users use the Presentation Layer to input data, view reports, and perform various tasks within the SAP system. It offers a familiar environment for users to enter data, navigate the system, and retrieve information.
• Real-time Feedback: The Presentation Layer is responsible for displaying real-time data to users. Whether it’s monitoring production processes, sales figures, or inventory levels, users can access up-to-date information through this layer.
• Customization: Users can often customize their interface to suit their specific needs and preferences. This personalization can include layout changes, favorite transactions, and user-specific settings.

The Application Layer is a central and critical component of SAP R/3 architecture. It plays a pivotal role in ensuring the seamless execution of business processes and the overall functionality of the ERP system. Below, we will delve into the purposes and functions of the Application Layer in SAP R/3 architecture.

Purposes of the Application Layer:

• Business Logic Execution: The primary purpose of the Application Layer is to execute the business logic that drives the organization’s operations. This layer houses the application programs responsible for various business processes, from order processing to financial accounting.
• Data Processing and Validation: It manages data processing by validating and processing user requests and transactions. This includes checking data for accuracy, consistency, and integrity to ensure the reliability of business operations.
• User Interaction Handling : The Application Layer is responsible for handling user interactions, such as transaction execution and data retrieval. It processes user requests and ensures that the appropriate data is fetched from the Database Layer for presentation to the user.
• Scalability and Performance Optimization: The Application Layer contributes to system scalability and performance optimization. By distributing the workload across multiple application servers, it ensures that the system can handle a large number of concurrent users and complex business processes efficiently.

The data are stored in the database layer. Every relational database is supported by SAP . No database is provided by SAP. But it works with all RDBMS. One system or computer must have the database layer installed. Oracle and DB2 are the two main databases utilized in SAP deployments.The Database Layer is the lowest tier in the SAP R/3 architecture and is responsible for storing and managing data. It stores all the business data, configuration settings, and user information.Databases like SAP HANA, Oracle, or Microsoft SQL Server are commonly used in the Database Layer. They are designed to handle large volumes of data efficiently and ensure data integrity.The Application Layer interacts with the Database Layer to retrieve, update, and manage data as needed to support business operations.

In conclusion, the Application Layer of SAP R/3 architecture is the heart of the system, where business logic is executed, data is processed, and user interactions are managed. Its purposes and functions are essential for efficient business operations, data management, and system performance. By separating these functions into a dedicated layer, SAP R/3 architecture provides flexibility, scalability, and reliability to organizations seeking to streamline their business processes.

Please Login to comment...

Similar reads.

• Geeks Premier League
• Geeks Premier League 2023
• How to Get a Free SSL Certificate
• Best SSL Certificates Provider in India
• Elon Musk's xAI releases Grok-2 AI assistant
• What is OpenAI SearchGPT? How it works and How to Get it?
• Content Improvement League 2024: From Good To A Great Article

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

Understanding Different Layers of ABAP Application Server Layers

Developed by SAP®, Advanced Business Application Programming (ABAP) is a programming language built for developing applications used on SAP® R/3 system, and executing within the SAP Web Application Server – at application layer. Also, it is used for customization and implementation of SAP® R/3 system.

ABAP encompasses Logical Databases (LDBs) which differentiates database, operating system and applications. ABAP is also used for boosting SAP applications and allows customers to prepare customized reports and interfaces.

Working on ABAP Application Server

The Application Server ABAP offers run time environment; integrated change and transport system (CTS), and Workbench for creating applications in ABAP. It uses a couple of protocols for SAP GUI that are Remote Function Call (RFC) protocol and HTTP/HTTPS/SMTP for Internet. Thus software can be used with web browsers or SAP GUI or some software via. Network.

Components of Application Server ABAP

The main components of Application Server ABAP are divided into different layers. They are:

Presentation Layer: As the name suggests, this layer receives and presents data to the users. This layer comes into play when web browsers act as a user interface to invoke application programs and Internet Connection Framework (ICF) interface to wrap the HTML pages. Web Dynpro ABAP (platform-independent web-based interfaces) and Business Server Pages (BSP, HTML pages) control web browser presentation. In case of MS Windows, Java and Web Browsers (SA GUI), display of user interface happens in windows using Web DynPro technology. Web DynPro, developed by SAP SE, is a web application technology (proprietary) used for server-side business applications development.

Application Layer: This layer serves as a platform for executing application programs. With its kernel made in C/C++, it uses ABAP Objects, ST, JavaScript, and XSLT to provide virtual machines.

Persistence Layer: Persistent data is present in database. Using ABAP programs which employ database interface, containing Native SQL (database-based SQL instructions) interface and Open SQL (part of the Structured Query Language -SQL) interface, database can be accessed.

SAP® ABAP online training

ABAP Programming to manage SQL database and create applications involves both relational database design and object-oriented programming. Hence for professionals who want to enhance their knowledge or get a deep insight about SAP® ABAP programming , considering ABAP online training program from a recognized organization would be a better option. With expert trainers; best study materials, and 24x 7 access to the portal, learning will become easy and ensure 360 degree learning for better understanding of the tool.

Related Posts

Your email address will not be published. Required fields are marked *

Email Address: *

Notice: It seems you have Javascript disabled in your Browser. In order to submit a comment to this post, please write this code along with your comment: 58114dc684d7fbc8b9c4d0b9887bc560

• All Courses
• Practice Tests
• Video Library

• Architecture

SAP Architecture – Detailed Explanation

What is sap, sap 3 tier architecture: different sap layers, 1. presentation layer, 2. application layer, 3. database layer, sap architecture components, how does the sap process work, additional resources.

SAP architecture is a set of principles, patterns and best practices that outline the architecture of an organization’s SAP environment. By using it, organizations can build a more secure and reliable platform for running business processes across their organization. SAP is a software-as-a-service solution, which means it’s cloud-based. This has implications for your SAP architecture. Your users will be accessing SAP via a web browser; they won’t be installing software on their desktops and laptops like they would with desktop applications.

That means you need to think about your SAP architecture beyond the technical components necessary to run SAP itself. You need to think about how to structure your system so that it is easily managed, supported and updated over time while remaining secure and reliable at the same time. This article covers everything you need to know about SAP architecture

SAP is a global leader in providing software solutions that enable organizations to process data efficiently and communicate information effectively. SAP was founded in 1972 and has grown from a small, five-person program development firm to a multinational corporation with more than 105,000 employees worldwide since then. Walldorf, Germany is SAP’s headquarters, where it’s run by more than 100,000 employees worldwide.

Confused about your next job?

SAP stands for “ Systems Application Program .” The SAP acronym is a widely used shorthand term for software, computer programs, and applications that all fall under the umbrella of SAP systems.

Some examples of applications that fall under the SAP acronym are accounting software, inventory management software, database management software and web application software. To be more specific, SAP is a business-to-business (B2B) application development platform which allows organizations to manage and optimize their business processes in order to increase productivity and profitability. By providing organizations with real-time access to critical information from multiple sources, such as financial data, inventory records and customer profiles, SAP systems enable them to effectively manage their operations. By streamlining business processes and reducing operational costs, SAP systems can help companies achieve greater growth and profitability.

The SAP System Architecture includes Presentation, Application, and Database layers. Each of these programmes operates on its own. In contrast, MiniSAP has all the components in one machine. We may distribute the whole system across diverse machines or it may also be on one machine like ours. The database and the application server can be on the same machine if we want to get an idea of the SAP system architecture in greater depth. In addition to these application servers, other applications are run on separate machines. To better grasp the SAP architecture, let’s look at these three elements in more detail.

The SAP System Architecture consists of the Presentation, Application, and Database layers.

• The presentation layer is responsible for the user experience and for making sure that the SAP system is responsive and easy to interact with.
• The presentation layer does not have any knowledge of the underlying data stored in the data layer.
• The data layer holds all the data that is being stored in the SAP system. The data layer is the realm where all the business rules and processes take place.
• The data layer exists between the presentation layer and the application server.
• When you connect to the application server and start to do work, the application server, which is the realm where all the logic happens, knows nothing about the data layer.
• This layer of the architecture is responsible for receiving and parsing data before it can be used by any part of the organization.
• This layer is also responsible for providing data within the correct format for each application.
• The last responsibility of the application layer is to ensure that the data is secure before it is sent to the next layer.
• This layer of architecture is a critical component to the success of your digital transformation. The work process must be carried out by a user who is registered in the system. For this reason, we define the work process as a user of the system. The work process will register itself in the database, and when it is required to create a new record in the system, this is done by the work process. The work process can be created by the system administrator through the SAP system. In the case of the SAP system, this can be done by setting the role of the user to a specific value. What happens when you do this is that the SAP system will create a new user in the database system. This user will register itself in the database, and when the system needs to create a new record, the user can do this. The user will create the work process, and when the system requires the work process to create a new record, the user will create the process.
• The system architecture is what defines how your SAP system is set up.
• If you were setting up a new company, you would choose a system architecture based on the type of business you want to start.
• For example, a manufacturer of motorcycles and scooters would be best served by a system architecture that focuses on production and inventory. A hotel would do best with a system architecture that focuses on customer relations. Once you have chosen the setting for your new company, you need to choose the SAP system architecture. The application and database layers receive information about actions performed on the presentation layer and then query the results. As a result, you can see the results of processing on the presentation layer.

The SAP R/3 3-tier Architecture is a popular application server topology for developing large-scale enterprise applications. With the increased use of web-based technologies and the ever-increasing importance of user experience, application servers are being replaced by web-based applications. However, there are certain situations where the usage of web-based applications is not possible, due to the size of the system, regulatory compliance, or other business reasons. In such cases, the usage of 3-tier application servers is unavoidable. The most common application server topology is the SAP R/3 3-tier Architecture.

• The role of the Message Server is to handle communication between ABAP Dispatchers that are distributed across the system.
• In this Dispatcher queue, process work of several different types is stored.
• Work processes are allocated by the dispatcher.
• Gateway provides access between SAP systems and external systems.
• Each R/3 dialog step is separately executed by ABAP-Work processes.

The following describes the types of work processes:

• An ICM work process can communicate with an ABAP work process via a memory pipe.
• The Java dispatcher and server processes are handled by the Message Server. Within the Java runtime environment, the Message Server enables communication.
• A server process is configured by a Java application program to handle logical locks. The queue server handles them.
• The central services are used to manage locks and transmit messages and data when working in a Java cluster. Java clusters are sets of cooperating processes that create a dependable system. A group of resources, such as memory, work processes, and so on, is known as an instance.
• The Dispatcher handles the incoming client requests and dispatches them to the correct server process.
• To install J2EE components using SDM, you must first download and install Software Deployment Manager.
• A high quantity of requests can be handled by a Java Server Process.
• Threading refers to the method of processing multiple items at once in the background.
• SAP can be accessed from a browser by entering the system’s URL. Because of this, ICM can also be used for communication.

When using the ABAP and Java systems, we use another component called a JCO to handle communication with the ABAP dispatchers. ABP+Java uses Java dispatchers to handle communication.

• The SAP Logon process is the first step of the SAP authorization process. This is a simple process which involves entering the identification number that you were assigned when you created an account with SAP.
• After this, you will be asked to provide your SAP password.
• After you successfully enter your SAP password, you will be sent a confirmation message confirming your successful logon. From here, you will be able to access the main menu of SAP.

Although the process may seem simple at first glance, it can sometimes be challenging to perform correctly. Therefore, it is recommended that users practice logging in before conducting business-critical activities such as signing contracts or performing transactions.

• The Dispatcher listens to user actions such as clicks on links or forms and forwards them to corresponding actions. When the action receives the request, it handles the request and returns the response to the Dispatcher. The Dispatcher forwards the response to the system.
• Once a process is assigned, the dispatcher will check if the resource is available in the Service Request Pool. If it is not, the dispatcher will go ahead and start the process and assign another work process when the work process is available. If the resource is available in the Service Request Pool, the dispatcher will find another process and assign that one and so on.
• The work process is responsible for putting work into the system and delegating it to other processes. Processes can be divided into two categories depending on their priority. These are critical processes which need to be executed immediately. These processes are called high priority. Critical processes and other high-priority processes can be assigned to users. Thus, depending upon user request work process is assigned.
• In the process of work, if a user does some changes in the process and the process is not completed, then the User will get an alert message. In the case of the dialogue step, when a user authorizes the work process, then shared memory will be checked. If any other user’s data is present in shared memory then the process will be stopped and an alert will be displayed.
• Another work process is reading. If there is no data in the buffer then data has to be retrieved from the database to get a response. And this process is called reading. If there is data in the buffer then it has to be removed. And this process is called kill. This process increases the performance of the system. It is very important to keep these work processes in mind while designing your application.
• A dispatcher is a class that receives requests from the GUI and sends the requests to the server. The server receives the request and executes the query and returns the result to the dispatcher which then updates the GUI. A dispatcher can be registered at the startup of the application and it can be unregistered at any time to stop the dispatching. By using this approach, the data is synchronized between the server and the GUI.
• If the shared data is not being used by any other user, it will eventually be evicted from shared memory and the system will have less memory to service other workloads. It is important to monitor data in shared memory for signs of stagnation, because once data is in shared memory it cannot be purged.

SAP architecture is the overall structure of an organization’s IT systems. It describes how these systems are put together, what roles they play, and how they relate to one another. One key goal of SAP architecture is to create a stable foundation that can support future growth. Following the right design patterns can help ensure this. One important aspect of SAP architecture is componentization. Each component should do one thing well, and it should be easy to replace or upgrade if necessary. Ideally, each component should also have a clear interface so that other components can easily interact with it.

When designing an SAP architecture, focus on creating a cohesive whole that works together as a cohesive whole. Another key goal of SAP architecture is to ensure that it scales with the business. As the business grows, so does the need for effective IT solutions. Scaling up or down as needed should be part of the plan from the beginning.

Finally, remember that SAP architecture is more than just technology. It’s about ensuring that all aspects of IT are working together in harmony to deliver maximum value for customers and shareholders alike.

• SAP Interview Questions
• SAP Basis Interview Questions
• SAP Security Interview Questions
• SAP ABAP Interview Questions
• SAP HANA Interview Questions
• SAP Architecture

Previous Post

• Coding Problems

Minimum Spanning Tree – Kruskal Algorithm

System architecture – detailed explanation.

In this topic, we described about the below sections -

• Kernel and Basis Services
• ABAP Workbench
• Presentation Components
• Presentation layer
• Application layer
• Database layer
• RFC Interface
• Internet Communication Manager (ICM)
• ABAP Channels

What are the views of R/3 System?

The R/3 system is the platform for all other applications in the R/3 System. In R/3, R stands for Real-time and 3 stands for 3-tier architecture. The R/3 System can have different set of views in different prospects. The main views among them are -

• Logical view
• Software Oriented View

What is the logical view of R/3 System?

The below diagram represents the logical view of the R/3 system -

The difference between “logical view” and "hardware or software-based view” is, not all the above components assigned to a specific hardware or software unit. The above diagram explains how the R/3 basis system constructs a central platform within the R/3 System. The tasks of three logical components tasks of the R/3 Basis system are described below -

Kernel and Basis Services –

The kernel and basis services is a runtime environment for all R/3 applications (i.e. hardware, operating system, and database specific). The runtime environment is mainly written in C and C++. However, some parts are also written in ABAP.

The tasks of the kernel and basis services are - “running applications”, “user and process administration”, “database access”, “communication” and “system monitoring and administration”.

ABAP Workbench –

The ABAP Workbench is a complete development environment for applications in the ABAP language. We can create, edit, test, and manage application developments using workbench. Workbench is itself written in ABAP and is fully integrated in the R/3 system.

Presentation Components –

The presentation components are responsible for the interaction between the R/3 System and the user.

What is Software Oriented View of R/3 system?

The software-oriented view specifies the different software components (i.e. all the SAPgui components and application servers) that produce R/3 system. The below diagram represents a software-oriented view of the R/3 System.

SAP R/3 system is a multi-tier client-server architecture. The SAP R/3 architecture is basically divided into three layers and those are -

Presentation layer –

Presentation layer is an interface between the R/3 system and its end-users. Presentation layer is a distributed to the workstations of end users. The end users can be client or customer or individual users.

Presentation layer receives the data from the input devices and sends it to the application layer (server) to process the data. And, responsible to receive the processed data from the application layer and sends the same to the devices where the result requires to display.

The data or input can be entered by using the input devices. The input devices can be browsers, mobile devices, font-end GUI systems and so on.

The presentation layer is normally distributed across several presentation servers. The presentation layer analyzes user inputs and transfers these to the application layer.

Application layer –

The application layer is an intermediate layer. This layer process the inputs from the presentation layer and one messaging server. The application layer is implemented using application servers. Application server(s) can be one or multiple. Each Application server can contain either one or multiple services to run an R/3 system.

It communicates to the database layer with the input received from the presentation layer, processes input and sends the results back to the presentation layer. The application layer contains the ABAP runtime environment where the ABAP programs are executed.

All the services are distributed to the more than one application server. Messaging server contains the information about the application groups and load balancing information. Messaging server is responsible for the communication between the existing application servers.

Messaging server is responsible for -

• Passes the requests from one application server to another.
• Assigns appropriate application server when users logged in.

Database layer –

Database layer is layer contains the central database system of all the data in R/3 system. Normally, this database layer installs on the different server due to the security, performance and processing issues.

This layer is responsible for processing the requests from the application layer and sends back the required information. In general, either SQL or ORACLE servers can be used.

All R/3 data stores in the database. Database layer contains two components -

• Database Management Systems

The communication flow happens from the presentation layer to database layer and vice versa. Technical distribution of the system is independent of the layers. I.e., All the three layers can be installed on the same machine or can be installed on different individual machines.

What are the external communication components of R/3 system?

These three layers are coming up with the following communication components -

RFC Interface –

This is the traditional functional interface of ABAP. A remote function call is a call of a function in other system that is different from the calling program running system. Calls are possible between different ABAP systems or between an ABAP system and an external system. On ABAP, the functions are implemented in function modules.

Internet Communication Manager (ICM) –

ICM is a process of ABAP that allows ABAP to communicate directly with the Internet using HTTP/HTTPS/SMTP. ICM is used to connect Web-based components such as SAPUI5, Web Dynpro ABAP, and BSP. ICM allows an ABAP to be used both as a client and as a server for Web services. ICM is accessed within ABAP programs using the classes and interfaces of Internet Communication Framework (ICF).

ABAP Channels –

ABAP Channels are a framework for event-based communication between application servers and the Internet. ABAP Messaging Channels (AMC) are used to exchange messages between ABAP programs on different application servers. ABAP Push Channels (APC), allow two-way communication between ABAP and the Internet using the WebSocket or TCP socket protocol.

• SAP Tutorial
• SAP - Evolution of SAP
• SAP - Introduction To ERP
• SAP - Modules

SAP - Architecture

• SAP - GUI Installation
• SAP - Net Weaver
• SAP - Logging onto SAP System
• SAP - GUI Customization
• SAP - End-User Customization
• SAP - GUI Navigation
• SAP - Programming Language (ABAP)
• SAP - SAP Security
• SAP - SAP Basis
• SAP - Transaction Codes
• SAP - Project Lifecycle
• SAP - Career In SAP
• SAP Useful Resources
• SAP - Quick Guide
• SAP - Useful Resources
• SAP - Discussion
• Selected Reading
• UPSC IAS Exams Notes
• Developer's Best Practices
• Questions and Answers
• Effective Resume Writing
• HR Interview Questions
• Computer Glossary

SAP : Three-Tier Architecture

With SAP R/3, SAP ushers in a new generation of enterprise software — from mainframe computing (client-server architecture) to the three-tier architecture of database, application, and user interface.

Three-Tier Architecture of SAP R/3

Presentation Servers

Presentation servers contain systems capable of providing a graphical interface.

• Presentation Layer is also known as client Layer
• Presentation Layer is a user interaction
• In SAP-User interaction purpose we use GUI
• GUI stands for Graphical user interface
• Example − Desktop, Mobile Devices, laptops

Application Servers

Application servers include specialized systems with multiple CPUs and a vast amount of RAM.

Application Layer is also known as Kernel Layer and Basic Layer.

SAP application programs are executed in Application Layer.

Application Layer serves as a purpose of a communicator between Presentation and Database Layer.

Application server is where the dispatcher distributes the work load to the different work processes makes the job done.

Database Servers

Database servers contain specialized systems with fast and large hard-drives.

• Database layer stores the data
• Data store can be Business data, SAP system data, SAP tables, Programs.
• Examples − Oracle, Microsoft SQL Server, IBM DB/2, Siebel, Sybase, etc.

Three-Tier Architecture

What is a Client?

A client is a logical portion of an SAP R/3 physical database. From a business standpoint, a client can be interpreted as a logical group of companies.

Points to Remember −

All customizing (configuration) and development (ABAP) work in SAP R/3 is performed in a client.

However, the data from both customizing and development work may be stored within an individual client (client dependent data) or among all clients (client independent data) in the system.

Client-Dependent vs. Client-Independent

The data in each client may be separate from that of the other clients. There are basically two types of data in an SAP R/3 system − Client-dependent and Client-independent data.

Client-dependent data is defined as data specific to an individual client. Examples of client-dependent data include number ranges, ABAP variants, and user masters as well as the data that is created or updated through SAP R/3 transactions.

Client-independent data can be defined as data contained across all clients in the system. Examples of client-independent data include data dictionary objects (tables, views), ABAP source code, screens, and menus.

Data resides in tables. To determine if a particular table is client-dependent or client-independent, the table structure needs to be reviewed. The table structure can be viewed by the data dictionary (SE11). If MANDT (client in German) is the first key field of the table, then the table is client-dependent; otherwise, the table is client-independent.

For example, the TSTC table is client-independent; however, the USR01 table is client-dependent.

SAP R/3 Delivered Clients

Every SAP R/3 system contains the three clients 000, 001, and 066. Let’s review these clients and examine what they contain.

These clients provide different features and must not be deleted.

Client 000 performs special functions. In particular, it is given extended functionality during upgrades.

Client 001 is basically a copy of 000 and can be used as a basis for a new customizing client.

Client 066 is a special client which is provided for operational system monitoring. It is used by SAP R/3’s Early Watch Service to provide performance recommendations.

In releases prior to 3.0, client 000 contained a model company. As of Release 4.0 clients, 000 and 001 are identical. Client 000 no longer contains a model company. Either client can be used as the basis for configuration through a client copy. Typically, most projects start with a copy of client 000 to begin building configuration. Customer work should never take place in the three delivered clients.

• Programming
• Admin & EIM
• BI & BW
• FICO & BPC
• CRM & Sales
• Introductions
• SAP PRESS Subscription

ABAP Programming for SAP

ABAP (Advanced Business Application Programming) is the name of SAP’s proprietary, fourth-generation programming language. It was specifically developed to allow the mass-processing of data in SAP business applications. 

By working with ABAP in SAP NetWeaver, companies running the SAP ERP and SAP S/4HANA business solutions have the opportunity to customize those systems to better meet their needs.

ABAP is a multi-paradigm programming language, meaning programmers can utilize procedural, object-oriented, and other programming principles. While it is SAP’s primary programming language, programs written with ABAP can run alongside those based on other programming languages such as Java , JavaScript , and SAPUI5.

Table of Contents

A Brief History of ABAP

New vs. old abap, when to use abap, abap editor, abap dictionary, abap painter, function builder, class builder, web application builder, other key abap terms, books by sap press.

ABAP was first introduced by SAP in the 1980s. Throughout the years, various enhancements to the language increased what programmers could do with it. For example, through April 2000 programs could only be created procedurally , meaning a program had to follow a set of pre-defined “procedures” to perform a certain task successfully.

In May 2000, SAP changed ABAP with release 4.6C, allowing for object-oriented programming (OOP). This programming strategy involves multiple individual “objects” interacting with one another, allowing programs to grow more complex with the use of ABAP design patterns and other OOP practices.

With the release of ABAP 7.4 and 7.5 in the early to mid-2010s, SAP gave object-oriented programmers using ABAP some powerful new features to play around with, vastly reducing the amount of code needed for common tasks. The end result is that code ends up being up to 50% shorter plus both cleaner and clearer—making both programmers and end users’ lives easier.

Other new features made available to ABAP programmers in the 2010s were extended syntax for Open SQL, ABAP Managed Database Procedures (AMDP), and core data services (CDS) Views.

Perhaps the biggest and most important change to ABAP programming came with the invention and release of the SAP HANA platform in the summer of 2011. Due to the in-memory architecture of this database, processing that formerly happened on the application layer now could be done on the database layer.

With the traditional, row-based database architecture of SAP R/3, it was important to have ABAP code run in the application layer rather than the database layer to save memory usage for further tasks. But SAP HANA allowed, and even encouraged, tasks to be completed in real-time by using in-memory technology.

This meant code could be developed and utilized in the database itself. For companies running the new ERP solution, SAP S/4HANA, this meant a whole slew of new programming opportunities. There are a few things to know when programming ABAP on SAP HANA , but it is very doable and quite powerful.

During the early 2010s, many developers wondered if ABAP was to become increasingly obsolete as SAP acquired multiple cloud, non-ABAP-based solutions and pivoted existing products towards the cloud. But with the advent of SAP S/4HANA, and more importantly ABAP in the Cloud, the language was given new life, leading many to proclaim “ABAP’s not dead.” Programmers went into the second half of the decade with a clear idea of how to use ABAP to code for SAP S/4HANA, SAP Business Technology Platform, and more.

These new platforms led to the creation of additional ABAP programming models. The first, the ABAP programming model for SAP Fiori , is used when developing SAP HANA-optimized OData services for SAP Fiori applications. These are based on core data services views and cover three application scenarios: analytical, transaction, and search.

The ABAP RESTful programming model is a very new paradigm based on the model for SAP S/4HANA, but eschews Business Object Processing Framework (BOPF) in place of a more advanced concept.

(Back to ToC.)

When working with a seasoned ABAP developer or scouring SAP Community blogs you may come across the terms “new,” “modern,” “old,” “classic,” “old-fashioned,” or “legacy” ABAP. What all does this mean?

Simply put, ABAP programming techniques that were used from the 1980s through April 2000 is typically what developers mean when they refer to “old,” “old-fashioned,” “classic,” or “legacy” ABAP. The advent of object-oriented programming in ABAP and the change in syntax that arrived with release 7.4 unofficially mark the changeover to “new” or “modern” ABAP.

All SAP solutions—from R/1 through SAP S/4HANA—can be modified with ABAP code. While some solutions, such as SAP Business One, SAP Ariba, and acquired products such as SAP Concur and SAP SuccessFactors, run primarily on other languages, ABAP will still play a role when these solutions interface with a central, ABAP-based SAP ERP or SAP S/4HANA system.

The ABAP Workbench

There are half a dozen important tools that programmers can use when working with ABAP code. They can be found in a development environment named the ABAP Workbench . This environment contains a number of needed development tools, the most commonly used of which accessible through the Object Navigator. You can access the Object Navigator with t-code SE80.

Here’s a breakdown of these key ABAP Workbench tools:

ABAP coding can be done in a special tool called the ABAP Editor , which has three different modes to work within—two versions of the Front-End Editor, and the Back-End Editor. The three editors are fully compatible and interchangeable. The source code created in one editor can be viewed by all other modes.

You can access the ABAP Editor with t-code SE38.

Also called the Data Dictionary, DDIC, or sometimes just “Dictionary,” this is a system-wide repository where database objects such as domains, data elements, and transparent tables are created and maintained. Programs will query the ABAP Dictionary to ensure that all sides are working with a single definition of an object.

You can access the ABAP Dictionary with t-code SE11.

The ABAP Painter is a set of two tools used to create GUI statuses and dynpros. The Menu Painter creates the GUI status and components, while the Screen Painter creates dynpros via text and screen editors.

You can access the Menu Painter with t-code SE41 and the Screen Painter with t-code SE51.

The Function Builder is a tool that can create and maintain function modules. These are universal procedures that start with FUNCTION and end with ENDFUNCTION .

You can access the Function Builder with t-code SE37.

The Class Builder is a specialized tool that creates and maintains class pools. A class pool is a repository object that stores global classes along with related definitions that will help the program implement the class.

You can access the Class builder with t-code SE24.

The Web Application Builder is a tool that allows programmers to create web applications.

You can access the Web Application Builder by following this menu path: Create > BSP Library > BSP Application .

While we’ve laid out much of the important terminology you’ll run into when working with ABAP, there are a handful more that will be helpful to you. Let’s take a look at twelve such terms and concepts.

• ABAP Debugger : A tool for performing functional troubleshooting in programs.
• ABAP Development Guidelines : A set of general and ABAP-specific guidelines meant to help programmers creating applications with ABAP.
• ABAP Development Tools : A set of downloadable plugins that allow programmers running Eclipse to develop ABAP. Formerly known as ABAP in Eclipse or ABAP Development Tools in Eclipse.
• ABAP Managed Database Procedures : A way to execute complicated code inside a database via stored procedure. Specific to SAP HANA and its in-memory processing.
• ABAP Objects : The official name for OOP in ABAP.
• ABAP Unit : A testing tool used to check functions of code sections.
• CDS Views : Core data service Views allow programmers to take full advantage of the SAP HANA database. They enhance information integration with cloud apps and other UIs via OData. These serve as the basis of SAP Fiori apps.
• Design Patterns : Tried and true solutions to common software requirements that can be “recycled” and used as the basis of a new program.
• Repository Information System : A source used to search repository objects; accessible via the Object Navigator or t-code SE15.
• SAP GUI (SAP Graphical User Interface) : The interface in the presentation layer of applications built with ABAP code that run on the desktop as opposed to in a browser.
• SAP NetWeaver AS ABAP : Part of a client server which allows for creating ABAP programs and consists of at least three layers, including the presentation, application, and database layers. The AS stands for Application Server .
• Two-Track Method Development : The simultaneous development of two versions of a method. An example of which might be implementing a method using both ABAP and AMDP .

Additional Resources

Feel you need more help learning ABAP programming? These books, blog posts, and videos will help, as well as this ABAP learning journey .

• “ 3 Things to Know When Coding ABAP on SAP HANA ”
• “ 4 Major OOP Updates in ABAP 7.4 and ABAP 7.5 ”
• " ABAP CDS Q&A with Authors Renzo Colle, Ralf Dentzer, and Jan Hrastnik "
• “ ABAP Debugging: Analyzing Memory Usage of Your Programs ”
• " ABAP Development in SAP HANA: The Code-to-Data Paradigm "
• " ABAP and Continuous Integration: the ABAP Test Cockpit and the ABAP Unit Runner "
• " ABAP in the Cloud: Getting to Know SAP BTP, ABAP Environment "
• " ABAP Q&A: CDS Views and Entities, ABAP RESTful Application Programming Model, and JOINS "
• " ABAP RESTful Application Programming Model versus BOPF "
• " ABAP Room 101 – The Worst Thing in the World "
• " ABAP Security Concepts "
• " ABAP SQL Versus CDS Views and AMDPs: What to Use? "
• " ABAP Test Cockpit Administration "
• " Advanced CDS Functionality for ABAP Development "
• " An Introduction to ABAP Development Tools "
• " The CASE Statement in ABAP "
• " CDS Access Control Fundamentals for ABAP "
• " Conditional Logic in ABAP "
• " The DO 1 TIMES Statement in ABAP "
• “ Exploring The ABAP Editor ”
• " Exploring the Architecture of the ABAP RESTful Application Programming Model "
• " How to Clean Your ABAP Code with One Keystroke Using ABAP Cleaner "
• " How to Create an ABAP Object in VS Code "
• " How to Create a Basic Interface CDS View with ABAP "
• " How to Create Your First ABAP Program in SAP [13 Steps] "
• " How Does Test-Driven Development Simplify ABAP Programming? "
• " How to Evaluate Custom Code Usage Data Ahead of an SAP S/4HANA Migration "
• " How to Install abapGit on an SAP System "
• " How to Name a Virtual Data Model in SAP S/4HANA "
• " How to Set Up an ABAP Cloud Development Environment "
• " How to Troubleshoot Implementations of CDS Models "
• " Implementing ABAP Server Session Security "
• " Importance of Packages for Agile ABAP Development "
• “ Installing SSL in SAP NetWeaver AS ABAP: Setting System Parameters ”
• " Introducing the Concept of Antifragile ABAP "
• " Metadata Extensions for CDS Views "
• " Taking the ABAP Pain Out of Upgrades "
• " Transactional Object Models in CDS for ABAP "
• “ Two-Track Method Development with AMDP and ABAP ”
• " Unhandled Exceptions and Short Dumps in ABAP "
• " Using XML in an ABAP Project "
• " What Are ABAP Statements? "
• "" What Are the Different SAP Development Tools? "
• " What Is ALV? An Overview of ABAP List Viewer/SAP List Viewer "
• " What Is Clean ABAP? "
• " What Is Different with the New ABAP Debugger? "
• " What to Know to Become an SAP Full Stack Developer "
• " What Is Legacy Code and Why Is it Bad? "
• “ What Is the ABAP RESTful Application Programming Model? ”
• " What Is SFLIGHT and the Flight and Booking Data Model for ABAP? "
• " Who Are ABAPers And What Do They Do? "
• “ Working with the ABAP Prototype Design Pattern ”
• " Your ABAP Questions, Answered by Paul Hardy "
• ABAP: An Introduction
• ABAP 7.5 Certification Guide
• ABAP Development for SAP HANA
• ABAP in the Cloud: Development and Operations with SAP BTP, ABAP Environment
• ABAP Programming Model for SAP Fiori
• ABAP RESTful Application Programming Model: The Comprehensive Guide
• ABAP to the Future
• Clean ABAP: A Style Guide for Developers
• Complete ABAP
• Core Data Services for ABAP
• Designing Testable ABAP Classes and Packages
• Design Patterns in ABAP Objects
• Full Stack Development with SAP
• Hands On with abapGit
• JavaScript for ABAP Developers
• Migrating Custom Code to SAP S/4HANA
• Object-Oriented Programming with ABAP Objects
• Parallel Processing with ABAP Objects: Implementation and Testing
• Refactoring Legacy ABAP Code
• SAP Cloud Platform, ABAP Environment: Application Development and Operation
• Test Data Classes for ABAP
• Test-Driven Development with ABAP Objects
• ABAP Core Data Services (CDS) Q&A with SAP's Renzo Colle, Ralf Dentzer, and Jan Hrastnik
• ABAPs Journey to the Cloud
• ABAP Q&A with Author and SAP Mentor Paul Hardy
• ABAP and SAP S/4HANA
• CDS Views Vs. CDS Entities
• How to Analyze ABAP Short Dumps in an SAP S/4HANA System
• How Do ABAP and SAP Fiori Relate?
• Learn SAP Full Stack Development with These Books from Consultants and SAP Employees
• Tips and Tricks for Better OO ABAP Design with Dr. Kerem Koseoglu
• What Is abapGit?
• What Is SAP ALV (ABAP List Viewer)?
• What Is the Future of Function Modules?
• What Is the Point of Automated Unit Testing?

And t o continue learning even more about ABAP, sign up for our weekly blog recap here:

• Legal Notes
• Privacy Policy
• Terms of Use
• Change Privacy Options

Discovering ABAP

Knowledge base for sap abap developers, abap code samples : abap and json, json examples.

The second example below, shows the list of collections from first example. Each value in the JSON can either be direct value or list of name-value pairs / collections included in [ ] and separated by comma i.e. ‘,’.

JSON vs XML

Validate jason data in abap.

Code Sample

Read JSON using ABAP

Create json using abap, call transformation, share this:, leave a comment cancel reply.