Logs of used rfc destinations

Hi Guys,
i'm looking for some tables including log-information of used rfc destinations. For now i have table EDIDC for IDoc-Logs. Do you know more tables, e.g. regarding BAPI usage? RFC logs in general (here i found ARFCSSTATE/ARFCRSTATE and some others, but they don't look as they would log all records, do they?
i just want to find out which rfc destinations are used and which not!
Best Regards
Stefan

Hi Stefan,
Generally we will RFC logs from SM58.
(Or) Check tcode SLG1 for application Log.
Thanks,
Krishna.

Similar Messages

  • Calling Remote enabled Function module in java using RFC Destination

    Hi
    We are on Portal 7.3 ehp1 sp9.
    Steps followed are :
    RFC Destination called “SAP_RFC” has been created as below :
    Configuration -> Destinations -> RFC Destinations
    Connection and Transport:
    Load balancing :Yes
    Provided : SystemID / MS Server / MS Server Service / Logon Group / Gateway Host / Gateway Service
    SNC : Inactive
    Logon Data:
    Authentication : Current User (Assertion Ticket)
    Language : EN
    Client : XXX
    Repository Connection:
    Destination Name : This Destination
    Specific Data:
    pooled Connection Mode : Yes
    Max : 5
    Size : 10
    Max. wait time : 10,000
    Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.
    JAVA Code as Follows:
    JCoDestination destination = JCoDestinationManager.getDestination("SAP_RFC");
    //destination.ping();
    JCoRepository repository = destination.getRepository();
    JCoFunction function = repository.getFunction("FM_NAME");
    function.execute(destination);
    Lines highlighted in RED color throwing an error as below :
    {"ERROR":"Initialization of destination JCO_RFC failed: Incomplete logon data. on <SID> mshost <MS_HOST>/ com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Incomplete logon data. on SID mshost MS_HOST"}
    And found that no COOKIE with the name “SAP_SESSIONID_<system>_<client>” was not found, I am afraid that “Assertion Ticket” was not created in above scenario.
    To confirm SSO configuration working, i have followed below steps:
    1) Created System Object pointing to R/3 and tests were successful for authentication type "SSOLOGONTICKET / ASSERTIONTICKET"
    It's J2EE application, no references or any other additional configuration been made part from above.
    Any help ?
    Thanks

    Here is log ..Assertion ticket could not be retrieved. Error was null
    Log Record Details
    Message:
    Assertion ticket could not be retrieved. Error was null
    Severity:
    Error
    Date:
    2014-04-23
    Time:
    20:28:26:056
    Category:
    /System/Security/destinations
    Location:
    com.sap.security.core.server.destinations.service.AssertionTicketRetriever
    Application:
    Thread:
    System [2]
    Data Source:
    j2ee/cluster/server0/log/system/security_00.log
    Arguments:
    Passport User Activity ID:
    3a7af5ddca8b11e384bd8adb6f484d33
    Message ID:
    Session:
    Transaction:
    User:
    Time Zone:
    +0800
    Customer Message Component:
    BC-JAS-SEC
    Runtime Component:
    tc~sec~destinations~service
    Correlation ID:
    3643650000002747
    Passport Session:
    3A7AF5DDCA8B11E384BD8ADB6F484D33
    Passport Connection:
    3a7af5ddca8b11e384bd8adb6f484d33
    Passport Connection Counter:
    0
    Log ID:
    C0000AD01D7B002200000EA5009800B2
    Host:
    host
    System:
    XXX
    Instance:
    J00
    Node:
    server0

  • Configuring receiver RFC adapter to use RFC destination

    Hello,
       I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system...  Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
       I ask this question because we, as a company, do not like to maintain passwords in multiple systems.  That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
       I checked the relevant links I could find below, but I can not resolve the answer from them.  Has anyone set this up successfully?  This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
    Thanks!
    John
    http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm  
    http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
    Re: Asynchronous RFC call

    Hi John !!
    I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
    Regards,
    Matias.

  • Creating Record in ZTable using RFC Destination

    HI All,
    From one of my production system, i want to write the records in the DBtable which is available in other production system using RFC connection.
    Is there any FM is available ?
    There is a RFC_READ_TABLE FM, which used only for reading the contents of the table.
    Is there anything to write also?
    Thanks & Regards,
    Ram

    Sorry for the confusion.
    I got the alternative way to solve this issue.
    Hence close this thread.
    Thanks & Regards,
    Ram

  • RFC destination definition with non-unicode external program

    Hello All,
    we have one issue with our RFID system connecting to WM system (SWD). 
    For most functions, external RFID server/middleware makes RFC call to SAP system.  Means, from outside system to inside SAP.  This seems to be working fine.
    But in one case, SAP needs to print label to RFID printer.  In this case, SAP is calling external RFID server/middleware using RFC destination.  Means, from inside SAP to outside system.  This is failing.
    We think this has something to do with ECC60 being unicode system, and the RFC destination setup.  We define rfc destination "ZRFID_SSI" in SM59.  We define it same way as in as-is SSI 4.6B production system.  But in SWD ECC60 system, SM59 has more options.  We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server.  RFC destination is actually working ok.
    To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI.   Listener on RFID server/middleware will respond to function call.  This also seems to be working.  But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0".  (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
    Compared with production environment, everything is the same, except that SAP is unicode system.  So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data.  I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange.  Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
    Anyone know how to help ?

    Hi Jeongbae,
    as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
    In earlier releases, this is not possible.
    In general, SAP systems use the logon language (SY-LANGU)  to determine the code page, if this is available.
    Please check SAP note 788239.
    Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
    In addition I would recommend to have a look at SAP note 1021459.
    However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
    For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
    Best regards,
    Nils Buerckel
    SAP AG

  • Ecatt using RFC

    Hi,
      While I was running the test script in ECATT using RFC destination I was encountering a problem .
    It is giving me following message in the log generated.
    Control data is obsolete, rerecord (VERBS-NAME: CreateObject CATT: <none>
    Callno: 000001)
         Message no. TT377
    Please help me on this regard.
    <b> Helpful posts will be rewarded</b>

    Hi folk!!
    I have the same error. Could you please let me know hoy do you solve it?
    Thanks!!

  • RFC Destination Settings

    Hello Gurus,
    Earlier we had 2 ECC systems in the landscape.
    Purchase requisition A from APO system supposed use RFC destination 1 and reflect in Plant XXXX
    Purchase requisition B from APO system supposed use RFC destination 2 and reflect in Plant YYYY
    Now we have only 1 ECC system in the landscape. we have changed the publication settings accordingly. but preq still not getting transferred correctly to ECC system.
    Debugging the code shows system trying use wrong RFC destination.
    Is there any other configuration setting we are missing.
    Please advise.
    Thanks In Advance
    Shyam

    Hi Shyam,
    Please find my suggestions in regards to respective configuration settings.
    1) Did you delete the obsolete RFC destination(Logical System) from your landscape?
    2) Did you correct the RFC destination of plant YYYY to RFC Destination1 (incase you scrap RFC destination2 from landscape)?
    3) Check what is the Logical System that is maintained for the location YYYY from the table /SAPAPO/LOCMAP in APO system.
    4) Similar check for the products in the table /SAPAPO/MATMAP.
    5) Remove the obsolete ECC System from the BSG using T-code /SAPAPO/C2.
    Post checking and correcting, do an intial transfer of locations via CIF from the current ECC system.
    Thanks,
    Santosh KB.

  • TCP/IP Connections in RFC Destination

    Hi,
    When we are using TCP/IP Connections in RFC Destinations in SAP XI and why?
    Regards
    bobby

    >
    jak jak wrote:
    > Hi Sujit,
    >
    > i have one small doubt,we are using WAS 6.40 with EP 6.0. So can we use this RFC destination service in our code?
    >
    >
    >
    > Thanks,
    > Jak
    You can use RFC Destinations with WAS 6.40. I wrote a blog on about it [here|/people/stefan.thibeault2/blog/2008/07/16/a-real-world-example-of-using-the-sap-enterprise-connector].

  • RFC destination types

    When do we use RFC destination Type T versus Type 3?
    While creating RFC destination Type T, the program ID, blogs says we should use "Registered server program" and can give any free text. I tried that but says there is no registered server program called XXX on system. So, i'm really confused here.
    my understanding is for IDOCs you need Type 3, and for RFC you need Type T. Is that true or we can use any type with these?
    Thanks,
    Anika

    Hi Anika,
    i think this links could be useful:
    http://help.sap.com/saphelp_47x200/helpdata/en/22/04262b488911d189490000e829fbbd/frameset.htm
    Differences in the RFC destination types
    You're right, for Idoc you have to use type 3 and for RFC you have to select a type T destination entering a program ID.
    Let's make an example.
    Suppose you have defined an RFC destination RFC_X with program id PID_X on ECC.
    On XI you have created an RFC sender adapter and you have specified ECC as the sender and PID_X as the program ID.
    When from ECC an RFC is called using destination RFC_X then the sapgateway looks for a receiver registered with the program id PID_X, it finds your RFC adapter and sends the call to XI.
    Hope it helps.
    Kind Regards,
    Sergio

  • Queues for RFC-Destination

    Hallo,
    must i assign a rfc-destination to a outbound queue? what happens when this is not done?
    Thanks in advance,
    Frank

    Hello Frank,
    In the context of using RFC Destination with quality of message EO(Exactly Once -- tRFC), the Queue will be automatically gets assigned at runtime.
    In the case of EOIO(Exaclty Once In Order-- qRFC), since the messages have to be executed in a sequence, a queue must be assigned during configuration.
    As per your query, if not assigned the messages would be struck.
    Regards,
    Sreenivas.

  • RFC Destinations for Webdynpro models

    Hello Everybody,
    I am trying to use RFC Destinations for the Webdynpro model.
    I have multiple systems with same RFCs. Based upon the inputs on the screen, I wanted to call respective RFC.
    To achieve this, can I use RFC destinations in my webdynpro application?
    I know, this could have been solved through XI in between.
    That is not a valid path for me right now.
    Have anybody used RFC Destinations in Webdynpro models?
    I am getting exception: NoClassDefFound when I used DestinationService API for this.
    Please help me.
    Thanks in Advance,
    Bhavik

    Hi Bhavik,
    RightClick on the project->Goto Properties
    try adding library "tcsecdestinations~interface" in the interface references of WebDynpro reference.
    "tcsecdestinations~service " in the library references.
    Regards, Anilkumar

  • Debug RFC destination system

    Hi,
    debugging production system A, I call an RFC function module in production system B, but instead of starting debugging system B, it continues debugging next step of system A.
    I don't know why this is happening, I can debug both systems A and B separately, but when calling B from A, I cannot debug system B.
    My user in system A is:  des005
    My user in system B is:  des005
    The passwords are not the same.
    Thanks in advance

    Hello Joan
    Here is my recommendation to facilitate debugging:
    DATA:
      ld_rfcdest     TYPE rfcdest.
      ld_rfcdest = 'EDURFC'.
    call function 'ZRFC_UPDATE_PROJECTE' destination ld_rfcdest
                          exporting
                            i_projecte       = lwa_projecte
                          tables
                            o_messtab        = it_messtab
                          exceptions
                            no_exist_pepampl      = 1
                            system_failure        = 2
                            communication_failure = 3
                            others                = 4.
    If you cannot debug using RFC destination "EDURFC" then I recommend to define a dummy RFC destination (e.g. "SysB" which just contains the technical details of the remote system.
    Set a break-point at the CALL function statement and then overwrite LD_RFCDEST with the dummy RFC destionation.
    The login popup will appear and if you are allowed to do debugging in the remote system you should be able to do so.
    Regards
      Uwe

  • How to find out, which RFC-Destinations are in use?

    Hi community
    We have a huge list of RFC-Destinations in our productive system and I want to delete unneeded entries.
    Is there a report or a log, which shows, which RFC-Destinations were used, and when?
    Thanks in advance.
    Regards, Michael

    HI
    can you see the default trace in tcode SMGW, Be careful about deleting any system rfc.
    Read the documentation about default RFC, internal RFC, LDAP_RFC, transport RFC.
    I don't know other way to do that you need
    Regards
    William Neira

  • RFC Destination (ABAP) to use Single Sign on

    How do I configure an RFC destination to take the current user-id and connect to the RFC destination system without prompting for logon? (I do not look for a dedicated user-id pwd option - must use the current user's id)
    SNC is configured, and when I doubleclick in sap logon pad, I get connected to the corresponding SAP system without the login screen. Specifying the same parameters in the SNC def (SM59 - change destination) doesn't make any difference and returns an RFC error when trying to test.
    I have checked SSO links (some) on SAP help site (Do I need to configure the system in SSO2?). From portal and all it works fine. Not sure what specific config is required to connect to ABAP RFC destination to use SSO (or SNC whatever it be) to not throw the login screen.
    Any help?
    Thanks,

    i assume you are talking about to ABAP systems.
    check this link, you have to set up trust relationship between the systems.
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/22/042671488911d189490000e829fbbd/frameset.htm">Trust Relationships Between SAP Systems</a>

  • How to call RFC in Async Mode using TCP/IP RFC Destination ?

    Hi experts,
         Can anybody tell me how to call an Async RFC using TCP/IP RFC Destination ?
    Regards,
    Umesh

    Check the link
    http://help.sap.com/saphelp_nw04/helpdata/en/80/09680289c751429ab3b07ad2a61c10/content.htm
    It says
    <b> For asynchronous calls, no connection to external systems is possible (TCP/IP connections in transaction SM59).</b>
    Regards,
    Abhishek

Maybe you are looking for