cancel
Showing results for 
Search instead for 
Did you mean: 

Redunancy between S4 and SAC

eupdike
Explorer

Team,

Was wondering if anyone has come across this and how they resolved it. Currently we are using SAC for month end reports and our compliance team wants a backup process to be established in case SAC is down during month end. Due to limitations within Query browser of displaying 10,000 rows, has anyone else come up with a process that would allow the business to regenerate reports if they couldn't access SAC?

Accepted Solutions (0)

Answers (1)

Answers (1)

DebjitSingha
Active Contributor
0 Kudos

Hello eupdike,

SAP Analytics Cloud comes with high availability and a SLA of >99.5% per month.

SLA Update for SAP Analytics Cloud

Chances of SAC going down outside of preannounced release schedule is very slim. In case SAP does not fulfill the committed availability customers may claim a credit as well. Service Level Agreement for SAP Cloud Services.

Still if you want to create redundancy with your month end reporting process - one way would be create direct Fiori or Analysis For Microsoft Office (Standard) report on top of S4 views. This way end users will have two form of reporting options.

Coming back to your +10K rows statement - Seems like your are better off using Excel based reports than SAC stories/apps. You can change the table behavior in SAC to show more rows. (More here - Q&A : How to Row Limitation in SAC ). As you have SAC license already, one option (no added cost) would be to use AO (SAC) or Excel add-in for SAC on top of SAC models. +10K rows will be easily consumes via an excel based add-in.

Other option would be to use AO (Standard) to connect directly to S4. This option would required BusinessObjects license agreement. Most customers have AO in their landscape. Hence AO (Standard) would be better choice over SAC add-in. Beside standard version can connect to S4 directly (to address your back up plan) and AO (SAC) dont.

Note: Cloud services usually show same behavior when it comes to same hyperscale. Say your S4 system is on same AWS geo region as your SAC (SaaS) tenant. In case one is encountering network outage, other will be impacted as well. This defeat the purpose of creating redundancy completely. Unless your have S4 hosted on private cloud or on-premise.

Viewers/ readers - If you find above information helpful, feel free to up-vote (arrows on left side).

-Debjit