Available RFC Destinations

Hello,
How can i check the available RFC destinations in J2EE engine on Portal.
(without Visual Administrator)
Regards

Hi,
you could for example check the JCO log in the J2EE:
<root>\usr\sap\<SYSID>\DVEBMGS00\j2ee\cluster\server0\dev_jrfc.trc
As well you could check the server or default trace.
--> from above location
.\log\defaultTrace.0.trc
.\log\server\server.0.log
For that you could use the log viewer of the J2EE (under services).
As well check all the settings for the JCO service in the J2EE.
Rgds Thomas

Similar Messages

Error-The RFC destination EDSCLNT900 is not available in ICWC

Hi All,
I'm working on CRM Utilities 2007. In the ICWC, I'm getting the error 'The RFC destination EDSCLNT900 is not available'. Kindly help me in resolving this error.
Regards,
Archana.
Edited by: archu_sap on Jul 15, 2009 10:30 AM
Edited by: archu_sap on Jul 15, 2009 10:33 AM

Hi,
You have to maintaine RFC Destination EDSCLNT900 in the CRM system.
generally we have to maintain RFC (t-code SM59) in the sytem where Function Module is present.
Suppose you are having FM in ECC system and you want to call in CRMsystem, then you have to maintain RFC destination (EDSCLNT900) in ECC system.
Thanks & Regards.
ShreeMohan

The RFC Destination ALESERVER is not available

Hi ,
I am getting the error message " The RFC Destination ALESERVER is not available " in my CRM Web UI screen.But when I login with another User ID , this error message is not showing.
RFC connections are maintained in transaction SM59 and BD97.but I m still facing with this issue.
Please advice what could be the cause of error.
Regards,
Ravi

Hello,
please check in SM59 the LOGON-User for this RFC-Destination.
Maybee the user where it works is maintained, the other not.
Or if there is a general RFC-User maintained the user where it does not work has maybee not the authorization in the target.
Best regards
Manfred

CCMS aler for RFC destinations availability

Hi Experts,
We have configured ccms alert autoreaction method for availability of RFC destinations.
alert is configured with yellow thershold as 10% and red threshold as 5%.
alert text is :&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)".
We are receiving mail alerts for CCMS red alert for RFC saying" 0 % < 5 % 15 min. avg. value below threshold value (1 measurements) ".
But when we checked the corresponding RFC is working fine.
Can anyone please explain how this RFCs destinations check alert will work and what is the meaning of alert text ":&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)"."
Thank you,
Kavitha

Hi
I have done
1. RFC connection from x to y and y to x
In X system:
1. In transaction RZ21, mark Method definitions, and choose Display overview
Copyed standard CCMS_RFCDest_Availability_Col method definition to ZCCMS_RFCDest_Availability_Col
Parameters tab
For x
Parameter name = RFC_DEST
value = SM_XCLNT510_TRUSTED
Parameter name1 = COLL_METHOD
value = ZCCMS_RFCDest_Availability_Col
Same in Y but for RFC_DEST give
Parameter name = RFC_DEST
value = SM_YCLNT100_TRUSTED
Execution Tab
Type of call = Function module
Call SALK = SALK_RFCDEST_AVAILABILITY
Execute method on = The local server of the MTE to be processed
Execute method for = Individual MTE
Control tab :
Execute method for = Individual MTE
Execute method = periodically in dialog process (short-running program)
Startup method = Execute method immediately after monitoring segment start
Execution location
of startup method = Only on the central instance
Start Tab:
Execute method = Data Collection Method
also try in so many way as in :Parameter Tab:
RFC_DEST               SM_XCLNT510_TRUSTED
COLL_METHOD            ZCCMS_RFCDest_Availability_Col
MTE_CLASS              Availability_RFC_Destinations
MTE_CLASS              CCMS_RFCDest_Availability_MO_Class
MTE_CLASS              CCMS_RFCDest_Availability_Col
COLL_METHOD            CCMS_RFCDest_Availability_Col
RFC_DEST               CCMS_RFCDest_Availability_Col
Problem:
I am not able to Reset the segment in WARMUP status
not able to find the node in RZ20
Regards,
Neni

Checking RFC destination availability

Hello,
In a transaction I'm working on, I loop at a table containing RFC destinations, and I call the same function module on each of these destinations. What I would like to do is, prior to the call, test if the system behind the RFC destination is available (neither completely crashed, nor just blocked by an administrator).
I tried to do this by simply calling any BAPI on the remote system, and check if there was a connection error. But the problem is, if the system is not down but just blocked by an administrator, the transaction suddenly displays the logon page of the remote system.
Do you know of a simple way to do this ?
Thanks in advance.

Hello Thomas
You could try with asynchronous RFC calls (for details refer to the ABAP documentation of CALL FUNCTION).
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Regards
Uwe

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

RFC destination Could not be SPecified for Logical System

Hello there
i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
when on Transaction launcher Wizard--> techincal
i am having a logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
while chosing the OBJ.TYpe :   and Method:
it says shows three erroe :
1) RFC destination could not be specified for the logical system ARD100
2) Object type and Method is not available
i have checked RFC , in SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
could you please help me to resolved the same
Regards
Rajiv

