[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EQSWWT5DVMTANN64ZQTWY4":3,"skill-same:01M6EQSWWT5DVMTANN64ZQTWY4":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6EQSWWT5DVMTANN64ZQTWY4","system-admin",null,"Use when performing SAP Basis or system administration tasks — transport management, user administration, background jobs, system monitoring, HANA administration, support pack maintenance, or system landscape management across DEV\u002FQAS\u002FPRD.","vigneshbarani24\u002Fsap-superpowers","vigneshbarani24","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20842962?v=4","01M6EQKRW2KZ2M0H75J985XGDX","Vignesh Barani Sivakumar","01M6EQKS0E6EWFSXP4XWK6Y760",11,"MIT","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmodules\u002Fsystem-admin\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"system admin","admin","system","user","across","background jobs","landscape","sap","jobs","maintenance","use","support","management","prd","monitoring","dev","tasks","2026-11-10 10:12:30",false,"---\nname: system-admin\ndescription: Use when performing SAP Basis or system administration tasks — transport management, user administration, background jobs, system monitoring, HANA administration, support pack maintenance, or system landscape management across DEV\u002FQAS\u002FPRD.\n---\n\n# SAP Basis \u002F System Administration\n\nGoverns all SAP system administration activities. The landscape is the foundation everything else runs on — changes to production without proper controls, untested transports, and unmonitored systems create outages that are 100% preventable.\n\n## Content Routing\n\n| Topic | Section |\n|-------|---------|\n| Transport management | Iron Laws + Transaction Codes |\n| User and authorization management | Key Concepts + Transaction Codes |\n| System monitoring and dumps | Transaction Codes + Red Flags |\n| Performance analysis | Key Concepts + Transaction Codes |\n| Support pack \u002F upgrade procedures | Key Concepts |\n| HANA administration | Key Concepts |\n\n## Iron Laws\n\n1. **NEVER CHANGE PRODUCTION WITHOUT CHANGE MANAGEMENT APPROVAL.** Every change to a production system — transport import, manual configuration, kernel patch, support pack, user role change — requires a documented change request approved through the organization's change management process (Cloud ALM, Solution Manager, or equivalent). \"Emergency\" changes require emergency change procedures, not bypassing controls.\n2. **ALWAYS CHECK SYSTEM LOGS BEFORE AND AFTER MAINTENANCE WINDOWS.** SM21 (system log) and ST22 (ABAP dumps) must be reviewed immediately before a maintenance window starts (to establish baseline) and within 30 minutes of completion. New dumps or log errors post-maintenance are caused by the maintenance — don't assume otherwise.\n3. **NEVER DELETE TRANSPORTS FROM THE IMPORT QUEUE WITHOUT DOCUMENTATION.** Removing a transport from STMS import queue permanently excludes it from the landscape unless re-imported manually. Deleting without documentation makes the gap impossible to detect in future audits or when troubleshooting missing functionality.\n4. **ALWAYS VERIFY BUFFER CONSISTENCY AFTER SUPPORT PACK APPLICATION.** Support packs modify ABAP repository objects, DDIC, and customizing. After application, run `\u002FSDF\u002FCDPOS_REORG` or use RSBC_BUFFER_CONSISTENCY to check buffer states. Inconsistent buffers after patching cause intermittent transaction failures that appear unrelated to the patch.\n\n## Rationalization Table\n\n| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |\n|---|---|---|---|\n| Import a transport directly to production to \"save time\" | \"It's a small config change, we tested it manually\" | Untested transports — even small ones — cause inconsistencies; they bypass QAS regression; they're undocumented and unauditable | Every transport must follow DEV → QAS → PRD. For emergencies: import to QAS first, get sign-off, import to PRD same day |\n| Create an RFC destination in production without a transport | \"RFC destinations can't be transported anyway\" | Manual production changes are invisible to future teams; RFC destinations with embedded credentials are a security exposure | Use SM59 transport flag where available; document all manual prod changes in the change request |\n| Schedule a background job in production without SM36 job documentation | \"The business asked me to add this job today\" | Undocumented jobs cause confusion, duplicate scheduling, and collision with existing job chains | Define the job in SM36 with proper job class, schedule, and owner; document in the ITSM ticket |\n| Skip STMS transport route verification after landscape change | \"The routes were set up when we built the system\" | Landscape changes (new client, new system addition) invalidate existing routes; broken routes cause silent non-delivery of transports | After any landscape change, run `STMS → Overview → Transport Routes` and verify consistency check passes |\n| Restart a crashed work process via SM50 without investigating the dump | \"The process is back, problem solved\" | The dump in ST22 contains the root cause; restarting without reading it means the same crash recurs | Always capture the ST22 dump before restarting; open an OSS message if the dump is SAP code |\n| Apply support packs in production without a rollback plan | \"We've applied packs before without issues\" | SPAM has no automatic rollback for already-applied packs; partially applied packs leave the system in an inconsistent state | Pre-patch: document current kernel\u002FSP level, take HANA snapshot, confirm backup completed. Define rollback procedure before starting. |\n| Unlock a user with SU01 in production to \"fix a login issue\" | \"The user is locked and has a meeting now\" | Production user unlocks without investigation mask repeated authentication failures, brute-force attempts, or incorrect logon data | Check SM20 (security audit log) for lock reason before unlocking; correct root cause (password reset via SSPR if available) |\n\n## Red Flags\n\nWatch for these in your own reasoning — each signals a controls or stability risk:\n\n- \"I'll just make this change directly in production...\" → Stop. Raise a change request. No exceptions regardless of urgency — escalate through emergency change procedure.\n- \"The transport queue is getting long, let me clean it up...\" → Do not delete transports without explicit approval. Long queues are a process problem, not a technical one.\n- \"The system is slow, let me restart the dispatcher...\" → A dispatcher restart is a last resort that drops all active sessions. Investigate via SM50\u002FSM66 and ST22 first.\n- \"ST22 shows old dumps, nothing new...\" → Check the date filter. Old unresolved dumps in ST22 indicate recurring issues that were never root-caused.\n- \"I'll set the user's password directly in SU01...\" → In SSO landscapes, manual password resets bypass identity provider sync. Confirm the authentication method (SU01 → Logon Data tab) before touching the password.\n- \"Let me increase the work process count to fix the bottleneck...\" → Work process count is bounded by hardware and license. Check SM50 utilization pattern first — more processes rarely fix the real problem.\n\n\u003CHARD-GATE>\nBefore any production system change: confirm a change request exists and is approved, a rollback procedure is documented, affected users\u002Fbusiness processes have been notified, and a post-change verification plan is defined. Do not proceed with any production change without these four items confirmed in writing.\n\u003C\u002FHARD-GATE>\n\n## Key Concepts\n\n### System Landscape\n- **Three-system landscape:** DEV (development and customizing), QAS (testing and integration), PRD (production). Changes flow DEV → QAS → PRD via STMS transport management.\n- **Client:** Logical separation within an SAP system. Clients share hardware but have independent application data. Client 000 (SAP default), 001 (copy template), customer clients (e.g., 100, 200).\n- **Client Settings (SCC4):** Controls client changeability (modifiable, not modifiable), cross-client object changes, and client role (production, test, customizing). Production client must be set to \"Not Modifiable.\"\n\n### Transport Management (STMS)\n- **Transport Request Types:** Workbench requests (SE01 — cross-client, repository objects), Customizing requests (SE09 — client-specific settings).\n- **Transport Route:** Defines which systems receive transports from which sources. Configured in STMS → Transport Routes.\n- **Import Queue:** Pending transports for a system. STMS → Import Queue → select system. Imports should follow sequence (transport number order) unless explicitly desequenced with documentation.\n- **SE10:** Overview of all transport requests for the logged-in user. Use to release and monitor request status.\n\n### User Management\n- **SU01:** Single user maintenance — create, change, lock, unlock, assign roles, set validity dates.\n- **SU10:** Mass user maintenance — apply role assignments or locks across multiple users simultaneously.\n- **SU53:** Authorization check analysis — displays the failed authorization object with actual vs. required field values. First tool to use for \"no authorization\" errors.\n- **SU24:** Transaction code to authorization object mapping — defines which auth objects are checked for each tcode, and whether the check is active, inactive, or proposed.\n- **Profile Generator (PFCG):** Role maintenance — creates authorization profiles from organizational levels and object selections. Always use PFCG to manage roles, never direct profile editing.\n\n### Background Job Management\n- **Job Classes:** A (high priority, reserved processing), B (normal), C (low priority, background). Production critical jobs should be class A or B.\n- **Job Chains:** Predecessor dependencies set in SM36 → \"After Job\" to sequence jobs. Avoids time-based scheduling that fails when previous job runs long.\n- **SM37:** Job monitoring — filter by user, job name, date, status. Check for status \"Cancelled\" or \"Active\" jobs running longer than expected.\n\n### System Monitoring\n- **SM50:** Work processes on the current application server — status, type (DIA, BTC, SPO, UPD), CPU, report name. Identify running long or stuck processes.\n- **SM51:** List of active application servers. Allows SM50 drill-through to individual servers.\n- **SM66:** Global work process overview across all application servers — critical for production load analysis.\n- **SM21:** System log — OS-level and R\u002F3 messages. Filter to ERROR and WARNING class for post-change review.\n- **ST22:** ABAP Runtime Error (short dump) viewer. Contains program, line, runtime value, and call stack. Must be analyzed before restart.\n\n### Performance Analysis\n- **ST02:** Buffer statistics — hit ratios for program buffer, table buffer, CUA buffer, screen buffer. Hit ratio below 95% for program\u002Ftable buffers indicates undersizing.\n- **ST03N \u002F ST03:** Workload Monitor — analysis of dialog, background, update, RFC response times by hour\u002Fday. Baseline performance before maintenance windows.\n- **ST06:** OS Monitor — CPU, memory, disk I\u002FO at OS level. Correlates with SM50\u002FSM66 work process saturation.\n- **SM12:** Lock entry table — identify and release stuck enqueue locks. Stuck locks block user transactions.\n\n### HANA Administration\n- **HANA Studio \u002F HANA Cockpit:** Primary tools for DBA tasks — backup scheduling, alert monitoring, memory analysis, user management.\n- **Backup\u002FRecovery:** HANA supports full, incremental, and differential data backups plus log backups. Recovery point objective (RPO) drives log backup frequency — production typically every 15–30 minutes.\n- **HANA Alerts:** Configured in HANA Cockpit. Critical alerts: low memory, high CPU, backup failure, replication lag (in scale-out). Integrate with SAP Alert Notification Service.\n- **Table Distribution (Scale-Out):** In scale-out HANA, monitor partition placement and rebalancing operations. Avoid manual redistribution during business hours.\n\n### Maintenance Procedures\n- **SPAM (Support Package Manager):** Applies ABAP support packages (SPs) and SAP Notes. Import queue shows available packages from SAP support portal. Always apply in the correct sequence.\n- **SAINT (Add-On Installation Tool):** Installs and upgrades add-on components (e.g., IS-Retail, SAP GRC, third-party add-ons). Requires system downtime in most cases.\n- **Kernel Upgrade:** Replace executables in the OS-level kernel directory. Requires system stop. Always verify the new kernel is certified for the current database and OS version via SAP Product Availability Matrix (PAM).\n- **Cloud ALM \u002F Solution Manager:** Central hub for transport monitoring, system monitoring dashboards, job monitoring, and IT calendar (maintenance window management).\n\n## Transaction Codes\n\n| TCode | Purpose |\n|-------|---------|\n| STMS | Transport Management System |\n| SE01 | Transport Organizer (Workbench + Customizing) |\n| SE09 | Customizing Requests (client-specific) |\n| SE10 | All Transport Requests |\n| SCC4 | Client Administration |\n| SCC1 | Client Copy (local) |\n| SCCL | Local Client Copy |\n| SU01 | User Maintenance (single user) |\n| SU10 | User Mass Maintenance |\n| SU53 | Authorization Error Analysis |\n| SU24 | Auth Object Checks per TCode |\n| PFCG | Role Maintenance (Profile Generator) |\n| SM36 | Define Background Jobs |\n| SM37 | Monitor Background Jobs |\n| SM50 | Work Process Monitor (local server) |\n| SM51 | Application Server List |\n| SM66 | Global Work Process Monitor |\n| SM21 | System Log |\n| ST22 | ABAP Runtime Error (Dump) Analysis |\n| SM12 | Lock Entry Table |\n| ST02 | Buffer Statistics |\n| ST03N | Workload Monitor |\n| ST06 | OS Monitor |\n| SPAM | Support Package Manager |\n| SAINT | Add-On Installation Tool |\n\n## Integration Points\n\n- **Cloud ALM \u002F Solution Manager:** Receives system monitoring data via Diagnostics Agent (SMD Agent). Provides centralized dashboards, transport tracking, and IT calendar for maintenance window coordination.\n- **ITSM Tools (ServiceNow, Jira):** Change requests and incident tickets must reference SAP transport numbers and system change details for audit trail.\n- **HANA Database:** Application servers connect via HANA JDBC. DBA Cockpit (DBACOCKPIT) provides SQL-level monitoring from ABAP; HANA Cockpit for native DBA tasks.\n- **Identity Providers (LDAP\u002FAD\u002FIAS):** SNC (Secure Network Communications) or SAML integration for SSO. Changes to LDAP connectivity affect all user logons — treat as high-risk change.\n- **Backup Infrastructure:** HANA backupcatalog must align with the organization's backup retention policy. Coordinate with infrastructure team for backup storage and off-site replication.\n\n## Verification\n\nThis skill is complete ONLY when ALL of the following are true:\n\n- [ ] Change request exists, is approved, and references all affected systems and transport numbers\n- [ ] Pre-change baseline captured: SM21 and ST22 reviewed, ST03N workload snapshot taken\n- [ ] Post-change verification completed within 30 minutes: SM21 clear, ST22 no new dumps, SM50 work processes stable\n- [ ] Transport import sequence verified in STMS: no transports skipped, import log shows no errors\n- [ ] Buffer consistency checked after support pack or kernel change: no inconsistency errors reported\n- [ ] Post-change communication sent to affected business users confirming system availability\n\n**Evidence required:** STMS import log showing successful completion; ST22 showing no new dumps post-change; change request updated to \"Closed\" with actual end time.\n\n## Next Skill\n\nAfter Basis maintenance or system change: `verification-before-completion`\nFor security role and authorization changes: `security-grc`\nFor integration connectivity issues post-change: `integration-suite`\n\n## Related Skills\n\n- `security-grc` — User authorization concepts and SoD analysis\n- `abap-cloud` — ABAP development impacting system objects\n- `troubleshooting` — Diagnosing ABAP dumps and runtime errors\n- `integration-suite` — RFC destinations and middleware connectivity\n","# SAP Basis \u002F System Administration\n\nGoverns all SAP system administration activities. The landscape is the foundation everything else runs on — changes to production without proper controls, untested transports, and unmonitored systems create outages that are 100% preventable.\n\n## Content Routing\n\n| Topic | Section |\n|-------|---------|\n| Transport management | Iron Laws + Transaction Codes |\n| User and authorization management | Key Concepts + Transaction Codes |\n| System monitoring and dumps | Transaction Codes + Red Flags |\n| Performance analysis | Key Concepts + Transaction Codes |\n| Support pack \u002F upgrade procedures | Key Concepts |\n| HANA administration | Key Concepts |\n\n## Iron Laws\n\n1. **NEVER CHANGE PRODUCTION WITHOUT CHANGE MANAGEMENT APPROVAL.** Every change to a production system — transport import, manual configuration, kernel patch, support pack, user role change — requires a documented change request approved through the organization's change management process (Cloud ALM, Solution Manager, or equivalent). \"Emergency\" changes require emergency change procedures, not bypassing controls.\n2. **ALWAYS CHECK SYSTEM LOGS BEFORE AND AFTER MAINTENANCE WINDOWS.** SM21 (system log) and ST22 (ABAP dumps) must be reviewed immediately before a maintenance window starts (to establish baseline) and within 30 minutes of completion. New dumps or log errors post-maintenance are caused by the maintenance — don't assume otherwise.\n3. **NEVER DELETE TRANSPORTS FROM THE IMPORT QUEUE WITHOUT DOCUMENTATION.** Removing a transport from STMS import queue permanently excludes it from the landscape unless re-imported manually. Deleting without documentation makes the gap impossible to detect in future audits or when troubleshooting missing functionality.\n4. **ALWAYS VERIFY BUFFER CONSISTENCY AFTER SUPPORT PACK APPLICATION.** Support packs modify ABAP repository objects, DDIC, and customizing. After application, run `\u002FSDF\u002FCDPOS_REORG` or use RSBC_BUFFER_CONSISTENCY to check buffer states. Inconsistent buffers after patching cause intermittent transaction failures that appear unrelated to the patch.\n\n## Rationalization Table\n\n| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |\n|---|---|---|---|\n| Import a transport directly to production to \"save time\" | \"It's a small config change, we tested it manually\" | Untested transports — even small ones — cause inconsistencies; they bypass QAS regression; they're undocumented and unauditable | Every transport must follow DEV → QAS → PRD. For emergencies: import to QAS first, get sign-off, import to PRD same day |\n| Create an RFC destination in production without a transport | \"RFC destinations can't be transported anyway\" | Manual production changes are invisible to future teams; RFC destinations with embedded credentials are a security exposure | Use SM59 transport flag where available; document all manual prod changes in the change request |\n| Schedule a background job in production without SM36 job documentation | \"The business asked me to add this job today\" | Undocumented jobs cause confusion, duplicate scheduling, and collision with existing job chains | Define the job in SM36 with proper job class, schedule, and owner; document in the ITSM ticket |\n| Skip STMS transport route verification after landscape change | \"The routes were set up when we built the system\" | Landscape changes (new client, new system addition) invalidate existing routes; broken routes cause silent non-delivery of transports | After any landscape change, run `STMS → Overview → Transport Routes` and verify consistency check passes |\n| Restart a crashed work process via SM50 without investigating the dump | \"The process is back, problem solved\" | The dump in ST22 contains the root cause; restarting without reading it means the same crash recurs | Always capture the ST22 dump before restarting; open an OSS message if the dump is SAP code |\n| Apply support packs in production without a rollback plan | \"We've applied packs before without issues\" | SPAM has no automatic rollback for already-applied packs; partially applied packs leave the system in an inconsistent state | Pre-patch: document current kernel\u002FSP level, take HANA snapshot, confirm backup completed. Define rollback procedure before starting. |\n| Unlock a user with SU01 in production to \"fix a login issue\" | \"The user is locked and has a meeting now\" | Production user unlocks without investigation mask repeated authentication failures, brute-force attempts, or incorrect logon data | Check SM20 (security audit log) for lock reason before unlocking; correct root cause (password reset via SSPR if available) |\n\n## Red Flags\n\nWatch for these in your own reasoning — each signals a controls or stability risk:\n\n- \"I'll just make this change directly in production...\" → Stop. Raise a change request. No exceptions regardless of urgency — escalate through emergency change procedure.\n- \"The transport queue is getting long, let me clean it up...\" → Do not delete transports without explicit approval. Long queues are a process problem, not a technical one.\n- \"The system is slow, let me restart the dispatcher...\" → A dispatcher restart is a last resort that drops all active sessions. Investigate via SM50\u002FSM66 and ST22 first.\n- \"ST22 shows old dumps, nothing new...\" → Check the date filter. Old unresolved dumps in ST22 indicate recurring issues that were never root-caused.\n- \"I'll set the user's password directly in SU01...\" → In SSO landscapes, manual password resets bypass identity provider sync. Confirm the authentication method (SU01 → Logon Data tab) before touching the password.\n- \"Let me increase the work process count to fix the bottleneck...\" → Work process count is bounded by hardware and license. Check SM50 utilization pattern first — more processes rarely fix the real problem.\n\n\u003CHARD-GATE>\nBefore any production system change: confirm a change request exists and is approved, a rollback procedure is documented, affected users\u002Fbusiness processes have been notified, and a post-change verification plan is defined. Do not proceed with any production change without these four items confirmed in writing.\n\u003C\u002FHARD-GATE>\n\n## Key Concepts\n\n### System Landscape\n- **Three-system landscape:** DEV (development and customizing), QAS (testing and integration), PRD (production). Changes flow DEV → QAS → PRD via STMS transport management.\n- **Client:** Logical separation within an SAP system. Clients share hardware but have independent application data. Client 000 (SAP default), 001 (copy template), customer clients (e.g., 100, 200).\n- **Client Settings (SCC4):** Controls client changeability (modifiable, not modifiable), cross-client object changes, and client role (production, test, customizing). Production client must be set to \"Not Modifiable.\"\n\n### Transport Management (STMS)\n- **Transport Request Types:** Workbench requests (SE01 — cross-client, repository objects), Customizing requests (SE09 — client-specific settings).\n- **Transport Route:** Defines which systems receive transports from which sources. Configured in STMS → Transport Routes.\n- **Import Queue:** Pending transports for a system. STMS → Import Queue → select system. Imports should follow sequence (transport number order) unless explicitly desequenced with documentation.\n- **SE10:** Overview of all transport requests for the logged-in user. Use to release and monitor request status.\n\n### User Management\n- **SU01:** Single user maintenance — create, change, lock, unlock, assign roles, set validity dates.\n- **SU10:** Mass user maintenance — apply role assignments or locks across multiple users simultaneously.\n- **SU53:** Authorization check analysis — displays the failed authorization object with actual vs. required field values. First tool to use for \"no authorization\" errors.\n- **SU24:** Transaction code to authorization object mapping — defines which auth objects are checked for each tcode, and whether the check is active, inactive, or proposed.\n- **Profile Generator (PFCG):** Role maintenance — creates authorization profiles from organizational levels and object selections. Always use PFCG to manage roles, never direct profile editing.\n\n### Background Job Management\n- **Job Classes:** A (high priority, reserved processing), B (normal), C (low priority, background). Production critical jobs should be class A or B.\n- **Job Chains:** Predecessor dependencies set in SM36 → \"After Job\" to sequence jobs. Avoids time-based scheduling that fails when previous job runs long.\n- **SM37:** Job monitoring — filter by user, job name, date, status. Check for status \"Cancelled\" or \"Active\" jobs running longer than expected.\n\n### System Monitoring\n- **SM50:** Work processes on the current application server — status, type (DIA, BTC, SPO, UPD), CPU, report name. Identify running long or stuck processes.\n- **SM51:** List of active application servers. Allows SM50 drill-through to individual servers.\n- **SM66:** Global work process overview across all application servers — critical for production load analysis.\n- **SM21:** System log — OS-level and R\u002F3 messages. Filter to ERROR and WARNING class for post-change review.\n- **ST22:** ABAP Runtime Error (short dump) viewer. Contains program, line, runtime value, and call stack. Must be analyzed before restart.\n\n### Performance Analysis\n- **ST02:** Buffer statistics — hit ratios for program buffer, table buffer, CUA buffer, screen buffer. Hit ratio below 95% for program\u002Ftable buffers indicates undersizing.\n- **ST03N \u002F ST03:** Workload Monitor — analysis of dialog, background, update, RFC response times by hour\u002Fday. Baseline performance before maintenance windows.\n- **ST06:** OS Monitor — CPU, memory, disk I\u002FO at OS level. Correlates with SM50\u002FSM66 work process saturation.\n- **SM12:** Lock entry table — identify and release stuck enqueue locks. Stuck locks block user transactions.\n\n### HANA Administration\n- **HANA Studio \u002F HANA Cockpit:** Primary tools for DBA tasks — backup scheduling, alert monitoring, memory analysis, user management.\n- **Backup\u002FRecovery:** HANA supports full, incremental, and differential data backups plus log backups. Recovery point objective (RPO) drives log backup frequency — production typically every 15–30 minutes.\n- **HANA Alerts:** Configured in HANA Cockpit. Critical alerts: low memory, high CPU, backup failure, replication lag (in scale-out). Integrate with SAP Alert Notification Service.\n- **Table Distribution (Scale-Out):** In scale-out HANA, monitor partition placement and rebalancing operations. Avoid manual redistribution during business hours.\n\n### Maintenance Procedures\n- **SPAM (Support Package Manager):** Applies ABAP support packages (SPs) and SAP Notes. Import queue shows available packages from SAP support portal. Always apply in the correct sequence.\n- **SAINT (Add-On Installation Tool):** Installs and upgrades add-on components (e.g., IS-Retail, SAP GRC, third-party add-ons). Requires system downtime in most cases.\n- **Kernel Upgrade:** Replace executables in the OS-level kernel directory. Requires system stop. Always verify the new kernel is certified for the current database and OS version via SAP Product Availability Matrix (PAM).\n- **Cloud ALM \u002F Solution Manager:** Central hub for transport monitoring, system monitoring dashboards, job monitoring, and IT calendar (maintenance window management).\n\n## Transaction Codes\n\n| TCode | Purpose |\n|-------|---------|\n| STMS | Transport Management System |\n| SE01 | Transport Organizer (Workbench + Customizing) |\n| SE09 | Customizing Requests (client-specific) |\n| SE10 | All Transport Requests |\n| SCC4 | Client Administration |\n| SCC1 | Client Copy (local) |\n| SCCL | Local Client Copy |\n| SU01 | User Maintenance (single user) |\n| SU10 | User Mass Maintenance |\n| SU53 | Authorization Error Analysis |\n| SU24 | Auth Object Checks per TCode |\n| PFCG | Role Maintenance (Profile Generator) |\n| SM36 | Define Background Jobs |\n| SM37 | Monitor Background Jobs |\n| SM50 | Work Process Monitor (local server) |\n| SM51 | Application Server List |\n| SM66 | Global Work Process Monitor |\n| SM21 | System Log |\n| ST22 | ABAP Runtime Error (Dump) Analysis |\n| SM12 | Lock Entry Table |\n| ST02 | Buffer Statistics |\n| ST03N | Workload Monitor |\n| ST06 | OS Monitor |\n| SPAM | Support Package Manager |\n| SAINT | Add-On Installation Tool |\n\n## Integration Points\n\n- **Cloud ALM \u002F Solution Manager:** Receives system monitoring data via Diagnostics Agent (SMD Agent). Provides centralized dashboards, transport tracking, and IT calendar for maintenance window coordination.\n- **ITSM Tools (ServiceNow, Jira):** Change requests and incident tickets must reference SAP transport numbers and system change details for audit trail.\n- **HANA Database:** Application servers connect via HANA JDBC. DBA Cockpit (DBACOCKPIT) provides SQL-level monitoring from ABAP; HANA Cockpit for native DBA tasks.\n- **Identity Providers (LDAP\u002FAD\u002FIAS):** SNC (Secure Network Communications) or SAML integration for SSO. Changes to LDAP connectivity affect all user logons — treat as high-risk change.\n- **Backup Infrastructure:** HANA backupcatalog must align with the organization's backup retention policy. Coordinate with infrastructure team for backup storage and off-site replication.\n\n## Verification\n\nThis skill is complete ONLY when ALL of the following are true:\n\n- [ ] Change request exists, is approved, and references all affected systems and transport numbers\n- [ ] Pre-change baseline captured: SM21 and ST22 reviewed, ST03N workload snapshot taken\n- [ ] Post-change verification completed within 30 minutes: SM21 clear, ST22 no new dumps, SM50 work processes stable\n- [ ] Transport import sequence verified in STMS: no transports skipped, import log shows no errors\n- [ ] Buffer consistency checked after support pack or kernel change: no inconsistency errors reported\n- [ ] Post-change communication sent to affected business users confirming system availability\n\n**Evidence required:** STMS import log showing successful completion; ST22 showing no new dumps post-change; change request updated to \"Closed\" with actual end time.\n\n## Next Skill\n\nAfter Basis maintenance or system change: `verification-before-completion`\nFor security role and authorization changes: `security-grc`\nFor integration connectivity issues post-change: `integration-suite`\n\n## Related Skills\n\n- `security-grc` — User authorization concepts and SoD analysis\n- `abap-cloud` — ABAP development impacting system objects\n- `troubleshooting` — Diagnosing ABAP dumps and runtime errors\n- `integration-suite` — RFC destinations and middleware connectivity\n",{"name":5,"description":7},"main","cf5d032baea1657808fa74369439ea7e9c7e0a20","skills\u002Fmodules\u002Fsystem-admin",3,"https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers","https:\u002F\u002Fsap-superpowers.vercel.app\u002F","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24","2026-08-23 17:03:43",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add vigneshbarani24\u002Fsap-superpowers --skill system-admin",{"tool":55,"command":56},"bunx","bunx skills add vigneshbarani24\u002Fsap-superpowers --skill system-admin",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vigneshbarani24\u002Fsap-superpowers --skill system-admin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmodules\u002Fsystem-admin\u002FSKILL.md",true,[],[64,90,97,106,115,124],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":36},"01M6EQTMCBV605ETS5WWEQX209","s4hana-migration","Use when advising on S\u002F4HANA migration approach, assessing greenfield vs brownfield vs selective data transition options, analyzing custom code impact, reviewing simplification items, or building a migration business case or timeline.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fs4hana-migration\u002FSKILL.md",[],[71,72,73,74,75,76,77,78,79,80,81,82,29,83,84,85,86,87,88,89],"migration","s4hana migration","data","case","impact","discover","simplification","project","brownfield","options","business case","project manager","business","technical","architect","timeline","analyzing","code","prepare",{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":36},"01M6EQTGJHSYYQDMBJY0APE19X","rise-licensing","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Frise-licensing\u002FSKILL.md",[],[96],"rise licensing",{"skillNo":98,"name":99,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":36},"01M6EQTCVAJPYQ7A8SA49A1Y72","joule-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fjoule-strategy\u002FSKILL.md",[],[103,104,105],"joule strategy","joule","strategy",{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":36},"01M6EQTA7RMJ6RNFDTK1E2E9YY","clean-core-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fclean-core-strategy\u002FSKILL.md",[],[112,113,114,105],"clean core strategy","clean","core",{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":36},"01M6EQT6QCR8MJ7J62ZP8WZ578","activate-methodology","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Factivate-methodology\u002FSKILL.md",[],[121,122,123],"methodology","activate","activate methodology",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":36},"01M6EQT3XFHC6Y2F0EWQ62PHSR","strategic","strategic skills category for SAP Superpowers. Contains 5 sub-skills.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002FSKILL.md",[],[126,131,26],"superpowers"]