workflow communication with Microsoft Outlook

[Marty Braithwaite]

Thanks Phil, the tip about asking the exchange administrator to setup a =
rule in the case of undeliverable messages from SAP, was just what I was =
looking for.
 
Thanks for your help,
Marty Braithwaite
CPrail SAP sustainment team
 
-----Original Message-----
From: Soady, Phil [mailto:phil.soady at sap.com]
Sent: Wednesday, January 08, 2003 6:13 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: workflow communication with Microsoft Outlook
 
 
Hi Marty
 
If you have critical communication with your groupware tool,
then tight integration is advisable.
MLUNXSND can react to errors. But does the called tool set the errors =
properly.
Getting scripts to set return codes (-1) when sendmail or equivalent =
didn't work can be=20
difficult. Is sendmail and your smtp server configured to return errors =
when the addressee
in unknown to the smtp server and its directory ?
All very messy and involves good knowledge of scripting OS return codes, =
SMTP and the groupware tool
or its SMTP server at least.
 
The direct connection (LOTUS connection supplied by IBM) or SXC SAP =
Exchange connector, supplied
by SAP is a better way of integrating groupware and SAP.
 
BTW,
  ask your Exchange administrator to send the mails or at least a mail =
to an a given account
if an mail from address (sapuser...) arrives and can not be forwarded to =
a valid user.
Server side rules can cover this if im not mistaken.
May be an easy way to quickly address your problem .
 
hth,
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Marty Braithwaite [mailto:Marty_Braithwaite at cpr.ca]=20
Sent: Wednesday, 8 January 2003 7:28 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: workflow communication with Microsoft Outlook
 
 
Hi Everyone,
 
We currently have a workflow process that sends an approval notification =
from SAP via SAPconnect to the desired agents Outlook inbox.  The =
problem we are running into is when a user doesn't receive the email, =
but when the send order is viewed via SCOT, SAP thinks it was sent just =
fine.  We only have
a 1 way communication with Outlook, so if a message fails for some =
reason, for example an invalid email address, SAP doesn't know it.  This =
doesn't happen often, but enough to cause some concern.  I was wondering =
if anyone knows of a way to setup a 2 way communication between Outlook =
and SAP so SAP
will know if the email was sent to Outlook successfully or not?
 
Thanks,
Marty Braithwaite
CPrail SAP Sustainment Team
 
 
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT =
------------------------------
 
Computer viruses can be transmitted via email. Recipient should check =
this email and any attachments for the presence of viruses. Sender and =
sender company accept no liability for any damage caused by any virus =
transmitted by this email.
 
This email transmission and any accompanying attachments contain =
confidential information intended only for the use of the individual or =
entity named above.  Any dissemination, distribution, copying or action =
taken in reliance on the contents of this email by anyone other than the =
intended recipient
is strictly prohibited.  If you have received this email in error please =
immediately delete it and  notify sender at the above email address.=20
 
 
Le courrier =E9lectronique peut =EAtre porteur de virus informatiques.  =
Le destinataire doit donc passer le pr=E9sent courriel et les pi=E8ces =
qui y sont jointes au d=E9tecteur de virus.  L'exp=E9diteur et son =
employeur d=E9clinent toute responsabilit=E9 pour les dommages caus=E9s =
par un virus contenu dans le
courriel.
 
Le pr=E9sent message et les pi=E8ces qui y sont jointes contiennent des =
renseignements confidentiels destin=E9s uniquement =E0 la personne ou =
=E0 l'organisme nomm=E9 ci-dessus.  Toute diffusion, distribution, =
reproduction ou utilisation comme r=E9f=E9rence du contenu du message =
par une autre personne que le
destinataire est formellement interdite.  Si vous avez re=E7u ce =
courriel par erreur, veuillez le d=E9truire imm=E9diatement et en =
informer l'exp=E9diteur =E0 l'adresse ci-dessus.
 
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT =
------------------------------
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT =
------------------------------
 
Computer viruses can be transmitted via email. Recipient should check =
this email and any attachments for the presence of viruses. Sender and =
sender company accept no liability for any damage caused by any virus =
transmitted by this email.
 
This email transmission and any accompanying attachments contain =
confidential information intended only for the use of the individual or =
entity named above.  Any dissemination, distribution, copying or action =
taken in reliance on the contents of this email by anyone other than the =
intended recipient is strictly prohibited.  If you have received this =
email in error please immediately delete it and  notify sender at the =
above email address.=20
 
 
Le courrier =E9lectronique peut =EAtre porteur de virus informatiques.  =
Le destinataire doit donc passer le pr=E9sent courriel et les pi=E8ces =
qui y sont jointes au d=E9tecteur de virus.  L=92exp=E9diteur et son =
employeur d=E9clinent toute responsabilit=E9 pour les dommages caus=E9s =
par un virus contenu dans le courriel.
 
Le pr=E9sent message et les pi=E8ces qui y sont jointes contiennent des =
renseignements confidentiels destin=E9s uniquement =E0 la personne ou =
=E0 l=92organisme nomm=E9 ci-dessus.  Toute diffusion, distribution, =
reproduction ou utilisation comme r=E9f=E9rence du contenu du message =
par une autre personne que le destinataire est formellement interdite.  =
Si vous avez re=E7u ce courriel par erreur, veuillez le d=E9truire =
imm=E9diatement et en informer l=92exp=E9diteur =E0 l=92adresse =
ci-dessus.
 
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT =
------------------------------