<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:Tahoma;}
h1
        {margin-top:12.0pt;
        margin-right:0cm;
        margin-bottom:3.0pt;
        margin-left:0cm;
        page-break-after:avoid;
        font-size:16.0pt;
        font-family:Tahoma;}
h2
        {margin-top:12.0pt;
        margin-right:0cm;
        margin-bottom:3.0pt;
        margin-left:0cm;
        page-break-after:avoid;
        font-size:14.0pt;
        font-family:Tahoma;
        font-style:italic;}
h3
        {margin-top:12.0pt;
        margin-right:0cm;
        margin-bottom:3.0pt;
        margin-left:0cm;
        page-break-after:avoid;
        font-size:13.0pt;
        font-family:Tahoma;}
a:link, span.MsoHyperlink
        {font-family:Tahoma;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:#606420;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:Tahoma;
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.m1
        {color:blue;}
span.pi1
        {color:blue;}
span.t1
        {color:#990000;}
span.ns1
        {color:red;}
span.b1
        {font-family:"Courier New";
        color:red;
        font-weight:bold;
        text-decoration:none none;}
span.tx1
        {font-weight:bold;}
@page Section1
        {size:595.3pt 841.9pt;
        margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-AU link=blue vlink="#606420">
<div class=Section1>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>I am
working on a webflow scenario that integrates a process between two SAP systems
–being R/3 Enterprise and SRM 4.0. The idea is that a workflow in started
in R/3 when an invoice is held. It collects various pieces of information then
starts a corresponding workflow in SRM using a webflow activity, and should
then wait until the SRM workflow is complete. The SRM workflow will request
creation of a service confirmation to an agent. Once this is complete, the SRM
workflow ends and the R/3 workflow will continue from there.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>Because
I haven’t worked with the webflow step before, I started by just creating
a simple example. In the example, an R/3 workflow fills a container element
with the value of a user-id and passes it to an SRM workflow which sends an
email to this user. A reference workflow is created with the same container
element. I just wanted to see the process working so I know how to write up a
spec for the real workflow scenario mentioned above and be sure that it is
going to work!<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>I
have the example working to the point where the initiating R/3 workflow successfully
sends the wf-xml message to the SRM system, which starts the SRM workflow
(passing the container value of my user-id correctly). The SRM workflow
completes ok. But before anything else can happen, the R/3 workflow goes into
error. The error message is "XML tag <ProcessInstanceKey> not
available"</span></font><font size=2><span lang=EN-US style='font-size:
10.0pt'>. </span></font><font size=2><span style='font-size:10.0pt'>When I
checked the request / response messages (with transaction SWXML), this is what
the “CreateProcessInstance.Request (received response)</span></font><font
size=2><span lang=EN-US style='font-size:10.0pt'>” </span></font><font
size=2><span style='font-size:10.0pt'>looks like:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><?xml
version="1.0" ?> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>-
<WfMessage Version="1.1"
xmlns="http://www.wfmc.org/standards/docs/Wf-XML"><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>-
<WfMessageHeader><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
<Response /> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
<Key>HTTP://stlmelhsapd.stlmel.bsl.net:8002/SAP/BC/WORKFLOW_XML/?~protocol=04&~localkey=WS90200001</Key>
<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
</WfMessageHeader><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>-
<WfMessageBody><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>-
<CreateProcessInstance.Response><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
<ProcessInstanceKey /> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
</CreateProcessInstance.Response><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
</WfMessageBody><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>
</WfMessage><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>So
it seems like the response from SRM is not being correctly formed when it responds
to the initial request from R/3.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>I
found a message previously in this group which suggested that it might be an
authentication problem. I tried using an authentication rule in the header of
the SRM workflow (passing a user and password to it) but it didn’t make
any difference. Does anyone have any idea what is going wrong or what I should
check?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'>Thankyou!<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Kind Regards,</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=red face=Tahoma><span style='font-size:
10.0pt;color:red'>Andrew Rankin</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=red face=Tahoma><span style='font-size:
10.0pt;color:red'>+61 0437991735</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<DIV><P><HR>
EOM<BR>
<BR>
NOTICE - This message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.
</P></DIV>
</body>
</html>