Webflow step - error "XML tag <ProcessInstanceKey> not available"

Fri Aug 12 10:54:57 EDT 2005

If you can't see the XML documents make sure you have authorisations ...
this has caught me out a few times as the BDS authorisations aren't
included in your normal roles you may have as a workflow developer.

	-----Original Message-----
	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Rankin, Andrew
	Sent: 12 August 2005 06:12
	To: SAP Workflow Users' Group
	Subject: RE: Webflow step - error "XML tag <ProcessInstanceKey>
not available"

	Hi Christian, Mark,

	Thankyou for your responses. Mark I went through all the steps
you mentioned and the problem I had has been resolved, I'm pretty sure
it was the possible agents in one of the workflow templates, so thanks
very much for the comprehensive list of checks.

	Unfortunately I now have a different problem in the receiving
(640) system. It receives the "CreateProcessInstance" message, starts a
workflow, sends back the response. Great, but when the workflow
completes, I get no "ProcessInstanceStateChanged" message coming back,
leaving the original workflow hanging... Also despite running
RSWXML_REPAIR, I cannot see any XML messages via SWXML in the receiving
640 system.

	I tried setting up the scenario in reverse and it all works
correctly, so there must be something wrong with the 640 system. I've
raised it in OSS.

	Kind Regards,

	Andrew Rankin

	0437991735

________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Griffiths, Mark
	Sent: Tuesday, 9 August 2005 7:58 PM
	To: SAP Workflow Users' Group
	Subject: RE: Webflow step - error "XML tag <ProcessInstanceKey>
not available"

	It looks like your XML file is missing the workitem id.

	Resolving these sorts of problems can be tricky, make sure:

	- you have maintained anonymous logon data in SICF for the
workflow_xml service 

	- you have configured SWR_WEBSERVER on both systems (when you
test you shouldn't get a logon prompt if SICF is OK).

	- You have run RSWXML_REPAIR (name may not be quite right but it
is in some oss notes) in both systems

	- 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

	When you test, both workflows should end up with at least 4 xml
files - read these and sometimes you will get extra error information.

	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.

	Good luck, this sort of WF_XML communication is much more fun
than boring old RFCs!

	Cheers,

	Mark

	SAP UK Consulting

		-----Original Message-----
		From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Rankin, Andrew
		Sent: 09 August 2005 02:37
		To: sap-wug at mit.edu
		Subject: Webflow step - error "XML tag
<ProcessInstanceKey> not available"

		Hi,

		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.

		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!

		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". When I checked the request
/ response messages (with transaction SWXML), this is what the
"CreateProcessInstance.Request (received response)" looks like:

		<?xml version="1.0" ?> 

		- <WfMessage Version="1.1"
xmlns="http://www.wfmc.org/standards/docs/Wf-XML">

		- <WfMessageHeader>

		  <Response /> 

<Key>HTTP://stlmelhsapd.stlmel.bsl.net:8002/SAP/BC/WORKFLOW_XML/?~protoc
ol=04&~localkey=WS90200001</Key> 

		  </WfMessageHeader>

		- <WfMessageBody>

		- <CreateProcessInstance.Response>

		  <ProcessInstanceKey /> 

		  </CreateProcessInstance.Response>

		  </WfMessageBody>

		  </WfMessage>

		So it seems like the response from SRM is not being
correctly formed when it responds to the initial request from R/3.

		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?

		Thankyou!

		Kind Regards,

		Andrew Rankin

		+61 0437991735

________________________________

		EOM

		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. 

________________________________

	EOM

	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. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050812/70eec6b7/attachment.htm