How to Get Started with Creating an Acquired Model in SAC to Be Consumed by Just Ask
In this post, we’ll dive into the steps for creating an refined Acquired Model and explore how it can really enhance your data analysis experience using just ask. While these best practices specifically apply to Acquired Models, we will go over soon in another post the best practices for working with Live Models on top of Datasphere.
Just ask is the new natural language query feature powered by AI. With just ask any user can query SAC data models by asking questions in everyday English. It supports SAP Analytics Cloud acquired data models and SAP Datasphere models.
Creating an Acquired Model in SAP Analytics Cloud (SAC) is a powerful way to represent and manage business data. Along with the just ask feature, which allows us to explore the model visually using natural language, this enhances our ability to analyze and interpret data effectively.
For individuals who are not yet familiar with just ask and require an introductory guide, one can follows the videos below as a helpful starting point:
How to Use Just AskHow to Enable and Manage Just Ask
or the following blog:
Initial Release of SAP Analytics Cloud Just Ask
In this post, we will explore the steps to create an Acquired Model and how it can enhance your data analysis experience.
For more in-depth information on Acquired Models, please visit our SAP Help Portal by clicking here:
Learn About ModelsCreate a Model from a Data Source
Using Acquired Models with Just Ask
Once you have created an Acquired Model in SAC, it can be consumed by just ask—a powerful AI feature in SAP Analytics Cloud that enables users to ask questions about their data in natural language. This conversational approach allows you to quickly gain insights without needing to navigate complex datasets.
When using an Acquired Model with just ask:
The data remains stable and unaffected by changes in the source system, giving you full control over what information is available.You can manually update the data model to ensure the model stays synchronized/up to date in just ask.With the data stored in SAC, just ask can quickly process and respond to user queries.
Why Best Practices Are Important When Creating a Model for Just Ask?
The main idea behind just ask is that, unlike other LLMs or chat assistants, just ask does not jump to conclusions if the information you are seeking is not included in the data or is not well modeled. This approach allows just ask to provide accurate answers based on your data, ensuring that it makes informed assumptions.
Here are a few suggestions for improving your model. Keep in mind that these are not mandatory but are highly recommended, and this list is not exhaustive; it can also be adapted based on the user’s discretion and specific use case.
1. Dates – Keep the Most Explanatory Date Column
When managing date-related data in your model, it’s essential to streamline the information by keeping only one date column.
Often, files may include multiple date columns with varying levels of granularity, such as daily, monthly, or yearly data. While these different perspectives can be useful, having too many date columns can clutter your model and make analysis more complex. To avoid redundancy, remove any extra date columns and retain the one that provides the most meaningful and explanatory information for your analysis.
The good news is that just ask is already equipped to handle different time granularities like Month, Year, Quarter, Year-to-Date (YTD), and Fiscal Year (FY). This means that, with the right date column in place, you can leverage just ask to easily apply time-based filters and perform date-driven analysis without the need for multiple date granularity.
By following this best practice, you simplify your model and ensure that it is optimized for efficient data queries and analysis.
2. Identify YEAR as a Date Dimension, not a Measure
When working with data extracted from different data sources, it’s common to encounter situations where the Year column is misinterpreted by the system. Instead of being recognized as a date, it may be treated as a measure, resulting as an integer or even as a value like “2023.0” being saved with a decimal point.
To fix this, it’s important to clean up the data by first removing the “.0” when identified as a decimal value. This can be easily done by replacing the decimal with an empty string, leaving you with a clean and correct year format.
Once the data is cleaned, make sure to save the Year column as a Date dimension and apply the appropriate format, typically YYYY. This ensures that the year is recognized properly in your model and is ready for time-based analysis.
If this is the only date-related column available in the model, make sure to retain it, as it will serve as the key date reference for your analysis, even if the granularity is broad.
By following this best practice, you’ll avoid data misinterpretation and ensure that your year date is properly structured for efficient analysis.
3. No Need for YTD, Previous Year, or Similar Columns
When working with SAP Analytics Cloud (SAC) and just ask, there’s no need to manually include columns for Year-to-Date (YTD), Previous Year, or similar data points.
Both SAC and just ask natively support queries and filters that handle these time-based calculations automatically. If the correct dates and years are set within your model, you can easily ask for YTD or Previous Year insights without needing dedicated columns for them.
This not only simplifies your model but also ensures more streamlined data management, allowing SAC and just ask to do the heavy lifting when it comes to time-based filtering and comparisons.
Here’s a list of time filters handled by just ask:
Time Periods: Users can specify various formats such as 2024, 2024-10, 2020.10.01, 2024/10, and 10th October, among others.Context Time Dimension: This filter includes options like “next month,” “previous fiscal year,” and the term “last,” all of which can be used with a number. For instance, users can input phrases such as “last 5 months,” “next 3 years,” or “previous 2 years,” providing them with greater flexibility in their time-based queries.Time Span: Options include phrases like “year to date,” “month to date (MTD),” and “quarter-to-date,” allowing users to easily track performance over specified periods.
Additionally, formats like “first quarter of YYYY” are also acceptable.
4. Identify IDs as Dimensions
When working with data models, it’s important to ensure that columns containing IDs or that similar values are correctly identified as dimensions, not measures.
For example, an ID column might contain a sequence of n-digit integers, but these numbers are not meant to be treated as numerical values for calculations. Instead, they represent unique identifiers, and therefore should be categorized as dimensions within your model.
By properly identifying ID columns as dimensions, you ensure that your data model remains accurate and functional, making it easier to filter, group, and analyze your data in a meaningful way.
5. Ensure Unique Values Across Dimensions to Avoid Repetition
To optimize the performance of your data models, it’s crucial to ensure that each dimension contains unique values and avoid duplicating content across different dimensions.
When the same data is repeated in multiple dimensions, it can unnecessarily increase the size of your model, leading to slower response times during analysis. By keeping each dimension unique, you reduce the model size, which improves both efficiency and performance.
It’s essential to mention that having repeated values across multiple dimensions can lead to misinterpretation of the query by just ask.
6. Ensure Unique Values Are Maintained Without Duplication Across Categories
Similarly to the previous point, it’s important to avoid repeating the name of a dimension within its own entities. Each category or entity within a dimension should have unique values, without any unnecessary duplication.
This practice not only helps keep your model clean and organized but also significantly improves response times by reducing the overall size of the model. A smaller, more efficient model translates into faster query processing and better overall performance.
7. Ensure There Are No Redundant Columns
A key best practice for optimizing your data model is to limit the presence of redundant columns, especially those that simply concatenate existing values.
Focus on keeping only the essential columns and ensure that any information derived from existing values is managed appropriately to avoid duplication.
8. Use Alternative Data Representations Instead of Binary Columns
When your data contains binary values like “Yes/No” or “1/0”, it’s a good practice to refactor the column and its values with more descriptive terms.
This adjustment helps improve the clarity and usability of your model, particularly when users query the data. For instance, instead of a binary column labeled “Region” with values like 1 for Europe and 0 for the rest of the world, consider renaming it with explicit categories, such as “Regions in Europe” or “Regions Outside Europe.”
This transformation enhances the quality of the results when users access the content through queries like “give me the sales for regions in Europe” or “show me sales for regions outside Europe.” Clear, descriptive column names make data queries more intuitive and effective.
9. Use Alternative Data Representations Instead of Many-to-Many Columns
When a column contains many-to-many values, it’s best to split those values into multiple columns to improve clarity and analysis.
Just like with binary cases, split many-to-many columns into separate one, more specific columns enhance the quality of the results when users query the data. For example, instead of having a single column that lists multiple product categories (like “Food, Beverage, Household”), it’s better to break this down into individual columns for each category.
This approach makes it easier to run specific queries, such as “give me the sales for food products,” leading to more accurate and focused results. Missing values are allowed, so if certain entries don’t apply to every column, the model will still handle it efficiently.
10. Ensure Values Are Without Units of Measure or Currency Symbols
When structuring your data, it’s important to remove any currency symbols or units of measure from within the content of your measures.
While these symbols are useful for interpretation, they should not be included directly in the data fields. Instead, both currency and units of measure should be set appropriately in the modeler. This ensures that the data remains clean and consistent, allowing for easier manipulation and analysis.
Detailed guidance on Setting Units of Measure (Static Currencies) can be found here.
Additionally, SAP Analytics Cloud (SAC) offers the ability to set dynamic currencies using table conversion features, providing flexibility for users who need to work with different currencies across regions or reports.
For comprehensive instructions on Table Currencies Conversion (Dynamic Currencies), please refer to the Display Currencies in Tables wiki.
However, at the present time, JA does not support dynamic currencies, but only static ones, so we highly recommend to set separate columns with the conversion.
11. Ensure Object Names Are Clear and Understandable
One of the simplest yet most impactful best practices for data modeling is to ensure that column names are clear and understandable.
Avoid using names that contain only numbers or special characters, such as “Date2023_02”, “–sales!@”, or “2023for&$”. These can be confusing and make the model harder to navigate and query. Instead, opt for straightforward, descriptive names that make the purpose of each column immediately obvious to anyone working with the data.
If, for some reason, a column cannot be renamed, make sure to set a synonym or ensure that it is queried exactly as it appears.
Conclusion
Adhering to above best practices is crucial for achieving high-quality, transparent, and efficient results. These guidelines ensure data is clean and well-prepared, which improves the accuracy and reliability of insights. Following consistent processes also helps reduce biases, leading to fairer outcomes.
How to Get Started with Creating an Acquired Model in SAC to Be Consumed by Just AskIn this post, we’ll dive into the steps for creating an refined Acquired Model and explore how it can really enhance your data analysis experience using just ask. While these best practices specifically apply to Acquired Models, we will go over soon in another post the best practices for working with Live Models on top of Datasphere.Just ask is the new natural language query feature powered by AI. With just ask any user can query SAC data models by asking questions in everyday English. It supports SAP Analytics Cloud acquired data models and SAP Datasphere models.Creating an Acquired Model in SAP Analytics Cloud (SAC) is a powerful way to represent and manage business data. Along with the just ask feature, which allows us to explore the model visually using natural language, this enhances our ability to analyze and interpret data effectively.For individuals who are not yet familiar with just ask and require an introductory guide, one can follows the videos below as a helpful starting point:How to Use Just AskHow to Enable and Manage Just Askor the following blog:Initial Release of SAP Analytics Cloud Just AskIn this post, we will explore the steps to create an Acquired Model and how it can enhance your data analysis experience. For more in-depth information on Acquired Models, please visit our SAP Help Portal by clicking here:Learn About ModelsCreate a Model from a Data SourceUsing Acquired Models with Just AskOnce you have created an Acquired Model in SAC, it can be consumed by just ask—a powerful AI feature in SAP Analytics Cloud that enables users to ask questions about their data in natural language. This conversational approach allows you to quickly gain insights without needing to navigate complex datasets.When using an Acquired Model with just ask:The data remains stable and unaffected by changes in the source system, giving you full control over what information is available.You can manually update the data model to ensure the model stays synchronized/up to date in just ask.With the data stored in SAC, just ask can quickly process and respond to user queries.Why Best Practices Are Important When Creating a Model for Just Ask?The main idea behind just ask is that, unlike other LLMs or chat assistants, just ask does not jump to conclusions if the information you are seeking is not included in the data or is not well modeled. This approach allows just ask to provide accurate answers based on your data, ensuring that it makes informed assumptions.Here are a few suggestions for improving your model. Keep in mind that these are not mandatory but are highly recommended, and this list is not exhaustive; it can also be adapted based on the user’s discretion and specific use case.1. Dates – Keep the Most Explanatory Date ColumnWhen managing date-related data in your model, it’s essential to streamline the information by keeping only one date column.Often, files may include multiple date columns with varying levels of granularity, such as daily, monthly, or yearly data. While these different perspectives can be useful, having too many date columns can clutter your model and make analysis more complex. To avoid redundancy, remove any extra date columns and retain the one that provides the most meaningful and explanatory information for your analysis.The good news is that just ask is already equipped to handle different time granularities like Month, Year, Quarter, Year-to-Date (YTD), and Fiscal Year (FY). This means that, with the right date column in place, you can leverage just ask to easily apply time-based filters and perform date-driven analysis without the need for multiple date granularity.By following this best practice, you simplify your model and ensure that it is optimized for efficient data queries and analysis. 2. Identify YEAR as a Date Dimension, not a MeasureWhen working with data extracted from different data sources, it’s common to encounter situations where the Year column is misinterpreted by the system. Instead of being recognized as a date, it may be treated as a measure, resulting as an integer or even as a value like “2023.0” being saved with a decimal point.To fix this, it’s important to clean up the data by first removing the “.0” when identified as a decimal value. This can be easily done by replacing the decimal with an empty string, leaving you with a clean and correct year format.Once the data is cleaned, make sure to save the Year column as a Date dimension and apply the appropriate format, typically YYYY. This ensures that the year is recognized properly in your model and is ready for time-based analysis.If this is the only date-related column available in the model, make sure to retain it, as it will serve as the key date reference for your analysis, even if the granularity is broad.By following this best practice, you’ll avoid data misinterpretation and ensure that your year date is properly structured for efficient analysis. 3. No Need for YTD, Previous Year, or Similar ColumnsWhen working with SAP Analytics Cloud (SAC) and just ask, there’s no need to manually include columns for Year-to-Date (YTD), Previous Year, or similar data points.Both SAC and just ask natively support queries and filters that handle these time-based calculations automatically. If the correct dates and years are set within your model, you can easily ask for YTD or Previous Year insights without needing dedicated columns for them.This not only simplifies your model but also ensures more streamlined data management, allowing SAC and just ask to do the heavy lifting when it comes to time-based filtering and comparisons.Here’s a list of time filters handled by just ask:Time Periods: Users can specify various formats such as 2024, 2024-10, 2020.10.01, 2024/10, and 10th October, among others.Context Time Dimension: This filter includes options like “next month,” “previous fiscal year,” and the term “last,” all of which can be used with a number. For instance, users can input phrases such as “last 5 months,” “next 3 years,” or “previous 2 years,” providing them with greater flexibility in their time-based queries.Time Span: Options include phrases like “year to date,” “month to date (MTD),” and “quarter-to-date,” allowing users to easily track performance over specified periods.Additionally, formats like “first quarter of YYYY” are also acceptable. 4. Identify IDs as DimensionsWhen working with data models, it’s important to ensure that columns containing IDs or that similar values are correctly identified as dimensions, not measures.For example, an ID column might contain a sequence of n-digit integers, but these numbers are not meant to be treated as numerical values for calculations. Instead, they represent unique identifiers, and therefore should be categorized as dimensions within your model.By properly identifying ID columns as dimensions, you ensure that your data model remains accurate and functional, making it easier to filter, group, and analyze your data in a meaningful way. 5. Ensure Unique Values Across Dimensions to Avoid RepetitionTo optimize the performance of your data models, it’s crucial to ensure that each dimension contains unique values and avoid duplicating content across different dimensions.When the same data is repeated in multiple dimensions, it can unnecessarily increase the size of your model, leading to slower response times during analysis. By keeping each dimension unique, you reduce the model size, which improves both efficiency and performance.It’s essential to mention that having repeated values across multiple dimensions can lead to misinterpretation of the query by just ask. 6. Ensure Unique Values Are Maintained Without Duplication Across CategoriesSimilarly to the previous point, it’s important to avoid repeating the name of a dimension within its own entities. Each category or entity within a dimension should have unique values, without any unnecessary duplication.This practice not only helps keep your model clean and organized but also significantly improves response times by reducing the overall size of the model. A smaller, more efficient model translates into faster query processing and better overall performance. 7. Ensure There Are No Redundant ColumnsA key best practice for optimizing your data model is to limit the presence of redundant columns, especially those that simply concatenate existing values.Focus on keeping only the essential columns and ensure that any information derived from existing values is managed appropriately to avoid duplication. 8. Use Alternative Data Representations Instead of Binary ColumnsWhen your data contains binary values like “Yes/No” or “1/0”, it’s a good practice to refactor the column and its values with more descriptive terms.This adjustment helps improve the clarity and usability of your model, particularly when users query the data. For instance, instead of a binary column labeled “Region” with values like 1 for Europe and 0 for the rest of the world, consider renaming it with explicit categories, such as “Regions in Europe” or “Regions Outside Europe.”This transformation enhances the quality of the results when users access the content through queries like “give me the sales for regions in Europe” or “show me sales for regions outside Europe.” Clear, descriptive column names make data queries more intuitive and effective. 9. Use Alternative Data Representations Instead of Many-to-Many ColumnsWhen a column contains many-to-many values, it’s best to split those values into multiple columns to improve clarity and analysis.Just like with binary cases, split many-to-many columns into separate one, more specific columns enhance the quality of the results when users query the data. For example, instead of having a single column that lists multiple product categories (like “Food, Beverage, Household”), it’s better to break this down into individual columns for each category.This approach makes it easier to run specific queries, such as “give me the sales for food products,” leading to more accurate and focused results. Missing values are allowed, so if certain entries don’t apply to every column, the model will still handle it efficiently. 10. Ensure Values Are Without Units of Measure or Currency SymbolsWhen structuring your data, it’s important to remove any currency symbols or units of measure from within the content of your measures.While these symbols are useful for interpretation, they should not be included directly in the data fields. Instead, both currency and units of measure should be set appropriately in the modeler. This ensures that the data remains clean and consistent, allowing for easier manipulation and analysis.Detailed guidance on Setting Units of Measure (Static Currencies) can be found here.Additionally, SAP Analytics Cloud (SAC) offers the ability to set dynamic currencies using table conversion features, providing flexibility for users who need to work with different currencies across regions or reports.For comprehensive instructions on Table Currencies Conversion (Dynamic Currencies), please refer to the Display Currencies in Tables wiki. However, at the present time, JA does not support dynamic currencies, but only static ones, so we highly recommend to set separate columns with the conversion. 11. Ensure Object Names Are Clear and UnderstandableOne of the simplest yet most impactful best practices for data modeling is to ensure that column names are clear and understandable.Avoid using names that contain only numbers or special characters, such as “Date2023_02”, “–sales!@”, or “2023for&$”. These can be confusing and make the model harder to navigate and query. Instead, opt for straightforward, descriptive names that make the purpose of each column immediately obvious to anyone working with the data.If, for some reason, a column cannot be renamed, make sure to set a synonym or ensure that it is queried exactly as it appears. ConclusionAdhering to above best practices is crucial for achieving high-quality, transparent, and efficient results. These guidelines ensure data is clean and well-prepared, which improves the accuracy and reliability of insights. Following consistent processes also helps reduce biases, leading to fairer outcomes. Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
