WS20000075: work item of 1st release step stays in status In process

Hi All,
I have activated and set up standard flow WS20000075 but the work item of 1st release (PO release strategy with 3 levels) step stays in status In process. The work item for the 2nd and 3rd release step are completed as expected.
What could cause only the work item of the 1st release step to stay In process?
Thanks a lot in advance

Hi,
I cannot see in what field the release code is filled in EKKO.
See here SWEL after 1st release:
And SWEL after 2nd release:
EKKO after 1st release
EKKO after 2nd release
release strat
Release strategy

Similar Messages

WF: Object DECISION Method PROCESS - stays in status in process forever

Dear Friend,
Could you, please, give me any ideas why Workflow Task based on business objects/method DECISION->PROCESS stays in status in process?
It happens after upgrade to ERP2005 from 4.6c. In old version it works perfectly.
Thanks a lot for help.

Hi,
If a Workitem has Status "In Process" then it means it is under execution and it is not completed. however it might get completed and the status is still can be "In Process". The reason for this would be the Workitem might have gone in Deadline monitoring. Check the Workflow Task whether any deadline is assigned or not. I guess it got assigned in your case. And another important thing is there must be a background program that is scheduled which takes care of such deadline monitoring Tasks. Check whether this program is ticked or not in transaction SWU3. So altogether you have to check two things.
hope this helps you.
thanks,
sksingh

Delete Work Item from PO Releaser's Inbox during Workflow

Hi All
How can I delete the previous Work Item that was created in the PO Releaser's Inbox if a PO was changed which re-triggered the PO Release workflow but this time to a different PO Releaser.
The workflow is working correctly, i.e. creating the new release item in the new releaser'd Inbox but not deleting the old Work Item for the previous releaser.
Any idea on how I can accomplish this?
Kind Regards
Utian Goliath

PLease refer the below stuff................create a task and put the code inside the method.This task should be fisrt step in your workflow.
User sets doc to Complete from FBV2 , Complete event triggered and workflow triggered.
Workitem goes to approver .
Now , the user immediately changes doc from FBV2 , sets it to Complete again and workflow triggered
workitem goes to the same approver for the same document.
SAP_WAPI_WORKITEM_TO_OBJECT - Worklist table will giv all parent id's for the object key concatenation of
com code , doc no and fiscal year.
SWP_WORKFLOW_INSTANCE_DELETE - Pass the parent id and will delete the entire instance but not
parent workitem id.
SAP_WAPI_WORKITEM_DELETE - Pass parent id everything will be deleted .( Check_final_state = blank ).
No trace found in SWI14 and SWI2_FREQ.
To remove the previous workitem , create a method in the begining of the workflow , use F.M.
SAP_WAPI_WORKITEM_TO_OBJECT to get the workflow id's and then
SWP_WORKFLOW_INSTANCE_DELETE or SAP_WAPI_WORKITEM_DELETE to delete the previous instance.
data : lt_worklist type table of SWR_WIHDR,
       lw_worklist type SWR_WIHDR,
       lv_objkey type SWOTOBJID-OBJKEY,
       lv_return type sy-subrc,
       lv_id type SWP_HEADER-WF_ID.
concatenate object-key-sourcecompanycode object-key-documentn
object-key-fiscalyear into lv_objkey.
CALL FUNCTION 'SAP_WAPI_WORKITEMS_TO_OBJECT'
EXPORTING
OBJECT_POR                     =
   OBJTYPE                        = 'FIPP'
   OBJKEY                          = lv_objkey
TOP_LEVEL_ITEMS                = 'X'
SELECTION_STATUS_VARIANT       = 0001
TIME                           =
TEXT                           = 'X'
OUTPUT_ONLY_TOP_LEVEL          = ' '
LANGUAGE                       = SY-LANGU
DETERMINE_TASK_FILTER          = 'X'
REMOVED_OBJECTS                = ' '
IMPORTING
   RETURN_CODE                    = lv_return
TABLES
TASK_FILTER                    =
    WORKLIST                       = lt_worklist
MESSAGE_LINES                  =
MESSAGE_STRUCT                 =
   if lt_worklist is not initial.
loop at lt_worklist into lw_worklist.
object-instance = 'X'.
move lw_worklist-wi_id to lv_id.
CALL FUNCTION 'SWP_WORKFLOW_INSTANCE_DELETE'
EXPORTING
    WF_ID                         = lv_id
    DO_COMMIT                     = 'X'
EXCEPTIONS
WORKFLOW_DOES_NOT_EXIST       = 1
OTHERS                        = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
ENDIF.
Second way is to create a fork , and use wait for event step in it with the same event that is triggering the WFL
In the same branch take a process control to end workflow instance.
In the second branch carry out normal processing.
Necessary branch = 1.
So incase the user triggers the event again, a new instance will be created ,
and in the previous instance , the first branch will follow ending the
previous instance and the workitems of other branch will be logically deleted.

