Declare rfc destination to receive idoc

i am trying an example to declare rfc destination to receive idoc. the directions say to create a new destination of type "L" with the name INTERNAL and desination NONE. When i try to create a new rfc desination with destination NONE is says there is already one there but it is of type "I". It will not let me change this to type "L" and I cannot delete it.
Any idea how to do this???
Also when I create it says give a name of INTERNAL but i see no field which says "name".

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

Similar Messages

RFC Destination type for IDOC to FILE

Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeff

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

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 not getting connected - IDoc to XI scenario

Hi Everybody,
I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
Please give me step by step solutions.... Thanks in Advance...
Regards/Guru

Requirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
please refer to michel book on IDCO usage in XI
Message was edited by:
Sreeram Reddy

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.

Defining a port /RFC Destination on XI for IDOC to File scenario

When defining a port on XI, what is the client number I am supposed to use to receive the IDOC from R3 to XI. I am assuming that I am supposed to use R3 client number to define the port in XI. Is this correct ?
Please explain this !!!
Also I am assuming the same procedure to define a RFC destination in XI. I am using the IP address of R3 client to define the RFC destination in XI to point to R3. Is this correct ?

hi satya
u may refer to the doc attached for more insight on the ports
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>

RFC Destination type RFC Receiver Adapter?

Hi,
What is the RFC destination type for Sender RFC Adapter?
and what is the need a Program ID for sender Adpter.
What is the RFC destination type for Receiver RFC Adapter?
Regards
Gopi

When we use the RFC Adapter?
SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter).
You require the sender adapter if you want to use the Integration Engine to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine to arrive in RFC format. In this case, the Integration Engine must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
The following three scenarios are possible when using the RFC adapter and the Integration Engine:
    1) SAP R/3 to SAP NetWeaver Application Server
    2) SAP NetWeaver Application Server to SAP R/3
    3) SAP R/3 to SAP R/3
When we use ABAP Proxy ?
SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.
To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.
Please Reward the points if it's helpful...
Regards,
Ramana.

RFC Receiver Adapter and RFC Destination -- Help

Hi,
I would like to configure the RFC Receiver Adapter for the invokation of a RFC on SAP System (Name: ALPHA) using a RFC destination provided by another system named BETA.
I have set External Server as server type.
My first question is: I have to quote an application server gateway and a gateway service. Is this information related to a service on ALPHA or BETA?
My second question is:
It is also necessary to provide a Programm-ID. The destination on BETA is a R/3 connection and doesn't have a programm id. Where do I get this from?
And my last question is:
Is at all possible to use the RFC destination on BETA?
Any help is really appreciated...
Kind regards,
Heiko

Hi Heiko,
I don't fully understand your need but:)
since both of your systems are SAP systems
why are you trying to use external server?
can't you just call RFC on BETA
and inside this RFC on beta call RFC on ALPHA?
in a sync or async way?
can you tell a little more about your requirement ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

File to IDOC Scenario - Doubt in RFC Destination

Hi all,
I m working on a File - IDOC Scenario. I got a IDX1 error Also when I try to import IDOC in IDX2, I got I:000 error message(No more information was given) . When I checked the RFC destination, Test Connection works fine. But Remote Logon didnt work, since the target system is not a Trusted System
Is it necessary to make the Target System, a Trusted System ? (For enabling Remote Logon)

Hi ,
There might be some problem with the R3 user that u r using...
For some versions of R3 it is required that the password be in CAPS for making an RFC connection...
I knw this sounds weird but even i had this problem....
Also chk if the XI user has RFC priviliges..
reward points if helpful
PrashANt

RFC Destination is required for R/3 receiver system

Hi All,
Is RFC destination required for R/3 receiver system? Scenario i,e File >XI> RFC
How XI system communicate with R/3 receiver system?
Regards,
Sameer

Hi,
RFC dest is not required in this case, XI will communicate thru RFC channel which you will configure as receiver channel. Hence in this channel, you will mention the required parameters.
Please search this fourm and you will get plenty for blogs with step - to -step details of configuring the FILE 2 RFC scenario.
Regards
Sai Ganesh

Does SAP HANA supports JCo to call BAPI RFC's and to receive IDocs?

Hi,
We are using a WSO2 ESB to integrate our SAP 4.7 version system with SalesForce.com and as part of this integration we use JCo libraries to receive IDoc's and to execute RFC's from ESB.
This year we are planning to migrate our SAP environment to SAP HANA and wondering if SAP HANA supports the JCo libraries? or is there any changes in the implementation how we use JCo libraries?
Thanks in advance.
Regards,
Venkat

