SAP Basis is a crucial module that supports the technical foundation for all SAP applications.

Below are some of the most important topics in SAP Basis along with their corresponding
transaction codes (T-codes):

1. User and Authorization Management

 SU01: User Maintenance

 PFCG: Role Maintenance
 SU10: Mass Changes for Users
 SUIM: User Information System

2. System Monitoring and Performance Tuning

 ST22: ABAP Dump Analysis

 SM37: Job Monitoring
 ST03N: Workload and Performance Statistics
 ST06: OS Monitoring
 ST02: Tune Summary

3. Client Administration

 SCC4: Client Administration

 SCCL: Local Client Copy
 SCC9: Remote Client Copy
 SCC5: Client Delete

4. Transport Management System (TMS)

 STMS: Transport Management System

 SE09: Transport Organizer (Workbench)
 SE10: Transport Organizer (Customizing)
 STMS_IMPORT: Import Transport Requests

5. Background Jobs Management

 SM36: Define Background Job

 SM37: Job Monitoring
 SM50: Process Overview
 SM66: Global Work Process Overview

6. Database Administration

 DB02: Database Performance Analysis

 DBACOCKPIT: Database Cockpit
 DB12: Backup Logs
 DB13: DBA Planning Calendar

7. System Configuration
  RZ10: Edit Profiles
 RZ11: Profile Parameter Maintenance
 SPRO: SAP Reference IMG (Implementation Guide)
 SMLG: Maintain Logon Groups

8. Patch and Kernel Management

 SPAM: Support Package Manager

 SAINT: Add-On Installation Tool
 SUM: Software Update Manager (External tool)

9. System Logs and Traces

 SM21: System Log

 ST11: Display Developer Traces
 ST22: ABAP Dump Analysis

10. SAP Note and OSS Connection

 SNOTE: SAP Note Assistant

 OSS1: Logon to Online Service System

11. Batch Input Monitoring

 SM35: Batch Input Monitoring

12. Work Process Management

 SM50: Work Process Overview

 SM66: Global Work Process Overview

13. System Administration

 SMLG: Logon Group Maintenance

 SCC3: Client Copy Log
 SCU3: Table History

14. Data Archiving

 SARA: Archive Administration

15. Job Scheduling Management

 SCMA: Central Process Scheduling by Redwood

These T-codes are essential for performing various administrative tasks in SAP Basis.
Mastering these will help in effectively managing and maintaining the SAP system.
 User and Authorization Management

User and Authorization Management in SAP Basis involves creating, maintaining, and
managing user accounts and their access rights within the SAP system. Below are key tasks
involved in user and authorization management, along with the corresponding transaction
codes (T-codes) and brief explanations for each task.

1. User Maintenance (SU01)

 T-code Definition: SU01 is used for user creation, maintenance, and deletion.
 Steps:
1. Create User:
 Enter T-code SU01.
 Click on the 'New User' icon.
 Enter the desired username and click 'Create'.
 Fill in details such as address, logon data, defaults, parameters, roles,
and profiles.
 Save the user.
2. Change User:
 Enter T-code SU01.
 Enter the username to be changed and click 'Change'.
 Modify the necessary details and save the changes.
3. Delete User:
 Enter T-code SU01.
 Enter the username to be deleted and click 'Delete'.
 Confirm the deletion.

2. Role Maintenance (PFCG)

 T-code Definition: PFCG is used to create and maintain roles, which are collections
of authorizations assigned to users.
 Steps:
1. Create Role:
 Enter T-code PFCG.
 Enter the role name and click 'Create Role'.
 Fill in the description and click on the 'Menu' tab to add transactions,
reports, or web links.
 Click on the 'Authorization' tab and select 'Change Authorization Data'
to define specific permissions.
 Generate the role by clicking on 'Generate'.
2. Assign Role to User:
 Go to the 'User' tab in PFCG.
 Enter the username to which the role should be assigned.
 Save the assignment.
3. Copy Role:
 Enter T-code PFCG.
 Enter the source role name and click 'Copy Role'.
 Provide the target role name and confirm the copy operation.
3. Mass User Changes (SU10)

 T-code Definition: SU10 is used for performing mass changes to multiple user
accounts simultaneously.
 Steps:
1. Select Users:
 Enter T-code SU10.
 Use the selection criteria to list users (e.g., by user type, role, or
profile).
 Select the users you want to change.
2. Change Attributes:
 Click on the 'Change' button.
 Modify the necessary attributes such as roles, profiles, or parameters.
 Save the changes.

4. User Information System (SUIM)

 T-code Definition: SUIM is used to generate reports related to users, roles, and
authorizations for analysis and auditing.
 Steps:
1. Execute Reports:
 Enter T-code SUIM.
 Select the desired report type (e.g., user by roles, user by profiles, user
by authorization).
 Enter the selection criteria and execute the report.
2. Analyze User Data:
 Use the report results to analyze user assignments, role distributions,
and authorization objects.
 Export or print the reports for documentation or further analysis.

5. Profile Generator (PFCG)

 T-code Definition: PFCG is also used to maintain authorization profiles, which are
sets of authorizations generated from roles.
 Steps:
1. Maintain Authorization Profiles:
 Enter T-code PFCG.
 Enter the role name and navigate to the 'Authorization' tab.
 Select 'Change Authorization Data' and adjust the authorization
objects.
 Generate the profile and save the role.

6. Authorization Check (SU53)

 T-code Definition: SU53 is used to display the last authorization check that failed for
the current user.
 Steps:
1. Check Authorization:
 Enter T-code SU53 after receiving an authorization error.
  The screen will display the failed authorization check.
 Analyze the missing authorization and adjust user roles or profiles
accordingly in PFCG.

7. User Comparison (PFUD)

 T-code Definition: PFUD is used to perform user comparison and synchronize user
master records with current role authorizations.
 Steps:
1. Run User Comparison:
 Enter T-code PFUD.
 Select the roles to be compared and updated.
 Execute the user comparison to synchronize user master records with
current role authorizations.

8. Authorization Objects and Fields (SU21)

 T-code Definition: SU21 is used to maintain authorization objects and fields, which
define the permissions required to perform specific actions.
 Steps:
1. Maintain Authorization Objects:
 Enter T-code SU21.
 Select the authorization class and object to be maintained.
 Define or modify the fields and permissible values.
 Save the changes.

Summary

User and Authorization Management in SAP Basis ensures that users have appropriate access
to perform their job functions securely. Regular monitoring and updates are essential to
maintain system security and compliance.
 System Monitoring and Performance Tuning

System Monitoring and Performance Tuning are critical aspects of SAP Basis administration.
These activities ensure that the SAP system runs efficiently and reliably. Below are key tasks
involved in system monitoring and performance tuning, along with the corresponding
transaction codes (T-codes) and brief explanations for each task.

1. ABAP Dump Analysis (ST22)

 T-code Definition: ST22 is used to analyze ABAP runtime errors (short dumps).
 Steps:
1. View Dumps:
 Enter T-code ST22.
 Select the date range to display dumps.
 Click on a specific dump to view detailed information.
2. Analyze and Resolve:
 Analyze the error details provided in the dump.
 Determine the root cause and implement necessary corrections (e.g.,
code changes, configuration adjustments).

2. Job Monitoring (SM37)

 T-code Definition: SM37 is used for monitoring background jobs.

 Steps:
1. List Jobs:
 Enter T-code SM37.
 Enter selection criteria such as job name, user name, or job status.
 Execute the search to list the relevant jobs.
2. Analyze Jobs:
 Select a job from the list to view its details.
 Check the job log for errors or performance issues.
 Take appropriate action (e.g., rescheduling, modifying job parameters).

3. Workload and Performance Statistics (ST03N)

 T-code Definition: ST03N is used to analyze workload and performance statistics.

 Steps:
1. Select Time Period:
 Enter T-code ST03N.
 Choose the desired time period (e.g., last hour, last day).
2. View Statistics:
 Navigate through different views like "User Profile", "Transaction
Profile", or "Response Time Distribution".
 Analyze the data to identify performance bottlenecks.
3. Optimize Performance:
 Based on the analysis, take steps to optimize performance (e.g., tuning
SQL queries, adjusting workload distribution).
4. OS Monitoring (ST06)

 T-code Definition: ST06 is used to monitor operating system statistics.

 Steps:
1. View OS Data:
 Enter T-code ST06.
 Select the relevant server from the list.
 View various OS metrics such as CPU utilization, memory usage, and
disk I/O.
2. Analyze Metrics:
 Analyze the metrics to identify potential performance issues at the OS
level.
 Coordinate with the OS team to address any identified issues.

