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

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

Partition on InfoCube F table for loading & query performance

I am thinking of creating partition on our SalesStatististics (Utility Ind) cube. The reasone why we are not dividing the cube into yearly/monthly cubes is because the posting trans can be back dated and maintaining all these InfoCubes would be hard.
In the partitioning of InfoCube by month, I am thinking of running ABAP code in the process chains to drop the index on only the current partition. I know that there could be a few transaction that might get directed to other partitions but not whole lot. I am trying to avoid deleting the index on the entire cube and then rebuilding them as it takes 5-6 hours.
Has anyone writen/used such code to drop index on a single partition. Or does anyone has a clue if this is an okay thing to do? Any ideas?
SYSTEM: BW3.5, Custom Utility SalesCube Statistics, Total: 1000 million recs, Each Delta about 700K records
The cube is extremly slow in loading as well as queries. I am also dividing the cube into yearly cubes but the current year would have monthly partitions. A multi-cube would be on top and an ODS would provide item level data before the cube.
thanksin advance...
Bilal

I'll post some of the specific questions later. It seems we do not get much response when overall design is the concern.
Thanks anyway.

Partitioning InfoCubes on BW 3.5

Hi all,
we are currently starting the process of partitioning two infocubes on our system.
FYI DB is Oracle 9.2 and it is BW 3.5.
The two Infocubes have been emptied of data and have been logically partitioned by CALMONTH over a year with a total of 14 partitions.
We are also going to physically partition these cubes, is this required, i.e. does physical and logical partitioning go together???
Does anyone know the work involved physically partitioning the cubes as I can't find any OSS notes???
Thanks for your help in advance,
Shane.

Physical Vs Logical Partitioning

Is there a way of partitioning the data in the cubes

Hello BPC Experts,
we are currently running an Appset with 4 Applciations. Anyway two of these are getting really big.
In BPC for MS there is a way to partitioning the data as I saw in the How tos.
In NW Versions the BPC queries the Multiprovider. Is there a way to split the underlying Basis Cube to several (split by time or Legal Entity).
I think this would help to increase the speed a lot as data could be read in parallel.
Help is very much appreciated.
Daniel
Edited by: Daniel Schäfer on Feb 12, 2010 2:16 PM

Hi Daniel,
The short answer to your question is that, no, there is not a way to manually partition the infocubes at the BW level. The longer answer comes in several parts:
1. BW automatically partitions the underlying database tables for BPC cubes based on request ID, depending on the BW setting for the cube and the underlying database.
2. BW InfoCubes are very different from MS SQL server cubes (ROLAP approach in BW vs. MOLAP approach usually used in Analysis Services cubes). This results in BW cubes being a lot smaller, reads and writes being highly parallel, and no need for a large rollup operation if the underlying data changes. In other words, you probably wouldn't gain much from semantic partitioning of the BW cubes underlying BPC, except possibly in query performance, and only then if you have very high data volumes (>100 million records).
3. BWA is an option for very large cubes. It is expensive, but if you are talking 100s of millions of records you should probably consider it. It uses a completely different data model than ROLAP or MOLAP and it is highly partition-able, though this is transparent to the BW administrator.
4. In some circumstances it is useful to partition BW cubes. In the BW world, this is usually called "semantic partitioning". For example, you might want to partition cubes by company, time, or category. In BW this is currently supported through manually creating several basic cubes under a multiprovider. In BPC, this approach is not supported. It is highly recommended to not change the BPC-generated Infocubes or Queries in any way.
5. If you have determined that you really need to semantically partition to manage data volumes in BPC, the current best way is probably to have multiple BPC applications with identical dimensions. In other words, partition in the application layer instead of in the data layer.
Hopefully that's helpful to you.
Ethan

How to know Whether Partition is done for Cube or not

Hi All,
I need information regarding Partition of a cube.
a)How do i know the Partition is done or not for Cube
b)On what basis we should make parttion of Cube.
Thanks and Regards,
C.V.

