Page tree
Skip to end of metadata
Go to start of metadata

Installation Procedure of a basic SAP Conversion Server

Usually, customers buy Conversion Servers from a third party which caters to their requirements. However there is also a basic conversion server provided by SAP. It has a lot of limitations like for example; it cannot convert all originals in a document structure.

Some sample files can can be found as attachment to this page. These files are already older and if you face problems with extracting them please get in contact with 3rd party conversion server vendors like SEAL Systems for example.

The files that need to be downloaded are in the file contents.txt. Please read the same and then download all of them. For WinNT in general the files required are as below. Ensure that you are downloading the latest versions of all the required files.

  • docu.4.sar
  • source.5.sar
  • NTintel/ConvUtil.6.SAR
  • NTintel/ConvServSamp.6.SAR
  • NTintel/bat.3.SAR
  • NTintel/sleep.SAR
  • NTintel/sapftp.SAR
  • NTintel/librfc32.dll.SAR

The SAR files are special kinds of files. They are generally equivalent to zip files. Hence they need to be extracted before we can install the conversion server. Just like .zip files require a WINZIP utility, .SAR files require a utility to extract them. This utility is in the form of an executable SAPCAR.exe. This SAPCAR.exe is available in the same site for download. The next step is to extract all the .SAR files. For this, you need to go the command prompt (Windows Start Menu > Run > 'cmd'). Here go to the appropriate directory and execute the command SAPCAR -xvf docu.4.SAR. Similarly for all the .SAR files execute the above steps and extract all the .SAR files. Once the extraction is done, ensure all files are in place. The significance of the files and programs is as below.

Conversion Server Files and Programs Architecture

When you start the conversion server you actually run the batch file RunConvUtil.bat in the external system where the conversion takes place. This batch file triggers the executable ConvUtil.exe as shown in the figure below (ConvUtil.exe is the binary executable generated from the C program ConvUtil.C). The RunConvUtil batch file starts the ConvUtil.exe which runs the saphttp and sapftp programs on the server machine which waits for requests from clients (in our case the applications servers are the clients) for conversion. ConvUtil.exe is the executable generated from the source program ConvUtil.c. The header file for ConvUtil.C is ConvUtil.h.

  • RunConvUtil.bat started manually
  • RunConvUtil triggers ConvUtil.exe 

Then when you run trigger conversion from R/3, the files which get triggered in the converter is as shown below. 

The batch file ConvServ.bat starts the RFC Server Program ConvServSamp.ConvServSamp is the RFC Server program which communicates with the converter and the R/3 application server.Information for the conversion is transferred from the SAP System to the program ConvServSamp using the RFC destination. ConvServSamp stores the information as files on the conversion server and starts a shell-script file (in this case: StartConv) with its own parameters. The shell-script file (in this case: StartConv) calls the converter (example: All2txt.bat) using the syntax for the converter.

Customizing Settings in R/3 for Conversion

Before looking into how a conversion server works we need to understand the settings that need to be done prior to using the conversion server.
Post Installation of the conversion server, the details are to be maintained in transaction SPRO and SM59.

Set up a TCP/IP Connection to the Conversion Server through SM59:
In the definition phase, we need to give all the details of the conversion server. We also need to go to sm59 transaction and then create a new TCP/IP (RFC) destination, configure the Gateway Service, Gateway Host etc to our conversion server and finally test the same. The parameters to be defined are as below:



SAP Gateway:

An SAP Gateway is installed on each Application Server. To see the list of all application servers for any R/3 system, (example for U9C), execute transaction SM51. To see all the Gateways connected to the SAP system, execute transaction SMGW.

Gateway Host:

Choose one of the app servers as the Gateway Host.

Gateway Service:

It usually takes the format < sapgw><system number>.
System number can be obtained from the SAP Logon pad by choosing the system and then viewing the properties.

Program ID:

Anything of your choice.

Next step is to make the modifications to RUNCONVUTIL.BAT file in the conversion server.
Modifications to RUNCONVUTIL.BAT (mandatory step):



Gateway Host: 

same as configured in SM59

Gateway Service:

same as configured in SM59

Program ID:

same as configured in SM59

Test TCP / IP connection to Conversion Server from R/3:

Run the conversion server. For this you need to run the batch file RUNCONVUTIL.BAT on the conversion server. This registers the Program Id on the Gateway.
Then in transaction SM59 in R/3, perform a TEST CONNECTION.
If everything is fine, you will get a success message else you get a error message.

Then you have to maintain also the configuration which need to be done in SPRO and define the Conversion Server here.

Define Conversion Server

As in the above screen shot, fill the values for Converter Name, the Converter Number and the Conv Help Prog. Leave the Conv Destination field blank and other destination fields blank. The program automatically computes the RFC destinations for the other fields. This concludes the definition phase. 


1 Comment

  1. Unknown User (m0cwbyt)

    Hello, any information on where SAR files could be downloaded ?

     Provided link is not working anymore