SAP Interview Questions: The 13 Worth Preparing

The SAP interview questions consultants get, grouped by topic: what each one tests, a short model answer, and the S/4HANA follow-ups to expect.

SAP interview questions for consultant roles test one thing above all: can you follow a business transaction through the system and explain what you did on a real project? Definitions only get you started; then come questions on how a purchase order becomes an accounting entry, what changed in S/4HANA, and what you would check when a posting fails. Below are 13 questions worth preparing, grouped by topic, each with what it tests and a short answer to adapt. Interviewing at SAP the company? See its own section below.

Why to prepare S/4HANA either way

In 2020 SAP announced that mainstream maintenance for the core applications of SAP Business Suite 7, which include SAP ERP 6.0, would run until the end of 2027, with optional extended maintenance until the end of 2030, and committed to maintaining SAP S/4HANA until the end of 2040. That timeline gives companies still on the older ERP a reason to move, so migration, the business partner and the universal journal are worth preparing even when the job ad only says "MM" or "FICO".

Fundamentals: the screening questions

1. What is SAP, in your own words?

Testing: plain explanation. Say that SAP is enterprise software in which finance, procurement, sales and logistics share one set of data, so a goods receipt in the warehouse reaches accounting without anyone re-keying it. Then name the modules you have worked in (FI, CO, MM, SD and so on) and stop.

2. What is the difference between master data and transaction data?

Testing: basics, plus whether you have seen bad data hurt a project. Master data changes rarely: customers, suppliers, materials, G/L accounts. Transaction data records events: purchase orders, goods receipts, invoices. The answer that stands out adds a consequence: wrong master data (a missing tax code, a wrong payment term) breaks every transaction that uses it.

Process questions: the functional round

3. Walk me through procure-to-pay, including the accounting.

Testing: MM–FI integration. Purchase requisition, purchase order, goods receipt, invoice, payment. Strong candidates explain the postings: in SAP's own training example, the goods receipt posts to a GR/IR (goods receipt/invoice receipt) clearing account, which holds the value of goods received but not yet invoiced, and the invoice is then posted with reference to the purchase order. SAP's training shows the accounts being found through MM automatic account determination, which works with transaction keys.

4. The goods receipt was valued at 300 and the invoice arrives at 320. What happens?

Testing: whether you know that differences have to land somewhere. This is SAP's own training example. A strong answer: the 20 does not disappear, and where it posts depends on the setup. For a material at standard price, it goes to a price difference account; for an item charged directly to a project or cost object, the difference goes to that object. Then say you would confirm it by opening the invoice document and checking which accounts it hit.

5. What is a posting key?

Testing: FI basics. SAP's training defines posting keys as controlling the account type, the debit or credit indicator and the field status of a line item. Know the common ones: 40 and 50 for G/L debit and credit, 21 and 31 for supplier debit and credit.

6. Explain the stages of the payment run.

Testing: sequence. Enter the parameters, run the proposal, which lists the invoices to be paid, carry out the payment run, which posts the payments, then print the payment forms. Say why the proposal matters: it is the point where someone reviews what is about to be paid before anything posts.

S/4HANA questions

7. What changed between the older SAP ERP and S/4HANA?

Testing: whether you know more than the name. Three points carry the answer. S/4HANA runs only on SAP's in-memory HANA database. Finance postings write line items to one table, the universal journal (ACDOCA), which SAP calls the single source of truth. And customers and suppliers are maintained as business partners, created through one entry point (transaction BP or the Fiori app). Expect a follow-up on customer/vendor integration (CVI); SAP's own S/4HANA project course has a lesson on the steps to business partner and CVI.

8. New implementation or system conversion: which would you recommend?

Testing: judgement, not vocabulary. A new implementation (greenfield) builds a fresh S/4HANA system and migrates data into it. A system conversion (brownfield) converts an existing SAP Business Suite system to S/4HANA. A third path, selective data transition, is used to consolidate or carve out parts of a landscape. A good answer does not pick one in the abstract: it asks about the client's custom code, whether their processes are worth keeping, and how much history they need.

9. How does fit-to-standard differ from a business blueprint?

Testing: recent project experience. The older five-phase model put a Business Blueprint phase before Realization. SAP Activate, used for S/4HANA, runs fit-to-standard workshops in its Explore phase instead: the implementation partner's experts demonstrate SAP's standard processes in a starter system, the business discusses where they fall short, and changes are meant to be limited to critical requirements, because each one adds maintenance at every upgrade. SAP's training also describes keeping a "clean core" (staying close to standard), which it says facilitates smooth system upgrades. If you ever pushed back on a customisation request, tell that story here.

10. How would you handle master data migration?

Testing: method. In S/4HANA Cloud, SAP's Migration Cockpit loads data either through staging tables (filled from XML or CSV templates) or by direct transfer over an RFC connection from an SAP ERP source system, with a guided workflow to validate mappings. The tool is the easy part. Say who owns data quality for each object, how you clean before loading, how many trial loads you run, and who signs off.

