ABAP Cloud Entwickler werden: Der komplette Lernpfad 2025

┌─────────────────────────────────────────────────────────┐
│ Monat 1-2: Grundlagen festigen                          │
├─────────────────────────────────────────────────────────┤
│ - OOP ABAP vertiefen                                    │
│ - Eclipse ADT meistern                                  │
│ - CDS Views & Annotationen                              │
│ - ABAP Unit Testing                                     │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Monat 3-4: RAP Core                                     │
├─────────────────────────────────────────────────────────┤
│ - RAP Managed Scenario                                  │
│ - Behavior Definitions (BDEF)                           │
│ - EML (Entity Manipulation Language)                    │
│ - Determinations & Validations                          │
│ - Actions                                               │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Monat 5: Integration & UI                               │
├─────────────────────────────────────────────────────────┤
│ - OData V4 Services                                     │
│ - Fiori Elements Basics                                 │
│ - Service Bindings                                      │
│ - UI Annotationen                                       │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Monat 6: Praxis & Zertifizierung                        │
├─────────────────────────────────────────────────────────┤
│ - Eigenes RAP-Projekt (siehe unten)                     │
│ - SAP Learning Hub (optional)                           │
│ - Community-Beiträge (Blog, GitHub)                     │
│ - SAP Zertifizierung (optional)                         │
└─────────────────────────────────────────────────────────┘

" Klassen & Interfaces verstehen
INTERFACE zif_calculator.
  METHODS add IMPORTING iv_a TYPE i iv_b TYPE i RETURNING VALUE(rv_result) TYPE i.
ENDINTERFACE.

CLASS zcl_calculator DEFINITION PUBLIC FINAL CREATE PUBLIC.
  PUBLIC SECTION.
    INTERFACES zif_calculator.
ENDCLASS.

CLASS zcl_calculator IMPLEMENTATION.
  METHOD zif_calculator~add.
    rv_result = iv_a + iv_b.
  ENDMETHOD.
ENDCLASS.

" Vererbung
CLASS zcl_base DEFINITION ABSTRACT.
  PUBLIC SECTION.
    METHODS process ABSTRACT.
ENDCLASS.

CLASS zcl_child DEFINITION INHERITING FROM zcl_base.
  PUBLIC SECTION.
    METHODS process REDEFINITION.
ENDCLASS.

" Polymorphismus
DATA(lo_calc) = CAST zif_calculator( NEW zcl_calculator( ) ).
DATA(lv_result) = lo_calc->add( iv_a = 5 iv_b = 3 ).

Ctrl+Space       Auto-Completion
Ctrl+1           Quick Fix
F3               Navigate to Definition
Ctrl+Shift+G     Find References
Ctrl+Shift+F     Format Code
Ctrl+/           Comment/Uncomment
F8               Activate
Ctrl+F11         Run

-- Interface View (I_*): Datenmodell
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Customer - Interface View'

define view entity ZI_Customer
  as select from kna1
  association [0..*] to ZI_SalesOrder as _SalesOrders
    on $projection.CustomerId = _SalesOrders.SoldToParty
{
  key kunnr as CustomerId,
      name1 as CustomerName,
      ort01 as CityName,
      land1 as Country,

      @Semantics.user.createdBy: true
      ernam as CreatedBy,

      @Semantics.systemDateTime.createdAt: true
      erdat as CreatedOn,

      // Association
      _SalesOrders
}

-- Consumption View (C_*): UI-spezifisch
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Customer - Consumption View'
@Metadata.allowExtensions: true

@UI: {
  headerInfo: {
    typeName: 'Customer',
    typeNamePlural: 'Customers',
    title: { value: 'CustomerName' }
  }
}