Hi Rajeev,
In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
The following steps are required before a RFC call is made from the CRM system to the R/3 system :
    o Use transaction SM59 to create an RFC destinations for the remote
       system.
    o Use transaction BD54 to create the logical system.
    o Use transaction BD97 to link the RFC destination created in SM59
       with the logical system created in BD54.
I hope this helps.
Best Regards
Gavin

Creation of RFC destination for SAP-Access Connectivity

Hi,
       I want to create a RFC destination for SAP-Access connectivity.
Can I get some help regarding it's connection type,activation type and gateway options required for the same.
Regrads,
Anthony D'souza

Hi
Please see the following:
1. Create an entry in Trxn DBCA for SQL Server in SAP, you are creating a database connection for the SQL server in SAP.
2. You use this connection, and write Native SQL stmnts...between EXECSQL...ENDEXEC to fetch the data..and then normal ABAP statements to put that data into your ztable.
TABLE DBCON Entry can be like this...depends on your External database..
CON_NAME          Raj                      Logical name for connection
DBMS                   MSS                   Microsoft SQL Server
USER_NAME        <User name>       For SQL Server
PASSWORD         <password>         " "
CON_ENV             MSSQL_SERVER=<server> MSSQL_DBNAME=<database name>
DB_RECO                 Availability type for an open database connect
FUNCTION z_houston_connect.
""Local interface:
EXEC SQL.
CONNECT TO 'RAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
*- Get the data from MS-SQL Server
EXEC SQL.
open C1 for
select
l.loc_id,
l.loc_name,
a.acc_id,
a.acc_name,
d.person
from ho_loc_mast as l
inner join snd_acc_mast as a on l.loc_id = a.loc_id
inner join snd_acc_addr as d on a.loc_id = d.loc_id and
a.acc_id = d.acc_id
where l.loc_id = '001'
ENDEXEC.
DO.
EXEC SQL.
FETCH NEXT C1 into :wa-c_locid, :wa-c_locname, :wa-c_acc_id, :wa-c_acc_name, :wa-c_person
ENDEXEC.
IF sy-subrc = 0.
PERFORM loop_output.
ELSE.
EXIT.
ENDIF.
ENDDO.
EXEC SQL.
CLOSE C1
ENDEXEC.
ENDFUNCTION.
Regards,
Raj

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

RFC Destination - Unicode / non - Unicode behavior

Hi All,
In our current production system the RFC destination from R3 to Xi is non-unicode.We have currently 300 Interfaces running using this RFC destination in production.
In few upcoming requirements for some 15 Interfaces some special characters will come from R3 to Xi system.In this case we need a unicode RFC Destination.
I have a query here , can i go ahead and change the existing RFC destination to Unicode or is it suggestible to create a new RFC destination only for these 15 Interfaces?
Need expert advice on this?
<<Text removed>>
Regards,
RK
Edited by: Matt on Oct 5, 2011 9:38 AM

Hello,
The Non-Unicode Single code page systems are supported by SAP for older applications for historical reasons - unicode was not available when they were released. These systems are restricted to only processing characters from their specific code page. This means their can be restrictions if they need to support language combinations that span multiple code pages - basically it is not possible. In addition some languages are not fully available at all for single code page systems like Thai. In addition the Euro symbol is not available.
Unicode is the future for all applications - SAP or otherwise. The significance at the moment is where customers who needs to convert to unicode to support additional business requirements like additional languages. Converting a system, although a simple process is not a trivial process in terms of time and resources.
So u can go ahead and change the existing RFC destination to Unicode .it will not create any prob. for other interfaces which are using non unicode setting.
Regards
Monica

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

RFC destination and webserver settings

Hi,
I need to configure the RFC destination and other technical settings and certainly need help from Basis people. However what inputs we have to give them enabling us to set right configuration. I find different proxy class, RFC destination etc have been set for different object types.
For ex, I want to configure cproject with MM,SD, CO etc
What information as a functional consultant we have to provide to Basis people.
I met with following error in accounting.please tell the path for required settings.
An error occurred when connecting to the accounting system EC6CLNT100
Message no. DPR_FIN_GECCO001
Diagnosis
A connection to the Accounting system could not be made. Possible causes are:
The system is not available
The RFC destination for the Accounting system is incorrectly defined in Customizing.
System Response
The system could not read data from the Accounting system. The system cannot distribute project data to the Accounting system.
Procedure
In transaction SM59 check the RFC destination defined for the Accounting system.
Check whether you defined the correct RFC destination for the object type. See Customizing for Collaboration Projects under --> --> .
Zinni
Edited by: Makwana Zinni on May 27, 2009 1:58 PM

