Workflow Restart

Hello,
We are facing a problem with workflow approval.
Once Shopping cart is available in the approvers inbox If approver is trying to save the shopping cart instead of approving it entire workflow getting restarted.
Here I am explaining the problem we are facing:
For example.
1.Shopping cart ordered.
2.It contains approvers list : A,B,C,D.
3.A & B approved the SC by clicking on right arrow(green color icon)
4.Now,it's in C's approval inbox, if C is trying to save the SC(by clicking on the sc description and save), the entire workflow is getting restarted. That means again this SC will be waiting for A and B's approval.
Could anybody suggest the proper approach to resolve the issue.
Any hint greatly appreciated.
Thanks,
kanaka

Hello kanaka,
Please check the BBP_WFL_SECURITY attribute value? Goto PFCG transaction and display the manager role then goto personalization tab.
Regards,
Masa

Similar Messages

Prevent automatic workflow restart after error on an interface

Hi, i've got an IDOC-XI-SOAP interface that sends large xml's.
It causes me constants time-outs because, the reciever interface, doesn't send the response until finish processing (more than 3 minutes per IDOC).
I need 2 things to solve this issue.
1- Change the time-out for this particular interface
2- Cancel the automatic workflow restart after error on this particular interface
Thanks for your time,
Roberto

RSXMB_RESTART_MESSAGES program when schedueld in BG restarts failed messages. Hence you can cancel this process. But it will affect other interfaces also.
http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/content.htm
I have 1 more Question for you. Are you usigna BPM for IDOC --> XI -- >SOAP?? B'cos IDOCS are aysnc in nature & you are talking about waiting for SOAP response from your receiver.
-SM

Error coming out of Workflow restart - Error:OBJECTS_OBJREF_NOT_ASSIGNED_NO

Hi all,
After restarting the workflow through SWPR we are getting an error message as per mentioned below.
Error coming out of Workflow restart - Error:OBJECTS_OBJREF_NOT_ASSIGNED_NO.
Kindly suggest what can be the possibility of the error. I scehduled the SWPR program in the background and passed some workflows and getting this error message in the background job. Kindly suggest.
Thanks,
Neslin.

I think you need to analyse the Workflow log and then try to restart. I think you might have to change the container element value in order to remove the error. Please check and act accordingly.
Thanks
Arghadip

ZBUS2009 .significantlyChanged Workflow Restarts

Hi All,
BUS2009 implementation uses event significantlyChanged.
I would prefer that any change restarts the workflow.
The root of the problem is a price change. We would prefer if the price is changed the WF is restarted rather than having to move between valuation tresholds defined in our release strategy's.
Is this possible to configure? I have checked SPRO and came up empty.
I was able to manipultate WFL security in SRM for BOR BUS2121, is there anything similar in ERP 6.0?
Thank you,
Will
Edited by: Bill Conlon on Dec 10, 2010 7:02 AM

Ha. Sorry Rick, indeed it is an event. I guess we need to find out where the even is raised and change the conditions... meaning changing a standard program probably. That will not be possible. I guess I will need to post in a diffeerent forum.
Cheers,
Will

Workflow Restart Error from transaction SWPR

Hi workflow Gurus,
I am facing problem restarting workflow from transaction SWPR. Instead of restarting workflow I am getting an error message as unable to start subflow (ID: XYZ, node: abc).
How can I restart the workflow?
Regards,
Abhishek.

The problem wad caused by mistake in workflow template WS75100021. After task 'Create test log' there is a loop. The end condition of the loop is 'test log is Submitted or Validated'. But the test log can have also status 'Closed' (The tester created the test log and close it immediately). It cause endless loop.
You can proceed following manual steps.
1. Go to transaction SWDD (Workflow Builder).
2. Open workflow template WS75100021.
3. Open loop number 000177
4. Change the condition this way
&FOPC_CASEL.STATUS& = IFO09 or
&FOPC_CASEL.STATUS& = IFO10 or
&FOPC_CASEL.STATUS& = IFO07
5. Activate the workflow template
if it helpful rewards points are appreciated

Workflow restart after logical delete..??

Hi All
Is there any way to restart workflows after a logical delete is performed..?? If we can do it, please describe the procedure.
Thanks
Deepak

