Scribd
Upload
3 views

SAP Basis JD

The document provides an overview of SAP architecture, detailing the types of SAP instances, including Central, Database, and Dialog instances, and their respective roles. It also describes various work processes essential for SAP operation, such as Dialog, Background, Enqueue, and Update processes. Additionally, it highlights the importance of the message service for communication between distributed dispatchers in the R/3 system.

Uploaded by

tanuyadav911
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views

SAP Basis JD

The document provides an overview of SAP architecture, detailing the types of SAP instances, including Central, Database, and Dialog instances, and their respective roles. It also describes various work processes essential for SAP operation, such as Dialog, Background, Enqueue, and Update processes. Additionally, it highlights the importance of the message service for communication between distributed dispatchers in the R/3 system.

Uploaded by

tanuyadav911
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Contents

1. SAP Architecture 18. Transport Management System (STMS)


2. SAP Instances 19. Spool Administration (SPAD, SP01)
3. SAP Active Servers (SM51) 20. Kernel Upgrade
4. Work process overview (SM50) 21. Applying Patches using (SPAM, SAINT)
5. Transaction Lock/Unlock (SM01) 22. Backup and Recovery (DB12)
6. Users overview/Active users (SM04) 23. SAP DBA Calendar (DB13)
7. System log (SM21) 24. Lock management (SM12)
8. ABAP Dump (ST22) 25. Update Administration
9. Database Size / Table Space / Space check 26. CCMS Alert Monitoring (RZ20/RZ21)
(DB02, BRTOOLS) 27. Trouble Shooting
10. BRTOOLS 28. Start and Stop SAP
11. Client Administration 29. Daily System Check
12. Logical System Creation (SALE) 30. WebAS
13. User management (SU01, SUIM, EWZ5, PFCG, 31. SAP Net weaver
SU53, SU24, SU25, SU10) 32. BW Administration
14. System Profiles (RZ10, RZ11) 33. Portal User Administration (SSO)
15. RFC Destinations setting (SM59) 34. ECC fundamentals
16. Operation mode Configuration (RZ04, SM63, 35. Q&A
RZ03)
17. Logon Load balancing (SMLG)
SAP Instances

SAP instance defines a group of resources such as memory, work processes and so on, usually in support of a single
application server or database server within a client/server environment. Application servers share the same
memory areas and are controlled by the same dispatcher process. There are 3 types of Instances available in SAP
system as defined below.

1. Central Instance (Unique Instance or SID name for an SAP Server)


2. Database Instance (Which contains data with its own SID)
3. Dialog Instance (Used for Load balancing purpose when needed)

SAP SID: 3 Alphanumeric Characters except some reserved ones, SAP SID may look like DEV, QAS, PRD, D01, Q01, P01
etc.

System Number: Number which differentiates between multiple instances in a single host. System Number varies
from 00 – 99 (75 and 99 are reserved for TCP/IP use).

Work Processes

There are different types of work process on which SAP Instance depends to run as described below.

 Dialog (D) – Used by frontend users or frontend process; every dispatcher requires at least two dialog work
processes.
 Background (B) – Used for long running Jobs; at least two for each R/3 system (more than one allowed for each
dispatcher).
 Enqueue (E) – Used for Locking / Unlocking purposes; only one enqueue work process is needed for each system.
 Update (V1) – Used for critical updates into database; at least one for each R/3 System (more than one allowed
for each dispatcher).
 Update (V2) – Used for normal updates after critical updates.
 Gateway (G) – Allows communication between R/3, R/2 and external application systems.
 Spool (S) – Used for printing from SAP; at least one process.
 Message Service (M) – Used for messaging purpose. The message server (MS or M) communicates between the
distributed dispatchers within the R/3 System and is therefore the prerequisite for scalability using several
parallel-processing Application servers.

You might also like