AW: SAP MAPI vs SAP Exchange Connector

[Schaffer, Klaus]

Hi Philip,
 
I remember a posting of Peter Roehlen who talked about the roll-out to 800+
Outlook MAPI users. Perhaps he's still on the list to tell us about his
expierence (e.g. what refresh intervall was set in the MAPI client). As I
have also a client who's concerned about the performance with more than 500
users, I would be happy if there a any workflowers on the list who can at
least confirm that it's working.
 
Well and of course the licencing issue. Our probably future SAP MAPI users
will receive about 20 workitems a month, so the full licence cost would be
too high. Are there any official informations on SAP Marketplace or is it
always an individual aggreement with the responsible SAP account manager?
 
Cheers. Klaus
 =20
 
-----Urspr=FCngliche Nachricht-----
Von: Kisloff, Philip [mailto:Philip.Kisloff at astrazeneca.com]
Gesendet: Mittwoch, 30. Januar 2002 10:37
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: SAP MAPI vs SAP Exchange Connector
 
 
Does anyone know of a limitation to the number of users that can
simultaneously use SAPMAPI? OSS note 454845 says there is limit
of 200 users for Lotus notes integration, but there is no mention
of any limits for SAPMAPI.=20
 
My company backed off using SAPMAPI on the question of number of=20
users and went for an SMTP mail with shortcut to the workplace inbox.
But I'm trying to find the source of these concerns. One possible=20
mechanism could have been from OSS note 0196537 (about two RFC=20
connections per user and 4.6B not auto-disconnecting) but any firm=20
data on this would be useful.
 
Also Greg, I noticed that OSS note 0480685 says that SAPMAPI does not
work for Windows XP/Outlook 2002. A temporary thing perhaps ?
 
Regards
 
Philip Kisloff
AstraZeneca
 
=20
 
-----Original Message-----
From: Rolim de Camargo S. Junior [mailto:rcjunior at usiminas.com.br]
Sent: 29 January 2002 19:17
To: SAP-WUG at MITVMA.MIT.EDU
Subject: RES: SAP MAPI vs SAP Exchange Connector
 
 
Hi Gregory
 
 
I am using SAP MAPI because  I didn=B4t obtain to make the integration with
SAP Exchange Connector.
 
My environment is SAP 4.0B with MS Outlook 97.
 
I recommend that you reads note 79875 (installation of SAP MAPI).After the
installation of SAP MAPI the integration is ready.
 
The only inconvenience is that it will be necessary to install SAP MAPI for
all users SAP. =20
 
When the user to have access the Outlook it will make one pseudo-login in
R/3.  All workitens sent by R/3 to the Outlook will go to contain an icon
that will allow the access to R/3.Exists options to work online or offline .
 
When the user to click on  this icon  will go to access directly
transaction in R/3. After this it will be able to execute the
function or to execute other transactions normally.
 
I=B4m in phase of implementation of the Purchase Requistion Release Scene
(WS0000038) with this integration and It=B4s functioning without problems.
 
Regards
 
Rolim C Souto=20
System Analyst
Usiminas S.A..
@-mail : rcjunior at usiminas.com.br
 
 
 
 
        ----- Mensagem original -----
        De:             Levy, Gregory [SMTP:gregory.levy at sap.com]
        Enviada em:             Ter=E7a-feira, 29 de Janeiro de 2002 15:19
        Para:           SAP-WUG at MITVMA.MIT.EDU
        Assunto:                SAP MAPI vs SAP Exchange Connector
        Prioridade:             Alta
 
        To All:
 
        Does anyone have experience executing workflow via SAP MAPI or SAP
Exchange
        Connector. My client would like to send and email to Outlook and
supply a
        link that enable the person to click the link and have workflow
kickoff. Any
        help on this issue would be greatly appreciated!!!
 
        Gregory Levy
        Senior Technical Consultant
        SAP America,  Inc.
 
        312 Walnut Street
        Cincinnati, Oh 45202
        T   513-977-5481
        P   888-760-2244
        F   513-977-5401
        E   gregory.levy at sap.com
        http://www.sap.com
 
 
--=20
                  E-Mail Disclaimer
 
Der Inhalt dieser E-Mail ist ausschliesslich fuer den bezeichneten
Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser=20
E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass
jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie,
sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu
setzen. Aussagen gegenueber dem Adressaten unterliegen den Regelungen
des zugrundeliegenden Angebotes bzw. Auftrags, insbesondere den=20
Allgemeinen Auftragsbedingungen und der individuellen Haftungs-
vereinbarung. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er
unsererseits durch einen Brief entsprechend bestaetigt wird. Die
Versendung von E-Mails an uns hat keine fristwahrende Wirkung. Wir=20
moechten Sie ausserdem darauf hinweisen, dass die Kommunikation per
E-Mail ueber das Internet unsicher ist, da fuer unberechtigte Dritte
grundsaetzlich die Moeglichkeit der Kenntnisnahme und Manipulation
besteht. Wir werden daher keine vertraulichen Daten unverschluesselt
per E-Mail ueber das Internet versenden.
 
The information contained in this email is intended solely for the
addressee. Access to this email by anyone else is unauthorized. If you
are not the intended recipient, any form of disclosure, reproduction,
distribution or any action taken or refrained from in reliance on it,
is prohibited and may be unlawful. Please notify the sender
immediately. All statements of opinion or advice directed via this
email to our clients are subject to the terms and conditions expressed
in the governing KPMG client engagement letter. The content of this
email is not legally binding unless confirmed by letter. The sending
of emails to us will not constitute compliance with any time limits or
deadlines. We also like to inform you that communication via email
over the internet is insecure because third parties may have the
possibility to access and manipulate emails. For this reason we will
not send any confidential information via email over the internet,
unless encrypted.