Background task stays with status "in process" without creating any error

Hi all,
we created a two step approval workflow for parked documents based on the SAP WF templates WF WS10000051 (WF frame) and WS10000053 (two step approval sub WF). The problem now is, that after the two approvals have been given and the release flag is set the system should post the document. This is done in a background task. This task is started automatically but the status stays at "in process" and the document remains "parked" and not posted.
What we did so far to solve the problem:
1.) Check if shortdump has been created via ST22 --> not the case
2.) Refreshed buffer via SWU_OBUF
3.) Reacticvated/executed task with workitem id from log in SWIA
--> nothing solved the problem so far. Please help!
Thanks in advance. Johannes

Hello Johannes !
              You have asked "What do you mean with populate the value?"
                        Populating means conceiving the variable or container with valid value.In your scenario , with reference to your URL http://img851.imageshack.us/i/wflog2.jpg/ , POSTED_FLAG should be populated with value X.It should not be "Not Set".
                        With reference to your URL http://img717.imageshack.us/i/wfprotocol.jpg/, Set Release Flag step does not sets release flag.
                        It's evident from the URL http://img263.imageshack.us/i/flagreleasesetsw01.jpg/
            The solution for your problem is straight forward : Pass all the export or result parameters of RELEASE step to SET RELEASE FLAG step. Similarly , pass all the export or result parameters of SET RELEASE FLAG step to POST PARKED DOCUMENT STEP.
Answer for question 1 : After successful workflow transportation, it's version changes.Never mind the versions unless either of the versions are inactive or the version you require is inactive.
Answer for question 2 : The user WF-BATCH should have SAP_ALL and SAP_NEW profiles.
Regards,
S.Suresh

Error in Fork Step causing issue in generating next work items

All,
We have ECC 6.0 with the following SP:
SAP_BASIS 700 0012 SAPKB70012 SAP Basis Component
SAP_ABA 700 0012 SAPKA70012 Cross-Application Component
I have this strange issue. In one of my custom workflows, i am using a Fork step with 02/ 02 necessary outcomes. In branch 1, i am sending a mail to a user's e-mail id. In branch 2, i have 3 activity steps for another user. Step 1 is to display an invoice and step 2 is a user decision to apprve/deny this invoice.
I know that during runtime, at the Fork step, the work item for branch 1 and the 1st work item for activity step 1 in branch 2 get generated almost simultaneously(though with some small time difference). This is OK. But the issue is, when the sendmail in branch 1 errors out due to some error, and when step 1 is finished successfully by another user, the work item for 2nd activity step in branch 2 is not getting created.
As i understand, in the Fork, the 2 branches, execution should be independent of each other, that means, the work item creation and execution of branch 1 and 3 steps in branch 2 should be happening independently. But, this doesn't seem to be the case.
I understand when the sendmail in branch failed, the wflow is set to 'Error' Status.But there is already an open workitem for step 1 of branch 2. When this workitem is completed successfully, I expect the work item for 2nd step should get generated.But this is not happening. But, when i restart the whole workflow using SWPR, it generates the witem for 2nd step in branch 2. And still the wflow is in 'Error' status.
When the user finishes the 2nd workitem of branch 2, the next work item for 3rd step is not getting generated. Instead i needed to restart the whole wflow again and this time, it generated the 3rd witem in ranch 2.
To my understanding, when a Fork is there, if i specify 02/02 outcomes necessary, these 2 branches should go in parallel, both creation and execution of workitems, until they are joined. And at this point, if the whole Fork step is successful, then workflow will proceed further with steps below the Fork. Shouldn't this be the case ?
Anybody had similar issue? Pl share your thoughts on this. I'd really appreciate if somebody can clarify whats going on in the above case and how to fix this.
Thank you in advance
Regards,
venu
Edited by: Venugopal Jogi on Jun 10, 2009 5:58 PM

Hi Arghadip,
Thanks for your reply. You said
"When a Workflow goes into error the processing should stop whether it is in same branch or in different.".
If this is correct, then as i explained earlier, when i restart the workflow without fixing the errored branch, then also, the next work item should not be created..Right ? But, it is. I didn't fix the errored branch but simply restarted the workflow. Then it created the witem for 2nd step, in the branch 2 that is not errored.
How can this be, the branch 1 is still in ERROR status only. So, can you pl clarify if something else might be going on here.
Also, fixing the issue is fine. But, the SendMail step in branch 1 is just an information only and per business requirement, this should not be holding up the approval process. And if we don't process the invoice in time, just because of some informational mail errored out, this will not be a feasible solution to the client,Right ? That's the whole reason i am using Fork step, so that they both proceed parallelly (independently).
If step 1 is a pre-requisite for step 2, then it makes sense to fix error in step 1 so that we can proceed with step 2.
Any other thoughts on this.....
Regards,
venu

