SM58 Transaction

Hi BW Gurus,
   I want to explore transaction SM58. SM13 and SMQ1. In one interview they asked abt this transaction. i don't have any SAP R/3 System. Wht we information we can get from this. how can i use these transaction while monitoring DataLoads.
If any body can provide the information about this. I would be very very Happy.
Thanks in Advance.
Regards,
Satish.

Hi Satish,
The most common reason why I have used this transaction in the past is that when you cancel your load in BW and do not cancel the corresponding R/3 job it will continue to keep pushing/stacking those tRFCs. Few times I cancelled the job in R/3, but later on noticed that the tRFCs were there and the R/3 system was trying to push it to BW. So, when you cancel the R/3 job, make sure there are no pending tRFCs waiting to be transmitted. If there are, you have to cancel those as well.
Yes, they are available for master and transactional data. In the SM58 tran, under EDIT, you can delete the tRFC, reset status, execute/push it manually or debug the process. One other helpful feature of this transaction is that you can find out the true size of your data being transmitted. Oh, you can also go to SMQ1 from this transaction.
Abdul

Similar Messages

  • SM58 (transactional RFC)

    Hi,
    In our source system in SM58 (transactional RFC) i am getting the Status Text:                                                 
    User is locked. Please notify the person responsib
    Please advise how to proceed
    Thanks
    Please search the forum before posting a thread
    Edited by: Pravender on Aug 12, 2011 4:09 PM

    Hi
    Thanks for the update.
    I can execute the TCode SM58 and there i can see all the RFC queus are failed becaus of User Locked

  • SM58 Transaction   Error

    Hi Everybody,
    All day we are having the problem in the SM58 transaction in PRD environment.
    The message thar appear is :
    Caller       Function Module               Target System Date       Time     Status Text                                          Transaction ID           Host     Tctn Program                                                                               
    CUA_ECP_400  SUSR_USER_RESPONSE            SMDCLI200     14.06.2010 14:47:12 wrong Name or password               0A090A1904F04C166B1F0BD6 ecc01         SAPMSSY1
    Caller       Function Module               Target System Date       Time     Status Text                                          Transaction ID           Host     Tctn Program                                                                               
    CUA_ECP_400  SUSR_USER_RESPONSE            SMDCLI200     14.06.2010 14:47:38 User is locked   0A090A1904F04C166B390BE1 ecc01         SAPMSSY1
    We have a CUA configured in the Solution Manager, i already checked that the user
    CUA_ECP_400 is not locked   in PRD and Solution Manager.
    How can we solve this issue?
    What log can i check?
    Best Regards,
    Fábio Karnik Tchobnian

    Dear
    Double click on the connection SMDCLI200 in SM58 and check the connection test & authorization test.
    The caller entry in SM58 does not equal the user that is used in the actual connection. So most likely you are looking at the wrong user as you mention the user is not locked, the log clearly states the user/pass is incorrect and that after X attempts the user gets locked.
    When the authorization test fails, you will have to check the correctness of the password in the RFC definition and if the user is locked on the target system.
    Kind regards
    Tom

  • SM58 Transaction Recorded Very Slow

    Dear Experts,
    I have many tRFC in PI system in SM58 with status transaction recorded. This seems to be because there were an unusual data (file to idoc) from 1 interface that suddenly sends more data than usual. This happens at midnight, since then we have a queue at in SM58 with many  transaction recorded (until tonight).
    Strange things is actually that when I try to execute the LUW (F6), the transaction could be processed successfully, even though sometimes after pressing F6, the processing time could take some time (marked by the loading cursor). When the processing time is long, I just stop the transaction, re-open SM58, then the transaction that was executed before will be in the "executing" status and then I execute LUW for the transaction again and it never takes a long time to execute it.
    Trying to execute LUWs and ticking the recorded status would end up no transactions executed.
    Checking in SMQS for the destination, it is rarely that the actual connection reach the maximum connection. Seeing QRFC resource in SMQS, the Resource Status shows OK.
    Going to SM51 then Server Name > Information > Queue Information, there are no waiting requests.
    Actually the transactions are do processed, it just they are processed very slow and this impact to the business.
    What can I do when this happens? How to really re-process those recorded transactions?
    Could this be because the receiver resources? How to check for this?

    Dear Experts,
    According to this link,
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?original_fqdn=wiki.sdn.sap.com&pageId=145719978
    "Transaction recorded" usually happens when A. processing idocs or B. BW loads.
    A.If it occurs when processing idocs you will see function module "IDOC_INBOUND_ASYNCH" mentioned in SM58.
    Check also that the idocs are being processed in the background and not in the foreground.
    Ensure that background processing is used for ALE communications.
    Report RSEOUT00 (outbound)can be configured to run very specifically for the high volume message types on their system. Schedule regular runs of report RESOUT00 it can be run for
    IDoc Type and\or Partner etc..
    To set to background processing for Outbound idocs do the following:
    -> go to transaction WE20 -> Select Partner Select Outbound Message Type and change the processing method from
    "Transfer IDoc Immedi." to "Collect IDocs".
    Reading that explanations, should the setting of IDoc processing to background (Collect IDocs) is done in PI or the receiver?
    If the IDocs is processed collectively, will it make the sending IDoc process faster from PI to the receiver system? What is the explanation that if the IDoc is processed collectively, it would make the IDoc sending to be faster?
    Why should we use RSOUT00 report when we already have SM58, and we can execute LUWs in SM58?
    Thank you,
    Suwandi C.

  • SM58 "Transaction recorded" status

    If the idoc has reached the destination correctly ,then it should not get displayed in SM58 ,is that correct?
    if yes then,
    what should be done when "Transaction recorded" status is displayed in SM58?

    If the idoc has reached the destination correctly ,then it should not get displayed in SM58 ,is that correct?
    if yes then,
    what should be done when "Transaction recorded" status is displayed in SM58?

  • SM58 "Transaction Recorded"

    Hi I am seeing transaction recorded status for trfc's in SM58. I am not able to process them. Please help on how to process them. I see that RFC connection is active.
    Thanks.

    Hi Pcrao,
    Thanks for your reply,
    Kindly clarify the following
    1. What ABAP program i should use in the Background job. If it is RSARFCSE how will i create the variant for this program.
    Also there were some entries in SM58 3 days old entries which are in Transaction recorded. should i delete those entries
    Can the old entires cause any issue
    regards
    Naveen

  • What are the importent transaction codes in edi

    what are the importent transaction codes in edi

    hi,
    =>sale - ALE Customizing
    =>bale - Distribution Administration (ALE)
    =>wedi - IDOC Type and EDI Basis
    =>shdb - BDC (Transaction Recorder)
    =>lsmw - LSMW
    =>bapi - BAPI
    =>spau - Display Modified DE Objects
    =>spdd - Display Modified DDIC Objects
    =>sara - central idoc archiving
    =>stms - Transport Management System
    =>wedi - IDOC Type and EDI Basis (IDOC Configuration)
    =>bd21 - Analyze change pointers - create IDOC from change pointer
    =>bd10 - Send Material Master
    =>bd12 - Send Customer Master
    =>bd14 - Send Vendor Master
    =>bd50 - Activate Change Pointer for Message Type
    =>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)
    =>bd54 - Maintain Logical Systems
    =>bd71 - Distribute Customer Model
    =>bd87 - Process Inbound IDOCs
    =>bd88 - Process Outbound IDOCs
    =>bdm2 - Cross-system IDOC Reporting
    =>bdm7 - ALE Audit - statistical analyses
    =>bdm8 - ALE Audit - sending confirmations
    =>bd61 - Activate Change Pointer generally
    =>bmv0 - Direct Input Data Transfer Administration
    =>rz04 - Operation Mode
    =>rz12 - RFC Server Group Maintenance
    =>sar3 - Archiving object customizing
    =>s001 - SAPoffice Inbox
    =>s010 - Standards Texts (SAP Script)
    =>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)
    =>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)
    =>se78 - Administration of Form Graphics (Import Graphics into SAP System)
    =>se84 - ABAP Repository Information (search for SAP objects)
    =>su01 - User Maintenance (Security)
    =>su02 - Maintain Authorization Profiles
    =>su03 - Maintain Authorizations
    =>sm36 - Background Job Scheduling
    =>sm37 - Background Job Monitoring (display batch jobs)
    =>sm31 - Table Maintenance
    =>sm30 - Calling View Maintenance
    =>sm35 - Batch Input Monitoring (Error Logs)
    =>sm50 - Process Overview
    =>sm58 - Transactional RFC Monitoring
    =>sm59 - Maintain RFC Destinations (Define RFC Configuration)
    =>snro - Number Range Objects (for IDOCs)
    =>we02 - Display IDOC
    =>we05 - IDOC lists
    =>we07 - IDOC statistics
    =>we12 - Inbound processing of outbound file - convert outbound to inbound file
    =>we14 - Process (dispatch) IDOCs through Port - RSEOUT00
    =>we15 - Outbound IDOC from NAST - message control
    =>we16 - Inbound File
    =>we18 - Generate status file
    =>we19 - Test tool
    =>we20 - Add new Message Type to Partner Profile
    =>we21 - Maintain Port Definition
    =>we30 - IDOC Type development
    =>we31 - IDOC Segment development
    =>we41 - Process Code Outbound
    =>we42 - Process Code Inbound
    =>we46 - IDoc Administration
    =>we47 - Status Code Maintenance
    =>we57 - Assign function module to logical message and IDoc type
    =>we63 - IDOC Type for Parser Output
    =>we82 - Assign IDOC to Message Type
    =>we60 - IDOC Documentation - IDOC Types
    =>we61 - IDOC Documentation - IDOC Record Types
    =>we81 - Create new IDOC Message Types
    =>we82 - Assign IDOC to Message Type
    =>pa20 - Display HR Master Data
    =>pa30 - Maintain HR Master Data
    =>bd59 - Create and assign Filter Object Type for Message Type
    =>bd64 - Maintenance of ALE or any other Distribution Model
    Hope this helps, Do reward.

  • Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

    Dear Experts,
    My configuration scenario is  outbound:   SAP (IDOC)-------->PI------->AS2 ThirdParty.
    SAP PI version: 7.31 dual stack.
    First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
    http://scn.sap.com/docs/DOC-34155
    http://scn.sap.com/docs/DOC-31398
    While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
    Could you please help me on this issue ,I will appriciate you .This is very urgent.
    Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
    and I are getting below error in SM58 ECC system.
    Error in  ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
    Thanks,
    Aadi

    Hi Aadi,
    Please check the below SAP notes
    1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
    1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
    reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
    also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
    regards,
    Harish

  • Error in SM58 on XI box

    Hi,
    While trying to post IDocs to an R3 system, getting the following error in sm58 - 'Transactional RFC' transaction 'PASSWORD LOGON NO LONGER POSSIBLE'.
    But when I do a connection test from SM59, to the corresponding RFC destination listed in the receiver IDoc adapter  there is no issue. The test is successfull.
    Anything I'am missing here?
    Thanks,
    Anand

    >>>> did try a remote logon from the RFC destination...on doing this I get a dialog box requesting username/password entry. And the user that appears here is my user ID, not the user that is in the RFC destination.Is this standard behaviour?
    No. This means your RFC destination is not working properly. Just fill the user Id, pwd with a valid user Id that has sufficient auth., then try. You should be directly logging into SAP on using the Remote logon option.
    Regards,
    Jai Shankar

  • Error in sm58

    Hi all,
       I am trying to send a IDOC from SAP system to XI and I getting the following error in sm58
    Transaction IDX1: Port SAPEN5, Client 800, RFC Destination contian error.
    BTW what is the difference between maintaing the port in we21 or idx1?

    >>what is the difference between maintaing the port in we21 or idx1?
    WE21 is mainted in R3.
    IDX1 is maintained in XI.
    <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> By Swaroopa Vishwanath
    Regards
    San
    <a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
    Where There is a <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/16">blog</a> there is a Way.

  • Error Importing IDOCs in SM58

    Hello,
    I'm trying to import an IDOC by RFC with a RFC user with few permissions.
    The Idoc stills with error in SM58 transaction with message "You're not authorized to send IDOCs of message type ORDRSP"...
    If a press F6 to "in theory" reprocess the message, I receive the message "Function Module does not exists or EXCEPTION raised".
    I work in R/3 4.6C.
    Could you help me with the authorizations needed to import the IDOC by RFC in my RFC user ??
    Thanks in advance

    Authorization problem

  • Transactional RFC

    hi experts,
    In SM58(Transactional RFCs) Status text showing "document is being distributed changes are not possible".
    why this error comming.
    Any one can help me out in this.
    Regards,
    Babu

    Hi Babu,
    In general, when you create any BP or Material or Order in R/3, it will move to CRM.
    Now if you try to edit that document in CRM, it will give the error message "document is being distributed changes are not possible".
    This can happen vice versa too, I mean if you create data in CRM and if it moves to R/3.
    If you have not done any settings regarding changing data after moving one system to another, this error message gets triggered.
    Check the below link to have a clear picture.
    Document is being distributed - changes are not possible
    Hope this helps.
    Thanks.
    Best Regards,
    Arun Sankar.

  • SM58 and SM59

    Hi All,
    What is the use of SM58 n SM59? How to use these T-Codes effectively ? I wanted to get some info bout Transactional RFC also.
    Thanks.
    Edited by: sap bw on Feb 11, 2008 2:52 AM

    Hi,
    SM58 - Transactional RFC (Remote Function Call). BW uses tRFC for data transmission and this transaction will list all the RFCs associated with a request. You can get details like target system, status, RFC id, etc. so that you can check in BW whether there was any errror with the RFC.
    SM58 is used to monitor the data packets coming into BW from the R3 side or from BW to BW. You can see every data packet through this transaction. So if any data packet is stuck in the source system, then you can basically see that from this transaction and take the necessary action to push it through. TRFC is nothing but Transactional RFC which connects the 2 systems and is used for sending data from one system to other.
    It'll be there for any load, full or delta coming from the source system. You can push them manually by clicking on the data packet and then hitting key F6. you can do that for most of the errors, but for say that the background user password has changed or if the user is locked, you need to change that first then reprocess.
    SM59- During the extraction process a job will run in R/3 side and we could see the status of that job in SM59 like what tables it is accessing and how many records and all
    RFC destination is connection to source system and BW we need to set up this on both the sides.
    Please check this link
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/67ee407552742ae10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/42/e7a9753c303ee4e10000000a1553f6/frameset.htm
    BW connectivity document
    http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
    Hope this helps,
    Regards
    CSM Reddy

  • Work Flow EVENT - SM58 Entries are not executing automatically

    Hi Experts,
    I have used the standard BOR2034 for creating PO after saving the contract.
    I have developed an RFC enabled FM refering to the Standard FM SWW_WI_CREATE_VIA_EVENT.
    Inside the custom FM I am calling the BAPI_PO_CREATE1 for creating PO.
    After creating a contract using VA41 I am able to see in Event trace that my Event with corresponding custom FM is triggering.
    and the two entries are created in SM58 - Transactional RFC one is my Custom FM name and another is SWF_EVT_HANDLER_START_INTERNAL.
    When I execute the LUW by selecting execution, PO is getting created. Where as this entries are not picking automatically.
    I want to know, whether I have missed any step in process or do we need to schedule any job for automatically clearing the SM58 queue entries.
    Please help me in resolving the issue.
    Responses are highly appreciated..
    Warm Regards...

    Hi Natasha,
    As you say that you see the below entries in TRFC monitor, you need have a commit work after the below FMs are called(just one will do),
    the two entries are created in SM58 - Transactional RFC one is my Custom FM name and another is SWF_EVT_HANDLER_START_INTERNAL.
    How and from where are the above FMs called?
    Regards,
    Chen

  • SM58 Standard Processing Job?

    is there an SAP standard Program for processing SM58 entries?
    Thank-You.

    Tom,
    Go to SM58 transaction and select System Menu --> Status :  There you can find the program name using for  this transaction. Similarly you can check for all the transactions.
    ---Satish

Maybe you are looking for