Download Sap Basis Extract of Certification PDF

TitleSap Basis Extract of Certification
File Size2.0 MB
Total Pages330
Table of Contents
                            Password Control in SAP Systems
Document Text Contents
Page 1

Support Phase

It is used to provide the support to End Users. There are various types of
Supports provided by the partners to the customers. Partner (Partner) is a
company which provides support services. Ex: IBM, HP, HCL, TCS, WIPRO,

1 L1 Support Tier-1 Level-1 Support-1
2 L2 Support Tier-2 Level-2 Support-2
3 L3 Support Tier-3 Level-3 Support-3
4 L 4Support Tier-4 Level-4 Support-4

1. Level-1 Support : It is a front end support or end user support to
Reset the Passwords lock and unlock users. GUI related issues.
(Installation, patches, upgrade) performance check list activities etc…

2. Note : Very less privileges are assigned to the users there will be no
input on the system by this users there will be no input on the system
by this users i.e. they can’t Delete, Drop, Change objects in the
system. It is also referred as monitoring Job.

3. Level-2 Support : The reports from the Level-1 consultants along with
recommendations are evaluated and ensure that they are resolved.
Level-2 consultant handle assignments of roles, Background Jobs
rescheduling, data transfers, notes etc…..

4. The issues which could not be resolved can be escalated to Level-3

5. Level-3 Support : Recommend the parameters for Tuning, Support
Package application, Scheduling down times, working with SAP,
database activities etc….

6. Level-4 Support ( Onsite ) :The consultant works with data center and
knowledge of O/S, R/3, DB etc is required for this. Responsible to Start
Up the BOX. Responsible for Backup, Restore, Recovery, DR, Standby,
Clustering, Mirroring, H/W migration,. UPS aircom etc.

Based on the nature of the company the following activities are also

7. Security

8. Performance


Page 2

9. Data Base

10. O/S

11. Transports

12. Normal BASIS Support

We can also propose to perform all the activities.

Roles and Responsibilities:

13. Define the Checklist

14. Working on Tickets/Requests/Cases

15. Configuring Work Processes

16. Configuring Buffers

17. Resolving Runtime Issues

18. Working with Dialog Process, Update Process, background
Process, Message, Spool and Enqueue Processes

19. Define Background Jobs and Monitoring

20. Monitoring Critical Update

21. Define the Printers

22. Working with SAP Archiving

23. Creating RFC Destinations

24. Define various methods for data transfer

25. Monitor EDI and IDOC

26. Release change request and import target systems

27. Applying patches notes etc…

28. Configuring CCMS and monitoring

29. Configuring logon load balancing


Page 165

locally. Use
- startsap name= nr= SAPDIAHOST= to start an R/3 instance and
- stopsap name= nr= SAPDIAHOST= to stop an R/3 instance (the executables
sapstart.exe, sapsrvkill.exe and sapntwaitforhalt.exe must be in the same directory)

To provide a stable startup procedure, a parameter read sequence (also known as
the parameter replace sequence) is defined during startup as follows:
R/3 processes read the appropriate parameters from the R/3 kernel, from the NT
system environment variables, and from the NT Registry environment variables.
The default profile
“\\\sapmnt\\SYS\profile\default.pfl” is read. Profile values already defined in the
R/3 kernel are replaced with the values in the default profile.
The instance profile
“\\\sapmnt\\SYS\profile\__” is read.
Profile values already defined in the default profile or in the R/3 kernel are replaced
with the values defined in the instance profile.
This procedure ensures that system parameter values reflect not only the instance
profile but also the values in the default profile and the R/3 kernel.
The SAP service reads only the start profile and the default profile. The R/3 kernel
(disp+work.exe) reads only the default profile and the instance profile. If you
change the default profile, you must restart the SAP service (including the R/3
instance). If you only change the instance profile, you only need to restart R/3 using
the MMC.


Page 166

R/3 work directories contain trace files and error files for messages relating to the
startup of work processes. Each R/3 instance has a separate work directory
containing information that may not be found in the R/3 System log.
The work directory files are initialized in chronological order. During startup, the
SAP service executable SAPSTARTSRV.EXE writes:
Database logs to the file STDERR1
Message server logs to the file STDERR2
Dispatcher logs to the file STDERR3
To define the level of information written to the developer trace files, set the profile
parameter “rdisp/TRACE” in the instance profile. The possible values for this
parameter are:
0: Write only errors (no traces)
1: Write error messages and warnings (default)
2: Write error messages and a short trace
3: Write error messages and the complete trace


Similer Documents