RFC Connection with and without logon credentials

[Former Member]

Hi,

We have a weird situation at this client. We have an RFC destination(XXXCLNT360) that is used to post payroll documents from HR to an FI instance and the same RFC is used to move Cost Centers from FI to HR.

The problem is on the Payroll documents once posted in the FI box have an option to view back on the original document in the HR box with the help of a BAPI activated on this RFC. The catch here is our client wants to restrict this access to a group of employees only.So at this stage I have to remove the Logon details used to automatically login into HR system using RFC (XXXCLNT360).

Now when I try to move cost centers to HR box, the above solution becomes an issue. I cannot move data automatically here because it will ask for logon credentails.

So, Is there a way I can make both the requirements happen?

I tried working with two RFC's but when I generate partner profiles it is looking at the logical system and is throwing an error.

So, Is there a enhancement on SM59 or else where where I can give the logon details during run time.

Regards,

Vikram

[Former Member]

Hi Vikram,

I guess if you use two RFCs then you can very well implement the above functionality. You need to create the logical system name (BD54) for both the systems(FI and HR) and then create two separate RFCs.

The RFC which logs into HR system can then be restricted with RFC auth groups( by restricting the role assigned to the communication user).

Let me know if you need more information on this. Also let us know if your issue is resolved with this.

Thanks.

[Former Member]

This message was moderated.

[Former Member]

You can either provide a special auth group protection to those accounts and documents posted to them, or make an authority-check before the BAPI is called back on the HR box, or look into a way to use logical system names as variables for destinations (from memory this is a an SSM* table to map the names).

Cheers,

Julius