Vous êtes sur la page 1sur 19

BY MR.

BABU (OASIS TECHNOLOGIES)

Chapter-1
SAP-ERP INTRODUCTION
Table of Contents-Chapter: 1
SAP-ERP Introduction ................................................................................................................................... 2
Enterprise Resource Planning ................................................................................................................... 2
Uses of ERP................................................................................................................................................ 3
Client Server System ................................................................................................................................. 4
SAP People ................................................................................................................................................ 5
Three Tier Architecture ............................................................................................................................. 6
Different Components of 3 Tier Architecture ........................................................................................... 9
ABAP/4 Introduction ............................................................................................................................... 11
Open and Native SQL .............................................................................................................................. 12
Some Configuration Details for ECC 6.0 Installation .............................................................................. 13
Initial Screen of SAP ................................................................................................................................ 16
Transaction Codes ................................................................................................................................... 17
ABAP Workbench .................................................................................................................................... 19
Object Navigator ..................................................................................................................................... 19

1
BY MR. BABU (OASIS TECHNOLOGIES)
SAP-ERP Introduction
SAP- Systems Applications & Products in Data processing

About SAP:

 SAP was found in June 1972 as “System Analysis and Program Development”.
 The name was later changed as “Systems Application and Products in Data processing”.
 SAP is a Germany based company. It was named as SAP-AG.
 SAP is world number one in ERP and third highest revenue independent software
provider.
 SAP is into almost all the industries such as Automobiles, Banking, Electronics etc….
 Impherical Chemical Industries (ICI) was the first customer of SAP.

Enterprise Resource Planning (ERP):

 It is used to integrate different data sources and business units.

Figure 1.1: ERP Centralized System

 In olden days Manufacturing Requirement Planning (MRP-II) and Material Requirement


Planning (MRP) are used before ERP is evolved
 MRP and MRP-II does not have integration between different business units.
 ERP is evolved from MRP-II
 MRP-II was evolved from MRP.
ERPMRP2MRP

2
BY MR. BABU (OASIS TECHNOLOGIES)
Uses of ERP:

 It is the centralized system to provide the strong integration between the different
business or functional areas.
 It provides the correct information on time to take the business decisions.
 The higher management (Directors, Managers, Leads etc…) with the knowledge of ERP
will be able to achieve their goals and targets using proper implementation of ERP.
 Better business plan and resource utilization.
 On time delivery and customer satisfaction.

Other ERP vendors:

There are more than 150 ERP vendors in market. Among them SAP is the best vendor. Few
other vendors are:

 Oracle
 PeopleSoft
 Microsoft etc….

Differences between ERP and MRP:

 In business point of view ERP is expanded from the co-ordination of the manufacturing
process to an Enterprise wide backend integration process.
 In technical point of view, ERP is expanded from the legacy implementation to more
flexible tires architecture.(Client-Server Architecture)

3
BY MR. BABU (OASIS TECHNOLOGIES)

Client- Server System:

Client:

It is a software or hardware combination which can send the requests for services from the
central respiratory system.

Server:

It is a software or hardware combination which can provide the services to a group of clients in
the shared environment.

Figure 1.2: Client- Server System

4
BY MR. BABU (OASIS TECHNOLOGIES)

SAP People:

SAP people are categorized as below:

Figure 1.3: SAP People

5
BY MR. BABU (OASIS TECHNOLOGIES)
Three Tier Architecture:
It is an arrangement of the systems or layers. There are three layers involved in SAP
architecture.

1. Presentation Layer
2. Application Layer
3. Database Layer

1. Presentation Layer:
 It is an environment from where all the requests are sent for the services from the
central respiratory system.
 The services or results are displayed in the presentation layer.

2. Application Layer:
 It receives the requests from the presentation layer to get them processed in the work
process.
 It also sends back the services to the presentation layer
 There will be more than one application layer.

3. Database Layer:
 It is a central depository of the data. It provides the data base services to a group of
clients in the shared environment.

Different Types of Architecture:

Following are different types of architectures:

a. SAP R/1  One Tier Architecture


b. SAP R/2  Two Tier Architecture
c. SAP R/3  Three Tier Architecture
d. MYSAP  For small scale industries

Here R - Real Time

6
BY MR. BABU (OASIS TECHNOLOGIES)

i. Single Tier Architecture:

 In this architecture, all the three layers are in the same system.

System

Presentation Layer

Application Layer

Database Layer

Figure 1.4: Single Tire Architecture

ii. Two Tier Architecture:

 In this architecture, there is a separate system for Presentation layer. Application layer
and Database layers are in another system.

System-1
Presentation Layer

Application Layer
System-2

Database Layer

Figure 1.5: Two Tier Architecture

7
BY MR. BABU (OASIS TECHNOLOGIES)

iii. Three Tier Architecture:

 In this architecture there is a separate system for each layer.

