SAP-WUG Digest, Vol 14, Issue 86 - Retrieving WF Agents from SWWUSERWI

Tue Jan 31 17:33:38 EST 2006

Yes 4.7 = 6.20 Basis release so you are high enough for all of those options. 
_RULE_RESULT relates to the binding between a workflow step and a rule. 
Events to recalculate agents on active work items are in the basic data of the workflow (look for the hat icon in 
SWDD) 

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 
Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.
Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dale Brown
Sent: Wednesday, 01 February 2006 12:17 AM
To: sap-wug at mit.edu
Subject: Re: SAP-WUG Digest, Vol 14,Issue 86 - Retrieving WF Agents from SWWUSERWI

Jocelyn,

Thanks for the information about the SAP_WAPI* function modules.
We are on release 4.7.
What release captures the other options you mentioned?  Are we high enough?

Thanks for the responding.  If we are not on a release high enough, what
recommendations
do you suggest?

Dale R. Brown
Duke University
OIT Application and Database Services
919.684.5341
http://faithforthefamily.com/sure.cfm    ç===

             sap-wug-request at m                                             
             it.edu                                                        
             Sent by:                                                   To 
             sap-wug-bounces at m         sap-wug at mit.edu                     
             it.edu                                                     cc 

                                                                   Subject 
             01/30/2006 05:50          SAP-WUG Digest, Vol 14, Issue 86    
             PM                                                            

             Please respond to                                             
              sap-wug at mit.edu                                              

Send SAP-WUG mailing list submissions to
             sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
             http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
             sap-wug-request at mit.edu

You can reach the person managing the list at
             sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."

Today's Topics:

   1. RE: WF_Doc to PDF (Paul Vlasveld)
   2. RE: Retrieving WF Agents from SWWUSERWI (Dart, Jocelyn)
   3. RE: Webservice problem (Dart, Jocelyn)
   4. RE: Extended notifications not working (Dart, Jocelyn)

----------------------------------------------------------------------

Message: 1
Date: Mon, 30 Jan 2006 13:19:57 -0800
From: "Paul Vlasveld" <pvlasvel at adobe.com>
Subject: RE: WF_Doc to PDF
To: <sap-wug at mit.edu>
Message-ID:

<4FA366C5A4633D448003F038CFC85B427759A4 at namail2.corp.adobe.com>
Content-Type: text/plain; charset="us-ascii"

Jeff,

Maybe you can use the printer device type "PDF1" in the workflow to
create the PDF.  We use this device type with the PDF converter driver
to print output to PDF.

Paul

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060130/92ac250c/attachment-0001.htm

------------------------------

Message: 2
Date: Tue, 31 Jan 2006 06:38:02 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Retrieving WF Agents from SWWUSERWI
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:

<EFB207BF0F7FAA47A800709C57D0523D02158303 at sgsine10.sin.sap.corp>
Content-Type: text/plain;            charset="iso-8859-1"

Dale,
Which release are you on?
You should avoid direct use of tables.
Look instead at the WAPIs (function modules prefixed SAP_WAPI*)
Also if you are in a high enough release there are other options for
capturing
original and forwarded agents such as the _RULE_RESULT container element,
events to recalculate agents on active work items, the executed_by user of
a work item etc.

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the
person or entity to which it is addressed. If you are not the intended
recipient, you are hereby notified that any distribution, copying, review,
retransmission, dissemination or other use of this electronic transmission
or the information contained in it is strictly prohibited. If you have
received this electronic transmission in error, please immediately contact
the sender to arrange for the return of the original documents.
Electronic transmission cannot be guaranteed to be secure and accordingly,
the sender does not accept liability for any such data corruption,
interception, unauthorized amendment, viruses, delays or the consequences
thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the sender
is authorized to state them to be the views of SAP AG or any of its
subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
employees make no representation nor accept any liability for the accuracy
or completeness of the views or information contained herein. Please be
aware that the furnishing of any pricing information/ business proposal
herein is indicative only, is subject to change and shall not be construed
as an offer or as constituting a binding agreement on the part of SAP AG or
any of its subsidiaries to enter into any relationship, unless otherwise
expressly stated.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dale Brown
Sent: Tuesday, 31 January 2006 5:31 AM
To: sap-wug at mit.edu
Subject: Retrieving WF Agents from SWWUSERWI

Our worlfkow has been in place for a few months and now we want to identify
multiple forwarding agents.

On our task that calls the FIPP release method, when an agent backs out of
the
task without rejecting or releasing it, the workflow just recircs and puts
the work item
back in the orignal list of agents that were identified to complete this
task.

However, one of the original agents, can forward the work item to other
agents. If one of these
forwarded agents just backs out of it, then it still recircs back to the
original list of agents.
We desire to keep the forwarded list of agents, once it has been forwarded.

I can write a method that will tell me the actual agent (one of the ones it
was forwarded to)
 that backed out of the work item, without releasing or rejecting it, but I
can not obtain the
rest of the forwarded agents. I was looking to go to the SWWUSERWI table,
but the work
item key changes before my new method step gets called.  A new work item is
assigned
and the prior work item is removed from SWWUSERWI .

