RFC destination error in SM58

Hi,
We are getting an error in SM58 "P85040 does not exist".
What could be the reason for this error in PI system?
When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
Kindlly help.
Thanks,
John

Hi John,
The reason can be the host name you are assigning is not existing.
In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
Sachin
Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

Similar Messages

RFC destination error while importing a client request

Dear Experts,
We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
The data file and co file in the backend of development is the same size as that of the Prd system.
I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
Regards,
Suratharajan .S

Hi Suratha,
Goto STMS->system overview and select the Communication tab.
Maintained the Instance number of the ASD system.
Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
Also distribute the configuration after entering the instance number.
With Regards
Ashutosh Chaturvedi

Interface RFC destination Error

Hi, while testing our interfaces we get this error, Stack>Error: Transaction IDX1: Port HED_020, client , RFC destination contain errors
We have checked IDX1 and SM58/59 and cant find any error.
Has anybody come across this before?
Thanks

Where do you get this error? In MONI or in SM58?
Make sure that the User Id in the RFC destination has the authoizations to post Idoc's.
Make sure that the receiver Idoc adapter has a valid Port name and RFC destination values as created in IDX1 and SM59
Regards
Bhavesh

Third Party (Garnishment) checks - RFC destination error

We have an issue with our testing of Third Party Garnishment checks. We have a split system, with our HCM system residing separately from the remaining ECC modules.
We are getting an error in regards to the printing of the checks in A/P.
The posting is working fine
the vendor account is cleared
However, It’s not creating a check # or check form.
We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
The text of the error message is as follows: An RFC destination could not be specified for the logical system HPQCLNT210.
We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
Can someone offer suggestions on what else we could check? Thanks so much.

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

RFC destination error in posting 3rd party payment in 4.7 FI system

Hi,
We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
The error says "An RFC destination could not be specified for the logical system HD1CLNT014
    Message no. B1550
Diagnosis
    An RFC destination should be specified for the logical system
    HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
    local logical system and this system is not included in the relevant
    Customizing tables.
Procedure
    Check:
        -   RFC destination
           -Port definition
         -oubound partner profile of message type SYNCH for this logical system
We checked our configuration for all Logical system and RFC destination and everything seems fine.
Any help in this regard is appreciated.
Thanks
Kesav

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207.
When we test newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

RFC DEstination Error

After creating the Destination in sm59 I tested the connection.
When testing the connection, it gives the result as
Connection type:    R/3 connection
Logon:                      2 msec
   0 KB:                    0 msec
10 KB:                    1 msec
20 KB:                    1 msec
30 KB:                    1 msec
I'm trying to create a rfc destination to php in the same system with the same hostname in which SAP is also running...I'm working with ides.
but when I try to run my php file inside sapclasses in www directory it gives an error as
SAPRFC extension not loaded
Message: This script use SAPRFC extension module for PHP and the extension isn't loaded. You can download it with installation instructions from http://saprfc.sourceforge.net. If you have already the extension compiled and installed, check your php.ini configuration

Here's a full text of the error I receive
<b>Error when processing your request
What has happened?
The URL http://<host_server>.com:<port>/sap/bw/BEx was not called due to an error.
Note
The following error text was processed in the system BQ1 : com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
The error occurred on the application server <host_server> and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE of program CL_RSRD_DISTRIBUTOR_KM========CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Form: EXECUTE of program CL_RSRD_SETTING===============CP
START-OF-SELECTION of program RSRD_BROADCAST_PROCESSOR
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BQ1 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server <host_server> in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server <host_server>. In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http-c:100-u:COLLINS -l:E-s:BQ1-i:<host_server>_BQ1_00 -w:0-d:20051012-t:121010-v: RABAX_STATE-e:CALL_FUNCTION_REMOTE_ERROR
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
</b>

RFC destination error in transport

Hello,
We are trying to import a transport into our BW QA system and we keep getting return code 8 with the following text:
BW RFC destination <systemname> is not maintained in the source system
Message no. R3078
The transport contains cubes and three ODSs. After the transport fails and I check the QA system, the cubes are active, but the ODSs are not.
I searched SDN and found another thread explaining the same problem and I tried everything suggested there. I looked in RSA1 --> Mapping of the source system names, and the BW DEV and QA systems are listed. I also looked in SM59 and checked the RFC connection, and that is ok as well.
Does anyone have any suggestions?
Thanks
Charla

I have searched OSS further and found that the contents of my RSLOGSYSDEST table are off.
The contents are as follows:
Src System    RFC Destination
AWQ100          AWP100
QAT100          QAT
I believe that in the above table, the AWP100 should be AWQ100. I looked at this table in our production environments, and in those cases the Src system entry and RFC Destination entry are the exact same, so I think this should be the case in our AWQ100 system as well.
Just curious if anyone knows if there is a program I can use to modify this table.
Thanks
Charla

System crash RFC destination

