Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

RFC Connection Help Needed

Go to solution
Former Member

‎2009 Jan 30 4:36 PM

0 Likes
746

Dear friends,

I would like to have your opinion on an issue. We have separated HR from main R/3 client and defined an RFC user to communicate between these two systems in order to transfer data. When a change or revision has been made by a user, letu2019s say user MELIH, in the HR client, data is send from HR to R/3. But at the R/3 side, user name who changed the document seems to be as a generic RFC user, letu2019s say ALEREMOTE. Is there any way to get from changed document of R/3 such as whoever has made and send the data from HR to R/3 rather than seeing ALEREMOTE.

Best regards,

Melih

1 ACCEPTED SOLUTION
Read only

Go to solution
Former Member

‎2009 Jan 30 5:27 PM

0 Likes
686

One way of doing this is to use Trusted RFC, ensure that the HR user also exists with the same UID name in the ERP system, and grant the target user authority for object S_RFCACL (see the documentation in transaction SU21) with the same user check activated.

In your RFC connection, you can then simply make the connection user context sy-uname and close the connection after the data transfer is completed (see the documentation on FM RFC_CLOSE_CONNECTION).

But you need to be carefull with this one... as a little mistake can be a big problem: See [SAP Note|https://service.sap.com/sap/support/notes/128447].

Cheers,

Julius

One way of doing this is to use Trusted RFC, ensure that the HR user also exists with the same UID name in the ERP system, and grant the target user authority for object S_RFCACL (see the documentation in transaction SU21) with the same user check activated.

In your RFC connection, you can then simply make the connection user context sy-uname and close the connection after the data transfer is completed (see the documentation on FM RFC_CLOSE_CONNECTION).

But you need to be carefull with this one... as a little mistake can be a big problem: See [SAP Note|https://service.sap.com/sap/support/notes/128447].

Cheers,

Julius

Reply
3 REPLIES 3
Read only

Go to solution
Former Member

‎2009 Jan 30 4:39 PM

0 Likes
686

If you are using change pointer technique in ALE to communicate the changes done in HR to SAP R/3, then you might want to have a look at the change pointer structures CDHDR and CDPOS.

CDHDR definitely has the user and time of change from the source system.


Structure of CDHDR

Edited by: Julius Bussche on Jan 30, 2009 6:08 PM

Removed long text in code tags because it messed up the formatting

Read only

Go to solution
valter_oliveira
Active Contributor

‎2009 Jan 30 4:43 PM

0 Likes
686

I'm not sure if you can change that.

One idea (not good to me) could be to create one RFC user for each HR user. Another would be passing the HR user in some RFC call atribute, and then, in R3 system, in some user-exit, changing the user in runtime.

Regards,

Valter Oliveira.

Read only

Go to solution
Former Member

‎2009 Jan 30 5:27 PM

0 Likes
687

One way of doing this is to use Trusted RFC, ensure that the HR user also exists with the same UID name in the ERP system, and grant the target user authority for object S_RFCACL (see the documentation in transaction SU21) with the same user check activated.

In your RFC connection, you can then simply make the connection user context sy-uname and close the connection after the data transfer is completed (see the documentation on FM RFC_CLOSE_CONNECTION).

But you need to be carefull with this one... as a little mistake can be a big problem: See [SAP Note|https://service.sap.com/sap/support/notes/128447].

Cheers,

Julius