What is mean by SID in SAP?

SID

        Each R/3 installation (SAP system) of a database server and several app servers running the application logic is uniquely identified by a single SID (SAP System Identification), SAP system name or SAP SID can be of maximum 3 alphanumeric characters and its first character must be an alphabet such as D11,SDK, K56, etc.

There some Reserved SIDs in SAP We unable use this SIDs.

No.	SID	Status	Description
1	ADD	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
2	ADM	Prevented by SWPM.	SQL keyword, when used as SAPSID queries could break.
3	ALL	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
4	AMD	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID.
5	AND	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
6	ANY	Prevented by SWPM. Listed as reserved since SAP NetWeaver 7.0 SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
7	ARE	Prevented by SWPM. Listed as reserved since 4.6C SR2.	ODBC reserved keyword, when used as SAPSID queries could break.
8	ASC	Prevented by SWPM. Listed as reserved since SAP NetWeaver 7.0 SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
9	AUX	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'AUX' is the Windows Pseudofile for Auxilary Device.
10	AVG	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID queries could break.
11	BIN	Prevented by SWPM SP06 and later. Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 or lower with problems to distinguish between 'bin' and 'BIN' on Windows and i5.
12	BIT	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
13	CDC	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Reserved keyword on MS SQL Server, can lead to data loss when used as SAPSID or DBSID.
14	COM	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. 'COM' is the Windows Pseudofile for a communication port.
15	CON	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'CON' is the Windows Pseudofile for Console input/output.

16	DAA	Prevented by SWPM 1.0 SP06 and later, for non Diagnostics Agent installations. Used by SAP Solution Manager Diagnostics Agent	In case 'DAA' is already used, the values 'DA1' … 'DA9' are tried and offered in the installer UI when installing an SAP Solution Manager Diagnostics Agent.
17	DBA	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
18	DBM	Prevented by SWPM for DB2 for Windows and Unix.	Cannot be used as DBSID.
19	DBO	Prevented by SWPM. Listed as reserved since SWPM 1.0 SP6.	Reserved keyword/schema on SQL Server, when used as SAPSID or DBSID queries could break.
20	DTD	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server Java. Requested by SUM 1.0 for Application server Java with problems to distinguish between 'dtd' and 'DTD' on Windows and i5.
21	END	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
22	EPS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
23	EXE	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 or lower with problems to distinguish between 'exe' and 'EXE' on Windows and i5.
24	FOR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
25	GET	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID.
26	GID	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
27	IBM	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
28	INT	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
29	KEY	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
30	LOG	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'log' and 'LOG' on Windows and i5.
31	LPT	Prevented by SWPM. Listed as	Cannot be used as SAPSID or DBSID.

 

		reserved since ERP 6.0 EHP5.	'LPT' is the Windows Pseudofile for a parallel printer port.
32	LIB	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'lib' and 'LIB' on Windows and i5.
33	MAP	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
34	MAX	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. SQL Server function.
35	MEM	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 with problems to distinguish between 'mem' and 'MEM' on Windows and i5.
36	MIG	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'mig' and 'MIG' on Windows and i5.
37	MIN	Prevented by SWPM.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
38	MON	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
39	NIX	Prevented by SWPM, Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Reserved for internal ABAP transport tools (tp) related to cofiles read error
40	NOT	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
41	NUL	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'NUL' is the Windows Pseudofile for NULL device.
42	OFF	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
43	OLD	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
44	OMS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
45	OUT	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. Reserved future keyword, when used as SAPSID queries could break in future.

 

46	PAD	Prevented by SWPM for MSSQL. Listed as reserved since ERP 6.0 EHP5.	MS SQL Server reserved keyword, when used as SAPSID or DBSID queries could break
47	PRN	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'PRN' is the Windows Pseudofile for Printer output.
48	RAW	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
49	REF	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
50	ROW	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
51	SAP	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Requested from ABAP transport tools (tp) related to anonymization. Furthermore sapadm (<sid>adm) is the operating system owner of the SAP Hostagent executables.
52	SET	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
53	SGA	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
54	SHG	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
55	SID	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
56	SQL	Prevented by SWPM. Listed as reserved since 4.6C SR2.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
57	SUM	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
58	SYS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SAP internal identifier. Cannot be used as SAPSID or DBSID.
59	TMP	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
60	TOP	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	SQL keyword, when used as SAPSID or DBSID queries could break.
61	TRC	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'trc' and 'TRC' on Windows and i5.
62	UID	Prevented by SWPM. Listed as	Cannot be used as SAPSID or DBSID.

 

		reserved since 4.6C SR2.	Should not be used for SAP application server ABAP or Java.
63	USE	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	MS SQL Server reserved keyword, when used as SAPSID or DBSID queries could break
64	USR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as DBSID.
65	VAR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Should not be used as SAPSID for SAP application server ABAP. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'var' and 'VAR' on Windows and i5.

 

SAP Standard Users

SAP Standard Users

SAP USER'S

1. SAP*
2. DDIC
3. EARLYWATCH

SAP*

     

       SAP* is the super user of SAP system and used for doing client copy. SAP* is the only user in the

SAP System that does not require a user master record, but that is instead defined in the system code

itself. SAP* has by default the password 'pass', as well as unlimited system access authorizations.

When you install your SAP System, a user master record is defined for SAP* with the initial password

as the master password (set during installation) in clients 000 and 001. When temporary license expires only SAP* user is allowed to login to client 000 to install permanent license.

Note: Now S/4hana not required SAP* for Run Client copy.

DDIC

     

       It is the maintenance user for ABAP Dictionary and software logistics. It is used for any upgrade or

installation type of work like,

1. TMS Configuration,
2. Applying Support Packages and Add-ons.
3. Implementing SAP Notes etc.

• Best practice is not to use DDIC user but create a new user by copying from DDIC.
• DDIC is the only user that is allowed to log on to the SAP System during an upgrade.
• DDIC is hard coded to do some things other IDs cannot and restricted from doing some things that other IDs can.

EARLYWATCH

        

    The SAP Early Watch service uses this user. This user should only be used for Early Watch functions

like monitoring and performance analysis. 

Note: This user no longer available in S/4hana platform.

SAP SUM tool phases overview

SAP SUM TOOL PHASES OVERVIEW

There the five phases in SAP SUM Tool.

• Extraction
• Configuration
• Checks
• Pre-processing
• Execution
• Post Processing

Extraction:

Following activities performed in this phase:

1. DDIC username and password
2. Scanning of download directory where all the patches are placed
3. Extract files to move to EPS/in
4. Check SPAM version.
5. <SID>adm credentials
6. Mapping of table classes to container
7. Pre-upgrade note list implementation

Configuration:

Following activities performed in this phase.

1. Main upgrade configuration, where you will give input parameters for -Advanced (expensive downtime optimizes, higher complexity, high resource assignment)
2. Keep database archiving on
3. Execution strategy for transaction SGEN
4. Maximum number of processes to be used for load generation. SGEN Processes
5. Batch Process(Uptime)
6. Batch Process(Downtime)
7. Maximum number of DDL processes (Uptime and Downtime)
8. Number of parallel import processes (R3trans -Uptime and Downtime)
9. Parallel Phases (Uptime and downtime)
10. Update Instances
11. Enhancement package inclusion
12. Add-On selection
13. Modification Adjustment (SPDD transport request and SPAU transport request)

Checks:

Following activities performed in this phase:

1. Insufficient space in database, Create four table spaces with script
2. Space checks
3. BW checks and phases
4. Activation and conversion checks
5. Modification support
6. Preliminary upgrade processing
7. List Locked SAP objects

Pre-Processing:

This is the pre-downtime phase where all the pre-tasks need to complete by SUM like

1. Check for locked objects
2. ABAP Workbench locking
3. Run shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)
4. SPDD Adjustments

Execution: 

Sum tool downtime is called as execution where actual are copied from Shadow to Main Instance and system were unavailable during the downtime.

1. Merging of shadow and Real Instance
2. system upgrade
3. Table conversion

Post Processing: 

This is post processing step of SUM just after downtime.

1. SPAU change
2. Backup

SAP GUI for Windows 7.60 Changed Features

SAP GUI for Windows 7.60 Changed Features:

Not supported for saplogon.ini and related configuration files

As of SAP GUI for Windows 7.60, the old configuration format for SAP Logon entries (saplogon.ini, sapmsg.ini, saproute.ini) is no longer supported by SAP GUI for Windows. SAP GUI for Windows can still handle this old format for compatibility reasons, because there may be external applications needing this old format, but using SAP GUI for Windows 7.60 with the old format is not supported. Therefore, all installations of SAP GUI for Windows 7.60 and newer must use SAP UI Landscape. 

Changed integration with SAP Business Client

If SAP GUI for Windows and SAP Business Client are installed together, the SAP Logon (Pad) Desktop icon and the Business Client Desktop icon are installed. Additionally, file associations for SAP Shortcuts are created for both SAP Logon (Pad) as well as SAP Business Client. When starting an SAP Shortcut, the user can decide which program to run. With this, the old installation component Install SAP GUI Desktop Icon / Shortcuts even though SAP Business Client is installed is obsolete.

Reference by : SAP Help

SAP Basis - All about SAP GUI

SAP Basis - All about SAP GUI

SAP Basis - All about SAP GUI

SAP GUI is a client tool which is used to access remote central server and runs on different operating systems like Microsoft Windows, Linux, Unix, Mac, etc. This is used to manage and access SAP applications like SAP ECC, S/4HANA and SAP Business Intelligence System.

Some Features in SAP GUI are:

1. A single face GUI for accessing all SAP components such as SAP ERP,SAP S4HANA, BI, CRM, SCM, XI, and SRM.

2. Users are allowed to login with their preferred language, as the same GUI can be used in different languages like(English, Germany).

3. This module is downward compatible for supporting all SAP applications that are below the current GUI Version. In other words, the latest version of GUI supports the lower versions of SAP components with ease.

4. SAP GUI offers role based and easy to access SAP menus for reducing the GUI load.

5. It allows access across low speed connections and displays screens without graphics/logos as they tend to consume more network traffic.

GUI SAP boasts of ergonomically designed interfaces for configuring GUI font size, colors, logos, visual designs and custom layouts.

Supported Available SAP GUI for Different Platforms

The following are the supported available versions for different platforms −

• SAP GUI for the Windows environment
• SAP GUI for the Java(TM) environment
• SAP GUI for HTML / Internet Transaction Server (ITS)
• SAP GUI has been released separately for Windows and Java support and the latest version for Windows and Java is 7.6.

SAP Basis - Overview

                       SAP Basis refers to the SAP BASIS Administrator or SAP Netweaver Administrator of SAP system that includes activities like installation, Upgrade and configuration, load balancing, and performance of SAP applications running on SAP ABAP Stack and SAP Java stack. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. This tutorial will help you through the Basic information of SAP Basis.

The key responsibilities of SAP Basis Administrator include:

• SAP System installation, upgrade, and maintenance of SAP    systems.
• SAP configuring, monitoring, tuning, and troubleshooting.
• SAP scheduling and executing the SAP transport system, design of interfaces     between SAP and external systems.
• Load balancing on servers and Performance management of different                   components.
• Managing servers and different services

With the help of SAP Basis, different SAP modules like FI,PP,MM,SD,PS and other modules can integrate and communicate with each other.

SAP Basis supports the installation and configuration of SAP applications on different operating systems like Windows, Unix, Linux, etc. and different databases like Microsoft SQL Server, Oracle, IBM DB2, HANA, MAXDB for back end database.

SAP BASIS Administrator Tasks Performed under Different Roles:

1. SAP Transport Admin

   => Change control across SAP landscape

2.  SAP Interface Analyst

 

  => Analyze and Monitor

  => Interfaces within SAP landscape

3. SAP System Admin

 =>Maintain system health

 =>Monitor and tune system performance

4. SAP Data Base Administrator (DBA)

 =>Manage integrity of SAP database objects

 =>Manage backups and restore

5. SAP DDIC Manager

 =>Manage changes to SAP data dictionary

6. SAP ABAP Specialist

 =>Troubleshoot and tune ABAP programs

 =>Apply correction to program

7. SAP Security Specialist

 =>Design, monitor, and manage System access to SAP landscape

8. SAP Batch Administrator

 =>Create and manage batch jobs across landscape

9.  SAP Solutions Specialist

 =>Installation of Application / Add-On

 =>Migrate Operating System / Database 

 =>Upgrade SAP version

 =>Archiving of SAP Data