<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR>
<STYLE>@font-face {
        font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Tahoma
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Tahoma
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Tahoma
}
H1 {
        FONT-SIZE: 16pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: Tahoma
}
H2 {
        FONT-SIZE: 14pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: Tahoma
}
H3 {
        FONT-SIZE: 13pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: Tahoma
}
A:link {
        COLOR: blue; FONT-FAMILY: Tahoma; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; FONT-FAMILY: Tahoma; TEXT-DECORATION: underline
}
A:visited {
        COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Tahoma; TEXT-DECORATION: none; mso-style-type: personal-compose
}
SPAN.m1 {
        COLOR: blue
}
SPAN.pi1 {
        COLOR: blue
}
SPAN.t1 {
        COLOR: #990000
}
SPAN.ns1 {
        COLOR: red
}
SPAN.b1 {
        FONT-WEIGHT: bold; COLOR: red; FONT-FAMILY: "Courier New"; TEXT-DECORATION: none
}
SPAN.tx1 {
        FONT-WEIGHT: bold
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-AU vLink=#606420 link=blue>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>It
looks like your XML file is missing the workitem id.</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2>Resolving these sorts of problems can be tricky, make
sure:</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><SPAN class=455124809-09082005><FONT
face=Arial color=#0000ff size=2>- you have maintained anonymous logon data in
SICF for the workflow_xml service </FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>- you
have configured SWR_WEBSERVER on both systems (when you test you shouldn't get a
logon prompt if SICF is OK).</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>- You
have run RSWXML_REPAIR (name may not be quite right but it is in some oss notes)
in both systems</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>- You
have set up possible agents for the calling, called and reference workflow
templates (steer clear of authentication rules until you get the basic
communication working) i.e. the agents at the 'header level' of the
template</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>When
you test, both workflows should end up with at least 4 xml files - read
these and sometimes you will get extra error information.</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>You
may also get problems with your workflows if your network isn't configured,
sometimes the systems find it difficult to talk to one another, get your basis
person to do an NIPING to make sure your reverse DNS is all OK (no idea what
this means but basis people will). Also check with basis that the ICM
parameters are all set up in RZ10 for your host and port.</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>Good
luck, this sort of WF_XML communication is much more fun than boring old
RFCs!</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2>Mark</FONT></SPAN></DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=455124809-09082005><FONT face=Arial color=#0000ff size=2>SAP UK
Consulting</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Rankin, Andrew<BR><B>Sent:</B> 09 August 2005 02:37<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> Webflow step - error "XML tag
<ProcessInstanceKey> not available"<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">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 face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">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 face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">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: 10pt">. </SPAN></FONT><FONT size=2><SPAN
style="FONT-SIZE: 10pt">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: 10pt">”
</SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 10pt">looks
like:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><?xml version="1.0" ?>
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">-
<WfMessage Version="1.1"
xmlns="http://www.wfmc.org/standards/docs/Wf-XML"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">-
<WfMessageHeader><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"> <Response />
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">
<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 face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">
</WfMessageHeader><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">-
<WfMessageBody><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">-
<CreateProcessInstance.Response><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"> <ProcessInstanceKey />
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">
</CreateProcessInstance.Response><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">
</WfMessageBody><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"> </WfMessage><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">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 face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt">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 face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt">Thankyou!<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Tahoma size=2><SPAN
style="FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Kind
Regards,</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face=Tahoma color=red size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: red">Andrew Rankin</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face=Tahoma color=red size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: red">+61
0437991735</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><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></P></DIV></BLOCKQUOTE></BODY></HTML>