Showing posts with label SAP. Show all posts
Showing posts with label SAP. Show all posts

Sunday, September 20, 2015

Why is SAP better than other ERP solutions?

Why is SAP better than other ERP solutions?


It is not necessarily better. 

All ERP packages have their strengths and weaknesses. SAP's weakness is that it is very expensive and takes a long time to implement. SAP's strength lies in the ability to develop and customize  - to handle complex business processes that other software doesn't 'fit'- and you can find a thousand Oracle proponents who will claim they can handle the same complex requirement - and they're right. 

The market penetration revolves around client size. If you have 5 customer service reps processing returns, well, Sage ERP has a half a dozen packages that will handle that. However, if you have 500 customer service reps you can use SAP and shave 60 seconds off the time it takes to complete the task with Sage, that's 500 x 60 seconds x 25 transactions per day x 5 days a week x 52 weeks a year x $15 per hour, it's close to a million a year in labor savings. And that's just in customer service. Factor in similar efficiencies in warehousing, delivery, web services, finance, and so on, and suddenly the $5m to install SAP makes sense - even the $3m to upgrade gets approved.  But none of it makes sense until you are in a company large enough to have, say 500 customer service reps worldwide.

SAP is most powerful but it is very expensive as compare to ERP as well it take more time to implement because of its vast modules but once it is implemented then it take of the work of the big organization because small company can't afford SAP package of ERP solutions However it is best enough in its reliability and effective.

SCN Download Center Is Now on the SAP Store: What's New?

SAP now announced that the old SCN Download Catalog has been moved to its own space in the SAP Store. In this new space, each package will be searchable. We initiated the migration project more than three years ago because the platform was old and unstable, the server was difficult to access and to maintain. Now we can offer a better user experience and we’ll be able to do a tracking for downloads.

How to find a Download Package
Please go to the Software Downloads space on SCN and use the Software Download Search to look for your download package.You can also search for your download package directly on the SAP Store using it's search functionality.

Downloads_Space.PNG

How to download a package
The SCN Download Catalog on the SAP Store offers a modern design and a clear catalog structure. The first catalog page indicates the package name and version, how it is rated and a short description of the download package. The free download packages are marked accordingly.

SAP_Store_Item.PNG

When clicking on the download button (Get it now), a pop-up opens.To get the download you need to fill in your credentials and to accept the SAP authorization as the Terms and Conditions by marking the corresponding check fields.
pic02.png
Having done this the download link will be provided to you via an email. From the catalog overview page you can get further information about the download package by opening the corresponding tabs (for example, screenshots and videos - if provided by the package owner - additional technical information, customer reviews, solution provider and related solutions displayed as small widgets).

One of the pain points and a key reason for the migration was the fact we couldn't track the number of downloads for each package. The SAP Store will enable us to see the items, views and the number of downloads for each package. These numbers will be generated and presented once a month to the stakeholders. If you are a package(s) owner, please contact us for more information.

How to upload a package
To upload a package, please send the necessary information (name of the package, version and size, technical description, documentation, screenshots and videos) about the download package to Ingvild Bayer or David Metser. Upload your package to SAP Box and send the link to Ingvild Bayer or David Metser. Your content will be checked and then published on the SAP Store and your package will be transferred to the Akamai Server.
SAPStore_List.PNG

Please contact us for any questions. We look forward to your feedback and comments.

We would like to take this opportunity to say a big thank you to Scott Lawley who helped us to make this happen and to Mikael Delbreus, the project manager, who drove this project.

Understanding the SAP R/3 Architecture

R/3 Architecture 
The SAP R/3 System has a three-tier client/server architecture. All data is stored in a database, and the data is processed in the application layer on the application servers. The SAPgui frontend (presentation layer) is the interface to the user. All three layers are connected to each other with networks. The following graphic depicts the client/server architecture of the R/3 System, and the communication requirements between the presentation and application layers and between the application and database layers:
Depending on your requirements, you can distribute the services to different hosts.
Smaller applications keep the database and the R/3 application on the same host. The large volume of data that passes between the R/3 application and the database (SAP server communication) is processed locally and not through a network.
The presentation layer is usually made up of PCs on which the SAPgui frontend is installed. The SAPgui is not a terminal emulation but an application program that displays R/3 application data graphically. This means that there are no great demands placed on the connection between the SAPgui frontend PCs and the R/3 application (access communication).
Higher processing demands on the R/3 application can be realized by additional application servers (application servers are hosts on which the R/3 application runs).
Very high demands are made on bandwidth and delay time between the application servers and the database server. You need to set up a suitable network connection to meet these demands.
You can speed up and secure data throughput to the database by placing the database on a separate host. The database server host then communicates only with the R/3 application servers. By isolating the database completely from the rest of the corporate network, you prevent unauthorized access to sensitive data and ensure high performance.
For data backup purposes you may need to connect the database server to a dedicated network (SAN = Storage Area Network).
Access Communication
Access communication covers all access to the R/3 System. This includes user access through the SAPgui, and also links to other R/3 Systems and external applications.
An access network is not a dedicated network segment, but includes all network segments through which the R/3 System is accessed.
Important Design Criteria for the Access Network:
  • Block-oriented data traffic ® delay times in the network are relatively non-critical for the SAPgui
  • Bandwidth must be determined separately for each location, depending on the number of users and their activities
  • The availability of the network must also be specified according to the user group or location
Server Communication
Server communication covers all communication between the application servers and the database server, and is of great importance for the R/3 System. In each individual case you must decide whether you want to process the server communication through its own physical network (server network), or whether you want access and server communication to share a physical network. You must remember that any worsening in server communication also has a negative effect on the performance of the R/3 System.
A server network is the network connection between the servers (application servers and database servers) of an R/3 System.
Important Design Criteria for the Server Network:

  • High throughput of data or high bandwidth
  • Minimum delay time (round trip time)
  • Includes the servers of the R/3 System only
  • High availability
  • No non-SAP data traffic (for example, data backup over the network)
  • Direct server connection ® no expensive cabling
  • Greatest possible security against unauthorized access to the database server if the server network is set up as a separate segment from the rest of the corporate network

References:
http://help.sap.com/

All About SAP System


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 fulfillmentbillinghuman 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 amainframe-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 asMicrosoft 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.[citation needed] 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.