WHAT IS ERP?

Enterprise resource planning (ERP) is a category of business-management software

typically a suite of integrated applicationsthat an organization can use to collect, store,
manage and interpret data from many business activities, including: product planning, cost.
Manufacturing or service delivery. Marketing and sales.

Advantages of ERP
With ERP to automate processes, the benefits are as follows:

Increase inventory turns

Increase inventory accuracy rate
Improve customer service
Reduce setup times
Reduce paper work.
Reduce inventory costs
Provide a unified customer database usable by all applications
Provide greater and effective control on account.
Faster response and follow ups to customers
Improves supply demand linkage with remote locations and branches in
different locations
Higher quality, less re-work

List of top 10 ERP software packages

(1) Epicor
(2) Infor
(3) Microsoft Dynamics
(4) SAP
(5) Oracle
(6) JD Edwards
(7) People Soft
(8) Baan

What is SAP

SAP stands for Systems Applications and Products in Data Processing.

It was founded in 1972 by five former IBM engineers In Germany.
SAP SE is a German multinational software corporation that makes enterprise software to manage
business operations and customer relations. SAP is headquartered in Walldorf, Baden-Wrttemberg,
Germany, with regional offices in 130 countries.

SAP : Founded: April 1, 1972, Weinheim, Germany

Founders: Hasso Plattner, Klaus Tschira, Claus Wellenreuther, Dietmar Hopp, Hans-Werner Hector
CEO: Bill McDermott
Headquarters: Walldorf, Germany
Revenue: 20.79 billion EUR (2015)
Stock price: SAP (ETR) 69.11
Availability: SAP NetWeaver
Subsidiaries: SuccessFactors, Concur Technologies, Fieldglass, more

Diffrence between ERP and SAP

ERP which stands for Enterprise Resource Planning is more of an Industrial

Terminology. Many of the ERP products do add it as a prefix to their product. SAP used
to call their product as SAP ERP.

Later on, when upgrades came in and newer versions came, SAP changed the name to
SAP ECC where ECC stands for Enterprise Central Component.
Earlier it used to be called as SAP R/3, later changed to SAP ERP and their latest version
is SAP ECC 6.0

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

SAP ERP is enterprise resource planning software developed by the German company
SAP SE. SAP ERP incorporates the key business functions of an organization. The latest
version (SAP ERP 6.0) was made available in 2006. The most recent Enhancement
Package (EHP7) for SAP ERP 6.0 was released in 2013.

SAP R/3 History & Release

SAP R/3 is the former name of the main enterprise resource planning software
produced bySAP AG. 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 or billing.
History of SAP R/3
The first version of SAPs flagship enterprise software was a financial Accounting system
named R/1called as YSR. This was replaced by R/2 at the end of the 1970s. SAP R/2 was
in 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 multi-currency and
multi-language capabilities built in. With the advent of distributed clientserver
computing SAP AG brought out a clientserver version of the software calledSAP
R/3 (The R was for Real-time data processing and 3 was for 3-tier). 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. It was renamed SAP ERP and later
again renamedECC (ERP 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 isSAP ERP 6.0
Releases
SAP R/3 Release 1.0A Release Date 6 July 1992
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 R/3 Enterprise Central Component 5.0
SAP R/3 Enterprise Central Component 6.0
Organization
SAP R/3 was arranged into distinct functional modules, covering the typical functions in
place in an organization. The most widely used modules were Financial 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 others
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.

Why Not SAP (SAP ISSUES)

No cache memory in ICM
In SAP R/3 architecture, clients treated as dumb terminals.
Complex Architecture
No Support for other languages.
WHY SAP (Advantages):
Multi Languages
Multi-Currency
Integrated
Secure Information
Best Business Practices

List of DATA BASES SUPPORT BY SAP

The following Database can be used in SAP software. The
functionality/programming technique is same for all database system.
a) Oracle
b) MS SQL
c) Informix
d) Sybase
e) Adabas D
f) DB2 for AIX
g) DB2/400
Supported Operating System for SAP
The SAP business suites can be installed on the following platforms (Operating
systems):
a) MS Windows NT
b) OS/400
c) Unix
d) Solaris
e) AIX
f) HP UX
g) Sinux
SAP MODULES Both FUNCTIONA and TECHNICAL

Main Functional SAP ERP Modules

1. FICO (Finance & Controlling)
2. HR (Human Resource)
3. PP (Production Planning)
4. MM (Material Management)
5. SD (Sales & Distribution)
6. PM (Plant Maintenance)
7. PS (Project System)
8. QM (Quality Management)
9. BIW (Business Information Warehousing)
SAP TECHNICAL MODULES :

SAP ABAP module Advanced Business Application Programming

 SAP Basis module Basis Admin, administration of SAP

