Microsoft. NET data provider for mysap Business Suite

Microsoft. NET data provider for mysap Business Suite, preview version

SQL Server 2005 supports using Microsoft. NET data provider for mysap business suite to access SAP data. You can use this interface to create an integration services package that can be connected to the mysap Business Suite solution, and then execute commands that can access data through the support interface. You can also create a Reporting Service Report based on the server running mysap business suite.
You can use Microsoft in the SQL Server Import and Export wizard and various integration services functions (including script tasks, datareader source components, and script components. NET data provider for mysap business suite, and data processing extensions can be used in reporting services.
SQL Server 2005 does not include Microsoft. NET data provider for mysap business suite. According to the license terms, this preview version is used as the pre-release software authorization. For more information about the prerequisites for using Microsoft. NET data provider for mysap Business Suite, see the README file contained in the downloaded file.

Http://download.microsoft.com/download/8/6/c/86c36c26-2532-4d02-87cc-d0208f9cbaaa/DataProviderSAP.exe
I am stupid when I see 4.2. I am not basis.

4.2 install RFC

To install these two RFC versions, follow these steps:

1. Copy files from the computer running SQL Server to the SAP application Program Server

1. Log on to the SAP application server of the development system as the sap r/3 system administrator.

2. RenameK9 *. bi1From the installation directory on the computer running SQL Server to the following directory on the SAP application server:

   Drive: \ USR \ sap \ trans \ cofiles

3. RenameR9 *. bi1From the installation directory on the computer running SQL Server to the following directory on the SAP application server:

   Drive: \ USR \ sap \ trans \ data.

2. Load the transmission to the transmission buffer on the SAP application server.

1. At the command prompt, go to the following transfer program directory on the SAP application server:

   Drive: \ USR \ sap \ trans \ bin

2. To load the transmission to the transport buffer, go\ USR \ sap \ trans \ binDirectory, and replace it with the System ID of your development system.Sysid:

   TP addtobufferTransportnumber SysidPF = tp_domain _Sysid. PFL

   WhereTransportnumberIs the actual transfer number (for example, bi1k900201 ).

3. TPAfter the command is executed, you will see a report containing similar information:
   

   This is TP version 320.56.66 (release 620)
   Addtobuffer successfulTransportnumber
   TP finished with return code: 0

   ReturnCode"0" indicates that everything goes well.

   The acceptable return code is 0 or 4. If the response code you receive is 8 or larger, contact Microsoft Product Support Service (PSS.

   Note:: You can easily export the actual transfer number from the cofile file name. For example, the transfer number provided by cofile named k900201.bi1 is bi1k900201.

3. Import the transmission to sap

2. Run the following command at a command prompt:

   TP ImportTransportnumber SysidClient =ClientnumberPF = tp_domain _Sysid. PFL

   Replace with the System ID of your development systemSysid. Replace it with the client number of your development systemClientnumber.

   You can use the U2 parameter to override the previously installed object, as shown below:

   TP ImportTransportnumber SysidClient =ClientnumberU2

   -Or-

   TP ImportTransportnumber SysidClient =ClientnumberPF = tp_domain _Sysid. PFL U2

   Note:: You can easily export the actual transfer number from the cofile file name. For example, the transfer number provided by cofile named k900201.bi1 is bi1k900201.

4. TPAfter the command is executed, you will see a report containing similar information:
   

   This is TP version 320.56.66 (release 620)
   This is r3trans.exe version 6.08 (release 620-04.02.03-14:54:00 ).
   R3trans.exe finished (0000 ).
   This is r3trans.exe version 6.08 (release 620-04.02.03-14:54:00 ).
   R3trans.exe finished (0000 ).
   TP finished with return code: 0

   The return code "0" indicates that everything went well.

   The acceptable return code is 0 or 4. If the response code you receive is 8 or larger, contact Microsoft Product Support Service (PSS.

4. Check transfer logs

Use transaction SE09 to check the transfer logs in sapgui transport organizer to confirm that there are no errors.