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

Similar Messages

How to configure RZ12 and SM59 ABAP connection settings when we have work with Load Balancing servers rather than a specific server .

Hi ,
If we have a specific server say 10.10.10.10 (abc.co.in) on which we are working, Then under RZ12 we make the following entry as :
LOGON GROUP          INSTANCE
parallel_generators        abc.co.in_10         ( Lets assume : The instance number is 10 )
Now in SM59 under ABAP Connections , I am giving the following technical settings:
TARGET HOST          abc.co.in
IP address                  10.10.10.10
Instance number          10
Now if we have a scenario of load balancing servers with following server details (with all servers on different instance numbers ) :
10.10.10.11
10.10.10.13
10.1010.10
10.10.10.15
In this case how can we make the RZ12 settings and SM59 settings such that we don't have to hardcode any IP Address.
If the request is redirected to 10.10.10.11 and not to 10.10.10.10 , in that case how will the settings be.
Regards,
SHUBHAM

Hi,
No one using FMS behind a load balancer? No one using RTMPT?

Exporting WE20, WE21 and SM59 Entries

Hi,
Can anyone knows how can we export or keep a copy of WE20, WE21 and SM59 Entries for later use. As We are going to refresh the development server with quality and wish to restore the orignal DEV servers parameter (Enteries) settings.
How can we do Export and Import. Pl. suggest me some solution.
Thanks,
Raj

Try this Script . Go to /usr/sap/trans/bin create a file ( <filename>.ctl > with the following entries
export
file '/usr/sap/trans/data/filename1.dat'
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
delete from rzlliclass
select * from rzlliclass
delete from sxroute
select * from sxroute
delete from rfccheck
select * from rfccheck
2 ) execute the command R3trans -w <filename>.log <filename.>.ctl , a log file will be created in /usr/sap/trans/bin with the file name <filename>.log , R3trans return code should be 000 0r 004.
3) If you want to reimport it to the same system at a later point of time create a script <filename2>.ctl in /usr/sap/trans/bin
import
file '/usr/sap/trans/data/filename1.dat'
4) R3trans -w filename2.log -u 1268 <filename2>.ctl
The return code should be 000 or 004 , compare the no of table enties in the exported and imported log files , they should be in sync .
Edited by: Mann Mohandas on Feb 20, 2010 8:33 AM

Export partner profiles and SM59 Entries before system refresh

Hello All,
How to Export partner profiles and SM59 Entries before system refresh in Netweaver
thanks
Shyam

In SDN search with name RFC export ..you will get so many answers ..
Once again please find the below prcoess for RFC export/import during system refresh.
RFC Export --
go to trans dir.. and then create .ctl file as below
#cd /usr/sap/trans/bin
#vi export_rfc_<sid>_<date>.ctl
#Please create the data file as u201Cexport_<SID>_rfc_<Date>.datu201D
Export
Client=<XXX>
file '/usr/sap/trans/data/export_<SID>_rfc_<Date>.datu2019
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rzllitab
select * from rzllitab
delete from ZTCA_USER_LANG
select * from ZTCA_USER_LANG
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
#After that excute export command as below.
R3trans u2013w <export_rfc_<targetSID>_date.log> export_rfc_<targetSID>_date.ctl>
(Format is: R3trans u2013w <logfile> <controlfile>)
Export is finished....
Import
Example:
#cd /usr/sap/trans/bin
#vi import_rfc_pta_11042004.ctl
#Please enter the exported RFC data file in the import control as follows:
import
file '/usr/sap/trans/data/export_pta_rfc_11042004.dat'
(Enter the file name, which is created during the export process)
Regards,
Srinivas Chapa.

Sm58 and RSARFCEX

Hi Guru 's
Can anybody tell me what is sm58 T-code .
I have R/3 , BW and APO system . Both APO and BW system are connected via rfc to R/3 .
I find some old request of last month in error . I dont know what to do with this .
Which tables does this error request get populated.
Also , what is the report " RSARFCEX ", what does it do and what frequency should we scheduled this report .
Regards
Anthony

Hi Anthony,
transaction SM58 is a report for monitoring the status of transactional RFC.
So with this transaction you can monitor the status of the tRFC communication towards your APO and BW.
The reason why somethimes it happens that you have an entry in that report is that an error happened (you can see the error description by double clicking on the status, tipically SYSFAIL) while trying to deliver a message to the target system.
For example if the user and password specified in the RFC destination are wrong (in transaction SM59) you'll get an error status in SM58.
Once you see an error you can manually restart the execution of the RFC.
Report RSARFCEX is used to automatically restart the execution of messages in error status so you get rid of temporary errors.
The scheduling frequency depends on your requirements but tipically it is scheduled every 5 or 10 minutes.
Regards,
Sergio

IDOC Error in SM58 and Management Console

