topic Re: con2 long time problem in Application Development and Automation Discussions

con2 long time problem

Former Member — Tue, 25 Aug 2009 08:47:24 GMT

hi,

When I execute the revaluation in the background and with parallel processing the revaluation runs without any problems, however, the update takes a long time to update the revaluation records.

thanks in advance..

Re: con2 long time problem

Former Member — Tue, 25 Aug 2009 10:11:15 GMT

Ferhan Tekin,

Parallel processing helps in parallelizing table reads and internal table manipulation fast. Though for update, an "upd" or "up2" work process in needed, based on whenther it is V1 / V2 update. Based on number of processes of the above type, the update speed is determined.

BR,

Re: con2 long time problem

Former Member — Tue, 25 Aug 2009 10:49:38 GMT

for parallel processing it is recommended to use local update, i.e. switch at the beginning to 'SET UPDATE TASK LOCAL'.

Update task are supposed to save response time, but they create an overhead in processing, in paralllel processing you want optimal throughput, therefore you should save the overhead.

Read documentation for implementation details.

Siegfried

Re: con2 long time problem

Former Member — Tue, 25 Aug 2009 12:19:06 GMT

hi SB

can you give me the sap notes or the document as

" http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4d7a79e11d1950f0000e82de14a/frameset.htm"; ?

thanks

ferhan

Re: con2 long time problem

HermannGahm — Tue, 25 Aug 2009 20:05:52 GMT

Hi Ferhan,

check if your program "revaluation" offers an "update mode" or uses a "call transaction" where the "update mode" can be specified... .

Kind regards,

Hermann

Re: con2 long time problem

Former Member — Wed, 26 Aug 2009 06:18:58 GMT

hi guru,

We have runtime problems (database) for the period-end closing step CON2 , it takes too long and we re unable to close the period.

System conditions re as follows,

Material ledger is active

Variant configuration is used

When we execute CON2 in test run, we dont face with any problem but without test run, in the back ground, it takes more than 48 hours without successful completion.

thanks

ferha