Additional PR release step while using standard workflow WS20000077

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. Release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the 1st release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise is it possible and how to implement the additional release step. Thanks.

Thanks for your quick response.
I also think about this to keep workflow side untouch by including one additional release code in MM release strategy configuration. Unfortunately material group is item-wise, material group of item 1 may not be the same as item 2 (unless we restrict all items' material group to be identical by user-exit). Otherwise, I'm not sure how to incorporate this into a document level overall release strategy.

Report to get cumulative effort based on child items related to parent work item

We have created a new work item type called 'Release'
Release -> Features -> PBI/Bugs -> Tasks/Test Case
I have requirement to create many reports that has to filtered across the Release work item been created. We usually slice it by Area/Iteration but here the requirement is different.
For ex:
Releases Overview report:
Release name| Owner as AssignedTo| Status Indicator | Completed Work | Remaining Work | Open Impediments
I can fetch all the release work items (Work Items with System_workItemType =Release) w.r.to team project for this report. But for other calculations :
Compute Open Impediments
Find all the child items belong to the parent 'Release work item'
Pick Open Impediments (Work_Item_Count with System_workItemType=Impediment and State = Open) in that list.
Is this possible by querying olap ? Or we need to go for stored procedures for querying warehouse?
please give a fair idea to start with and good resources for learning MDX.
Thanks
Divya

Hi Divya,
Thanks for your post.
To get the Release work items and all linked Impediments, you can try to create the Work item and direct links query, under Filters for lined work items section, set Type of trees = Parent/Child, work item type = Impediments and State = Open. Please refer
to the information in this document:https://msdn.microsoft.com/en-us/library/dd286705.aspx?f=255&MSPPError=-2147217396.
For such a Release Overview report, you need create your custom report. For the MDX resource, please refer to this document:https://technet.microsoft.com/en-us/library/ms144785.aspx?f=255&MSPPError=-2147217396.
Or contact SQL Server Reporting Service experts for the better response
And you can also create the work item report using TFS API.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Please Help me with the Work Item agent to agent forwarding error

hi folks ,
This is the error I am getting when I am trying to forward the work item from agent to agent.
"Work item 000000017188: Method SAP_WAPI_FORWARD_WORKITEM not allowed for type F "
Please Help in this regards. its Urgent.
thanks in advance for your help
Krishna Chaitanya

The F type Workitem cannot be forwarded because it represents Workflow (Also Subworkflow) workitem Id.
You have to find out with workitem which has status W(Dialog Work Item; Represents a Single-Step Task) from SWWWIHEAD table and status should be in process and the TOP_WI_ID should be the value that you are trying to forward.
Thanks
Arghadip

WD for Java and UWL work items (Adobe HCMPF)

Hi Experts,
I am implementing the Adobe forms HCMPF from the HR Administartive Services BP based on the 'old' WebDynrpo for Java. SAP references in SAPnote 1024326 that when the WD Java is preferred over the WD ABAP one can configure the Application Parameter "isEnabled=X" for the Java WD's.
This application parameter works fine for iViews like Start Processes and Search Process. However, the problems come when you open the work item for approving/editing a form that is received in the UWL.
These workitems call the WD application that is defined in ECC. However, they do not call an iView from the PCD but the application directly. Therefore I was not able to configure the Application Parameter "isEnabled=X" for these applications (eg sap.com/paasrformstep).
Can anyone please help and explain how to set the application parameter property for applications that are called directly fron the UWL work items?
Without this we can only start the processes but not contunue them after the workflow has started.
You expertise is greatly appreciated and will be rewarded when helpful!
Regards,
Thomas

Solution found.
Edit the XML UWL configuration to inlcude the application property for the workflow work items in questions.

UWL work items

Hi,
There are UWL work items and when a user selects a workitem to process, UWL opens up a new window when you choose an item.
It should go to the item in same window and when complete take you back to the UWL, where the item completed should no longer display in the list.
Please advice further - Thanks
Regards, Neeta

Hi ,
check the below thread.
download standard uwl configuration xml file and check the property related to newwindow feauture and set it to false.
then it will open in same window rather than new window
check example code in that which used to open in new window
UWL - open item in new window
Koti Reddy

Work item display for step : Deadline Missed

Hi,
Parked invoices for one of the vendor is not triggering the work item in the workflow inbox.
But the status is showing as complete. Appreciate if provide guidance how to analyse the issue.
The message is read as below:
Deadline Missed: Invoice# 5106117758 PO# 4567819 Vendor# 10300
Work item display for step " Deadline Missed: Invoice# 5106117758 PO# 4567819 V " called...
Message no. WL223
Thank you

Hello,
"i looked in SWI1 to see who processed it. But it is not showing any parituclar agent name. "
Maybe nobody has process it, which is why it went overdue and passed the deadline.
If it's a dialog task and it's completed then there must be an agent attached to it.
Look in the workflow builder to see how the deadline is set up for that step. It could be that it just issues a notification.
regards
Rick Bakker
hanabi technology

Work Item - Step History - Message: Reserved work item replaced ??

Hello all,
I am currently trying to understand what went wrong with one of our WF. When I look at the "technical log" of the WF and I select one specific step, I see the following messages under the STEP HISTORY tab:
Dialog work item created - No Errors - JOHN - 06.05.2010 - 16:17:17
Execution started automatically - No Errors - JOHN - 06.05.2010 - 16:17:17
Reserved work item replaced - No Errors - JOHN - 06.05.2010 - 16:19:01
Agent determination for step '0000000001' failed - PAUL - 06.05.2010 - 16:19:11
I am trying to understand what caused the 3rd message (Reserved work item replaced) to be added the log.
Anyone knows the answer ?
PS: I know what caused the RED message about agent determination.
Thanks in advance.
José

Dear PAQUEJO
Could you let me know the root cause or solution for this.
I am also facing the same issue for the last 3 weeks.
Below is the work item step log:
       PI_MDM_ USR               Dialog work item created                 12.01.2011 08:16:53
       Olivia Ye                 Execution started                        12.01.2011 08:19:31
       Olivia Ye                 Reserved work item replaced              12.01.2011 08:20:31
       Olivia Ye                 Execution started                        12.01.2011 10:02:30
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:03:12
       Olivia Ye                 Execution started                        12.01.2011 10:03:43
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:03:50
       Olivia Ye                 Execution started                        12.01.2011 10:04:00
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:12:16
Your help is highly appreciated.
Regards,
Raja Ram.

Forwarding 'Wait Step'work items using SWIA

Hi,
I need to forward work items of one user A to another user B urgently, using SWIA.
The work items are in executed state. This is after a fork step in the workflow, where the executed work item is one branch of the fork.
As these items are executed, we will have to forward the work items that are in ready state.
The work item for the other branch of the fork is in ready state. However this is a wait step, and hence I am not able to forward this item.
Kindly advise as to how should I forward these items.
Best Regards,
Smruthi.

Hi Smruthi,
Dont confuse with the wait for events and dialog work item. There is no direct link between the wait for events and the work item.
Only dialog work items needs the user action and dialog work item's only can be forwarded to other user's.
For this, the work item should have the status of 'Ready'. If the work item has the status 'In process' that means, the user opened the work item and still he didnt take ant action on it.
In this case, using SWIA you can manually change the status as 'Ready' and then you can forward the work item to the other user's.
To forward the work item use the function module 'SAP_WAPI_FORWARD_WORKITEM' or use the SWIA transaction.
Thanks,
Viji.

Need to send work item to mutiple users at top level in PR release strategy

Dear All,
We are using workflow WS20000077 for PR release strategy.
Now the requirement is, at higer level, say at Board of director level, the work item should go to mutiple users and any one can approve/reject the work item. In other words, upto the board of director level , the workflowwill send work item to respective users as defined in release strategy, only at the Board of director level it should send work item to multiple users.
So how to send work item to mutiple users at a particular level in release strategy.
Thanks & Regards,
Fawaz

Hi Fawaz,
Your requirement can be achieved if you use Organisation Plan for agent assignment.
In the plan, you create position for each stage and assign the position ID in the worklfow section of the PR release strategy against the release code in MM.
The work item will goto all the users assigned to that position. this way is very flexible too for future agent change. only change the user assignment to the position.

Change N Step work item text

Hi. We are using the N step workflow with SRM 4.
We have got the workflow working fine and the approval preview is fine.
However, all the approvals have the same text in the inbox "Approve shopping cart from ...... with value .......".
We want the workflow text to contain the approval type from the approval preview.
The text is in the original workflow but it is not passed to the sub workflow and the task that creates the work item in the users inbox.
I could change the task and the binding to pass the description down, but won't that get overwritten by support packs?
Is there any other way? I've tried method SET_APPROVAL_DESCRIPTION in the N step BADI but that does not do anything. It is called but it changes nothing that I can see.
Does anyone know how we can get the step description into the work item text?
Thanks a lot for your help,
Dave.

Hi,
Customer defined workitem is available.
Transaction: PFTC_DIS
Menu: Edit -> Workitem text -> Redefine, Customer Definition
Save.
Transaction: SWU_OBUF, refresh buffer
Regards,
Masa

WS20000075: work item of 1st release step stays in status In process

Similar Messages

Maybe you are looking for