28
ERP - OVERVIEW Madhusudan Rao K 20-10-2013

SAP Basis Overview

Embed Size (px)

DESCRIPTION

It explains about ERP and different types of ERP's available. And explains ERP in SAP much in detail.

Citation preview

Page 1: SAP Basis Overview

ERP - OVERVIEW

Madhusudan Rao K20-10-2013

Page 2: SAP Basis Overview

ERP

• Planning the resources in an organization is called ERP

• ERP stands for Enterprise Resource Planning which is used to integrate one or more departments in an organization and it is also used to minimize paper work in the organizations.

Page 3: SAP Basis Overview

Examples for ERP’s

–Oracle Apps–BAAN–Siebel–People Soft–SAP

Page 4: SAP Basis Overview

Why sap?

• Rich set of modules• Data integrity• Data sharing between modules is easy• Easy administration• Only one database• It supports all available databases and OS• Upgrade from time to time• 24x7x365 global support• User friendly

Page 5: SAP Basis Overview

• Secured and reliable• Supports interface to other sap/non sap

systems• Sap supports Multilanguage available using

Unicode• Easy add-ons to add functionality to existing

system• Common programming language which

supports oops and ABAP. SAP supports JAVA

Page 6: SAP Basis Overview

6

SAP AG• SAP AG is a German software corporation that

provides enterprise software applications and support to businesses of all sizes globally. Headquartered in Waldorf, Germany, with regional offices around the world.

• SAP is the largest enterprise software company in the world (as of 2009).

• It is also the largest software company in Europe and the fourth largest globally. The company's best known products are its SAP Enterprise Resource Planning (SAP ERP) and SAP Business Objects software.

Page 7: SAP Basis Overview

Evaluation of SAP

• SAP was founded in June 1972 as System Analysis and Program development by five former IBM engineers, later it named as Systems, Applications and Products in Data Processing

Page 8: SAP Basis Overview

• In 1973, the SAP R/1 solution was launched• Six years later, in 1979, SAP launched SAP R/2• In 1981, SAP brought a completely re-

designed solution to market. However, SAP didn't significantly improve until the period between 1985 and 1990. The most major improvements came not from the founders or employees, but from a partnership with an educational institution, "Chico State".

Page 9: SAP Basis Overview

• Chico State remained SAP's only educational partner for the first few years, vastly improving and extending modules within R/2, which led to the development of R/3 with a few new modules. SAP and Chico State developed and released several versions of R/3 in 1992 through 1995.

Page 10: SAP Basis Overview

WHAT IS R/3

• 3 TIER LAND SCAPE SYSTEM• DATABASE LAYER• APPLICATION LAYER• PRESENTATION LAYER

Page 11: SAP Basis Overview

Sap releases

• SAP R/3 Release 3.1I• SAP R/3 Release 4.0B Release Date June 1998• SAP R/3 Release 4.5B Release Date March 1999• SAP R/3 Release 4.6A Release Date 1999• SAP R/3 Release 4.6B Release Date Dec 1999• SAP R/3 Release 4.6C Release Date April 2001• SAP R/3 Enterprise Release 4.70 Release Date March- Dec 2003• SAP R/3 Enterprise Edition 4.7• SAP Enterprise Central Component 5.0• SAP Enterprise Central Component 6.0• SAP R/3 ENTERPRISE PORTAL 7.0

Page 12: SAP Basis Overview

• ECC 5.0• ECC 6.0• ECC 6.0 with EHP-5

Page 13: SAP Basis Overview

SAP MODULES

• Sap is a set of integrated modules• Namely sales, finance, planning and

management, material, production, quality etc.,

• Sap is available as an integrated pack

Page 14: SAP Basis Overview

• Technical • Functional

Page 15: SAP Basis Overview

Technical consultant

• ABAP• BASIS

Page 16: SAP Basis Overview

FUNCTIONAL CONSULTANT

• SALES• CRM• FICO• HR• ETC.,

Page 17: SAP Basis Overview

BASIS

• BUSINESS APPLICATION SOFTWARE FOR INTEGRATED SOLUTIONS

Page 18: SAP Basis Overview

BASIS CONSULTANT JOB

• INSTALLATION• POST INSTALLATION• MOVING PRODUCTS FROM ONE SERVER TO

ANOTHER• MIGRATION• UPGRADATION• FIXING THE ERRORS• MONITORING SAP• SUPPORT

Page 19: SAP Basis Overview

Hardware Sizing• To analyse the business requirements of an organization level

depending upon the users data will allocate the hardware resources. We can give over business time, standby time, legacy data, o/s and DB version, data archiving. Steps for Hardware sizing:

1. Contact SAP2. Get OSSID (Online SAP Service ID)3. Login to www.service.sap.com/qsizing (It is sap official site)4. Go to Quick Sizer Tool5. Enter project name/Customer Number6. Create Project7. No. of Users (Low/Medium/High Activities)8. Amt. of legacy data.9. No. of modules.10.I) user based ii) object based.11.Select operating system of SAP12.Select database and its version.13.Select the peak load time.14.High availability.15.Data Security[Mirroring/Raid/Clustering ….etc.,]16.Save the details.17.Calculate the Results.