5. Tune Summary (ST02)

 T-code Definition: ST02 is used to display SAP buffer and memory statistics.
 Steps:
1. View Buffer Stats:
 Enter T-code ST02.
 View different buffer types such as Program buffer, Table buffer, and
Extended memory.
2. Analyze and Tune:
 Analyze the buffer quality and swap rates.
 Adjust buffer parameters if necessary to improve performance (via
profile parameter changes).

6. System Log (SM21)

 T-code Definition: SM21 is used to view the system log for important system
messages and errors.
 Steps:
1. View Logs:
 Enter T-code SM21.
 Select the time period for which you want to view logs.
 Execute the search to display the logs.
2. Analyze Logs:
 Review the logs to identify errors and warnings.
 Take appropriate actions to resolve issues based on log entries.

7. Developer Traces (ST11)

 T-code Definition: ST11 is used to view developer traces for detailed technical
information on various components.
 Steps:
1. View Trace Files:
 Enter T-code ST11.
 Select the desired trace file from the list.
2. Analyze Trace Files:
  Analyze the trace file content to diagnose issues at a technical level.
 Coordinate with developers to resolve any identified issues.

8. Global Work Process Overview (SM66)

 T-code Definition: SM66 is used to display a global overview of work processes

across all application servers.
 Steps:
1. View Work Processes:
 Enter T-code SM66.
 The system displays the status of work processes across all servers.
2. Analyze Work Processes:
 Identify long-running or stuck work processes.
 Take appropriate actions such as terminating or restarting work
processes.

9. Work Process Overview (SM50)

 T-code Definition: SM50 is used to monitor and manage work processes on a

specific application server.
 Steps:
1. View Work Processes:
 Enter T-code SM50.
 The system displays the status of work processes on the selected
server.
2. Manage Work Processes:
 Identify problematic work processes.
 Take actions such as cancelling or debugging specific work processes.

10. Database Performance Analysis (DB02)

 T-code Definition: DB02 is used to monitor database performance and space

statistics.
 Steps:
1. View DB Statistics:
 Enter T-code DB02.
 View statistics on tablespace usage, database growth, and other
performance metrics.
2. Analyze and Optimize:
 Analyze the statistics to identify performance issues.
 Work with the database administrator to optimize database
performance (e.g., indexing, partitioning).

Summary

Effective system monitoring and performance tuning ensure the SAP system runs smoothly
and efficiently. Regular monitoring helps in early detection and resolution of issues, while
performance tuning optimizes the system's overall performance.
 Client Administration

Client Administration in SAP Basis involves managing clients within the SAP system.
Clients are self-contained units in an SAP system with their own user master records,
customizations, and data. Below are key tasks involved in client administration, along with
the corresponding transaction codes (T-codes) and brief explanations for each task.

1. Client Administration (SCC4)

 T-code Definition: SCC4 is used for client administration, including creating, modifying, and
deleting clients.
 Steps:
1. Create a Client:
 Enter T-code SCC4.
 Click on the 'New Entries' button.
 Enter the client number, description, and other required details such as
client role and logical system.
 Save the entries.
2. Modify a Client:
 Enter T-code SCC4.
 Select the client to be modified and click on 'Change'.
 Modify the necessary details and save the changes.
3. Delete a Client:
 Enter T-code SCC4.
 Select the client to be deleted and click on 'Delete'.
 Confirm the deletion.

2. Local Client Copy (SCCL)

 T-code Definition: SCCL is used to perform a client copy within the same SAP system.
 Steps:
1. Initiate Local Client Copy:
 Enter T-code SCCL.
 Select the source client and the target client.
 Choose the copy profile (e.g., SAP_ALL, SAP_CUST, SAP_USER).
 Schedule the copy job immediately or at a later time.
2. Monitor Copy Process:
 Monitor the background job via T-code SM37 to ensure successful
completion.
3. Post-Copy Actions:
 Check the log for any errors and perform necessary post-copy steps such as
adjusting client-specific settings.

3. Remote Client Copy (SCC9)

 T-code Definition: SCC9 is used to copy clients between different SAP systems.
 Steps:
1. Configure RFC Connection:
  Ensure an RFC connection is established between the source and target
systems via T-code SM59.
2. Initiate Remote Client Copy:
 Enter T-code SCC9.
 Select the RFC destination, source client, and target client.
 Choose the copy profile.
 Schedule the copy job immediately or at a later time.
3. Monitor Copy Process:
 Monitor the background job via T-code SM37.
4. Post-Copy Actions:
 Review the log for errors and perform necessary post-copy steps.

4. Client Export/Import (SCC8 / SCC7)

 T-code Definition: SCC8 is used to export a client, and SCC7 is used to import a client.
 Steps:
1. Export Client (SCC8):
 Enter T-code SCC8.
 Select the source client and specify the export options.
 Choose the transport target system and create the transport request.
 Start the export process and monitor it via T-code SM37.
2. Import Client (SCC7):
 Enter T-code SCC7 in the target system.
 Select the transport request containing the client data.
 Start the import process and monitor it via T-code STMS_IMPORT.

5. Client Deletion (SCC5)

 T-code Definition: SCC5 is used to delete a client and its data.

 Steps:
1. Initiate Client Deletion:
 Enter T-code SCC5.
 Select the client to be deleted.
 Confirm the deletion and schedule the background job.
2. Monitor Deletion Process:
 Monitor the background job via T-code SM37.
3. Post-Deletion Actions:
 Review the log for any errors and ensure the client has been completely
removed.

6. Client Copy Log (SCC3)

 T-code Definition: SCC3 is used to view logs of client copy operations.

 Steps:
1. View Copy Logs:
 Enter T-code SCC3.
 Select the log you want to review.
 Analyze the log entries to verify the success or identify issues in the client
copy process.
7. Table History (SCU3)

 T-code Definition: SCU3 is used to view changes to tables that are critical for client
management.
 Steps:
1. View Table Changes:
 Enter T-code SCU3.
 Select the relevant table or change document.
 Analyze the changes to understand modifications to client-specific data.

Summary

Client administration in SAP Basis involves creating, copying, modifying, and deleting
clients within the SAP system. Regular monitoring and maintenance of clients are essential to
ensure data integrity and system performance.
 Transport Management System (TMS)

The Transport Management System (TMS) in SAP Basis is used to manage, control, and
track changes in the SAP system landscape. It allows the transport of configuration settings,
developments, and customizations from one SAP system to another within a landscape (e.g.,
from Development to Quality Assurance and then to Production). Below are key tasks
involved in TMS, along with the corresponding transaction codes (T-codes) and brief
explanations for each task.

1. Transport Management System Overview (STMS)

 T-code Definition: STMS is the central transaction code used to configure and
manage the transport system.
 Steps:
1. Access TMS:
 Enter T-code STMS.
 The initial screen provides an overview of the transport domain,
systems, and transport routes.
2. Configure TMS:
 To configure TMS, go to System Overview and ensure all systems are
properly configured.
 Define the transport routes (standard, consolidation, and delivery
routes) to manage how transport requests move between systems.

2. Transport Organizer (SE09 / SE10)

 T-code Definitions:
o SE09: Transport Organizer for workbench requests (ABAP development
objects).
o SE10: Transport Organizer for customizing requests (configuration changes).
 Steps:

1. Create Transport Request:

 Enter T-code SE09 or SE10.
 Click on 'Create' to create a new transport request.
 Fill in the required details, such as the description and owner.
2. Display and Modify Requests:
 Use the search criteria to list existing transport requests.
 Select a request to display its details or modify it.
3. Release Transport Request:
 After making changes, release the transport request by selecting it and
clicking 'Release'.
 This action makes the request ready for export to other systems.

3. Import Transport Requests (STMS_IMPORT)

  T-code Definition: STMS_IMPORT is used to import transport requests into the
target system.
 Steps:
1. Access Import Queue:
 Enter T-code STMS_IMPORT.
 Select the target system to view its import queue.
2. Import Requests:
 Select the transport request(s) to be imported.
 Click on 'Import' and choose the import options (e.g., import all,
specific request).
3. Monitor Import Process:
 Monitor the import status and logs to ensure successful importation.
 Address any errors or issues that arise during the import process.

4. Transport Landscape Configuration (STMS)

 T-code Definition: STMS is also used to configure the transport landscape and
manage transport routes.
 Steps:
1. Define Transport Routes:
 Enter T-code STMS.
 Go to Overview -> Transport Routes.
 Define and configure the transport routes to determine how transport
requests flow between systems.
2. Configure Systems in the Transport Domain:
 Ensure that each system in the landscape is correctly added to the
transport domain.
 Configure system-specific settings and roles (e.g., development,
quality assurance, production).

