cancel
Showing results for 
Search instead for 
Did you mean: 

entry in SOST not consisting of workitem id of the task

puneet_gupta1
Explorer
0 Kudos

Hello Experts,

          We r upgrading from 4.7 to ECC 6.0. The process works fine in 4.7 but not in ECC 6.0.

           A workflow consists of 1st step as user decision followed by several steps. When it is executed from a FM, WF gets triggered.

           In 4.7, there r 2 entries generated in SOST. Both the entries point to the work item id of the task ie the user decision step. The workflow is seen in ready state. The task/user decision step is classified as general task. So another user can also login and exceute the task ie approve and reject the decision. This is fine

In 6.0 this doesn not happen. Only single entry is created in SOST tcode, which consists of the workitem id of the workflow and not of the task / user decision step as a result when any other user tries to login. As a result, he faces an error "The workflow cannot be restarted in started mode".

After analysis, i found the entry in SOST is faulty or it should consist of the workitem id of the task and not of the workflow.

But i do not know how to correct the entry in SOST or what amendment should be made in SAP workflow.

Please help me with this. this is an urgent issue and needs to be solved asap.

Any help is appreciated. Please let me know if any details need to be furnished in order to understand the scenario.

Regards

Puneet

meetupuneet@gmail.com

Accepted Solutions (0)

Answers (2)

Answers (2)

puneet_gupta1
Explorer
0 Kudos

The notification to the agent consisted of the workitem of the workflow instead of the task and hence the agent could not execute the work item. The reason: when the workflow gets called using sap_wapi_start_workflow in ECC6.0 with do_commit as space, during runtime the table SWWWIHEAD table is not getting populated and the custom code is trying to find out the workitem with type W and it is not present in the table of the related workitems. when the workflow is called with do_commit as X, then the SWWWIHEAD table is getting populated at run time and hence the FM sw_get_related_workitem  is able to find workitem with type W.

This workitem as then inserted in the notification as attachement and hence the user is able to execute the workitem.

Thanks for the help. good learning !

Puneet

former_member185167
Active Contributor
0 Kudos

Hello,

Are you sure you mean SOST? That has to do with emails.

regards

Rick Bakker / hanabi technology