Cube for Reporting

Hi All,
What sort of optimization techniques i need to follow in order to build a cube for fast retrievals.I do not mind of disc space, but for the users retrivals should be fast. Please suggest!!
Regards,
HR

ASO cubes are much faster to calculate but I don't know that they are any quicker to retrieve from. Materalizing aggragations makes them faster than if you don't. And of course MDX formulas could slow down retrieval depending on how complex the formula is. That said, just like BSO cubes, they are pretty quick to retrieve from in most cases

Similar Messages

Advantages of using Virtual cube & Multi Cube for Reporting

Dear all,
Can you please explain me the advantages of desiging Virtual Cube with services & multi Cubes for Reporting.
Thanks in advance
Thanks & regards
Sailekha

Hi sailekha;
Pls go through the link below:
http://help.sap.com/saphelp_nw04/helpdata/en/62/d2e26b696b11d5b2f50050da4c74dc/content.htm
For the multi-cube;
you can create a reports out of different infoprovider...let's say you have infocube for actual and another for plan...you can create a report to see actual and plan both...
Hope this helps.
BK

Best practices for loading apo planning book data to cube for reporting

Hi,
I would like to know whether there are any Best practices for loading apo planning book data to cube for reporting.
I have seen 2 types of Design:
1) The Planning Book Extractor data is Loaded first to the APO BW system within a Cube, and then get transferred to the Actual BW system. Reports are run from the Actual BW system cube.
2) The Planning Book Extractor data is loaded directly to a cube within the Actual BW system.
We do these data loads during evening hours once in a day.
Rgds
Gk

Hi GK,
What I have normally seen is:
1) Data would be extracted from APO Planning Area to APO Cube (FOR BACKUP purpose). Weekly or monthly, depending on how much data change you expect, or how critical it is for business. Backups are mostly monthly for DP.
2) Data extracted from APO planning area directly to DSO of staging layer in BW, and then to BW cubes, for reporting.
For DP monthly, SNP daily
You can also use the option 1 that you mentioned below. In this case, the APO cube is the backup cube, while the BW cube is the one that you could use for reporting, and this BW cube gets data from APO cube.
Benefit in this case is that we have to extract data from Planning Area only once. So, planning area is available for jobs/users for more time. However, backup and reporting extraction are getting mixed in this case, so issues in the flow could impact both the backup and the reporting. We have used this scenario recently, and yet to see the full impact.
Thanks - Pawan

How the data is fetched from the cube for reporting - with and without BIA

hi all,
I need to understand the below scenario:(as to how the data is fetched from the cube for reporting)
I have a query, on a multiprovider connected to cubes say A and B. A is on BIA index, B is not. There are no aggregates created on both the cubes.
CASE 1: I have taken RSRT stats with BIA on, in aggregation layer it says
Basic InfoProvider     *****Table type      ***** Viewed at      ***** Records, Selected     *****Records, Transported
Cube A     ***** blank ***** 0.624305      ***** 8,087,502      ***** 2,011
Cube B     ***** E ***** 42.002653 ***** 1,669,126      ***** 6
Cube B     ***** F ***** 98.696442 ***** 2,426,006 ***** 6
CASE 2:I have taken the RSRT stats, disabling the BIA index, in aggregation layer it says:
Basic InfoProvider     *****Table Type     *****Viewed at     *****Records, Selected     *****Records, Transported
Cube B     *****E     *****46.620825     ****1,669,126****     6
Cube B     *****F     ****106.148337****     2,426,030*****     6
Cube A     *****E     *****61.939073     *****3,794,113     *****3,499
Cube A     *****F     ****90.721171****     4,293,420     *****5,584
now my question is why is here a huge difference in the number of records transported for cube A when compared to case 1. The input criteria for both the cases are the same and the result output is matching. There is no change in the number of records selected for cube A in both cases.It is 8,087,502 in both cases.
Can someone pls clarify on this difference in records being selected.

Hi,
yes, Vitaliy could be guess right. Please check if FEMS compression is enabled (note 1308274).
What you can do to get more details about the selection is to activate the execurtion plan SQL/BWA queries in data manager. You can also activate the trace functions for BWA in RSRT. So you need to know how both queries select its data.
Regards,
Jens