Without a repair to SAP code, is there another way to capture all of the
forwarded agents?

Dale R. Brown
Duke University
OIT Application and Database Services
919.684.5341
http://faithforthefamily.com/sure.cfm    ?===

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

------------------------------

Message: 3
Date: Tue, 31 Jan 2006 06:42:03 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Webservice problem
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:

<EFB207BF0F7FAA47A800709C57D0523D02158309 at sgsine10.sin.sap.corp>
Content-Type: text/plain;            charset="us-ascii"

Damian,
Please report this in to SAP via the usual channels (i.e. a problem
message in service.sap.com or call your local help desk).
WFWS is relatively new and I don't think many people have tried it as
yet, so it could
well be a simple bug.  In any case I think you would be best to get
official confirmation on
any requirements for the WSDL file when using WFWS.

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Reyes Diaz, Damian
Sent: Tuesday, 31 January 2006 2:21 AM
To: SAP-WUG at mit.edu
Subject: Webservice problem

Hi,

I've a problem with my sap business workflow definition.
I try to use a webservice created in Java and defined by a WSDL. I
execute WFWS transaction (WSDL import) but something is wrong because
it's not recognized. I try with google service and WFWS recognizes it
well but not when I try my own WSDL file.
I don't know why. This is my WSDL (very simply):

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
name="PruebaJDBCWsd" targetNamespace="urn:PruebaJDBCWsd"
xmlns:bns0="urn:PruebaJDBCWsd/ConfigPruebaJDBC/document"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
  <wsdl:import
location="http://aldp4.es.heiway.net:50000/PruebaJDBC/ConfigPruebaJDBC/b
indings?wsdl&amp;style=document"
namespace="urn:PruebaJDBCWsd/ConfigPruebaJDBC/document"/>
  <wsdl:service name="PruebaJDBC">
    <wsdl:port name="ConfigPruebaJDBCPort_Document"
binding="bns0:ConfigPruebaJDBCBinding">
      <soap:address
location="http://aldp4.es.heiway.net:50000/PruebaJDBC/ConfigPruebaJDBC?s
tyle=document"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

Can anybody help me? Please, this is important.
Thanks in advance

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

------------------------------

Message: 4
Date: Tue, 31 Jan 2006 06:49:51 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Extended notifications not working
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:

<EFB207BF0F7FAA47A800709C57D0523D0215830F at sgsine10.sin.sap.corp>
Content-Type: text/plain; charset="iso-8859-1"

Hi Mikko,

Well by the look of it your config to select the notifications is correct,
but you are missing something in your
config to send out a message.

We have it working fine at other sites.  Are you using the standard
category WORKFLOW or your own custom copy?
Have you assigned message templates?

Have you checked user WF-BATCH has a valid email address for use as a
sender address?

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com <http://www.sap.com/>

The information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the
person or entity to which it is addressed. If you are not the intended
recipient, you are hereby notified that any distribution, copying, review,
retransmission, dissemination or other use of this electronic transmission
or the information contained in it is strictly prohibited. If you have
received this electronic transmission in error, please immediately contact
the sender to arrange for the return of the original documents.

Electronic transmission cannot be guaranteed to be secure and accordingly,
the sender does not accept liability for any such data corruption,
interception, unauthorized amendment, viruses, delays or the consequences
thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the sender
is authorized to state them to be the views of SAP AG or any of its
subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
employees make no representation nor accept any liability for the accuracy
or completeness of the views or information contained herein. Please be
aware that the furnishing of any pricing information/ business proposal
herein is indicative only, is subject to change and shall not be construed
as an offer or as constituting a binding agreement on the part of SAP AG or
any of its subsidiaries to enter into any relationship, unless otherwise
expressly stated.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Mikko M?ki-Rahkola
Sent: Monday, 30 January 2006 10:25 PM
To: SAP Workflow Users' Group
Subject: Extended notifications not working

Hi all,

I'm on a WAS6.40 system and trying to send out some emails with the
extended notifications functionality verification report but the system
gives me some unexpected errors. Hope some of you have overcome this issue,
too, and could help me out...

The report SWN_TEST_VERI01 launches workflow WS77300061 and task TS77307918
as its first work item. I've also set both objects' agent assignment to
general task and I can see that the work item is waiting in my inbox. There
is also an active node in SCOT under INT and I have my email address
maintained on my user ID. So everything should be fine according to my
understanding.

But when I run the report, it seems to select the work item all right
according to the log:

             Selection of Notifications

             00001 notifications selected
             00001 notifications deleted (logically)
             00001 new notifications saved
             00000 notifications saved
             Sending Messages

             00001 notifications selected
             00000 messages sent
             Unable to send 00000 notifications due to errors

             No notification was sent for the work item
             Test of the standard functions failed

...but the notification doesn't get sent. Looking at the application log in
SWNCONFIG, there's only an error "Error when creating message" (SWN032) for
this batch run.

Any ideas what could be wrong?

Best regards,
Mikko
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060131/2ff469c4/attachment.htm

------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

End of SAP-WUG Digest, Vol 14, Issue 86
***************************************

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug