Sap system architecture


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sap system architecture

  1. 1. ERP •ERP stands for Enterprise Resource Planning. •ERP is a way to integrate the data and processes of an organization into one single system. ERP systems will have many components including hardware and software to achieve integration. •ERP systems use a unified database to store data for various functions found throughout the organization. •The term ERP originally referred to how a large organization planned to use organizational wide resources. •The use of ERP has changed and is extremely comprehensive, today the term can refer to any type of company, no matter what industry it falls in. •ERP systems are used in almost any type of organization - large or small.
  2. 2. Introduction
  3. 3. History of SAP •SAP: Systems Applications and Product in Data Processing. •In 1972, five systems analysts began working nights and weekends to create standard software with realtime data processing. Twenty-five years later their vision is a reality: SAP is the world’s market and technology leader in business application software. •On April 1, 1972 five former IBM employees founded SAP as Systeme Anwendungen, Produkte in der Datenverarbeitung(“Systems Applications, products in Data Processing”) in Mannheim, Germany. Their vision was to develop and market standard enterprise software which would integrate all business processes. The idea came to them through their work as systems consultants for IBM when they noticed that client after client was developing the same, or very similar, computer programs. The second part of their vision was that data should be processed interactively in realtime, and the computer screen should become the focal point of data processing. •Products have played the central role in SAP's success story. In this area, two milestones stand out: first, the development and 1979 market release of the R/2 software system for mainframes, and, second, the R/3 client/server software system introduced in 1992. Since its debut, the R/3 System use has grown explosively and now accounts for the lion's share of SAP product sales. At present, more than one million end users around the world work with the R/3 System.
  4. 4. History of SAP • The development of SAP products has continually benefited from major advances in the hardware sector. Back in 1972, the limited storage capacity of computers posed one of the biggest challenges. In those days, mainframes only had 500 kilobytes of storage capacity. Slow data input and output meant that only partial applications with a limited data volume were feasible. It was against this technological background that SAP signed its first customer, the German ICI subsidiary in Östringen. • With the successful implementation of its initial project, SAP had nine employees and, at the end of its first fiscal year, posted a profit on revenues of DM 620,000. In the second year of operation, two local businesses – the tobacco and cigarette manufacturer RothHändle and the pharmaceutical company Knoll - selected the newly developed SAP Financial Accounting (RF) System. This system quickly earned a reputation as an excellent standard package and installations expanded to 40 customers. But product development did not slow on this success, and a second standard product, the Materials Management (RM) System, with modules for purchasing, inventory management and invoice verification, soon followed. The benefits of SAP's integration philosophy showed through, with data from Materials. Management flowing straight into Financial Accounting. • The Previous versions and the current versions are 4.7EE, 5.0ECC and 6.0ECC.
  5. 5. Specification of 6.0ECC Master Data Deleting Bonus Buys: The condition records which are created for bonus buy can be deleted. Basic Functions: Pricing and Conditions Condition-Based Excise Determination in SD: JINFAC Sales from manufacturing plants JINEXP Export sales JINDEP Sales from depots JINSTK Stock transfers Taxes: Condition-Based Excise Determination in SD can calculate excise duties and sales taxes applicable in India in sales documents using standard pricing procedures (condition-based excise determination). Sales: Evaluation of open sales documents according to US-GAAP guideline SFAS 133. According to SFAS 133 - Accounting for Derivative Instruments and Hedging Activities - the balance sheets to the market value must be prepared for open values in certain sales documents.
  6. 6. • • • • • • • Purchase Requisitions Generated from Sales Orders Update FM As of SAP R/3 Enterprise Public Services 1.10, a purchase requisition that is generated out of an SD order line item creates a commitment line in Funds Management (FM). Budget can be assigned during this update. SD Order Update in Funds Management (FM) As of SAP R/3 Enterprise Public Services 1.10, billing-relevant SD orders update commitment line items in FM. Billing: Resource-Related Billing for Internal Orders With Revenues (new) Up to now, resource-related billing was not possible for: Sales documents with cost collectors Service orders with revenues WBS elements with revenues Doc. Flow Evaluations of Resource-Rel. Billing (New) Billing Requests for Sales Order Items (Enhanced) Collective Processing for Resource-Related Billing (Enhanced)
  7. 7. Introduction to SAP System
  8. 8. Screen Elements
  9. 9. Standard Easy Access • Easy access is a standard entry screen. • Set default transaction a default, extras-set start transaction. • Set favorites, select favorite-transaction code.
  10. 10. Online Help • • • • • • • Application help: Displays comprehensive help on the current application. Selecting this menu option in the initial screen displays help on getting started with R/3. SAP Library: This is where all online documentation can be found. Glossary: Enables you to search for definitions of terms. Release notes: Displays notes which describe functional changes that occur between R/3 releases. SAPNet: Enables you to log on to SAPNet. Feedback: Enables you to send a message to the SAPNet R/3 Frontend, SAP’s service system. Settings: Enables you to select settings for help.
  11. 11. System architecture
  12. 12. Client/Server Principles • Server means a service provided by a software component. The component consist of a process or group of processes. • Software components that use these servers are called as clients
  13. 13. R/3 system client/server configuration
  14. 14. System Kernel • • • • User enters the data, is sent to dispatcher through user interface (SAP GUI). Process request is saved in dispatcher in request queues and processed according to FIFO. Data is actually processed in work process. The result of processing is send through dispatcher back to SAP GUI.
  15. 15. Processing the request
  16. 16. Database interface
  17. 17. Locks in R/3 system
  18. 18. SAP Products • R/2 System • R/3 System
  19. 19. R/2 System • It is a main frame system compatible to IBM, Siemens etc., • Data intensive and big centralised Industries. • It is not open system. (It can not communicate with other systems. But with the help of ALE it can be linked to R/3 and can be made open system)
  20. 20. R/3 system • Client server system • Multi Lingual • It can be easily customized based on country’s needs. • It has OSS (Online Support System) • It has other services like Information service and Maintenance service. • It has Preventive service (early watch serv.)
  21. 21. SAP R/3 Architecture D a ta b a s e S e rv e r A p p li c a t i o n S e rv e r P r e s e n ta io n S e rv e r P r e s e n ta tio n S e rv e r A p p li c a t i o n S e rv e r P r e s e n ta tio n S e rv e r P r e s e n ta tio n S e rv e r P r e s e n ta io n S e rv e r A p p li c a t i o n S e rv e r P r e s e n ta tio n S e rv e r
  22. 22. SAP R/3 Architecture contd. Database Server Application Server Presentation Server : Stores Database. : Contains Software for Running the Application Logic. : Graphical User Interface
  23. 23. SAP R/3 Architecture contd. The advantage of having 3 tier or 3 layered Architecture is to reduce traffic on the Database Server.
  24. 24. SAP R/3 Architecture contd. Based on the required degree of distribution, you can combine two servers or all three servers in the same machine (Stand alone).
  25. 25. SAP R/3 Structure • Application Layer for Standard and new applications. • Middle ware Layer also called as R/3 Basis (will be discussed later) • Operating System, Database O.S NT Unix AS/400 Database GUI Oracle Win 3.1 Ingress NT,95 Informix,DB/2 Protocols TCP/IP CPC
  26. 26. Components of M.W.Layer • ABAP/4 Development Workbench • Database Interface • GUI etc.,
  27. 27. ABAP/4 Dev Workbench It contain different tools for development of ABAP/4 objects, checking and analysing programs and finally transportation of objects. 1) ABAP/4 Language 2) Data modeler 3) Object browser 4) Repository 5) Test & Analysing tools 6) The Query and 7) Workbench Organizer
  28. 28. ABAP/4 Language It is the Central part of Middle ware layer that eliminates dependencies from Hardware, Operating Systems or database management systems.
  29. 29. Interfaces of R/3 system • • • • • Remote Function Call (RFC) Object Linking and Embedding (OLE) Connecting R/3 to the Internet Electronic Data Interchange (EDI) Data transfer interfaces
  30. 30. RFC-Remote Functional Call There are three types of RFC calls: • Synchronous RFC call: The calling program stops until the function module has been processed on the target server and any results have been returned to the caller. Only then does the calling program continue processing. • Asynchronous RFC call: The calling program runs parallel to and independently of function module processing in the target system. Programmers are responsible for the processing of the results. In addition, the target system must also be available at the time of the RFC call. • Transactional RFC call: Several function modules can be grouped into one transaction. They are processed only once in the target system, within an LUW, and in the sequence in which they were called. In the case of an error, a message is sent to the calling system that you can analyze using transaction SM58. For transactional RFC, the target system does not have to be available at the time of the RFC call. In addition, you can configure the frequency and intervals of individual queries.
  31. 31. SAP Netweaver
  32. 32. System Landscape
  33. 33. Security in R/3 System