SAP R/3 is a successful ERP software in SAP SE.

SAP R/3 is a system that still covers all processes of a commercial enterprise, where resources can be planned efficiently by digital mapping and where effectiveness problems can be identified. The system uses a system structure that is split into clients and server. Here the client requests a service from the server and the server responds to this request. The SAP R/3 client-server model enables the digitalization of business processes. SAP R/3 is a set of integrated business applications in which all business-relevant areas of a company are viewed in context. The application is the successor to SAP R/2, which was designed for operation on mainframe computers.

SAP R/3 provides for the storage, processing, analysis, and retrieval of company data (e.g. financial analyses, production processes) in various ways. The access to SAP R/3 applications and R/3 databases is possible via web access and web browsers. Business applications, such as Microsoft Office, can be connected via a defined interface.

SAP R/3 is compatible with all conceivable operating systems and platforms. The system can be used by multiple companies even if they are using different platforms. Integration and collaboration have been developed to make the system accessible for planning options and processes of companies in all possible industries and areas.

SAP Moduls in SAP R/3 - SAP ERP ECC

SAP ECC enables IT-supported implementation of a variety of tasks which occur in a typical commercial enterprise. The modular structure of the system maps the typical organizational structure of many companies.

In accordance with the SAP ECC system, multifunctional and flexible modules are assigned to the three business application areas supported by SAP ECC, accounting (SAP ERP Financial), human resources (SAP ERP Human Capital Management), and logistics (SAP ERP Operation). The most commonly used modules are accounting, controlling, HR, materials management, production planning, and sales.

Each of these modules handles a specific work operation and is, if necessary, linked with other modules to facilitate and simplify the work process. The main goal when using SAP R/3 continues to be the digitalization of work processes.

Strukture in SAP ERP ECC, SAP R/3

In December 2003, SAP R/3 was renamed mySAP ERP. Since 2007, the designation SAP ERP ECC (ERP Central Component) has been used.

SAP ECC differs from SAP R/3 in that SAP ECC is based on SAP NetWeaver. Here, integral components can be implemented in ABAP and in Java. New functional areas are frequently no longer created as part of the existing SAP ERP systems but as independent components or as a separate system.

Since 2006, the SAP ERP application is extended functionally by way of enhancement packages. These SAP enhancement packages guarantee the stability of existing functions and ensure easy, selective access to new functionality.

SAP R/3 client-server architecture

SAP R/3 uses a client-server architecture:

  • Database server
  • Application server
  • Presentation layer on the client side

This structure makes it possible, with growing requirements, to increase the performance of the overall system.

User interface SAP GUI in SAP R/3 - SAP ECC

Most of the applications are operated via the graphical user interface SAP GUI. Depending on the components, other clients are also possible: Web browser with or without Java, WAP or Java Web Start.

The client software SAP NetWeaver Business Client enables role-based display of all the applications developed by SAP.

SAP Customizing

In contrast to smaller ERP systems or non-SAP systems, numerous functions in SAP ERP can be set up simply using parameters. The adjustment of these settings is referred to as SAP customizing and this takes place on introduction of the SAP system or SAP module.

Most of the parameters are controlled via database tables which are evaluated during runtime.

If the settings options through the available customizing functions are not sufficient, the standard programs have several extension points where customer-specific program elements can be embedded in the standard system via defined interfaces (e.g. user exits, customer exits).

If these are also not sufficient, then it is possible to use almost any standard program. These modifications are all recorded automatically so that, in the event of error messages, responsibility can be assigned. Due to the increased follow-up effort involved, e.g. in update comparison of the standard programs, modifications should be avoided if possible.

Customizing the system to a company’s requirements calls for a certain level of experience. TRIACOS provides this expert experience.

Follow us: