Swipe left or tap Next ▶ to turn the page.
Select any text to highlight it or add a note. Tap a diagram to enlarge it.
SAP Foundations: ERP, Modules, SAP GUI, Org Structure and Data Types
- ✔ Explain what ERP is and why companies move to SAP
- ✔ Name the main SAP modules (FI, CO, MM, SD, PP, HCM) and how they connect
- ✔ Log in and move around SAP GUI using transaction codes and command-field shortcuts
- ✔ Draw the SAP organisational structure and tell master, transaction and configuration data apart
Why companies need ERP
SAP interviews often open with "What is ERP?" A clear, simple answer shows the panel you understand the business problem before the software.
Picture Shakti Steels Ltd, with a factory in Pune and a depot in Chennai. Sales keeps orders in spreadsheets, stores keeps a stock register, and accounts retypes everything. Numbers do not match and nobody knows today's true stock. These separate islands of data are called silos.
What ERP means
ERP (Enterprise Resource Planning) is a single software system, with one shared database, that runs the core processes of a business: buying, making, storing, selling, paying people and keeping the accounts.
Sales books 20 tonnes of rods in its spreadsheet.
Stores does not see it and gives the rods to another customer.
The root cause: each team has its own copy of the data.
Answer: an ERP fixes this because all teams read and write the same order and stock records.
What SAP is
Interviewers expect you to expand the name, place SAP as a company and a product, and name its main product generations in the right order.
SAP is both a German software company and the name of its ERP products. The company was founded in 1972 by five former IBM employees and has its headquarters in Walldorf, Germany.
The name stands for Systeme, Anwendungen und Produkte in der Datenverarbeitung, which in English is Systems, Applications and Products in Data Processing. Say each letter: "S-A-P", not "sap" like tree juice.
The product generations
flowchart LR A[R/1<br/>early system] --> B[R/2<br/>mainframe] B --> C[R/3<br/>client-server] C --> D[ECC<br/>ERP Central Component] D --> E[S/4HANA<br/>runs only on HANA]
| Generation | Key idea |
|---|---|
| R/2 | Mainframe |
| R/3 | Client-server, three tiers |
| ECC | ERP core of SAP Business Suite; several databases |
| S/4HANA | Launched 2015; SAP HANA database only |
The "R" in R/3 stands for real-time: a posting is visible to everyone at once, not after an overnight batch.
Job posts mention both "ECC 6.0" and "S/4HANA", so know both names. Day 5 covers S/4HANA in detail.
You are given: S/4HANA, R/2, ECC, R/3.
Mainframe era comes first: R/2.
Client-server three-tier comes next: R/3.
ECC is the later name of the R/3-line ERP core.
Answer: R/2 → R/3 → ECC → S/4HANA.
Which SAP generation runs only on the SAP HANA database?
S/4HANA was built for the HANA in-memory database. ECC and R/3 could run on several databases.
The three-tier architecture
"Explain SAP's three-tier architecture" is a standard question for every track, functional or technical.
R/3 introduced a design with three layers, each doing one job.
The design scales well: when users grow, the company adds application servers without touching the database, and the user's PC only shows screens.
Inside an application server: dispatcher and work processes
Each application server has a dispatcher. It puts incoming user requests in a queue and hands each one to a free work process, which does the actual processing. Different kinds of work need different work process types:
| Work process | What it handles |
|---|---|
| Dialog | Online screen steps of users at their desks |
| Background | Scheduled jobs (SM36 to plan, SM37 to monitor) |
| Update | Writing changes to the database after Save |
| Enqueue | The lock table, so two users cannot change one record together |
| Spool | Print and output requests |
Ravi schedules a stock report to run at 2 a.m. with nobody watching.
Work that runs without a user at the screen is a scheduled job.
Answer: a background work process runs it.
The system landscape
Companies usually keep three separate SAP systems:
flowchart LR DEV[Development<br/>DEV] -->|transport| QAS[Quality / Test<br/>QAS] QAS -->|transport| PRD[Production<br/>PRD]
Changes are built in DEV, tested in QAS and moved to PRD using transport requests.
A user in Kolkata types an order and clicks Save.
The screen and the click belong to the presentation layer.
The check "is this material blocked?" runs on the application layer.
Writing the order row into a table happens in the database layer.
Answer: presentation → application → database, in that order.
Keep going with the full course
Day 1 has 22 pages. You have read the first 3.
See what's inside →