Technical questions (ABAP and support)

11. What is code pushdown?

Testing: modern ABAP thinking. It means moving data-heavy calculations to the database layer instead of pulling rows into the application server. Example: compute a total with an aggregate function in the database rather than looping over every line item in ABAP.

12. A transport failed to import. What do you check?

Testing: support instinct. Read the return code first: 4 means imported with warnings, 8 means errors such as syntax or activation problems, 12 means the import was cancelled, for example because an object was missing. Then check the import sequence and whether the request contains every object it depends on. Related: a logical unit of work (LUW) is a set of database changes that either all commit or all roll back.

13. A user says they cannot post an invoice. Walk me through it.

Testing: troubleshooting order. Reproduce it with the user's data and read the full error. Then check, in order: master data (is the supplier blocked, is the tax code valid?), configuration, whether the posting period is open, and authorisations. Then record the cause in the ticket. The order matters more than any single tool.

Interviewing at SAP the company

One third-party guide describes SAP India's process as an online assessment, a technical interview, a managerial interview and an HR interview, with extra technical rounds for senior roles. Treat it as a rough outline.

A one-week preparation plan

• Days 1–2: Draw procure-to-pay (or order-to-cash, if you are in SD) on one page, with the postings at each step.
• Days 3–4: Prepare three true project stories: a defect you fixed, a requirement you challenged, and a data or migration problem. Know the transaction codes and Fiori apps you actually used; expect to be asked.
• Days 5–6: Read up on questions 7–9, even if your projects were on the older ERP.
• Day 7: Answer all 13 out loud, timed.

For SAP support roles, our application support interview questions guide covers tickets and escalation. Interviewing with a consulting firm? See the Accenture managerial round guide, and for the first call, HR screening questions.

To rehearse, Verve AI's Mock Interview has an AI recruiter ask you questions one at a time, and afterwards you get a performance report with feedback and scoring.

Sources

• SAP Business Suite 7 / SAP ERP 6.0 maintenance to end of 2027 (extended to 2030) and S/4HANA commitment to 2040: https://news.sap.com/2020/02/sap-s4hana-maintenance-2040-clarity-choice-sap-business-suite-7/
• Purchasing process postings: GR/IR clearing account, invoice posted with reference to the PO, the 300/320 example, price differences, MM automatic account determination and transaction keys: https://learning.sap.com/courses/project-financials-control-in-sap-s-4hana/performing-the-purchasing-process
• Posting keys (21/31, 40/50) and what they control: https://learning.sap.com/courses/customizing-core-settings-in-financial-accounting-in-sap-s4hana/configuring-the-header-and-line-items-of-financial-accounting-fi-documents
• Universal journal (ACDOCA) as single source of truth, simplified data model, in-memory database: https://learning.sap.com/courses/customizing-core-settings-in-financial-accounting-in-sap-s4hana/getting-an-overview-of-sap-s-4hana-1
• Business partner as single point of entry, transaction BP, CVI: https://learning.sap.com/courses/customizing-core-settings-in-financial-accounting-in-sap-s4hana/managing-business-partners
• SAP S/4HANA project course lesson "Steps to Business Partner and Customer Vendor Integration (CVI)": https://learning.sap.com/courses/guide-your-sap-s-4hana-project-to-success/steps-to-business-partner-and-customer-vendor-integration-cvi-_LE_046abcaa-b7a4-49fe-af57-c5cfda8ba2de
• S/4HANA runs only on HANA; new implementation, system conversion and selective data transition: https://en.wikipedia.org/wiki/SAP_S/4HANA
• Traditional five implementation phases (Business Blueprint, Realization) and SAP Activate: https://en.wikipedia.org/wiki/SAP_ERP
• Fit-to-standard workshops in the Explore phase, standard processes demonstrated in a starter system, changes limited to critical requirements: https://learning.sap.com/courses/implementing-sap-s-4hana-cloud-public-edition/providing-an-overview-of-the-fit-to-standard-analysis-process_aa2f7030-617a-4679-997f-c937f8a8cc03
• Clean core facilitates smooth system upgrades: https://learning.sap.com/courses/sap-s-4hana-cloud-private-edition-sourcing-and-procurement/exploring-why-a-clean-core-is-necessary_b0e7532d-7ced-4643-98d8-a3e36961e891
• Migration Cockpit: staging tables, direct transfer over RFC, guided validation: https://learning.sap.com/courses/implementing-sap-s-4hana-cloud-public-edition/introducing-the-sap-s-4hana-migration-cockpit_ca4ff972-d855-448b-a69a-42b2501d6ea7
• Payment run stages, code pushdown, transport return codes, LUW, SAP India interview rounds (third-party guide): https://www.interviewbit.com/sap-interview-questions/
• Verve AI Mock Interview (AI recruiter, performance report with feedback and scoring): https://docs.vervecopilot.com/features/mock-interview