We have Data Integrator 11.7 installed in a Windows Machime and we are trying to connect to SAP R/3 in an Unix Server.
We have tested the connection to the SAP R/3 aplication server and SAP GUI works fine from Data Integrator Server.
However, we create the R/3 Data Store in DI with the R3 aplication server adress, user, password, R3 client and R3 system number as shown in the SAP GUI connection and we receive the error shown in the attached file:
We have looked in the dev_rfc.trc file and we see the following probem:
**** ERROR file opened at 20081028 115002 Romance Standa, SAP-REL 640,0,55 RFC-VER 3 717389 MT-SL
T:2080 ======> Client AC1 is not available in this system
T:2080 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
But this client is the client used in SAP GUI for connecting to SAP R/3!!
Is there something more we have to do to test the connection??
We have not installed R/3 functions provided by Data Integrator in the R/3 system yet. Are these functions necessary for defining the connection or only for generating the ABAP code when executing the DataFlows?
I have read something about the RFC_ABAP_INSTALL_AND_RUN function in a Webpage but I don’t know what is necessary to do.
I can’t find information in the DI manual, somebody know what can be happening or have a link or information about the full connection process?
Can you post the screenshot of the SAP-Logon Pad as well to compare the settings, especially around SystemNumber and the such.
Is it possible you mixed up client with SystemID? The Client you chose when starting SAPGUI, in the dialog with username/password/language there is the forth field CLIENT.
It is as I said, you mistreated SystemID AC1 as client number. Logon to the SAPGUI, you will find in that logon screen the client to be used.
No, the ABAP functions do not need to be installed for development. If the SAP user you have got has development permissions and can create new ABAPs on that system you are fine.
You are right, we have introduced the wrong value for both the R3 client and the R3 and the system number!!
However, now we get an error saying that username or password is incorrect.
**** ERROR file opened at 20081028 173809 Romance Standa, SAP-REL 640,0,55 RFC-VER 3 717389 MT-SL
T:5220 ======> Name or password is incorrect (repeat logon)
T:5220 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
We have used in the Data Store definition the same username and password that is working to access using SAP GUI and another username and password used by the administrator working fine.
Is it necessary something special about this user or a special configuration??
Maybe a permission thing? Login with that SAP user, run the transaction /nse37, type as function module “RFC_ABAP_INSTALL_AND_RUN” and then click on the “Test” button to execute it. In the next screen keep the parameters as is and click on “Execute”. You should get an error saying “no parameters provided”. My guess is, you get an error along these lines somewhere proving that you do not have development permission for that user.
I did as you instructed above. The error I get in the SAP client is “Changes to Repository objects are not permitted in this client”. So does that mean I don’t have the development permission and would this also affect establishing a connection from the setup screen within Data Integrator for a Datastore?
It means you are developer, you do have permissions but you are not on a development system but an integration/production system where changes are not allowed.
Option 1: Do the development on a development SAP system. There you are allowed to write ABAPs. And then you ask your programs to be moved to the integration/production servers. Downside: Often the development SAP server does not have useful data and that move-abaps takes extra time.
Option 2: Ask the SAP team to install the “Data Integrator provided SAP functions” found in “C:\program files\BO\DI\admin\r3functions\transport…”. The SAP provided function RFC_ABAP_INSTALL_AND_RUN does have a test if the permissions of the user is S_DEVELOP and the system does allow for changes. We copied that function, removed the second test and called it Z_AW_RFC_ABAP_INSTALL_AND_RUN. Once this function is available it is used automatically.
Option 3: Ask the SAP team to remove that flag. Unfortunately it is a global flag so very very likely you don’t get that done.
(BOB member since 2004-12-17)
(BOB member since 2007-09-12)