SAP HANA
SAP BI module Business Intelligence
SAP BPC module Business Planning and Consolidation
SAP BODI module Business Objects Data Integrator
SAP EP module -Enterprise Portal
SAP MDM module Master Data Management
SAP Security module Security for enterprise operations
SAP Solution Manager module Manages technical support for
distributed systems
SAP XI module Allows the implementation of cross-system
processes on services
SAP PI module Enterprise application integration (EAI)software

SAP CORE VERSIONS:

1.
2.
3.
4.
5.
6.
7.

CRM (Customer Relationship Management)

SCM (Supply Chain Management)
SEM (Strategic Enhanced Management)
APO (Advanced Planner Optimizer)
EP (Enterprise Portal)
SRM (Supplier Relationship Management)
XI (Exchange Infrastructure)

SAP BASIS :

Basis is a set of programs and tools that act as an interface with Database,
Operating system, communication protocols and other SAP modules like
FI,HCM, SD etc. This course will introduce different features of Basis.
SAP BASIS Consultant Responsibilities:

1. Starting & Stopping R/3 System.

2. SAP User Administration.
3. Daily Monitoring Tasks.
4. Spooling and Printing.
5. Background Processing.
6. R/3 System Landscape.
7. Client Administration.
8. Backup & Restore.
9. R/3 Administrative Task.
10. SAP R/3 installation and router Installation.

How to Monitor SAP Systems

This document is intended for all persons who are responsible to monitor Production Systems
in SAP. Following activities are explained in detail with screenshots:
Check SAP Process Overview SM51/ SM50
System Wide Work Process Overview SM66
Users Logged On AL08/ SM04
Spool Requests SP01
Check SAP Locks SM12
Check for Updates SM13
Check System Log SM21
Check Background Jobs SM37
SAP Buffers ST02
Workload Analysis ST03
Operating System Monitor ST06
ABAP Dump Analysis ST22
Database Analysis ST04
Check Database PerformanceDB02
Check E-Mail and Fax Messages SOST
Check for failed IDOCs WE02/ WE05

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@

SAP LAND SCAPE Details:

Landscape is like a server system or like a layout of the servers or
some may even call it the architecture of the servers viz.
SAP is divided into three different landscapes DEV, QAS and
PROD.
(1) DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180Unit Test.
(2) QAS may again have mutiple clients for ex: 300- Integration Test, 700 to
710 Training.
(3) PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or
they have been using in their previous implementations or how is the client's
business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients.
Whenever you think you are satisfied with your configuration and you think you
can use it moving forward, you RE-DO it in the golden client (remember, this is a
very neat and clean client and you cannot use it for rough usage). As you re-do
everything that you had thought was important and usable, you get a transport
request pop up upon saving every time. You save it under a transport request and
give your description to it. Thus the configuration is transported to the Unit Test
client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100
(golden) client. This is a configuration only client. Now upon a successful transport
by the Basis guy, you have all the configuration in the Testing client, just as it is in
the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you cannot even access SPRO (Display IMG) screen. It's
a transaction only client where you perform the unit test. Upon a satisfactory unit
test, you move the good configuration to the next SERVER (DEV). The incorrect

or unsatisfactory configuration is corrected in Golden (may again as well be

practiced in the sandbox prior to Golden) and accordingly transported back to 180
(Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may
rather call it the 'ultimate' reference client for all the good, complete and final
configuration that is being used in the implementation.
In summary:
Landscape: is the arrangement for the servers
IDES: is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY ----> PRODUCTION
DEVELOPMENT: is where the the consultants do the customization as per the
company's requirement.
QUALITY: is where the core team members and other members test the
customization.
PRODUCTION: is where the live data of the company is recorded.
A request will flow from Dev. ->Qual ->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are
given a sandbox server where you do all the configuration/customization as per the
companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done
is development server and saved in workbench requests, to be transported to
Production server.
3. Production Server: This is the last/ most refined client where the user will work
after project GO LIVE. Any changes/ new develpoment is done is development
client and the request is transported to production.
These three are landscape of any Company. They organised their office in these
three way. Developer develop their program in Development server and then
transport it to test server. In testing server tester check/test the program and then
transport it to Production Server. Later it will deploy to client from production
server.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@

SAP Administrator's Frequently Used Transactions

SM04/AL08 User List

SM51 Display Application Server

SM37 Background Job Overview

SM50/SM66 Manage Work Processes

SM12 Mange Lock Entries

PFCG Maintain Roles

SM13 Manage Update Records

SM21 Analyze System Log

SM02 Send System Messages

SAP Administration

Starting and stopping SAP instance(s)

User administration setup and maintenance

Authorization / Role / Profiles setup and maintenance

Setup SAP security

Maintenance of systems health

Monitor system performance and logs

Spool and print administration

Maintain system landscape

Transport management systems

Manage change requests

Create / Manage batch jobs

Backup schedule, run, and monitor backup of SAP

Apply patches, kernel, and OSS notes