Hi Guys,
Good day!
I am currently having issues on sending IDOCs to BODS.
There are instances that an IDOC gets stuck or ends up with an error in transaction code SM58. In transaction WE02, the IDOC is
successfully processed with status 03. In a set of IDOCs (10 or more), one IDOC is in error in SM58, usually the first IDOC gets the error and the next IDOCs are successfully processed. The error received in SM58 displays the following:
Error 1: R3RfcClient(DI_CLIENT)ActaIDocFunc::Process()...
Error 2: CPIC-CALL ThSAPCMRCV no data received
However, the client interface is active/running.
In the management console, the error Logs-History displays the following:
(14.0) 04-08-14 23:32:51 (E) (8060:3868) Unknown: SP(INVOICE_001, ABC:1234)::flowThread() Flow became
invalid during waiting for request (BODI-300137)
(14.0) 04-08-14 23:32:51 (E) (8060:9356) Unknown: R3RfcClient(RFC_CLIENT_INTERFACE) ActaIDocFunc::Process()
encountered processing error for Requeste(15149) (Communication Error. See real time job log for details.) (IDOC 0000001234567890/ABCDE). (BODI-300129)
For the Real-Time Services log, the following is displayed:
(14.0) 04-08-14 23:32:39 (E) (70684:47620) RUN-051005: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS Execution of <Regular Load Operations> for target <IDOC_DETAILS> failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.
(14.0) 04-08-14 23:32:50 (E) (70684:68856) DBS-070401: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS ODBC data source <ABC\ABC,12345> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host. >.|<Regular Load Operations>|<IDOC_DETAILS>
Given this, I would like to ask on how to eliminate this issue.
Thanks,

Getting Error in SM58 and IDX2 while using IDOC from

Dear All,
Getting error when trying to send FIDCCP02 Idoc from ECC to PI system.
"Basic Type 'FIDCCP02' is unknown"
Getting the same error while trying to import metadata using IDX2 from PI side.
All connections and distribution model are created.
Please help
Regards

hey,
I checked all config again but getting error while checking ocnsistency in BDM5 on ECC system(E1Q).
It is failing when the messge type FIDCC1 reaches PI QA (X1Q) system and the error states
Message type FIDCC1 is not defined
Please check last line of below message:
E1QCLNT001     Checks in own system E1QCLNT001
     Message type     @08\QCheck OK@     Message type FIDCC1 is defined
     Segment filtering     @08\QCheck OK@     No segment filtering
     Conversions     @08\QCheck OK@     No conversion
     Partner profile     @08\QCheck OK@     Partner profile has been created
                                @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Packet size 0001
          @08\QCheck OK@     .....Basis type FIDCCP02
          @08\QCheck OK@     .....enhancement
     Port     @08\QCheck OK@     Port PI_QA : To PI Quality System
          @08\QCheck OK@     .....Port type: Transactional RFC
          @08\QCheck OK@     .....port version 3: IDoc record types from Version 4.0 onwards
          @08\QCheck OK@     .....Logical address (destination) X1QCLNT001
     Logical address (destination)     @08\QCheck OK@     Logical address (destination) X1QCLNT001 is defined
X1QCLNT001     Checks in partner system X1QCLNT001
     Check of own logical system     @08\QCheck OK@     Own logical system is X1QCLNT001
          @08\QCheck OK@     Logical system is the same as the target address
                   Message Type     *@0A\QCheck resulted in error@*     Message type FIDCC1 is not defined
When I am clicking on error it is taking to WE81 on PI side.
So do I need to add this message type in PI system as it is present in ECC side?
Thanks
Edited by: Chanakya Sharma on Dec 10, 2010 12:10 PM

Shure SM58 and baggs M1 acoustic guitar pickup

I have tried to get a 'true' acoustic sound using the above, Using two mono dry tracks, zero settings, I am getting a delayed response signal through my headphones when I play. What have I forgotten to do? I never had a problem with Garageband. I'm new to Logic and one of those guitarists who record dry tracks and adds effects when mixing down, done.

Try these:
1. verify if your M-Audio has a zero latency monitoring;
2. low the buffer size;
3. disable Logic monitoring.
cheers
rob

Source system not available error

If the error message is teling as source system not available
so what can be the reasons for that and tell me the solution also.
data cllection is incorrect
so what can i do i have checked trfc connections every thing but every thing is fine
so any body help me out in this.
your suggstions will be rewarded.
Regards.
Vikram.

Hi Vikram,
Try the below mentioned steps:
1. Check the connections on BW sysetem and R/3 system.
Use the tcodes: sm58 and sm59. On the context menu of the source system created, check the option for conections. If connections are not fine, contact the basis team
2. Go to 'source systems' select you source system and right click and select 'Repicate Data Sources' , then try replicating the the infosource for that
appilication at the top node level as a whole, the try replicating the Data source
with in your infoarea..
Hope it would help ..if yes..assign points.
Regards,
Manu.

Trouble shooting PI

