SAP Fundamentals: ERP Landscape, Modules & Organization

SAP (Systems, Applications, and Products in Data Processing) is one of the world's leading ERP (Enterprise Resource Planning) vendors. An ERP system integrates core business processes — finance, procurement, sales, manufacturing, HR — into a single source of truth with shared master data and real-time reporting.

Instead of isolated spreadsheets and departmental databases, SAP connects transactions end-to-end. When a sales order ships, inventory updates automatically, a billing document is proposed, revenue posts to the general ledger, and management dashboards reflect the change — all from one integrated platform.

Key concepts for new employees:

• SAP instance / system — the running environment (development, quality, production).
• Client (mandant) — a logical partition within a system; data in client 100 is isolated from client 200. Production usually runs a single productive client.
• Transaction code (T-code) — a shortcut to a SAP program, e.g. FB03 (display document), ME21N (create purchase order).
• Customization vs configuration — configuration adapts standard SAP to your business (company codes, payment terms); customization involves code changes (ABAP) and carries higher maintenance cost.

SAP S/4HANA is the current-generation suite, built on the HANA in-memory database. It simplifies the data model (e.g. Universal Journal in Finance) and powers modern UX through Fiori apps.

SAP is organized into functional modules. Every employee interacts with at least one; integration architects connect them all.

Module	Full Name	Primary Purpose
FI	Financial Accounting	General ledger, accounts payable/receivable, asset accounting, financial statements
MM	Materials Management	Procurement, inventory, vendor master, goods movements
SD	Sales & Distribution	Customer master, quotations, sales orders, delivery, billing
HR / HCM	Human Capital Management	Personnel master, org management, payroll, time, talent

How they connect — a simplified example:

1. SD creates a sales order for 100 units.
2. MM checks stock; if insufficient, a purchase requisition may trigger procurement.
3. Delivery and goods issue reduce inventory (MM).
4. Billing generates an invoice (SD → FI).
5. Payment receipt clears the receivable (FI).

Other common modules include PP (Production Planning), PM (Plant Maintenance), QM (Quality Management), and CO (Controlling — cost centers, profitability analysis). In S/4HANA, some boundaries blur: Finance and Controlling merge into SAP S/4HANA Finance with the Universal Journal table ACDOCA.

Knowing which module owns which master data prevents "fixing" a problem in the wrong place — vendor issues belong in MM master data, not FI.

SAP ECC (ERP Central Component) ran for decades on traditional databases (Oracle, SQL Server, DB2). SAP S/4HANA is its successor — re-architected for HANA, with simplified tables, embedded analytics, and Fiori as the primary UX.

Aspect	ECC	S/4HANA
Database	Any DB	SAP HANA only
Finance	Separate FI + CO tables	Universal Journal (ACDOCA)
UX	SAP GUI (classic)	Fiori-first, GUI still available
Custom code	Full legacy ABAP	Requires remediation (simplification list)

Organizational structure defines who can do what and where:

Client (mandant)
 └── Company Code (legal entity — balance sheet, P&L)
      └── Plant (manufacturing / logistics site)
           └── Storage Location (warehouse bin level)

Additional org units include Sales Organization, Distribution Channel, Division (product lines), and Purchasing Organization. These combine into organizational structures assigned to transactions — a purchase order is always created for a company code and plant.

Example: Company code 1000 (US entity) may have plants 1001 (Chicago) and 1002 (Dallas). Posting a goods receipt to the wrong plant breaks inventory reports even if the vendor invoice is correct.

SAP Fiori is the modern user experience layer — responsive web apps with role-based launchpads instead of dense SAP GUI menus. Each tile opens a task-oriented app: "Approve Purchase Orders," "Manage Customer Line Items," "My Timesheet."

Fiori apps consume OData services backed by ABAP or S/4HANA APIs. The Fiori Launchpad groups apps by job role — a buyer sees MM apps; a controller sees FI apps.

Roles and authorizations control access:

• Role (PFCG) — a collection of transactions, apps, and authorizations assigned to users.
• Authorization object — e.g. F_BKPF_BUK (company code access for accounting documents).
• Field values — org-level restrictions: user may post only to company code 1000, plant 1001.

" Simplified: SU53 shows the last failed authorization check
" Transaction SU01 maintains user master records and role assignments

Segregation of Duties (SoD): Critical combinations (create vendor + pay vendor) are separated across roles to reduce fraud risk. GRC (Governance, Risk, and Compliance) tools analyze role assignments for SoD conflicts.

Practical tips for new users:

• If a transaction "does nothing" or shows empty, check authorization (SU53) and organizational assignment first.
• Fiori app catalogs differ from GUI T-codes — ask your basis team which entry point your role uses.
• Never share user credentials; audit logs (SM20, security audit log) track sensitive actions.