RFC-RFC

[Former Member]

Hi Experts,

I have a scenario RFC-RFC ,in ECC while checking in sm59 ,getting the error as

Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT', communication r,

I have done the gateway refresh in ECC and full cache refresh in SAP ECC and PI as well,still the same error exist.

Please find the attachment for further error details.

The RFC connection we have TCP/IP connectiong type T.

Please suggest.

Regards,

Kalpana.

[Former Member]

Hello All,

Thanks for your reply.The issue is resolved by creating the new RFC destination.

Regards,

Kalpana

[former_member182412]

Hi Kalpana,

Check question 20 in below SAP Note.

730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter

20: It is not possible to send RFC calls to the RFC Adapter sender channel and the RFC Adapter is not registered at the SAP Gateway. RFC Adapter receiver channels report a error like "RFC Adapter: receiver channel not in list of running clientPools..." in the Message Audit Log of the Adapter Engine. What happened? A: The RFC Adapter checks the configuration of each channel during the
start of this channel. This is done during startup of the whole RFC Adapter (J2EE service) or when the RFC Adapter receives a new (or
changed) channel from the Integration Directory. Mainly the RFC client parameter are checked with a connect/disconnect to the remote system. In receiver channels this is done for the client parameter and the metadata repository parameter, in sender channels only for the metadata repository parameter. If this check fails the channel is marked as failed and will not be used for sending or receiving of RFC calles within RFC Adapter. The test is done again each time when the channel is updated in the Integration Directory or after a restart of the RFC Adapter. The status of each channel in the RFC Adapter can be monitored in the Adapter Monitor. Note 769791 describes this in detail.

There may be situations where the check of the connection will fail due to a temporary error (like network, ...). The channel will not be
usable despite the temporary error may disappeared when the first message should be delivered through this channel. If this is common in the environment where the RFC Adapter is used, the check can be disabled for the whole RFC Adapter. Set the RFC Adapter J2EE service property 'initialRfcClientConnectCheck' from 'true' to 'false'. The changing of J2EE properties is discussed in Q 17. This parameter was introduced in XI 3.0 SP9.

Set the RFC Adapter J2EE service property 'initialRfcClientConnectCheck' from 'true' to 'false' according SAP Note Then even temporary connection problem to ECC system the channel will not be in error status.

Regards,

Praveen.

[vicky20691]

Hi Kalpana,

Check in SMGW-> goto-> logged on clients . can you see your program id over there as Registered program id.

If you can see it there just give program id in SM59 and keep gateway host and service blank and try

If you can't see your program id in SMGW then it is not registered yet.

Regards,

Vikas

[markangelo_dihiansan]

Hi Kalpana,

After configuring the RFC as suggested and it still does not work, ask your basis to upgrade the reginfo to allow the TP to be registered.

Regards,

Mark

[iaki_vila]

Hi Kalpana,

Set the program ID in your sender RFC channel and activate before to do the test in the sm59 transaction.

Regards.

[manoj_khavatkopp]

+ Make sure you have entered correct gateway host and port in the RFC destination.

[former_member186851]

Hello Kalpana,

I guess your program ID is not registered.

Refer the below link

program not registered - ABAP Connectivity - SCN Wiki