ERPGenie.COM -> FAQ -> SAP Exchange Connector

1. How can I link Microsoft Exchange with R/3?

2. How can I access SAPoffice with the Outlook or Exchange Client?

3. How can I use forms to process data in R/3?

4. How can I operate E-mail or faxes in R/3 applications/users with the available Exchange Infrastructure?

5. Which types of forms can I use in Outlook and in the Exchange Client?

6. What Workflow function is supported?

7. Which options do I have for offline processing?

8. What are the required SAP components, what prerequisites do they have, when are they available and how much do they cost?

9. Where can I find current information on the respective components?

Tell me about the history of SAP Exchange connector and the applicable versions.

1.) How can I link Exchange with R/3?

A link from R/3 to Exchange can be produced with three different components that can be used individually or combined, depending on the functions required:

• Client based solution with the SAP MAPI service provider:
  The Outlook or Exchange Client can be enhanced with the SAP MAPI Service Provider so that mails that are stored in SAPoffice can be read and processed in a separate message store. Work items in the SAP Business Workflow, which are found in the SAPoffice inbox, are visible and can be executed. In addition, a SAPoffice address book is available. Mails can be moved back and forth between the exchange message store and the SAPoffice message store.

• SAPforms via mail:
  SAPForms is a technology which allows you to control different interfaces of the R/3 system from different types of forms. A possible application is starting workflows and processing form-based work items in the R/3 system via Internet mail. A specially structured mail is sent to a special receiver (Agent) in the R/3 system from an Outlook or Exchange form to start a workflow. Vice Versa, workitems can be sent from the R/3 system as Internet mail to the external mail address of an SAP user. This workitem mail can be processed with a form on the Outlook or Exchange client. Processing is possible offline (that is without connection to the R/3 system); starting the workflow is also possible offline.

• Exchange Server link using SAPconnect SMTP Linking or SAP Exchange Connector:
  Using the SAPconnect SMTP Linking or the SAP Exchange Connector, it is possible to use the MS Exchange Infrastructure with R/3 applications or R/3 users without the Exchange Client. The sending and receiving of messages, including status information (received and read) is supported here for Internet, fax and Exchange mailbox recipients.

2.) How can I access SAPoffice with the Outlook or Exchange Client?

Via the SAP MAPI Service Provider, SAPoffice can be linked to a MS Outlook or Exchange client as the mail and storage system of the R/3 system. For the user, this means that he can work in the normal PC environment, and can have access to the SAPoffice functions via the Outlook or the Exchange interface. This naturally includes the options for internal and external communication and the hierarchical SAPoffice "private" and "shared folders".

Editing and sending work items and messages

Users also receive the work items generated by the SAP Business Workflow in their inbox. Work items are activities that are assigned to a user (or to a user group) and which can be displayed and processed via the SAPoffice inbox. The connection via the SAP MAPI Service provider is narrower than the connection via Internet mail. If a user for example selects a work item for processing, all other users who are specified as agents are removed from the in-box. This would not be the case with the Internet mail connection.

In addition, notifications from the applications of the corresponding user are sent directly to his in-box.

Actions are actions in R/3

SAP MAPI Service Provider causes actions or changes to R/3 work items or messages via the Outlook or Exchange Client to have direct actions in R/3. Documents deleted from the inbox, for example, are also deleted at the same time in R/3 or a SAPgui is started to further process the work items in the R/3 System that were generated by SAP Business Workflow.

3.) How can I use forms to process data in R/3?

In the Exchange environment the form types Outlook form and Exchange form are supported by Microsoft. See question 4 for the differences between these two types. SAPforms support both form types. With these form types, SAPforms allow you to;

• call up BAPIs and RFC capable function modules,

• start workflows and

• process workitems.

The communication with the R/3 system is synchronously carried out via RFC with BAPI and FB call-up. You can choose between synchronous

call-up via RFC and communication via (Internet) mail when starting the workflow and processing workitems. Communication via mail can be carried out via the SAP MAPI Service Provider or via a server based connection (SAP Exchange Connector, SAP Internet Gateway).

4.) Which types of forms can I use in the Outlook and Exchange Client?

Only Exchange forms can run in the Exchange client. These can be created either in C++, with the Microsoft Eforms Designer (EFD), or with 3rd party products. Using C++ to create them requires extensive MAPI know how. There are examples for this in the MAPI SDK from Microsoft. There is no support for C++ forms by SAPforms.

