SAP Basis daily checklist
System Monitoring
- Access the SAP GUI.
- Navigate to transaction code SM21.
- Set the time frame for the log check.
- Review the entries for any errors or warnings.
- Document any critical issues for follow-up.
- Use transaction code SM63 for operation modes.
- Check the current modes for each instance.
- Access transaction code SM37 for background jobs.
- Filter jobs by status (e.g., finished, active).
- Analyze any failed or long-running jobs.
- Open transaction code DB02.
- Check the database size and growth statistics.
- Review performance metrics like response time.
- Look for any locks or deadlocks.
- Document any anomalies for further analysis.
- Access transaction code AL08 for alerts.
- Review the list of active alerts.
- Check the severity and impact of each alert.
- Ensure notifications are acknowledged as needed.
- Follow up on critical alerts with relevant teams.
Performance Checks
- Access system monitoring tools.
- Check CPU usage percentages.
- Review memory consumption and available RAM.
- Evaluate disk space usage and I/O operations.
- Identify any alerts or thresholds breached.
- Access transaction ST02.
- Review buffer statistics (e.g., hit ratios).
- Identify buffers with low hit ratios.
- Analyze performance impact of buffer settings.
- Consider adjustments to buffer sizes as needed.
- Utilize transaction ST03N.
- Select critical transactions to monitor.
- Review average response times.
- Identify transactions with prolonged response times.
- Investigate the root causes for delays.
- Access transaction SM37.
- Filter for batch jobs completed today.
- Review job duration and status.
- Identify any jobs with delays.
- Investigate reasons for processing time anomalies.
- Access database monitoring tools.
- Evaluate query execution times.
- Identify long-running queries.
- Review execution plans for optimization.
- Consider indexing or query rewriting.
- Access transaction SM50 or SM66.
- Review active processes and workload distribution.
- Identify any processes consuming excessive resources.
- Analyze system resource contention.
- Consider redistributing workloads as necessary.
- Access transaction SM12.
- Check for any locked entries.
- Review deadlock situations and analyze causes.
- Evaluate enqueue performance metrics.
- Consider resolving conflicts in application logic.
- Access transaction SM50.
- Identify processes running longer than expected.
- Analyze process details for resource usage.
- Investigate potential issues causing delays.
- Consider terminating problematic processes if necessary.
- Access transaction SLG1.
- Filter logs for performance-related entries.
- Review warnings and errors.
- Identify recurring issues or patterns.
- Document findings for further analysis.
- Review instance sizing based on workload.
- Compare current configuration against best practices.
- Evaluate CPU, memory, and disk allocations.
- Identify potential areas for improvement.
- Document recommendations for resizing.
- Use network monitoring tools.
- Check latency metrics between servers.
- Identify any network bottlenecks.
- Evaluate response times for network calls.
- Consider optimizing network configurations.
- Review current archiving policies.
- Analyze data growth and retention metrics.
- Evaluate performance improvements post-archiving.
- Identify archiving opportunities for large tables.
- Document findings for future planning.
- Access transaction ST05 for performance trace.
- Analyze execution times of custom programs.
- Identify inefficient code or queries.
- Consult developers for potential optimizations.
- Document recommendations for performance improvements.
- Review current SAP kernel version.
- Check for available kernel updates.
- Evaluate improvements in newer versions.
- Plan for kernel upgrades if beneficial.
- Document upgrade procedures and impacts.
- Access SAP Support Launchpad.
- Search for relevant performance notes.
- Review applicability to current system.
- Implement applicable notes and document changes.
- Monitor performance post-implementation.
- Use transaction DB02.
- Check for temporary table usage metrics.
- Identify excessive or unnecessary temporary tables.
- Evaluate impact on overall database performance.
- Consider optimizing table usage patterns.
- Access transaction SM37.
- Review background job scheduling times.
- Identify any jobs causing resource contention.
- Analyze scheduling patterns for optimization.
- Document recommendations for scheduling adjustments.
- Access transaction SMGW.
- Check gateway performance metrics.
- Evaluate connection times and bottlenecks.
- Review configuration settings for optimization.
- Document potential improvements.
- Access transaction SM66.
- Review active processes and their statuses.
- Identify resource-intensive processes.
- Evaluate their impact on overall system performance.
- Consider adjustments or terminations if necessary.
Backup and Recovery
User and Security Management
- Access the user logon statistics report.
- Identify any anomalies or spikes in logon attempts.
- Investigate the origins of unusual activity.
- Document findings and take necessary actions if needed.
- Run a report of all user accounts.
- Identify accounts that haven't been used for a predefined period.
- Decide on actions: deactivate, delete, or reach out to users.
- Ensure documentation of actions taken for compliance.
- Review user roles assigned to each account.
- Verify alignment with job functions and security policies.
- Adjust roles and authorizations as necessary.
- Document any changes made for audit trails.
- Access the security logs in the SAP system.
- Look for failed logon attempts and other suspicious activities.
- Investigate any unauthorized access patterns.
- Report findings and escalate if necessary.
- Review MFA settings for all user accounts.
- Identify accounts that do not have MFA enabled.
- Implement MFA for those accounts as required.
- Document compliance status for audit purposes.
- Collect current role definitions and business requirements.
- Identify roles needing updates based on changes.
- Update roles accordingly and communicate changes.
- Document the updates for future reference.
- Schedule regular audits of user access.
- Compare current roles against the principle of least privilege.
- Adjust roles to restrict unnecessary access.
- Maintain documentation of the audit process.
- Identify critical transactions within the SAP system.
- Review user access to these transactions.
- Limit access to only authorized personnel.
- Document access controls for audits.
- List all service user accounts in use.
- Evaluate the necessity of each account.
- Secure or deactivate accounts that are no longer needed.
- Keep records of accounts for security audits.
- Review logs for changes in user roles.
- Identify who made the changes and the reasons.
- Document all changes and rationale.
- Ensure compliance with change management policies.
- Review current password policies in place.
- Check for user compliance with those policies.
- Enforce policy adherence through reminders or training.
- Document compliance and any issues found.
- Analyze user activity logs for anomalies.
- Look for patterns that deviate from normal behavior.
- Investigate users exhibiting unusual access requests.
- Report and take action if necessary.
- Verify logging settings for critical transactions.
- Ensure logs are capturing necessary data.
- Schedule regular reviews of these logs.
- Document findings and actions taken.
- Draft and distribute updated security policies.
- Conduct training sessions to explain changes.
- Collect feedback and ensure understanding from users.
- Document communication efforts for audit trails.
Use in Manifestly