Logical Partition of Cube

Hi BW experts,
Can anyone explain the steps to create logical partitioning of Cube data?
I want to do it per fiscal year. If we create 05 cubes(Same structure) each for say fiscal year 04' 05'...08'
now how will the data flow into respective cubes.
Kindly explain the steps.
thanks,
Nipun Sharma
P.S. points will be rewarded.

Hi Nipun,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
*pls assign points,if info is useful*
Regards
CSM reddy

Similar Messages

Logical Partition of infocube

We have a cube logical partitioned by sales org. We now would like to add additional sales org's to the list. Is this possible?? Currently with data in the cube it is blocked. Does anyone know steps to re-logical partition a cube?? With/or without data re-loading? Any options at the database level (oracle)?
Thanks!!

Hi,
Yes that is correct you cant do cube partitioning with existing data.
Another important thing is based upon selection conditions only you can do the partitioning. There are two selection conditions they are as follows.
1. 0CALMONTH
2. 0FISCAL YEAR PERIOD
if these two time characteristics were not used in the cube means you can't partition the cube.
STEPS TO PARTITION THE INFOCUBE:
for example if you have Sales and Distribution cube you want to do logical partitioning on that cube.
we have to create infocube with same structure ( this we can do by giving the technical name of the cube in copy from option) at the time of creation of cube. Activate the cube and come back.
then you should create update rules for that cube.
select the first cube right click on it choose the option generate export datasource.
the system will finish generation process.
select the infosource option on the left side of the AWB.
in that we have DATAMART select it choose refresh icon.
you get the infosource with datasource assignment.
select the data source right click on it choose create infopackage.
it will take you to the maintain infopackage screen.
here you need to select the datatarget tab and select the target into which the data need to be updated.
schedule it and start.
now manage the data target and check the data has been updated or not.
after doing all this process go to infoprovider select the first cube delete the data.
now depending upon your requirement do the partitioning.
double click on the cube it will take you to the edit infocube screen from the menu bar select extras it will display the partitioning option select it.
then it will popup one small wizard showing the time characteristics based upon your requirement choose which ever you want check that box and continue the process.
Hope this will help you
Thanks and Regards
Vara Prasad

Impact of logical partitioning on BIA

We are on BI release 701, SP 5. We are planning to create logical partition for some of the infocubes in our system. These cubes are already BIA enabled, so will creation of logical indexes have any impact on the BIA or improve the BIA rollup runtime

Hi Leonel,
Logical partitioning will have impact on BIA in terms of performance .
Current cube is already indexed on BIA. Now if you divide current cube data into different cubes and create multiprovider on it then each cube will have its own F table index on BIA.
you have to put new cubes to BIA and Execute Initial filling step on BIA and place rollups for respective cubes.
Point to be noted :
As Data will be deleted from Current cube and move to other cubes , Indexes will not get deleted
from corresponding F table indexes in BIA . There will be indexes for records which are not present in cube. Thus it is always a good practice to flush BIA which will remove all the indexes from BIA for current cube and create new Indexes on BIA.
In this case , we will have consistent indexes on BIA which will not hamper performance.
This will also improve rollup time as data will be less in each cube after logical partitioning. For rollup
improvement time , we can implement Delta indexing on BIA as well.
Question : Why do we want to create logical partitioning for cubes which are present on BIA as queries will never come to Cubes in BI system ?
Regards,
Kishanlal Kumawat.

Logical Partitioning -How much %age improvement.

Hello All,
I want to know if we use Logical partitioning for cube then how much %age performance will be improve and how about its depends on loaded data into the cube.
Q1:Logical partitioning of cubes - How much % of performance can be expected.
Q2:How much % of performance improvement can be expected if say no. of records in cube is half the current no. of records.
Thanks in advance,
Bandana.

