SAP BW BPS 3.5 Limitations

[former_member186740]

We are setting up a planning area for 90 users with 2000+cost centers and cost elements .

Setting up a environment to budget and forecast with up-to 12 versions of forecasts.

I wanted to understand the performance implications of using BPS for the above planning purpose..

one of them I identified was ...

the planning package closes at around 50000 records and the records are no longer available to be edited .

so if user is working on one record and the package is closed he will no longer be able to edit the same record....

he will have to create another record and then send a delta update ....this is time consuming and not what the users want ....

does any one have a work around for this problem.....

Also please discuss various other limitations of using BPS.

[Former Member · Accepted solution]

Whether a request is closed or not has absolutley no impact on whether a record can be edited or not. Where did you hear this? It is incorrect information.

BPS (or IP) always sends a delta record when an entry is changed (assuming the original entry was saved).

For example, if a record is created with value 10, and then saveet. Subsequently, the value is changed to 15. BPS will write a +5 record with the same characteristic values to the cube. It will do this if the request the data is contained in is open or closed.

[former_member186740 · Accepted solution]

I completely understand what you say ....

But the same record is not available in the planning area ....

eg cost center xx with amount 10 is closed by a package we will have to enter it again

as cost center xx with amount 20 to update the record. and delta updates will be sent to the cube.....

I want to see the record Cost center XX with amount 10 in the planning area after the package is closed....and edit this 10 to 20 without creating a new record....

Please let me know if this is possible .

Thank you for your time.

[Former Member · Accepted solution]

When the record that was previously enterd as 10 is displayed in the planning application, it will show as 10 and be editable.

When the user changes it to 20, a delta record of +10 will be added to the cube.

This is how BPS, IP, and BPC work. It is not a limitation.

If you only want to see 20 in the cube afterwards, then collapse the InfoCube.

in any case, why does it matter? The process is totally transparent to the user. When you run a report, you will se 20.

[former_member186740 · Accepted solution]

When the record that was previously enterd as 10 is displayed in the planning application, it will show as 10 and be editable.

Correct ...but this 10 will be editable and displayed to user in the area only till the infopackage is closed.

user can see this in his reports ...but now he want to see 10 again in planning area and change it to 20 its not possible.

he will have to create a new record and put 20 ...which will send the deltas as you have mentioned.

Thank you for your time..

[Former Member · Accepted solution]

"Correct ...but this 10 will be editable and displayed to user in the area only till the infopackage is closed."

As I wrote in my first post:

"Whether a request is closed or not has absolutley no impact on whether a record can be edited or not. Where did you hear this? It is incorrect information."

Wether or not a combination of characteristic values and key figures is available for input or update on a planning layout has nothing whatsoever to do with the status of the request that particular data resides in.

A record in BW InfoCubes is never updated (either by data loading or by BPS). Records can only be added to InfoCubes. That is their technical nature.

[former_member186740 · Accepted solution]

Hello

In continuation to the above questions I need a clarification on one point.

We have 10 cost center managers with each having auth to 5 different cost centers.

They continue to do the planning in the planning area...

one user has planned for the 5 cost centers for the entire fiscal year....he has around 500 records ........

Each time he opens his planning area he can see these records .....and add new records if necessary ...

My question is now if the planning package closes after the specified limit of 50000 will he continue to see the 500 records in the area ?

If yes , can anyone explain on what basis the records are displayed to the user .....?

[Former Member]

Firstly understand that a Planning package like a Planning Area or Level is just a structure. Planning package is not opened or closed. When you enter data into any of the input layouts a request is created for that InfoCube. This is like any BW data loading request. Only difference is this request will stay open till it gets to say 50000 records. So it is displayed in Yellow and once it gets closed it gets displayed in Green. The request staying open does not affect the records getting stored in the Cube as well as the retrieval of the same records in the layout.

As an experiment change the mode of the cube to dataloading (this will close the open request if any). Then change back to planning mode. Enter a few records. Then you can repeat the above activity of changing modes. Go to manage for the real time infocube that was affected. You will see that the latest recor will have exactly the same number of records that you entered.

If you changed any existing records then you will find that count on the no. of records updated.

Hope it helps. Assign points if this was useful.

Thanks.

Rohit