SAP R/3 is the previous name of enterprise resource planning software produced by the German company SAP AG (now SAP SE). It is a corporate information system designed to coordinate all the resources, information, and activities necessary to complete business processes such as order fulfillment, billing, human resource management, and production planning.
The current router software for SAP R/3 is known as SAP ERP Central Component (ECC).
Video SAP R/3
History of SAP ECC
Previous version
SAP R/2 is a very successful mainframe-based business application software in the 1980s and early 1990s. It's very popular with major European multinational companies that require real-time software business applications, with multi-currency and multi-language built-in capabilities.
R/3
With the advent of distributed client-server computing, SAP SE released a version of server-client software called SAP R/3 ("R" for "Real-time data processing" and "3" is for "tier": 1) database , 2) application server, and 3) client (SAPgui)). The new architecture is compatible with various platforms and operating systems, such as Microsoft Windows or UNIX. This opens SAP to a new customer base.
SAP R/3 was officially launched on July 6, 1992. Various software releases were made during the 1990s.
The latest version of the software, with its revised technical architecture, was released in 2004, and renamed to SAP ERP Central Component (ECC). SAP dominates the large business application market. The latest version of this product is SAP ECC 6.0 Enhancement Pack 8.
SAP ECC is a core component in SAP Business Suite (a collection of applications including CRM, SCM and others, along with ECC components). SAP ECC contains different functions but is integrated in its "module", eg. Financial module, HR module, Warehouse Management etc all within ECC). The combined complexity of the Business Suite, along with newer in-cloud competitors, has in recent years encouraged SAP to invest in simplification and greatly increased system response time, culminating in the S/4 Simple Suite announcement in February 2015./4 has a single tenant architecture and is being built on a pile of database technology in SAP's (HANA) memory and will be available in cloud and on-deployment options. The classic three-tier architecture and database-agnostic R/3 are replaced by two-tier architecture.
Maps SAP R/3
Release
- SAP R/1 RF System: 1973
- SAP R/2 Mainframe System: 1979
- SAP R/3 Enterprise Edition 1.0 A: July 1992
- SAP R/3 Enterprise Edition 4.0B (SAP R/3 4.0B): April 6, 1998
- SAP R/3 Enterprise Edition 3.1l (SAP R/3 3.1I): May 11, 1998
- SAP R/3 Enterprise Edition 4.3
- SAP R/3 Enterprise Edition 4.5B (SAP R/3 4.5B): March 29, 1999
- SAP R/3 Enterprise Edition 4.6B (SAP R/3 4.6B): December 6, 1999
- SAP R/3 Enterprise Edition 4.6C (SAP R/3 4.6C): April 3, 2000
- SAP R/3 Enterprise Edition 4.6F
- SAP R/3 ENTERPRISE 4.7X110: July 15, 2002
- SAP R/3 ENTERPRISE 4.7X200: September 22, 2003
- SAP ERP Central Component (ECC) 5.0: June 21, 2004
- SAP ERP Central Component (ECC) 6.0: October 24, 2005
- SAP 1 upgrade package for SAP ERP 6.0 (EHP1 FOR SAP ERP 6.0): December 21, 2006
- SAP 2 upgrade package for SAP ERP 6.0 (EHP2 FOR SAP ERP 6.0): July 27, 2007
- SAP 3 upgrade package for SAP ERP 6.0 (EHP3 FOR SAP ERP 6.0): December 7, 2007
- SAP 4 upgrade package for SAP ERP 6.0 (EHP4 FOR SAP ERP 6.0): November 21, 2008
- SAP 4 upgrade package for SAP ERP 6.0 on SAP upgrade package for SAP NetWeaver 7.0 (EHP4 FOR SAP ERP 6.0/NW7.01): November 21, 2008
- SAP 5 upgrade package for SAP ERP 6.0 (EHP5 FOR SAP ERP 6.0): July 12, 2010
- SAP 6 upgrade package for SAP ERP 6.0 (EHP6 FOR SAP ERP 6.0): August 24, 2011
- SAP 7 upgrade package for SAP ERP 6.0 (EHP7 FOR SAP ERP 6.0): August 13, 2013
- SAP Fiori 1.0 for SAP ERP (UI FOR EHP7 FOR SAP ERP 6.0): 29 November 2013
- SAP S4 HANA 1511
- SAP 8 upgrade package for SAP ERP 6.0 (EHP8 FOR SAP ERP 6.0): January 20, 2016
- SAP S4 HANA 1610
- SAP S4 HANA 1709
Software organization
SAP R/3 is structured into different functional modules, which include distinctive functions within a business organization. The most widely used modules are Finance and Control (FICO), Human Resources (HR), Material Management (MM), Sales & amp; Distribution (SD), and Production Planning (PP).
Each module handles certain business tasks on its own, but is related to other modules if applicable. For example, invoices from Sales & amp; The distribution will pass to accounting, where it will appear in receivables and cost of goods sold.
SAP typically focuses on best practice methodologies to drive its software process, but has recently been extended to the vertical market. In this situation, SAP generates custom modules (called IS or Certain Industries) targeted to specific market segments, such as utilities or retail.
Technology
SAP based on R/3 architecture on a three-tier client/server structure:
- Presentation Layer (GUI)
- Application Layer
- Database Layers
Presentation Layer
SAP enables IT-supported processing of many tasks that occur in a typical company. The new 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 largely no longer created as part of previous ERP systems, with closely related constituencies. , but as an independent component or even a system.
Application Server
This server contains SAP applications. In a two-layer system, this server forms part of the database server. The application server can be set 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) program and manage inputs and outputs for them. When the application server starts, all these executable files start at the same time. When the application server is stopped, they are all shut down together. The number of processes that start when you open an 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 is run and when it is running. For example, the app server profile specifies:
- Number of processes and types
- The amount of memory each process can use
- The length of time the user is inactive before being automatically deleted.
The Application layer consists of one or more application servers and messaging servers. Each application server contains a set of services used to run R/3 systems. Not practical, only one application server is required to run R/3 systems. In practice, however, services are distributed across multiple application servers. This means that not all application servers will provide a full range of services. The message server is responsible for communication between application servers. It passes requests from one application server to another in the system. It also contains information about the application server group and the current load balancing in it. Use this information to select the correct server when the user logs into the system.
The application server exists to interpret the ABAP/4 program, and they just run there. If the ABAP/4 program requests information from the database, the application server sends a request to the database server.
Security
Server-to-server communication can be encrypted with SAP cryptographic libraries. With recent acquisitions from relevant SECUDE sections, SAP can now provide a cryptographic library with SAP R/3 for Secure Network Communications and Secure Sockets.
See also
- NetWeaver
- SAP ERP
- T-code
References
Source of the article : Wikipedia
0 Comments