The EFD is a graphical form painter which can create forms with simple basic functions. EFD delivers a 16 bit Visual Basic project as output, which can be reprocessed with VB4-16. Since there are no add-ons available in VB4-16, using SAPforms Designer for these projects is more involved. Forms created with EFD are very slow, especially when they communicate with 32 bit ActiveX components. SAPforms consist of such components!

There are 3rd party products (for example SAX mPower for Exchange), which make creating 32 bit forms in VB possible. The above mentioned disadvantages are omitted in these cases.

The above mentioned MAPI forms can also run under Outlook. Additionally, Outlook has its own type of form (Outlook forms) that only run under Outlook. Outlook forms are 32 bit and very efficient. They are preferred in pure Outlook environments over the above mentioned MAPI forms. SAPforms support these types of forms since Release 4.5A.

5.) Use of the available MS Exchange Infrastructure?

MS Exchange allows the enhancement of an Exchange Server with links (Exchange connectors, previously known as gateways), that connect other communications services (Internet mail, X.400, Fax, MS Mail, SNAD ... ) to the Exchange Server. The SAP Exchange Connector is also a link of this type, that enables you to make all other Exchange links, such as Internet addresses, X.400 addresses or fax numbers available to R/3 applications or users.

In particular, you can use Internet mail transactions to or from R/3 via the Internet Mail Connector, as well as using certain pre-installed fax software components for fax transfer. Furthermore, it is possible to send mail to or receive mail from exchange mailboxes, by addressing these via the Internet, X.400 or fax address. An address book compare search/display is possible between R/3 and Exchange using LDAP version 3 compatible X.500 access to the Exchange address book information.

Status information is also transferred with a message (such as received or read) assuming the communications service used allows this (for example, X.400 supports received and read, Internet mail does not support either, faxes generally only supports received). Furthermore, several separate R/3 Systems can be linked via one or more Exchange Servers for E-mail transactions, even if no direct RFC link is possible (a so-called backbone). Backbone). Here too, the R/3 users of the other systems can either be addressed via X.400 or Internet addresses (depending on the backbone).

The SAP Exchange Connector, in contrast to the SAP MAPI Service Provider , provides a server connection. The available Exchang infrastructure is used for data traffic to/from R/3, regardless of the client.

With the SAP Web Application Server 6.10 (e.g. used in SAP CRM 3.0), the SAPconnect SMTP Linking should be used instead of the SAP Exchange Connector. It allows an Exchange connection on the server in the same way as described above but has some advantages (e.g. independence of the Exchange and Windows version, lower administration effort, lower installation effort). Exchange Fax connectors can still be used if they support address type SMTP and the fax numbers contained in SMTP (see IETF RFC).

6.) Which functions of the Workflow are supported?

The degree of integration with SAP Business Workflw depends on the Inbox technology used. A closer connection is achieved to SAP Business Workflow with SAP MAPI Service Provider than with Integration via mail. In the following a few points are compared:

SAP MAPI

a) Separate Inbox

b) Processing any work items

c) Processing Work items with special forms similar to the Work item display in R/3

d) Installation on every client is necessary

e) Accepted Workitems disappear from the in-box of other agents.

f) Execution via local forms on the desktop is possible

g) Local forms must be installed on the desktop

h) Starting the Workflow is possible

SAPforms via Mail

a) Sharing the Exchange Inbox

b) Only form based Work items

c) Standard message form with R3F attachment

d) Dito

e) Conflict situations possible

f) Dito

g) A form can automatically be installed from the Exchnge Server

h) Dito

7.) What possibilities do I have for offline processing?

The option for offline processing with forms depends largely on the offline abilities of the mail client where the forms are used. If the mail client allows mails to be created in offline operation, it is also possible to fill out and send a form in offline operation. The Outlook client and Exchange client in connection with the Exchange server for example make this possible.

The Outlook client in connection with the SAP MAPI Service Provider also supports the offline processing of workitems because Release 4.5A. In earlier releases offline processing of SAPoffice messages was already possible. The operations reserve, replace, transfer, change the priority and explicitely end are supported for workitems. Execution via a local form (Update or Outlook) is possible with form based Work items and also decision tasks. Work items that call up a SAPGUI transaction can only be processed in the online operation.

8.) Components and Prerequisites?

