SAP SAC INTERVIEW QUESTIONS

AND ANSWERS

How to secure data security while connect the SAP

HANA /BW to SAP SAC ?
To secure data when connecting SAP HANA to SAP Analytics Cloud (SAC), ensure
secure communication using TLS/SSL (HTTPS), implement strong authentication
methods like SAML or SSO, and leverage role-based access control for data
models within SAC.
Here's a more detailed breakdown of security measures:
1. Secure Communication:
 TLS/SSL for Encrypted Communication:
Use Transport Layer Security (TLS)/Secure Sockets Layer (SSL) to encrypt
data transmitted between SAP HANA and SAP Analytics Cloud. This ensures
that even if intercepted, the data remains unreadable.
 HTTPS Protocol:
Ensure all communications use the HTTPS protocol, which is the secure
version of HTTP.
 SSL/TLS Certificates:
Utilize valid SSL certificates to authenticate the identity of the SAP HANA
server and establish a secure connection.
2. Authentication and Authorization:
 Strong Authentication Methods:
Implement robust authentication mechanisms like Single Sign-On (SSO) or
SAML (Security Assertion Markup Language) for user access to SAP HANA
data within SAC.
 User Roles and Permissions:
Assign users appropriate roles and permissions within SAC to control access
to specific data models and views.
 Data Access Control:
Leverage data access control features in SAC to restrict access to sensitive
data based on user roles and organizational needs.
3. Data Security within SAP HANA:
 Encryption:
Enable encryption on data and log volumes within SAP HANA to protect data
at rest.
 Secure Stores:
Utilize SAP HANA's secure stores for storing and managing encryption keys.
 Data Storage Security:
 Implement appropriate file permissions and security configurations for the
operating system where SAP HANA is installed.
 External Key Management Service (KMS):
If required, use the SAP Data Custodian Key Management Service (KMS) to
manage your own encryption keys.
4. SAP Analytics Cloud Security:
 Model Data Privacy:
Enable model data privacy in SAC to control who can view and access
specific data models.
 Role-Based Security:
Assign users appropriate roles and permissions within SAC to control access
to data models and stories.
 Audit Logs:
Enable audit logging in SAC to track user activity and identify potential
security breaches.
5. Connectivity and Tunnel Connections:
 Direct Connections:
Utilize direct connections between SAC and SAP HANA for faster performance
and efficiency.
 Tunnel Connections:
If necessary, use tunnel connections to access data from SAP HANA on-
premise, while maintaining security.
 CORS:
Consider using Cross-Origin Resource Sharing (CORS) for secure connections
between SAC, the Identity Provider (IdP), and backend data sources.
6. Cloud Connector Security:
 Hard-Drive Encryption:
Use hard-drive encryption for the machine running the Cloud Connector to
protect configuration data.

What is use case of Regression in SAP SAC ?

SAP Analytics Cloud (SAC), a regression use case involves predicting a
numerical value (the target variable) based on the relationship with other
variables, for example, predicting sales based on advertising spend and
seasonality.
Here's a more detailed breakdown:
 What is Regression in SAC?
 Regression is a statistical method used to model the
relationship between a dependent variable (the target) and
one or more independent variables (predictors).
  In SAC, it's used within the "Smart Predict" feature to generate
predictive models.
 The goal is to predict a continuous numerical value.
 How it Works
 You select a predictive scenario (regression) and choose a
data source.
 You identify the target variable (the value you want to predict)
and the influencer variables (the variables that might
influence the target).
 SAC uses machine learning algorithms to train a model on
historical data and then uses that model to make predictions.
 Example Use Cases
 Predicting Sales: Forecasting future sales based on factors like
advertising spend, seasonality, economic indicators, and
previous sales data.
 Predicting Production Levels: Estimating the production output
of a factory based on factors like machine capacity, raw
material availability, and labor hours.
 Predicting Customer Churn: Determining which customers are
likely to churn based on factors like demographics, purchase
history, and engagement metrics.
 Predicting Insurance Costs: Estimating the cost of a
customer's health insurance based on factors like age, BMI,
smoking status, and medical history.
 Steps in SAC
o Create a predictive scenario.
o Choose "Regression" as the scenario type.
o Name the scenario.
o Select a data source.
o Select the target variable and influencer variables.
o Train the model.
o Use the model to make predictions.

Data isn't loading in SAP SAC in first time how can you
identify it ?
If data isn't loading initially in SAP Analytics Cloud (SAC), try refreshing
your browser cache, ensuring the "Optimize Story Building Performance"
option is enabled, and using relevant filters to limit the number of
records.
Here's a more detailed breakdown of troubleshooting steps:
1. Basic Checks & Refresh:
Restart Browser/System:
Sometimes, browser cache or system issues can cause
problems. Restarting your browser or even your entire system might
resolve the issue.
Refresh Browser Cache:
Clear your browser's cache and cookies, as they can sometimes interfere
with data loading.
Check SAC Version:
Ensure you are using the latest version of SAP Analytics Cloud, as
updates often include performance improvements and bug fixes.
Check System Requirements:
Make sure your system meets the minimum requirements for SAP
Analytics Cloud.
2. Optimize Story Building Performance:
Enable Optimization:
In the Model Preferences under "Data and Performance", check if the
"Optimize Story Building Performance" option is enabled.
Show Unbooked Data:
When possible, choose to show unbooked data in a chart, as this can
reduce the time SAC spends differentiating between booked and
unbooked data.
Avoid Exception Aggregations:
Instead of using Exception Aggregations in the Model, use Restricted
measures or Calculation functionality in stories.