Hi,
I am getting the same error. Could you please elaborate on how you fixed the error. I am not sure what/how to test in tcode SM59. I am following the cofig guide for cProjects but the cProjects screen is still giving me the error msg and I am not able to understand the solution.
Here is the ERROR MSG
An error occurred when connecting to the accounting system
Message no. DPR_FIN_GECCO001
Diagnosis
A connection to the Accounting system could not be made. Possible causes are:
The system is not available
The RFC destination for the Accounting system is incorrectly defined in Customizing.
System Response
The system could not read data from the Accounting system. The system cannot distribute project data to the Accounting system.
Procedure
In transaction SM59 check the RFC destination defined for the Accounting system.
Check whether you defined the correct RFC destination for the object type. See Customizing for Collaboration Projects under --> --> .
ANYONE'S HELP WILL BE APPRECIATED!!

Error message when calling a Business Connector RFC destination from SRM

Hello all,
We are facing one problem with data Purchase Order transmission between SRM 5.0 (SRM_SERVER 5.5, extended classic scenario) and Business Connector 4.7.
We made needed customizing in order to have "XML / XI" output medium available in tab 'Company Data' in "Manage Business Partners" web transaction (by updating BBP_USE_AI table in SM30 transaction).
Then, we implemented BAdI definition BBP_EBPXML_OUT_BADI with method PURCHASEORDER in order to change XI system type to Business Connector.
In this way, PO transfer data between SRM and BC is done using BC Module Function BAPI_POEC_XML_SEND (TCP/IP RFC connection was defined for Purchase Order in BBPC_RFCDEST table).
Nevertheless, even if method BBP_PO_SEND_XML is correctly triggered when PO is created with a vendor with XML output medium, we have in the document output log ("Process Purchase Order" web transaction) an error message:
' Error (Unknown Partner and Message Type. Routing Rule created. Sender: SMR Receiver:) when calling RFC destination BC '
where SRM is the SRM log. sys. and BC the Business Connector log. sys.
Our EAI team is working on it, but if you have any idea, your are welcome !
Thank you in advance.
Regards.
Laurent

Hello Christian,
Thank you for your help. However, we abandoned this solution between SRM and Business Connector.
So, we followed instructions indicated in OSS note 883693 - "ECS: PO output determination in R/3".
Nevertheless, in order to restrict this behaviour for specific vendors and purchasing organizations, we added some filters.
It is working fine.
However, when the PO is modified in SRM, then order again, PO is modified in R/3 (by the RFC user from SRM) more than once.
As a consequence, we have as much messages as modifications of the order in R/3 (due to multiple RFC access with the SRM RFC user).
Does anybody have an idea to have only one R/3 output message when the PO is modified in SRM ?
One solution could be to check in the NAST table if the time creation of the last output message is lower than, for example, one minute.
If it is the case, we do not allow R/3 ouput message.
Any suggestions is welcome.
Regards.
Laurent.

Transaction IDX1: Port SAPPRD, client , RFC destination contain errors

Hi all,
when I send an IDOC from Xi to R/3 I get the following message in XI monitoring:
Transaction IDX1: Port SAPPRD, client , RFC destination contain errors
ERROR= 2:IDOC_ADAPTER(151)
However everything is maintained correctly (i think) in IDX1. I can upload the IDOC metadata with IDX2 from the R/3 system.
I seems that Xi doesn't have the clientnumber available. (should be 600) but is not mentioned in the error.
Did I miss something?
Thanx Ron
Message was edited by: Ron van der Sterren

Hi Ron,
Settings in XI side.
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is R/3 server name and logon tab enter the R/3 logon details.
Test the connection is success and check the Remote login button it's connecting the R/3 system or not.
2. Create the Port IDX1 and pass the client number is (R/3 client) and pass the RFC destination which you created above.
R/3 side
1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is XI server name and logon tab enter the XI logon details.
Test the connection is success and check the Remote login button it's connecting the XI system or not.
2. Create the TRFC port to transfer the IDOC'S and pass the RFC destination which you created above.
3. create the logical system in BD54 this name should be same as XI logical system name.
4. Create the partner profile (WE20) and partner type is 'LS' with inbound parameters and pas the appropriate values.
Let me know if you have any issues.
Regards,
venu.

RFC Destination None Error for MIGO

Hi,
I am getting RFC Destinatnation NONE error while posting Goods Receipt. GTS service for SD and MM is not active. Error showing for FM GRC01_COST_OBJECT_COST.
Can any one help in this regard.
Thanks in advance.
SP Raj

Hi,
Pl find the details below of the error.
Short text
    RFC destination "NONE" does not exist.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLCK36" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The 'destination' "NONE" for a Remote Function Call
    is unknown.
    You can display the RFC destinations available in the system using
    the transaction SM59.
Trigger Location of Runtime Error
    Program                                 SAPLCK36
    Include                                 ISAUTO_CK_SAPLCK36============E
    Row                                     812
    Module type                             (FORM)
    Module Name                             PRICE_STRATEGY_NEW
806 ************************************************************************
807 *     DOERNER, GRC, 10/11/1999: Add one new strategy:
808 * 3b. Create costestimate during goods receipt
809 ************************************************************************
810     when 4.
811       if k_debug_loc is initial.
>>>>>         call function 'GRC01_COST_OBJECT_COST' destination 'NONE'
813                 exporting
814                      im_vbeln     = f_mtcom-vbeln
815                      im_posnr     = f_mtcom-posnr

Available RFC Destinations

Similar Messages

Maybe you are looking for