BAPI_TRANSACTION_COMMIT doesn't have two import parameter, please check

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

Config idoc adapter - RFC destination?

while configuring the idoc adpater ( in FILe to idoc scenario)do i need to write the
rfc destination of r/3 system of netweaver xi systems
2. do we need to create the same port in we21 and idx1
3. is it necessary to give the gateway host and service in r/3 and xi
even if not used when made thru test connection it was successfully connected

> while configuring the idoc adpater ( in FILe to idoc
> scenario)do i need to write the
> rfc destination of r/3 system of netweaver xi systems
>
Create RFC destination in XI on SM59 . This should point to the SAP system. Use this in the Idoc adapter
>
> 2. do we need to create the same port in we21 and
> idx1
>
Create a port in IDx1 in XI.
We21 is used to create a port in SAP systems. For file to Idoc, no need of a port in We21.
> 3. is it necessary to give the gateway host and
> service in r/3 and xi
No need for Gateway host and service if there is a direct connection between XI and the SAP system.
Regards
Bhavesh

Can not receive IDocs

Hi together,
I have configured an IDoc listener in xMII 12. The listener is started. According to the connection test in transaction SM59 the connection to the listener is fine.
Distribution model and so on are all created.
Now I try to send me the IDocs I want by using transaction CI42N which is used to send production orders.
Looking to transaction WE05 the IDocs are in the list with status "IDoc sent to SAP system or external program".
But in xMII there is no IDoc received. Either with or without message rules.
There also is no entry in the table XMII_JCOMESSAGES.
I checked the default trace and warnings of the xMII (Netweaver) Server. But there is no entry within the time range when IDocs were sent and also before or after is no entry that has to do something with IDocs or message listeners.
The xMII Version used is 12.0.2 Build(88).
Anyone has an idea what goes wrong there?
Regards
Timo

Hi Timo
I am not sure if you already got the answer to the problem u mentioned.
There can be various reasons for IDocs not received in XMII. So I will list the most obvious ones that I think might happen. Just take some time to check through this list one by one.
1. Go to SM59 and do a connection test on ur RFC Destination. If it is successful then go to Menu option "Extras" -> "Target System". Do this a couple of times and see if on al the tries it points to the correct XMII System. It is possible that u have used the same Program Id for 2 connections and RFC gateway is working as a Loadbalancing server.
2. If 1 is correct the go to trx BD64 and do a Model View Distribute of ur configuration. In XMII u should get a RFC message of type "Model_View_Distribute". If this is there then your configuration is correct.
3. send the idocs from ur trx and check in trx sm58 for the status. If it fails there then they never reached XMII. Check the error message here.
4. If all 3 are correct check if you have a processing rule which might be deleting the messages or a clean up rule which is cleaning them.
Best of luck.
Hope this helps.
Partha

RFC Destination Query

Hi Experts,
I have a query on RFC destination.
We create RFC destination for connecting between ABAP system and XI system.
Say for example we create ABAPRFC and XIRFC. Now if for some reason say ABAPRFC stops working then will IDOC/Proxy be sent to XI system as XIRFC is working. Also if XIRFC stops working and ABAPRFC is working then can we send IDOC/Proxy to ECC system. Or we need both of them to work for sending data to either of the systems.
Regards,
Shaibayan

Hi Shaibayan,
Let me explain thru simple example:
For example:
1) We have RFC connection "ABAPRFC" in XI system which is using ECC Target host and ECC system credentials to create connection from XI to ECC, therefore if XI has to send IDoc to ECC it will use "ABAPRFC" connection to connect with ECC system. If "ABAPRFC" connection stops working then XI cannot send IDoc to ECC and IDoc will fail in XI itself.
But if your RFC connection from ECC to XI is working then XI will continue to receive the IDoc from ECC.
2) We have RFC connection " XIRFC" created in ECC system which is using XI target host and XI system credentials to connect with XI system from ECC, therefore if ECC has to send IDoc to XI it will use XIRFC connection. If XIRFC connection stops working then ECC will not be able to send the IDoc to XI and IDoc will fail in ECC itself.
But if your RFC connection from XI to ECC is working then ECC will continue to receive the IDoc from XI.
So conclusion here is that you have two seperate RFC connections, one which is created in ECC to send the IDoc to XI and another is created in XI to send the IDoc to ECC.
Hope it is clear now.
Let us know if there is any confusion.
Regards,
Akshay

Declare rfc destination to receive idoc

Similar Messages

Maybe you are looking for