Top 30 SAP BASIS Interview Questions & Answers for 2026

If you’re preparing for an SAP BASIS interview in 2026, here’s the honest truth: the questions have changed. Standard definitions and transaction codes won’t cut it anymore. Interviewers today want to know how you handle real scenarios — S/4HANA conversions that go wrong at 2 AM, HANA databases hitting 95% memory, transport imports that break production. That’s what this guide is for.

📚 Related resources on this blog:
• ECC to S/4HANA Conversion – Complete Roadmap
• SAP HANA DBA Calculations Guide
• BW on HANA Upgrade via SUM DMO
• SAP Tracing for Troubleshooting
• SAP Load Balancing Analysis Tool
• 4-Tier Roadmap: SAP Basis to Cloud Platform Admin

I’ve compiled 30 of the most commonly asked SAP BASIS interview questions for 2026, organized by experience level and topic area. Each question includes a practical, real-world answer — not textbook definitions. Whether you’re a fresher or a senior consultant aiming for that architect role, work through these and you’ll walk into your interview ready.

Part 1: SAP BASIS Interview Questions for Freshers

Q1. What is SAP BASIS?

SAP BASIS is the technical foundation of any SAP system. Think of it as the operating system for SAP — it handles installation, configuration, monitoring, performance tuning, transport management, and security. Without BASIS, the SAP applications (FI, CO, SD, MM) simply don’t run. In 2026, that definition has expanded to include cloud platforms like SAP BTP and hybrid landscape management.

Q2. What is an SAP system landscape?

The standard SAP landscape consists of three tiers: Development (DEV) — where changes are built; Quality (QAS) — where they’re tested; and Production (PRD) — the live environment. Changes flow from DEV → QAS → PRD via the Transport Management System (TMS). Some organizations also add a Sandbox system for experimentation and a Pre-Production (PRE) for final validation.

Q3. Explain the three-tier SAP architecture.

SAP follows a three-tier client-server architecture: the Presentation Layer (SAP GUI, Fiori Launchpad), the Application Layer (where dispatcher and work processes handle user requests), and the Database Layer (where data is stored and retrieved). In S/4HANA, this gets interesting — the application and database are tightly coupled, with HANA handling both transaction processing and analytics in memory.

Q4. What is a client in SAP?

A client is a logical, self-contained unit within an SAP system with its own master data, configuration, and user base. Multiple clients can exist in one system (e.g., Client 800 for testing, Client 100 for production training). Clients are separated at the database level by the MANDT field. After new system installation, SAP creates three default clients: 000 (SAP reference), 001 (copy of 000), and 066 (EarlyWatch).

Q5. What is the Transport Management System (TMS)?

TMS manages the movement of configuration and development objects between SAP systems. It has two request types: Workbench requests (cross-client — Repository objects like programs, classes, screens) and Customizing requests (client-specific — configuration data). TMS handles import queues, dependency checks, and automated import scheduling.

Q6. What is SAP GUI?

SAP GUI is the desktop client that connects users to SAP systems. The main flavors are SAP GUI for Windows (most common, full functionality), SAP GUI for Java (cross-platform, now largely phased out), and SAP GUI for HTML (browser-based). In 2026, Fiori is gradually replacing SAP GUI for most end-user transactions, but BASIS admins still live in GUI for administration.

Q7. What is an SAP instance?

An instance is a set of SAP work processes, memory buffers, and services that form one functioning SAP system. A Central Instance (CI) contains all dispatcher, work processes, message server, and gateway. A Dialog Instance (DI) adds more work processes to handle additional user load. In S/4HANA, the traditional CI/DI concept is evolving with the HANA database using a single application server model.

Q8. Name some databases SAP supports.

Currently: SAP HANA (primary, mandatory for S/4HANA), Oracle, Microsoft SQL Server, and IBM DB2. For non-production, SAP also supports ASE (Sybase) and MaxDB. Since S/4HANA only runs on HANA, most organizations are migrating away from legacy databases — making HANA administration the single most important skill in 2026 BASIS interviews.

Q9. What is the purpose of ST22 and SM21?

ST22 (ABAP Dump Analysis) — shows terminated programs with details on the error class, termination type, and source code location. SM21 (System Log) — displays system-wide events, errors, security messages, and startup/shutdown logs. Both are the first places to check when something breaks.

