Planning Sequences and packaging

[Former Member]

Hi all,

I'm executing a planning sequence in a process chain, with packaging. It should write every pachage in the cube, it seems it writes everything at the end of the last package, so I've memory problems because it reaches the limits of the buffer. Am I missing something?

tks all

Mike

[FCI]

Hello Mike,

What type of packaging do you use (Automatic ?) ? Did you try another one ?

Regards,

Fred

[Former Member]

Hi Fred,

thanks for the answer. I tried both ways automatic and manual, but it seems nothing changes.

Mike

[Former Member]

Hello,

It might not be a memory overflow because of teh data but may be due to the number of lock entries created on lock server. If you are getting message RSPLS 091 : "Overloading of lock server for InfoProvider &1 (-> see long text)" then this is due to the memory overflow because of the lock parameter settings regardless of use of packaging, .

In your case you can try by maintaining values under "Lock Attempts" and "Wait Time in Seconds" in RSPLSE transaction. In most cases, the following settings suffice:

"Lock Attempts": 3

"Wait time in Seconds": 5

To maintain these parameters you have to go in Expert mode of transaction RSPLSE. For this first start RSPLSE and then type EXPERT in command window in SAP GUI to activate the modes and NOEXPERT to deactivate it. The system display several new fields in this mode. There is F1 documentation for all of these fields and ther you can maintain the values as suggested above.

Now, test your process chain again.

Regards,

Deepti

[Former Member]

Hi,

thanks Deepti, but I'm getting a more generic error: TSV_TNEW_PAGE_ALLOC_FAILED

The internal table "\CLASS=CL_RSPLS_PLAN_BUFFER\METHOD=READ\DATA=E_T_DATA"

could not be further extended.

It seems with packaging or without pakaging I'm using the same amount of memory.

Mike

[Former Member]

Check the thread and SAP note 552209.

[Former Member]

It seems with packaging it does a big commit of all data at the end, do you think this is normal?

tks all

Mike

[Former Member]

Hi Mike,

please read http://help.sap.com/saphelp_nw70ehp1/helpdata/en/45/946677f8fb0cf2e10000000a114a6b/content.htm on this.

Regards Matthias

[Former Member]

Hi Mike,

please read http://help.sap.com/saphelp_nw70ehp1/helpdata/en/45/946677f8fb0cf2e10000000a114a6b/content.htm on this.

There you can find a section how the data is stored for processing the data in packages.

Regards Matthias

[Former Member]

Hi,

No, that's not the case.

When you don't use packaging then only after the entire planning sequence is executed, system will saves all the data on the database if all the contained functions have been executed without errors.

But, with packaging planning sequence is executed step by step. And system writes the modified data to the database after each step and deletes it from the buffer. Also, for each step you can set whether and how it should be packaged, i.e you can also increase the no. of package in that step. When a step is packaged, the system writes each individual package that was processed without errors to the database.

Hence, packaging is not the reason of memory overflow. You can try either increasing the no. of package in each step or ask your basis team to increase the memory limit for the buffer.

Rgds,

Deepti

[balajee_sivakumar]

Hi,

The actual phenomenon of panning sequence in process chains is as follows,

1. Process Without Packaging

The entire planning sequence is executed. The system only saves all the data on the database when all the contained functions have been executed without errors.

No further settings are required for this option.

2. Process in Packages

The planning sequence is executed step by step. The system writes the modified data to the database after each step and deletes it from the buffer.

For each step you can set whether and how it should be packaged. When a step is packaged, the system writes each individual package that was processed without errors to the data base.

Regards,

Balajee

[Former Member]

Tks all for the answers,

still my sequence (with just one function in it) seem to use the same amount of memory either with or without packaging.

I deactivated the lock but it seems again same memory.

any idea?

tks

Mike

[balajee_sivakumar]

Hi,

Can you please share regarding the number of planning functions in your sequence.

Regards,

Balajee

[Former Member]

Hi,

I've just one planning function in my sequence, it is an old abap BPS function.

Mike

[balajee_sivakumar]

Hi,

I feel that if you have only one function, it doesn't make any difference whether if you use with or with out packaging.

as I had mentioned in my previous post.

But can you share with me regarding the way you are packaging, I mean which packaging type are you using ??

Automatic or configured?

Because baed on the characteristic used for packaging the execution time differs.

Regards,

Balajee

Edited by: balajee sivakumar on Jan 6, 2011 12:47 AM

[Former Member]

Hi Balajee,

tks for your time,

I tried automatic and manual packaging and no packaging either, it seems it is using almost the same amount of memory.

It seems it reads more data than necessary from the cube even if I have very selective filters.

Mike

[Former Member]

Hi,

are you using BPS or BI-IP? For BPS you can try report UPC_BUNDLE_EXECUTE_STEP or UPC_BUNDLE_EXECUTE_STEP_2.

Regards Matthias

[Former Member]

Hi Matthias,

it's BI-IP

Regards,

Mike