How the data is fetched from the cube for reporting

hi all,
I need to understand the below scenario:(as to how the data is fetched from the cube for reporting)
I have a query, on a multiprovider connected to cubes say A and B. A is on BIA index, B is not. There are no aggregates created on both the cubes.
CASE 1: I have taken RSRT stats with BIA on, in aggregation layer it says
Basic InfoProvider     *****Table type      ***** Viewed at          ***** Records, Selected     *****Records, Transported
Cube A     *****             blank                 *****           0.624305         *****          8,087,502        *****             2,011
Cube B     *****                     E   *****                      42.002653 *****                  1,669,126            *****                    6
Cube B     *****                     F *****                     98.696442    *****                  2,426,006       *****                    6
CASE 2:I have taken the RSRT stats, disabling the BIA index, in aggregation layer it says:
Basic InfoProvider     *****Table Type     *****Viewed at     *****Records, Selected     *****Records, Transported
Cube B     *****E     *****46.620825     ****1,669,126****     6
Cube B     *****F     ****106.148337****     2,426,030*****     6
Cube A     *****E     *****61.939073     *****3,794,113     *****3,499
Cube A     *****F     ****90.721171****     4,293,420     *****5,584
now my question is why is here a huge difference in the number of records transported for cube A when compared to case 1. The input criteria for both the cases are the same and the result output is matching. There is no change in the number of records selected for cube A in both cases.It is 8,087,502 in both cases.
Can someone pls clarify on this difference in records being selected.

Hi Jay,
Thanks for sharing your analysis.
The only reason I could think logically is BWA is having information in both E and F tables in one place and hence after selecting the records, it is able to aggregate and transport the reords to OLAP.
In the second case, since E and F tables are separate, aggregation might be happening at OLAP and hence you see more number of records.
Our Experts in BWA forum might be able to answer in a better way, if you post this question over there.
Thanks,
Krishnan

Back up cube for report from planning area

Hi Gurus,
We are in implementation and i had seen that client wanted to see daily data and wanted to delete that data and load next day data.One more point is client even wanted monthly data as well in a same cube and this two facilities should be in single info cube.
How is is possible?
for further info we have calday and calmonth time Chart.
please suggest me some good ideas.
I will be verythankfull to your suggestions.
Thanks a Lot
Regards,
Raj

Hi Raj,
You can use SAP BW to create reports for the user. You have the option of using an external BW system or the BW system that is coupled with the APO server. If you have an external BW system, then it is recommended that you report from there. As you may know APO is an OLTP system and thus is configured for such. The external BW system will be configured for OLAP access and thus would be much more suitable for reporting purposes.
You may want create a SAP RemoteCube so that the data in your report is "as fresh as possible".
Here are the steps if you will be using the BW component in the APO system:
1) Create an export datasource for your planning area. (Transaction /n/SAPAPO/SDP_EXTR)
2) Create an InfoSource and attach the datasource your have created in step 1. (transaction RSA1 Modelling tab)
3) Create a SAP RemoteCube and attach your InfoSource and SourceSystem to that.
4) Create a BeX query and a BeX report (either in Web or Excel).
If you will be using an external BW system here are the steps:
1) Create an export datasource for your planning area in the APO system (Transaction /n/SAPAPO/SDP_EXTR)
In the external BW system:
2)replicate the datasource your have created.(transaction RSA1, Modelling tab, sourcesystems->choose the APO system->Right click->Replicate DataSources).
3) Create an InfoSource and attach the datasource that you have created in step 2. (transaction RSA1 Modelling tab)
3) Create a SAP RemoteCube and attach your InfoSource and SourceSystem to that.
4) Create a BeX query and a BeX report (either in Web or Excel).
Note that a RemoteCube is only suitable for few users only. If you will have many users, you need to create a Basic InfoCube instead.
In your BeX query, you can choose the granularity of your report. If you want your report to be aggregated to monthly level then be sure to include the 0CALMONTH InfoObject.
Please post again if things are not clear and I will be happy to help out.

BW Cubes for reporting of Goods Receipts for materials