There are several threads on partitioning, so it would be a good start for this question (as with any question) to search the BI forums on "Partitioning" and review thsoe first.
Some basic considerations on partitioning -
- Your DB must support Range partitioning to permit partitioning your InfoCube. The option will be greyed out if it is not available.
- InfoCube must be empty to be partitioned.
- InfoCube can only be partitioned on 0FISCPER or 0CALMONTH. You can define it so that you have a partition for each month/fiscper, or so that each partition will hold a few or several months of data.
- Generally, you would not partition small cubes.
- Thru BW 3.5 Aggregates automatically get partitioned the sme way the InfoCube is partitioned as long as the partitioning characteristic is in the aggregate. In 2004s, I believe you have options as to whether an aggregate gets partitioned or not.
- Partitioning may be done for query performance reasons and data administration. If the queries on the InfoCube regularly run with restrictions/filters on the partitioning characteristic (FISCPER or CALMONTH), the database will "prune" any partitions that do not contain the FISCPER/CALMONTH value(s), so that it does not need to consider them , e.g. most of your users only run a sales query for the current and previous month, but your cube contains 3 years of data. By partitioning on CALMONTH (we'll assume 1 partition / month), the database will exclude all but the two partitions from consideration. This could help query performance a lot. or maybe only a little, depending on a variety of other factors.
Again - it is important that the queries restrict onthe partitioning characteristic to be of any value on query performance. So don't partition on FISCPER if all the queries use CALMONTH for restrictions.
The data adminsitration reason you might partition is to improve selective deletion or archiving time. These processes are capable of using a DB function to Drop the partition, which quickly removes the data from the cube, rather than having to run a resource intensive Delete query. This only happens if you deletion/archiving criteria is set to remove an entire partition of data.
Again - review the other threads on the BI forums on Partitioning. Most questions you have will already have been asked and answered before, and post again on SDN if there is something you still have a question about.

Phys Partitioning steps in Netweaver 2004s

Dear SDN,
I am trying to do physical partition a cube in Sandbox.
Extras option has nothing as Partioning it shows clustering and DB archiving.
How to do this in 2004s.
Regards,
Rahul

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.
If you want to partition an InfoCube using the fiscal year/period (0FISCPER) characteristic, you have to set the fiscal year variant characteristic to constant.
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.
Hope it Helps
Chetan
@CP..

Does not allow to set time characteristics while performing Partition

I had loaded the monthly inventory cube without setting any partition.
Now, when I tried to partition the cube thru RSDCUBE >> Change >> DB performance >> Partition, the time characteristic is greyed off and does not allow to set.
Is it becuase the cube had been loaded? Can I perform the partition now that I had compressed the request in the cube?

Yes you are correct....You want to modify an InfoCube into which data has already been loaded. You use remodeling to change the structure of the object without losing data.
You use partitioning to split the total dataset for an InfoProvider into several, smaller, physically independent and redundancy-free units. This separation improves system performance when you analyze data delete data from the InfoProvider.
You can only partition a dataset using one of the two partitioning criteria u2018calendar monthu2019 (0CALMONTH) or u2018fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoProvider.
But you are trying to partition the cube which already has data so...You choose Repartitioning...
Repartitioning can be useful if you have already loaded data to your InfoCube, and:
●      You did not partition the InfoCube when you created it.
●      You loaded more data into your InfoCube than you had planned when you partitioned it.
●      You did not choose a long enough period of time for partitioning.
●      Some partitions contain no data or little data due to data archiving over a period of time.
Let me know if you need help with the steps to perform repartitioning

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

Cube Partition

Hi,
Can anbody please explain as to what criteria is used to specify the MAX. NO OF PARTITIONS when partitioning a Cube.

Hi
By using partitioning you can split up the whole dataset for an InfoCube into several, smaller, physically independent and redundancy-free units. Thanks to this separation, performance is increased when reporting, or also when deleting data from the InfoCube.
Only certain database providers support this function (for example, ORACLE, INFORMIX). If you use a database that does not support this function, then this function is not provided by the BW system.
Integration
Prerequisites
You can only partition a dataset using one of the two partitioning criteria u2018calendar monthu2019 (0CALMONTH) or u2018fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoCube.
If you want to partition an InfoCube using the fiscal year/period (0FISCPER) characteristic, you have to set the fiscal year variant characteristic to constant.
See Partitioning InfoCubes using the Characteristic 0FISCPER
Functions
When activating the InfoCube, the fact table is created on the database with one of the number of partitions corresponding to the value range. You can set the value range yourself.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
6 years * 12 months + 2 = 74 partitions are created (2 partitions for values that lay outside of the range, meaning < 01.1998 or >12.2003).
You can also determine how many partitions are created as a maximum on the database for the fact table of the InfoCube.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
You choose 30 as the maximum number of partitions.
Resulting from the value range: 6 years * 12 calendar months + 2 marginal partitions (up to 01.1998, from 12.2003) = 74 single values.
The system groups three months at a time together in a partition (meaning that a partition corresponds to exactly one quarter); In this way, 6 years * 4 partitions/year + 2 marginal partitions = 26 partitions are created on the database.
The performance gain is only gained for the partitioned InfoCube if the time dimension of the InfoCube is consistent. This means that all values of the 0CAL* characteristics of a data record in the time dimension must fit each other with a partitioning via 0CALMONTH.
In the following example, only record 1 is consistent. Records 2 and 3 are not:
Activities
In the InfoCube maintenance choose Extras ® Partitioning, and specify the value range. Where necessary, limit the maximum number of partitions. Note: You can only change the value range when the InfoCube does not contain any data.

Partitioning rules

Should partitioning be performed at the Cube and RDBMS level? Is this an AND or an OR issue where you can do both or only either one?
What are the things to look out for when partitioning?
What are some of the rules?

First - Partioning concept is related to Performance in BI.
Nor mallally it leads to Data loading Performnce & Query Performnce.
Plz find some of the points below related to Cube Partioning.
F-Fact tables and partitioning :
Similar to PSA tables the partitioning of F-fact tables is done automatically. The key difference is the partitioning key. SAP BI will create a new partition for every new load job which inserts data into the F-fact table of an InfoCube. The so-called request id is included in the InfoCube in the form of the package dimension. Therefore the key in the F-fact table which is used to join to the package dimension is also the partitioning key. In the example under b, 18 load jobs inserted test rows into the PSA table. These rows were loaded into the InfoCube via a Data Transfer Process DTP. Figure 11 shows 4 load requests in the InfoCube and figure 12 shows that there are 4 corresponding table partitions in the F-fact table. But how did we get 4 requests in the F-fact table while there are 18 requests in the PSA Table ? Here are a two things to consider in order to understand how a DTP inserts data into a F-fact table :
1. when a DTP in delta mode will be started immediately after a request was loaded into the PSA table it will create a new partition in the F-fact table to store the data.
This is what happened with the first three requests ( ID 413, 415 and 417 ) which can be seen on figure 11. It also shows that depending on the load pattern there might be partitions of very different size within the same fact table.
2. when <n> requests are loaded into the PSA table before the DTP starts then the
DTP will combine all of them into one request in the F-fact table. This is what happened with the other 15 PSA requests in the PSA table. Each of them had 110K rows. Figure 11 shows the total number of rows under u201CTransferredu201D for request ID 433. In addition to this the DTP will aggregate the data from the PSA requests by its key columns. In the sample the 15 PSA requests which were loaded into the InfoCube via one single DTP had 110K rows each and were identical regarding the customer dimension as well as the time dimension ( only two dimensions in the cube ). Aggregation in this case means that all rows with
the same dimension values will be combined and the u201Ckey figuresu201D will be calculated ( depending on the aggregation type u2013 typically u201Csumu201D ). That‟s why we see 1650000 rows transferred but only 110000 rows inserted into the InfoCube.
E-Fact tables and partitioning :
For E-fact tables a customer has the freedom to define the partitioning strategy based on the time dimension. Either month or fiscal year can be used to specify the partitions. The option can be found under u201CExtrasu201D -> u201CDB Performanceu201D when editing an InfoCube in the Administrator Workbench ( transaction RSA1 ). This can only be done as long as the InfoCube is empty and no data was loaded. NetWeaver 7.x offers a re-partitioning tool which allows to change the partitioning for InfoCubes which contain data.
Table partitioning and delete performance:
The main benefit of range table partitioning in SAP BI is the maintenance of huge tables. Especially when it‟s necessary to delete requests the difference might be factor 10, 100, 1000 or even more depending on the amount of data. With SQLServer2000 you found the appropriate delete statements in a ST05 trace for getting rid of a request. Now u2013 with table partitioning activated u2013 a ST05 trace will include the corresponding alter table / switch commands to delete a partition ( see figure 23 and 24 ). What took minutes or hours before now will be done within seconds. To get rid of a partition it‟s necessary to u201Cswitchu201D it out. This is a pure meta data operation and will convert the partition into a normal table which can be dropped. Afterwards a merge command is required to adapt the partition function. In the current implementation this might take some time which is still much less than deleting all the rows. There is a workaround available to avoid moving data during the merge by switching out the next partition too and switch it back in afterwards. But this is not feasible for SAP. The deletion of a request in a F-fact table will automatically delete the corresponding requests in all aggregates which were built on top of this InfoCube. But this works only as long as the u201Ccompression flagu201D ( described under item 4, ) is turned off. Otherwise all aggregates have to be recalculated or completely rebuilt which has a massive performance impact on the whole system. Therefore it‟s recommended to turn the flag off in case requests are deleted on a regular basis.
Figure
Regards
Ram.

Steps for Repartitioning Infocube in BI7

Hi all,
Plaese give me detailed steps for Repartitioning Infocube which is having Data & not having partitions ( Before ) in BI 7.
2. Please provide significance of a) Adding Partitions
b) Merging Partitions
c) Complete Repartitioning Processing Options in the Repartitioning of Infoproviders Screen.
Points will assign.
Thanks & Regards,
Ram.