Hi,
When creating projects it fails with the messages:-
1) System crash RFC destination , Call TMW_VERSION_TEST: User SAPSYS has no RFC authorization for function group TMW_TRACKING .
2) System crash RFC destination , Call TMW_VERSION_TEST: Name or password is incorrect. Please re-enter.
3) RFC destination error SM_PRDCLNT000_READ: RFC task PRD:000:TMW_GET_FULL_LIST already open.
It is my understanding that 1 and 2 are related. The question I have is: How do I assign auhtorisation for SAPSYS to the function group TWM_TRACKING?
Regards

Hi Ferrandi,
See if these notes are relevant to your scenario:
Note 896042 - RFC access from satellite systems generates dump
Note 920805 - Correction of the FM TMW_VERSION_TEST in Note 804198
Also Which user do you use to generate the RFC`s??? Check the authorization for that user to generate RFC`s.　Ｔｈｅ　ａｕｔｈ　ｏｂｊｅｃｔ　S_RFCACL and S_RFC which is not a part of SAP_ALL profile should be assigned to the user.
Hope this is helpful.
Regards,
P. Kumaravel.
Ps: Award points for helpful answers.

RFC channel error

Hi Experts,
First time, transport objects form DEV to QTY server in SAP PI 7.31 dual stack.
My scenario is RFC to JDBC. Activation is done, but when try to test RFC destination from ECC qty (which freshly created in ECC QTY) getting some error in sender channel.
RFC destination error
for Unicode test
Any suggestion to resolve this issue?
Thanks,
Arthita

Hi
Two check if the program is registered go to SMGW.
Go to --> Logged on clients. Here must appear your PROG_ID
If not, check authorizations to register external programs (RECINFO and SECINFO)
Regards
Javi

RFC Destination contains errors

Hello,
I am doing a IDOC - File scenario.
for XI :
RFC : R3RFC
Port : R3PORT
LS : XICLNT010
for R3 :
LS : CLNT090
RFC : XICLNT100
Port : XI100
When the IDOC was sent, its showing up in green color but when I go to SM58, I see the error message, " Transaction IDX1: Port SAPB999, client 800, RFC desestination contains erorrs "
But when I click on remote logon, the RFC is taking me to XI start sap access screen (same is the case with XI RFC connection, working as expected)
No messages were shown in SXMB_MONI
The port specified in the error message and the actual port varies.
Checked in port... specified a proper RFC destination.
Where are the things going wrong?
Checked previous answered posts related to the same and tried few things from them
dint work out..
Help !!!
thanks
Nikhil.

Hi,
Check the User you are providing in RFC Destination is Exist & have the Proper Authorizations
In XI Side RFC Dest::
Give the User name & PWD in RFC Destination , Which you are using for R/3.
In R/3 Side RFC Dest:::
Similarly Give the User name & PWD in RFC Destination , Which you are using for XI
Regards
Bopanna

Rfc to file scenario error in sm58

rfc to file scenario error in sm58
i get the error as com.sap.aii.afccommunication.RfcAfwException
:look up of alternative

hey
>>i have a doubt do we have to use
starting new task or back ground destination
well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
have a look at the following
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
thanx
ahmad

RFC Error in SM58 Commit fault

My scenario is RFC to XI to FILE.
I made RFC destination in SM59
and configure xi according to
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
The connection test in SM59 is succeeded.
I would like to execute BAPI, so wrote following..
CALL FUNCTION 'BAPI_CUSTOMER_GETLIST'
       IN BACKGROUND TASK
       DESTINATION 'BAPI_XI_001'
   <<< parameters >>>
   COMMIT WORK.
BUT in SM58, I got error
'Commit fault: com.sap.aii.af.rfc.afcommunication.
RfcAFWException: alterna '.
Any ideas?
Best regards.

Thank you very much for your information.
I checked Q&A19 of SAP NOTE 730870
and configured XI again.
Then I got a different error...
' program BAPI_CUSTOMER_GETLIST not registered / CPI
C-CALL: 'ThSAPECMINIT'# '
I have already checked the spelling of BAPI's name.
Have you saw this error??

RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication

Have a RFC interface between Sap R/3 and XI. Submit RFC request: call function 'Z_PGM'
        in background task
        destination 'XID'
        tables
          it_zmsfi_labels = t_table.
Getting error in SM58 in R/3 : Commit fault com.sap.aii.af.rfc.afcommunication.Rf cAFWException: alternat
Message no. SR053
Any ideas? If I do test connection on in SM59 on TCP connection it's Ok.

call function 'Z_PGM'
in background task
destination 'XID'
tables
it_zmsfi_labels = t_table.
<b>COMMIT WORK.</b>
This should solve your problem.
regards
SKM

Error in Local Message System: RFC destination MB3AP1039 does not exist.

Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
Can anyone help me in resolving the above issue.
Thanks & Regards,
Mirza Kaleemulla Baig.

Dear friend
You have to of following option
1.Define Service Desk destination in the R/3 systems:
Note: for this you need to log in the R/3 system.
Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
2.a. Go to transaction SM30.
b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
c. Press the Continue button in the following screen:
d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
e. In the next screen, enter the following information:
In the RFC Destination you should point to your Solution Manager destination RFC.
0ss_msg w sm_bsmclnt_back cust620 1.0
shailesh

RFC destination error in SM58

Similar Messages

Maybe you are looking for