RFC layer monitoring

Hi,
can anyone please direct me to a link describing how to monitor errors in the RFC layer? Transaction SM58 shows RFC calls in error status and I would like to set up a monitor which sends an email, or at least an alert to a support team.
Any suggestions are appreciated.
best regards,
Jason.

Hai,
You can acheive this my activating the auto reaction methods in RZ20 for this particular MTE.
You can find this MTE under SAP CCMS Monitor Templates -- Communications -- Transactional RFC and Queued RFC.
Here you can add your Autoreaction method, ie., to trigger alerts mails in case of errors, for this you need to configure Mail configuration first.
http://help.sap.com/saphelp_nw70/helpdata/en/f0/02a63b9bb3e035e10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/30237989-0901-0010-70a4-944691eb5e52 [original link is broken]
It is always better to configure your own MTE under RZ20, you can find the step by step guide in help.sap.com
Regards,
Yoganand.V
Edited by: Yoganand Vedagiri on Feb 18, 2009 10:52 AM

Similar Messages

  • RFC message monitoring (RFC Adapter)

    Hello everyone!
    I am planning to use the RFC receiver adapter in XI to send messages to an SAP system. My question is, how would I monitor the RFC messages coming into the SAP system? Will they be viewable in sxmb_moni?

    hey
    yes u can monitor RFC's in sxmb_moni.
    in addition to that you can see SM58 (in case of any errors in RFC)
    thanx
    Aamir

  • RFC Monitoring using CCMS

    Hi All,
    We need to configure RFC availablity Monitoring in CCMS of our Solman system for our PRD satellite system.
    In PRD, We have created data collection method Z_CCMS_RFCDest_Availability_Trex which is using SALK_RFCDEST_AVAILABILITY as function module,
    Parameters in collection method are :
    COLL_METHOD            Z_CCMS_RFCDest_Availability_Trex
    RFC_DEST                   TREX_ES3_NWPRFI
    MTE_CLASS                Availability_RFC_Destinations_MA_Clas 
    CCMS agents are running fine in Solman and PRD. Now I expect that in Solman->rz20->PRD I should get Node like:
    PRD\Availability\...\RFC-Destinations\TREX_ES3_NWPRFI
    But I do not see any node there, It is blank screen on rz20 of this system.
    Please suggest what I am missing to complete the configuration part.
    Regards,
    Shivam Mittal

    Thanks Gary,
    I haven't seen this no where would I find it. Had a quick look on the market place and can't find it!
    Chris
    Just to add were using Netweaver 2004s
    Message was edited by:
            Chris Soden

  • Monitoring of RFC Connections

    Hi Folks,
    is there any option to monitor a TCP/IP RFC connection.
    I need something like a heartbeat on a registered program connection.
    Something like GRMG for http, just working for RFC.
    Is there any standard way to do this or do I need to use OS level tools?
    Thanks,
    Bastian
    Edited by: Bastian Schneider on Jul 3, 2008 9:15 PM

    Hi
    Please check this note for RFC monitoring
    Note 1069130 - RFC Destination Monitoring: Separate Method for Each Dest.
    And check for this link for Email configuration
    /docs/DOC-8701#section12
    Configuring the Sending of E-Mails as an Auto-Reaction

  • Monitoring RFCs on Remote Systems

    Hi,
    I am attempting to convert our CCMS monitoring to a central instance on solman. One of the things we monitor in the PRD system is availability of two RFC destinations.
    I am unable to figure out how these can be monitored from solution manager as a central system. When I set these up in solman under availability monitoring, it appears that solman is expecting these RFC destinations to be local to solman, rather than on the PRD system.
    How can I get solman to monitor the RFC on PRD? It does not appear that the RFC availability monitoring method allows you to specify which system the RFC resides on.
    Thanks much,
    Chris.

    Hi,
    ok I will try to explain how get to see the MTE's of ur PRD system.
    1.   TA: RZ20
    2.   change in maintenance mode (Extras -> Activate Maintenance Mode)
    3.   now u r able to create a new monitor set. So please do this by clicking on the create button.
    3.2 place a describing name and select who should be able to see this set. Click OK and now u will see ur new own monitor set
    4.   Click one time on that set and click one more time on the create button. Now u will get an list with all monitored Systems, that are connected to the solution Manager. Search in the PRD System the MTE u like to see and save ur new monitor with an discribing name.
    5. Hopefully if I'm forgottin' nothin u will see after save and activate ur objects from the managed System in the CEN System.
    So if anything is missing feel fre and contact me ...
    br Lars

  • Is it possible to call custom designed RFC function module, apart from BAPI

    Hi Friends,
    1.     Is it possible to call custom designed RFC function module, apart from BAPI.
    2.     Why we call it Adaptive RFC layer, Since every time the JCO layer updated with SAP, Why can’t be dynamic.
    Thanx for Ur time.
    Cheers,
    Sam

    Also check <a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/38bc8f813719488ddc9d9b21251ec3/frameset.htm">here</a> for more information on aRFC. Here you can find why it is called adaptive.
    Regards,
    Christophe

  • Trusted RFC - TRUSTING_SYSTEM@P11and SM_P11CLNT040_TRUSTED

    Dear SAP colleagues,
    From SAP Solution Manager, I want to connect a satellite system (P11).
    I have currently 2 Trusted RFC :
    1. TRUSTING_SYSTEM@P11
    2. SM_P11CLNT040_TRUSTED generated from SMSY.
    I am currently re-checking all RFC of SOLMAN and I am wondering why 2 TRUSTED RFC which are directed to the same system and client are necessary ?
    In other term, what is RFC TRUSTING_SYSTEM@P11 used for ?
    Is this RFC only created during system installation ?
    Best regards
    P. C.

    Hi PC,
    The Trusted system RFC TRUSTING_SYSTEM@P11 is automatically created while establishing a trusted system access using SMT2.
    Please refer to the below link:
    http://help.sap.com/saphelp_nw04/Helpdata/EN/8b/0010519daef443ab06d38d7ade26f4/content.htm.
    Its not always necessary to have two trusted access. Mainly used to jump into the other satellite system without giving userID and password and authorizations pays a key role here.
    The usage depends on the scenario. It is normally required for the system monitoing functionality and you do have an option to define the Trusted RFC for monitoring, when you setup system monitoring. It also plays a key role in Central system adminstration.
    Hope this helps, Revert for any issue.
    Thanks,
    Jagan
    Edited by: jagadheeshan govindasamy on Oct 7, 2009 7:50 AM

  • Sender RFC Scenario Error:Payload Is Missing

    I am facing an issue in 'RFC2JDBC' scenario which is mentioned below:
    here our scenario is 'RFC2JDBC'.here our 'RFC' is having 2 fields in tables parameter
    i.e. empno & empname.
    the results of the 'RFC' is coming as:
    Personnel Number  Employee Name
    00000100                 Rasmiraj
    00000200                 Tanmay
    00000300                 Kanhu
    00000400                Debabrata
    00000500                shantanu
    i am triggering the 'rtfc' through a program.
    when i am triggering the 'RFC',in monitor of PI it's coming as sucessful.however in the payload one of the field value is missing i.e. employee name.(same also updating in the legacy database)
    in the payload it's appearing as:
    [  <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:ZSAM_SEND_RFC_PI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    - <EMP_DTLS>
    - <item>
      <EMPNO>00000100</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000200</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000300</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000400</EMPNO>
      <EMPNAME>a</EMPNAME>
      </item>
    - <item>
      <EMPNO>00000500</EMPNO>
      <EMPNAME />
      </item>
      </EMP_DTLS>
      </rfc:ZSAM_SEND_RFC_PI> ]
    please,suggest.(here,we are using sender 'RFC' communication channel & an 'RFC'destination of type 'T'(with parameter registered server program,gateway host,gateway service)

    Hi rasmiraj tripathy,
    I am also facing the same problem (Sender or Payload is missing) while integrating R3 to B1 using IDOC. When I resend IDOC, it capture by B1iSN but doesn't work, it gives me error. When I look into xml document, it is found that there is no receiver payload.
    My R3 system is non-unicode and it is difficult to change it to unicode as it requires updation.
    Can you please confirm that this error is coming due to Non-Unicode, and can be resolved by setting it to Unicode.
    Note: There is no double definition of any object.

  • Erratic behavior with multiple calls to the same RFC

    Hi,
    I am running into a strange problem invoking a custom RFC from a .NET application. I would appreciate it if someone has any insight into it.
    The steps to call the RFC are straightforward:
    1. Open the connection to SAP server
    2. Make the call
    3. Close the connection
    As you can imagine, the code is also quite simple. 
    In my simulation program, I have a button on a UI form that one can click and execute the above steps.
    The problem I am running into is that, on multiple calls, sometimes the parameter values that show up on the SAP side are not right. When the input parameter (a structure) is viewed in the ABAP debugger, the field values are all getting exchanged. For example, first name field contains values for the last name. Also, some fields that are supposed to have values do not have any.
    Just before the RFC call is made, when we look at the structures on the .NET side, the field values are the way they are supposed to be.
    I have not been able to establish a pattern. Sometimes, it takes two clicks to reproduce this problem. Sometimes it takes five.
    One of the team members thinks that this starts occurring right after one call fails for some valid reasons. However, I am not yet convinced.
    Having written many custom .NET applications using RFCs an BAPIs, I am fairly conversant with the technology. However, this one just baffles me. It appears something is getting messed up at the RFC layer itself. Does anyone have any idea on what could be happening?
    Thank you in advance for your help.
    Pradeep

    Indeed this is interesting .
    The problem is caused by an incompatible change from .NET Framework 1.1 to 2.0. Howerver, the documentation on the 1.1. API was not clear enough to decide if the incompatible change was adequate or not. Now in detail:
    NCo runtime uses the reflection API Type.GetProperties to read and cache all properties of a Proxy structure. NCo assumes that the order of the returned properties is the same on each call and especially that it is the order of the properties as they appear in source code. This was the behavior in .NET 1.1. It has changed in 2.0, see e.g. the internet forum discussion in http://www.thescripts.com/forum/thread455492.html .
    Calling Type.GetProperty(<PropertyName>) or Type.SetProperty(<PropertyName>)  in your code moves the mentioned properties up in the list returned by Type.GetProperties() later inside of NCo.
    We found the following work-arroud:
    When using late-binding, call a dummy Type.GetProperties()  before any GetProperty or SetProperty.

  • Issue in RFC to File Scenario

    Hi All,
    I am working on SAP PI 7.31 dual stack. I have configured a simple RFC to File scenario with aysnchronous interface. I am using classic configuration.
    In Sender RFC channel monitoring I am getting the below exception and the file is not created.
    "Error in processing caused by : com.sap.aii.af.lib.mp.module.ModuleException : call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message xxxxxxxxxxx(OUTBOUND) expired".
    Please suggest me what could be the issue.
    Thanks,
    Madhurima

    Hi Madhu
    As the log says the function module is try to execute synchronously.
    But as per your requirement it should be asynchronous. Please remove all the  export parameters from the function module.
    Then re-import the function module in PI and adjust mapping and operation mapping.
    Stop and start the RFC sender adapter so that it will get the new metadata of the function module.
    The function module should have only import parameters so that it will act like a asynchronous interface.

  • Very strange issue regarding Sender JDBC to Recevier RFC?

    I've been testing sender JDBC to Receiver RFC,
    but i realized that target RFC was not performed even though moni is clear and RFC adapter monitoring is clear,
    both monitoring is successful.
    also checked that RFC_Receiver adapter setting is correct.
    i also checked RFC Function at Target side whether it is running or not correctly, it is no problem with test value.
    i've never been seen such issue.
    Dose anyone has such experience?
    Message was edited by: Tony
    Message was edited by: Tony

    yes, nothing there.
    but i forgot to tell you one thing,
    sender has one and target has two each communication channel on service, JDBC to JDBC and RFC.
    JDBC to JDBC is ok, but JDBC to RFC is above issue.
    sxmb_moni has two message according to above two receivers when i execute, and two messages are correct
    adapter monitoring is correct
    Message was edited by: Tony

  • RFC Sender error - lookup of alternativeServiceIdentifier

    Hi,
    I am trying to configure an R/3-XI-Java proxy scenario using the RFC adapter as sender. When I execute the RFC on the R/3 system using the RFC destination, I get the exception SYSTEM_FAILURE. In the RFC adapter monitor, the error message  is "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel". I have verified the settings mentioned in SAP note 730870 (Q. 15), but am still getting the same error. Please let me know how to resolve this error.
    Thanks,
    Sumanth.

    Hi Sumanth,
    Check the <i>Adapter Specific Identifiers</i> in the Business sytem which contians RFC adapter.
    Make sure that R/3 System ID is equal to the one specified in the SLD.
    You can also "compare" the same with that in the SLD.
    You should concider clearing the SLD data cache before comparison
    Cheers,
    Rashmi

  • RFC receiver asynchronous

    Hi,  i’ve got a problem with an Asynchronous message. The operation goes from an FTP to a RFC. The file adapter converts a flat file into a XML, and the XML is sent to a Remote RFC.
    Everything is ok in XI. In the SXMB_MONI and in the RFC adapter monitor we see that the message is correctly sent to the RFC, but the RFC receive nothing.
    We have written a short routine in the RFC that just insert an ‘X’ in a testing table, but nothing happen.
    Thanks.

    Hi Eduardo,
    look as well to XI: SM58 and R/3: ST22 to find out the reason.
    Regards,
    Udo

  • Regarding BW precalculation server monitoring

    Hi Experts, we have BW precalculation server configured in pur NW2004s BW system. My requirement is if i can monitor RSPRECADMIN using Solution manager. Like if precalc server goes down it should generate an alert.
    Any inputs on the above would be much appreciated.
    Thanks Amber S

    As indicated [earlier here in SDN|How to monitor Bi Precalculation?;,there is no MTE for monitoring Precalc. The work-around is to monitor the BI RFC PREC_<SID>. This provides a better end-to-end check than simply checking the Windows service on the Precalc server. Rather than monitor the RFC on the remote system, I simply created a duplicate of the RFC on the Solution Manager system, and monitored that.
    See [Monitoring Availability of Services|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70531389-0c01-0010-2a95-c019524764ae] (PDF) for a description of RFC monitoring.
    Also, here are some notes on data collection method CCMS_RFCDest_Availability_Col:
    SAP Note:0570083 CCMS: RFC Destination Monitoring does not work
    SAP Note:0771455 CCMS: Incorrect MTE Class in RFC Destination Monitoring
    SAP Note:0696194 CCMS: MTE class specification in SALK_RFCDEST_AVAILABILITY
    SAP Note:0762183 Monitoring the SAP SCM optimizer in CCMS (RZ20)
    SAP Note:1069130 RFC Destination Monitoring: Separate Method for Each Dest.
    SAP Note:1439088 CCMSPING: ccms_ni_ping_collect Does Not Work / Router
    Regards,
    Sean

  • RFC-Call using dynamic Parameters

    Dear Forum!
    I'd like to call a RFC function module using a dynamic parameter list.
    I can either call
    CALL FUNCTION bapiname DESTINATION fsystem.
    or
    CALL FUNCTION bapiname
            PARAMETER-TABLE lt_param
            EXCEPTION-TABLE lt_excep.
    but not both combined!
    The ABAP docu says, both should work together. If using DESTINATION the same options as for standard FM calls are allowed... (seen at: Transaction ABAPHELP, search for CALL FUNCTION, choose topic 4 for RFC)
    Who is wrong? The docu or me? How can I combine both?
    Cheers
    Torsten

    Hi Abir,
    thanks for your helpful answer.
    But I don't understand this:
    For calling a remote enabled FM, it needs to be released which means the parameters would be fixed and thus the RFC layer does not allow using parameter table in such cases.
    The FM resides on a remote system. It does not matter me, whether the FM is released, fixed or done with something other. As long it is reachable, I'm fine.
    I am wondering about the fact, that I can call a local FM dynamically, but cannot do so for a remote call.
    In the online documentation you can read, that a remote call function (with parameter destination ) has the same options like a standard call function. Actually this statement seems to be wrong. Right?
    Best regards
    Torsten

Maybe you are looking for