SAP Mock Interview: 20 Questions in 50 Minutes

Transactional apps let users create, change or approve business documents such as purchase requisitions. Analytical apps show KPIs and drill-down charts from live data using CDS views. Fact sheets show key information about an object and links to related objects; in S/4HANA many are now object pages. SAP also provides SAP GUI-based apps inside the launchpad for transactions without a native Fiori version.

Master data is relatively stable reference data used in many transactions, such as customers, suppliers, materials, GL accounts, cost centers and bank details. Transaction data is created by business events, such as sales orders, purchase orders, goods movements and invoices, and it refers to master data. Good master data quality is essential, because wrong master data causes wrong prices, postings and taxes in every transaction.

An SAP system has a presentation layer (SAP GUI, browser with Fiori), an application layer (one or more ABAP application servers running work processes that execute business logic), and a database layer (SAP HANA in S/4HANA). Users connect to the application server, which reads and writes the database. This separation lets companies scale by adding application servers and keeps the database central.

ECC runs on several databases such as Oracle, DB2 or HANA, uses many aggregate and index tables, and mainly uses SAP GUI. S/4HANA runs only on HANA, removes most aggregate tables, uses the Universal Journal (ACDOCA) for finance, Business Partner instead of separate customer and vendor masters, and offers Fiori apps. Mainstream maintenance for ECC 6.0 ends in 2027, which is why many Indian clients are running S/4HANA migration projects now.

SUM (Software Update Manager) is the Basis tool used to update SAP systems and to convert ECC to S/4HANA. DMO (Database Migration Option) is a SUM feature that combines the database migration to HANA and the software update in one run, so a customer on Oracle or DB2 can move to S/4HANA on HANA in a single downtime. Basis teams run test conversions several times before the production run.

S/4HANA can run on-premise in the customer's data centre or a hyperscaler they manage, as S/4HANA Cloud Private Edition (usually sold through RISE with SAP, a single-tenant system managed by SAP), or as S/4HANA Cloud Public Edition (multi-tenant SaaS with quarterly updates and limited customization). On-premise and Private Edition allow classic extensions and full customizing, while Public Edition needs a clean core and standard processes.

SAP Basis is the technical administration of SAP systems. Basis consultants install systems, apply support packages and upgrades, manage transports, clients and system copies, monitor performance, jobs and work processes, handle backups and HANA database tasks, and often manage users and security roles. In cloud setups such as RISE, many Basis tasks move to SAP or the hyperscaler, but customers still need Basis skills.

RISE with SAP is a subscription bundle that packages S/4HANA Cloud (mostly Private Edition), infrastructure on a hyperscaler such as AWS, Azure or Google Cloud, technical managed services, SAP BTP credits, and tools such as SAP Signavio for process insight. The customer pays one contract to SAP instead of buying licences, hardware and hosting separately. GROW with SAP is a similar offer focused on Public Edition for mid-size companies.

The Simplification List documents every functional and technical change in an S/4HANA release, such as removed transactions, changed tables and mandatory replacements. The SAP Readiness Check is a tool that analyses an existing ECC system and reports which simplification items apply, custom code impact, add-on compatibility, data volume and sizing. Together they help a team estimate the effort and plan a conversion project.

SAP GUI scripting is an automation interface that records and replays user actions in SAP GUI using VBScript or other languages. Teams use it for repetitive data entry, test automation and simple bots. It must be enabled on the server with profile parameter sapgui/user_scripting and on the client. Because it depends on screen layouts, it breaks when screens change, so APIs or Migration Cockpit are better for large loads.

Material type groups materials with the same business use, such as raw material (ROH), finished goods (FERT), semi-finished (HALB) and trading goods (HAWA). It controls which views are allowed, number range, price control and whether quantity and value are updated. Industry sector, such as mechanical engineering or retail, controls screen layout and field selection. Material type has the bigger impact on processes.

I combine ATC results with usage data from SCMON or UPL so unused objects are removed first. For used objects I fix mandatory findings first, such as removed tables, changed field lengths like the 40-character material number, and syntax errors. Performance and best-practice findings come later. I group similar fixes, use quick fixes in ADT where possible, and track progress with the custom code migration app.

I would analyse transaction usage with ST03N and the Fiori Apps Recommendations report to map transactions to standard Fiori apps. Then I design business roles per job with spaces and pages, activate apps in waves starting with high-volume users, keep SAP GUI for HTML tiles for transactions without apps, train key users, and collect feedback. Custom apps are built only where real gaps remain.

I ask the user to run SU53 right after the error, which shows the failed authorization check, including object and missing value. I compare it with their roles in SU01. If the access is valid for their job, I raise an access request through the approved process so the security team adds the correct role, rather than giving direct access. I also check segregation of duties rules before approval.

I would first check if a standard Fiori app on mobile meets the need, since Fiori is responsive. For offline use, I would consider SAP Build apps or the SAP Mobile Services on BTP. The app would call a released OData API or a custom RAP service through BTP destinations with secure authentication. I would design for limited connectivity, data sync and simple screens.

For operational KPIs I would start with embedded analytics: standard analytical Fiori apps and custom analytical queries on CDS views, which show live data. For management dashboards with charts and drill-down, I would connect SAP Analytics Cloud live to S/4HANA. If they need to combine data with non-SAP sources or long history, I would add SAP Datasphere. This avoids extracting data unnecessarily.

Situation: accounts users spent an hour daily filtering an ALV report. Task: reduce manual effort. Action: I studied their steps, created report variants and saved layouts, scheduled the report in the background with email output, and trained the team. Result: the daily effort dropped to about ten minutes, and the team lead asked me to do the same for two other reports.

Situation: SAP releases changes every year, and cloud products update quarterly. Task: stay current while working full time. Action: I follow SAP Community blogs and release notes, use SAP Learning Hub or free learning journeys, practice in a trial BTP account, and earn a certification every year or two. Result: I was the first in my team to work on RAP and Fiori elements, which helped us win a new extension project.

Situation: a conversion with four mock runs and many teams. Task: keep business and IT aligned. Action: I set a weekly steering update with simple status, risks and decisions needed, and daily stand-ups during mocks. I shared measured downtime and reconciliation results openly, including bad news early. Result: leadership approved an extra mock when timings were tight, and the final conversion finished within the planned weekend window.

Situation: invoices were posting to the wrong revenue account for a new product line. Task: find the cause across SD and FI. Action: I traced the billing document, found that the new materials had no account assignment group, and the VKOA entry was missing for the new combination. I fixed master data, added configuration through a transport, and reposted documents with finance. Result: correct revenue from that day and no audit issue.