Hi Ram,
Repartitioning can be useful if you have already loaded data to your InfoCube, and:
1.You did not partition the InfoCube when you created it.
2. You loaded more data into your InfoCube than you had planned when you partitioned it.
3.You did not choose a long enough period of time for partitioning.
4.Some partitions contain no data or little data due to data archiving over a period of time.
Integration
All database providers support this function except DB2 for Linux, UNIX, Windows and MAXDB. For DB2 for Linux, UNIX and Windows, you can use clustering or reclustering instead. For more information, see Clustering .
Features
Merging and Adding Partitions
When you merge and add partitions, InfoCube partitions are either merged at the bottom end of the partitioning schema (merge), or added at the top (split).
Ideally, this operation is only executed for the database catalog. This is the case if all the partitions that you want to merge are empty and no data has been loaded outside of the time period you initially defined. The runtime of the action is only a few minutes.
If there is still data in the partitions you want to merge, or if data has been loaded beyond the time period you initially defined, the system saves the data in a shadow table and then copies it back to the original table. The runtime depends on the amount of data to be copied.
With InfoCubes for non-cumulatives, all markers are either in the bottom partition or top partition of the E fact table. Whether mass data also has to be copied depends on the editing options. For this reason, the partitions of non-cumulative InfoCubes cannot be merged if all of the markers are in the bottom partition. If all of the markers are in the top partition, adding partitions is not permitted. If this is the case, use the Complete Repartitioning editing option.
You can merge and add partitions for aggregates as well as for InfoCubes. Alternatively, you can reactivate all of the aggregates after you have changed the InfoCube. Since this function only changes the DB memory parameters of fact tables, you can continue to use the available aggregates without having to modify them.
SAP recommends that you completely back up the database before you execute this function. This ensures that if an error occurs (for example, during a DB catalog operation), the can restore the system to its previous status.
Complete Partitioning
Complete Partitioning fully converts the fact tables of the InfoCube. The system creates shadow tables with the new partitioning schema and copies all of the data from the original tables into the shadow tables. As soon as the data is copied, the system creates indexes and the original table replaces the shadow table. After the system has successfully completed the partitioning request, both fact tables exist in the original state (shadow table), as well as in the modified state with the new partitioning schema (original table). You can manually delete the shadow tables after repartitioning has been successfully completed to free up the memory. Shadow tables have the namespace /BIC/4F<Name of InfoCube> or /BIC/4E<Name of InfoCube>.
You can only use complete repartitioning for InfoCubes. A heterogeneous state is possible. For example, it is possible to have a partitioned InfoCube with non partitioned aggregates. This does not have an adverse effect on functionality. You can automatically modify all of the active aggregates by reactivating them.
Monitor
You can monitor the repartitioning requests using a monitor. The monitor shows you the current status of the processing steps. When you double-click, the relevant logs appear. The following functions are available in the context menu of the request or editing step:
Delete: You delete the repartitioning request; it no longer appears in the monitor, and you cannot restart. All tables remain in their current state. The InfoCube may be inconsistent.
Reset Request: You reset the repartitioning request. This deletes all the locks for the InfoCube and all its shadow tables.
Reset Step: You reset the canceled editing steps so that they are reset to their original state.
Restart: You restart the repartitioning request in the background. You cannot restart a repartitioning request if it still has status Active (yellow) in the monitor. Check whether the request is still active (transaction SM37) and, if necessary, reset the current editing step before you restart.
Background Information About Copying Data
By default, the system copies a maximum of six processes in parallel. The main process splits dialog processes in the background. These dialog processes each copy small data packages and finish with a COMMIT. If a timeout causes one of these dialog processes to terminate, you can restart the affected copy operations, after you have altered the timeout time. To do this, choose Restart Repartitioning Request.
Background Information About Error Handling
Even if you can restart the individual editing steps, you should not reset the repartitioning request or the individual editing steps without first performing an error analysis.
During repartitioning, the relevant InfoCube and its aggregates are locked against modifying operations (loading data, aggregation, rollup and so on) to avoid inconsistent data. In the initial dialog, you can manually unlock objects. This option is only intended for cases where errors have occurred and should only be used after the logs and datasets have been analyzed.
Transport
Since the metadata in the target system is adjusted without the DB tables being converted when you transport InfoCubes, repartitioned InfoCubes may only be transported when the repartitioning has already taken place in the target system. Otherwise inconsistencies that can only be corrected manually occur in the target system.
Activities
You can access repartitioning in the Data Warehousing Workbench using Administration, or in the context menu of your InfoCube.
You can schedule repartitioning in the background by choosing Initialize. You can monitor the repartitioning requests by choosing Monitor.
Hope this helps
Regards
Karthik

