SAP R/3

SAP R/3 is the former name of the enterprise resource planning software produced by the German corporation SAP AG (now SAP SE). It is an enterprise-wide information system designed to coordinate all the resources, information, and activities needed to complete business processes such as order fulfillment, billing, human resource management, and production planning.[1]

The current successor software to SAP R/3 is known as SAP ERP.

History of SAP R/3

Earlier versions

The first version of SAP's flagship enterprise software was a financial accounting system named R/1. This was replaced by R/2 at the end of the 1970s. SAP R/2 was a mainframe-based business application software suite that was very successful in the 1980s and early 1990s. It was particularly popular with large multinational European companies who required soft-real-time business applications, with built-in multi-currency and multi-language capabilities.

R/3

With the advent of distributed client–server computing SAP AG brought out a client–server version of the software called SAP R/3 (the "R" was for "Real-time data processing" and "3" was for "3-tier": 1) database, 2) application server, and 3) client (SAPgui)). This new architecture is compatible with multiple platforms and operating systems, such as Microsoft Windows or UNIX. This opened up SAP to a whole new customer base.

SAP R/3 was officially launched on 6 July 1992. Various releases of the software were made through the 90s.

A newer version of the software, with new architecture, was released in 2003–2004, renamed as SAP ERP. ECC is a version name for SAP ERP,(ERP Central Component). Other SAP Implementations can be customized products can function on the central component. SAP came to dominate the large business applications market over the next 10 years. SAP ECC 5.0 ERP is the successor of SAP R/3 4.70. The newest version of the suite is SAP ERP 6.0, Enhancement Pack 7.

Releases

Software organization

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.

Technology

SAP based the architecture of R/3 on a three-tier client/server structure:

  1. Presentation Layer (GUI)
  2. Application Layer
  3. 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 NetWeaver: 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:

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.[3] With the recent acquisition of relevant parts of SECUDE,[4] SAP can now provide cryptography libraries with SAP R/3 for Secure Network Communications and Secure Socket.

See also

References

  1. ↑ Esteves, J., and Pastor, J., "Enterprise Resource Planning Systems Research: An Annotated Bibliography", Communications of AIS, 7(8): 2–54.
  2. ↑ "Difference bet. ECC 6.0 & SAP R/3 4.7". Itknowledgeexchange.techtarget.com. 2012-06-01. Retrieved 2012-09-12.
  3. ↑ SAP Cryptographic Library (SAPCRYPTOLIB
  4. ↑ SAP to Acquire Software Security Products and Assets from SECUDE

External links

Android applications:

This article is issued from Wikipedia - version of the Wednesday, February 10, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.