Hi,
I need information regarding cubes, I beleive they will be from MM area, required to be installed to report on Goods receipt for materials and the associated amount Spend that will result from those receipts, including related charges and fees.
Please share the information.
Thanks,
Rajani

HI,
If you need to get only goods receipts at MM Side you should be aware of movement types generally 1* in your system to get their values and Quantities.
If you are going from FI Side you can have FI Document type WE for GR which will help you in getting the spend amount .
Hope this helps for you.
Thanks.
Arun

How to Combine 2 dimensions in ASO cube for Reporting

Hello,
We have several OBIEE reports being extracted out of ASO Essbase cube through the RDP Layer.
The requirement by a new report is to Combine two dimension in the Underlying ASO cube.
The following two dimension needs to be combined into one, using MDX intersection
PRODUCT
- OIL
- GAS
REGION
- APAC
- AMEA
Combined Dimension
- OIL_APAC [MDX]
- GAS_APAC [ MDX]
Can you please help me the MDX syntax for acheiving the above
Cheers
MS

Hi,
Thank you for sharing this with us, and it will help others who have met with this issue.
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Use of virtual cube 0FIGL_V10 for reporting on Financal Statements

Dear all,
I am new to the GL reporting and I have a question about the usage of the virtual cube for reporting on Financial Statements.
On the content site I see that you can report your Balance Sheet based on the infocube 0FIGL_C10, where you can use the infoobject 0GLACCOUNT to display the balances.
I also installed the Virtual Cube 0FIGL_V10, which has the infoobject 0GLACCEXT to show the Financial Statement Item hierarchy.
My questions are:
- to create a Balance Sheet Report, is it advisable to use the content query 0FIGL_C10_Q001?
If I run that query now, it is showing the data on seperate G/L accounts, where I would like to see a hierarchy display.
For reporting on the capital expenditure however the requirement is that some G/L acoounts don't have to be taken into account. How can I exclude those then from the hierarchy for that report?
- to create the P&L, advice on the content site is to use the virtual cube because you have the Financial Statement Item hierarchy available there and you can report on specific financial statements.
Can anyone tell me the added value of using the Virtual Cube? Or can I skip it and just add the Financial Statement Item hierarchy in the 0FIGL_C10 cube and create a report where I select the nodes of the hierarchy that are only applicable for the P&L? Will that corrupt the figures or have any other effect?
Thanks in advance for the help!

Hi Sundar,
As ravi said the VC can be used when we have leass number of users, basically in VC the structure will be available. And moreover when you generetae a report based on Multiprovider which is based on the VC then it will pick up the data directly from the source to which it has been connected..
Hope it helps..
***Assign Points***
Thanks,
Gattu

Which one is better ODS-INFOCUBE for reporting in BW

Hello expert's
1.I want to know which one ODS or INFOCUBES are better (technically/functionally) for reporting purpose in BW.if some one is having any comparisons on ODS/INFOCUBE then plz pass on to me.
2.Are Z tables reliable in case of data updation and fetching when we create ODS/INFOCUBE.
3.HOW RELIABLE THE "Z"(*TABLES/REPORTS) are in SAP-BW/R/3-ABAP.

1.Cubes are optimized for reporting..due to star schema structure.Use cubes for reporting aggregated data to be accessed by large number of users.
ODS are for detailed level reporting.ODS structure is like flat DB table.
usually drilldown is setup from cube report to the ODS report.
2.Are u referring to custom ODS and cubes..then they have the Z tables internally..reliability depends on ur design.But always try to use BC content,else copy BC content and change/enhance it.else if no BC content found then create Z-content directly.
3.Again,depends on the design.But always using BC content is suggested.
cheers,
Vishvesh

Which on is better-ODS/INFOCUBE for reporting

Hello expert's
1.I want to know which one ODS or INFOCUBES are better (technically/functionally) for reporting purpose in BW.if some one is having any comparisons on ODS/INFOCUBE then plz pass on to me.
2.Are Z tables reliable in case of data updation and fetching when we create ODS/INFOCUBE.
3.HOW RELIABLE THE "Z"(*TABLES/REPORTS) are in SAP-BW/R/3-ABAP.

Hi Gaurav,
1.The choice of ODS or cube for reporting depends upon your requirements. It depends upon several factors like the details in which you want to see the reports, the amount of data you will be looking at etc. Since ODS is a flat structure (transparent table), you can not store large amounts of data. If you want to see some reports which contains data for several years (huge), you are better off running a report on a cube. Otherwise, reporting on ODS is ok. It all depends on your requirement.
2. You definitely can extract data from Z tables in R/3. Again the type of extraction depends upon the design of the R/3 table. You should not have any problem in extracting the data from R/3 Z tables into an ODS or cube.
3. When you say Z tables/reports, they are totally custom made. So, if they are used regularly in R/3, i think they must be reliable. If they are not reliable, they would not use them in the production server.
Hope this helps.
Thanks and Regards
Subray Hegde

(Request for reporting available) is not coming in Cube

Hi All,
I have Cube & DSO.
I added fields in DSO & Cube.
Cube1 has Aggregrates built on it.i added 5 infoobjects on it, Now when i load data from DSO to Cube(Request for reporting available) is not coming up. i cant do reporting on it. can anyone help.
thanks in advance,
Kiran.

Hi ....
Have you done the Roll up ?
Since aggregates are there on that cube....until and unless you do the roll up that request will not be available for Reporting...
Regards,
Debjani....

Request in cube is not avilable for reporting, how to trace this in chain?

Hello,
We have cube that gets the delta daily.
Some day, some body did full load and its failed.
Regular process chain delta load were sucessfull but they never turned reportable since the previous full load was failed.
Since we have not received any failure notification.
Is there way we can find if the request is not reportable to get notification>?
I have checked the avilable process types, it looks like we need to build custom process type.
Please advice.
Cheers
Angelo

Hi Angelo,
If the full update is run via a process chain then you can configure for that chain that if the load fails you get an email notification,
in the setup of the email notificaton you could make a reference to the target cube and then at least you know that if you don't fix this issue subsequent requests will not be available for reporting in the cube.
Best Regards,
Des

Simultaneous data activation in cube - request for reporting available

Hi,
I'm on BW 3.5.
I am loading several million records to a cube, processing is to PSA first and subsequently to data target.
I have broken the load up into 4 separate loads to prevent caches from filling up and causing huge performance issues.
When I load all the data in a single load, it takes 10 hours to load. When I break it up into 4 loads it takes 3 hours.
My problem is that during the loading from PSA to data target, the first data load becomes green and ready for reporting before the last one has finished loading, and so the users get inaccurate report results if they happen to run a report before the last request activates.
Is it possible to get all 4 requests to activate simultaneously?
I have tried adding an aggregate to the cube, no good.
I have tried loading the 4 loads to the PSA in sequential order in the process chain, and then loading from PSA to data target simultaneously (side by side), no good.
Does anyone have a solution?
Many thanks,
Paul White

Hi ....
Have you done the Roll up ?
Since aggregates are there on that cube....until and unless you do the roll up that request will not be available for Reporting...
Regards,
Debjani....

How to make cube data avilable for reporting

Hello,
I have loaded data in to info cube from flat file, and created a query using BEx Analyzer. that query does not return results and gives an error msg "No Applicable Data Found".
Padmanabha Rao had a same problem. In his thread, expert is recommending to check whether the data is available for Reporting by Rt clicking Infocube -> Manage -> Requests tab. Ideally, you'll be able see an indicator(Query icon) if it's available for reporting.
My cube data is not available for reporting, how can I make it available for reporting?
Regards,
Tejas.

Normally when the data gets loaded to cube, it will be available for reporting unlike DSO where you need to activate the data to make it available for reporting. There could be many reasons why the data is not available for reporting;
1. May be there is aggregrates created on the cube and the data never been rolled up to the aggregates. If you see a summation sign next to the cube then there is aggregates created on the cube and you need to fill the aggregates first before you can have the data available for reporting in the cube. To do that, manage ->rollup and start, that will fill the aggregates.
2. If there is any request in the cube which is still red, then any request after that won't be available for reporting until you either delete the red request.
If the problem still persist, then I would just delete all the data from the cube and reload the data again.
thanks.
Wond

Cube for Reporting

Similar Messages

Maybe you are looking for