System-1
Presentation Layer

System-2
Application Layer

System-3
Database Layer

Figure 1.6: Three Tier Architecture

8
BY MR. BABU (OASIS TECHNOLOGIES)
Different Components of Three Tier Architecture:

 Following are different components of three tier architecture:

Figure 1.7: Different Components of Three Tier Architecture

9
BY MR. BABU (OASIS TECHNOLOGIES)
1. Presentation Layer:-

 It is an environment from where all the users requests are sent and display the results
or services.

2. Application Layer:-

 It receives the request from the presentation layer to get them processed.
 It also sends back the services (result) to a presentation layer.
 Following are the different components in application layer:
a. Dispatcher.
b. Gate way.
c. Shared Memory.
d. Work Process.

a. Dispatcher:

 It is a link between the presentation layer and the work process. It receives the request
from the presentation layer and sends them to an appropriate relevant work process to
get them processed.
 It also sends back the services (result) to the presentation layer.

b. Layer:

 It is a communication protocol of the cross application components such are RFC


(Remote Function Call), BAPI (Business Application Program Interface)..etc.
 It provides a link between two SAP systems
 (SAP R/3  SAP CRM) and a link between and non-SAP systems (SAP 
.NET/JAVA)…….etc.….

c. Shared Memory:

 It is a common main memory which can be shared by all the work process.

d. Work Process:

 It is a component to execute (process) the application or requests.


 Each work process is linked with a context which can run the application or request.
 Following are different types of work process:

10
BY MR. BABU (OASIS TECHNOLOGIES)
Background Work Process: It takes care of all the background job requests. Background
jobs are scheduled to execute the application without user interaction periodically (hours,
daily, monthly)……

Dialogue Work Process: It is used to process all kind of screen requests.

Enqueue Work Process: All the lock requests are handed by this work process.

Message Work Process: All the message requests are processed in this work process.

Spool Work Process (print): All the print requests are processed in this work process.

Update Work Process: All the database update requests are processed in this work
process.

3. Database Interface (or) Database management system:

 It converts all ABAP open SQL statements in to the database compatible statements to
access or to maintain the data in any database.

Note: SAP is database independent software because of the database interface layer in the
architecture.

Example: Database could be any oracle (or) SAP DB………….etc.

ABAP/4 Introduction:

 It is the programing language for SAP platform.


 It was founded in 1980 as ‘Generic Report Preparation Processor’.
 The name was later changed as ‘Advanced Business Application Programing’, 4th
generation language.
 It is used to develop the new application, enhance the existing application and
implement the cursor specific requirement in SAP environment.
 The open SQL statements are used in ABAP to interact with any kind of database.
 Following are some of the open SQL statements:
a. Select: To access or extract the data from the databases.
b. Modify: To modify the data in the database.
c. Delete: To delete the data from database.
d. Insert: To insert a new data.
e. Update: To update the existing data.

11
BY MR. BABU (OASIS TECHNOLOGIES)
Open and Native SQL:

 Open SQL is a set of SQL statements which can interact with any kind of database.
 Native SQL is specific to the particular database.
 The ABAP statement EXEC……..ENDEXEC are used to specify native sql.
Example: EXEC
*Native SQL
.
.
.

END EXEC

Note:
 In ABAP we mostly work with open SQL.
 The statements mentioned with in EXEC and ENDEXEC cannot be syntaxically checked.
 The table which is not available in SAP (specific to database) can be accessed using
native SQL.

Figure 1.8: Open and Native SQL

12
BY MR. BABU (OASIS TECHNOLOGIES)
Some Configuration Details for ECC 6.0 Installation:

 Hard Disk Drive – 250GB (500GB advisable)


 RAM -- 2GB and above (4GB is advisable)
 OS -- Windows Server 2003 and above
 Processor -- Dual Core and above

Steps to start the SAP server (SAPMMC):

 Double click on an icon ‘SAP Management Console’.


 Expand SAP systems by pressing an icon + if required.
 Right click on the required system name (ECC).
 Click on start.
 Enter the password. Example: india123(default password)
 Click on ‘ok’ button.

Note: Wait until the color of the system icon changes to green.
(Grey  Yellow  Green)

 Click on icon refresh to get the system status refreshed.

Steps to stop the server (SAPMMC):-

 Maximize SAPMMC window.


 Right click on the system required name (ECC).
 Click on ‘stop’.
 Click on ‘yes’ button.

Note: Wait until the color of the system icon becomes grey color.
(Green  Yellow  Gray)

 Click on ‘close’ icon to close SAPMMC.


 Click on ‘no’ button.

13
BY MR. BABU (OASIS TECHNOLOGIES)
Steps to add the system to login pad:

 Double click on an icon ‘SAPLOGIN’.


 Click on ‘new item’ button.
 Click on ‘next’ button.
 Enter the required details; such are Description, Application server address, System
