6 videos • 📅 2025-08-08 08:00:00 Asia/Singapore
Watch Video
2:30
2025-08-08 08:19:52
2:26:14
2025-08-08 13:05:14
21:21
2025-09-04 08:09:02
5:20:18
2025-09-04 10:36:01
23:09
2025-09-05 08:13:48
2:10:51
2025-09-05 13:50:47

Course recordings on DaDesktop for Training platform

Visit NobleProg websites for related course

Summary

Overview

This course session introduces extensibility options for standard SAP Fiori applications, focusing on two primary methods: extending OData services and modifying the UI via SAP Business Application Studio. The trainer outlines the process for identifying target applications, locating relevant OData services, and understanding support mechanisms. The session sets the foundation for hands-on practice in adapting Fiori apps, emphasizing practical workflows for adding fields via OData and UI-level customizations using adaptation projects.

Topic (Timeline)

1. Introduction to Fiori Extensibility Methods [00:01:16.690 - 00:04:26.460]

  • Two primary methods for extending standard SAP Fiori applications:
    1. Extending the underlying OData service to add new columns/fields.
    2. Modifying the UI using SAP Business Application Studio (or Visual Studio Code) and redeploying.
  • Goal of the session: Demonstrate both approaches, followed by practical exercises and exploration of additional apps.
  • Starting point: SAP Fiori Library to identify the target application for extension.
  • Extensibility defined: Modifications such as adding, removing, or hiding UI elements; changing text; or enhancing list views in standard Fiori apps.

2. Identifying Target Applications and Extensibility Pathways [00:04:26.460 - 00:08:23.370]

  • Example application: “Travel and Expenses” (My Travel and Expenses) used as a case study.
  • Two documented pathways for extensibility:
    1. OData-based extension (focus of initial demo).
    2. UI adaptation via SAP Business Application Studio (to be covered next).
  • Emphasis on using official SAP documentation and community resources to determine correct extensibility approach.
  • Initial step: Locate the OData service associated with the Fiori app via configuration settings.
  • Clarification: Configuration alone is insufficient; extensibility requires direct access to OData or UI adaptation tools.

3. OData Service Analysis and Application Context [00:08:23.370 - 00:14:03.460]

  • OData service must be identified first to determine extensibility feasibility.
  • If the OData service supports specific capabilities (e.g., add fields), extension can be automated with minimal effort.
  • Practical step: View the target Fiori application in the system to understand its structure and potential modification points.
  • Note: OData-based extension is optimal for adding new columns/fields, especially for in-house developers.
  • Limitation: Non-field additions (e.g., layout changes, new buttons) require SAP Business Application Studio.

4. Support and Component Identification for Fiori Apps [00:14:05.700 - 00:15:53.260]

  • Importance of knowing the exact SAP application component for raising support tickets.
  • If an issue arises, users can directly reference the Fiori app’s underlying component to expedite SAP support resolution.
  • Understanding the app’s architecture enables precise communication with SAP support teams.

5. Extensibility Tools and Method Selection [00:15:55.540 - 00:20:54.220]

  • SAP provides tutorials for Business Application Studio-based adaptations (to be reviewed later).
  • OData extension is the fastest method for field/column additions, provided the service supports it.
  • Critical check: Verify whether the OData service is active and accessible in the system.
  • Final step: Confirm visibility of the Fiori app UI and OData service response to ensure readiness for extension.
  • Session ends mid-demo, indicating transition to hands-on practice (implied but not fully captured in transcript).

Appendix

Key Principles

  • OData Extension: Use only for adding new fields/columns; requires the underlying service to expose extendable entities.
  • UI Adaptation: Required for layout, control, or behavior changes; must be done via SAP Business Application Studio.
  • Support Readiness: Always document the Fiori app’s technical component (e.g., from “Implementation Information”) for efficient SAP support.

Tools Used

  • SAP Fiori Library (for app discovery)
  • SAP Configuration (to locate OData service)
  • SAP Business Application Studio (for UI adaptation)
  • OData Service Browser (to validate service status)

Common Pitfalls

  • Assuming configuration changes alone enable extensibility (they do not).
  • Attempting UI changes via OData (not supported).
  • Failing to verify OData service activation before attempting extension.
  • Not identifying the correct application component for support requests.

Practice Suggestions

  • Identify a standard Fiori app in your system and locate its OData service via configuration.
  • Test if the service allows field addition (e.g., via $metadata).
  • Create a mock adaptation project in Business Application Studio for a UI element (e.g., hide a button).
  • Use SAP Help Portal to cross-reference extensibility guidelines for your target app.