• SAP MAPI Service Provider:
  Delivery: With R/3 3.1G on the presentation CD
  R/3 Release: 3.1G upwards. For pilot customers and testers
  former Release (3.0D/1 and 3.0F) on request
  since 4.5A: Workflow Offline, Outlook Form
  Operating system: NT4.0, Win2000, Win XP
  Mail clients: OL98, OL2000, OL2002

• SAPforms:
  Delivery: With R/3 3.1G on the Presentation CD
  R/3 Release: 3.1G upwards
  Operating systems: All Windows 32 bit/Intel platforms
  Types of Forms: Visual Basic
  since Release 4.5A: Outlook, Word, Excel
  Mail Clients: MS Outlook, MS Exchange, Internet Mail
  (IExplorer), etc.

• SAP Exchange Connector (SXC):
  Delivery: see Note 122657
  Mail clients: not dependent
  R/3,NT and Exchange: For Release dependencies see Note 122657

9.) Where can I find current information on the components?

• SAP MAPI Service Provider:
  White Paper "Communication Services in the SAP Sytem R/3"
  Notes 62431
  User documentation 3.1G
  SAPInfo article in SAPInfo 1/1997
  mapifaq.htm in the installation directory of SAP MAPI

• SAPForms:
  SAPInfo article in SAPInfo 51/1996, user documentation 3.1G
  SAPforms Whitepaper order number 50021701 (English), 50021663(German)
  Exchange and R/3: Blueprint can be found under
  http://www.microsoft.com/industry/erp/sap/downloads/downloads1.asp

• SAP Exchange Connector:
  User documentation on the Presentation CD (see Note 122657 for path information) and in the R/3 online help.
  SAPNet R/3 frontend under the BC-SRV-COM-MSX component

Version Overview and History

SAP Web Application Server Version 6.10 or higher using any Exchange and Windows Version:

If you are using an SAP system based on the SAP Web Application Server (WAS) Version 6.10 or higher (for example, SAP CRM 3.0), then you should use the SAPconnect (E)SMTP linkage for the exchange connection.You no longer need to install the SAP Exchange Connector.You can therefore decouple the links in a more stable way (for example, no dependencies to the Exchange or Windows versions, no dependency to the Windows domain structure and account structure used) as well as lower administrative and installation effort.

For more information, see notes 455127 and 17194. 455127, 17194

As with all SAPconnect RFC connections provided by SAP (SAP Internet Mail Gateway, SXC), maintenance for the SXC will be completed at the same time as maintenance for SAP Basis 4.6C or SAP Basis 4.6D.SAPconnect RFC will no longer be supported as of SAP Web Application Server Version 7.x.After that, you can avail of the modern and SAP-independent communications log (introduced with 6.10 and 6.20) with SAPconnect (E)SMTP and HTTP interfaces.

SAP R/3 up to 4.6D, Exchange 5.5 under NT4 and Windows 2000:

Use the current SXC Version 1, for example, SXC 1.54. You cannot use the SXC Version 2, for example, SXC 2.00, with Exchange 5.5.

The version is delivered on the SAP Presentation CD. Path:GUI\WINDOWS\WIN32\SXC. First unpack and read the documentation in GUI\WIN32\SXC\DATA\PROGRAM\MANUAL.EXE.

SAP R/3 up to 4.6D, Exchange 2000 under Windows 2000:

Use the current SXC Version 2, for example, SXC 2.01 with patch 2.03. You cannot use SXC Version 1, for example, SXC 1.54, with Exchange 2000.

The version is delivered on the SAP system components CD as of Release 6.20

Enhanced versions or advance versions are available via ftp on the sapservx machines (see also note 73360).In this case, the dependencies to the SAP System and Exchange are listed.Some of the hot fixes mentioned are no longer available from Microsoft.In this case, change to the next higher Exchange version.

Version overview:

1. SXC Version 1.0 delivered with R/3 3.1G, for Exchange Server 4.0 Support Package 3, R/3 3.1G, NT 4.0 Support Package 3

2. SXC Version 1.1 delivered with R/3 3.1H and 3.1I, for Exchange Server 4.0 Support Package 4 with Hotfix "Hotfix Q167132 - post Support Package 4 store", R/3 3.1G to 3.1I, NT 4.0 Support Package 3

3. SXC Version 1.2 delivered with R/3 4.0A, for Exchange Server 5.0 with Support Package 1 and MS hotfixes

• "Hotfix HF39311 - Store and Named Properties" Service Request (SR) no.:SRZ970605000931,

