Skip to main content

Module 1 - Introduction to SAP & ABAP

This module lays the foundation of SAP and ABAP. Before writing any code, you must understand what SAP is, how SAP systems are structured, and where ABAP fits in the ecosystem.


1. What is SAP?

SAP stands for Systems, Applications, and Products in Data Processing.
It is an Enterprise Resource Planning (ERP) software used to manage end-to-end business processes.

What SAP Really Does

SAP integrates finance, logistics, HR, sales, and manufacturing into one unified system backed by a single source of truth (the database).

Key Characteristics of SAP

  • Integrated business processes
  • Centralized database
  • Real-time data processing
  • Highly configurable and extensible
  • Enterprise-grade security and scalability

Common SAP Modules

  • FI – Financial Accounting
  • CO – Controlling
  • MM – Materials Management
  • SD – Sales and Distribution
  • PP – Production Planning
  • HR/HCM – Human Resources
ABAP’s Role

ABAP is used to extend and customize SAP standard functionality when business requirements go beyond configuration.


2. SAP Application Architecture

SAP follows a multi-tier architecture, traditionally known as the 3-Tier Architecture.

2.1 Presentation Layer

  • SAP GUI
  • SAP Fiori / Web UI
  • User interaction only

2.2 Application Layer

  • ABAP Runtime Environment
  • Business logic execution
  • Work processes:
    • Dialog
    • Background
    • Update
    • Spool

2.3 Database Layer

  • Stores all business data
  • Examples:
    • SAP HANA
    • Oracle (legacy)
    • DB2 (legacy)

User → Presentation Layer → Application Layer → Database

Why Developers Must Understand This

Performance issues in ABAP often come from wrong interaction between application and database layers.


3. What is ABAP?

ABAP (Advanced Business Application Programming) is SAP’s proprietary programming language.

Why ABAP Exists

  • SAP data model is complex
  • Business logic must be consistent and secure
  • Database independence is required

ABAP is Used For

  • Reports (Classical, ALV)
  • Function Modules
  • Classes and Interfaces
  • Enhancements (BAdIs, User Exits)
  • OData & RAP services
Enterprise Nature of ABAP

ABAP is not just a language—it is tightly integrated with authorization, transport, database, and runtime management.


4. ABAP vs ABAP on HANA

SAP HANA changed how ABAP is written and optimized, not the language itself.

Classic ABAP (Pre-HANA)

  • Logic executed mostly on application server
  • Loop-heavy data processing
  • Basic Open SQL
  • Database-agnostic

ABAP on HANA

  • In-memory database
  • Code pushdown to database
  • Advanced SQL capabilities
  • CDS Views, AMDP, RAP
AspectClassic ABAPABAP on HANA
ProcessingApp ServerDB + App
SQL PowerLimitedAdvanced
PerformanceModerateHigh
New ConceptsFewCDS, AMDP, RAP
Important Clarification

ABAP syntax did not change with HANA — programming mindset did.


5. ABAP Workbench

The ABAP Workbench is the traditional development environment inside SAP GUI.

Key Transactions

TransactionPurpose
SE80Object Navigator
SE38ABAP Programs
SE24Class Builder
SE37Function Builder
SE11Data Dictionary

SE80 – Object Navigator

  • Central tool for development
  • Organizes objects using packages
  • Provides navigation across all ABAP artifacts
Real-World Usage

Even today, SE80 is heavily used for maintenance, debugging, and legacy systems.


6. Transport System Basics

SAP systems are landscape-based: Development → Quality → Production

6.1 What is a Transport?

A transport request is a container that moves changes between SAP systems.

6.2 Transport Types

  • Workbench Requests
    • ABAP programs
    • Classes
    • Dictionary objects
  • Customizing Requests
    • Configuration data

6.3 Transport Flow

  1. Develop in DEV
  2. Release transport
  3. Import to QA
  4. Import to PROD
Golden Rule

Never change code directly in Production.
All changes must go through transports.


7. Common Beginner Mistakes

Avoid These Early Mistakes
  • Treating ABAP like Java or Python
  • Ignoring SAP architecture
  • Writing SELECTs inside loops
  • Not understanding transport dependencies

8. Summary

  • SAP is an integrated ERP system
  • ABAP is SAP’s core backend language
  • SAP uses a 3-tier architecture
  • HANA changed performance strategies
  • ABAP Workbench is still relevant
  • Transports ensure controlled system changes

9. What’s Next?

➡️ Module 2: ABAP Development Environment

  • ADT (Eclipse)
  • Modern ABAP workflow
  • Debugging fundamentals
Learning Advice

A strong foundation here will save months of confusion in advanced topics like CDS, AMDP, and RAP.