RFC destination and FM

Hi all
I need to call a FM by RFC.
It is possible to specify calling the FM the RFC destination logon parameters?
Bye
enzo

Hi,
You can call using only destination.
CALL FUNCTION 'RFC_READ_TABLE'
        DESTINATION IV_RFCDEST
    EXPORTING
      QUERY_TABLE           = IV_TABNAME
      ROWCOUNT              = IV_ROWCOUNT
    TABLES
      OPTIONS               = IT_OPTION
      FIELDS                = CT_FIELD_GENERIC
      DATA                  = CT_DATA
    EXCEPTIONS
      TABLE_NOT_AVAILABLE   = 1
      TABLE_WITHOUT_DATA    = 2
      OPTION_NOT_VALID      = 3
      FIELD_NOT_VALID       = 4
      NOT_AUTHORIZED        = 5
      DATA_BUFFER_EXCEEDED = 6
      SYSTEM_FAILURE        = 7
      MESSAGE
      CV_MESSAGE
      COMMUNICATION_FAILURE = 8
      MESSAGE
      CV_MESSAGE
      OTHERS                = 9.
regards
vijay

Similar Messages

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!!

RFC destination and logigal destination.`

If I am transfering the data uisng ALE,
is RFC destination and logical system name of receiveing system should be same ??????
If the names of the both are different what will be the effect plz tell me ????

HI Prahlad,
Logical system is nothing but participating system in the ALE scenario.
By Using RFC call we can connect to Other system .
In SM59(Def RFC ) we mention Logical sytstem name.
So both should be same .
1. Creating Logical Systems
o     Login using 800 client
o     Go to T. Code SALE
o     Expand Sending and Receiving Systems
o     Expand Logical Systems
o     Click on Define Logical System
o     Click on New Entries
o     Create STUD_S, STUD_R Logical Systems
o     Save and come back
o     Assign the STUD_S Logical System to client 800
o     Assign the STUD_R Logical System to client 810
2. Creating the RFCs
o     Go to T. Code SM59
o     Expand R/3 Connections
o     Enter RFC Name as STUD_S
o     Connection Type as 3
o     Language as EN
o     Client as 800
o     User as SAPUSER
o     PWD as abap
o     Target host as sap
o     Click on Remote logon button to test the RFC
o     Enter RFC Name as STUD_R
o     Connection Type as 3
o     Language as EN
o     Client as 800
o     User as SATISH
o     PWD as abap
o     Target host as sap
o     Click on Remote logon button to test the RFC
<REMOVED BY MODERATOR>
Thanks
Jagadeesh.G
Edited by: Jagadeshwar Gollapelly on Apr 22, 2008 3:44 PM
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 1:15 PM

RFC Destination and Logical System

Hi Friends,
Can anybody tell me how the RFC Destination and Logical System are related to each other?

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.
Thanks.

Why do we need to define RFC destination and user for material replication

Dear Experts,
why do we need to define RFC destination and user for material replication? Here we use crm middleware only for material replication. Could you please help me to understand it?
regards,
Ranjan

Hello,
As far as I know, you can use the same RFC destination already available in ECC to SRM to replicate materials.
You can refer to note 720819.
Regards,
Ricardo

Check RFC destination and Valid User

HI all!
I'm trying to verify the RFC destination in SM59 transaction. I have 2 trusted connection to other sap system with an associated account. My goal is to verify that there isn't problem regarding the account and the connection, the best it's something that try to made a remote logon and give an exception in case of:
- account isn't working
- account is working but there's no connection (think about a network problem)
Which function i could try to use to accomplish this goal ?? any idea or just made report?
I have only make a function using a BDL_SERVER_PING but isn't enough.
Help are Very apreciated
thanks!

Hi,
Use fm RFC_GET_SYSTEM_INFO
a®

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
     RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
          CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
          No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*"      PED_ORDEN STRUCTURE ZSD_RFC_T04
*"      RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
               tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
          FROM zsd_ped_orden
          WHERE estatus EQ space.
LOOP AT tb_ped_orden.
    MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
    APPEND ped_orden.
    tb_ped_orden-estatus = 'X'.
    tb_ped_orden-fecha_actualiz = sy-datum.
    tb_ped_orden-hora_actualiz = sy-uzeit.
    MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
          FROM zsd_rfc_r01
          WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
    MOVE-CORRESPONDING tb_rfc_orden_error TO return.
    APPEND return.
    tb_rfc_orden_error-estatus = 'X'.
    tb_rfc_orden_error-fecha_actualiz = sy-datum.
    tb_rfc_orden_error-hora_actualiz = sy-uzeit.
    MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
      return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
     TABLES
          ped_orden             = ped_orden
          return                = return
EXCEPTIONS
    communication_failure = 1
    system_failure        = 2
    OTHERS                = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

Purpose of RFC and JCO-RFC destinations

Hi,
Can you please tell me what is the purpose of RFC and JCO-RFC destinations and where do we create them.
Regards
Rahul

Hi,
RFCs are SAP interfaces for communicating between SAP systems. They accept inputs, do the processing and return the output values. You can call rfcs through different applications like web dynpro.
http://help.sap.com/SAPhelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
JCO helps Java applications to connect and communicate with SAP backend systems. Using JCO we can make rfc calls. JCO will help in getting the rfcs in a java compatible format.
http://help.sap.com/saphelp_nw04/Helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm
Example for setting up jco destinations:
http://help.sap.com/saphelp_erp60/helpdata/EN/ca/115e4088dc0272e10000000a155106/content.htm
Regards,
Shyam.

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

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

Doubt about RFC Destination in FILE to IDOC Async scenario

hi
In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
Any specific reason.
Thanks in advance.

First you need to have a clear understading of how the idoc adapters works.
In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
Hope this answers your ques.
cheers
*Raj*
*POINTS IF SATISFIED WITH ANSWER.

Best practice for creating RFC destination entries for 3rd parties(Biztalk)

Hi,
We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP.
We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
We also wanted to know if there are any best practices to optimise on number of RFC destinations.
Here were a few suggestions we had in mind to tackle the same.
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
I would appreciate if you can suggest the best architecture or practice to achieve RFC destinations in an optimized manner.
Thanks in advance
Sam

Not easy to give a perfect answer
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
-> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
-> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
-> consider this option 2.
We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

Check RFC Destination without access to SM59

Hi,
Typically SM59 is reserved for BASIS teams in our organization.
Assuming there is no access( even read only) for SM59, is there a way (another tool) to test a RFC destination and check whether its functioning correctly ?
Regards,
Jon

Or with SE37 test RFC_PING and input the target RFC destination (and of course not NONE as in my screen)
Regards,
Raymond

RFC destinations in WebDynpro

Why does there really need to be a model RFC destination and a metadata destination in webdynpro?
Honestly is there really any advantage of having these pointing to either two different places?
Or having two different means of loging on?

I know what its used for, but honestly in most cases in development the metadata id is someone who has developer access so can access the bapi's etc (ie in SE37) and a lot oc client independant stuff like DDIC. In a production box the model data is mapped to the users who has to have security access to the client in question, but then doesn't that users have to have access so the metadata RFC still work?

RFC destination and FM

Similar Messages

Maybe you are looking for