Page 20: SAP Basis Overview

20

Output of Hardware Sizing

• Disk size.• Memory requirement in MB• CPU requirement in SAPS [System

Application Benchmarks for Performance standards]

• SAPS are calculated based on the usage of processors.

• Analysis says that each 1500 saps we require one CPU.

Page 21: SAP Basis Overview

21

Installation

Page 22: SAP Basis Overview

22

Pre-Requisites:1. Proper hardware is received according to H/W Sizing.2. Verify SAP Software.3. Installation document from SAP

www.service.sap.com4. Read the document and highlight the steps involved

inst. guides. 5. Internet connection to resolve the runtime issues.6. Install o/s and patches7. Get a static IP address from N/W team8. Assign the IP address9. Specify an IP address and Host name entry in \etc\

hosts10. Dump the s/w into server11. Setup Virtual Memory VM=3*RAM+50012. Install current version of JAVA because SAP

Installation too requires JAVA Runtime Environment [JRE]

13. Set the environment variable JAVA_HOME & Path14. Install Oracle and Patches.

Page 23: SAP Basis Overview

23

There are 2 installation tools:R/3 setup <= 4.6Csapinst >=4.7 EE

SAP Installation consists of 3 Types:1. Central Instance Installation2. Database Instance Installation3. Dialog Instance Installation:

Page 24: SAP Basis Overview

24

SAP ArchitectureProcess Flow (LOGON)

1. User requests2. Dispatcher handles the

request3. Keeps in queue and assign

WP based on FIFO4. The work process gets the

username, password, client, logon language and the task handler interprets and hand over the task to the database process.

5. The DB process checks the credentials of the user and provides the necessary authorizations to the process.

6. The entire information is copied into the user context which is referred as ROLL OUT. (The information is copied into Roll Area which is subsequently available for all the requests made by the user)

It Consists 3 Layers.

1. Presentation Layer 2. Application Layer3. Database Layer.

Page 25: SAP Basis Overview

25

Instances is of various types

• 1. Database Instance .• 2. Central Instance. • 3. Dialogue Instance.

• 1. Database Instance: This is the Instance where database is installed.2. Central Instance: This is the Instance where Application Server/ Tier/ Layer are installed. There will be only one instance in the entire system.3. Dialogue Instance: These are the instances which are used to handle the load on the central instances. We can install as many instances as possible assuming that each instance can serve up to 200 - 500 users depending upon the type of the users.

Installation Logs:Sapinst.log - Specifies the installation success / failureSapinst_dev.log - also provides similar log in case of installation is aborted

Page 26: SAP Basis Overview

26

Types of Work Processes Even though the processes are unique at OS level SAP

differentiated between the work processes based on the nature of work.The process are determined by the instance name DVEBMGS<Instance_No>For Dialogue instances the work process will be denoted as D01, D02....

D - DialogueV - UpdateE - EnqueueB - Back groundM - MessageG - GatewayS - SpoolDVEBMGS is only available in the Central instance.D01 to DN-1 for Dialogue instances.

Page 27: SAP Basis Overview

27

Central InstanceDVEBMGS - 2112111It hosts all the process and their will be only one central instance in the entire system.

1. DIALOGUE 'D' It is only the

process which communicates interactively with the users. There should be atleast 2 Dialogue work process per instance. Dialogue work process initiates Update, Background and Spool.

2. UPDATE 'V' It is used to

update the transactions in the database. It is initiated by Dialogue process. There should be atleast 1 Update in the entire system. It is also recommended to have an update process for every 5 Dialogue.

3. ENQUEUE 'E' It is used to provide locks

for the records that are going to be updated. It ensures consistency for updates. There will be only 1 Enqueue configured in the system during the installation. It is possible to have more than one enqueue provided they are installed or configured on the central instance.

4. BACKGROUND 'B' The tasks which are

expensive or time consuming are scheduled to run in the background mode non-interactively. There should be atleast 2 background work process in the system

• 5. MESSAGE 'M' • There should be

only 1 message server in the entire R/3 system. It is used to manage all the dispatchers. It is used to load balance the requests to identify the least loaded dispatcher.

• It is also used to provide locks to the request that are coming from Dialogue instances.

• 6. GATEWAY 'G' • It is used to

provide a means of communication with SAP and NON-SAP systems. There will be only 1 gateway for each instance.

• 7. SPOOL 'S' • It is used to

print the documents to a printer or output to a fax machine etc. There should be atleast 1 Spool process in the entire system. It is also possible to configure more spool process depending on the print/ spool volume.

Page 28: SAP Basis Overview

CONTACT US For Additional Assistance , Course Details, Demo and Batch Scheduling Information, Get the details from

MAXSOFTSOLUTIONS.COMUSA: +1-8452073000

India: +91-8886060607E-Mail ID : [email protected] : www.maxsoftsolutions.com