define view entity ZC_Customer
  as projection on ZI_Customer
{
      @UI.facet: [{ position: 10, type: #IDENTIFICATION_REFERENCE }]

  key @UI.lineItem: [{ position: 10 }]
      @UI.identification: [{ position: 10 }]
      CustomerId,

      @UI.lineItem: [{ position: 20 }]
      @UI.identification: [{ position: 20 }]
      CustomerName,

      @UI.lineItem: [{ position: 30 }]
      CityName,

      @UI.lineItem: [{ position: 40 }]
      Country,

      _SalesOrders : redirected to composition child ZC_SalesOrder
}

CLASS ltc_calculator DEFINITION FINAL FOR TESTING
  DURATION SHORT RISK LEVEL HARMLESS.

  PRIVATE SECTION.
    DATA mo_cut TYPE REF TO zcl_calculator.  " CUT = Class Under Test

    METHODS:
      setup,
      teardown,
      test_add_positive FOR TESTING,
      test_add_negative FOR TESTING,
      test_add_zero FOR TESTING.
ENDCLASS.

CLASS ltc_calculator IMPLEMENTATION.

  METHOD setup.
    CREATE OBJECT mo_cut.
  ENDMETHOD.

  METHOD test_add_positive.
    " Arrange
    DATA(lv_a) = 5.
    DATA(lv_b) = 3.

    " Act
    DATA(lv_result) = mo_cut->add( iv_a = lv_a iv_b = lv_b ).

    " Assert
    cl_abap_unit_assert=>assert_equals(
      exp = 8
      act = lv_result
      msg = '5 + 3 should equal 8'
    ).
  ENDMETHOD.

  METHOD test_add_negative.
    DATA(lv_result) = mo_cut->add( iv_a = -5 iv_b = 3 ).
    cl_abap_unit_assert=>assert_equals( exp = -2 act = lv_result ).
  ENDMETHOD.

  METHOD test_add_zero.
    DATA(lv_result) = mo_cut->add( iv_a = 0 iv_b = 0 ).
    cl_abap_unit_assert=>assert_equals( exp = 0 act = lv_result ).
  ENDMETHOD.

  METHOD teardown.
    CLEAR mo_cut.
  ENDMETHOD.

ENDCLASS.

┌────────────────────────────────────────┐
│         Fiori UI (Browser)             │
└───────────────┬────────────────────────┘
                │
                ▼ OData V4
┌────────────────────────────────────────┐
│       Service Binding                  │
│       (ZUI_TRAVEL_O4)                  │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│       Service Definition               │
│       expose ZC_Travel as Travel       │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│    Projection Layer (C_*)              │
│    ZC_Travel (Consumption View)        │
│    + Projection Behavior               │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│    Business Object Layer (I_*)         │
│    ZI_Travel (Interface View)          │
│    + Behavior Definition (BDEF)        │
│    + Behavior Implementation (ABAP)    │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│         Database (ZTRAVEL)             │
└────────────────────────────────────────┘

" READ
READ ENTITIES OF zi_travel
  ENTITY Travel ALL FIELDS WITH VALUE #( ( TravelId = '00001' ) )
  RESULT DATA(lt_travel).

" CREATE
MODIFY ENTITIES OF zi_travel
  ENTITY Travel CREATE FIELDS ( AgencyId CustomerId )
  WITH VALUE #( ( %cid = 'CID_1' AgencyId = '001' CustomerId = '042' ) )
  MAPPED DATA(mapped).

COMMIT ENTITIES.

" UPDATE
MODIFY ENTITIES OF zi_travel
  ENTITY Travel UPDATE FIELDS ( Status )
  WITH VALUE #( ( TravelId = '00001' Status = 'A' ) ).

COMMIT ENTITIES.

" DELETE
MODIFY ENTITIES OF zi_travel
  ENTITY Travel DELETE FROM VALUE #( ( TravelId = '00001' ) ).

COMMIT ENTITIES.

-- Service Definition
@EndUserText.label: 'Travel Service'
define service ZUI_TRAVEL_O4 {
  expose ZC_Travel as Travel;
  expose ZC_Booking as Booking;
}

Service Binding:
1. Eclipse ADT → New → Service Binding
2. Binding Type: OData V4 - UI
3. Service Definition: ZUI_TRAVEL_O4
4. Publish
5. Preview → Fiori Elements App öffnet

@UI: {
  headerInfo: {
    typeName: 'Travel',
    typeNamePlural: 'Travels',
    title: { value: 'Description' },
    description: { value: 'TravelId' }
  }
}
define view entity ZC_Travel
  as projection on ZI_Travel
{
      // Facets (Tabs auf Object Page)
      @UI.facet: [
        { position: 10, type: #IDENTIFICATION_REFERENCE, label: 'General' },
        { position: 20, type: #LINEITEM_REFERENCE, label: 'Bookings', targetElement: '_Bookings' }
      ]

      // List Report Columns
  key @UI.lineItem: [{ position: 10 }]
      @UI.identification: [{ position: 10 }]
      @UI.selectionField: [{ position: 10 }]
      TravelId,

      @UI.lineItem: [{ position: 20 }]
      @UI.identification: [{ position: 20 }]
      AgencyId,

      // Action Buttons
      @UI.lineItem: [
        { type: #FOR_ACTION, dataAction: 'acceptTravel', label: 'Accept' },
        { type: #FOR_ACTION, dataAction: 'rejectTravel', label: 'Reject' }
      ]
      Status
}

Datenmodell:
- Equipment (ID, Name, Type, Status, PurchaseDate, Cost)
- Maintenance (ID, EquipmentId, MaintenanceDate, Cost, Notes)

Features:
- CRUD für Equipment & Maintenance
- Validation: MaintenanceDate nicht in Zukunft
- Determination: Auto-Status basierend auf letzter Wartung
- Actions: markAsDefect, markAsRepaired
- UI: Fiori Elements (List Report + Object Page)

Datenmodell:
- Employee (ID, Name, Department, VacationDays)
- LeaveRequest (ID, EmployeeId, StartDate, EndDate, Type, Status, Approver)

Features:
- CRUD für LeaveRequest
- Validations:
  - EndDate nach StartDate
  - Genug Urlaubstage verfügbar
  - Keine Überschneidungen mit anderen Requests
- Determinations:
  - Auto-calculate LeaveDays
  - Update Employee.VacationDays bei Approval
- Actions:
  - approve, reject, cancel
- Draft-enabled (Zwischenspeichern)
- Email-Benachrichtigung (via save_modified Hook)
- UI: Fiori Elements mit Custom Actions

Datenmodell:
- ExpenseReport (ID, EmployeeId, TripDate, TotalAmount, Status)
- ExpenseItem (ID, ReportId, Date, Category, Amount, Receipt)
- Approval (ID, ReportId, ApproverLevel, Approver, Status, Comments)

Features:
- Composition: Report → Items
- Multi-level Approval-Prozess
- Validations:
  - Receipts für Items > 100 EUR
  - Budget-Check gegen Kostenstelle
- Determinations:
  - Auto-calculate TotalAmount
  - Next Approver setzen
- Actions:
  - submit, approve, reject, requestChanges
- Business Events: ReportSubmitted, ReportApproved
- Integration: PDF-Generation (Receipt Upload)
- Custom Entity: Currency Conversion (via API)
- Authorization: Nur eigene Reports sehen (DCL)
- UI: Custom Fiori Elements (Freestyle für Receipt Upload)