Problem in SOST

[Former Member]

Hi Friends,

When I execute the Tcode SOST.It is taking long time to execute.

Any Suggestions.

Regards,

Sapient

[former_member184112 · Accepted solution]

Hi,

Select Send Status and Select Sent boxes.

And Execute.Everytime should be in tick marks in Sent boxe

Go to Utilities ---> Start Send Process ---> go to Details Button ---> Give package size

Thanks and Regards,

Prabhakar Dharmala

[KjetilKilhavn · Accepted solution]

This is new information for me. You say you will get better performance by increasing the number of entries displayed when you enter the transaction.

That is indeed interesting. I wonder how they manage that.

[former_member184112 · Accepted solution]

Hi Kjetil..Thank you,

Hi,

Go to Active & Scheduled Send Jobs ---> Select on "Create Button"(But this not for Creation this for Schedule job)Select Schedule Job for INT --> in Job Values give Start Immed / Period 2 Min..

Thanks and Regards,

Prabhakar Dharmala

[KjetilKilhavn · Accepted solution]

1: I don't understand why frequency of sending should improve performance of SOST.

2: I still don't understand how making SOST display more entries makes it faster.

After all, the original question was about how to reduce the time it takes from you start transaction code SOST until it displays the initial result.

[Former Member · Accepted solution]

Hi Guys,

As per Kjetil sugggestion i disabled the sent check but still my problem is not solved.It is fast if there are no objects to be sent.If there are some objects waiting in the Queue it is taking more time(Even there is a single object).

Do we have to apply some notes to increase the performance.Kindly Clarify

I am working on SAP ECC 5.0 with BASIS 640

Regards,

Sapient

[pokrakam · Accepted solution]

Hello sapient (if that is your <a href="/people/eddy.declercq/blog/2006/04/21/from-the-grumpy-old-man-autor-anonim-model-necunoscut name</a>),

Have your basis team set up SapOffice reorganisation?

If not then everything that's sent will stay in SOST for evermore, be completely useless and slow things down. Try selecting a weekday a few months/years ago to see if anything gets purged. If you find stuff that old that has already been sent then talk to basis to look after SapOffice properly.

Hope that helps,

Mike

[KjetilKilhavn · Accepted solution]

Ahh... your memory must be better than mine, Mike

I have had to do such reorganization myself, I think back in those days the problem was a table called ADRVP, but I had forgotten about that possibility.

[pokrakam · Accepted solution]

Nope nothing to do with memory, I just happen to be sitting at a client working with Basis to clear out 60GB of rubbish from SapOffice as a bit of distraction from the usual Workflow stuff

The killer tables are SOC3 or SOFFCONT1, depending on whether you have an external knowledge provider or not.

[Jakn · Accepted solution]

The main reason for slow SOST startup is usually large SAPoffice tables (SOFFCONT1, SOC3, ADRVP). Regular SAPoffice reorganization (e.g. RSBCS_REORG / SARA – SAP_BCS) should be scheduled by Basis. After cleanup, SOST performance improves significantly.