Partioning of Cube

hi firends
i wand information on the Partition of cube, i have partition on the cube per month wise, but where it is going to show me
where i can see the data in the sap according that partition
thanks and regards
shafeeq ahmed

hi venkat,
i got it but u r saying that we can see it in extras but it is used to make the partitions,
but i want to see that if i forget or some one eariler made it and forget it
the number of partitions made on a cube where we can see value
based on what options as month wise or year wise it can by viwe in menu extras
can i chang it again
where i can see the data as per partition
u got it naa
thanks and regards
shafeeq ahmed

Similar Messages

Partioning OLAP cube

Hello experts,
I read somewhere that when the size of BPC partitions becomes too big, then to keep a good performance, it's advised to create new partitions.
This point is mentioned in "SAP_BPC_Performance_Tuning_Guide.doc" I downloaded, but impossible to find the documentation regarding the partitioning.
Could someone give me more information about it ?
Thanks in advance,
Lionel
Edited by: Lionel Blind on Feb 7, 2009 1:58 PM
Edited by: Lionel Blind on Feb 7, 2009 2:01 PM

Hi,
Partitions are necessary when you are seeing a degardation of performances of your reports because of amount of data. We can not provide a clear indication regarding amount of data because it is depending by many other details like;
Number of rows from fact table
Number of hierachies for dimensions
What filters asre used into your reports.
So into HTG you can find SSAS 2005 Partitions document.
If not then I will publish this HTG next week.
Regards
Sorin Radulescu

Logical Partioning

Hello Experts,
Can someone let me know the procedure of logical partioning a cube. I am actually designing a cube for each year and i would want to know the whole process ( the configuration in BW including ).
All answers would be duly rewarded.
Thanks,
Nandita

Hi Nandita,
Well, u really need not to have separate the cube for the Yearly basis. U have store data for several years in the same Cube. Well Logical partitioning is dividing the data on the TimeScale, The Permitted time Scale is either CALMONTH or FISCPER (fiscal period) (Only one is possible, not both), Here there will be individual tables at the database for timescale.
U can follow the path Cube-Extra-partitioning- select your timescale- and the range.
Here no of table created will ne range+2, two for Before and after range.
This Database partitioning is based on underlying database, Not all database Support this, MS SQL do not support database partitioning whereas Oracle Supports.
While creating this database partitioning cube should not contain any data.
This all is information pertaing the database partitioning.
Assign the points if it helps You.

What is the use of cube partition?

Hi,
What is the purpose of partioning the cube by 0calmonth, 0fiscper? Is creating aggregates on cube by 0calmonth, 0fiscper same?
Thanks,
Sammy

hi sammy,
Partition of the cube is done to improve the query performance. If u dont do partition the data will get stored in the infocube randomly. while reporting it will take more time to execute the report because it needs to search the records in the entire infocube.
If u do partitions on a infocube while reporting the performance is improved because it will search records only in the relevant partitions not on the entire infocube and the response time of the query is improved.
Partition allows you to organize your data in a proper manner so that it decreases the search time.
In order to do partiton we should have 0calmonth,0fiscper infobjects in your infocube.
If u are having more years of data in the data ware house do partition based on ofiscper otherwise some years of data i.e 3 years do using 0calmonth.
Only oracle database supports partition.
Aggregates can be done on any characteristics we can create a aggregate on region infoobject as well but partition is be done only on 0fiscper,0calmonth.
Partition also improves load performance.
Assign points if u found helpful
Message was edited by:
Shahid Syed

Drill-through via Transparent Partition

Hi
I am using Essbase Server and EIS 11.1.1. I have a ASO target cube which points to different ASO source cubes partitioned on dates. Each source cube has defined a drill-through report and this drill-through reports work fine if I access them directly from Excel add-in. But when I access these source cubes via my target cube (transparent partition) drill-through reports don't work (no visual effect on intersection cells). When I double click on them I cannot see my drill-through reports. Could anyone tell me what I am doing wrong here please? According to documentation, I should be able to drill-through via tranparent partioned target cube.
Regards
Chandra