• "Hotfix HFE3627 - IMC and Extension-DLL" Service Request (SR) no.:SRZ970605001183,

• "MTA Fix 1459.46 - Address transfer in MTA" Service Request (SR) no.:SRD971015000038
  (While HF39311 and HFE3627 are absolutely necessary, you do not need the MTA Fix.) or alternatively, Exchange 5.5 without a Support Package.

The R/3 Systems can be 3.1G to 3.1I and 4.0A, NT 4.0 Support Package 3.

4. SXC Version 1.21 delivered with R/3 4.0B, for Exchange Server 5.5 without a Support Package and R/3 3.1G to 3.1I as well as 4.0A to 4.0B, NT 4.0 Support Package 3.
Changes to 1.2:

• MS Exchange DLLs are no longer contained in the delivery.You must therefore install the Exchange Administrator first as well as an Exchange client (for example, Outlook) on the installation machine.

5. SXC Version 1.3 delivered with R/3 4.5A, for Exchange Server 5.5 Support Package 1 and R/3 3.1G to 3.1I, 4.0A to 4.0B and 4.5A, NT 4.0 Support Package 3
Note: If possible, install SXC 1.31, see below, or perform an update.
Changes to 1.21

• Double byte character set support, for example, for Shift-JIS

• From: Addresses are also expanded against custom recipients

• X.400 address attribute sequence adjusted to Exchange specifications

• To:Addresses also contain R/3 internal recipients if they do not have an email address of the address type used.

6. SXC Version 1.4, delivered with R/3 4.5B, for Exchange Server 5.5 Support Package 1 up to Support Package 2, R/3 3.1G up to 3.1I, 4.0A up to 4.0B, 4.5A up to 4.5B, NT 4.0 Support Package 3 up to Support Package 4.
Changes to 1.3

• Handbook contains sketches

• RfcOut service no longer exits when the R/3 System is exited.

• Performance improvement

7. SXC Version 1.31, only delivered via ftp/sapservx for Exchange Server 5.5 Support Package 1 and R/3 3.1G to 3.1I, 4.0A to 4.0B and 4.5A, NT 4.0 Support Package 3.
Changes to 1.31

• Greatly simplified setup with value check and enhanced log file

• Remove SXC (Uninstall) function in the setup.exe

• Problem elimination for double byte character sets (Kanjii)

• Time zones

• Simplified RFC parameter maintenance (saprfc.ini no longer required)

• SFX box can be changed to any recipient address container

• Set missing attributes for status reports (for example, subject)

8. SXC Version 1.41, delivered with R/3 4.6A, for Exchange Server 5.5 Support Package 1 to Support Package 2, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A, NT 4.0 Support Package 3 to Support Package 5.
Changes to 1.4

• The new 4.6A librfc32.dll and the system DLLs used there are included.

• The Readme is improved

• Important:An update of existing 1.4 installations to 1.41 is not required as you can continue to use the old librfc32.dll.This version is therefore not supplied via ftp and sapservx.

9. SXC Version 1.41, delivered with R/3 4.6A, for Exchange Server 5.5 Support Package 1 to Support Package 2, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A, NT 4.0 Support Package 3 to Support Package 5.
Changes to 1.41

• Msvcrt.dll removed from the setup as this, in general, is locked by NT during the setup.If an older version of the msvcrt.dll is available on the host (recognizable by the error "invalid entry point in msvcrt.dll" at the start of the SXC), this can be imported using a <CD disk drive>:\GATEWAY\NT\I386\NTPATCH\R3dllins.exe.

• Errors in time and date specification corrected in status messages.

• Controllable through NT registry settings conversion of text attachments (see note 170209).

• Additional log file output (text attachments before/after conversion, status message creation)

10. SXC Version 1.5, delivered with R/3 4.6D, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6.
Changes to 1.42

• sapsxcie.dll enhanced:via the "EL_NoAutomaticReroute ON" flag in the imcroute.cfg, you can prevent messages to receivers with unknown domains from being routed back into the Internet (see also note 177867).

• You try to set all types of attachment names (display name, attachment name, file name and so on) to the original file name of the attachment which existed when uploading to R/3.If the original name is too long for one of the name fields, the name is shortened as normal (for example, toolongname.doc toolon~1.doc).

11. SXC Version 1.5, delivered with R/3 4.6D, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6.
Changes to 1.43

• Improvements in the setup (NT user check, exchange server check, logging)

• Improvements for time and data conversion