DSO Logical Partitioning

I've seen lots of discussions on Logical Partitioning of InfoCubes, but not a lot on Logical Partitioning of DSO Objects.
Can anyone talk to Logical Partitioning of DSO's or point me to some examples?
Thanks

Kenneth,
Logical partitioning refers to splitting the data into smaller logical chunks by way of design ... for example having two cubes with one cube for data for 2008 and one for 2009 would be an example of logical partitioning.
Similar approaches can be taken for DSO's as well - have separate DSOs one for each country... things like that.
Also please note that this is not the same as physical partitioning - which refers to the usual cube compression etc....

Partitioning & Flexible Updating

Hello Group,
1.It is said that "By partitioning in the database levels we can delete data from the ODS object much more quickly."
How ?
2.How does the query performance improve when we partition a cube ?
3.How does deleting data from the cube gets faster after partitioning ?
4."The Infosouce with flexible updating can contain transaction data & master data but not hierarcies." why ?
5.What is the procedure to delete the data in E-fact table ?
 Kindly answer to the point.
 Kindly help I have an interview
 Vijay

Hi
This is what Partition is which answers ur 1-3 questions
Database (or Physical) Partitioning
1)Database tables are cut into smaller chunks (partitions)2)One logical database table. Transparent for user
3)Available for the following database management systems
4)Range Partitioning: ORACLE, Informix, IBM DB2/390
Hash Partitioning: IBM DB2/UDBYear
Benefits
1)Parallel accesses to partitions
2)Read smaller sets of data
3)Fast Deletion of partitions (DROP PARTITION instead DELETE FROM WHERE)
Automatically Partitioned Database Tables (for Range Partitioning)
1)InfoCube F-Fact table: partitioned by request
2)PSA table: partitioned by request
3)ODS Change Log: similar to PSA table
User Defined Partitioning Criteria (for Range Partitioning)
1)InfoCube E-Fact table
2)Partition Criteria: Time characteristics like month or fiscal period
Note: Both fact tables are extended by the SID of the chosen time characteristic
4) The Infosouce with flexible updating can contain transaction data & master data but not hierarcies." why ?
 Heirarchies also can contain
