Connection Error between ITS and SAP: R/3 system

Dear All,
Recently we have migrated our Backend SAP: R/3 Servers to AIX/Oracle platform. The server landscape is running on two application servers and one central instance with load balancing.
We have changed all RFC destinations from the SAP:R/3 and ITS side and tested the connection.
We are not able to login to backend SAP:R/3 server through ITS.
The following error appears
"Fatal Error!
The ITS failed to handle this request
The HTMLBusiness interpreter failed to interpret the template.
The internal error message is:
0x2101: Interpreter: The specified input file does not exist."
What other changes from ITS side we have to look into or check?
Regards
saikat180965

Hi saikat180965,
Might be the problem is being caused by missing templates. Please have a look in the ITS traces to get more information about the missing file.
Regards,
Dieter

Similar Messages

  • Difference between ITS and Web Application Server

    Hi All,
       What is ITS server. Can anyone explain me the difference between ITS and WAS(Web Application Server)
    Thanks
    Harpreet

    Hi Harpreet:
    ITS is basically the tool that allow you to use SAP via http. Theres lots of info about <a href="http://help.sap.com/saphelp_nw04/helpdata/en/0d/654d356560054ce10000009b38f889/frameset.htm">ITS</a> or <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/5f/0ef441ad7bc417e10000000a155106/frameset.htm">WebAS with Integrated ITS</a>
    The ITS is a standalone application connected to R3 via RFC connection, In the SAP WebAS the ITS is integrated to the system.
    Hope this help!
    Juan
    PS: Please reward with points if helpful

  • What is the difference between ERP2004 and SAP 47 Enterprise?

    Currently we have SAP 47 Enterprise with WAS 6.2. I understand ERP2004 is NW and 6.4 sp9. Can any one please let me know the major difference between ERP2004 and SAP 4.7 Enterprise ( more from abap / workflow view)?
    Thanks
    Swamy

    From Abap point of view some of the major add-on in erp2004,netwever :
    1) Development of webdynpro studio for java development for portal and iviews.
    2) Major abap development uses <b>Abap object oriented</b> methodology, rathet hten old conventional Abap,i.e MVC model (Model,View,Controller) where in it uses concept of classes,interfaces,etc.
    3) Advanced BSP tech using MVC model to develop web based modules
    4) It is closesly integrated with web-based CRM and BW/APO

  • What is the difference between mySAP2004 and SAP ERP 2004?

    Hi,
      Can anybody tell me what is the difference between mySAP2004 and SAP ERP 2004?
    If someone has the document, then please mail me at [email protected]
    With Regards
    tiffny

    Hi Tiffny,
    actually I don't see a difference as "mySAP2004" is not an official name for anything
    There is "mySAP ERP 2004" which is the marketing name for a bunch of functionality provided by several different bits of software components.
    Hth,
    Michael

  • Difference between ITS and WAS server

    difference between ITS and WAS server

    Hello Pradeep,
    The ITS is the Internet Transaction Server.  WAS is Web Application Server.  I'm not sure how to compare the two because the WAS from Basis 6.40 and higher includes the ITS.  I think the question you wanted to ask is the difference between the Standalone ITS and the Integrated ITS???
    The Standalone ITS is installed on a web server (IIS or Apache usually).  It could also include another server that we call the AGate. 
    The Integrated ITS comes with the WAS Basis 6.40 and higher.  Therefore not needing a separate web server.
    There is also a note that lists some differences of the two.
    Edgar

  • Relation between EDI and SAP MM

    Hello Gurus,
    Is there any relation between SAP MM and EDI...?
    Omkar--

    Hello Omkar,
    There is no specific relation between EDI and SAP MM. SAP MM module is for your internal data while Industry EDI is communication media.
    E.g.
    If you create a PO in your system , it is related to your MM part while information with regards to craeted PO is supplied to vendor by EDI _ Electronic data interchange.
    Hope this will help you.
    Amit C kulkarni.

  • (UIX XML) Sharing Connection objects between BC4J and custom java.

    If I have a UIX XML page that contains some BC4J application modules, then in the event handler I call [public static EventResult handleMyEventEvent (BajaContext context, Page page, PageEvent event..) ], which in turn calls some java classes I have written that take a java.sql.Connection object and access the database doing some updates/inserts with this Connection object (via JDBC)....HOW CAN I USE THE SAME TRANSACTION AS WAS USED IN THE BC4J APPLICATION MODULE...i.e. CAN I SHARE THE CONNECTION OBJECT BETWEEN BC4J AND MY OWN JAVA CLASSES THAT USE JDBC?
    What are the best ways to share such a transaction?
    Thanks,
    Paul.

    Would it be easier to use a custom method on the bc4j Application module?
    Take this scenario...
    1. User opens UIX XML web page which opens a bc4j App Module..it has a VO based on all employees.
    2. User presses the add button and a new employee is created (using the bc4j App Module).
    (Notice: no commit yet!)
    3. User presses the submit button...fires event REVIEW_SALARY.
    4. This event is 'handled' in the event section of the UML XML...it calls:-
    public static EventResult handleREVIEW_SALARYEvent (BajaContext context, Page page, PageEvent event)...
    5. I now want to call a java class I wrote that computes an employees new salary and updates the employee record with this new salary. This update will fail unless it is part of the same transaction as the one used by the bc4j App Module (that inserted the new employee).
    How best to proceed from here?
    How about having a method on the bc4j App Mod's VO called 'reviewSalary'? Calling this would use the same transaction? I could then call my java class from within the VO's method? However do I still have the same problem in that my java class expects to be passed the connection object?
    The approach you suggested previously seems a touch dangerous....in that these are not 'publically exposed'...and a new release of JDev may break my code.
    Thanks,
    Paul.

  • Synchronization error between LMDB and SMSY

    Hello Experts
    I have a sync error between LMDB and SMSY entries. I want your help to make this synchronization to Solution Manager 7.1 SP07.
    Thank you very much for your help
    Juan Carlos Salazar R

    Solman Setup - Configuration Lost
    To try to solve the synchronization error
    I have been running a Report for get some information and as a consequence all the information into the solman configuration was lost. I mean everything, all the clock (the date of modification) are in zero, and all the status are grey.
    Someone know How to bring this information back; without performing a backup or to perform a setup again.
    The report is the RLMDB_SYNC_TECHNICAL_SYSTEM

  • Secure the file/data transfer between XI and any third-party system

    Hi All,,
    I would like to use to "secure" SSH on OS Level the file/data transfer between XI and any third-party system Run OS Command before processing and OS command After processing. right now my XI server installed on iSeries OS.
    with ISeries we can't call the Unix commands hope we need to go for AS400 (CL) Programming. If we created the AS400 programm how i can call that in XI.
    If any one have idea pls let me know weather it will work or not.
    Thanks in adavance.
    Venkat

    Hi,
    Thanks for your reply.
    I have red some blogs like /people/krishna.moorthyp/blog/2007/07/31/sftp-vs-ftps-in-sap-pi to call the Unix Shell script in XI.
    But as i know in iSeries OS we can write the shell script we need to go for AS400 programe. If we go with AS400 how we need to call that programe and it will work or not i am not sure there i need some help please.
    Thanks,
    Venkat

  • RFC connection error between BW 3.5 and ECC 6.0

    Hi gurus,
    We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test  (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
    Any idea? Is there any other place (users, RFC) where we have to change user password on system?
    Thanks a lot!
    Regards,
    Iván.
    Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

    Solved!
    This is because of the incompatibility of password handling between
    640 and 700 systems.
    We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
    1. Change the password for the user in SAP R/3.
    2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
    3. Authorization test is now successful.
    (SM59 - Test - Authorization).
    Regards!

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • RFC connection error between Netweaver 7 EHP1 and Ides ECC6

    Hi Friends,
    I try to create  source system  in BI from Netwever EHP1 to IDES ECC6 EHP3.
    During the creation I get a connection error, says. check connction parameter.
    I checked the parameter, everything is fine. Server, System and number.
    When I went to the SM59 and created a connction.
    I.E. with the same parameter like system = 06 and server = compi9 gave client 800 etc.
    The Host name is resolved to 192.168.2.111 wich is OK.
    But when I run the connection test it shows me  "ERROR: partner '80.156.86.78:sapgw06' not reached"
    I have no idea where this IP '80.156.86.78" is comming from.
    No Problem with the opposite way, from Ides to NW and login to the System is OK too.
    Can anybody help me with this problem.
    RG. Jimbob

    Hi,
    What is the next screen that comes up when you click on remote logon.
    If no screen comes up then:
    Check the user type of the user id used for this RFC.
    It should be either dialog or service user for able to remote login.
    If it open a new window and asks for password, then its excatly password issue.
    Also make sure that the password is in numeric and correct.
    Also make sure that the current user check box is unchecked.
    Even if it dosent work, delete the connection and create again.
    Please award points if helps.
    Thanks
    Santhosh

  • Connectivity loss between PLC and Kepware

    Hi Experts,
    I m working on SAP PCo and PLC connectivity using Kepware.
    I m trying to find out ways to find connectivity loss between
    1) PLC and kepware
    2) kepware and PCo
    For 2nd approch,if connectivity loss is there then PCo instance will go in error state and using remote monitoring we can get alert.
    But m not able to find any way for 1st approch.
    If PLC connection lost then only tag quality in kepware is bad.
    Is there any way in PCo expression editor to check tag quality so that i can trigger MII transaction?
    Thanks in advance.
    Regards,
    Neha

    To add to Hubrisnsx's comment ... are you provisioned Ethernet or MoCA for the WAN connection?
    Edit: Never mind, I see in the first post you said MoCA.   So, if the MoCA channel is staying up, then it sounds like it might be something inside the ONT. 
    Keep in mind that while some Verizon folks do drop by these forums from time to time, that this is primarily are user to user forum where customers can help one another.

  • SSL between ITS and LDAP

    Hello:
    I have a ITS 6.20 patchlevel 22 with Linux Red Hat Enterprise 4. I have configured the service PAS to access to the Employee Self-Service of the ITS via LDAP.
    I want to configure SSL between my ITS and the LDAP, but I read in note 456666 that it is only possible for Microsoft Windows and my ITS is Linux.
    Is it correct?
    Regards,
    Felipe Sánchez

    Hi,
    ~ldapport=636
    636 is normally the secure port or the LDAP SSL port, but this depends on the directory server and additionaly things also.
    Therefore I advise you to use example or SDK coding from your directory server or vendor. Normally things like certificate exchange / key exchange and configuration needed to ensure the secure configuration.
    All these things are vendor dependend steps and therefore SAP has no documentation about it,e.g. Novell directory server has a SDK with example coding for SSL connections. This coding in combination with SAPs PAS SDK can be used to build a shared library with LDAP SSL.
    regards,
    -markus

  • RFC Connection error in SM59 for SAP J2EE

    Hi All,
    i am getting the following error description while testing the connection for
    SAP J2EE ...
    Connection Test SAPJ2EE  
    Connection Type TCP/IP Connection  
    Logon              Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program sapfallback not registered
    Error Details     LOCATION: SAP-Gateway on host filip / sapgw00
    Error Details     DETAIL: TP sapfallback not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 1483
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1694
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Tue Mar 31 02:44:35 2009
    Error Details     VERSION: 2
    Help me resolve this
    Regards,
    Mahesh.

    Hi,
    Please follow this steps:
    Creating RFC Destinations in the ABAP and Java Environment
    You need to create the following RFC destinations in transaction SM59 (ABAP) and the Visual Administrator (Java):
    u2022 AI_RUNTIME_JCOSERVER
    u2022 AI_DIRECTORY_JCOSERVER
    u2022 LCRSAPRFC
    u2022 SAPSLDAPI
    Depending on your client settings, it may be necessary to be logged on your SAP Exchange Infrastructure host as SAP system user with the authorization to maintain customizing tables and to release transport orders. Note, that user "SAP*" or "DDIC" does not have these authorizations.
    Maintaining the RFC Connections (Transaction SM59)
    1. Log on to your SAP Exchange Infrastructure central instance host.
    2. Call transaction SM59.
    3. Choose Create.
    4. Enter at least the following:
    RFC destination: AI_RUNTIME_JCOSERVER
    Connection type: T
    Description: <your description>
    5. Choose ENTER
    6. Choose the tab Technical settings and do the following:
    a. Select Registered Server Program
    b. In the Program ID field, enter: AI_RUNTIME_<SID> where <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only.
    c. Enter Gateway host and Gateway service of your Integration Server host. To find out the required parameters:
    a. On the Integration Server host, call transaction SMGW
    b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)
    7. Choose tab Special Options and select the flag Unicode in the box Character Width in Target System.
    8. Save your settings.
    9. Repeat the steps 3 u2013 8 for the remaining destinations:
    Destination
    Values
    AI_DIRECTORY_JCOSERVER
    Program ID: AI_DIRECTORY_<SID>, where <SID> is the SAP system ID of your SAP XI host
    LCRSAPRFC
    Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your SAP XI host.
    SAPSLDAPI
    Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your SAP XI host.
    10. Leave the transaction SM59 open for later tests.
    J2EE Configuration for the Destinations (Visual Administrator)
    1. On your SAP Exchange Infrastructure central instance host, start the J2EE Engine administration tool.
    2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
    3. In the section RFC destination, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintaining the RFC connection above. Additionally, set the number of processes to 10.
    4. In the section Repository, do the following:
    a. Enter the parameter for the SAP XI host: Application Server, System Number, Client and Language.
    b. For User and Password maintain the login parameters for the user SAPJSF.
    c. Select the flag Unicode.
    6. Choose Set.
    7. Repeat the steps 3 u2013 6 for the remaining destinations:
    Destination
    Values
    AI_DIRECTORY_JCOSERVER
    u2022 Corresponding values from SM59
    u2022 Number of processes: 10
    LCRSAPRFC
    u2022 Corresponding values from SM59
    u2022 Number of processes: 3
    SAPSLDAPI
    u2022 Corresponding values from SM59
    u2022 Number of processes: 3
    Testing the RFC Destination
    After you have maintained all RFC destinations in both the ABAP and Java environment, you can check all the connections above as follows:
    1. Call transaction SM59 again.
    2. Open your RFC destination.
    3. Choose Test Connection. No error should be displayed.
    This will solve your problem.
    Thanks
    Laxmi Bhushan

Maybe you are looking for