• Connection to the SAPconnect trace and status management

• Explode embedded messages in attachments

• Removal of same recipients from the recipient list

• Changing restriction handling and thus removing registry modifications

• Conversion of new SAPoffice text attachment types

12. SXC Version 1.51, only delivered via ftp, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6.
Changes to 1.5

• Exchange Administrator enhancement (Exchange Admin DLL, sapsxcae.dll) of the SXC in the area of time zone selection is improved.

13. SXC Version 1.52, delivered via ftp only, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6.
Changes to 1.51

• Improvement for body text.With text attachments such as notepad texts (.TXT), special characters are no longer removed (exchange to R/3).As the body text, text attachment extensions are assumed whose line length has a maximum value of 255 (for example, TXT).SXC Version 1.53, only delivered via ftp, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6, Support Package 6a.

• Various errors in the area of text attachment and messages were corrected (only line feed instead of carriage return line feed in the message text, however, carriage return line feed in the text attachment, adjustment of the attachment length with character set conversion, correct initialization of text attachment lines in accordance with the R/3 codepage).

14. SXC Version 1.53, only delivered via ftp, for Exchange Server 5.5 Support Package 3, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, NT 4.0 Support Package 6a.
Changes to 1.52

• Changing the MAPI attribute PR_RTF_COMPRESSED to PR_BODY for the message text (message body).You therefore avoid the MAPI_E_NOT_ENOUGH_MEMORY error in the SXC gateway.If you want to drive double or multi-byte character sets, you have to set a registry value:
  "HKLM\System\CurrentControlSet\Services\MSExchangeSXC_GW_<number>\ Parameters\SAP Exchange Connector\Use RTF Body", Type DWORD, value =1.
  Adjustments to Windows 2000 Support Package 1. The use of SXC 1.54 is therefore released for the Windows 2000 Mixed Mode Security Model.
  The underlying error for this workaround is eliminated in later versions.However, if the MAPI_E_NOT_ENOUGH_MEMORY error occurs in the gateway log (other symptom:messages in R/3 have a subject and a recipient but no message text), the value "Use RTF Body" must be set to "0" again.

15. SXC Version 1.54, delivered via ftp and R/3 6.10, for Exchange Server 5.5 Support Package 3 to Support Package 4, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, 6.10 to 6.20, NT 4.0 Support Package 6, Support Package 6a, Windows 2000 Support Package 1, Support Package 2.
Changes to 1.53

• Adjustments for Windows 2000 Support Package 1. In this case, the use of SXC 1.54 is released for Windows 2000 Mixed Mode Security Model. Use of SXC 1.54 in the Native Mode Security Model is not tested and not released.
  However, you can choose whether the SXC is installed in a root domain or in a child domain within the mixed mode model.

• Corrections and changes to codepages that are different to ISO-8859-1 ("Latin1").For example, tests were run against Greek (ISO-8859-7) and Japanese (Shift Jis) character sets.We urgently recommend that you update to SXC 1.54 if you are using character sets that are different to ISO-8859-1.Outlook 2000 was used as an exchange client for the test.We cannot guarantee that older Outlook versions (Outlook 97 or 98) are able to correctly display the Unicode characters in the subject or message text (body).You are therefore required to update to Outlook 2000. (For more details, see OSS note 381028). (Details s. OSS note 381028)

• Enhancement of the text conversion settings (specifying the expected character set in the incoming case, specifying the character set for the outbound).

• Elimination of smaller program errors.

