cancel
Showing results for 
Search instead for 
Did you mean: 

Saving one layout in a workbook instead of the entire workbook

Former Member
0 Kudos

Hi Guys,

We are using BEX workbook layouts for data collection. We have multile layouts in a workbook. We are facing a performance issue with regard to SAVE_AREA in the command button. If we do a SAVE_AREA, the workbook tries to save the data in all the layouts in the workbook which takes about a minute to save becasue of the data volume.

We are trying to do save specific to each layout. For this we were think of using a planning function to do the save which runs of the same aggregation/filter of the layout. In BPS we use to have API_SEMSAVE_DATA to save the data in the buffer. Do we have anything similar to this in IP.

Regards

Ruban

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ruban,

BI-IP is designed for "planning on the fly". That means you can plan in different layout without saving data. You can see your changes in the layout immediately and play around with the figure as long as you want. All changed data is internally stored. Finally when you save the data the whole area is saved. So what you want is against the philosphie of BI-IP. I would try to restrict the amount of data or use less queries/layouts in your workbook.

Hope this helps

Matthias

former_member93896
Active Contributor
0 Kudos

Hi Ruban,

Matthias already made a good point. You also have to understand that typically the data in the various planning layouts are related for example one layout might show detailed data that is then shown in an aggregated view in another layout. It would not be possible to save just one part and not the other without causing inconsistencies.

If the data in your planning layouts is not related, then why is it in one big workbook? Maybe you can split it into a few smaller workbooks.

Finally, saving all data is not the real problem, right? It's the runtime of the save! Therefore you/we need to investigate why it's taking so long in your case and then see how we can reduce the runtime. Please open a customer message with a reproducible example.

Regards,

Marc

SAP NetWeaver RIG

Former Member
0 Kudos

Marc / Mathias,

Thank you for the reponse. I understand your views. We have already split the layouts into multiple workbooks but since the Orgainzation structure is such that we cannot reduce any further. The users do not want to open multiple workbooks to enter their plan data. We have P&L Planning workbook which has 10 layouts such Revenue planning, Expense, Outside Services , COGS and so on. Currently, if they want to change a number in revenue, the data save takes a lot of time and it is trying to save the workbook. If we have just one layout, it takes about 8 seconds but the entire workbook takes 60 seconds. We have tried to do the regular cube optimization functions such as compression, indexing etc but not much of improvement.

We were thinking of putting a save button which will just save the layout instead of the workbook and the summary sheet will have the SAVE_AREA which will save the entire workbook data.

I will try to open a customer message and let you know.

Thank You

Ruban