Thank you for the reply but Essbase Studio does NOT support drill-through from Recursive Hierarchy dimensions. That's why I had to go back to EIS.
Edited by: user2695091 on 20-Feb-2009 17:30

Partition of Infocube

Hi Gurus,
I need to design new Infocube by having existitng Infocubes as reference. How can I know wether the existing Infocube is partioned with Fiscal year or Fiscal period???

Hi BW,
Some more info on partitioning
You can partition a cube only when there is no data in it.Recommended alternative as against deleting the data in cube and reloading after partitioning is to create a copy of cube. Suppose if you want to partition cube A, the steps would be
1)Create a cube B which is a copy of cube A
2)Generate export datasource on cube A to transfer data to cube B
3)Empty cube A
4)Do partioning in cube A for the characteristics mentioned in the above post.
5)Generate export datasource on cube B to transfer data back to cube A
6)Delete cube B
Regards,
Balaji

Partitioning the fact table

Hi Gurus,
I have a question regarding partitioning the cube. When you partition the cube from the Extras menu, will it partition the F table or is it the E table or both.
Second question: After partitioning, how will i know the newly created table names.
Thanks,
ANU

Hi Anu,
Partition Need and its definition
Infocube contains huge amount of data n the table size of the cube increases regularly. so
when a query is executed on cube then it has to check entire table to get the records for
example Sales in Jan08.
Advantage of Partition
so we can partition the cube so that smaller tables are formed .so that report performance
will increase bcoz the query hits that particular partition.
Steps for Partition
1.To partiotion a cube, it must not contain data.
2. Partition can be done using time characteristics 0CALMONTH and fiscalperiod.
steps:
1. in change of the cube, select extras menu and Partioning option.
2. select calmonth time characteristic.
3. it will ask for the time period to partiotion and no. of partiotions. give them
4. activate the cube.
In BI 7 we can partition the cube even if it contains data.
select the cube, right click , select repartitioning.
1. we can delete existing partitions
2. create new ones
3. merge partitions.
Partitioning of the Cube
http://help.sap.com/saphelp_nw04s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Partitioning Fields and Values
partition of Infocube
Partitioning of cube using Fiscal period
Infocube Partition
After Partition
You can find the Partition in the following tables in SE11 >
E tables /BIC/E* or /BIC/E(cube name)
Please also go through the following links
Partioning of Cube
partioning
Partioning of ODS object
/thread/733456 [original link is broken]
Hope i had answered your question
Assign points if helpful,
Thanks and regards
Bala

Any real reason for logical partitioning over physical?

Hi!
I have seen a number of scenarios where SAP BI (assuming BI 7.0 for the rest of the discussion), running in high volume scenarios, have been cluttered by a lot of logically partitioned cubes joined by multi providers....
Obviously the disadvantage of using logical partitions is that it increases maintenance efforts: you need a new update rule for each logical partition (cube) , then you need to manually add/delte cubes from the multiprovider, filtering data in the update rules to reach the correct cube based on time characteristic etc etc...
I have seen one clear advantage which is the parallelization of queries run against a multiprovider - assuming you wan't to all underlying cubes ... but are there any other advantages which overcome the mainenance overhead?
For me it feels like using physical database partitions in the same cube would be the correct decision in 90% of the cases. It seems to me that the underlying RDBMS should be able to handle itself to:
1) Parallellize a query over several physical partitions if needed.
2) Be smart enough to only query the needed partition if the query is restricted based on the partitioning characteristic.
Please correct me anyone? - When is logical partitions really motivated?
Best regards,
Christian
Edited by: Christian on May 15, 2008 3:55 PM

Hi,
This is a great question. Generally it is very difficult to understand the real motivation for the physical partioning - multiple cubes. You are right, it definitely increases the maintenance overhead. And you have already pointed out both the advantages and disadvantages.
Physical Partitioning is more useful where we have huge amounts of data. Imagine a cube with 3 or 4 GB of data - which are not usual - but possible. The Table Partioning is useful with small infocubes, less than 1 GB. With bigger Infocubes, Table level partitioning may not provide the required level of performance. If we have too many small partitions, that would also reduce the perfomance. If we have too few partitions, the query performance will not be as much as we want. In this scenario, we can use Physical partitioning (Multiple Cubes) combined with Table Level Partitioning to achieve the required performance levels. On top, we can even think of using Aggregates for further betterment of the performance.
While all the above seems to be relevant for older versions of BW (upto 3.5), BI 7.0 has the BIA (BI Accelerator), which works on the Blade Server with all the data cached directly on the main memory. I am not sure how much this would impact the data modeling - I have not started working on the BIA as yet.
rgds
naga

