cancel
Showing results for 
Search instead for 
Did you mean: 

RFC/PROXY/IDOC

Former Member
0 Kudos

What are prerequisites has to be done before going to RFC/PROXY/IDOC

Thanks

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

diff RFC/PROXY/IDOC

thanks

Former Member
0 Kudos

hi parvath,

RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

RFCs manage the communication process, parameter transfer and error handling.

Have a look at this links.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

proxy 's in xi are used for direct communication with xi using XML, here no xml conversion is done....so it is known as adapterless communication

IDOC 's are message structures & known as intermediate documents for data transfer across the R/3 systems in a distrubuted environment

pls do chk this link it is very usefull

http://www.informatik.fh-wiesbaden.de/~werntges/lv/edi/specs_EN/SAPdoc/IDoc_d.htm

reward points if helpfull

regards

kummari

Former Member
0 Kudos

Hi,

If you have the solution for the earlier post please close that thread and open a new thread.

Regards,

Nithiyanandam

Edited by: Nithiyanandam A.U. on Jul 11, 2008 6:16 AM

Former Member
0 Kudos

Hi Parvatha,

Inorder to communicate with SAP R/3 system you have three options. ABAP PROXY/RFC/IDOC.

If your WAS>6.20 then u can go for Proxies.

RFC means REMOTE FUNCTION CALL, if any previously built function is supporting your requirement then u can go for RFC adapter. That also depends on your client interest.

Some clients may be interested going for proxies,because if u use proxies performance will be increated ,because R/3 system directly speaks with XI,no need of any adapter,no need any conversion.

IDOC (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. If any IDOC is existing for your requireemnt then u can go with IDOC adapter.

Hope this gives u some idea on PROXY/RFC/IDOC.

Former Member
0 Kudos

Hi,

Refer these details for RFC, IDOCs and BAPI:

ABAP Proxy:

http://www.saptechnical.com/Tutorials/XI/ABAPProxy/page1.htm

Idoc and RFC:

Configuration in R/3:(RFC)

One Business System representing the sending R/3 is required to be configured of type 3rd party in SLD (System Landscape Directory).

Create RFC Destination (RFC)

Use TCode SM59 to create RFC Destination in R3X to connect to XI system

Maintain Ports

Use TCode WE21 to create a tRFC Port. The RFC Destination created in the previous step should be assigned to this port.

Maintain Partner Profile

Create a Partner Profile for the Receiver System using the T-Code WE20, with the Inbuond/outbound parameters.

Create Distribution Model (BD64) :Create model view and add Message type

Configurations in the Integration Server(XI):

Create RFC Destination (RFC)

Use TCode SM59 to create an RFC Destination of Type 3 in order to establish communication with the Sender SAP system

Create Port

On the Integration Server, create a port for IDoc communication using transaction IDX1.

Ideally, the port name should be of the format SAPxxx, where xxx is the system id of the SAP system. The created port has to be bind with the RFC Destination of the Sender SAP system configured

Transaction IDX2

This configuration step is used to import the metadata of the IDoc using the corresponding Business systemu2019s port

Regards,

Nithiyanandam

Former Member
0 Kudos

Hey,

Prerequisites for Idoc.

Steps for ALE settings:-

Steps for XI

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the R3 system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto IDX1.

Create a new port.

Give the port name.

Give the client number for the R3 system.

Select the created Rfc Destination.

Step 3)

Goto IDX2

Create a new Meta data.

Give the Idoc type.

Select the created port.

Steps for R3.

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the XI system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto WE21.

Create a port under transactional RFC.(R3->XI)

Designate the RFC destination created in prev step.

Step 3)

Goto SALE.

Basic settings->Logical Systems->Define logical system.

Create two logical systems(one for XI and the other for R3)

Basic settings->Logical Systems->Assign logical system.

Assign the R3 logical system to respective client.

Step 4)

Goto WE20.

Partner type LS.

Create two partner profile(one for XI the other for R3).

Give the outbound or inbound message type based on the direction.

Step 5)

Goto WE19

Give the basic type and execute.

fill in the required fields.

Goto IDOC->edit control records.

Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

Click outbound processing.

Step 6)

Go to SM58

if there are any messages then there is some error in execution.

Goto WE02.

Check the status of the IDOC.

Goto WE47.

TO decode the status code.

Step 7)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

SAP r3

sm59(status check)(no message)

WE02(status check)

WE05(status check)

BD87(status check)

WE42 process code

WE47 status info.

Prerequisites for PRoxy.

First you need do certain settings on R3.

refer to this link for proxy settings on R3.

then you can configure your Proxy in SPROXY.

refer to this link for Proxy configuration.

ABAP Proxy

Enhanced ABAP proxy

Prerequisites for RFC.

You need to create RFC destination in SM59.

reward points if useful.

regards,

Milan

Former Member
0 Kudos

HI,

RFC -- > For using the RFC you need to setup the RFC destination in SM59

PROXY --> For ABAP PRoxy you need to configure it as mentioned in below link

For IDOC ---> You need to setup logical system and Partner Profile (ALE setup) as below

E-mail this message Reply

Please check this link for ALE setup for inbound and outbound processes.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

Thanks

Swarup

Former Member
0 Kudos

Hi parvath

In simple terms, Proxy talks with XI in XI native formats. Therefore, the time required in conversion of messages from one format to another is saved. Thatu2019s why proxies are faster in execution than other adapters wherein the conversion of message from one format to other takes place.

Applications based on SAP WEB AS version 6.20 or higher can communicate with the XI using proxies

Also, better monitoring features for ABAP proxies(you can monitor message from the R/3 system - sxmb_moni)

1)The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.

2) Proxies communicate with the XI server by means of native SOAP calls over HTTP.

Regards

Abhishek Mahajan

**Reward points if helpful*

3) RFC does not, so you have to convert from SOAP to RFC calls and vice versa.

4) ABAP proxies support two different protocols; XI and Web Services

5) Most important is that they can be used for both synchronous and asynchronous communication.

6) RFC/BAPI is basically only intended for Synchronous comm. which asks much more system resources from your XI system.

7) Proxies are used when you have large chunks of data coming in and that too if itu2019s unstructured, so if it comes from a SAP system we go for an ABAP proxy, if itu2019s from a non sap system, we take a java proxy.

😎 For ABAP proxy we may use a report to send a proxy data to Sap XI.

9) EOIO quality of service can be obtained with Proxies and not with RFC/BAPI.RFC/BAPI support BE (Best Effort) when used synchronously.