Post import RFC connection FINBTR@SIDCLNT100 does not point to local system SID but to empty system

[Sandra_Rossi]

During the import of a transport request containing R3TR TDAT FINB_TR_DERIVATION, there is an error with the below messages in the log, especially the message FINB_TR081 is an error:

Post-import method FINB_TR_AFTER_IMP_METHOD started for FINB_TR_DERIVATION T, date and time: 20250328170804 (PU122)

Post-processing taking place in client 100 (PU186)

RFC connection FINBTR@SIDCLNT100 does not point to local system SID but to (FINB_TR081)

No suitable RFC destination could be found (FINB_TR032)

Errors occurred during post-handling FINB_TR_AFTER_IMP_METHOD for FINB_TR_DERIVATION T (PU133)

Why is there no system indicated after "but to"? How to solve?

[Sandra_Rossi · Accepted solution]

The RFC destination FINBTR@SIDCLNT100 in SM59 is invalid: either it points to an invalid system, or the user is blocked or has an invalid password.

Technical reason: the function module FINB_TR_AFTER_IMP_METHOD (defined as post import function module of object FINB_TR_DERIVATION in transaction SOBJ) is called when R3TR TDAT FINB_TR_DERIVATION is imported, it calls FINB_TR_GET_RFC_DEST, which calls the subroutine DESTINATION_CHECK, which checks that the RFC destination is valid but doesn't check if it fails for which reason it fails and always send the error message FINB_TR081:

    CALL FUNCTION 'RFC_GET_SYSTEM_INFO'
      EXPORTING
        destination  = l_dest_str
      IMPORTING
        rfcsi_export = l_rfcsi.
    IF l_rfcsi-rfcsysid <> sy-sysid.
*     raise an exception because rfc-dest was found but customized wrongly
      MESSAGE e081 WITH i_rfcdest sy-sysid l_rfcsi-rfcsysid RAISING not_found.
*   RFC-Verbindung &1 zeigt nicht auf das lokale System &2
    ENDIF.

I would expect that after the function module call, if L_RFCSI is initial it fails with the error message coming either from the parameter DEST_SYSTEM_MESSAGE (e.g. "Name or password is incorrect (repeat logon)") or from the parameter DEST_COMMUNICATION_MESSAGE (e.g. "RFC destination XXXXXXX does not exist.") 

NB: how to create the RFC destination FINBTR@SIDCLNT100 is explained either in the note 644610:

• c) Preliminary remarks on the RFC connection in the import postprocessing
• An RFC destination is required for the import postprocessing in the target clients of the transport. Create an RFC connection for this using Transaction SM59 of the category '3' (R/3 connection). For security reasons, the user of the RFC connection should be a communication user with sufficient authorizations. The client must be explicitly entered in the destination, the logon language should not be entered. Implement this RFC destination in Transaction FINB_TR_DEST (under FINBASIS 1.0B Transaction SM30 with view FINB_TR_DESTV) and check the effectiveness of the RFC connection.

Or in SPRO (go there directly by using SM30 > View FINB_TR_DESTV > Button "Customizing"). NB: the RFC destination wizard is the transaction code FINB_TR_WZ:

Excerpt from the Wizard documentation in SPRO: "Examples: 1. You want to transport Customizing settings to client 100 of the current system. Start the wizard and enter 100 as the client. 2. You want to make a client copy from client 000. Start the wizard and enter 000 as the client."