Q10. What are SAP work processes?

Work processes are the execution units within an SAP application server. The main types: Dialog (handles interactive user requests), Update (database changes, V1-critical, V2-deferred), Background (scheduled jobs), Spool (print output), Enqueue (lock management). In 2026, modern landscapes also include ABAP Push Channels (APC) and ICF work processes for web communication.

Part 2: Experienced Professional Questions

Q11. What is a system refresh? Walk me through the process.

A system refresh copies production data into a non-production system (QA or DEV) to create a realistic test environment. The process: (1) Request and plan the refresh window, (2) Back up target system, (3) Refresh the database from production backup, (4) Post-refresh steps: change RFC destinations, reconfigure printers, update background jobs to not send real emails, clear user buffers, and reset passwords. The #1 mistake? Forgetting to update RFCs pointing to other systems — you can accidentally trigger production workflows from a test system.

Q12. Explain kernel upgrade — how do you do it?

A kernel upgrade replaces the SAP executable files that run the system. Steps: (1) Download the kernel from SAP Support Portal (matching your OS, DB, and Unicode status), (2) Stop the SAP system, (3) Back up the current kernel directory, (4) Extract new kernel files into the kernel directory (/usr/sap//SYS/exe/run), (5) Restart the system, (6) Verify version via disp+work -V and check all functions work. Recent 2026 kernel versions include important security patches — never skip patch notes.

Q13. What’s the difference between local, remote, and export/import client copy?

Local client copy (SCCL) — copies within the same system, same database. Fastest. Remote client copy (SCC9) — copies between different systems via RFC. Good for refreshing a QA system from production. Export/Import (SCC8/SCC7) — exports to files, imports to target. Most flexible — works across OS and database platforms. Match the method to your scenario: local for quick DEV refreshes, remote for regular QA refreshes, export/import for cross-platform or one-time migrations.

Q14. How do you monitor SAP system performance?

I use a layered approach: ST06 for OS-level metrics (CPU, memory, disk), ST03 for workload analysis (response times, user distribution, top transactions), ST02 for buffer performance, ST04 for database performance, and DBACOCKPIT for detailed database analysis. In S/4HANA with HANA, HANA Studio and HANA Cockpit are essential for monitoring memory pressure, column store usage, and expensive statements. Also set up Cloud ALM or Solution Manager alerts for proactive notification.

Q15. How do you troubleshoot when a user reports “System is slow”?

Never trust the statement — trust the data. Step 1: Log into ST03N and check average response time for the past hour. Step 2: Use ST06 to rule out CPU/memory/disk bottlenecks at the OS level. Step 3: Check ST02 — if buffer quality is below 95%, investigate. Step 4: SM50 to see if work processes are stuck. Step 5: DBACOCKPIT for database locks or slow SQL. 80% of the time, it’s either a single user running a heavy report, a lock conflict, or a database issue. The other 20%? That’s where experience comes in.

Part 3: Advanced Scenario-Based Questions

Q16. All work processes are full — how do you handle it?

Log into SM50 right away. Look for processes with the same report name (likely a single user consuming everything) or processes in “PRIV” mode (private memory allocation). If one report is stuck, cancel it. If a user ran a massive query without selection criteria, kill it and advise them. If this is a recurring issue, you need to either increase dialog work processes or optimize the offending program. Don’t just keep canceling — find the root cause.

Q17. A transport import failed. What’s your troubleshooting approach?

Step 1: Check STMS import queue — look at the transport log for the failed request. Step 2: Common causes — missing prerequisites (earlier transports not imported), authorization issues, locked objects, or data dictionary inconsistencies. Step 3: Fix the issue (import prerequisite requests, assign authorizations, unlock objects via SM12). Step 4: Re-import. Step 5: If it fails again, check the system log (SM21) and short dumps (ST22). For critical production failures, you may need to manually repair objects or restore from backup.

Q18. Walk me through an S/4HANA conversion using SUM with DMO.

The lifecycle: (1) Pre-requisites — check Simplification Item Catalog, run SUM Pre-Analysis, fix custom code, archive data. (2) Run Software Update Manager (SUM) with DMO option. DMO (Database Migration Option) combines the software update and database migration in a single process. (3) SUM phases: Preparation (checks, space, passwords), Execution (shadow instance creation, data migration, SPDD/SPAU adjustments), Post-processing (activation, import, final checks). (4) Validation — test critical business processes, Fiori apps, and integration scenarios. The biggest risk? Underestimating downtime. Always run a mock conversion first with production data volume.

Q19. How do you estimate downtime for an S/4HANA conversion?

Downtime in SUM has two phases: uptime (system partially available — pre-analysis, shadow instance) and downtime (system fully unavailable — data migration, table conversion, activation). To estimate: run a mock conversion in an environment with similar data volume. Multiply the mock downtime by a 1.5x safety factor. Key factors affecting downtime: data volume (especially large transparent tables), custom code complexity, and hardware performance. For large systems, consider downtime-optimized DMO or near-zero downtime strategies.

Q20. HANA database is consuming 95% memory. What do you do?

First, don’t panic — HANA is designed to use available memory. Check HANA Memory Overview in HANA Studio/Cockpit. Identify what’s consuming: column store tables, row store, or the SQL plan cache. Run SELECT * FROM M_HEAP_MEMORY for detailed breakdown. Common causes: a column table missing compression, a runaway SQL statement, or insufficient allocated memory. Fixes: enable compression for large tables, identify and optimize expensive SQL via M_EXPENSIVE_STATEMENTS, kill problematic sessions, and as a last resort add more memory or increase the allocation limit. If it’s a persistent issue, adjust table partitioning and eviction policies.

Part 4: Cloud & Modern SAP Questions

Q21. How has SAP BASIS changed with S/4HANA and the cloud?

Dramatically. A 2026 BASIS admin needs skills beyond traditional administration: HANA database management (in-memory, column store, partitioning), BTP integration (Cloud Connector, transport management for CPI), Cloud ALM instead of Solution Manager, Identity and access management for hybrid landscapes, and automation (Terraform, Ansible for SAP provisioning). The era of “just installing and monitoring” is over. Modern BASIS means cloud architecture, security governance, and automation engineering.

Q22. What’s your experience with SAP on Azure/AWS/GCP?

On Azure: SAP-certified VMs (M-series for HANA, E-series for application servers), Availability Sets/Zones for HA, Azure NetApp Files for shared storage, Azure Backup for HANA databases. On AWS: SAP-certified instances on EC2, EFS for transport directory, Launch Wizard for automated deployment. On GCP: Sole-tenant nodes for licensing, Hyperdisk for HANA performance. Key considerations across all hyperscalers: proximity placement groups (to minimize latency between app and DB), OS compatibility, and proper sizing for HANA memory requirements.

Q23. Explain SAP BTP and how BASIS admins interact with it.

SAP BTP (Business Technology Platform) is SAP’s PaaS offering — it’s the cloud layer where extensions, integrations, analytics, and AI reside. As a BASIS admin, you’ll interact with BTP through: Cloud Connector (secure tunnel between on-prem and BTP), BTP Cockpit (subaccount management, entitlements), Transport Management Service (moving CPI iFlows across environments), and Identity Authentication Service (IAS) for user management. Key skill: understanding the shared responsibility model — what SAP manages vs. what you manage in a RISE landscape.

Q24. Solution Manager vs Cloud ALM — what’s the BASIS impact?

Solution Manager 7.2 goes out of mainstream maintenance at the end of 2027. SAP Cloud ALM is the strategic replacement. Key differences: Cloud ALM is SaaS (zero maintenance for BASIS teams), has built-in SAP Activate content, and supports cloud-first monitoring. However, Cloud ALM lacks some features of SolMan — no ChaRM (Change Request Management), no deep Custom Code Management, and no built-in ITSM. The transition strategy: start using Cloud ALM for new cloud projects today, keep SolMan for existing on-premise landscapes, and plan a phased migration. SAP Focused Run can fill some gaps for advanced monitoring needs.

Q25. What is SAP Clean Core? Why does it matter to BASIS?

Clean Core is SAP’s strategy to keep the S/4HANA system as close to standard as possible while moving customizations to the BTP side-by-side extension layer. For BASIS admins: Clean Core means fewer custom code objects to break during upgrades, simplified testing, and faster release cycles. In practice: new developments should use the ABAP Cloud model (released APIs only), legacy custom code should be refactored or moved to BTP, and SAP Standard should not be modified directly. It’s the biggest shift in how we manage SAP systems since the move to HANA.

Part 5: The “Interviewer Trap” Questions

Q26. Tell me exactly where SUM stores its log files.

SUM stores logs under /usr/sap//SUM/abap/log/. The most important files: MIGRATE.XML (overall status), MIGRATE_PROTOCOL.XML (detailed step-by-step progress), and SUM_ERROR_LOG. In the DMO scenario, additional logs are under DMO/abap/log/. Knowing this path under pressure signals real hands-on experience.

Q27. What failed in your last migration project?

Be honest here. Good answers: “We underestimated data volume for one large transparent table with 2 billion rows — it added 4 hours to the downtime. We learned to check RSTAT and DAT files more carefully.” Or: “The SUM pre-analysis caught custom code that was modifying SAP standard tables directly — we had to stop the conversion, refactor that code, and reschedule.” Interviewers want honesty and learning, not perfection.

Q28. How do you know DMO is actively migrating data?

Watch the SUM GUI in real time — the progress bar for the “Data Migration” step advances in percentage. More granular: check MIGRATE_PROTOCOL.XML for the current migration phase and table being processed. In HANA Studio, you can monitor migration-related sessions executing CREATE TABLE or INSERT statements. At the OS level, monitor disk I/O on the HANA data volume — sustained high I/O indicates active migration.

Q29. How would you recover from a failed HANA backup?

Step 1: Check backup catalog (BACKUP CATALOG ENTRY queries) to understand what failed. Step 2: If it’s a transient issue (network, storage), retry. Step 3: If backup ID is corrupted, delete the failed entry and restart. Step 4: Verify the backup using BACKUP VALIDATE CHECK. Step 5: Set up BACKUP NOTIFICATION to alert on failures immediately — a silently failing backup is the most dangerous scenario in any SAP landscape.

Q30. Why should we hire YOU as our SAP BASIS consultant?

This is where you connect your experience to their landscape. Frame it as: “Your organization is migrating to S/4HANA on Azure within 18 months. I’ve done this three times — including one complex migration with 8TB of HANA data where I reduced downtime from 36 to 19 hours using downtime-optimized DMO. I also understand that the real value isn’t in the conversion itself — it’s in the Clean Core strategy after. That’s where I’ll help your team standardize on ABAP Cloud, move custom code to BTP, and reduce your upgrade effort for the next 10 years.” Be specific. Be relevant. Be confident.

📊 High-Priority Topics — Study Focus Table

If you’re short on time before your interview, prioritize these topics based on actual 2026 interview patterns:

✅ Final Tips for Your SAP BASIS Interview in 2026

• Know your TCodes cold: ST22, SM50, ST03, ST06, ST02, SM21, SM12, SU01, SU53, PFCG, DBACOCKPIT. If you fumble on these, the interviewer knows immediately you lack hands-on experience.
• Prepare one real WAR STORY: Every senior interviewer will ask for a migration or troubleshooting story. Have one ready — with actual metrics (data volume, downtime, team size, business impact).
• Cloud experience is non-negotiable: If you don’t have Azure/AWS/GCP experience on your resume, get a certification before the interview. SAP on cloud is the default in 2026, not the exception.
• Know the SAFE answers: For any production issue — “First, I assess the business impact. Then I stabilize, analyze root cause, fix, document, and verify.” This structure shows maturity.
• Use the STAR method: Situation, Task, Action, Result. Every scenario answer should follow this structure.
• Stay current: Check the SAP Cloud ALM Transition Guide and SAP BTP Developer’s Guide for the latest updates before your interview.

Conclusion

The SAP BASIS role has evolved more in the last three years than in the previous fifteen. The admin who only knows how to check SM21 and manage transports is being replaced by a professional who understands HANA memory architecture, cloud deployment models, automation, and Clean Core strategy. The 30 questions above are your roadmap — work through them, build your hands-on confidence, and you’ll be ready for whatever the interviewer throws at you.

Good luck! Drop a comment below if there’s a question you’ve faced in interviews that I should add to this list — I update this guide regularly based on actual interview feedback.