Unable to Open Inbox in SBWP - runtime error

[Former Member]

Hi Gurus,

I have a problem with my inbox - I'm experiencing runtime error (time_out) when opening it. It says 'Time limit exceeded', and 'The program 'SAPFSSO0' has exceeded the maximum permitted runtime without interruption and has therefore been terminated.

Can anyone of the Workflow experts tell me what is the probable cause, and what do you sugggest to solve this and prevent from happening again?

Thanks!

Regards,

Joyreen

[Former Member · Accepted solution]

Hi Joyreen Maceda,

'Time limit exceeded' Is a Time out information and this is not a ERROR, In SAP each and every application will be having its own time limit, if the user exceeds thistime limit then the application will be timedout and you have to start form the begining.

Checks:

1. Check is it happens for all the users.

If yes, then ask the basis team to increase the time limit for SBWP program which will be a background program normally

2. If it happens for a specified user.

Ask the basis team to check the SBWP program for this specified user.

Thanks and Regards

Balaji K.

[Former Member · Accepted solution]

Hi Balaji,

Timeout happens only to my inbox.

If I want to delete messages in my inbox, will I only need to contact Basis so they can do that?

Thanks!

[Former Member · Accepted solution]

Any idea how many workitems would be there in your inbox ?

Go to SWI5 give Type as US and Id as Your user id

select Type of Analysis as "Work Items to be completed" and execute it..

You will get the workitems which are pending for action in your inbox. Are there too many of them ?

Regards,

PR.

[Former Member · Accepted solution]

This may or may not solve your problem but gives you an idea on performance of SBWP.

Check the Note 764707 - Performance in Business Workplace

This note describes the factors that affect the performance in the Business Workplace, and ways in which you can improve the performance:

The performance in the workflow inbox depends on several factors:

1. Use of organizational objects (O, S ...) for tasks

If agent assignment for tasks is controlled using organizational objects, a structural explosion is necessary. Complex organizational structures can mean that the time required to construct the inbox is greater. This is carried out once a day for each user when the user logs on initially, and the information is then buffered. As a result, the initial construction of the inbox takes the most time.

2. Number of work items in the system

The time required for selecting work items for a user increases with the number of work items that exist in the system.

3. Number of work items that are displayed in the workflow inbox or in the subordinate views.

4. Use of dynamic columns

The dynamic columns are filled on a task-specific basis with content that is determined dynamically during runtime. To do this, it is necessary for the system to read the work item container and then to determine the attributes to be displayed, for example, of an business object.

Displaying the dynamic columns greatly affects performance, since the system accesses both the work item container and application tables.

5. Grouping according to contents, content type and sort key

Each work item carries the two container elements WIObject_ID (dominant object) and WIGroup_ID (Grouping characteristic) to its container. Both elements are defined so that an object reference can be included.

Grouping according to content and content type is based on the container element WIObject_ID, and grouping according to sort key is based on WIGroup_ID. For each of these grouping types, the system needs to access the container for each work item to read the object reference. In addition, the system must determine the default attribute of the respective object, which involves accessing the application tables.

6. Showing the columns group object and work item contents

As above, showing the two columns is based on the container elements WIObject_ID and WIGroup_ID. The system determines the values to be shown by reading the work item container and the default attribute of the relevant object.

Solution

1. Detail the assignment of tasks in the organizational model.

2. Archive work items that are no longer needed (see Note 49545).

3. In the Business Workplace, BAdIs are available for the following purposes:

a) WF_BWP_SELECT_FILTER

This BAdI enables you to limit the number of the work items displayed by filtering. It is mainly suited to scenarios where all users are working on the same inventory of work items (for example, call center).

(see Note 765783)

b) WF_BWP_DYN_COLUMN

Hiding the dynamic columns improves performance in the Business Workplace.

If this is not possible, you can implement the BAdI WF_BWP_DYN_COLUMN to determine the values of the dynamic columns directly from the application data. The BAdI is available with Note 848382.

c) WF_BWP_OBJ_ATTRIBUTE

With this BAdI, it is possible to set the default attributes of the dominant object (_WI_Object_ID) and the grouping characteristic (_WI_Group_ID). The default attributes are used for grouping according to content, and grouping according to sort key and for hiding the group object column and work item content.

The BAdI is available with Note 848382.

4. It is also advisable to implement Note 848382 (or one of the corresponding Support Packages) if you do not want to implement either of the BAdIs. The note also contains an optimization that affects the determination of the object references in the container elements WIObject_ID and WIGroup_ID.

Header Data

Regards,

PR.

[Former Member · Accepted solution]

Hi PR,

Thank you for your comprehensive answer, I'll try all of your recommendations.

[Former Member · Accepted solution]

I just pasted what ever is mentioned in the Note becoz some might not have access to Notes.

Hope your problem will get resolved soon...

Regards,

PR.

[Jocelyn_Dart]

Hi Joyreen,

The probable cause is people not doing their work! 😞

This happens a lot in dev and qa systems where no-one cleans up, and also where people have left the ALE/IDOC error workflows turned on but assigned them to General Task so everyone is getting work that is not relevant to them.

Try checking the inbox content using transaction SWI5 and Work items to be completed option to see what is clogging up the inbox.

And then perhaps use transaction SWIA and its menu options to mass select and logically delete the unwanted work.

Regards

Jocelyn

P.s. If this is production then you also want to check the SAP Notes on http://service.sap.com with keywords SBWP Performance  - there are a couple around improving the inbox performance. But I would still recommend checking its not self-inflicted by the relevant user first, especially if the user is you... 😉

[Former Member]

Hi Jocelyn,

For all users we are unable to go into transaction SBWP or run SWI5 for a particular user both result in memory dump.

After using SWIA with Status READY, and a small Creation Date period we noticed all tasks were IDOC related.

Transaction SWIA allows for mass selection "Logically Delete" but NOT "Complete Manually"

I would prefer to "Complete Manually" and then archive the work items.

Is there a report to "Complete Manually" workitems?

Cheers,

Gareth

[Jocelyn_Dart]

hi Gareth no there is no standard report but you could write your own using the equivalent SAP_WAPI_ADM_... function module. That's why these workflow API functions are provided.

[Former Member]

Hi Jocelyn,

Thanks for the reply I noticved the "Logically Delete" is actually "Cancel", my bad, not a workflow admin.

So I am happy I have managed to "Logically Delete" over 2000000 work Items Idoc related and We are able to get into SBWP again, crazy stuff.

Kind Regards,

[Former Member]

Hi joyreen,

Lets make it simple..

Go to SMICM - Services -  SMTP - Change (Increase the Alive time and Max.Processing time).

It worked for me.

- Paroor

[Former Member]

hi,

r u running a workflow first in SWDD if yes, pls check the workflow log details

or Try TCODE SO01.

try to find if there any background process available to u when u are accessing your INBOX.

[Former Member]

Are you accessing Inbox through Portal ?

Is this happening becoz of any upgrade ?

In Portal

Check the "Display Connection Status" to see if there are any errors..

Edited: I'm sorry i didn't check the subject carefully.. Its SBWP thru which you are accessing inbox.

Lets wait for Experts answers..

Regards,

PR.

Edited by: Pathanjali Reddy on Feb 12, 2009 9:30 AM