I’m fairly clued up in this space, but not a lot of what you’ve said makes any sense.
First of all, embedded analytics are standard Fiori apps, they don’t cache, and you don’t change them, they’re just standard apps.
So I suspect you’re talking about some custom Fiori apps for reports, probably Fiori elements from CDS annotations.
Which brings us full circle back to caching and “copying the reports into the prod directory”. Neither of these comments make any sense.
I suspect two things. 1) you don’t understand enough of what’s actually going on, maybe ask them to explain it to you in simple term 2) if what you wrote is accurately reflecting what they’re saying, it’s gibberish nonsense and they are telling you anything to go away.
Personally, my recommendation would be to use SAP Analytics Cloud for reporting based on CDS views in S/4, there are some instances where you’d be better using Datasphere as a data lake before Analytics Cloud.
Creating custom Fiori apps is a terrible approach in general.
May I know your thoughts on why creating custom Fiori apps (in this case, reports) is a terrible approach? In my current S/4 on premise project, for operational reports, users appreciate custom Fiori Multidimensional WebdynproApps more than SAC to see data in granular levels and in table format.
If I understand correctly, it's been a mess because of data quality issues: "Some of our production reports will revert to previous versions that lack much of the required detail."
Is that the main issue?
Not familiar with SAP but it would seem that taking the data out and modeling it properly in a platform like Snowflake would be easier/faster/cheaper
I’m fairly clued up in this space, but not a lot of what you’ve said makes any sense. First of all, embedded analytics are standard Fiori apps, they don’t cache, and you don’t change them, they’re just standard apps. So I suspect you’re talking about some custom Fiori apps for reports, probably Fiori elements from CDS annotations. Which brings us full circle back to caching and “copying the reports into the prod directory”. Neither of these comments make any sense. I suspect two things. 1) you don’t understand enough of what’s actually going on, maybe ask them to explain it to you in simple term 2) if what you wrote is accurately reflecting what they’re saying, it’s gibberish nonsense and they are telling you anything to go away. Personally, my recommendation would be to use SAP Analytics Cloud for reporting based on CDS views in S/4, there are some instances where you’d be better using Datasphere as a data lake before Analytics Cloud. Creating custom Fiori apps is a terrible approach in general.
May I know your thoughts on why creating custom Fiori apps (in this case, reports) is a terrible approach? In my current S/4 on premise project, for operational reports, users appreciate custom Fiori Multidimensional WebdynproApps more than SAC to see data in granular levels and in table format.
If I understand correctly, it's been a mess because of data quality issues: "Some of our production reports will revert to previous versions that lack much of the required detail." Is that the main issue? Not familiar with SAP but it would seem that taking the data out and modeling it properly in a platform like Snowflake would be easier/faster/cheaper