16. SXC Version 2.00, only delivered via ftp, for Exchange Server 2000 Support Package 2 (however, not defined as an Exchange front-end server, R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, SAP WAS 6.10 up to 6.20, Windows 2000 Support Package 2
Changes to the SXC 1.x versions:

• SXC 2.0 is an SXC version for Exchange 2000, large parts of which have been newly developed. You should therefore refer to the SXC 2.00 handbook for information on the changes over earlier versions.

• Note that SXC 2.00 for Exchange 2000 Support Package 2 is released for productive use, because only Support Package 2 eliminates an exchange error that up to Support Package 1, prevents the message ID from being transferred to status messages and consequently the status assignment in the SAP system.Contact Microsoft directly with regard to the delivery of Exchange 2000 Support Package 2.

• Note that you should not run the SXC 2.0 on an Exchange 2000 front-end server (even though this does not make sense and contradicts Microsoft's recommendations for a front-end server).

17. SXC Version 2.01, delivered via ftp, on SAP 6.20 System Components CD as well as via the Service SAP Marketplace (last is in preparation), for Exchange Server 2000 Support Package 2 - Support Package 3 (but not designated as an Exchange front-end server !), R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, SAP WAS 6.10 to 6.20, Windows 2000 Support Package 2
Changes to SXC 2.00:

• The setup tool was changed from InstallShield to SAPSetup 6.20. Note here that you have to uninstall the already existing SXC 2.00 version and install it gain using the SXC 2.01 setup.

• Correction for the problem according to note 502094

• Correction for the problem according to note 502098

• File version overview:
  CsObjPck.dll 1.0.0.0
  CsSearch.dll 1.0.0.0
  CsSvcMgr.dll 1.2.0.0
  CsTzMgr.dll 1.0.0.0
  SapSxcGw.exe 2.0.0.0
  SapSxcIn.exe 2.0.0.0
  SapScxMg.dll 2.0.0.0
  SapSxcMv.exe 1.4.0.2
  SapSxcOi.dll 2.0.0.0
  SapSxcOu.exe 2.0.0.0
  SapSxcTo.dll 2.0.0.0
  SxcAdmin.ocx 1.0.0.2
  SxcSvcMgr.dll 1.0.0.0
  SxcTrace.dll 1.1.0.0

18. SXC Version 2.02, delivered via ftp, for Exchange Server 2000 Support Package 2-Support Package 3 (but not designated as an Exchange front-end server), R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, SAP WAS 6.10 to 6.20, Windows 2000 Support Package 2
Changes to SXC 2.01:

• Improved error output for incorrect time zone definitions in the NT/Windows system.

• Correction for the problem according to note 515329

• File version overview:
  CsTzMgr.dll 1.1.0.0
  SxcAdmin.ocx 1.0.0.3

• If you want to uninstall the SXC, first uninstall this patch with:
  sapsetup /uninstall /p:"{ABB97D97-233E-42b1-8F2B-5A6CEB5F2490} "
  called on the command line in the setup directory of the SXC 2.01 Setup package.

19. SXC Version 2.03, delivered via ftp, for Exchange Server 2000 Support Package 2 - Support Package 3 (however, not defined as an Exchange front-end server), R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, SAP WAS 6.10 to 6.20, Windows 2000 Support Package 2 - Support Package 3.
Changes to SXC 2.01:

• All corrections from SXC 2.02, this is therefore a cumulative patch, you do not need to import the previous patch 2.02.

• Corrections in the display of non-Latin1 characters in the Exchange System Manager SXC administration interface.

• File version overview:
  CsTzMgr.dll 1.1.0.0
  SxcAdmin.ocx 2.0.0.3

• If you want to uninstall the SXC, first uninstall this patch with:
  sapsetup /uninstall /p:"{ABB97D97-233E-42b1-8F2B-5A6CEB5F2490} "
  called on the command line in the setup directory of the SXC 2.01 Setup package.

20. SXC Version 2.04, delivered via ftp, for Exchange Server 2000 Support Package 2-Support Package 3 (however, not defined as an Exchange front-end server), R/3 3.1G to 3.1I, 4.0A to 4.0B, 4.5A to 4.5B, 4.6A to 4.6D, 5.00, SAP WAS 6.10 until 6.20, Windows 2000 Support Package 2-Support Package 3.
Changes to SXC 2.01:

• All corrections from SXC 2.02 and 2.03 (cumulative patch). Therefore, you do not need to implement the 2.02 and 2.03 SXC patches.

• Activated message tracking in the Exchange 2000 Server causes an MAPI_E_CALL_FAILED error in the SXC. This is due to an incompatible change in the Exchange 2000 Server Support Package 3 in the area of the RPC Server.

• If you want to uninstall the SXC, first uninstall this patch with: sapsetup /uninstall /p:"{ABB97D97-233E-42b1-8F2B-5A6CEB5F2490} " called on the command line in the setup directory of the SXC 2.01 Setup package.

Note the following restriction when using the SXC with Exchange 5.5:

If messages are transported via X.400 backbone (for example, two R/3 Systems communicate via two Exchange Servers via X.400 log) and no directory synchronization is made between the backbone Exchange Servers, (non-) receipt and (non-) read confirmations are not transmitted successfully because the SAP Exchange Connector of the Exchange Server contains exchange names as sender and recipient addresses rather than X.400 addresses.