5) Use this program RSDRD_DELETE_FACTS or completely delete the contents of the data target
hoep it helps
Assign points if usefull
regards
AK

BW Interview Questions 2

Hi,
Here are some BW interview questions. Make sure you have prepared for all the q's before going for an interview.
1) Please describe your experience with BEx (Business Explorer)
A) Rate your level of experience with BEx and the rationale for youre self-rating
B) How many queries have you developed? :
C) How many reports have you written?
D) How many workbooks have you developed?
E) Experience with jump targets (OLTP, use jump target)
F) Describe experience with BW-compatible ETL tools (e.g. Ascential)
2) Describe your experience with 3rd party report tools (Crystal Decisions, Business Objects a plus)
3) Describe your experience with the design and implementation of standard & custom InfoCubes.
1. How many InfoCubes have you implemented from start to end by yourself (not with a team)?
2. Of these Cubes, how many characteristics (including attributes) did the largest one have.
3. How much customization was done on the InfoCubes have you implemented?
4) Describe your experience with requirements definition/gathering.
5) What experience have you had creating Functional and Technical specifications?
6) Describe any testing experience you have:
7) Describe your experience with BW extractors
1. How many standard BW extractors have you implemented?
2. How many custom BW extractors have you implemented?
8) Describe how you have used Excel as a compliment to BEx
A) Describe your level of expertise and the rationale for your self-rating (experience with macros, pivot tables and formatting)
B)
9) Describe experience with ABAP
10) Describe any hands on experience with ASAP Methodology.
11) Identify SAP functional areas (SEM, CRM, etc.) you have experience in. Describe that experience.
12) What is partitioning and what are the benefits of partitioning in an InfoCube?
A) Partitioning is the method of dividing a table (either column wise or row wise) based on the fields available which would enable a quick reference for the intended values of the fields in the table. By partitioning an infocube, the reporting performance is enhanced because it is easier to search in smaller tables. Also table maintenance becomes easier.
13) What does Rollup do?
A) Rollup creates aggregates in an infocube whenever new data is loaded.
14) What are the inputs for an infoset?
A) The inputs for an infoset are ODS objects and InfoObjects (with master data or text).
15) What internally happens when BW objects like Info Object, Info Cube or ODS are created and activated?
A) When an InfoObject, InfoCube or ODS object is created, BW maintains a saved version of that object but does not make it available for use. Once the object is activated, BW creates an active version that is available for use.
16) What is the maximum number of key fields that you can have in an ODS object?
A) 16.
17) What is the specific advantage of LO extraction over LIS extraction?
A) The load performance of LO extraction is better than that of LIS. In LIS two tables are used for delta management that is cumbersome. In LO only one delta queue is used for delta management.
18) What is the importance of 0REQUID?
A) It is the InfoObject for Request id. OREQUID enables BW to distinguish between different data records.
19) Can you add programs in the scheduler?
A) Yes. Through event handling.
20) What is the importance of the table ROIDOCPRMS?
A) It is an IDOC parameter source system. This table contains the details of the data transfer like the source system of the data, data packet size, maximum number of lines in a data packet, etc. The data packet size can be changed through the control parameters option on SBIW i.e., the contents of this table can be changed.
21) What is the importance of 'start routine' in update rules?
A) A Start routine is a user exit that can be executed before the update rule starts to allow more complex computations for a key figure or a characteristic. The start routine has no return value. Its purpose is to execute preliminary calculations and to store them in a global data structure. You can access this structure or table in the other routines.
22) When is IDOC data transfer used?
A) IDOCs are used for communication between logical systems like SAP R/3, R/2 and non-SAP systems using ALE and for communication between an SAP R/3 system and a non-SAP system. In BW, an IDOC is a data container for data exchange between SAP systems or between SAP systems and external systems based on an EDI interface. IDOCs support limited file size of 1000 bytes. So IDOCs are not used when loading data into PSA since data there is more detailed. It is used when the file size is lesser than 1000 bytes.
23) What is partitioning characteristic in CO-PA used for?
A) For easier parallel search and load of data.
24) What is the advantage of BW reporting on CO-PA data compared with directly running the queries on CO-PA?
A) BW has a better performance advantage over reporting in R/3. For a huge amount of data, the R/3 reporting tool is at a serious disadvantage because R/3 is modeled as an OLTP system and is good for transaction processing rather than analytical processing.
25) What is the function of BW statistics cube?
A) BW statistics cube contains the data related to the reporting performance and the data loads of all the InfoCubes in the BW system.
26) When an ODS is in 'overwrite' mode, does uploading the same data again and again create new entries in the change log each time data is uploaded?
A) No.
27) What is the function of 'selective deletion' tab in the manage->contents of an infocube?
A) It allows us to select a particular value of a particular field and delete its contents.
28) When we collapse an infocube, is the consolidated data stored in the same infocubeinfocube? or is it stored in the new
A) Data is stored in the same cube.
29) What is the effect of aggregation on the performance? Are there any negative effects on the performance?
A) Aggregation improves the performance in reporting.
30) What happens when you load transaction data without loading master data?
A) The transaction data gets loaded and the master data fields remain blank.
31) When given a choice between a single infocube and multiple InfoCubes with a multiprovider, what factors does one need to consider before making a decision?
A) One would have to see if the InfoCubes are used individually. If these cubes are often used individually, then it is better to go for a multiprovider with many cubes since the reporting would be faster for an individual cube query rather than for a big cube with lot of data.
32) How many hierarchy levels can be created for a characteristic info object?
A) Maximum of 98 levels.
33) What is open hub service?
A) The open hub service enables you to distribute data from an SAP BW system into external data marts, analytical applications, and other applications. With this, you can ensure controlled distribution using several systems. The central object for the export of data is the Infospoke. Using this, you can define the object from which the data comes and into which target it is transferred. Through the open hub service, SAP BW becomes a hub of an enterprise data warehouse. The distribution of data becomes clear through central monitoring from the distribution status in the BW system.
34) What is the function of 'reconstruction' tab in an infocube?
A) It reconstructs the deleted requests from the infocube. If a request has been deleted and later someone wants the data records of that request to be added to the infocube, one can use the reconstruction tab to add those records. It goes to the PSA and brings the data to the infocube.
35) What are secondary indexes with respect to InfoCubes?
A) Index created in addition to the primary index of the infocube. When you activate a table in the ABAP Dictionary, an index is created on the primary key fields of the table. Further indexes created for the table are called secondary indexes.
36) What is DB connect and where is it used?
A) DB connect is database connecting piece of program. It is used in connecting third party tools with BW for reporting purpose.
37) Can we extract hierarchies from R/3 for CO-PA?
A) No We cannot, NO hierarchies in CO/PA�?.
38) Explain field name for partitioning in CO-PA
A) The CO/PA partitioning is used to decrease package size (eg: company code)
39) What is V3 update method ?
A) It is a program in R/3 source system that schedules batch jobs to update extract structure to data source collectively.
40) Differences between serialized and non-serialized V3 updates
41) What is the common method of finding the tables used in any R/3 extraction
A) By using the transaction LISTSCHEMA we can navigate the tables.
42) Differences between table view and infoset query
A) An InfoSet Query is a query using flat tables.
43) How to load data from one InfoCube to another InfoCube ?
A) Thro DataMarts data can be loaded from one InfoCube to another InfoCube.
44) What is the significance of setup tables in LO extractions ?
A) It adds the Selection Criteria to the LO extraction.
45) Difference between extract structure and datasource
A) In Datasource we define the data from diff source sys,where as in extract struct it contains the replicated data of datasource n where in we can define extract rules, n transfer rules
B) Extract Structure is a record layout of InfoObjects.
C) Extract Structure is created on SAP BW system.
46) What happens internally when Delta is Initialized
47) What is referential integrity mechanism ?
A) Referential integrity is the property that guarantees that values from one column depend on values from another column.This property is enforced through integrity constraints.
48) What is activation of extract structure in LO ?
49) What is the difference between Info IDoc and data IDoc ?
50) What is D-Management in LO ?
A) It is a method used in delta update methods, which is based on change log in LO.
Plz experts.. provide the answers for the questions..
Thanx in advance.
Sunil

Hi,
In my case i dont have an experience in BW. I went straight to academy.It is like i am starting a new career.Are the questions also apply to me .

Partition of Infocube

Similar Messages

Maybe you are looking for