Top 50 Most Asked SAP Interview Questions

Greenfield is a fresh implementation: new processes are designed and only selected master data and open items are migrated. Brownfield is a system conversion of an existing ECC system to S/4HANA, keeping configuration, custom code and history. Selective data transition, sometimes called bluefield, is a mix where a new shell system is built and chosen data, company codes or years are moved. The choice depends on process quality, custom code volume, history needs and timeline.

WRICEF lists the types of custom development in an SAP project: Workflows, Reports, Interfaces, Conversions, Enhancements and Forms. Some teams write RICEFW or add an extra letter for Fiori apps. Functional consultants write a functional specification for each object, and technical consultants build it and write a technical specification. Counting WRICEF objects helps estimate effort and track development during the Realize phase.

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.

Embedded analytics uses CDS views inside S/4HANA for real-time operational reporting on live data. SAP BW/4HANA is an on-premise enterprise data warehouse for historical, cross-system reporting. SAP Datasphere is the cloud data warehouse and data fabric on BTP that combines SAP and non-SAP data with business semantics. Many companies use embedded analytics for daily work and Datasphere or BW for group reporting.

Horizon is the current visual theme for SAP Fiori, replacing older themes like Quartz and Belize. It offers a modern look with updated colours, typography, icons and better accessibility, and it has light, dark and high-contrast variants. It is the default theme in recent S/4HANA and BTP releases. Users can change themes in the launchpad settings if the administrator allows it.

SAP is a German software company and also the common name for its ERP products. SAP S/4HANA stands for SAP Business Suite 4 SAP HANA. It is the fourth generation ERP suite, built to run only on the SAP HANA in-memory database. It replaced SAP ECC (ERP Central Component) as the main ERP product, with a simplified data model, real-time analytics and the Fiori user experience.

SAP HANA is SAP's in-memory, column-oriented relational database. It keeps data mainly in RAM and stores it by column, which makes aggregation and analytics very fast and allows one system to handle both transactions and reporting (OLTP and OLAP). It also offers compression, calculation views, text search, spatial and predictive functions. S/4HANA runs only on HANA, which allowed SAP to remove aggregate tables and simplify the data model.

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.

Work processes are the operating system processes that execute user and system requests. Dialog processes handle interactive steps, update processes write database changes asynchronously (V1 and V2), background processes run batch jobs, enqueue manages locks, and spool handles printing. The dispatcher assigns requests to free work processes. Basis checks them in SM50 or SM66, and long-running dialog steps often point to performance problems.

SAP GUI is the classic desktop client used to log on to SAP systems and run transactions. SAP Logon lists available systems, and after logon the SAP Easy Access menu shows a tree of transactions. Variants include SAP GUI for Windows, SAP GUI for Java and SAP GUI for HTML (Web GUI in a browser). In S/4HANA, Fiori is the main experience, but many consultants still use SAP GUI for configuration and technical work.

It is an online SAP catalogue that lists all Fiori apps with their app ID, business role, supported releases, required OData services, business catalogs and roles, and implementation steps. Consultants use it to find the right standard app for a process and to know which services and catalogs to activate. Searching by transaction code shows which Fiori app replaces a classic transaction.

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.

The material master holds all information about a material or product, organised in views such as Basic Data, Sales, Purchasing, MRP, Work Scheduling, Storage, Quality, Accounting and Costing. Different departments maintain their views at levels such as client, plant or sales organization. It is created with MM01 or the Manage Product Master Data app, and controls procurement, stock, valuation and selling of that material.

CVI is the synchronisation framework that links Business Partners with the classic customer (KNA1, KNB1, KNVV) and vendor (LFA1, LFB1, LFM1) tables. In S/4HANA every customer and vendor must exist as a BP. In a brownfield conversion, CVI must be configured and all customers and vendors converted to BPs in ECC before the technical conversion, which is a major pre-conversion task.

Some data is at client level, such as material description, base unit and material group, and applies to all plants. Plant-level data includes MRP, purchasing, work scheduling and usually valuation. Storage-location-level data covers storage bin and picking area. Sales data is at sales organization and distribution channel level, and warehouse data at warehouse number level. This lets each unit control its own settings.

Key areas are Finance (FI) for legal accounting, Controlling (CO) for internal cost and profit analysis, Materials Management (MM) for purchasing and inventory, Sales and Distribution (SD) for selling and billing, Production Planning (PP) for manufacturing, Quality Management (QM), Plant Maintenance (PM), Warehouse Management (EWM), and Project System (PS). HR is now mostly delivered by SAP SuccessFactors, while S/4HANA keeps some on-premise HCM options.

SAP CO (Controlling) supports internal management accounting. It tracks costs by cost centers, internal orders and projects, calculates product costs, and analyses profitability by customer, product or region through margin analysis. CO helps managers plan budgets, compare plan and actual costs, and allocate overheads. In S/4HANA, CO postings are in the same Universal Journal as FI, so both always reconcile.

SAP Ariba is a cloud procurement platform for sourcing, contracts, supplier management, guided buying and the Ariba Network, where buyers and suppliers exchange purchase orders and invoices. SAP Concur handles employee travel booking and expense reporting. Both integrate with S/4HANA, which remains the system of record for accounting and payments. Companies use them to extend core MM and FI processes.

