Skip to Content
Since SAP is the industries most respected information system hence its integration with the organizations messaging system is essential for leveraging organizations performance and productivity. With this article I am going to explain the setup of SAP R3 4.6C or SAP R3 4.6D environment for email collaboration with Microsoft Exchange Server 2003 with Service Pack 2 using SAP Exchange Connector 2.11/2.12. The prerequisite of getting all this up and running is a R3 and a MS Exchange Server 2003 environment.

Step 0: Downloading the SAP Exchange Connector

    Download the SAP Exchange Connector from

      Start a browser with the above URL and click in the left frame on SAP Support Packages and Patches

      ->Entry by Application Group

      ->Additional Components

      Then change to the right frame and click on


      Under SAP EXCHANGE CONNECTOR 2.00 -> Win32 you will find the SXC 2.12 for Microsoft Exchange 2003 Server.

      1. Unzip the RAR/ZIP file and you should get the directory structure as show in Figure 1. 


      Figure 1: SAP Exchange Connector 2.11 Directory Structure

       Step 1: Installation Exchange Connector on Your Windows 2003 Exchange Server.

      1. Logon to the Exchange 2003 Server with the account used for installing the Exchange Server 2003.
      2. Access the directory where you have unzipped the SAP Exchange Connector Installation Files

      Execute the *SXCSETUP.EXE, it’s a 2 step process e.g. Next and Finish</li><li>Click Next </li><li>Click Finish</li><li>The SAP Exchange Connector is now installed on you machine Go to Start-> Control Panel ->Add/Remove Programs , in the installed program list look for program titled “SAP Exchange Connector” to verify the installation. </li></ol><p>Step 2: Adding the SAP Exchange connector in Microsoft Exchange Server 2003.</p><ol><li>Open Exchange System Manager</li><li>Go to Routing Group-> Connectors  or  Go to Connectors </li></ol><p>!|height=397|alt=|width=576|src=!<br />Figure 2: SAP Exchange Connector Path in Exchange 2003 System Manager.</p><ol><li>From Connectors Go to New-> SAP Exchange Connector on selecting  SAP Exchange Connector from the menu you would get Installation Properties window</li></ol><p> !|height=566|alt=|width=410|src=!<br />Figure 3: SAP Exchange Connector 2.11 Installation Properties Window.* 

      The connector by default picks up all the field values based on your exchange server settings .It is recommended that you keep the settings to default and only change the Gateway, RfcIn and RfcOut service name if you don’t like the ones already recommended.

        1. Click OK .You have just added the connector to you Exchange environment. 

      Step 3: Configuring SAP Exchange Connector Gateway Service In Exchange System Manager.

      Caution the only difficulty I faced while configuring SAP Exchange Connector in 2003 is the invocation of properties window all the connector components but you need not to worry as after 1,2 tries of left and right click you do get the properties window.

      1. Go to Exchange System Manager ->Connector

      Here you would see your newly added SxcGw Connector.From the right pane select  SxcGw and right click for properties


        Figure 4: Accessing SAP Exchange Connector 2.11 Gateway Service Properties. 

        1. Select Properties option

        In the SxcGw properties window you would need to maintain 3 tabs Gateway , Services and  Address Space

        In the Gateway tab  you just need to maintain the code page notation for R/3 in NT and R/3 in R/3, run RSPARAM Report in R/3 and look for “parameter installed/codepage/appl_Server” value as for my environment its was 1100 , leave the NT notation to default.


          Figure 5: Setting Up Gateway Properties for SAP Exchange Connector Gateway Service 

          In Services Tab you just need to maintain the User-Id and Password of the account that was used for installing the Exchange Server 2003, the *User-Id *format is as follows <Domain Name>\<User-Id>.


            Figure 6: Maintaining Service Account Details For SAP Exchange Connector 2.11 Gateway Service 

            1. In Address Space Tab, press Add Button.

            In the popup window “Address Space Properties” set the following values

            Type = SMTP

            Cost = 1

            Address = **</li></ol><p>Tip:</p><p>Remember that all emails generated from SAP R3 are treated as SMTP emails. Hence if in your setup you already have an Internet email connector configured at Exchange Server 2003 (which I am sure would be the case) then you would have to restrict the Sap Connector address space (SxcGw->Properties->Address Space*)  to only facilitate emails from SAP system E.g. SxcGw->Properties->Address Space =


            Figure 7: Maintaining Address Space in Gateway Service 

            1. Select Ok to complete Gateway Service Configuration. Go to Step 4 

            Step 4: Configuring SAP Exchange Connector RFCIn Service In Exchange System Manager

            Expand the SxcGw from the left pane to get the 2 service container RfcIn and RfcOut

            Now from the left pane select RFCIn Service container and from the right pane select the service and its properties.


              Figure 8: Accessing RFCIn Service Properties Window 

              In the properties window starting from RFC tab select option “Use Application Server “, enter you application Server Name and System Number. In* *the Logon Portion at the bottom of the windows enter R3-Client,Language, User-Id and Password.

              The User-Id you mentioned here would have the authorization for communication with SAP Connect SAP profile S_A.SCON.The best option is to create a separate account with user type system and assign it the SAP profile S_A.SCON.In my example I have used the account by the name of mail_admin 


                Figure 9: RFCIn Service RFC Configuration Window. 

                Now go to the “Service Tab” and maintain the service account details similar to that used in during the configuration of “SxcGw->Service” tab “Step 2(g) Figure 6”.

                Select Ok on Service Tab to complete the configuration of RFCIn Service. 

                  Step 5: Configuring SAP Exchange Connector RFCOut Service In Exchange System Manager.

                  Now from the left pane select RFCOut Service container and from the right pane select the service and its properties.

                  In the RFC Tab of the properties window select the option “Register at SAP gateway” and enter the gate way Server name which in the current scenario is the Application Server name you had entered in the RFCIn RFC Tab “Step 4(b) Figure 9.

                  Enter the gateway service sapgw00 which is the default gateway service running on each SAP Application Server.

                  Now enter the program ID, it could be any name that please you. In my example I would be using name RFCOUT03 The MS Exchange 2003  and R3 uses this program to  send email to and fro between these systems


                    Figure 10: RFCOut Service RFC Configuration Window. 

                    Now go to the “Service Tab” and maintain the service account details similar to that used in during the configuration of “SxcGw->Service” tab “Step 2(g) Figure 6. Select OK to complete the configuration of RFCOut Service.

                      Step 6: Starting SAP Exchange Connector Services In Exchange System Manager.</p><ol><li>Now from the left pane select Connector, and from the right pane select SxcGw Gateway Service and right click for properties and select the option “Start All Components“.</li></ol><p></p><p>Figure 11: Starting SAP Connector Services </p><ol><li>This would three services on you Exchange Server. You can go to MyComputer->Manage->Service and Application->Services to look for 3 services SxcGw, SxcRfcIn and <strong>SxcRfcOut</strong>. If all three services are running successful then you are Ok to go to the next step.</li><li>You have now successfully configured the SAP Exchange connector in MS Exchange 2003. </li></ol><p>Step 7: Verifying SAP Connector Service Registration With SAP Gateway In SAP R3 Environment.</p><ol><li>Logon to your R3 system mentioned in the Exchange connector configuration </li><li>Go to T-Code “SMGW”. Gateway monitoring and would see you service registered on to you SAP gateway. </li></ol><p>!|height=107|alt=|width=575|src=!</p><p>Figure 12: Registered Exchange Connector Service With SAP R3 Gateway. </p><p>Step 8: Creating RFC In SAP R3 Environment For Collaboration With SAP Exchange Connector Service. </p><ol><li>Go to T-Code *”SM59″ *RFC Maintenance Screen.</li><li>Click the “Create” button.</li><li>In the RFC creation screen maintain RFC Name,<strong>RFC Type = “T”</strong> ,*Description *and <strong>Logon details</strong> (language, user-id ,password and client) you can use the same User-Id and <strong>Password</strong> and other details used in the Exchange connector configuration RFCIn “<strong>Step 4(b) Figure 9</strong></li><li>Press Enter and Select the Registration Button. </li></ol><p>!|height=610|alt=|width=562|src=!</p><p>Figure 13: Create RFC in SAP R3 Environment </p><ol><li>In the registration window set the program ID value = “RFCOUT03“, the one used in the RFCOut Configuration of Exchange connector “Step 5(d) Figure 10.</li><li>Select Save and then Test Connection. If the connection is successful you would be viewing the following connection test window.</li></ol><p>!|height=152|alt=|width=434|src=!</p><p>Figure 14: RFC Successful Connection Test Output </p><p>Step 9: Creating SMTP Node In SAP Connect Administration Interface. </p><ol><li>Now Go to T-Code *”SCOT” *</li><li>In SCOT transaction go to Settings->Communication Methods, all communication method that you want to use MS Exchange 2003 service should be set the value “SAP Connect”. In our example we would be using INT (internet) method.</li></ol><p>!|height=262|alt=|width=575|src=!</p><p>Figure 15: Setting SAP Connector as Default Method for INT Message Type</p><ol><li>Click back button (F3) to go to system view of SCOT transaction.</li><li>Now from the system view select “Create”.</li><li>In the create screen enter node Name (max 6 characters) and Description.</li></ol><p>!|height=520|alt=|width=478|src=!</p><p>Figure 16: Create RFC in SAP R3 Environment</p><ol><li>Press Continue.</li><li>Select RFC create in “Step 8(c)” “<strong>RFC_SAP_Exchange</strong>” and click Continue.</li><li>Select node Internet(INT) under which new SMTP node would reside</li></ol><p>!|height=522|alt=|width=481|src=!</p><p>Figure 17: Create RFC in SAP R3 Environment</p><ol><li>Click Continue</li><li>In the address space window enter the address space “* and click Continue.</li></ol><p>!|height=521|alt=|width=480|src=!</p><p>Figure 18: Create Address Space Supported By SMTP Node </p><ol><li>In the format window select “All formats“. These would be the format in which the message and its attachment would be transmitted to and fro b/w the 2 system.</li></ol><p> !|height=521|alt=|width=477|src=!</p><p>Figure 19: Select Message Format Supported By SMTP Node </p><ol><li>Select Device type POSTSCPT, if in the previous screen you have only selected support format TXT then you can select Device type ASCIIPRI. Press Continue button.</li></ol><p>!|height=521|alt=|width=479|src=!</p><p>Figure 20: Select Device Type Supported By SMTP Node</p><ol><li>Select No and click button Continue.</li><li>Enter the time duration after which the system tries to send the message again if an initial failure as occurred in sending the message.Press Continue button. </li><li>In the new window select “N” option and click Continue button.</li><li>In the next window enter waiting time after which the system would try to resend the message if failure has occurred during the first attempt.</li></ol><p>!|height=521|alt=|width=480|src=!</p><p>Figure 21: Set Waiting Time for Repeat Message Send Attempt </p><ol><li>In the next screen select option if you want to monitor node activity or if node is able to resolve path references. For the current example do not select both options and press the Continue button.</li><li>In the next window select the option “Node in use” and “Node support connection test status and support“. Click Yes if prompted to carry out test now.</li></ol><p>!|height=521|alt=|width=478|src=!</p><p>Figure 22: Activate and Test SMTP Node. </p><ol><li>After a connection test click Continue button to complete the configuration of SMTP Node within the INT node  </li></ol><p>Step 10: Scheduling Job For SMTP Node For Message Sending And Receiving Activity. </p><ol><li>Select the node SMTP and Go to View->Jobs</li><li>Press create button and enter Job Name </li><li> Select job variant “SAPConnectInt” and Click Schedule</li><li>In schedule enter start date and time and click Schedule periodically and select minutes and enter value 3 click Create. You have schedule the mail sending and receiving activity of sap with MS Exchange Server 2003.</li><li>Goto T-code SU01 and in Address Tab maintain the users internet address in the user maintenance screen like say **

                      You can now test the new setup configuration by going to SAP Office T-Code SBWP.

                        1. Create New Message, enter subject and body in the Recipient list enter the email address any user on your Exchange 2003 and select recipient type = Internet Address and Click Send.

                       Goto T-Code SCOT and you can see a message under waiting column for node INT. Message would be send when the job for the node is executed which in our example would be by 3 minutes.  


                        Figure 23: Create RFC in SAP R3 Environment 


                        With this article you have successful setup the R3 4.6C or 4.6D and MS Exchange 2003 collaboration for Email Exchange. I have discussed in detail each steps required for configuration of SAP R3 environment as well as SAP Exchange Connector on MS Exchange Server 2003. The current configuration settings are feasible for most organizations running MS Exchange 2003 and SAP R3 4.6C or 4.6D.


                        To report this post you need to login first.

                        1 Comment

                        You must be Logged on to comment or reply to a post.

                        Leave a Reply