SAP BPC Partitioning on a Windows 64 bit Server

Hello, we are considering SQL Server 2005 partitioning the SAP BPC (V5 SP3) time dimension by month on a Windows 64 bit Server since we curently have more than 70 million records in the application FACT table. Has any body got any experience of partitioning with Windows 64 bit servers and if so can you provide ay recommendations and did you come across any issues that we should be aware of?

Hi Wayne,
It is no difference between 64 bits and 32 bits regarding the partioning of SQL 2005.
I think you would like to partition the cubes not the table.
Partioning of table doesn't help for performances but partionning of cube for OLAP it is provide at least 40% improvements for retrieve data (mdx queries).
So if you know to do the partitioning for 32 bits then you have to follow the same steps for 64 bits.
If you need information about how to do partitions in general then you can find into wiki information about how you can do partitions for BPC 5.X.
Regards
Sorin Radulescu

Steps for cube partioning

hi gurus
can any one tell me detail steps for cube partioning .And what is the use.
regards
karan

Follow these thread
Partitioning of the Cube
http://help.sap.com/saphelp_nw04s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Partitioning Fields and Values
partition of Infocube
Partitioning of cube using Fiscal period
Infocube Partition
Khaja

Getting Strange Error Running Query After Partioning Cube

I am using BI 7.0, Service Pack 11:
I just partitioned a cube. I hav eorginal cube XFI_C001 and create a new cube C2_XFIC01 by copying from XFI_C001. Now I developed a query on C2_XFIC01. Similar query on XFI_C001 does not give any error. How can I debug this problem? Error reported when running query is shown below. I ran ST22, no dump. I did SM50, looked at developer trace, no clue.
The initial exception that caused the request to fail was:
Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:148)
at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113)
Detailed Exception is:
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error while generating HTML
     at com.sap.ip.bi.webapplications.ui.items.UiItem.render(UiItem.java:365)
     at com.sap.ip.bi.webapplications.runtime.rendering.impl.ContainerNode.render(ContainerNode.java:63)
     at com.sap.ip.bi.webapplications.runtime.rendering.impl.PageAssemblerRenderingRoot.processRendering(PageAssemblerRenderingRoot.java:52)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:3565)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:3280)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:3236)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2512)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:956)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:842)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:430)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:174)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:148)
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113)
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:144)
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113)
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:144)
     at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:113)
     at com.sap.ip.bi.base.application.service.RfcService.fillMessages(RfcService.java:268)
     at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:218)
     at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:57)
     at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:227)
     at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:57)
     at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.prepareForSelectionMemberAccess(ProviderInfoObject.java:1215)
     at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.setup(ProviderComponentList.java:87)
     at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.getComponents(ProviderComponentList.java:120)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.ComponentList.setup(ComponentList.java:96)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.ComponentList.<init>(ComponentList.java:77)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.CartesianProduct.setup(CartesianProduct.java:78)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.CartesianProduct.<init>(CartesianProduct.java:55)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.Selection.<init>(Selection.java:57)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.createSelection(SelectionObject.java:538)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.getSelectionSpace(SelectionObject.java:549)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.getEffectiveSelection(SelectionObject.java:577)
     at com.sap.ip.bi.km.impl.KmUtilities.getEffectiveSelection(KmUtilities.java:66)
     at com.sap.ip.bi.km.impl.source.property.QueryBuilderMulti.getQueryExpressionWrapper(QueryBuilderMulti.java:129)
     at com.sap.ip.bi.km.impl.source.CmFolderSource.getDocumentQueryResult(CmFolderSource.java:132)
     at com.sap.ip.bi.km.common.selection.DocumentSelectorResultSet.readQvDocuments(DocumentSelectorResultSet.java:234)
     at com.sap.ip.bi.km.common.selection.DocumentSelectorResultSet.getCellsWithDocuments(DocumentSelectorResultSet.java:136)
     at com.sap.ip.bi.km.common.selection.DocumentsSelectionService.getCellsWithDocuments(DocumentsSelectionService.java:258)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsDataCells.hasDocuments(RsDataCells.java:620)
     at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsDataCell.hasDocuments(RsDataCell.java:543)
     at com.sap.ip.bi.webapplications.ui.items.analysis.renderer.interactive.RendererInteractive.createContent_DocumentSymbol(RendererInteractive.java:1660)
     at com.sap.ip.bi.webapplications.ui.items.analysis.renderer.interactive.RendererInteractive.createCell_Content(RendererInteractive.java:545)
     at com.sap.ip.bi.webapplications.ui.items.analysis.renderer.interactive.RendererInteractive.createCell(RendererInteractive.java:525)
     at com.sap.ip.bi.webapplications.ui.items.analysis.renderer.interactive.RendererInteractive.createTableRow(RendererInteractive.java:489)
     at com.sap.ip.bi.webapplications.ui.items.analysis.renderer.interactive.RendererInteractive.getContent(RendererInteractive.java:423)
     at com.sap.ip.bi.webapplications.ui.items.analysis.control.AcPivotTableInteractive.buildUrTree(AcPivotTableInteractive.java:321)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:33)
     at com.sap.ip.bi.webapplications.ui.framework.base.composites.UiRootContainer.iterateOverChildren(UiRootContainer.java:40)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.advancedcontrols.bridge.AcItemBridge.iterateOverChildren(AcItemBridge.java:61)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.FlowLayoutItem.iterateOverChildren(FlowLayoutItem.java:63)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.FlowLayout.iterateOverChildren(FlowLayout.java:69)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.framework.base.composites.UiRootContainer.iterateOverChildren(UiRootContainer.java:40)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.advancedcontrols.bridge.AcItemBridge.iterateOverChildren(AcItemBridge.java:61)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.MatrixLayoutCell.iterateOverChildren(MatrixLayoutCell.java:63)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.MatrixLayoutRow.iterateOverChildren(MatrixLayoutRow.java:56)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.MatrixLayout.iterateOverChildren(MatrixLayout.java:69)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.container.matrixlayout.control.AcMatrixControlGrid.iterateOverChildren(AcMatrixControlGrid.java:40)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.framework.base.composites.UiRootContainer.iterateOverChildren(UiRootContainer.java:40)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.advancedcontrols.bridge.AcItemBridge.iterateOverChildren(AcItemBridge.java:61)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.Group.iterateOverChildren(Group.java:63)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.container.group.control.AcGroupControl.iterateOverChildren(AcGroupControl.java:259)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.framework.base.composites.UiRootContainer.iterateOverChildren(UiRootContainer.java:40)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.advancedcontrols.bridge.AcItemBridge.iterateOverChildren(AcItemBridge.java:61)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.FlowLayoutItem.iterateOverChildren(FlowLayoutItem.java:63)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.FlowLayout.iterateOverChildren(FlowLayout.java:69)
     at com.sap.ip.bi.webapplications.ui.framework.base.impl.CompositeBuildUrTreeTrigger.process(CompositeBuildUrTreeTrigger.java:36)
     at com.sap.ip.bi.webapplications.ui.framework.base.composites.UiRootContainer.iterateOverChildren(UiRootContainer.java:40)
     ... 42 more

