SAPUI5 flexibility to adapt standard SAP apps

SAPUI5 is SAP’s strategic Web framework for Web applications such as SAP Fiori. In this context, SAPUI5 flexibility offers capabilities to adapt standard apps, not only for developers but also for key users and end users using simple WYSIWYG drag and drop tools. Learn about all the capabilities: SAPUI5 Flexibility – All You Need to Know. SAPUI5 flexibility provides features to realize a clean core approach with on-stack extensions: SAP standard apps remain untouched, no modifications are needed, and even predefined extension points are unnecessary.

SAPUI5 flexibility – Developer adaptation

Developers can leverage the concepts of SAPUI5 flexibility by using SAPUI5 adaptation projects in SAP Business Application Studio (BAS), the development environment of SAP Build Code. Those projects contain all code-based custom adaptations, created in the new Adaptation Editor and other code editors of BAS.

Picture: The new Adaptation Editor in SAP Business Application Studio

Extension project vs. Adaptation project

While adaptation projects are the strategic, advanced technology for code-based extensions of SAPUI5 apps, we also have the predecessor extension projects. To address frequent confusions, I want to summarize the differences to help understanding what you see in your system:

 Extension projectAdaptation projectSAP strategy  Legacy usageStrategic, advanced approach, leveraging SAPUI5 flexibility conceptsExtendonly legacy apps not (yet) compliant to SAPUI5 adaptation projects (1.)most apps, as given in SAP Fiori Apps Reference Library -> Implementation Information -> Extensibility via SAPUI5 Adaptation Projects. (2.)PrerequisitesIndividual, predefined extension points in each appGeneral enablement of app (1.)Supported applicationsFreestyle SAPUI5 apps onlyAny SAPUI5 app (freestyle SAPUI5 and SAP Fiori elements apps)Extension optionsLimited options (e.g. no extension of lifecycle methods)Increased options for all essential app artefactsExtension locationExtend in predefined extension points onlyExtend anywhere (3.) (unless blocked by application logic)Stability with upgradesLimited stabilityImproved stabilityFuture-proof conceptOne layer of changesMultiple layers possible (planned)Platform supportSAP S/4HANA on-prem onlyAny platform (4.)

Footnotes

Details on prerequisites for respective platforms in Extending SAP Fiori Applications.If an adaptation project is being created for an app not compliant to SAPUI5 adaptation projects, the wizard in SAP Business Application Studio automatically creates an extension project. (An example for such an app is My Inbox.)including existing extension points, controller hooksSee details in Features and Availability.

What does this mean for existing extension projects?

If you have an existing extension project, you can continue using it, i.e. running it and also maintaining it. In case a) you are planning to add new extensions due to bigger requirements and b) the underlying standard app supports SAPUI5 adaptation projects (see above), SAP recommends to manually migrate the extension project to an adaptation project to make use of its advanced options. (The UI5 team currently plans to provide guidance for this manual migration.)

Further references

Migrate from SAP Web IDE to SAP Business Application Studio: Blog post & MissionSAP Fiori Elements: Adaptation Project – Adding a Custom Filter to the List ReportAdaptation Project: Freestyle SAPUI5 App – Adding a Search Link to Items on a TableWork with SAPUI5 Adaptation Projects to extend SAP S/4HANA Cloud Public Edition 

 SAPUI5 flexibility to adapt standard SAP appsSAPUI5 is SAP’s strategic Web framework for Web applications such as SAP Fiori. In this context, SAPUI5 flexibility offers capabilities to adapt standard apps, not only for developers but also for key users and end users using simple WYSIWYG drag and drop tools. Learn about all the capabilities: SAPUI5 Flexibility – All You Need to Know. SAPUI5 flexibility provides features to realize a clean core approach with on-stack extensions: SAP standard apps remain untouched, no modifications are needed, and even predefined extension points are unnecessary.SAPUI5 flexibility – Developer adaptationDevelopers can leverage the concepts of SAPUI5 flexibility by using SAPUI5 adaptation projects in SAP Business Application Studio (BAS), the development environment of SAP Build Code. Those projects contain all code-based custom adaptations, created in the new Adaptation Editor and other code editors of BAS.Picture: The new Adaptation Editor in SAP Business Application StudioExtension project vs. Adaptation projectWhile adaptation projects are the strategic, advanced technology for code-based extensions of SAPUI5 apps, we also have the predecessor extension projects. To address frequent confusions, I want to summarize the differences to help understanding what you see in your system: Extension projectAdaptation projectSAP strategy  Legacy usageStrategic, advanced approach, leveraging SAPUI5 flexibility conceptsExtendonly legacy apps not (yet) compliant to SAPUI5 adaptation projects (1.)most apps, as given in SAP Fiori Apps Reference Library -> Implementation Information -> Extensibility via SAPUI5 Adaptation Projects. (2.)PrerequisitesIndividual, predefined extension points in each appGeneral enablement of app (1.)Supported applicationsFreestyle SAPUI5 apps onlyAny SAPUI5 app (freestyle SAPUI5 and SAP Fiori elements apps)Extension optionsLimited options (e.g. no extension of lifecycle methods)Increased options for all essential app artefactsExtension locationExtend in predefined extension points onlyExtend anywhere (3.) (unless blocked by application logic)Stability with upgradesLimited stabilityImproved stabilityFuture-proof conceptOne layer of changesMultiple layers possible (planned)Platform supportSAP S/4HANA on-prem onlyAny platform (4.)FootnotesDetails on prerequisites for respective platforms in Extending SAP Fiori Applications.If an adaptation project is being created for an app not compliant to SAPUI5 adaptation projects, the wizard in SAP Business Application Studio automatically creates an extension project. (An example for such an app is My Inbox.)including existing extension points, controller hooksSee details in Features and Availability.What does this mean for existing extension projects?If you have an existing extension project, you can continue using it, i.e. running it and also maintaining it. In case a) you are planning to add new extensions due to bigger requirements and b) the underlying standard app supports SAPUI5 adaptation projects (see above), SAP recommends to manually migrate the extension project to an adaptation project to make use of its advanced options. (The UI5 team currently plans to provide guidance for this manual migration.)Further referencesMigrate from SAP Web IDE to SAP Business Application Studio: Blog post & MissionSAP Fiori Elements: Adaptation Project – Adding a Custom Filter to the List ReportAdaptation Project: Freestyle SAPUI5 App – Adding a Search Link to Items on a TableWork with SAPUI5 Adaptation Projects to extend SAP S/4HANA Cloud Public Edition Read More Technology Blogs by SAP articles 

#SAPCHANNEL