RFC Sender Adapter

[Former Member]

Hi,

I want to configure following szenario:

RFC -> XI -> SOAP and back as synchronous

After triggering (SE37) the RFC I always get the Message "JCO.Server could not find server function 'ZMyFunction'". I configured RFC Communication Channel, Sender, Receiver Agreements, Receiver and Interface Determination in XI and TCP/IP Destination with corresponding Program-ID in R/3.

Any hint is welcome?

Thanks in advance

Falk

[Former Member]

hi,

I am trying following scenario

R/3 4.7 -> RFC ADAPTER-> XI -> FILE ADAPTER -> LOCAL SYSTEM

I am getting simillar error while trying to make a RFC call from custom defined function.

Did u get any solution?

Thanks for your help in advance.

sachin kotalwar

[Former Member]

Hi,

I assume you call " call funtion "ZABC" destination DEST

DEST as the SM59 pointing to the RFCXMBS registered program.

Since this is the XI port XI quecks to see if there is a match against the receiver determination, e.g. service from and interface from and check the sender agreement. The sender agreement had the to match the SM59 settings you have done in your R/3 system. Once this is ok the message is received into XI and you would see a message in SXMB_MONI. BTW SYNC calls need to be setup to be shown in SXMB_MONI, e.g. go to SXMB_ADM and go to intergration engine config under option RUNTIME LOGGING_SYNC I believe.

Further use the trace option in SM59 to see if the trace helps. Then there is OSS Note 793434 which explains how to enable the JCO trace using the XI 3.0 RFC Adapter.

I have setup about 20 or so BAPIs and no issue with the RFC Adapter.

I hope this helps. Please let me know.

Stefan

[Former Member]

Thanks stefan!

well I did following steps. As mentioned earlier my scenario is

SAP R/3 (4.7) --> RFC Adapter > XI 3.0 (SPACK 5)> ...

- I have configured RFC Sender adapter in XI system

- I can see registered program name on gateway monitor at R/3 box.

- I have created destination at R/3 box as below and test connection with XI is successful,

1. Call the transaction Display and Maintain RFC Destinations (SM59).

2. Select an existing RFC destination of type R/3 Connections (for example, R/3_Old) by double clicking it.

¡ Choose Destination Copy and copy the RFC destination using a new name (for example, R/3_New).

3. Save the new RFC destination (R/3_New) and delete the old RFC destination (R/3_Old).

4. Create a new RFC destination (for example, RFC_Adapter) of type T (TCP/IP connection) as the RFC destination for the RFC adapter.

5. Select the registration type Registered Server Program and in the field Program ID enter the corresponding program ID from the configuration of the sender RFC adapter.

6. In the Gateway host and Gateway service fields, enter the gateway host and gateway service from the configuration of the sender RFC adapter.

7. If the sender system is a Unicode system, define the RFC destination as Unicode.

8. Using the name of the old R/3 connection (R/3_Old), create a new RFC destination of type L (logical destination with reference entry).

9. In the field Reference Entry enter the RFC destination (RFC_Adapter) for the RFC adapter.

Under the name of the old RFC destination (R/3_Old) – formerly an R/3 Connection, now a Logical Destination – the system calls the new RFC connection (RFC_Adapter) of type TCP/IP Connection for the RFC Adapter.

well when I execute the function at the TCP IP destination above I get following error.

"alternativeServiceIdentifier: party/service from channel configuration are not found..."

I think its trying to search the function on XI box rather than executing on R/3 and posting result to XI box.

Can you guide me??

Thanks for all your help in advance..

sachin kotalwar

[Former Member]

Hi,

what happens if you call the RFC in SE37 under test and enter as destination directly the XI RFC Adapter Port instead of the Logical system.

Can you see in the adapter framework monitor that the RFC adapter is green or has any errors? (http://<server>:<j2eeport>/AdapterFramework/monitor/monitor.jsp).

Did the logging help to shed some light on what payload is sent?

Stefan

[Former Member]

Sachin,

Its very nice you have written the detailed steps for config. But I have a doubt in the following steps.

*****************************************

5. Select the registration type Registered Server Program and in the field Program ID enter the corresponding program ID from the configuration of the sender RFC adapter.

6. In the Gateway host and Gateway service fields, enter the gateway host and gateway service from the configuration of the sender RFC adapter.

*****************************************

You have not specified the actual program ID that is started under the J2EE tool(As a part of Basis setup).

If you have done this then I assume you do it on the XI box and both the Gateway host and Service are pointing to XI box on both Sender Agreement and the SM59 entry on the R3 box.

Also I have one more question, in your actual

"call function ZABC..." what exactly is the ZABC? Where and how will it find this function?

Thanks,

Ramesh Balasubramanian

[Former Member]

hi stefan,

When I try to call RFC in SE37 giving the R/3 OR TCP destination (configured as mentioned earlier) I get error function module could not be found error.

Basically I am trying to place a scheduler at SAP R/3 box which will trigger a custom RFC function. The result of same should be sent to XI. Is it possible to do this?

regards,

sachin.