Unable to Open Inbox in SBWP - runtime error

Question

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

Answer 1

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.