Devenir developpeur ABAP Cloud : Le parcours d apprentissage complet 2025

┌─────────────────────────────────────────────────────────┐
│ Mois 1-2 : Consolider les bases                          │
├─────────────────────────────────────────────────────────┤
│ - Approfondir la POO ABAP                                │
│ - Maitriser Eclipse ADT                                  │
│ - Vues CDS et Annotations                                │
│ - Tests unitaires ABAP                                   │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Mois 3-4 : RAP Core                                      │
├─────────────────────────────────────────────────────────┤
│ - Scenario RAP Managed                                   │
│ - Behavior Definitions (BDEF)                            │
│ - EML (Entity Manipulation Language)                     │
│ - Determinations et Validations                          │
│ - Actions                                                │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Mois 5 : Integration et UI                               │
├─────────────────────────────────────────────────────────┤
│ - Services OData V4                                      │
│ - Bases Fiori Elements                                   │
│ - Service Bindings                                       │
│ - Annotations UI                                         │
└────────────┬────────────────────────────────────────────┘
             │
             ▼
┌─────────────────────────────────────────────────────────┐
│ Mois 6 : Pratique et Certification                       │
├─────────────────────────────────────────────────────────┤
│ - Projet RAP personnel (voir ci-dessous)                 │
│ - SAP Learning Hub (optionnel)                           │
│ - Contributions communautaires (Blog, GitHub)            │
│ - Certification SAP (optionnel)                          │
└─────────────────────────────────────────────────────────┘

" Comprendre les classes et interfaces
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.

" Heritage
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.

" Polymorphisme
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               Naviguer vers la definition
Ctrl+Shift+G     Trouver les references
Ctrl+Shift+F     Formater le code
Ctrl+/           Commenter/Decommenter
F8               Activer
Ctrl+F11         Executer

-- Interface View (I_*) : Modele de donnees
@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_*) : Specifique a l'UI
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Customer - Consumption View"
@Metadata.allowExtensions: true

@UI: {
  headerInfo: {
    typeName: 'Client',
    typeNamePlural: 'Clients',
    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 devrait etre egal a 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.

┌────────────────────────────────────────┐
│         UI Fiori (Navigateur)          │
└───────────────┬────────────────────────┘
                │
                ▼ OData V4
┌────────────────────────────────────────┐
│       Service Binding                  │
│       (ZUI_TRAVEL_O4)                  │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│       Service Definition               │
│       expose ZC_Travel as Travel       │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│    Couche Projection (C_*)             │
│    ZC_Travel (Consumption View)        │
│    + Projection Behavior               │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│    Couche Business Object (I_*)        │
│    ZI_Travel (Interface View)          │
│    + Behavior Definition (BDEF)        │
│    + Behavior Implementation (ABAP)    │
└───────────────┬────────────────────────┘
                │
                ▼
┌────────────────────────────────────────┐
│         Base de donnees (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 → L'application Fiori Elements s'ouvre

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

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

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

      // Boutons d'action
      @UI.lineItem: [
        { type: #FOR_ACTION, dataAction: 'acceptTravel', label: 'Accepter' },
        { type: #FOR_ACTION, dataAction: 'rejectTravel', label: 'Rejeter' }
      ]
      Status
}

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

Fonctionnalites :
- CRUD pour Equipment et Maintenance
- Validation : MaintenanceDate pas dans le futur
- Determination : Statut auto base sur la derniere maintenance
- Actions : markAsDefect, markAsRepaired
- UI : Fiori Elements (List Report + Object Page)

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

Fonctionnalites :
- CRUD pour LeaveRequest
- Validations :
  - EndDate apres StartDate
  - Assez de jours de conges disponibles
  - Pas de chevauchements avec d'autres demandes
- Determinations :
  - Calcul auto des LeaveDays
  - Mise a jour Employee.VacationDays a l'approbation
- Actions :
  - approve, reject, cancel
- Active Draft (sauvegarde intermediaire)
- Notification email (via hook save_modified)
- UI : Fiori Elements avec Actions custom

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

Fonctionnalites :
- Composition : Report → Items
- Processus d'approbation multi-niveaux
- Validations :
  - Justificatifs pour Items > 100 EUR
  - Verification budget contre centre de couts
- Determinations :
  - Calcul auto TotalAmount
  - Definir l'approbateur suivant
- Actions :
  - submit, approve, reject, requestChanges
- Business Events : ReportSubmitted, ReportApproved
- Integration : Generation PDF (Upload justificatifs)
- Custom Entity : Conversion de devises (via API)
- Autorisation : Voir uniquement ses propres rapports (DCL)
- UI : Fiori Elements custom (Freestyle pour upload justificatifs)