Bandana,
I would say that the question is incorrect ..( Carl Sagan..? )
First - the percentage improvement depends on the amount of data - if my cube has 100 records and I do a logical partition I will not see any improvement - but then ramp up the numbers to 1 billion records - I see very significant improvements..
Lets say your cube has data for 2010 and 2011 and you want to logically separate out the data . Typically logical partitions would mean separating out the data into separate cubes by year / country etc - any partition that is not using the default partitioning of 0FISCPER / 0CALMONTH etc...
If this is not what you are looking at or if I am wrong - please correct me here...
Now if you split your cube into two parts - one cube for 2010 and one for 2011 - the time required to access the data in the 2010 cube decreases - because it has a cube of its own - this is the benefit you get in terms of data access times - but then this is not going to be a 100% improvement because you have a cube for each year... it depends to a large extent on the query also - but in almost all cases you will have a performance benefit.
I am not able to understand your second question.

Logical Data Partitioning Info cube

Hi,
We have a Legacy system data in BW which is about 25 million reports span across 6 years and by Fiscal year/period.
Currently data is held in 6 DSO's and its one time load to cube...data load won't happen on daily basis as legacy system is de commissioned.
How to Logical Data Partitioning Info cube
Thanks

Hi Choudary,
One way is as follows: Convert the update process (for 0VENDOR) to flexible update. For this you will need to make 0VENDOR an InfoProvier (RDS1 > Master data tab). Then you need to create update rules from the 0VENDOR_ATTR InfoSource to 0VENDOR InfoObject. Since you now have the 0VENDOR_ATTR InfoSource you can also create update rules from this InfoSource to your cube and load the data.
Hope this helps...

Logical partitioning, pass-through layer, query pruning

Hi,
I am dealing with performance guidelines for BW and encountered few interesting topics, which however I do not fully undestand.
1. Mainetance of logical partitioning.
Let's assume logical partitioning is performed on year. Does it mean that every year or so it is necessary to create additional cube/transformation and modify multiprovider? Is there any automatic procedure by SAP that supports creation of new objects, or it is fully manual?
2.Pass- though layer.
There are very few information about this basic concept. Anyway:
- is pass through DSO write optimized one? Does it store only one loading - last one? Is it deleted after lading is sucessfully finished (or before new load starts)? And - does this deletion do not destroy delta mechanism? Is the DSO replacing PSAfunctionally (i.e. PSA can be deleted every load as well)?
3. Query pruning
Does this happen automatically on DB level, or additional developments with exits variables, steering tables and FMs is required?
4. DSOs for master data loads
What is the benefit of using full MD extraction and DSO delta insetad of MD delta extraction?
Thanks,
Marcin

1. Mainetance of logical partitioning.
Let's assume logical partitioning is performed on year. Does it mean that every year or so it is necessary to create additional cube/transformation and modify multiprovider? Is there any automatic procedure by SAP that supports creation of new objects, or it is fully manual?
Logical partitioning is when you have separate ODS / Cubes for separate Years etc ....
There is no automated way - however if you want to you can physically partition the cubes using time periods and extend them regularly using the repartitioning options provided.
2.Pass- though layer.
There are very few information about this basic concept. Anyway:
- is pass through DSO write optimized one? Does it store only one loading - last one? Is it deleted after lading is sucessfully finished (or before new load starts)? And - does this deletion do not destroy delta mechanism? Is the DSO replacing PSAfunctionally (i.e. PSA can be deleted every load as well)?
Usually a pass through layer is used to
1. Ensure data consistency
2. Possibly use Deltas
3. Additional transformations
In a write optimized DSo - the request ID is key and hence delta is based on request ID. If you do not have any additional transformations - then a Write optimized DSO is essentially like your PSA.
3. Query pruning
Does this happen automatically on DB level, or additional developments with exits variables, steering tables and FMs is required?
The query pruning - depends on the run based and cost based optimizers within the DB and not much control over how well you can influence the execution of a query other than havin up to date statistics , building aggregates etc etc.
4. DSOs for master data loads
What is the benefit of using full MD extraction and DSO delta insetad of MD delta extraction?
It depends more on the data volumes and also the number of transformation required...
If you have multiple levels of transformations - use a DSO or if you have very high data volumes and want to identify changed records - then use a DSO.