We have a problem where everything looks good in SXMB_MONI. The XML document is sent into our system.   However, the ABAP code is not getting triggered.   This has worked for 2 weeks and until around 12:30 today.
We've checked SM58 and SM59.   Everything looks good.
SU01D, the PI user looks good. There are not any locks.
Any other ideas?   THere are not any errors. Nothing in Sm21 or ST22.
Are there any other transactions that you would look at for this kind of a problem?
Any information would be helpful.
Thank you,
Michelle

Hey
In SXMB_MONI,scroll to the right and see whats the status under "Outbound Status "column?
If it is red or green flag,then the messages are stuck in queue,if it is chequered flag,then the messages were delivered from XI correctly.
Thanks
Aamir

Trfc issue

how can we solve Transact Rfc issue "

TC SM58 AND SM59.
but this is actually a BC task

Transfer (Idocs and TRFC): Errors occured

Dear All,
data extraction from R/3 into BI is working for small number of records. for huge number of records it ends with error,
i have adjusted info package setting DataS. Default Data Transfer but did't work. on the R/3 side i can see "transaction recorded" on tcode SM58 and the job successfully completed
please share me your experience on this issue,
With Regards,

Okay then I would think that there is some cofiguration issue related to communication between two system. Can you check below:
1. SM59 - RFC connections are wroking fine?
2. Any stuck Idoc or failed idocs in WE05/WE02- just trigger the infopackage and have look at WE05 and monitor the idocs. It may happen that you are able to recieve the Idocs but not able to send it back.
3. Configuration in WE20 for partner profiles in ECC system for your BW system. mainly outbound parameters message type RSSEND. Check if is as transfer immedeately.
4. Try executing your datasource in RSA3 with same exact selections as you pass from BW.
5. Check if you have any short dumps in ST22.
6. Check logs in SM21.
7. Try running infopackage for the same selection from past when you know it worked fine.
Please let me know findings.
Thanks
Amit

Generating and transferring purchase requisition IDoc

In ECC 6.0 there exists ALE_PR_CREATE which gave us all the required fields for generating the IDoc that we needed to transfer to our JCo program. Once the IDoc was generated using this program, it's status was set to '30' automatically.
The next step in order to send this generated IDoc to the designated port was to make use of the standard program RSEOUT00 passing the message type so that it sends all IDocs, of that particular message type (PREQCR and PREQDL in our case) and having a status of 30, to the port, changing the status to 12 once this operation is completed.
Since it was a standard program , I used the same logic in 4.6C. Unfortunately, the function module ALE_PR_CREATE does not exist in 4.6C.
The alternative was to use ALE_REQUISITION_CREATE and ALE_REQUISITION_DELETE.
Why 2 Function modules? Here's why...
The first function module gave us all the required fields except one - the deletion indicator.
Keep in mind that this field was also provided by ALE_PR_CREATE in ECC 6.0 system thus eliminating the need to look elsewhere.
So, to satisfy our requirement of getting the deletion indicator for deleted items of a particular Purchase requisition, we found the second mentioned function module - ALE_REQUISITION_DELETE.
This threw another problem in front of us...
This function module gave us only the purchase requisition number, item number and deletion indicator. All the other data fields that we required for our java app to process the IDoc were missing.
In order to solve this issue, we have designed our program to generate 2 IDocs one after the other. First using ALE_REQUISTION_CREATE and next using ALE_REQUISITION_DELETE in sequence.
This gives us all the fields.
The next problem was that the generated IDocs were having the status 03 (Data passed to port. OK.) but the Java application never seemed to receive the generated IDocs.
A search on SDN led me to check the IDoc queue in SMQ1, a case of stuck IDocs in SM58 and also changing IDoc status in BD75 all in vain.
Finally, on debugging the RSEOUT00 program, found out that it is checking for the status '30' (IDoc ready to be sent to port) which is hard coded in the program.
On doing further research on SDN, find some resources that suggested various function modules.
Tried out all of them one after the other.
By trial and error, finally stumbled upon the Function Module 'DEQUEUE_ES_EDIDOCS' that acted as a replacement to using the RSEOUT00 program.
After the IDoc is generated, just passing the IDoc number to this Function module sends it to the port and this was successfully received by our Java app.
Posting this on SDN for the general benefit.
Has anyone faced any similar issues? Let us know.

Hi,
Im using the non-enjoy BAPI and BAdI for PR and for deletion the outbound IDoc gets send out all the way but for create outbound IDoc it gets stuck in status 30. I did try the FM that you suggested but doesnt have any effect.
FMs that is being used inside my BAdI:
ALE_REQUISITION_CREATE
ALE_REQUISITION_DELETE
Thanks,
Arash

Alert in case of errors in XI tx sm58

Hi,
we discovered that we sometimes (not more often than once a month) have errors in XI tx sm58, e.g. when a target SAP system has been down and idocs have not been delivered.
Is there an easy way to monitor sm58 and send e.g. an email in case of errors?
Thanks,
Philipp

Hi,
May be you can have a check on "ARFCLOG" table so that you can generate the alert.
for the blocked/Queued IDocs.
Hope this helps.
-Prasad Babu.

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 and SM59

Similar Messages

Maybe you are looking for