Hi Arghadip
Thanks for the quick reply. I tried to see the tasks using the SWUS transaction, however when i executed the transaction with the WF number which was logically deleted; I got an error message - "No task available with the specified number".
How do i deal with this now..?? It'll be great if you can elaborate more on this process.
Thanks
Deepak

Invoice Workflow restart on year change

Hi,
on year change all the invoices of the previous year and their workflows (Invoice verification) are closed and new invoices are created with the same data of the old ones, but in the new fiscal year. I need to know if there's a standard mechanism that reopens workflows and brings them in the same state of the old ones, withe the same approval tasks already executed.
Could anyone help me please?
Thanks in advance!!!

>
Mike Pokraka wrote:
> I had a look, the note states:
> "+By implementing the attached enhancement, the respective workflows are no longer deleted and created again, but transferred. The prerequisite for this solution is that the necessary enhancements regarding the workflow base (see related notes) have been installed. As of Release 3.1I, you need only to run the attached report (not in the standard SAP system)."
>
> In other words: implement the note, run the report. Then do your fiscal year change and it should transfer all the existing workflows. I still suggest you test it thoroughly.
>
> Cheers,
> Mike
You suggested to test it and before you said you did quite a bit of testing to get it right. Why? What could go wrong?
Thanks
francesco

Change or Restart Workflow and Skip to Workflow

You have the option in server settings to "Restart current workflow for the selected projects", with the choices of skipping to current workflow stage or to a particular workflow stage. Using a new 2013 project server workflow neither of these
choices work. The project in each case is returned to the very first workflow stage.
Is this a bug or badly designed workflow?
Is this also the case with legacy 2010 workflows?
rgds
Mike
Mike Mahoney

Mike,
Thanks to John on the Product Team, I think I can explain what is going on.
I am going to assume you have a workflow similar to the one below? Some simple logic, a wait event and a transition or some type.
As the workflow progresses in the above case, it will log a message out, then wait for the submit button to be pressed before transitioning. If you try to use the Change / Restart workflow function and choose Restart > Skip to Stage 3, what
you will see is the workflow restart, log Stage 1 to the history list, and then wait for input. There is no skipping through as the workflow is waiting for the event.
The new workflows, whilst allowing looping etc, are essentially still sequential in nature, so to skip though the various stages, they need to start at the beginning and then progress through the stages depending on the logic in the stage transitions.
Just like in 2010, to get something to progress, you need to introduce some special 'Skip to Stage' logic (for want of a better phrase), with this logic, you can tell the workflow 'If the workflow is being run normally, or restarts the workflow and includes
this stage' execute the actions within. This is achieved by using the 'Include Stage' condition I mentioned in a post above. In the example below, I have wrapped the logging and the Wait for submitted event in an 'Include Stage' action (and added
some extra logging)
Now when this workflow runs normally, it will go through and execute everything, including the bits inside the 'Include Stage' action because the workflow was started normally (as in the name).
However, if I choose to restart > Skip to Stage 3 for instance, the workflow will realise it is in 'Skip to Stage' mode and not execute anything in the 'Include Stage' action as the workflow is not being run normally, nor is that stage included (we
are skipping to Stage 3). As the Wait for Submit is not executed, the workflow will not wait for the submit button to be pressed and progress without issue to the desired stage. From a logging perspective, you should see something like 'Stage 1 > Leaving
Stage 1 > Stage 2 > Leaving Stage 2 > Stage 3 > Included Stage 3.
It took some time, but I hope that explains what your seeing. If it doesn't, well it does give a good overview of how to use Skip to Stage logic in 2013 workflows.
Alex Burton
www.epmsource.com |
Twitter
Project Server TechCenter |
Project Developer Center |
Project Server Help | Project Product Page

Restart Workflow after Dump

Hello,
How to restart the the workflow after dump. I know the t-code SWPC. But the workflow is not displaying in this transaction.
Will i have to delete it logically and restart with reference.
Note: It has a subworkflow.
Thanks in advance,
Bikash.

Please follow the following links
Workflow Restart After Error - SAP Business Workflow - SAP Library
http://help.sap.com/saphelp_nw70/helpdata/en/f4/84322acb0211d1950d0000e82dec10/frameset.htm
regards,
Modak

Process-controlled workflow hang due to dump

Hi all,
due to a temporary dump in an SRM 7 system, some document-related workflows are stucked... in other terms, these workflow processes have been started, the the dump occoured and by now, they seems to be stucked in "in process" state.
Tecnically, these are not workflow in error, so SWI2_DIAG is not helpful.
We'd like to unlock this situation and -eventually- restart the workflow process. How can we do it?
Thanks in advance for your help and support.
edit: system dump is now solved, which means, triggering the same workflow process will result in a success.
Edited by: Matteo Montalto on Jun 30, 2011 4:34 PM

Ok. There used to be OSS Note 1458380 - Process Controlled Workflow Restart Program, if the document is in "Awaiting Approval" Status.
Or do the manual restart by using tcode SWUE (Event trigger)
Object Category - ABAP Class
Object Type - /SAPSRM/CL_WF_PDO_SC
Event - READY_FOR_WORKFLOW
Object Key - <DOCUMENT_GUID>
Event Parameter - <SC Creator User ID>
and Click "Create Event" button
Use SWI1 to check whether the event is created and see whether the document is submitted for workflow triggering or use SWI6 to check for that SC document

Issue in N level workflow of shopping cart

Hi all,
SRM5.0 and ECC5, using ECS scenario
We are using the N level workflow ( SC approval workflow and not item level workflow) with the BADI for determining the approvers of the shopping cart.
The following are issues faced during rejection:
1. When the 1st approver rejects some of the line items and approves others, The SC is sent back to the requester or. the requester accepts the changes, the SC instead of going to the next level of approvers gets approved.
I have debugged and found that the actual index is set to 2 and the next level of approvers are determined correctly in the BADI, once it is out of the BADI, something happens and the SC is approved and it doesn't go for approval.
2. When the 1st approver approves all the line items and the 2nd approver does a partial rejection, the SC is sent back to the requester and once the requester accepts the changes, the workflow restarts and the approvers are redetermined again.
For the 2nd issue, if its a standard process, Can onyone provide me with a document or a OSS note which can be used for substantiating it. Does this behavior correspond to the back and forth process of N level workflow?
Thanks and Regards
Kishan

Hi Munna,
The code just determines the approvers for each level, this works fine when I debug but it changes after the control comes out of the N level BADI.
Is there any other check which I need to do?
Regards
Kishan

Can we debug a workflow

Hi All,
I wish to know can we debug a workflow. If yes then how?
Also if i want to know how the flow is going for the business process in question. I mean if it is stuck some where, then what is the way for it?
Thanks in advance.
Regards,
Neha

Hi Neha,
Yes you can debug the WF to check the LOG in terms of Graphical Display and Technical details..!!
Use the following transaction:-
1> SWE4/SWELS -> EVENT TRACE ON/OFF (Switch On the Event Trace)
2> SWEL -> DISPLAY EVENT TRACE
3> SWUD -> WF DIAGNOSTICS
4> SWPR -> WORKFLOW RESTART AFTER ERROR
Enter the WF Number and Click on the LOG Icon.
There you can see the Graphical Log of the WF to know where the WF is stuck.
And You can also check the Technical Details of the WF there, to find which WF Container has what value.
Let me know if you need any help on this.
Regards,
Kanika

Behaviour of BADI /SAPSRM/BD_WF_PROCESS_RESTART in workflow

