on 10-18-2023 2:43 PM
Hi,
I have read multiple documents on how to keep the core clean for S/4HANA and BTP, but they're mostly related to the backend stack (OData, APIs, enhancements, etc.). All these documents mention some stuff about the UI part (e.g. available extension options), but they're not that detailed and lack the view from the architectual perspective.
I have a couple of questions related directly to SAP Fiori and how to keep the core of UI5 clean in BTP + S/4HANA architecture:
BR,
Adrian
Hi Adrian,
I think it might be not clear for you that when you do an extension project for a given standard app, you have to deploy it to the S/4 HaNA ABAP system!!! This deployment will create a new layer in the onprem layered repository of that app. Then you have to configure your tile to use this new layer.
With side-by-side extension you will create a brand new fiori app which will be deployed to BTP. Such an app can use however custom backend service(s) created via RAP or CAP model, or you can just simply use the existing standard S/4 HANA oData services.
Br
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
rpalotaiebc - but we have two options when it comes to extensibility:
- adaptation project (layering): here I understand you are forced to push it to S/4HANA system, which is clear,
- older component configuration extension (using app extension points): not all standard apps are possible to be extended with adaptation, so you have to develop an extension app.
Here I'm not sure where the extension app should be deployed.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.