Skip to Content

SAP Analytics Cloud Import Data - Data volume constraints from SAP BW?

Hello,

i would like to know there are constraints in data volume and rows when I import data from SAP BW?

Thanks in advance!

Mo Schaaf

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Jan 16 at 06:41 AM

    With live connection, data volume is processed in your back-end system. There is no theoretical limitation. Query is executed in back-end system. Query should limit volume returned to Web Browser by applying adequate input control or aggregation.

    With Data acquisition, it exists volume limitations as follow:

    Data acquisition maximums:

    • Columns: 100
    • Rows: 800,000
    • Dimension members:
    • Planning models: 250,000
    • Analytic models: if there are more than 250,000 unique members, the dimension will be made read-only
    • Dimension members with attributes: 150,000
    • Dimension members with geo enrichment: 200,000
    • Dimension members in hierarchy: 150,000
    • Hierarchy depth: 1,000

    Regards,

    Geetha.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi You can tell me that in an official document I find the limited of 250,000 import for the plannig models because I am looking for and found over the 800,000 records but I find the import limit in plannning when the source is a BW. Thank you

  • Posted on Jan 16 at 10:18 AM

    Hello,

    The figures presented by Geetha are correct, but this is only the theoretical part (and applies very well to SQL sources like Google BigQuery, SAP HANA or any SQL DB you have connection with -> for SAP BW - no matter the version of your BW 7.3, 7.4, 7.5... #HANA or #NON HANA, the figures are highly different).

    In reality, the end results of your data acquisition process from BW sources (BW Query) will get influenced by the number of dimensions from your query and the measures (Calculations; KF's; restricted KF; Aggregations and Exceptions Aggregations).

    Be very careful that when you consume data from SAP BW because if you are expecting to have the same number of rows and columns as you see in Analysis Office, in SAC you will get a lot less. Even if changing the setup from RSADMIN in BW or you are increasing the SCC agent/ Tomcat server limitations, you will still have a dataset results less important than in Analysis Office.

    Please be very careful with your expectation SAC <-> SAP BW (Data Acquisition) because you'll are going to be deceived at the end.

    There are solutions and workarounds, but I find them very complex to use and not really friendly.

    Tips to get around:

    • Create queries in BW for that resume only to specif context -> avoid phrases "one query for all my needs";
    • If you have errors/limitations- you can acquire each key figure in a separate sac query -> create a model with one measure and all the dimensions (once it is create) add a second measure into the model, create a new query for that new measure update it in SAC and continue like that until you finish;
    • Create a model with a limited number of rows and initialise the model with the historical data from .CSV or Excel file exported from the BW query;
    • Create complex calculations/restrictions and exception aggregations as much as possible in SAC (Model and Story) -> avoid using BW Queries with huge amount of calculations - complex formulas;
    • Create as much as possible Public Dimensions with hierarchies (Key and Text) and use them into blank models in order to avoid a higher number of columns retrieval from BW;
    • If your BW Systems allows it -> use HANA in order to exploit a higher number of rows and columns that you may be able get from BW;
    • Imagine a mix between Analysis Office (for details - drill - slice and dice) and SAC (to have the "big picture") - think about the interoperability of these tow solutions;

    I hope you have a better understanding of how to get along with BW data acquisition into SAC.

    Regards,

    Alex

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 15 at 10:09 PM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 13 at 05:43 AM

    I would also see on the safety belt in BW - normally that is 500.000 cells - so no matter how much data SAC can store - BW is only allowed to send 500.000 cells

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.