Check FM in SRM7 (Keohan, Susan - 1140 - MITLL)

Tue Sep 30 11:49:38 EDT 2014

Hi Andy,

We *never* take SAP’s advice ;-)

We are using the same custom workflow templates that we used in SRM5.  But the Check FM ‘works’ – it just gives the end user that nasty-gram.

The old WFs were too complex to have been converted to PC during this particular upgrade.  (Looking forward to THAT effort too!).

Thanks for your feedback!

Sue

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Andy Curtis
Sent: Tuesday, September 30, 2014 11:15 AM
To: SAP Workflow Users' Group
Subject: Check FM in SRM7 (Keohan, Susan - 1140 - MITLL)

Sue

Why do you have a custom check FM? If your taking the SAP advice and 'not modified' the SAP templates then you shouldn't ever get duplicate Wf's.  We don't and we have gone from SRM5 to SRM7 AC Wf.  

Thinking, SAP actually start a Waiting status Wf when you make a change to a PO/SC and SAVE it.  They use it to record the Approval chain and display it in the Approval Preview.

Andy 

On Tue, Sep 30, 2014 at 3:43 PM, <sap-wug-request at mit.edu> wrote:

Send SAP-WUG mailing list submissions to
        sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
        http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
        sap-wug-request at mit.edu

You can reach the person managing the list at
        sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."

Today's Topics:

   1. Check FM in SRM7 (Keohan, Susan - 1140 - MITLL)

---------- Forwarded message ----------
From: "Keohan, Susan - 1140 - MITLL" <keohan at ll.mit.edu>
To: "SAP Workflow Users' Group (sap-wug at mit.edu)" <sap-wug at mit.edu>
Cc: 
Date: Tue, 30 Sep 2014 14:42:07 +0000
Subject: Check FM in SRM7

Hi all,

We’re upgrading to SRM7 (technical only) from SRM5 and using our old Application Controlled Workflows.

We’ve always used a Check Function Module in the Event Linkage table to prevent multiple workflows from kicking off for Purchase Order Change Versions  if the same GUID is already involved in an active workflow process.  

So if the Check Function module (referenced in SWETYPV) finds an active workflow using that PO GUID, it exits gracefully with our friendly exception NO_WORKFLOW.

In SRM7, however, this is interpreted as something completely different in the PDO layer…

A very nasty error is displayed to the user:

Has anyone else had to change their methodology of using Check FMs in SRM7?  I know I can put a task in the workflow to check for other flows on the same GUID, but Check FMs seemed to work so nicely before.

Thanks in advance,
Sue

Susan R. Keohan

SAP Workflow Specialist

MIT Lincoln Laboratory

244 Wood Street, LI-200

Lexington, MA. 02420

781-981-3561

@skeohan

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140930/f11b6aa6/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 10978 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140930/f11b6aa6/attachment-0001.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6646 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140930/f11b6aa6/attachment-0001.bin