number and System ID.

Example:

Description – ( )

Application server – ( )

System number – ( )

System ID – ( )

 Click on ‘finish’ button.

Note:
 The button change item is used to change the existing system details.
 The button delete item is used to delete the unwanted system from logon pad.

Steps to logon to SAP system:

 Double click an icon ‘SAP logon’.


 Select the required system (DEV-Development system).
 Click on logon button.
 Enter the required logon credentials such are client no, username and password.
Example: Client ( )
User ( )  not case sensitive
Password ( )  case sensitive
Language ( )  default in EN-English
 Press ‘Enter’.

14
BY MR. BABU (OASIS TECHNOLOGIES)
Note:
 The client no’s will be specific for the projects in the real time. The client no could be
100/200/300…………….. But not 8* series number.
 In the real time the user names will be unique in each project. The usernames could
be the combination of our names.
Example: (NAME) or (Z50074) (up to 12char)
But not SAPUSER

Note:
 The below logon details can be used to logon to IDES (Internet Demonstration and
Evaluation System).
Client : 800
Username : sapuser
Password : india123
(For practice session only)

15
BY MR. BABU (OASIS TECHNOLOGIES)
Initial Screen of SAP:

 The initial screen of SAP is divided into the following different paths.

Figure 1.9: Initial Screen of SAP

Command Field:

 The command field on the standard tool bar is used to execute or access the transaction
codes in SAP.

16
BY MR. BABU (OASIS TECHNOLOGIES)
Transaction codes:

 The transaction codes are the commands or short cuts to execute or access the
corresponding predefined applications.
 In Sap each screen is linked with the unique transactional code.
 The transactional codes are mainly categorized in to two:
1. Standard transaction codes
2. Custom transaction codes

1. Standard Transaction Codes:

 The standard transactional code is the system provided transaction codes which are
linked with the predefined standard applications.
 The standard transaction codes could be the combination of only alphabets and the
alpha numericals.
Example: SQVI, SE11, SM30,……..etc.
SQ*  SAP Query
SE* System Engineering
SM*  System Machine

Note: The ABAP technical consultants mostly work with the transaction codes starts with SE*
and rarely work with SM*.

2. Custom Transaction Codes:-

 The custom transaction codes are maintained by the technical consultants.


 The custom transaction codes are maintained using the standard predefined transaction
code SE93.
 The custom object names should start with either ‘z*’ or ‘y*’.

Note: In most of the projects the custom object names start with ‘Z*’.

 The custom transaction codes could also be combination of only alphabets and alpha
numerals.

Example: ZCUSTCODE, ZCUST11, ZCUST-TCODE…………….

17
BY MR. BABU (OASIS TECHNOLOGIES)
Note:
 There should not be any space or special characters in the custom object names but
can be separated with underscores (_).
Example: ZCUST _CUST ZCUSTCODE
ZCUST$CODE ZCUST_CODE
(Not preferable) (Preferable)
 The underscores (_) must not be a second character in the custom object names.
Example: Z_CUSTCODE ZCU_STCODE
(Preferable) (Preferable)

Shortcuts to work with the transaction codes:-

 The below shortcuts are used to work with the transaction codes in the system:

1) /o + transaction code + enter  to execute the transaction code in another new system.
Example: /ose11 (enter)

Note: Up to six sessions can only be opened in a system.

2) /n + transaction code + enter  to execute transaction codes on the same session.


Example: /nzcust_code (enter) or /nycust_code (enter)
3) /n + ex + enter  to exit out off the system.
Example: /nex(enter)
4) /n + end + enter  to end the system by giving conformation command.

Steps to execute the transaction code:

 Enter the required transaction code (/nse11) press enter button

18
BY MR. BABU (OASIS TECHNOLOGIES)
ABAP work bench:

 The ABAP work bench is a set of tools which can be used to develop the applications,
change the existing applications and implement the customer specific business
requirements in the SAP environment.

Following are some of the useful work bench tools:

 Data Dictionary (DDIC – SE11): To maintain central depository of the data and data
definitions. DDIC is independent to the data base.
 ABAP Editor (SE38): To maintain the different types of programs.
 Message Class (SE91): To maintain the global messages.
 Function Builder (SE37): To maintain global functions.
 Menu painter (SE41): To maintain customer specific menu items and push buttons.
 Screen painter (SE51): To maintain the screens.
 Form painter (SET1 or SMARTFORMS): To maintain the different types of forms.

Objects Navigator (SE80):-

 It is the central point of entry to work with any kind of work bench objects such as data
dictionary objects, programs, function groups……… etc.
 The transaction code or SE80 or SE84 is used to work with an object navigator.
 The object navigator look as below

Figure 1.10 Object Navigator

19

Vous aimerez peut-être aussi