Extending modern SAP Fiori apps is usually straightforward with extension points. But when working with classical Fiori apps built on libraries, things get tricky. These apps often lack Component.js and extension points, making reuse and customization painful. This blog shares how to extend such legacy apps by replacing fragments and views.
F0773
Stay SAP Sharp
Top Blog Posts
- Connecting SAP backend OData services to external systems using SAP BTP API Management
- Extension Projects in BAS: Handling Legacy SAP Fiori Apps
- Extending Legacy SAP Fiori Apps: A Case Study with Clear Incoming Payments (F0773)
- Dynamic Cross-App Navigation in Fiori Elements: Navigate to Different Apps from the Same Column
- Messages Handling in Purchase Order (ME21N/ME22N/ME23N) and Purchase Requisition (ME51N/ME52N/ME53N) Enhancements
- Simplifying SAP Access with Gen AI: Built on Copilot Studio, Integrated via SAP BTP & Azure APIM, Delivered in Teams & Copilot
- How to transport the extensions/enhancements created using Fiori App "Custom Fields and Logics"?
- Test OData Service using SAP Gateway Client
- Everything Fiori Notification
- Get Current System Time Stamp in CDS