Physical Vs Logical Partitioning

We have 2 million records in the sales infocube for 3 years. We are currently discussing the pros and cons of using Logical partitioning Vs Physical Partitioning. Please give your inputs.

hi
there are two types of partitioning generally talked about with SAP BW, logical and physical partitioning.
Logical partitioning - instead of having all your data in a single cube, you might break into separate cubes, with each cube holding aspecific year's data, e.g. you could have 5 sales cubes, one for each year 2001 thru 2005.
You would then create a Multi-Provider that allowed you to query all of them together.
A query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, running at the same time. The system automatically merges the results from the 5 queries into a single result set.
So it's easy to see when this could be a benefit. If your queries however are primarily run just for a single year, then you don't receive the benefit of the parallel processing. In non-Oracle DBs, splitting the data like this may still be a benefit by reducing the amount of rows in the fact table that must be read, but does not provide as much value to an Oracle DB since Infocube queries are using a Star_Transformation.
Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. This is a separately licensed option in Oracle.
Physical partitioning allows you to split an Infocube into smaller pieces. The pieces, or partitions, can only be created by 0FISCPER or 0CALMONTH for an InfoCube (ODSs can be partitioned, but require a DBAs involvement). The DB can then take advantage of this partitioning by "pruning" partitions during a query, e.g. a query only needs data form June 2005
The DB is smart enough to restrict the indices and data it will read to the June 2005 partition. This assumes your query restricts/filters on the partitioning characteristic. It can apply this pruning to a range of partitions as well, e.g. 0FISCPER 001/2005 thru 003/2005 would only look at the 3 partitions.
It is NOTsmart enough, however, to figure out that if your restrict to 0FISCYEAR = 2005, that it should only read 000/2005 thru 016/2005 since 0FISCYEAR is NOT the partitioning characteristic.
An InfoCube MUST be empty in order to physically partition it. At this time, there is no way to add additional partitions thru AWB, so you want to make sure that you create partitions out into the future for at least a of couple of years.
If the base cube is partitioned, any aggregates that contain the partitioning characteristic (0CALMONTH or 0FISCPER) will automatically be partitioned.
In summary, you need to figure out if you want to use physical or logical partitioning on the cube(s), or both, as they are not mutually exclusive.
So you would need to know how the data will be queried, and the volume of data. It would make little sense to partition cubes that will not be very large.
physical partitioning is done at database level and logical partitioning done at data target level.
Cube partitioning with time characteristics 0calmonth Fiscper is physical partitioning.
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.
logical Vs physical partitions ?

Physical and logical partation of cube

hi
can i get scenerio for logical and physical partation of cube.
based on year or calmonth that is called physical partation? or not
what is logical partation

Hi sunil,
Partitioning is mainly done to increase the performance by optiomizing the Time Utility.
Physical Partitioning is the partitioning done at the database level and to do so, we can partition based on the Time,date so on... In terms of Cube partitioning we usually use 0CALMONTH, 0CALYEAR or 0FISCYEAR.
And
Logical Partitioning is the partitioning done at the Query level while retriving data from the cube. This is said to be Logical because the data is not partitioned at the database level.
Ex: Restict the Query using 0CALMONT,0CALYEAR.
Hope this helps you and solves your problem,if it helps assgn pnts.
Regards
neelima

Where are partitioning a cube based on calmonth & fiscper

Q1.where are partitioning a cube based on calmonth & fiscper ok In partitioning cube there are two types 1.physical partition & 2.logical partition so i want to know the both things and diferrences.

