Phase 0 — Foundations
🎯 In plain words
❓ Why it matters
You can't configure or read a posting if you don't know how SAP is structured or what a debit and a credit mean. Skip this and later phases feel like magic spells you memorise; learn it and they become obvious. This is the cheapest hour you'll ever spend — it pays back in every other phase.
🧠 Key concepts you must know
1. ERP = one system for the whole business
ERP (Enterprise Resource Planning) means one shared system for buying, making, selling, and accounting — instead of separate disconnected tools. When you receive goods, the stock figure and the accounts update in the same breath. SAP is the market-leading ERP; MM (Materials Management) is the part that handles purchasing and inventory.
2. S/4HANA vs ECC — what changed
ECC is the older SAP; S/4HANA is the modern one you're learning. The big shifts:
- Universal Journal (ACDOCA) — one single table holds all financial line items (no more separate FI/CO tables).
- Material Ledger is now mandatory (it tracks material value, multi-currency).
- Business Partner replaces the old separate vendor/customer masters — one object plays both roles.
- Fiori — modern web apps and tiles sit on top of the classic screens.
3. Getting around the system
- Two front ends: the classic SAP GUI and the web-based Fiori launchpad.
- T-codes (transaction codes) jump straight to a screen — type them in the command box.
- /n = open the T-code in the same window; /o = open it in a new window.
- You can run multiple sessions (windows) at once to compare screens side by side.
4. The system landscape
Changes flow through three systems: DEV → QAS → PRD (Development → Quality Assurance → Production). You build and test config in DEV, it's packed into a transport, then imported into QAS to test, and finally PRD where the real business works. You never change config directly in PRD.
5. The accounting you actually need
- Debit and credit — the two sides of every entry. Think of a T-account: debits on the left, credits on the right.
- The document must balance — total debits must equal total credits, always. If they don't, SAP won't post it.
🛠️ Do it now — practise alongside
Don't just read — open these and click around so the words turn into a real system:
SAP Basics Accounting 101 Learning Path mapLog into your IDES, try /n and /o, open a second session, and find the command box. Then sketch one debit/credit T-account on paper.
🔗 Connects to
- Phase 1 — Enterprise Structure: the org "skeleton" you'll build sits on top of these basics.
- Phase 8 — Valuation & OBYC: reading how stock postings hit the accounts needs the debit/credit you learn here.
- Accounting 101: the deeper dive on debits, credits, and T-accounts.
🎓 Cert focus & quick recall
C_TS452 area ① (Business Processes & system fundamentals). Expect light questions on S/4HANA differences and navigation; the accounting pays off across every other area.
Name three key differences between ECC and S/4HANA.
Universal Journal (single ACDOCA table) instead of separate FI/CO tables; Material Ledger is mandatory; Business Partner replaces separate vendor/customer masters; plus Fiori as the modern UI.
What is a T-code, and what's the difference between /n and /o?
A transaction code jumps straight to a screen. /n opens it in the same window; /o opens it in a new window (session).
What does "the document must balance" mean?
Total debits must equal total credits in every accounting document — if they don't, SAP refuses to post it.
What are DEV, QAS and PRD?
The three-system landscape: Development (build/test config), Quality Assurance (test imports), Production (the live business). Config moves between them via transports.
✅ You're ready to move on when…
- You can say in one sentence what ERP is and where MM fits.
- You can navigate with T-codes and explain /n vs /o and the DEV→QAS→PRD flow.
- You can read a simple debit/credit entry and know why it must balance.