Hi,
The error log shows you are executing your query on portal which uses Java stack. There may some issue with the portal configuration. Check with your basis/portal team.
The query will execute in BEx and RSRT as RSRT executes query on ABAP stack.
Regards,Niraj

Partioning cube Measures dynamically

Hi Team,
We need to partition our cube dynamically based on year and period(ex 201306). So when there is a data load/update is happening in the fact only the particular partition is processed and not all.
Dynamic partition I mean, when there is a load happening for a particular Year and Period, then a partition need to created in the cube.
Please suggest. Thanks.
Regards
Jim

Hi Jim,
According to your description, you want to create the partition dynamically and then load/update is happening in the fact only the particular partition is processed and not all, right?
For creating dynamically partition, please refer to the link which provided by Sqlsaga.
For dynamic partition processing since re-processing the full cube is no longer viable due to the length of time it is taking, please refer to the links below to see the detail information about it.
http://secretsql.wordpress.com/2011/02/06/ssas-dynamic-partition-processing/
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/a3af5aaa-0ac0-45ec-b972-b9d7a2482ed6/dynamically-processing-partition-of-a-cube-with-ssis-package-2008?forum=sqlanalysisservices
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

Partioning cube

Hello All,
Please give me steps to do physical and logical partioning in infocube

Hi ,
check out this link for physical partitioning :
http://help.sap.com/saphelp_nw04/Helpdata/EN/0a/cd6e3a30aac013e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/Helpdata/EN/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
Logical partitioning :
https://community.altiusconsulting.com/blogs/glenchambers/archive/2008/03/10/infocube-partitioning.aspx
Physical Vs Logical Partitioning
hope it helps,
Supriya

