Here is another cool example of copying from one Planning Area to another

(using Multi-Planning Area, of course) - from a granular level to a rolled up aggregated

level:

Copying with Automatic Summarization

You want to copy the transaction data from

planning area G1 into area G2. Both areas contain the same key figures. Whereas the independent characteristics article and

article group are in G1, G2 only contains the characteristic article group. For this reason, the breakdown according to

individual articles will inevitably be lost for the data to be copied to G2 – the data is automatically aggregated. To

achieve this, you create the copy function in the context of a planning level, which only contains the characteristic article

group. Therefore, you require the following objects in all:

Again, from the SAP Help - two important points to remember:

1. In a multi-planning area, you can only define

selection conditions for characteristics which occur in all basic planning areas of the multi-planning area. These conditions

are used when reading data in all involved basic planning areas. Key figures and characteristic values, which are not

contained in all basic planning areas, are included in the multi-planning area with the initial value.

Ok.. sorry guys. .today I am going through the BPS and BW documentation to get the finer

stuff.. and want to record things that I thing are cool and useful in the long run from the SAP Help. Please leave your

comments on this topic also - whoever has used DATA SLICES extensively!

When you use data slices, the following

rules apply:

If no data slice is defined for a planning area, you can update data for any characteristic value

combination.

Here is another useful

verbiage from the SAP Help on the situations when you can change the Info Cube or the RFC destination in the Planning

Area:

You use an existing InfoCube as reference for a new InfoCube, which you add further characteristics

and key figures to. You copy the planning area, which is connected to the reference InfoCube and assign the new InfoCube to

the new planning area. In this way, you can use all the objects, which were available in the original planning area, in the

new planning area without further Customizing effort. You also have the possibility to use the additional characteristics and

key figures.

Transactional Infocubes

are used for SEM.. and are meant for Read. Here is the documentation from SAP Help to convert a standard cube into

transactional cube when it has data:

Conversion with the Loss of Transaction Data

If the standard InfoCube already contains transaction

data but you no longer need it (for example, test data from the implementation phase of the system), you proceed as

follows: