cancel
Showing results for 
Search instead for 
Did you mean: 

FM workflow is restarting

Former Member
0 Kudos

Hi.

I have implemented a workflow for funds reservartion approval (it's a copy of standard workflow WS50000016) with triggering events FMRE-CREATED and FMRE-CHANGED. Approval procedure is working fine when document is created (transaction FMX1) or changed (transaction FMX2).

A funds reservation document has a Purchase Requisition as subsequent document. Problem is: when PR is modified (transaction ME52N) system triggers again the event FMRE-CHANGED and funds reservartion document goes to approval procedure again. This is in production system; QAS works fine.

Any idea in how to evoid this behavior? Thanks for any help.

Kind regards.

Juan

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Problem resolved implementing a check function module in event type linkage.

Regards.

former_member185167
Active Contributor
0 Kudos

Hello,

Check that the transports to Production had no errors and they were done in the same order as to QA.

Is there a start condition missing or deactivated (SWB_COND)?

Does QA have an activated link in SWE2 between FMRE-CHANGED and the workflow?

Has ME52N been changed in QA and that transport didn't make it to Production?

regards

Rick Bakker

Hanabi Technology

Former Member
0 Kudos

Hi Rick, thanks for your answer.

As I mentioned in last answer, current problem is after an upgrade from 4.7c to ECC 6.0.

There's not any start condition for workflow.

In both systems (QA and Production) there are activated links in SWE2 between FMRE-CHANGED and FMRE-CREATED and the workflow.

MM consultant ensures me that there's no change in ME52N in QA.

Any other idea?

Kind regards.

Juan

former_member185167
Active Contributor
0 Kudos

Hello,

If ME52N is creating an event in PROD but not QA, then I can't think of any alternative other than that ME52N is different (given that there's no start condition).

Try to confirm that ME52N is creating an event in PROD by turning on the event trace (SWELS) for a while.

Also, save a change in ME52N in QA and step through in the debugger, you may find a place where the event creation has been switched off.

regards

Rick Bakker

Hanabi Technology

surjith_kumar
Active Contributor
0 Kudos

Hi,

1) Compare the PR SPRO Configuration in DEV & QA

2) Check the Transport Request Moved in Sequence

To Restart the Workitem Use the FM SAP_WAPI_ADM_WORKFLOW_RESTART

Regards,

Surjith

Edited by: surjith kumar on Jun 2, 2009 11:10 PM

Former Member
0 Kudos

Hi Surgith, thanks for your answer.

1) SPRO Configuration is the same in both systems.

2) There's not a specific Transport Request. I forgat to mention that current problem is after an upgrade from 4.7c to ECC 6.0.

Regards.

Juan