Hi Kishore,
Logical Partitioning means dividing the data into two or more cubes. The cubes will have the same structure, but will store mutually exclusive data sets. For eg. storing data from Calendar year 2000 to 2005 in one cube, 2006 to 2008 in another cube and 2009 to 2011 in another cube. As these three cubes will have the same structure, we can create a multiprovider to combine these cubes for comprehensive reporting. This can be done any characteristic....like company code, controlling area, sales organization, distribution channels or any time characteristics. This is more of data model designing option.
Physical Partitioning is done on one cube. This is based on the Calender Month or the Fiscal period. This physically partitions the Fact table of the cube. For eg. you want to partition a cube that stores 2 years of data. The maximum no. of partitions allowed here are 26... (24 for each of the 24 months and two for data not belonging to these 24 months - these two partitions are system defaults and we have not control over). However, we can define any number less that 26 and the system calculates the maximum number to be utilized. Supposing we specify, a maximum of 18 partitions to be used, the system will use a 14 partitions only - 12 partitions for the 24 months (each 2 months) and 2 on either side of the time scale.
rgds
Naga

NW 7.3 specific - Database partitioning on top of logical partitioning

Hello folks,
In NW 7.3, I would like to know if it is possible to add a specific database partition rule on top of a logical partitioned cube. For example, if I have a LP cube by fiscal year - I would also like to specifically partition all generated cubes at DB level. I could not find any option in the GUI. In addition, each generated cube can be viewed only (cannot be changed in the GUI). Would anybody know if it is possible?
Thank you
Ioan

Fair point! Let me explain more in details what I am looking for - in 7.0x, a cube can be partitioned at the DB level by fiscal period. Let's suppose my cube has only fiscal year 2011 data. If I partition the cube at the DB level by fiscal period in 12 buckets, I will get 12 distinct partitions (E table only) in the database. If the user runs a query on 06/2012, then the DB will search for the data only in the 06/2012 bucket - this is obviously faster than browsing entire cube (even with indexes).
In 7.3, cubes can be logical partitioned (LP). I created a LP by fiscal year - so far so good. Now, I would like to partition at the DB level each individual cube created by the LP. Right now I could not - this means that my fiscal year 2012 cube will have entire data residing in only 1 large partition, so a 06/2012 query will take longer (in theory).
So my question is --> "Is it possible to partition a cube generated by a LP in fiscal period buckets"? I believe the answers is no right now (Dec 2011).
By the way, all the above is true in a RDBMS environment - this is not a concern for BWA / HANA since data is column based and stored in RAM (not same technology as RDBMS).
I hope this clarifies by question
Thank you
Ioan

Logical partition for CO-PA

Hello,
I need to split the CO-PA data into two info-cubes (logical partitioning by Record Type). I know that i can create few DataSources for COPA. Should i use the same DataSource or should i make 2 DataSources?
Please Advice,
David
Message was edited by: David Cohn

What datasources are you using now?
Cheers!
/smw

Logical Partition.

Hello All,
I have a lil knowledge about logical partition. Could you please send me some document related to logical partition?
Where and how it can be used in BW?
Thanks.

Hi ,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
Re: logical Vs physical partitions ?
*Hope this helps*
Regards
CSM reddy

Logical partitioning of an ODS - when / what size e.g. 100 Mio records?

Hi Folks,
we got an ODS/DSO with about 80 fields and we are currently planning futher rollouts which will lead to an overall volume in the DSO about 100 Mio records.
I wonder if this volume for a DSO is still fine to do reporting and loading / activation with good performance?
Or is there a "rule of thumb" to have let's say only 50 Mio reocrds in a ODS and then go for a logical partion approach in larger scenario
50 Mio -> Region EMEA, APJ
50 Mio -> Region AMS
Thanks for you inputs in advance,
Axel

100 Mo records is not such a big DSO. You should not encounter problems for loading and/or activating your DSO.
You may encounter performance problems with reporting functionnalities but it will depend on the reporting you do. And anyway, if you really want to do reporting on this data, why don't you put this level of detail in the cube (logically partitionned or not).
You can logically partitionned any kind of infoProvider, but I've never seen this for DSO (I'd rather partition the upper levels and have a DSO with all data).
Regards,
Fred