Semantic Partitioning Delta issue while load data from DSO to Cube -BW 7.3

Hi All,
We have created the semantic partion with the help of BADI to perform Partitions. Everthing looks good,
first time i have loaded the data it is full update.
Second time i init the data load. I pulled the delta from DSO to Cube . DSO is standard where as Cube is partition with the help of semantic partition. What i can see is the records which are updated in Latest delta are shown into the report rest all are ignored by the system.
I tried compression but still it did not worked.
Can some has face this kind
Thanks

Yaseen & Soujanya,
It is very hard to guess the problem with the amount of information you have provided.
- What do you mean by cube is not being loaded? No records are extracted from DSO? Is the load completing with 0 records?
- How is data loaded from DSO to InfoCube? Full? Are you first loading to PSA or not?
- Is there data already in the InfoCube?
- Is there change log data for DSO or did someone delete all the PSA data?
Sincere there are so many reasons for the behavior you are witnessing, your best option is to approach your resident expert.
Good luck.
Sudhi Karkada
<a href="http://main.nationalmssociety.org/site/TR/Bike/TXHBikeEvents?px=5888378&pg=personal&fr_id=10222">Biking for MS Relief</a>

Cube to cube data transferred ,and delta status

Hi Gurus
I need to do Portioning in cube
I have a cube Zaa_c01 which is updated by two data source ZDS1 and ZDS2 (Delta Update) I copy the Zaa_c01 and I created new cube Zaa_c02, also I transferred the data to that. But it is shoeing in single request in cube, after partion I again reloaded to ZAA_C01 , know I am seeing only single request in a cube.
Whether I lose delta in this case , or I am missing any step, this activity I done in Development, and need to do in production.
Regards
Shashi

Hai Shashidhar,
Partitioning is split the large dimensional cube into smaller cubes.... regarding performance point of view we have to do this partitioning.
there are two types of partitioning..
1. Logical Partitioning.
2.Physical Partitioning
physical partitioning is done at Database level . and logical partitioning done at Data target level.(EX: Info cube level)
Cube partitioning with time characteristics 0calmonth Fiscper is physical partitioning.(so, we need at leats one of the above time charecterstics for doing partioning...).
Logical partitioning is u partition ur cube by year or month that is u divide the cube into different cubes and create a multiprovider on top of it.
STEPS :
SELECT YOUR CUBE.. AND DOUBLE CLICK IT..->
in the menu's select EXTRAS menu--> in that select -->DB PERFORMANCE sub menu..-> in that again select Partitioning sub menu..
and specify how many partions you want to do...
but you cube should be contain atleast ocalmonth or phical varient should be there...
Prerequisites
You can only partition a dataset using one of the two partitioning criteria calendar month (0CALMONTH) or fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoProvider.
http://help.sap.com/saphelp_nw04s/helpdata/en/8c/131e3b9f10b904e10000000a114084/frameset.htm
Thanks,
kiran.

Partioning of Cube

Similar Messages

Maybe you are looking for