5. Transport Logs and Monitoring (STMS and STMS_IMPORT)

 T-code Definitions:
o STMS: General monitoring and logs.
o STMS_IMPORT: Specific import logs and status.
 Steps:

1. View Transport Logs:

 Enter T-code STMS and navigate to Logs to view the overall transport
logs.
 For import-specific logs, use T-code STMS_IMPORT.
2. Analyze Transport Issues:
 Analyze the log entries to identify any errors or warnings.
 Take necessary actions to resolve issues, such as re-importing requests
or adjusting configurations.

6. Transport Directory (AL11)

 T-code Definition: AL11 is used to access and manage the transport directory.
  Steps:
1. Access Transport Directory:
 Enter T-code AL11.
 Navigate to the directory path related to transport files (usually
/usr/sap/trans).
2. Manage Transport Files:
 View and manage the files and directories associated with transport
requests.
 Ensure proper file management and address any file-related issues.

7. Transport Request Tracking (SE01)

 T-code Definition: SE01 is used for advanced transport request tracking and
management.
 Steps:
1. Track Transport Requests:
 Enter T-code SE01.
 Use various filters to search and track transport requests.
2. Detailed Analysis:
 Select a request to view its detailed history, including changes,
releases, and imports.
 Use the information to track the lifecycle of transport requests and
ensure proper management.

Summary

Transport Management System (TMS) in SAP Basis is essential for managing changes and
ensuring consistency across the SAP landscape. Proper configuration and monitoring of
transport requests facilitate efficient and error-free transport operations. Regular use of the
above T-codes and steps ensures smooth transport processes and system stability.
 Background Jobs Management

Background Jobs Management in SAP Basis involves scheduling, monitoring, and managing
background jobs to automate repetitive tasks and ensure they run without manual
intervention. Below are key tasks involved in background jobs management, along with the
corresponding transaction codes (T-codes) and brief explanations for each task.

1. Job Scheduling (SM36)

 T-code Definition: SM36 is used to schedule background jobs.

 Steps:
1. Create a Job:
 Enter T-code SM36.
 Enter a job name in the Job Name field.
 Optionally, specify a job class to prioritize the job.
 Click on the "Start condition" button to set the job's start time and
conditions.
2. Define Job Steps:
 Click on the "Steps" button to define the job's steps.
 For each step, specify the program, variant (if any), and user under
which the program will run.
3. Save the Job:
 Review the job's details and click the "Save" button to schedule the
job.

2. Job Monitoring (SM37)

 T-code Definition: SM37 is used to monitor and manage background jobs.

 Steps:
1. List Jobs:
 Enter T-code SM37.
 Specify selection criteria such as job name, user name, job status, and
time period.
 Click the "Execute" button to list the jobs matching the criteria.
2. Monitor Job Status:
 Review the list to monitor the status of jobs (scheduled, released,
ready, active, finished, or canceled).
 Click on a job to view its details, including logs and history.
3. Manage Jobs:
 Use the options to start, stop, delete, or reschedule jobs as needed.

3. Job Log (SM37)

 T-code Definition: SM37 is also used to view the log of background jobs.
 Steps:
 1. Access Job Log:
 Enter T-code SM37 and list the jobs.
 Select a job from the list and click the "Job Log" button to view its log.
2. Analyze Job Log:
 Review the log entries to analyze the job's execution.
 Identify and troubleshoot any errors or warnings recorded in the log.

4. Job Documentation (SM37D)

 T-code Definition: SM37D is used to create and manage documentation for

background jobs.
 Steps:
1. Create Documentation:
 Enter T-code SM37D.
 Select the job for which you want to create documentation.
 Enter the documentation details, including description, purpose, and
instructions.
2. Save Documentation:
 Save the documentation to make it available for future reference and
audit purposes.

5. Job Scheduling Assistant (SM36C)

 T-code Definition: SM36C is used for advanced job scheduling with a wizard-like
interface.
 Steps:
1. Use Scheduling Assistant:
 Enter T-code SM36C.
 Follow the step-by-step instructions provided by the wizard to
schedule a job.
 Define job parameters, steps, and start conditions through the guided
interface.
2. Complete Scheduling:
 Review the job summary and finish the scheduling process.

6. Job Deletion (SM37)

 T-code Definition: SM37 is also used to delete background jobs.

 Steps:
1. List Jobs for Deletion:
 Enter T-code SM37.
 Specify the selection criteria to list the jobs to be deleted.
 Select the jobs from the list.
2. Delete Jobs:
 Click the "Delete" button to remove the selected jobs from the system.
 Confirm the deletion.

7. Job Management Overview (SM39)

  T-code Definition: SM39 is used to get an overview of job management.
 Steps:
1. Access Job Management Overview:
 Enter T-code SM39.
 Use the overview to monitor job schedules, job definitions, and job
statistics.
2. Analyze Job Data:
 Review the provided data to analyze job execution patterns and
performance.
 Use the insights to optimize job scheduling and resource allocation.

8. Batch Job Spool Administration (SP01)

 T-code Definition: SP01 is used to manage spool requests generated by background

jobs.
 Steps:
1. List Spool Requests:
 Enter T-code SP01.
 Specify selection criteria such as spool request number, user, or time
period.
 Execute the search to list spool requests.
2. Manage Spool Requests:
 View, delete, or reprint spool requests as necessary.
 Analyze spool logs to troubleshoot issues with job outputs.

9. Job Workload Analysis (SM36P)

 T-code Definition: SM36P is used to analyze the workload of background jobs.

 Steps:
1. Access Workload Analysis:
 Enter T-code SM36P.
 Specify the selection criteria for workload analysis.
2. Review Workload Data:
 Review the analysis report to understand the distribution of job
workloads.
 Use the data to balance and optimize job scheduling.

Summary

Background Jobs Management in SAP Basis ensures efficient and automated execution of
tasks. Regular monitoring, scheduling, and management of background jobs using the
mentioned T-codes help maintain system performance and reliability.

4o
 Database Administration

Database Administration in SAP Basis involves managing the database that underlies the
SAP system to ensure data integrity, performance, and availability. Below are key tasks
involved in database administration, along with the corresponding transaction codes (T-
codes) and brief explanations for each task.

1. Database Monitoring (DB12)

 T-code Definition: DB12 is used to monitor the database backup logs and status.
 Steps:
1. Access Database Backup Logs:
 Enter T-code DB12.
 Review the status of recent database backups.
2. Check Backup Details:
 Click on individual backup entries to view detailed logs and status
information.
3. Verify Backup Consistency:
 Ensure that backups are completed successfully and are consistent.

2. Database Performance (DB02)

 T-code Definition: DB02 is used to monitor database performance and space

statistics.
 Steps:
1. Access Database Performance Statistics:
 Enter T-code DB02.
 View the various performance metrics, such as tablespace usage,
buffer quality, and database growth.
2. Analyze Performance Data:
 Identify any performance bottlenecks or unusual growth patterns.
 Take corrective actions like reorganizing tables or adding indexes.
3. Monitor Tablespaces:
 Check tablespace usage and ensure there is enough free space.
 Extend tablespaces if necessary.

3. Database Activities (DB13)

 T-code Definition: DB13 is used to schedule and monitor database-related jobs, such
as backups and reorganization tasks.
 Steps:
1. Schedule Database Jobs:
 Enter T-code DB13.
 Select the type of job to schedule, such as a database backup, update
statistics, or database reorganization.
  Set the schedule and parameters for the job.
2. Monitor Scheduled Jobs:
 Use DB13 to monitor the status of scheduled database jobs.
 Ensure jobs complete successfully and address any failures.
3. Review Job Logs:
 Access the logs for completed jobs to verify their success and
troubleshoot any issues.

4. Tablespace Management (DB02)

 T-code Definition: DB02 is also used to manage tablespaces in the database.

 Steps:
1. Monitor Tablespace Usage:
 Enter T-code DB02.
 View the usage statistics for all tablespaces.
2. Manage Tablespaces:
 Identify tablespaces that are running low on space.
 Perform actions such as extending tablespaces or reorganizing tables.
3. Check Tablespace Fragmentation:
 Analyze the fragmentation level of tablespaces and take necessary
actions to reduce fragmentation.

5. Database Reorganization (DB14)

 T-code Definition: DB14 is used to manage and monitor database reorganizations.

 Steps:
1. Plan Reorganization:
 Enter T-code DB14.
 Plan and schedule reorganization activities to optimize database
performance.
2. Execute Reorganization Tasks:
 Execute the planned reorganization tasks.
 Monitor the progress and ensure tasks complete without issues.
3. Analyze Reorganization Results:
 Review the results of reorganization tasks and verify improvements in
performance and space utilization.

