Regarding Error handling and customisation in RFC, Idocs and Proxy

[Former Member]

Hi,

I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.

Please let me know in detail if possible.

Regards,

Sampada

[former_member859847 · Accepted solution]

Hi,

If the interface has corresponding standard idoc,

then go for idoc adapter..

if it's required to enhace more...then gof or proxy communication.

if you have any standard RFC's to meet the business requirementthen go for RFC.

in case of proxy, u can implement application log in abap program.

regards

mahesh.

[Former Member]

Hi,

wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.

The amount of customization required will complete depend on the client requirement.

IDOC.

In IDOC we have the standard one according to business requirement if u have to add new fields or in the file to IDOC scenario if u have to validate any data with data base then u have to do some customization in function module or u have to create the new segment to add new fields.

RFC

In RFC also same u have to check the business requirement if u require u have to change the logic in the BAPI.

PROXY

In server or client proxy u have to code it according to business requirement.

the coding will be more compare to IDOC and RFC

Regards,

Phani

[Former Member]

Hi Sampada,

Adding to other replies:

Customization level will depend upon the business requirements. If std IDOc type is available go for this route else we need to extend Idoc adding segments for customized fields which needs customization.

Faster and most robust because monitoring is better. least development required

RFC: used when data volume is high.

ABAP proxies: coding amount is higher compared to others.

hope this helps.

regards-

Ravi

[former_member240483]

I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means

RFC and IDOC

for RFC and IDOC's it depends upon whether using standrad or customized ones.

if you using standard one there is not much customization need to be done but for the customized ones u have to do create and configure everything .

Proxies

You need to generate client proxy and call this one in a trigger program.

Proxy communication is always prefered way but if standard FM or IDOC available try it use those .

For error handling it depends upon the project requirements .

Regards

Rao

[former_member537867]

Hi ,

Check this blog to know when to use which adapter:

/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems

we use proxy in sap 6.0 version or higher.

Basically used for adapter less communication

& very high volume of data has to be transfered.

Step for Configuration fo IDOC in R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (IDX1)

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Load Meta Data for IDOC (IDX2)

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (We21)

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Create Partner Profile (WE20)

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

In SLD – System Landscape Directory

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

In Transaction SALE

Define and Assign the logical system name.

Regards,

Vinod.

[Former Member]

Check this to get some idea...

/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems