Debug RFC destination system

Hi,
debugging production system A, I call an RFC function module in production system B, but instead of starting debugging system B, it continues debugging next step of system A.
I don't know why this is happening, I can debug both systems A and B separately, but when calling B from A, I cannot debug system B.
My user in system A is: des005
My user in system B is: des005
The passwords are not the same.
Thanks in advance

Hello Joan
Here is my recommendation to facilitate debugging:
DATA:
ld_rfcdest     TYPE rfcdest.
ld_rfcdest = 'EDURFC'.
call function 'ZRFC_UPDATE_PROJECTE' destination ld_rfcdest
                      exporting
                        i_projecte       = lwa_projecte
                      tables
                        o_messtab        = it_messtab
                      exceptions
                        no_exist_pepampl      = 1
                        system_failure        = 2
                        communication_failure = 3
                        others                = 4.
If you cannot debug using RFC destination "EDURFC" then I recommend to define a dummy RFC destination (e.g. "SysB" which just contains the technical details of the remote system.
Set a break-point at the CALL function statement and then overwrite LD_RFCDEST with the dummy RFC destionation.
The login popup will appear and if you are allowed to do debugging in the remote system you should be able to do so.
Regards
Uwe

Similar Messages

RFC Destination (ABAP) to use Single Sign on

How do I configure an RFC destination to take the current user-id and connect to the RFC destination system without prompting for logon? (I do not look for a dedicated user-id pwd option - must use the current user's id)
SNC is configured, and when I doubleclick in sap logon pad, I get connected to the corresponding SAP system without the login screen. Specifying the same parameters in the SNC def (SM59 - change destination) doesn't make any difference and returns an RFC error when trying to test.
I have checked SSO links (some) on SAP help site (Do I need to configure the system in SSO2?). From portal and all it works fine. Not sure what specific config is required to connect to ABAP RFC destination to use SSO (or SNC whatever it be) to not throw the login screen.
Any help?
Thanks,

i assume you are talking about to ABAP systems.
check this link, you have to set up trust relationship between the systems.
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/22/042671488911d189490000e829fbbd/frameset.htm">Trust Relationships Between SAP Systems</a>

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

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

Service desk RFC destination in the Satellite system

HI All,
can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
Thanks in advance
Regards
Amit

Hi Amit,
I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
Sorry but I am quite sure that it is working like this.
There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
Regards,
uDo

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 BW could not be created in the source system R3073

I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
RFC destination BW could not be created in the source system message number R3073
Why is this happening? The connection tests just fine.
I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
Any ideas?
thanks

Hi,
I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
Create your BWDEV RFCDEST manually in your BWQA .
Perform test and authorization test within SM59 from both sys.
When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
hope this helps...
Olivier.

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

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

HOw to find out the RFC destination from BW system to ISU

Hi,
Currently my requirement is to call a function module which is written in ISU (remote enabled) from BW system.
I am unable to find out the rfc destination from BW to ISU system.
In CRM we have table like smofparsfa1. Is there any table in BW which can provide me the ISU destination?
I need to compare the records stored in isu as well as in BW system.
I need to call a function module which will provide me the data from isu.
please help me in this regard.
Krishna

Hi,
You can check it in SM59 if there are any RFC destinations for the above systems.
Alternatively ,check the table RFCDEST if any entries are maintained
Regards,
Lakshman.

RFC destination for Sender System in R/3 4.6c

Hi All,
I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?

Hi Arul,
One more important point u have missed.
Program ID,
When ur configuring sender service from RFC,The most important point is Program ID.
Use some name and create it.Use the same name in SM59.
s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
Reghards
chandra shekar

RFC destination from XI ABAP engine to 4.5 B system

I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
It does not work and gives an error.
<b>Error Details DETAIL: NiIGetSockName</b>
-Naveen.

Hi Naveen,
First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
Plz. confirm...
Regards,
Audy

RFC destination of receiver system

Hi Guys,
I am trying to do the shell creation from scracth, and now i have found on the RFC destination creation there are three RFC connection which needs to be define. But my question is in this step we dont have any receiver system becasue export files has not been generated yet that will come after this step, so how can i proceed.
Regards,
Subhash

Hello Subhash,
In the step 'Define RFC Destinations' you create the RFC destinations for the SAP systems that participate in your project (or subproject).
Yes, you are correct, since the target/receiver system is not yet created, you cannot establish a RFC for the same.
Please proceed by maintaining the following:
Server name, System number , Language, Client, Username and Password for the control and the sender system.
Best Regards,
Mridu.

RFC destination Java = ABAP system to wrong system

Hello everyone,
I have a NW04 Java system (WebAs 640, SP19), which has an RFC destination to an ABAP system.
The strange this is this: we changed the target system of the RFC connection to a different one (let's say from SID1 to SID2), they have different system numbers, different host names and different gateways. Only user and password we kept the same, as that's easier to maintain.
We have a self developed java application which uses this RFC connection.
When we call the application using only the <b>not</b>-fully-qualified hostname the RFC connection to the old (SID1) is used, but the destination is defined with SID2.
However, when we use the fully qualified hostname in the URL, it works with SID2 (which is correct).
Does anyone have an idea why that happens and what we can do to prevent that?
Regards,
Cornelia

Hi Mantosh,
it's an RFC connection entered in Visual Administrator of the Java System (service Destinations), so there's no possibility to set an RFC type like in SM59.
Of course you're right concerning the hostnames, but I was wondering how that could happen. Normally, it should read the data which I configured in the RFC connetion and use that.
We deleted temporary files and cookies and all from the workstation were we started the browser, even rebooted the workstation, but no effect.
Do you know any cache were the java system could have the old data left?
Regards,
Cornelia

Debug RFC destination system

Similar Messages

Maybe you are looking for