Send mail step and container element data type

[David Weston]

Hi everyone,
 
Thanks to Jocelyn, Alon for the help and advice.
 
Thanks for the help.....it looks like my problems are centred
around my subtype ZPDOTYPE_O to its supertype PDOTYPE_O returning
OL832 errors.
 
I am now investigating these errors and how I can work around them
 
Cheers
Dave
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: 05 November 2002 17:21
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Send mail step and container element data type
 
 
Hi Dave,
SWHACTOR or WFSYST-AGENT should be fine - all you need is a 14 char
field.
 
What SEND MAIL parameter are you passing your expression to? And with
what recipient type?
 
If the send mail step is giving misleading messages, go to the control
tab and enter the binding manually there - that's a more realistic test
of what is needed.  Send mail tends to put a few unnecessary
restrictions on the simple screen (basically to keep it simple) but you
can usually override them by doing the binding yourself.
 
If not, try putting your send mail task in an activity step instead.
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: weston at clockwork.ca [mailto:weston at clockwork.ca]
Sent: Wednesday, 6 November 2002 5:30 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Send mail step and container element data type
 
 
Hi folks,
 
Well I'm still battling with my workflow to dynamically find the
positions attached to a rule defined by responsibilities and use the
element against the send mail step in the workflow.
 
Can someone clarify for me the correct data type to use for a container
element when using the send mail step with the config of expression and
organizational objects ?. The famous book mentions that the data type
should be based on SWHACTOR but this is rejected as an invalid data type
by the send mail step in the workflow builder. So I have now created a
virtual attribute against my object PDOTYPE_O (HR org units) as a
multiline attribute based on WFSYST-ACT_AGENT to find the positions from
the function RH_GET_ACTORS.
 
Only problem now is my workflow stalls in process with an OL832
message....saying my "object type component COCODEAGENTS is not
supported by object type ZPDOTYPE_O" where COCODEAGENTS is my virtual
attribute and ZPDOTYPE_O is my subtype.
 
Any ideas or guidance would be gratefully received ?
 
Dave
 
 
 
 
 
 
 
--------------------------------------------------------------------
mail2web - Check your email from the web at http://mail2web.com/ .