<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Sorry, but the sandbox system where I built this is no longer. If I get some time to re-create this, I will get back to you. It's crunch time on my current project.<BR>
<BR>
Ed<BR> <BR>
<HR id=stopSpelling>
From: edwarddiehl@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: RE: Wait step using correlation - NEW!<BR>Date: Thu, 21 Jan 2010 07:32:26 -0600<BR><BR>
<STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
Hi Jake,<BR>It's been a long time since I played around with correlations. I have never had the opportunity to actually put one in production. I put a blog on SDN covering the whole process of setting up a correction. As a part of developing the blog I built a prototype that did work. Let me see if I can find that prototype and to see how the event was entered.<BR> <BR>Kudos for giving it a try. I'll get back to you.<BR>Ed<BR> <BR>> Subject: RE: Wait step using correlation - NEW!<BR>> Date: Wed, 20 Jan 2010 17:01:06 -0600<BR>> From: jake.schmidt@spiritaero.com<BR>> To: sap-wug@mit.edu<BR>> <BR>> Hey WUG,<BR>> <BR>> I'm replying to a rather old WUG message but it is the latest around<BR>> correlations I could find. I'm having trouble on both an ECC 5.0<BR>> SAPKB64018 and an ECC 6.0 SAPKB70103 box when trying to get a<BR>> correlation to work. I can define my correlation in SWF_CRL1 (I hope<BR>> I'm defining it right can't test it yet). I can add my wait step with<BR>> correlation following the instructions in OSS 1335009. My problem<BR>> arises with the activation part via a process control step. When you<BR>> select a PC step and set to function 9 Activate Correlation the "Name of<BR>> Event" field has no values other than local events. I can type my<BR>> correlation name, base element, and a correlation instance (based on<BR>> CL_SWF_MOD_CORRELATION)...however I get an error because I lack an<BR>> event. It seems buggy but maybe I'm doing something wrong...??<BR>> <BR>> I'm trying to correlate a quality notification BUS2078 to tasks QMSM.<BR>> The key for BUS2078 is a partial key for QMSM. I believe this qualifies<BR>> as something to use correlations for. Below is the best WUG message<BR>> around correlations. The SAP help is weak, the second edition of<BR>> Practical Workflow doesn't touch on correlations, I found 1 SDN power<BR>> point that wasn't helpful, OSS isn't helpful other than the note Ed<BR>> mentioned below. Taking all that into account I'm curious how many<BR>> people use correlations or recommend them?<BR>> <BR>> I'll provide more info as requested.<BR>> <BR>> Thank you WUG<BR>> Jake Schmidt<BR>> Workflow Developer - Spirit Aerosystems<BR>> <BR>> <BR>> <BR>> -----------------------------------------------------------------<BR>> <BR>> Edward Diehl edwarddiehl at hotmail.com<BR>> Tue Apr 28 12:49:10 EDT 2009<BR>> <BR>> * Previous message: Excel attachment not attached in Workflow<BR>> * Next message: Extended notifications<BR>> * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]<BR>> <BR>> Hi WUGgers,<BR>> <BR>> Awhile back I asked if anyone out there had successfully implemented a<BR>> correlation wait step. I didn't get any response, so either no one has<BR>> tried it or gave up when they did.<BR>> <BR>> Let me encourage you to investigate the correlation mechanism - an event<BR>> mechanism on steroids. In one of our workflows here we are using it to<BR>> "listen" for an inbound IDOC that applies a credit for a material<BR>> return. The IDOC object instance cannot possibly be known at the time<BR>> the workflow is initiated - hence the need for a mechanism that uses<BR>> anecdotal information; i.e. the FI-AR document number, which is known to<BR>> the IDOC object as well as the workflow.<BR>> <BR>> Well, it turns out there is a bug in the correlation mechanism. It will<BR>> be fixed in OSS 1335009, which has not yet been released. There is<BR>> however, a workaround I got from the SAP developer. Please see the<BR>> attachment.<BR>> <BR>> First, create the correlation wait step and activate the workflow<BR>> template. The correlation step will fail without doing the following as<BR>> outlined in the attachment:<BR>> <BR>> 1. Uncheck the "Use Correlation" box.<BR>> 2. Using F4, select the object from the workflow container. <BR>> 3. Check the "Use Correlation" box and it will take you back to your<BR>> original correlation cofig.<BR>> <BR>> That's it.<BR>> <BR>> Let me know if you have any questions.<BR>> <BR>> Ed Diehl<BR>> <BR>> <BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR>
<HR>
Hotmail: Powerful Free email with security by Microsoft. <A href="http://clk.atdmt.com/GBL/go/196390710/direct/01/">Get it now.</A> <br /><hr />Hotmail: Trusted email with powerful SPAM protection. <a href='http://clk.atdmt.com/GBL/go/196390707/direct/01/' target='_new'>Sign up now.</a></body>
</html>