Partition on cube

Hi All,
We have some issue on Query performance.I want to know that Cubes on which this Query run has some partitioned or not how can i know this ?
<removed by moderator>
Thanks,
Deepak
Edited by: Siegfried Szameitat on Jun 22, 2011 7:43 AM

First of let me tell why we go for partition ,Partitioning is used to optimise read performance of queries.
For ex:-If you have 10 years of data in the infocube,but
you user requirement is only they want to see the data from
2 year.
Case 1:-Without partitioning whenever we run the query it will search
the relevent data from all the 10 years data,so here the performance of the
query will decreased as serach operation will take more time.
Case 2:-With partition For example if we have created partition
for 2006-2008 not system automatically creates two partition
ie before and after P1(Before partion):-2000-2006 P2:-2006-2008
P3 (After Parttition):-2008-2010.Now wheneever we run the query
it will directly go to the relevent partition and serach for the relevnet reord
here the query performance will be high as the serach operation will take
less time.
Physical partition: It is done when you want to partition the data in your cube in the database using 0calmonth or 0fiscyear.
Logical Partition: This method is used if your data in your cube become huge. So you create multiple cubes say for 1cube for 2001, another cube for 2002, etc... You can then use a multiprovider - which consists of all these cubes and then report on all the data.
You have to choose either 0FISCPER or 0CALMONTH wich is defined by the usage of your most-used big queries (i.e. weekly , monthly, quarterly) and calculate the number of necessary partitions by giving a time period from / to.
Make sure you get a good rows per partition ratio by keeping record numbers big in each partition and partition numbers small by giving a maximal partition number
i.e.
CALMONTH:
max. partition number = 96 (add 1 for MAXVALUE partition)
from 01.2000 to 12.2007 = 8 * 12 + 1 = 97 partitions (for each month 1 partition)
max. partition number = 24 (add 1 for MAXVALUE partition)
from 01.2000 to 12.2007 = 8 * 3 + 1 = 25 partitions (for each quarter 1 partition)
Thanks,
Saveen Kumar

Partitioning of cube

Gurus,
I am extracting AR data using standard datasources in BW3.5 and would like to partition the data by creating year specific cubes. I have to store data for around 15 years so I was thinking of having cubes with data for 3 years each and report using a multiprovider. But wanted to clarify a few things -
The data that will be coming for deltas, should that be going to the current cube or should my update rules be connected to all the cubes? What happends in case an older invoice is cleared, say from 1998 is cleared should the data be updated in 1998 cube as well as current or only in the current cube?
The company has 16 posting periods. If I am doing logical partioning based on 0FISCPER so should that partioning be from say 001/1998-016/2001 or will it be 001/1998-012/2001.
The company is not having fiscal variant based on calendar year, but is from April to March. Could this be a problem for me to partition the cube.
Thanks for your help.
Regards,
Venkat

Hi,
The data that will be coming for deltas, should that be going to the current cube or should my update rules be connected to all the cubes? What happends in case an older invoice is cleared, say from 1998 is cleared should the data be updated in 1998 cube as well as current or only in the current cube?
--> Chances of getting such old records are rare or almost ZERO.
--> Those records supposed to load into that particular cube only. Not to current cube(2009).
The company has 16 posting periods. If I am doing logical partioning based on 0FISCPER so should that partioning be from say 001/1998-016/2001 or will it be 001/1998-012/2001.
The company is not having fiscal variant based on calendar year, but is from April to March. Could this be a problem for me to partition the cube.
--> Fiscal variant required to report against fiscal poriod. To restrict at cube level.
Loading into a multiple cubes only useful, if query contains selection and filter restriction on infocubes. Or again accessing all cubes through multiprovider(multiple joins) creates Negative performance than a single cube.
Srini

Logical Partition of Cube

Similar Messages

Maybe you are looking for