6. Database Backup and Restore (DB12 / DB13)

 T-code Definitions:
o DB12: Monitor database backup logs.
o DB13: Schedule and monitor database backup jobs.
 Steps:

1. Schedule Backups:
 Enter T-code DB13.
 Schedule regular database backup jobs, specifying parameters like
frequency and backup type (full, incremental).
2. Monitor Backup Jobs:
 Use DB13 to monitor the status of backup jobs.
Ensure backups are completed successfully.
3. Restore Database:
 In case of a failure, use the appropriate database-specific tools and
procedures to restore the database from backups.

7. Database Consistency Check (DB20)

 T-code Definition: DB20 is used to perform consistency checks on the database.

 Steps:
1. Run Consistency Checks:
 Enter T-code DB20.
 Select the checks to be performed and execute them.
2. Review Check Results:
 Analyze the results of the consistency checks.
 Identify and resolve any inconsistencies found in the database.

8. Update Statistics (DB13)

 T-code Definition: DB13 is also used to schedule and monitor the update of database
statistics.
 Steps:
1. Schedule Update Statistics Job:
 Enter T-code DB13.
 Schedule the job to update database statistics, which helps the database
optimizer choose the best execution plans.
2. Monitor the Job:
 Ensure the job completes successfully and analyze the impact on query
performance.
3. Verify Statistics:
 Check the updated statistics and verify that they are accurate and up-
to-date.

9. SQL Command Execution (DBACOCKPIT / DB02)

 T-code Definitions:
o DBACOCKPIT: A comprehensive tool for database administration.
o DB02: Specific for database performance monitoring and administration.
 Steps:

1. Execute SQL Commands:

 Enter T-code DBACOCKPIT or DB02.
 Navigate to the SQL Command Editor.
 Execute custom SQL queries to monitor, manage, or troubleshoot the
database.
2. Analyze Results:
 Review the results of SQL commands to diagnose issues or gather
necessary data.
3. Perform Administrative Tasks:
  Use SQL commands to perform administrative tasks, such as user
management or space allocation.

10. Database User Management (DBA User Tools)

 T-code Definition: Typically managed using the database-specific user tools within
the DBACOCKPIT.
 Steps:
1. Create/Modify Users:
 Access the DBA user management tools via DBACOCKPIT.
 Create new database users or modify existing ones.
2. Assign Roles and Privileges:
 Assign the necessary roles and privileges to database users.
 Ensure users have the appropriate permissions for their tasks.
3. Monitor User Activities:
 Regularly monitor user activities to ensure compliance and security.

Summary

Effective database administration in SAP Basis ensures the stability, performance, and
security of the SAP system's underlying database. Regular monitoring, maintenance, and
optimization using the mentioned T-codes help maintain data integrity and system
performance.
 System Configuration
System Configuration in SAP Basis involves setting up and maintaining the parameters and
settings that define how the SAP system operates. This includes configuring system profiles,
tuning system parameters, managing RFC destinations, setting up operation modes, and
configuring background jobs. Below are key tasks involved in system configuration, along
with the corresponding transaction codes (T-codes) and brief explanations for each task.

1. System Profile Management (RZ10)

 T-code Definition: RZ10 is used to maintain the instance profiles that contain
configuration parameters for the SAP system.
 Steps:
1. Load Profiles:
 Enter T-code RZ10.
 Select the profile you want to maintain (e.g., DEFAULT.PFL,
instance-specific profile).
2. Edit Parameters:
 Choose the operation mode (extended maintenance) to edit profile
parameters.
 Add, change, or delete parameters as required.
3. Activate Profile:
 Save the changes and activate the profile.
 Restart the instance to apply the changes.

2. System Parameter Tuning (RZ11)

 T-code Definition: RZ11 is used to display and change the runtime parameters of the
SAP system.
 Steps:
1. Display Parameters:
 Enter T-code RZ11.
 Enter the parameter name or search for it to display its details.
2. Change Parameters:
 Click on "Change" to modify the parameter value.
 Apply the changes and verify their impact on system performance.
3. Documentation:
 Use the "Display Documentation" button to understand the purpose
and implications of each parameter.

3. Operation Modes and Work Processes (RZ04)

  T-code Definition: RZ04 is used to define and manage operation modes and work
process distribution.
 Steps:
1. Define Operation Modes:
 Enter T-code RZ04.
 Create new operation modes or modify existing ones.
 Define the distribution of work processes for each operation mode.
2. Assign Instances:
 Assign the operation modes to the relevant instances.
3. Activate Operation Modes:
 Save the changes and activate the operation modes to optimize
resource usage.

4. Client Administration (SCC4)

 T-code Definition: SCC4 is used for client administration, including creating,

modifying, and deleting clients.
 Steps:
1. Create/Modify Clients:
 Enter T-code SCC4.
 Add new clients or modify existing ones, specifying client roles and
logical system assignments.
2. Delete Clients:
 Select clients to be deleted and remove them from the system, ensuring
data consistency and compliance.
3. Set Client Options:
 Configure client-specific options such as client copy protection and
cross-client data changes.

5. RFC Destination Management (SM59)

 T-code Definition: SM59 is used to create and maintain RFC (Remote Function Call)
destinations.
 Steps:
1. Create RFC Destinations:
 Enter T-code SM59.
 Choose "Create" and specify the type of RFC destination (e.g., ABAP
Connection, TCP/IP Connection).
 Enter the required connection parameters and save the destination.
2. Test RFC Connections:
 Select the RFC destination and use the "Test Connection" button to
verify connectivity.
3. Maintain RFC Connections:
 Regularly update and maintain RFC destinations to ensure reliable
communication between systems.

6. Background Job Configuration (SM36)

 T-code Definition: SM36 is used to schedule and manage background jobs.

 Steps:
 1. Schedule Jobs:
 Enter T-code SM36.
 Create a new job by specifying job name, class, and scheduling
parameters.
2. Define Job Steps:
 Add steps to the job, specifying programs or reports to be executed.
3. Save and Monitor Jobs:
 Save the job and monitor its execution using T-code SM37.

7. Transport Management System (STMS)

 T-code Definition: STMS is used to manage and control transports across the SAP
landscape.
 Steps:
1. Configure Transport Routes:
 Enter T-code STMS.
 Define and manage transport routes to control the flow of changes
between systems.
2. Import Transports:
 Use T-code STMS_IMPORT to import transport requests into target
systems.
3. Monitor Transports:
 Track transport requests and monitor their status to ensure successful
deployment of changes.

8. System Monitoring (SM21, ST22, SM66)

 T-code Definitions:
o SM21: System log to view system messages and errors.
o ST22: Dump analysis to check ABAP short dumps.
o SM66: Global work process overview.
 Steps:

1. Monitor System Logs (SM21):

 Enter T-code SM21.
 Review system logs to identify and resolve system errors and issues.
2. Analyze ABAP Dumps (ST22):
 Enter T-code ST22.
 Review and analyze short dumps to troubleshoot ABAP runtime errors.
3. Global Work Process Overview (SM66):
 Enter T-code SM66.
 Monitor work process utilization and resolve performance bottlenecks.

9. Spool Administration (SPAD)

 T-code Definition: SPAD is used for spool administration and printer management.
 Steps:
1. Configure Printers:
 Enter T-code SPAD.
  Add and configure printers, specifying device types and output
formats.
2. Manage Spool Requests:
 Monitor and manage spool requests to ensure proper printing of
documents.
3. Troubleshoot Printing Issues:
 Resolve printer errors and troubleshoot spool request problems.

10. System Health Check (DBACOCKPIT)

 T-code Definition: DBACOCKPIT is used for comprehensive database and system

health monitoring.
 Steps:
1. Monitor Database Health:
 Enter T-code DBACOCKPIT.
 Review database performance metrics and health indicators.
2. Check System Performance:
 Monitor system performance and identify potential bottlenecks or
issues.
3. Perform Regular Maintenance:
 Schedule and perform regular maintenance tasks to ensure optimal
system performance.

Summary

System Configuration in SAP Basis is essential for ensuring the smooth operation and
optimal performance of the SAP system. Regular monitoring, parameter tuning, and proper
configuration management using the mentioned T-codes help maintain system stability and
reliability.
 Patch and Kernel Management
Patch and Kernel Management in SAP Basis involves updating the system with the latest
patches and kernel versions to ensure security, stability, and optimal performance. This
process includes applying support packages, kernel upgrades, and other patches to keep the
SAP system up to date. Below are the key tasks involved in patch and kernel management,
along with the corresponding transaction codes (T-codes) and brief explanations for each
task.

1. Applying Support Packages (SPAM)

 T-code Definition: SPAM (Support Package Manager) is used to apply support

