3 Replies Latest reply: Jun 1, 2007 2:41 PM by Guest RSS

regarding sm58

Vikram K
Currently Being Moderated

Hi Gurus,

 

 

    I have a doubt regarding the tcode SM58.  What do we actually look in the tcode  SM58 .  What do the contents of the tcode SM58 tell us . Can anyone plz give  me a brief explanation about it.

 

Thanking you in advance.

Vikram.

  • Re: regarding sm58
    Sriramachandra Murthy Parasuramuni
    Currently Being Moderated

    SM58 - Asynchronous RFC Error Log

    Please refer to the below links -

    /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

    http://help.sap.com/saphelp_nw04/helpdata/en/22/042578488911d189490000e829fbbd/content.htm

     

    transaction SM58 (Tools ® Administration ® Monitoring ® Transactional RFC). This tool lists only those transactonal RFCs that could not be carried out successfully or that had to be planned as batch jobs. The list includes the LUW ID and an error message. Error messages displayed in SM58 are taken from the target system. To display the text of the message, double-click on the message.

     

    Transaction SM58 also lets you control your transactional RFC at various stages. If the call ends abnormally during the sending process, you may need to use the Rollback LUW function to manually rollback the LUW before attempting a resend. If the target system was unavailable, you can use the Backgr.job function to display the batch job created for your call. Execute funct. module lets you restart the call after the occurrence of a temporary error (such as a syntax error).

     

    http://help.sap.com/saphelp_nw04/helpdata/en/22/042585488911d189490000e829fbbd/content.htm

     

    Hope this helps you.

     

  • Re: regarding sm58
    Mohan Kumar K
    Currently Being Moderated

    Hi Vikram

                    Well sriramachandra is right, to add few more points about SM58 transaction.

     

    <b> SM58 --> Also called RFC Monitor   </b>

     

    How to handle RFC errors? When you have this question in mind then SM58 helps you pretty well.

     

    If errors occur during Remote Function Call, these are processed in individual error handling in the standard system. For each incorrect RFC, the system schedules a batch job which starts the RFC repeatedly until processing is successful. If the link to the destination system is interrupted, this can lead to a large number of batch jobs being created, thus placing a heavy load on the transmitting system that is processing the jobs.

     

    When the system is in use, it is absolutely necessary that you use the collective error handling facility to improve system performance. When you use this method, RFC transmissions are not automatically repeated immediately. Instead, a periodically scheduled batch job collects the incorrect RFCs and transmits them again as a package. As a result, the number of batch jobs is kept to a low level. This feature is available for system and TCP/IP links.

     

    To carry out the error handling procedure:

     

           1.      Choose Tools --> Datafeed Monitors --> RFC monitor or the corresponding path in SEM Banking.

     

    You can also access the RFC monitor in other ways - e.g. from the main menu, choose Tools --> Administration --> Monitor --> Transactional RFC (SM58 tr. code).

     

           2.      Enter the User name and the dates for the Display period.

     

           3.      Choose Execute.

     

    Schedule a periodic batch job for error handling.

    Before you go live, practice the error handling procedure for Remote Function Call errors.

     

    The user name SAP* may not be used for Remote Function Calls by the destination system.

     

    Usefull: Please reward points.

     

    Thanks and Kind Regards

    -


    Mohan

  • Re: regarding sm58
    Currently Being Moderated

Actions