web flow

Christian Nicklas christian.nicklas at ixos.de
Thu Nov 7 03:59:37 EST 2002


Hi*,
 
included you will find a short excerpt of our WF-XML study and here is a
cool link to the SAP-NET ;-) (link only in German).
http://www.sap.info/de/news.php4?OID=Article-178383dc6631b538a1
 
Kind Regards
Christian Nicklas
 
 
-----Original Message-----
From: Christian Nicklas [mailto:christian.nicklas at IXOS.DE]
Sent: Montag, 4. November 2002 08:08
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: web flow
 
 
Hi Susie,
 
we have created a scenario with parts of a supplay chain management process.
Two SAP-systems are linked with the WF-XML protocoll to send and receive XML
documents and interact via a cooperative workflow-scenario. Different SAP
Objects are involved in this process. Let me know how you get on. Are you
using the ITS as web-server and is the process between different companies
or within one company? (Out of the firewall)
 
Kind Regards
Christian Nicklas
 
 
 
 
 
-----Original Message-----
From: Nicholas Brand [mailto:nicholas.n.brand at uk.pwcglobal.com]
Sent: Friday, October 25, 2002 11:33 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: web flow
 
 
Susie,
 
Sorry for slight delay. As Jocelyn said, the answer is 'yes'.
You'll need to liaise with the supplier to get them to build the
corresponding target workflow.
It's important that in both the sending and target workflows, the workflow
container elements being sent and received via Wf-XML have identical names.
 
When  the workflow reaches the Web activity step, it extracts from the Task
      Container all elements that are either:
   ABAP Dictionary types or
   XML_DOC object types
 
It places these values in the generated Wf-XML document.
Task container elements from the calling workflow must be populated, if
only with an initial value, if they are to be included in the Wf-XML
document passed to the remote workflow system.
The Workflow Container Elements in the remote workflow must be named
identically to their respective Task Container Elements in the calling
workflow - i.e. the Container Element name is the matching key used.
When the remote workflow has completed, the values of those Workflow
Container Elements set as 'Export' parameters are sent back to the calling
workflow in a Wf-XML document.
Once the Wf-XML document reaches the calling workflow system, the values
are put into the like-named Task Container Elements, overwriting any value
stored there.
 
Hope that helps.
Do let us know how it goes.
 
 
Kind regards,
Nicholas Brand
 
 
 
 
 
 
 
"Norris, Susie" <Susie.Norris at sabre.com>@MITVMA.MIT.EDU> on 23/10/2002
15:54:09
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
 
 
Subject:    Re: web flow
 
 
Nicholas,
We have a need to do something like this to communicate to our supplier's
R/3 system.  Both systems are 4.6C; would this be possible?
 
-----Original Message-----
From: Nicholas Brand [mailto:nicholas.n.brand at uk.pwcglobal.com]
Sent: Wednesday, October 23, 2002 4:31 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: web flow
 
 
Sekar,
 
It's exciting to hear of people using the Wf-XML feature at last. It's been
around for a while now but rarely gets a mention on the WUG.
Have many other people in the group used this technique? It would be
interesting to see how many other collaborative workflow are being built
out there.
 
Anyway, back to your question:
 
You're right, with the wait for feedback flag set on your webflow task, the
associated work item is not completed during execution until a reply is
received in the form of a Wf-XML document. If you choose transfer format 01
(Wf-XML), the system's required reply URL is included in the XML document
sent to your target system. The XML reply document must contain the
operation ProcessInstanceStateChanged and set the process status to
closed.completed or closed.abnormalCompleted before the workflow can
continue.
 
Of course, you must complete the workflow in the target system before the
necessary Wf-XML document is sent back to the calling system; it may be
that you simply have to execute the workitem.
 
This was on a 4.6c system.
 
Please let us know how you get on.
 
 
Kind regards,
Nicholas
 
 
 
 
 
 
 
"Sekar, A" <a.sekar at intel.com>@MITVMA.MIT.EDU> on 23/10/2002 08:07:24
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
 
 
Subject:    web flow
 
 
Any help in this is greatly appreciated.
 
   I am using SAP 6.1.
We are trying to call a workflow in a system from another system's workflow
.Both the systems are in 6.1.
I used the web activity to make this call.If I check the wait for feedback
in the calling system then the source system is not able to complete the
workflow.That is, it is waiting in the web activity step.
In the target system it creates two xml document one is request and the
other one is response document.Both got the operation
>CreateProcessInstance</Operation.
How to generate a document with processInstancestateChanged .I think this
document will complete the workflow in the source system.
 
Thanks
Sekar
 
 
--------------------- End of message text --------------------
 
PLEASE NOTE THAT IBM recently completed its acquisition of
PricewaterhouseCoopers' global management consulting and information
technology services business, PwC Consulting.  As a result, PwC Consulting
is no longer a part of the PricewaterhouseCoopers network of firms, and is
now a part of the IBM Global Services business unit.  Accordingly, all
references to PwC Consulting or PwCC in this document should be deemed to
be references to IBM Global Services.
 
IBM (including IBM Global Services) and PricewaterhouseCoopers are not the
same organisation, and neither governs or is affiliated with the other, or
any
affiliate, subsidiary or division of the other.  The sender is neither a
partner in,
nor employee of PricewaterhouseCoopers and is now an employee of, and
acting for, IBM.
_________________________________________________________________
 
 
--------------------- End of message text --------------------
 
PLEASE NOTE THAT IBM recently completed its acquisition of
PricewaterhouseCoopers' global management consulting and information
technology services business, PwC Consulting.  As a result, PwC Consulting
is no longer a part of the PricewaterhouseCoopers network of firms, and is
now a part of the IBM Global Services business unit.  Accordingly, all
references to PwC Consulting or PwCC in this document should be deemed to
be references to IBM Global Services.
 
IBM (including IBM Global Services) and PricewaterhouseCoopers are not the
same organisation, and neither governs or is affiliated with the other, or
any
affiliate, subsidiary or division of the other.  The sender is neither a
partner in,
nor employee of PricewaterhouseCoopers and is now an employee of, and
acting for, IBM.
_________________________________________________________________
 


More information about the SAP-WUG mailing list