Generated internal RFC connection does not work after AS/CS-split - error in SM58

[guenteraigner]

Hello together,

since we have performed the AS/CS split in our ERP System E10 we face problems with some transactions (IW31, IW31) regarding the transactional RFCs to the internal system.

When I look into SM58 I see the entrys with the error: "Error when opening an RFC connection".

The function module is "SHARED_BUFFER_DELETE" and the target system is "ie10cs10_E10_10" which indicates that the target system is the central instance.

But of course the transaction itself is started on the dialogue instance (ie10di31).

When I doubleclick on the target system column in SM58 I come to the internal RFC which is automatically generated.

Trying a connection test shows the following error:

ERROR: Gateway not connected to local R/3

LOCATION: SAP-Gateway on host ie10cs10...... / 3310

COMPONENT: SAP-Gateway

MODULE: gwxxrd.c

RETURN CODE: 726

When I check the internal RFCs in SM59 I can only find another RFC Destination with the name "ie10di31_E10_31" - so this would be the dialogue instance.

I do not understand how the internal RFCs are created automatically and why I see the central instance in the SM58 as target system but only the dialogue instance RFC is visible in SM58 under type "I" connections.

I hope I could explain the issue......your help would be really appreciated.

Thanks a lot in advance and regards

Günter

[isaias_freitas]

Hello Günter,

Whenever an ABAP isntance starts, it creates an internal destination.

Use the transaction SE16 do see the contents of the table RFCDES.

You can filter for the type of destination (internal).

If you see incorrect / old entries (for internal destinations!) there, you should delete them.

Best regards,

Isaías

[guenteraigner]

Hello Isaias,

RFCDES has already been cleaned up so there are no old/inactive entries existing.

In addition to the standard entries BACK, NONE, NONE_NU meanwhile I have only the following entry in RFCDES:

RFCDEST               RFCTYPE          RFCOPTIONS

ie10di31_E10_31     I                         H=ie10di31,S=31,d=1

But the TRFC entries I see in SM58 contain the target system ie10cs10_E10_10 and this is exactly the point that I do not understand.

Where does this SM58 target system - which is the central instance - come from????

The internal RFC is only created (automatically) for the dialogue instance.

On another system where the same business transaction works fine I can see entries for the central instance and all the dialogue instances in RFCDEST but as these are automatically created and cannot be generated by myself in SM59 I cannot step forward at this point.

When you say the internal destinations are created automatically whenever an instances is started.....which target system is used for this automatically created destination.

Actually I am even not sure whether it is a technical/basic issue because the internal RFC is created wrong - or a business issue because the transaction uses somehow the central instance for the TRFC call instead of the dialogue instance (where an internal RFC would exist).

Many thanks for your reply If you have any idea

Best regards

Günter

[isaias_freitas]

Hello Günter,

These internal destinations point to the instance itself (e.g., when the instance ie10di31_E10_31 starts, it creates the internal destination pointing to itself).

The issue could be related to the functional/application/business area instead of basis, since it is the application that creates the SM58 entries as it needs (including which destination to be used).

Was the original CI (before the ASCS split) named "ie10cs10_E10_10"?

After the split, the CI should remain with the same name, but without the Message Server process or a work process of type enqueue. You would also have a new instance (ASCSxx), where the Message Server and the Standalone Enqueue processes will be running.

Best regards,

Isaías

[guenteraigner]

Hello Isaias,

thanks - great to know now that the instance always creates the internal destination pointing to ITSELF!

I tought that this maybe can be influenced by any (wrong) parameter that causes the internal RFC to be created to the wrong instance.

The original CI before the split was named "ie10ci10_E10_10" - so only the "ci" was changed to "cs" which is the new CI now - and of course the additional DIs exist.

So I am quite sure now that the problem is located somewhere in the application as it is the one which creates the SM58 entries containing the wrong destination.

Hope this is the case and will update the result her.

Best regards

Günter

[former_member215961]

Hi Güter,

I've never done a ASC/SC split, but maybe the instance number of the gateway change to the default 3300?

Trying a connection test shows the following error:

ERROR: Gateway not connected to local R/3

LOCATION: SAP-Gateway on host ie10cs10...... / 3310

COMPONENT: SAP-Gateway

MODULE: gwxxrd.c

RETURN CODE: 726

change the instance of your gateway to:

sapgw00

or

3300

Cheers

[Former Member]

Hi Gunter,

Make sure you have entries for dialog, central instance and ascs instance details in services files on each host.

Also you are able to telnet between these host.

Regards

Prithviraj