RFC to File Help needed ?

[Former Member]

Hi friends ,

My scenario is RFC to File . I have followed the folowing blogs

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

I have created Communication channel in XIDEV with program id , which is pointing to R3 Development server

<b> In R3 Dev</b> using sm59 transaction i have created the RFC Destination using TCP/IP connection with program ID ref to Michals blog.

Tested the Connection ok .

My Question is

<b>1. Do i need to do anything on XIDEV server ? like SM59 ?</b> OR shall i proceed further ?

<b> 2. If i moved to production then again i have to create RFC Destination in R3 Production server with SM 59 ?</b>

Please explain in detail

Regards.,

Shyam

[Former Member · Accepted solution]

1. Do i need to do anything on XIDEV server ? like SM59 ?

No. but in ur RFC Sender communication channel u have to give correct connection parameters of R3 system

2. If i moved to production then again i have to create RFC Destination in R3 Production server with SM 59 ?

Yes configuration is required. For Integration u can maintain Transport targets to avoid recreation of communication channels in XI Prod.

Regards

Rajeev

[Former Member · Accepted solution]

Hi rajeev ,

Thanks for ur reply. Then i don't need to create port and and all right ?Like we21 Like that ?

Please explain in steps

Regards.,

Shyam

[Former Member · Accepted solution]

Hi,

Port n partner profile <b>not required</b>. Juz rfc destinations.

<b>Cheers,

*RAJ*</b>

[Shabarish_Nair · Accepted solution]

<i>Then i don't need to create port and and all right ?Like we21 Like that ?</i>

>>

of course not. It is req. only while doing a IDOC scenario

ref: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

Else all you need to do in a RFC scenario is to maintain the destination in SM59, configure your RFC adapter as mentioned in Mike's blog once you have imported the RFC into IR.

For troubleshooting ref: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

[prateek]

1. No. no other config required on XIDEV. I hope u have imported the RFC. U may proceed further.

2. Yes. U have to recreate it

Regards,

Prateek

[Former Member]

Hi Prateek ,

Do we need the Following steps as krishnan specified for RFC to file

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.

Regards.,

Shyam

[Former Member]

hi

you r doin r3 to xi

follow these steps

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.

cheers

kish

<b>reward points if useful</b>