There is a program being used in 2 business user use

same data in sac is it visible to 2 user or more in case of
live connection as well ?
Yes, when multiple business users in SAP Analytics Cloud (SAC) use the
same data, it's generally visible to them, and the system handles potential
conflicts through versioning and collaboration features, not through a
"love connection" scenario.
Here's a more detailed explanation:
 Visibility:
If users are working with the same data model or story, they will typically
see the same data and the same content.
 Version Management:
When a user makes changes to a public version, the version goes into
"Edit Mode," creating a private version that only the user can see until the
changes are published.
 Overwriting Changes:
If multiple users are editing the same version, the user who publishes
their changes later will overwrite any other published data, but not the
private versions of other users.
 Collaboration:
SAC provides features for collaboration, such as discussions and
comments on specific pages or widgets within a story, allowing users to
work together on the same data.
 Data Access Control:
You can also manage data access control in dimensions, providing read
and write access to teams or users in secured dimensions.
 Live Data Connection:
SAC allows for live connections to data sources, meaning users can work
with real-time data without needing to import or replicate it.
 Import Data Connections:
SAC also supports import data connections, where data is imported into
SAC and changes in the source system don't affect the imported data.

How to resolve unnecessary data issue in SAP SAC ?

To address unnecessary data issues in SAP Analytics Cloud (SAC), focus on
optimizing your models, stories, and data actions. This includes filtering
dimensions and measures, simplifying calculations, reducing the number
of widgets on a page, and utilizing caching and performance analyzer
tools.
Here's a more detailed breakdown:
1. Model Optimization:
 Reduce Calculation Scope:
Minimize the number of calculations and the complexity of formulas used
in your data actions and models.
 Remove Unnecessary Dimensions and Measures:
Carefully review your model and remove any dimensions or measures that
are not actively used.
 Optimize Planning Models:
Consider using planning areas to organize your planning data and improve
performance.
 Data Action Optimization:
 Check Calculation Scope: Hover over a supported function to
check the scope.
 Reduce FOREACH Loops: Minimize the use of FOREACH
functions, as they repeat calculations for each member.
 Remove Unnecessary IF Statements: Complex scripts with
many IF statements can slow down performance.
 Avoid "= NULL" Comparison: This can slow down data actions
as the script needs to check each member.
 Reduce the Number of DATA Functions: Using a lot of DATA
functions can also cause slow performance.
 Model Design:
Reconsider model design choices to make versions smaller.
2. Story Optimization:
 Filter Dimensions and Measures: Ensure your stories only include the
necessary dimensions and measures, reducing the data being
processed and displayed.
 Optimize Widgets: Limit the number of widgets (charts, tables, etc.)
on a single page to avoid performance strain.
 Utilize Caching: Enable story or model caching wherever possible to
reduce query execution times.
 Performance Analyzer: Use the Performance Analyzer tool in SAC
(accessible via Developer Tools) to identify and resolve bottlenecks.
  Use Fewer Pages: Reduce the number of pages in your story to
improve loading times.
 Manage Process-Heavy Widgets: Be mindful of the number of
process-heavy widgets on a page.
 Collapse Page Filters and Input Controls: Collapse filters and input
controls to reduce the amount of data loaded.
 Manually Set Top N: Manually set the Top N value for charts and
tables to limit the amount of data displayed.
 Keep Images Small: Use small images to reduce the size of your
story.

What are techniques to optimize SAC in large data like

25 lakh data?
To optimize SAP Analytics Cloud (SAC) performance with large datasets
like 25 lakh records, focus on data model design, story optimization, and
data action efficiency, including filtering data, limiting widgets, and
optimizing advanced formulas.
Here's a breakdown of key optimization techniques:
1. Data Model Optimization:
 Filter Dimensions and Measures:
Ensure your story includes only the necessary dimensions and
measures to reduce the amount of data being processed and
displayed.
 Data Source Optimization:
If using BW/4HANA, optimize BW queries by filtering out
unnecessary columns and simplifying composite providers and
calculation views.
 Unbooked Data:
Disable "Show Unbooked Data" unless explicitly needed, as this can
impact performance, especially with large datasets.
 Data Actions:
Optimize data actions by running them on the minimum required
dataset and copying filtered data to private versions.
 Data Locking:
Use data locking to control access and prevent unnecessary data
manipulation, especially in planning models.
2. Story Optimization:
 Limit Widgets: Reduce the number of widgets (charts, tables, etc.)
on a single page to minimize performance strain. Distribute widgets
across multiple pages if needed.
 Performance Analyzer: Utilize the Performance Analyzer tool in
SAC (accessible via Developer Tools) to identify and resolve
bottlenecks in your stories.
 Caching: Enable story or model caching wherever
possible. Precomputed data reduces query execution times.
 Story Filters: Use story/page filters to allow users to minimize the
amount of data loaded by filtering.
 Use Fewer Pages: Reduce the number of pages in your story to
improve loading time.
 Manage Process-Heavy Widgets: Optimize pages with many
process-heavy widgets.
 Collapse Filters and Input Controls: Collapse filters and input
controls to reduce the visual clutter and improve performance.
 Manually Set Top N: Manually set Top N for charts to reduce the
amount of data displayed.
 Keep Images Small: Reduce the size of images to decrease
download times.
 Chart Optimizations: Avoid charts with a large number of data
points (>500). Leverage Explorer instead of using large tables.