Hi Pradeep,
In order to analyze the RFC error you should check: Note 128447 - Trusted/trusting systems
the return code is very important to find the root cause. Also check ST22 in GRC Box and in plugin system to get more details:
"No authorization to log on as a trusted system (Trusted RC = #)."
In this case, the trusted return code # (# = 0, 1, 2, 3) has the following relevance:
0 Invalid logon data (user and client) for the trusting
system.
Solution: In the server system (trusting system), create the user
in the relevant client.
1 The calling system is not a trusted system, or the
security key for the system is invalid.
Solution: Recreate the trusted system (see
documentation).
2 In the trusting system, the user has no authorization that contains
the authorization object S_RFCACL, or a logon was carried out using one of the protected users 'DDIC' or 'SAP*'.
Solution: Either provide the user with the relevant
authorization, or use neither of the protected
users 'DDIC' or 'SAP*'.
3 The time stamp of the logon data is invalid.
Solution: Check the system time on the client host and on the
server host and check the validity date of the logon data. The
system times of both systems must be synchronized.
Since you're on SP09, note 1652880 does not apply.
I've added some documentation in order to configure decentralized EAM. If you're interested in this functionality you have to apply SP10.
Cheers,
Diego.