TIBCO ADR3 SAGA Chapter One SAP R/3 – An Introduction

SAP AG brought out a client–server version of the software called SAP R/3

Real-Time Data Processing (3 stands for 3-tier)

  • Database
  • Application Server
  • Client (SAPgui)



  • SAP R/1 System RF: 1972
  • SAP R/2 Mainframe System: 1979
  • SAP R/3 Enterprise Edition 1.0 A: July 1992
  • SAP R/3 Enterprise Edition 2.0: 1993
  • SAP R/3 Enterprise Edition 3.0: 1995
  • SAP R/3 Enterprise Edition 4.0B: June 1998
  • SAP R/3 Enterprise Edition 4.3
  • SAP R/3 Enterprise Edition 4.5B: March 1999
  • SAP R/3 Enterprise Edition 4.6C: April 2001
  • SAP R/3 Enterprise Edition 4.6F
  • SAP R/3 Enterprise Edition 4.7: 2003
  • SAP ERP Central Component (ECC) 5.0: 2004
  • SAP ERP Central Component (ECC) 6.0: October 2005
  • SAP enhancement package 1 for SAP ERP 6.0: December 2006
  • SAP enhancement package 2 for SAP ERP 6.0: July 2007
  • SAP enhancement package 3 for SAP ERP 6.0
  • SAP enhancement package 4 for SAP ERP 6.0
  • SAP enhancement package 5 for SAP ERP 6.0: June 2010
  • SAP enhancement package 6 for SAP ERP 6.0: June 2012
  • SAP enhancement package 7 for SAP ERP 6.0: 2013
  • SAP S/4 Simple Suite for HANA: February 2015


  • SAP R/3 was arranged into distinct functional modules, covering the typical functions in a business organization. The most widely used modules were Financials and Controlling (FICO), Human Resources (HR), Materials Management (MM), Sales & Distribution (SD), and Production Planning (PP).
  • Each module handled specific business tasks on its own, but was linked to the other modules where applicable. For instance, an invoice from the billing transaction of Sales & Distribution would pass through to accounting, where it will appear in accounts receivable and cost of goods sold.
  • SAP typically focused on best practice methodologies for driving its software processes, but more recently expanded into vertical markets. In these situations, SAP produced specialized modules (referred to as IS or Industry Specific) geared toward a particular market segment, such as utilities or retail.
  • SAP based the architecture of R/3 on a three-tier client/server structure:
  • Presentation Layer (GUI)
  • Application Layer
  • Database Layer



  • Presentation Layer
  • SAP allows the IT supported processing of a multitude of tasks which occur in a typical company. The newer SAP ERP software differs from R/3 mainly because it is based on SAP Net Weaver: core components can be implemented in ABAP and in Java and new functional areas are mostly no longer created as part of the previous ERP system, with closely interconnected constituents, but as self-contained components or even systems.


  • Application Server
  • This server contains the SAP applications. In systems with two layers, this server forms part of the database server. Application server can be set up for online users, for background processing, or for both.
  • An application server is a collection of executables that collectively interpret the ABAP/4 (Advanced Business Application Programming / 4th Generation) programs and manage the input and output for them. When an application server is started, these executables all start at the same time. When an application server is stopped, they all shut down together. The number of processes that start up when you bring up the application server is defined in a single configuration file called the application server profile. Each application server has a profile that specifies its characteristics when it starts up and while it is running. For example, an application server profile specifies:
  1. Number of processes and their types
  2. Amount of memory each process may use
  3. Length of time a user is inactive before being automatically logged off.


  • 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.
  • Not practical, only one application server is needed to run an R/3 system.
  • But in practice, the services are distributed across more than one application server.
  • This means that not all application servers will provide the full range of services.
  • 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 choose an appropriate server when a user logs onto the system.
  • The application server exists to interpret ABAP/4 programs, and they only run there.
  • If an ABAP/4 program requests information from the database, the application server will send the request to the database server.


  • Security
  • Server-to-server communications can be encrypted with the SAP cryptographic library. With the recent acquisition of relevant parts of SECUDE, SAP can now provide cryptography libraries with SAP R/3 for Secure Network Communications and Secure Socket.

One comment

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s