packages to the SAP system.
 Steps:
1. Download Support Packages:
 Download the necessary support packages from the SAP Service
Marketplace.
 Transfer the downloaded files to the appropriate directory on the
application server.
2. Load Support Packages:
 Enter T-code SPAM.
 Click on the "Support Package" button and then select "Load
Packages."
3. Apply Support Packages:
 In SPAM, choose the support packages to be applied.
 Click on the "Import Queue" button to start the import process.
 Monitor the import process and resolve any issues that arise.
4. Confirm Import:
 After successful import, confirm the application of support packages.

2. Kernel Upgrade (SAINT and SUM)

 T-code Definitions:
o SAINT: SAP Add-On Installation Tool, also used for kernel updates.
o SUM: Software Update Manager, a comprehensive tool for kernel upgrades
and other system updates.
 Steps:

1. Prepare for Kernel Upgrade:

 Download the latest kernel version from the SAP Service Marketplace.
 Extract the kernel files to the appropriate directory on the application
server.
2. Stop the SAP System:
  Stop the SAP system to replace the kernel files.
3. Replace Kernel Files:
 Backup the existing kernel directory.
 Copy the new kernel files to the kernel directory, replacing the old
files.
4. Start the SAP System:
 Restart the SAP system and verify that the new kernel is active.
5. Verify Kernel Version:
 Enter T-code SM51 to verify the new kernel version.

3. Software Update Manager (SUM)

 Tool Definition: SUM is a comprehensive tool for performing updates, including

support packages, enhancement packages, and kernel updates.
 Steps:
1. Download SUM:
 Download the latest version of SUM from the SAP Service
Marketplace.
2. Prepare SUM Directory:
 Extract SUM to a dedicated directory on the application server.
3. Run SUM:
 Execute the SUM tool and follow the guided procedure.
 Select the update type (e.g., support package, enhancement package,
kernel update).
4. Perform Update:
 Follow the steps in SUM to apply the updates.
 Monitor the process and resolve any issues as directed by SUM.
5. Complete Update:
 Verify that the updates have been successfully applied.

4. Patch Management (SPAM and SAINT)

 T-code Definitions:
o SPAM: Support Package Manager for applying support packages.
o SAINT: SAP Add-On Installation Tool for applying add-ons and patches.
 Steps:

1. Download Patches:
 Download the necessary patches from the SAP Service Marketplace.
 Transfer the downloaded files to the appropriate directory on the
application server.
2. Load Patches:
 Enter T-code SPAM or SAINT.
 Load the patches into the system.
3. Apply Patches:
 In SPAM or SAINT, choose the patches to be applied.
 Start the patch application process and monitor its progress.
4. Confirm Patch Application:
 After successful application, confirm the patches.
5. Support Package Stack Update (MP and SNOTE)

 T-code Definitions:
o MP: Maintenance Planner for planning and downloading updates.
o SNOTE: Note Assistant for implementing SAP Notes.
 Steps:

1. Plan Update in Maintenance Planner:

 Use Maintenance Planner
