OData service limitations

[deshmukh]

We want to create OData service to consume SAP Datasphere (DS) analytical model into tools like Power BI, Service Now etc. Are there any limitations when the analytical models are consumed in other tools using OData service vs SAC. I mean does the analytic model behave same in other tools vs SAC? What other points to consider when consuming analytical models using OData service.

[Savio_Dmello]

There are limitations.  
SAC and datasphere leverage same cloud analytical engine for query execution plan.
SAC is deeply integrated with SAP Datasphere and can leverage advanced features such as storyboards, smart insights, and predictive analytics that are natively supported.
Other tools like Power BI or ServiceNow may not fully support these advanced capabilities. The analytical model may lose certain functionalities or optimizations when accessed through an OData service.

Some complex calculated measures or restricted key figures that work seamlessly in SAC might not be fully supported or behave differently in other tools due to varying support for advanced calculation logic in these tools.

OData services can expose large datasets, but the performance can vary depending on the external tool’s ability to handle and optimize queries. SAC is optimized for querying and rendering data from SAP Datasphere. Other tools might face performance bottlenecks, especially with large datasets or complex queries.

SSO and row level security could also be a challenges when connected to their party front end tools. 

[deshmukh]

thanks a lot for the above valuable points

[Martin_Kuma]

Check this docu: https://help.sap.com/docs/SAP_DATASPHERE/43509d67b8b84e66a30851e832f66911/7a453609c8694b029493e7d87e...

There is a part for Analytic Models as well. 

I would say, there is no difference. SAC and OData will just consume the multidimensional model.