RFC sender adapter not running

[Former Member]

Hi there,

I have following scenario: R3 -(rfc)-> XI -(ftp)-> LEGACY.

In R3, i created a RFC DESTINATION (type T) : with Program_ID & GW options (hostname= R3 hostname & service= sapgwXX where XX means sys number). This RFC currently works!!

In the RFC sender adapter, i used the same program ID and the same hostname and service mentioned above.

If i execute SMGW + GoTo->Logged clients, i can see my program ID there but if i click on it, the register status is WAITING!!!!!

Besides, if i execute the program, no information is transmitted to XI via RFC so i cannot see any error message.

Do i have to do anything else??? Maybe i am missing something...

Could you please help?

best regards,

david

[aashish_sinha]

Hi,

In sender RFC :

Configuration takes place using a RFC adapter communication channel and TCode SM59 (Create rfc connections).

- All systems that send an RFC via RFC Adapter require an RFC connection to the respective RFC Adapter(inbound). Metadata is gathered in the same way. Register the program id of the RFC adapter in SM59. The rfc destination must be of type "T" tcp/ip.

- You cannot send IDocs using this rfc connection. you must send IDocs to the RFC destination of the IDOC Adapter.

Also check out that Program id is case sensitive.

in the functiion check out for the COMMIT WORK at the end of LUW.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Hi all,

RFC destination(typeT) in the R system is still working.

I checked the comm channel monitoring as well and it has green status but no more info (as is it has not processed anything). SMQ1 and SMQ2 are empty, which is good.

I deactivated and activated the sender channel and...nothing.

I refreshed CPACache with no results.

In XI i have NO RFC destination Type T but i do have a RFC dest type 3, using the same user that i configured in RFC sender comm channel.

I am stuck on this.

Please, any other clue?

Best regards,

david

[Former Member]

Hello,

where do you call the RFC in the R system?

The 'Destination' in a program is the (case-sensitive) name of the RFC

and not of the program id.

Regards

Patrick

[Former Member]

Hi Patrick,

In R3, i called the RFC properly (i think) : CALL FUNCTION + RFC name (not program ID)

The RFC fills a table and this one should be retrieved by XI, but XI rfc sender channel does not process any message.

I thought XI would take the info over the RFC as soon as the table was fulfilled...

In addition, i do not know if my program_ID register status (SMGW + GoTo->logged clients) has to be WAITING.

Could you please give some support?

[Former Member]

Hello,

you are right, the status (in smgw) should be 'connected'.

At the moment i don't know what there is to do.

Regards

Patrick

[Former Member]

The <i>state</i> is CONNECTED but the <i>register status</i> is WAITING ...

does anybody know other hint to investigate further?

david

[Former Member]

Hello,

then it was a misunderstanding, register status 'waiting' is alright.

Regards

Patrick

[Former Member]

Hello,

you said already that the RFC-Test is working, that means

the sender adapter is working.

So i guess the problem could only be the program which calls the RFC.

Regards

Patrick

[Former Member]

Hello,

in your program:

Call Function means the function that you have imported to the 'Repository'.

Destination ist the RFC-Destination.

Regards

Patrick

[Former Member]

Hi,

Yes, call function calls a RFC which i previously imported in IRep.

RFC destination is the name of a conection of type .. between systems.

BTW, Thanks

[Former Member]

Hello,

as long you have a sender agreement (and i think so),

i am still the opinion the error must be in the program.

after the

'commit work.'

you can write

IF sy-subrc = 0.

WRITE 'No Errors occured.'.

ENDIF.

and look for the 'No Errors occured' message after running your program.

Regards

Patrick

[nisarkhan_n]

nthing more stps to do for rfc sender config....

try reactivating the adapter...

[Former Member]

Check the status of the RFC adapter in Communication Channel Monitoring.

THanks

Farooq.