QM (Quality Management) plans and records inspections, for example at goods receipt or during production, using inspection plans, inspection lots, results recording and usage decisions, and manages quality notifications. PM (Plant Maintenance, now part of Asset Management) maintains equipment and functional locations through notifications, maintenance orders, preventive maintenance plans and costs. Both are important in manufacturing, pharma and process industries.

Automatic account determination is configuration that tells SAP which GL accounts to post when a logistics transaction happens, so users never enter accounts manually. MM uses transaction keys such as BSX for stock and WRX for GR/IR in OBYC, based on valuation class and movement type. SD uses VKOA for revenue accounts. Errors here are a common cause of integration failures and wrong financial results.

VA11 or VA21 create an inquiry or quotation, VA01 creates a sales order, VL01N creates an outbound delivery, VL02N is used for picking and post goods issue, VF01 creates the billing document, and F-28 posts incoming payment. VA05 lists sales orders and VF04 processes the billing due list. In Fiori, Manage Sales Orders and Create Billing Documents apps cover the same.

SAP Business Application Studio (BAS) is a cloud development environment on SAP BTP based on Code-OSS. It offers dev spaces with SAP Fiori tools, generators for Fiori elements and freestyle apps, CAP development, service connections through BTP destinations, a preview with mock data, and deployment to the ABAP repository or BTP. Developers can also use VS Code with the same Fiori tools extensions locally.

I check the browser console and network calls for errors, then the gateway error logs. Upgrades often change the SAPUI5 version, so I look for deprecated controls or APIs, and check if the back-end service or CDS view changed. I test in quality with the UI5 support assistant, fix deprecated code, update the manifest's minimum UI5 version, and redeploy. Regular upgrade testing prevents surprises.

I show them their launchpad layout and the few apps they need, how to search apps, use filters and save views, and how list report and object page work together. I compare one familiar transaction with its Fiori app side by side. A short quick reference guide and a follow-up after a week usually build confidence, and their feedback helps improve role design.

A functional consultant understands a business area such as finance or sales, gathers requirements, configures the system in customizing (SPRO), writes functional specifications and tests processes. A technical consultant, usually an ABAP or integration developer, builds custom reports, enhancements, interfaces, forms and Fiori apps from those specifications. Basis consultants are a third group who install, maintain and secure the system. Freshers often start as functional or ABAP associates in support or implementation projects.

It compares business requirements against what standard SAP already offers. In fit-to-standard workshops the consultant demos the standard process in a best-practice system, and users confirm what fits, what needs configuration, and what is a real gap. Gaps are then solved by changing the process, by configuration, by a WRICEF development, or by a partner solution. The goal is to keep the core clean and avoid unnecessary custom code.

A client is an independent business unit inside one SAP system, identified by a three-digit number such as 100 or 200. Each client has its own master data, transaction data and users, while repository objects such as programs and tables are shared across all clients. Configuration can be client-specific or cross-client. A development system often has a configuration client, a unit test client and a sandbox client.

The Universal Journal is table ACDOCA, which stores all actual line items from Finance, Controlling, Asset Accounting and Material Ledger in one place. In ECC these were spread across many tables such as BSEG, COEP, FAGLFLEXA and ANEP with totals tables. With one table, FI and CO are reconciled by design, reporting reads line items directly, and month-end reconciliation work is greatly reduced.

The Fiori launchpad is the browser-based entry point for S/4HANA users. It shows tiles and links grouped into spaces and pages based on the user's roles. Each tile opens a Fiori app or a classic transaction in a web GUI. Users can search apps, personalise their home page, see notifications and use the same launchpad on desktop, tablet or phone.

/n opens a new transaction in the same session, /o opens a new session, /nend logs off with confirmation, /nex logs off without confirmation, /i closes the current session, and /h switches on debugging. Typing search_sap_menu finds transactions in the menu. F1 shows field help, F4 shows possible values, and F8 executes reports. These shortcuts save a lot of time for consultants and power users.

Open the SAP Fiori Apps Reference Library and search with the transaction code, such as ME21N. The results show matching apps with app ID, type, roles, catalogs and required back-end services. In the system, the Fiori launchpad content manager and the app search help find what is already active. Many classic transactions run as SAP GUI for HTML tiles when no native app exists.

A purchasing organization negotiates prices and conditions with suppliers and is responsible for procurement. It can be plant-specific (one per plant), company-code-specific (covering plants of one company code) or cross-company-code (central purchasing for many company codes, assigned only to plants). A purchasing group represents the buyer or team handling day-to-day purchasing activities.

I check the customer's sales area data in BP, such as pricing procedure indicator, price group and price list, and the material's sales data, such as material pricing group. Then I check condition records for the customer and material in the relevant condition types and validity dates. Finally I run the pricing analysis inside the sales order to see which condition was found and why others were skipped.

SAP FI (Financial Accounting) records all external financial transactions for legal reporting. Its main parts are General Ledger, Accounts Payable, Accounts Receivable, Asset Accounting and Bank Accounting. FI produces the balance sheet and profit and loss statement for each company code, handles taxes such as GST and TDS in India, and supports period closing. Every logistics transaction that has value creates an FI document.

SAP Analytics Cloud (SAC) is SAP's cloud tool for business intelligence, planning and predictive analytics. It connects live to S/4HANA, BW or Datasphere, or imports data, to build stories and dashboards. Finance teams use its planning features for budgets and forecasts. It is commonly used for management dashboards because it combines reporting and planning in one interface.

Order to cash is the selling cycle: an inquiry or quotation may lead to a sales order (VA01) with pricing, availability and credit checks, then an outbound delivery (VL01N) with picking and post goods issue, then billing (VF01) which posts revenue and receivables, and finally incoming payment is received and cleared in FI. It links SD, MM for stock and FI for accounting.

At post goods issue, the cost of goods sold account is debited and the inventory account is credited at the material's valuation price. At billing, the customer account is debited and revenue and output tax (GST) accounts are credited. Revenue accounts are found through revenue account determination (VKOA), using keys like account assignment group of customer and material.

Document flow shows all documents linked in a process chain, such as quotation, sales order, delivery, goods issue, invoice and accounting document. In SD transactions it is shown with the Display Document Flow button, and in Fiori as related documents or a process flow. It helps users and consultants see the status of each step and quickly find where a process is stuck.

S/4HANA integrates through OData and REST APIs, SOAP web services, IDocs, RFC and BAPIs, and events through SAP Event Mesh or Advanced Event Mesh. Middleware such as SAP Integration Suite (Cloud Integration) or older SAP PI/PO maps and routes messages. The SAP Business Accelerator Hub (api.sap.com) lists released APIs. Modern projects prefer released APIs and events over direct table access.

I read the full message, which usually names the transaction key, chart of accounts and valuation class, for example account determination for entry BSX not possible. I check the material's valuation class in the accounting view and OBYC settings for that key and valuation grouping. If the configuration is missing for a new valuation class or plant, I add it in development, test, and transport. Often the master data is the real issue.

Internal tables hold multiple rows of data in memory during program run time, similar to arrays of structures. Types are standard (index access, appended rows), sorted (kept sorted by key, binary search) and hashed (unique key access with constant time). Programs fill them with SELECT, then loop, read, modify or sort them. Choosing the right type matters for performance with large data.

Options include user exits and customer exits (older), BAdIs (Business Add-Ins, classic and new kernel-based), implicit and explicit enhancement points, and in S/4HANA, key user extensibility with custom fields and custom logic in Fiori apps. Developer extensibility uses released objects and ABAP Cloud. Modifications through the modification assistant are the last resort because they must be checked at every upgrade.

Code pushdown means moving data-intensive logic from the ABAP application server to the HANA database, so calculations happen close to the data and only results travel. Techniques include CDS views, ABAP SQL with aggregations and expressions, and AMDP (ABAP Managed Database Procedures) written in SQLScript. Instead of selecting millions of rows and looping in ABAP, the database filters and aggregates, which improves performance a lot.

In S/4HANA I would first try key user extensibility with the Custom Fields app, which adds the field to the database, Fiori UI, CDS views and APIs without code. If logic is needed, I use the Custom Logic app or a released BAdI. Only if these do not cover the case would I use classic enhancement such as a screen enhancement in ME21N. I document the choice for upgrade safety.

I would write a report that selects open orders using a CDS view or ABAP SQL with proper filters, formats the data to the agreed layout, and writes the file to an application server directory or sends it through SAP Integration Suite. I would add a selection screen with variants, logging with the application log (SLG1), error notifications, and schedule it in SM36 or Application Jobs. Testing covers volume and format checks.

Fiori elements are predefined floor plans, such as List Report, Object Page, Analytical List Page, Overview Page and Worklist, that generate the UI from metadata. The developer provides an OData service and CDS annotations describing fields, line items and facets, and the framework renders a consistent app with little JavaScript. This speeds development and keeps apps consistent and upgrade-safe compared to freestyle SAPUI5.

Users can first check the table settings, because many fields are available but hidden. If the field exists in the service but not the UI, a key user can use Adapt UI or a developer can add an app variant or annotation extension. If the field does not exist, the Custom Fields app can add it and enable it for the app. A custom app is the last option.

ERP (Enterprise Resource Planning) is software that runs core business processes such as finance, purchasing, sales, production, inventory and HR on one shared database. Businesses use it to remove separate spreadsheets and disconnected systems, so a sales order, a goods issue and the accounting entry all update the same data in real time. The result is one version of the truth, better control, faster month-end closing and easier compliance with tax and audit rules.

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.

SAP Activate is SAP's current delivery framework for S/4HANA projects. It combines SAP Best Practices (ready business process content), guided configuration and an agile, iterative approach. Its phases are Discover, Prepare, Explore, Realize, Deploy and Run. Instead of writing a long blueprint first, teams run fit-to-standard workshops on a preconfigured system, record gaps in a backlog and deliver in sprints, which shortens timelines and reduces custom code.