(https://support.sap.com/maintenanceplanner) to plan the update.
 Select the target stack and download the necessary files.
2. Implement SAP Notes:
 Enter T-code SNOTE.
 Download and implement any required SAP Notes.
3. Apply Updates Using SUM:
 Use SUM to apply the downloaded stack updates.
 Follow the steps in SUM to complete the update process.

6. Checking System Status (SM51, SM50, SICK)

 T-code Definitions:
o SM51: Display list of SAP servers and verify the system status.
o SM50: Process overview for monitoring work processes.
o SICK: Initial consistency check of the SAP system.
 Steps:

1. Verify System Status:

 Enter T-code SM51 to display the list of active servers and their
statuses.
2. Monitor Work Processes:
 Enter T-code SM50 to monitor the status and performance of work
processes.
3. Perform Consistency Check:
 Enter T-code SICK to run a system consistency check and identify any
issues.

7. Database Patching (DBACOCKPIT)

 T-code Definition: DBACOCKPIT is used for comprehensive database

administration, including patch management.
 Steps:
1. Check for Database Patches:
 Regularly check for available database patches from the database
vendor.
2. Apply Database Patches:
 Use the database vendor's tools to apply patches.
 Verify the database status post-application.
3. Monitor Database Performance:
  Use DBACOCKPIT to monitor the performance and stability of the
database after patching.

Summary

Patch and Kernel Management in SAP Basis is crucial for maintaining the security, stability,
and performance of the SAP system. Regularly applying support packages, kernel updates,
and other patches using the mentioned T-codes ensures the system is up to date and running
optimally.

System Logs and Traces

System Logs and Traces in SAP Basis are essential for monitoring system activities,
diagnosing issues, and ensuring system stability. They provide detailed information about
system events, errors, and performance metrics. Here are the key tasks involved in managing
system logs and traces, along with the corresponding transaction codes (T-codes) and brief
explanations for each task.

1. System Log (SM21)

 T-code Definition: SM21 is used to display and analyze the system log.
 Steps:
1. Access System Log:
 Enter T-code SM21.
 Select the time range and type of messages (e.g., all, error, warning).
2. Analyze Log Entries:
 Review the log entries to identify any errors or warnings.
 Click on specific log entries for detailed information.
3. Filter and Search:
 Use filters and search criteria to focus on specific issues or events.
4. Export Logs:
 Export the log entries to a file for further analysis or reporting.

2. Short Dump Analysis (ST22)

 T-code Definition: ST22 is used to display and analyze ABAP runtime errors (short
dumps).
 Steps:
1. Access Short Dump List:
 Enter T-code ST22.
 Select the date and time range for the dumps to be displayed.
2. Analyze Short Dumps:
 Click on individual short dumps to view detailed information.
 Identify the cause of the runtime error and possible solutions.
3. Correct Errors:
 Based on the analysis, take corrective actions to resolve the underlying
issues.
4. Delete Old Dumps:
  Regularly delete old short dumps to manage space and keep the system
clean.

3. Application Log (SLG1)

 T-code Definition: SLG1 is used to display application logs created by various SAP
applications.
 Steps:
1. Access Application Log:
 Enter T-code SLG1.
 Specify the object and sub-object for which the logs are to be
displayed.
2. View Log Entries:
 Review the list of log entries.
 Click on individual entries for detailed information.
3. Analyze and Filter Logs:
 Use filtering options to narrow down the logs to specific events or
issues.
4. Export Log Data:
 Export the log data for further analysis or reporting purposes.

4. System Trace (ST01)

 T-code Definition: ST01 is used for system-wide tracing, including authorization

checks, kernel functions, and SQL traces.
 Steps:
1. Activate System Trace:
 Enter T-code ST01.
 Select the trace components to be activated (e.g., Authorization check,
Kernel, SQL).
2. Start Trace:
 Click on "Start Trace" to begin capturing trace data.
3. Perform Actions:
 Perform the actions in the SAP system that you want to trace.
4. Stop and Analyze Trace:
 Click on "Stop Trace" to end the tracing session.
 Analyze the captured trace data to identify issues or performance
bottlenecks.
5. Save and Export Trace Data:
 Save the trace data and export it if needed for further analysis.

5. SQL Trace (ST05)

 T-code Definition: ST05 is used for SQL trace analysis to diagnose database
performance issues.
 Steps:
1. Activate SQL Trace:
 Enter T-code ST05.
 Select "Activate Trace" and choose the trace options (e.g., SQL trace,
Enqueue trace).
 2. Perform SQL Operations:
 Execute the SQL queries or transactions you want to trace.
3. Deactivate Trace:
 Deactivate the trace once the operations are complete.
4. Analyze Trace Data:
 View the captured trace data and analyze the SQL statements and their
performance.
5. Optimize SQL Statements:
 Based on the analysis, optimize the SQL statements or database access
methods to improve performance.

6. Performance Trace (STATS)

 T-code Definition: STATS is used to analyze the performance statistics collected by

the SAP system.
 Steps:
1. Access Performance Statistics:
 Enter T-code STATS.
 Select the time range and type of statistics to be displayed.
2. View Performance Data:
 Review the performance data, such as response times, workload, and
system utilization.
3. Analyze Performance Issues:
 Identify any performance issues or bottlenecks.
 Take corrective actions to resolve performance problems.
4. Generate Reports:
 Generate reports based on the performance statistics for further
analysis or documentation.

7. Enqueue Trace (SM12)

 T-code Definition: SM12 is used to monitor and manage lock entries (enqueue) in the
SAP system.
 Steps:
1. Display Lock Entries:
 Enter T-code SM12.
 View the list of current lock entries in the system.
2. Analyze Locks:
 Identify long-running or problematic lock entries.
3. Manage Locks:
 Manually delete problematic lock entries if necessary, ensuring no data
inconsistency.
4. Monitor Lock Activity:
 Continuously monitor lock activity to prevent deadlocks and
performance issues.

8. Update Requests (SM13)

 T-code Definition: SM13 is used to monitor and manage update requests in the SAP
system.
  Steps:
1. Access Update Requests:
 Enter T-code SM13.
 View the list of update requests and their statuses.
2. Analyze Update Failures:
 Identify any failed update requests and analyze the reasons for the
failures.
3. Repeat or Delete Updates:
 Manually repeat or delete failed update requests after resolving the
underlying issues.
4. Ensure Update Consistency:
 Ensure that update requests are processed consistently and without
errors.

Summary

System Logs and Traces in SAP Basis are critical tools for monitoring, diagnosing, and
maintaining the health of the SAP system. Using the mentioned T-codes, administrators can
effectively track system activities, identify and resolve issues, and ensure optimal system
performance and stability. Regular monitoring and analysis of logs and traces help in
proactive system management and problem resolution.
 SAP Note and OSS Connection
SAP Notes and OSS (Online Service System) Connections are critical components in SAP
Basis for maintaining and updating the system, addressing issues, and ensuring continuous
support from SAP. Here are the key tasks involved in managing SAP Notes and OSS
Connections, along with the corresponding transaction codes (T-codes) and brief
explanations for each task.

1. SAP Note Management (SNOTE)

 T-code Definition: SNOTE is used to implement SAP Notes, which are updates, bug
fixes, or enhancements provided by SAP.
 Steps:
1. Download SAP Notes:
 Enter T-code SNOTE.
 Click on the "Download SAP Notes" button.
 Enter the SAP Note number and download it from the SAP Support
Portal.
2. Implement SAP Notes:
 In the SNOTE screen, find the downloaded note in the list.
 Select the note and click on the "Implement SAP Note" button.
 Follow the guided steps to apply the note to your system.
3. Check Note Implementation Status:
 Review the status of the note implementation to ensure it has been
successfully applied.
 Resolve any conflicts or prerequisites that may be indicated.
4. Documentation and Follow-up:
 Read the documentation provided with the note for detailed
instructions and implications.
 Test the system functionality to ensure the note has addressed the issue
or enhancement.

2. OSS Connection Setup and Management (SM59, OSS1, SNOTE)

 T-code Definitions:
o SM59: Used to create and manage RFC (Remote Function Call) connections.
o OSS1: Used to log in to the SAP Service Marketplace (OSS) for SAP support.
o SNOTE: Used for note management and to ensure connection to OSS.
 Steps:
 1. Create RFC Destination (SM59):
 Enter T-code SM59.
 Create a new RFC destination of type "HTTP Connection to External
Server".
 Enter the connection details provided by SAP, including the target host
and service number.
 Save and test the connection to ensure it is correctly configured.
2. Set Up OSS Connection (OSS1):
 Enter T-code OSS1.
 Ensure that the RFC connection created in SM59 is listed and
functional.
 Log in to the OSS system using your SAP Support credentials.
3. Manage SAP Notes (SNOTE):
 Use T-code SNOTE to download and implement SAP Notes, as
described above.
 Ensure the OSS connection is active and can reach the SAP Support
Portal to download notes.
4. Maintain OSS Credentials and Authorizations:
 Regularly update and maintain OSS credentials.
 Ensure that the necessary authorizations are in place for users who
manage OSS connections and SAP Notes.

3. Maintaining and Troubleshooting OSS Connections

 T-code Definitions:
o SM59: For managing RFC destinations.
o OSS1: For OSS-specific configuration and troubleshooting.
 Steps:

1. Verify RFC Destination (SM59):

 Regularly test the OSS RFC destination in SM59 to ensure
connectivity.
 Troubleshoot any connectivity issues by checking network settings,
credentials, and SAProuter configurations.
2. Check OSS1 Configuration:
 In OSS1, verify that the correct RFC destination is being used.
 Ensure that the OSS system can be accessed and that there are no
errors.
3. Troubleshoot Connectivity Issues:
 Check the SAProuter settings if used, and ensure it is properly
configured and running.
 Review firewall and network settings to allow traffic to and from the
SAP support servers.
4. Contact SAP Support:
 If issues persist, contact SAP Support for assistance.
 Provide them with details of the RFC configuration and any error
messages encountered.

4. Usage of SAP Note Assistant (SNOTE)

  T-code Definition: SNOTE is a comprehensive tool for managing and applying SAP
Notes.
 Steps:
1. Access SAP Note Assistant:
 Enter T-code SNOTE.
 Familiarize yourself with the interface and options available for note
management.
2. Download and Apply Notes:
 Use the "Download SAP Note" function to retrieve notes from the SAP
Support Portal.
 Apply the notes following the implementation steps provided in the
note details.
3. Check Prerequisites and Dependencies:
 Ensure all prerequisites and dependencies for the note are met before
implementation.
4. Monitor Note Application:
 Monitor the status of applied notes and verify their successful
implementation.
 Resolve any issues that arise during the application process.

Summary

Managing SAP Notes and OSS Connections is crucial for maintaining the SAP system's
health, security, and performance. By effectively using T-codes such as SNOTE, SM59, and
OSS1, SAP Basis administrators can ensure that their systems are up-to-date with the latest
patches, bug fixes, and enhancements provided by SAP. Regular monitoring and
troubleshooting of OSS connections ensure seamless communication with SAP Support for
continuous system improvement and issue resolution.
 Batch Input Monitoring
Batch Input Monitoring in SAP Basis involves overseeing and managing batch jobs that input
data into the SAP system in bulk. These jobs are critical for mass data uploads, updates, and
transactions. Below are the steps involved in monitoring batch inputs and the corresponding
transaction code (T-code) used for this task:

Batch Input Monitoring Steps

1. Accessing Batch Input Monitoring (SM35):

o T-code Definition: SM35
o Enter transaction code SM35 in the SAP GUI to access Batch Input
Monitoring.
2. Viewing Batch Input Sessions:
o In SM35, you'll see a list of batch input sessions that have been processed or
are in process.
o Sessions are organized by date, time, and status (processed, error, scheduled).
3. Monitoring Session Details:
o Click on a specific session to view its details.
o Details include the session name, status (success, error), number of
transactions processed, start and end times, and processing log.
4. Analyzing Session Logs:
o Review the session log to understand the outcome of the batch input process.
o Logs provide information about errors encountered during data processing and
details on successfully processed data.
5. Resolving Errors:
o For sessions with errors, analyze the logs to identify the root cause.
o Correct errors in the source data or in the batch input program/configuration.
o Restart sessions that encountered errors after resolving the issues.
6. Reprocessing Sessions:
o If needed, reprocess sessions that have encountered errors or that were
intentionally stopped.
o Use the options in SM35 to restart sessions with corrections applied.
7. Deleting Old Sessions:
o Regularly clean up old and unnecessary batch input sessions to optimize
system performance and storage.
o Use the deletion options available in SM35 to remove completed and outdated
sessions.
Summary

Batch Input Monitoring (SM35) in SAP Basis is essential for overseeing bulk data processing
jobs within the SAP system. It allows administrators to monitor the status of batch input
sessions, troubleshoot errors, and ensure data integrity and system performance. By using
SM35 effectively, administrators can manage data uploads and updates efficiently, ensuring
that business processes relying on batch inputs run smoothly and reliably.

3.5

Work Process Management

Work Process Management in SAP Basis involves overseeing and managing the work
processes that execute various tasks within the SAP system. These work processes handle
user requests, execute background jobs, and manage dialog transactions. Here are the steps
involved in managing work processes and the relevant transaction codes (T-codes) used for
this task:

Work Process Management Steps

1. Accessing Work Process Overview (SM50):

o T-code Definition: SM50
o Enter transaction code SM50 in the SAP GUI to access the Work Process
Overview.
2. Viewing Work Process Status:
o In SM50, you can see a list of all active work processes in the SAP system.
o Each work process is identified by its type (Dialog, Background, Update,
Spool, etc.), status (Running, Waiting, or Held), and current activity.
3. Monitoring Work Process Load:
o Check the workload distribution among work processes to ensure balanced
system performance.
o Monitor CPU and memory utilization for each work process to identify
potential bottlenecks or resource constraints.
4. Analyzing Work Process Details:
o Click on a specific work process to view detailed information such as its PID
(Process ID), user, current transaction, and resource consumption.
o Review the workload and transaction log to understand the activities
performed by the work process.
5. Performing Work Process Administration (SM51):
o T-code Definition: SM51
o Enter transaction code SM51 to access the SAP System Overview.
o From SM51, you can manage work processes by starting, stopping, or
adjusting parameters (e.g., process type, memory allocation) for individual
instances.
6. Handling Work Process Issues:
o Identify and resolve issues related to work processes that are in a waiting or
held status.
o Check for deadlock situations, long-running transactions, or other factors
causing work process delays.
 7. Restarting Work Processes (SM49):
o T-code Definition: SM49 (Execute External OS Commands)
o In some cases, you may need to restart work processes manually due to errors
or performance issues.
o Enter transaction code SM49 to execute OS commands and restart work
processes under controlled circumstances.
8. Optimizing Work Process Configuration (RZ11):
o T-code Definition: RZ11 (Dynamic System Configuration)
o Use RZ11 to adjust parameters affecting work process behavior, such as
memory allocation, buffer settings, or timeout values.
o Ensure optimal performance and resource utilization based on system
workload and user demands.

Summary

Work Process Management in SAP Basis is crucial for maintaining system performance and
ensuring efficient processing of user requests and background jobs. By using the mentioned
T-codes effectively, administrators can monitor work process status, troubleshoot issues, and
optimize system resources to meet business requirements effectively. Regular monitoring and
adjustment of work process configurations contribute to stable and responsive SAP system
operations.

3.5
 System Administration
System Administration in SAP Basis involves a range of tasks essential for maintaining,
monitoring, and configuring the SAP system to ensure its smooth operation. Here are the key
steps involved in system administration and the relevant transaction codes (T-codes) used for
these tasks:

System Administration Steps

1. System Monitoring (SM51, SM66, ST06):

o T-code Definitions:
 SM51: Display SAP System Instances
 SM66: Global Work Process Overview
 ST06: Operating System Monitor
o Steps:
 Use SM51 to view active SAP instances and their statuses.
 Use SM66 for a global overview of all work processes across instances.
 Use ST06 to monitor operating system performance metrics relevant to
SAP.
2. User Management (SU01, SU10):
o T-code Definitions:
 SU01: User Maintenance
 SU10: Mass Changes to User Master Records
o Steps:
 Use SU01 to create, modify, and manage user accounts in the SAP
system.
 Use SU10 for mass changes to user master records, such as updating
user parameters or roles.
3. Client Administration (SCC4, SCCL):
o T-code Definitions:
 SCC4: Client Administration
 SCCL: Local Client Copy
o Steps:
 Use SCC4 to manage client-specific settings and authorizations.
 Use SCCL to perform local client copies for system refresh or testing
purposes.
4. Transport Management (STMS):
o T-code Definition: STMS (SAP Transport Management System)
o Steps:
 Use STMS to configure and manage transport routes, transport layers,
and import transports into target systems.
  Monitor transport requests and ensure seamless movement of changes
across system landscapes.
5. Job Scheduling and Monitoring (SM37, SM36):
o T-code Definitions:
 SM37: Overview of Job Selection
 SM36: Define Background Job
o Steps:
 Use SM37 to monitor and manage background jobs scheduled in the
SAP system.
 Use SM36 to define new background jobs, specify job parameters, and
schedule recurring tasks.
6. System Backup and Recovery (DB13, BRBACKUP):
o T-code Definitions:
 DB13: Database Administration
 BRBACKUP: Database Backup Using BR*Tools
o Steps:
 Use DB13 for database administration tasks, including scheduling
backups and monitoring database performance.
 Use BRBACKUP (part of BR*Tools) for performing database backups
and restores.
7. System Performance Tuning (ST02, ST04):
o T-code Definitions:
 ST02: Tune Summary
 ST04: DB Performance Monitor
o Steps:
 Use ST02 to analyze SAP buffer and memory utilization, and make
adjustments to optimize system performance.
 Use ST04 for database performance monitoring and tuning, focusing on
SQL statement analysis and index optimization.
8. System Health Checks and Monitoring (ST06, SM51):
o T-code Definitions:
 ST06: Operating System Monitor
 SM51: Display SAP System Instances
o Steps:
 Regularly monitor system health using ST06 to check operating system
parameters and resources.
 Use SM51 to monitor SAP instances, work processes, and overall
system availability.

Summary

System Administration in SAP Basis encompasses a broad range of tasks aimed at ensuring
the stability, security, and performance of the SAP landscape. By effectively utilizing the
mentioned T-codes and following these steps, administrators can maintain system integrity,
optimize performance, manage users and clients, schedule and monitor jobs, and perform
essential administrative functions to support business operations effectively. Regular
monitoring, proactive management, and adherence to best practices contribute to a reliable
and efficient SAP system environment.
3.5

Data Archiving
Data archiving in SAP Basis involves the process of transferring older or less frequently
accessed data from the operational database to a separate storage location to optimize system
performance and reduce storage costs. Here are the steps involved in data archiving and the
relevant transaction codes (T-codes) used for these tasks:

Data Archiving Steps

1. Archiving Object Definition (SARA):

o T-code Definition: SARA (Archive Administration)
o Steps:
 Enter transaction code SARA in the SAP GUI to access Archive
Administration.
 Define archiving objects (AOBJ) which specify what data to archive
(e.g., sales orders, invoices).
 Configure parameters such as retention period, selection criteria, and
archiving session settings.
2. Archiving Session Creation (SARA):
o Steps:
 Create new archiving sessions (AS) within SARA based on defined
archiving objects.
 Specify selection criteria to identify data eligible for archiving (e.g.,
based on document date, document type).
 Schedule archiving sessions for execution at a convenient time to
minimize impact on system performance.
3. Executing Archiving Sessions (SARA):
o Steps:
 Execute archiving sessions (AS) to start transferring data from the
operational database to the archive files.
 Monitor the progress of archiving sessions to ensure they complete
successfully.
 Review logs and reports generated by SARA to verify the outcome of
archiving sessions.
4. Displaying Archived Data (SARI):
o T-code Definition: SARI (Archive Information System)
o Steps:
 Use transaction code SARI to display archived data and check the
contents of archive files.
 Search for archived data based on specific criteria (e.g., document
number, archive session).
5. Deleting Archived Data (SARA):
o Steps:
  Optionally, delete archived data from the database (AD) once it is
confirmed to be successfully archived and no longer needed for
operational purposes.
 Follow the guidelines and procedures defined for data retention and
deletion policies.
6. Monitoring and Troubleshooting (SARA, SARI):
o Steps:
 Monitor archiving sessions (AS) and review logs (ALOG) in SARA for
any errors or issues encountered during archiving.
 Use SARI to analyze archived data and ensure completeness and
integrity of archived information.

Additional Considerations

 Archiving Development and Custom Objects: For custom-developed applications,

ensure archiving objects are defined and managed appropriately using custom
archiving programs and tools.
 Legal and Compliance Requirements: Adhere to legal and regulatory requirements
for data retention and archiving in your industry or region.
 Performance Optimization: Regularly optimize archiving strategies and adjust
selection criteria to maintain optimal system performance.

Summary

Data archiving in SAP Basis is crucial for managing data growth, optimizing system
performance, and reducing storage costs. By utilizing the mentioned T-codes and following
these steps, administrators can effectively define, execute, and monitor data archiving
processes to ensure efficient data management and compliance with organizational and
regulatory requirements. Regular monitoring and optimization of archiving strategies
contribute to maintaining a lean and responsive SAP environment.

3.5
 Job Scheduling Management
Job Scheduling Management in SAP Basis involves the scheduling, monitoring, and
management of background jobs within the SAP system. These jobs automate tasks such as
data backups, data transfers, and periodic system maintenance activities. Here are the steps
involved in job scheduling management and the relevant transaction codes (T-codes) used for
these tasks:

Job Scheduling Management Steps

1. Define Background Job (SM36):

o T-code Definition: SM36 (Define Background Job)
o Steps:
 Enter transaction code SM36 in the SAP GUI to define a new
background job.
 Specify job attributes such as job name, job class (A, B, C), start
condition (immediate or scheduled), and periodicity (daily, weekly,
monthly).
 Define the executable program or function module that the job will
execute.
2. Schedule Background Job (SM37):
o T-code Definition: SM37 (Job Monitoring)
o Steps:
 Use transaction code SM37 to monitor and schedule background jobs.
 Search for existing jobs or select the job defined in SM36.
 Schedule the job to run immediately or at a specified future date and
time.
 Configure job variants if applicable (different parameter sets for the
same job).
3. Monitor Background Jobs (SM37):
o Steps:
 In SM37, monitor the status of scheduled background jobs.
 View job logs to check job execution details, including start time, end
time, status (success, warning, error), and any job-specific messages.
 Identify jobs that have completed successfully and those that require
attention due to errors or issues.
4. Manage Background Job Variants (SM37):
o Steps:
 Maintain job variants within SM37 to specify different sets of input
parameters for the same background job.
 Create, modify, or delete job variants to meet specific job execution
requirements.
5. Cancel or Reschedule Jobs (SM37):
o Steps:
 Cancel background jobs in SM37 if they are no longer needed or if
errors prevent successful completion.
 Reschedule jobs with adjusted parameters or timing based on system
requirements or user requests.
6. Job Documentation and Reporting (SM37):
o Steps:
 Document job execution details and outcomes using job logs and
reports available in SM37.
 Generate job execution reports to analyze job performance, execution
times, and resource consumption.
7. Alerts and Notifications (SM37, SCOT):
o Steps:
 Configure job alerts and notifications in SM37 to receive alerts via
email or SAP Workplace when jobs encounter errors or fail to execute
as scheduled.
 Use transaction code SCOT to set up email configurations for job
notifications.

Summary

Job Scheduling Management in SAP Basis is essential for automating routine tasks and
ensuring timely execution of critical processes within the SAP system. By utilizing the
mentioned T-codes and following these steps, administrators can effectively define, schedule,
monitor, and manage background jobs to optimize system performance and support business
operations efficiently. Regular monitoring and proactive management of job scheduling help
maintain system reliability and responsiveness.
TRANSACTION CODES PURPOSE:
USES AND WITHOUT USE :

In SAP Basis, transaction codes (T-codes) are essential for system administration,
monitoring, configuration, and user management. Here is a list of some of the most important
T-codes along with their purposes, the impact of using them, and the consequences of not
using them:

System Administration and Monitoring

1. SM51: SAP System Overview

o Purpose: Displays active application servers and their statuses.
o With Use: Provides visibility into server operations, facilitating system
monitoring.
o Without Use: Administrators would lack insight into server statuses, making
it difficult to manage system health and troubleshoot server-related issues.
2. SM50: Work Process Overview
o Purpose: Monitors the status and activity of work processes on an application
server.
o With Use: Enables monitoring and troubleshooting of work process issues,
improving system performance and stability.
o Without Use: Identifying and resolving performance bottlenecks would be
challenging, leading to potential system slowdowns.
3. SM66: Global Work Process Overview
o Purpose: Provides a global overview of all work processes across all
application servers.
o With Use: Facilitates system-wide monitoring, helping to balance workloads
and address performance issues.
o Without Use: Administrators would struggle to get a consolidated view,
making it harder to manage system-wide performance.
4. ST06: Operating System Monitor
o Purpose: Monitors operating system performance metrics such as CPU,
memory, and disk activity.
o With Use: Helps in identifying and resolving hardware performance issues.
o Without Use: Hardware performance problems might go unnoticed,
potentially affecting overall system performance.
5. ST22: Dump Analysis
o Purpose: Analyzes ABAP runtime errors (short dumps).
 o With Use: Facilitates troubleshooting and resolving ABAP errors, ensuring
system stability.
o Without Use: Runtime errors would be difficult to diagnose, potentially
leading to unresolved issues and system crashes.

User and Authorization Management

6. SU01: User Maintenance

o Purpose: Manages user accounts (creation, modification, deletion).
o With Use: Ensures proper user access management and security.
o Without Use: Managing user accounts would be error-prone, increasing the
risk of unauthorized access and security breaches.
7. SU10: Mass Changes to User Master Records
o Purpose: Performs mass updates to user master records.
o With Use: Allows efficient mass user management, saving time and reducing
errors.
o Without Use: Mass user updates would need to be done individually,
increasing time and effort.
8. PFCG: Role Maintenance
o Purpose: Creates and maintains authorization roles.
o With Use: Structured role management, ensuring appropriate access levels.
o Without Use: Role management would be less organized, leading to potential
security issues.
9. SUIM: User Information System
o Purpose: Provides reports and queries for user and authorization information.
o With Use: Facilitates auditing and analyzing user access.
o Without Use: User access analysis would be challenging, reducing audit
efficiency.

Client Administration

10. SCC4: Client Administration

o Purpose: Manages client-specific settings and authorizations.
o With Use: Enables proper client management, ensuring isolated environments
for development, testing, and production.
o Without Use: Client management would be more difficult, impacting the
ability to maintain separate environments.
11. SCCL: Local Client Copy
o Purpose: Performs local client copies within the same system.
o With Use: Efficiently creates test or training environments.
o Without Use: Setting up new environments would be time-consuming and
complex.
12. SCC9: Remote Client Copy
o Purpose: Copies clients between different SAP systems.
o With Use: Facilitates system refreshes and data transfers.
o Without Use: Client data transfers between systems would be less efficient.

Transport Management
 13. STMS: Transport Management System
o Purpose: Manages transport requests and configuration of the transport
landscape.
o With Use: Ensures controlled changes across systems.
o Without Use: Coordinating and managing changes would be chaotic,
increasing the risk of inconsistencies.
14. SE01: Transport Organizer
o Purpose: Central management of transport requests, tasks, and objects.
o With Use: Organized tracking and control of system changes.
o Without Use: Tracking and managing transport requests would be less
efficient, leading to potential errors.
15. SE09: Workbench Organizer
o Purpose: Manages workbench requests for transporting development objects.
o With Use: Efficiently transports development objects.
o Without Use: Development deployments would be more difficult, potentially
causing delays and errors.
16. SE10: Customizing Organizer
o Purpose: Manages customizing requests for transporting configuration
settings.
o With Use: Ensures consistent system configurations across environments.
o Without Use: Transporting configuration changes would be less efficient.

Job Scheduling and Monitoring

17. SM36: Define Background Job

o Purpose: Schedules background jobs with specific parameters.
o With Use: Automates routine tasks and batch processing.
o Without Use: Routine tasks would require manual intervention, increasing the
risk of missed or delayed jobs.
18. SM37: Job Monitoring
o Purpose: Monitors and manages scheduled background jobs.
o With Use: Provides status updates and logs for job execution.
o Without Use: Monitoring job execution would be challenging, leading to
potential job failures.

Database Administration

19. DB13: DBA Planning Calendar

o Purpose: Schedules and monitors database backup and maintenance tasks.
o With Use: Ensures regular data protection and maintenance.
o Without Use: Database maintenance would be less efficient, increasing the
risk of data loss.
20. DB02: Database Performance: Tables and Indexes
o Purpose: Monitors and analyzes database performance.
o With Use: Identifies and resolves database performance issues.
o Without Use: Database performance issues would be harder to detect,
affecting system performance.

System Configuration
 21. RZ10: Profile Maintenance
o Purpose: Manages system profiles and parameters.
o With Use: Configures system settings efficiently.
o Without Use: Configuring system parameters would be less straightforward.
22. RZ11: Profile Parameter Maintenance
o Purpose: Displays and maintains runtime system parameters.
o With Use: Adjusts runtime parameters for optimal performance.
o Without Use: Managing runtime parameters would be less convenient.

Patch and Kernel Management

23. SPAM: Support Package Manager

o Purpose: Applies support packages and SAP Notes.
o With Use: Keeps the system updated with the latest fixes and enhancements.
o Without Use: Applying patches would be cumbersome, increasing the risk of
unresolved issues.
24. SAINT: Add-On Installation Tool
o Purpose: Installs SAP add-ons and support packages.
o With Use: Manages add-ons efficiently.
o Without Use: Installing add-ons would be more difficult.

Logs and Traces

25. SM21: System Log

o Purpose: Displays and analyzes system logs.
o With Use: Provides insights into system events and errors.
o Without Use: Troubleshooting system issues would be more challenging.
26. ST11: Display Developer Traces
o Purpose: Views and analyzes developer traces.
o With Use: Assists in debugging and troubleshooting.
o Without Use: Debugging development issues would be more difficult.

Data Archiving

27. SARA: Archive Administration

o Purpose: Manages data archiving processes.
o With Use: Reduces database size and improves performance.
o Without Use: Managing data growth would be challenging, leading to
increased storage costs.
28. SARI: Archive Information System
o Purpose: Displays and searches archived data.
o With Use: Facilitates easy access to archived information.
o Without Use: Accessing archived data would be less efficient.

SAP Note and OSS Connection

29. SNOTE: SAP Note Assistant

o
o Purpose: Implements SAP Notes for updates and corrections.
 o With Use: Ensures the system is up-to-date with necessary fixes.
o Without Use: Applying SAP Notes would be more time-consuming.
30.
31. OSS1: Logon to SAP Service Marketplace (OSS)
o
o Purpose: Manages OSS connections for accessing SAP support.
o With Use: Facilitates communication with SAP support for issue resolution.
o Without Use: Accessing SAP support services would be more difficult.