We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE: [sap-basis] Status PRIV in SM50

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by sbavan( Sap Basis)
on 07/26/2009 09:09:00 PM


Hi there,
IN this case, we must know what are the user is exactly doing, is the user creating or generating report, if the user is creating a report the memory would not be very high. If the user is generating a report or doing a search then it will take up some memory.You can do a trace by using the user id and t-code but at the same time the program must be executed. Use ( ST12 ) or you can get a screen shot from ( STAD ) to see where is the problem, for eg :- db time, GUI time, abap programming time. All this steps need to be look into it. then only can analyse the details whether the memory need to upgraded or not.

But in your case i pressume it will be abap programming, but yet to confirm.

I can help you to analyse, if you provide me the screen shot. of the above tcodes. I would also need the screen shot of sm 51 and the sm04 memory consumption the the user when the program is executed. The problem can be simulated in Testing environment provided the sufficent data.

regards,

-Bavan-






From: sap-basis@Groups.ITtoolbox.com
To: samrads@hotmail.com
Date: Fri, 24 Jul 2009 12:29:54 -0400
Subject: RE:[sap-basis] Status PRIV in SM50
We are seeing the same in our Deman Pplanning /sapapo/sdp94 and it is affecting the user performance. We are looking into memory tuning to rsolve it. ME23N could be memory hug depending on criteria used. Your user may use wild card that cold cause reading heavy data volume and causing this issue.
__.____._

Copyright © 2009 CEB Toolbox, Inc. and message author.

Toolbox.com
4343 N. Scottsdale Road
Suite 280
Scottsdale, AZ 85251
In the Spotlight
Get Total Access to the Most Relevant White Paper Research. Visit the White Paper Library at Toolbox for IT.
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language