Dear SAP gurus,
We're encountering the same issue as in post SRM 7.0 PC Workflow - Restart BADI behaviour /SAPSRM/BD_WF_PROCESS_RESTART
We observe that the restart workflow does triggered twice, and in the second run, there is no difference anymore between the one being processed and the one in the database. As there is no difference anymore we cannot know in which case we should restart and which case we should NOT restart (the requirement is to restart ONLY if quantity is changed).
As from the previous post, the sample coding provided by Bharatan is not working as if we write like he suggest:
DATA:
Internal Table to hold Shopping Cart Item details ...
lt_item_detail TYPE bbpt_pd_sc_item_d,
Internal Table to hold Shopping Cart Item Master table details ...
lt_PDIGP_master TYPE BBP_PDIGP,
Work Area to hold Shopping Cart Item details ...
lt_item_detail_line LIKE LINE OF lt_item_detail,
Work Area to hold shopping cart details ...
lwa_sc_header TYPE bbp_pds_sc_header_d.
Fetch Shopping Cart Item details ...
CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
EXPORTING
i_guid = is_document-document_guid
i_with_itemdata = 'X'
IMPORTING
e_header = lwa_sc_header
TABLES
e_item = lt_item_detail.
Loop at lt_item_detail into lt_item_detail_line.
SELECT *
from BBP_PDIGP into lt_PDIGP_master
Where GUID = lt_item_detail_line-GUID.
ENDSELECT.
IF lt_item_detail_line-QUANTITY GT lt_PDIGP_master-QUANTITY.
EV_RESTART = ''.
ELSE.
EV_RESTART = 'X'.
ENDIF.
ENDLOOP.
There will be NO difference at all between lt_item_detail_line-QUANTITY and lt_PDIGP_master-QUANTITY --> as apparently in the second run of BADI restart, SAP already update the data into table BBP_PDIGP
Can anyone shed light on this matter?
Best regards,
John

We adapt our coding to the observed behaviour. In the first run, we export the data to memory id which then will be imported in the second run.

AD-hoc approver n step item level shopping cart workflow

Hi
We are on latest version of SRM and using n step item level SC approval workflow.
The scenario goes like this:
-     Requester creates shopping cart and workflow goes for two step approval.
-     In the approval preview the requester is able to see both levels of approvers, which is correct.
-     Requester now selects second level approver and replaces him with a ad-hoc approver. WE DO NOT WANT THIS. Requester should NOT be able to replace an approver determined by approval badi. However should be able to extend approval step with ad-hoc approver say third level approver a ad-hoc approver. Also he should be able to change AD-HOC approvers ONLY.
Thanks
Joe

Jo,
You may be able to achieve it in the BADI BBP_WFL_SECUR_BADI .
You can use the Business Add-In (BAdI) BBP_WFL_SECUR_BADI to determine whether
A shopping cart can be changed during the approval process
The approval workflow restarts when changes are made to the document
A reviewer/approver can be added or changedThese are the call scenarios (see import parameter SCENARIO).
Regards,
Suren

Problem in workflow trigger

Hi,
I was trying to create a pretty simple workflow for "Sales Order Change". Whenever a sales order is changed, my workflow should get triggered and I should receive a workitem in my sap inbox displaying the salesorder number getting modified.
Object Type used : BUS2032
Start Event used : Changed
Task Method used : Display
But even after changing a sales order I'm not getting any workitem in my SAP Inbox. I've also checked the tcode "SWUD".
If I'm executing "Determine Instances for Task", it has no records inside.
If I'm executing "Work Item queue (TRFC Log)", it shows the records, each time I've changed the sales order. And
each record shows an error as "Syntax error in program CL_SWF_RUN_WIM_LOCAL".
I believe the workflow is fine.
Could you please help me out in solving this problem. If you want any other detail please let me know.
Thanks and Regards,
Pritam Mohanty.

Hi Pritam,
Your Query seems still un-answered after a Long-Interval also.
This could probably provide a Solution for you:-
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow%252bscenario
This is the PO Scenario similar to your Sales Order Scenario.
/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
You can also Debug the WF to know where it has Stuck:-
Use the following transaction:-
1> SWE4/SWELS -> EVENT TRACE ON/OFF (Switch On the Event Trace)
2> SWEL -> DISPLAY EVENT TRACE
3> SWUD -> WF DIAGNOSTICS
4> SWPR -> WORKFLOW RESTART AFTER ERROR
Enter the WF Number and Click on the LOG Icon.
There you can see the Graphical Log of the WF to know where the WF is stuck.
And You can also check the Technical Details of the WF there, to find which WF Container has what value.
Check on the following points as well:-
1> WF is activated or not.
2> what are the start conditions and event for the WF.
3> Binding between the WF container and Event Containers - should be Active.
4> Agent Assigned to the Workitem that should not be a background process.
5> Event Linkage in Start Conditions of the WF are active or not.
6> check the WF log, to determine where the WF is stuck
Kindly check the RFC Settings in SWU3. All should be green ticks. If you face any problem with this, contact your BASIS Team..!!
Let me know if you are still stuck anywhere..!!
Regards,
Kanika

Workflow Restart

Similar Messages

Maybe you are looking for