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

Deciding RFC destination dynamically

Former Member

‎2008 Apr 24 4:39 PM

0 Likes
1,002

Hello All,

I need to call a RFC which is there in R3 system from SRM system . While calling RFC I want to decide the RFC destination name dynamically i.e. depending upon the development , quality and production environment.

Is there any way to decide the RFC destination name dynamically depending upon the source and target system's logical system name or with some other way.

Thanks and regards,

Keith

Hello All,

I need to call a RFC which is there in R3 system from SRM system . While calling RFC I want to decide the RFC destination name dynamically i.e. depending upon the development , quality and production environment.

Is there any way to decide the RFC destination name dynamically depending upon the source and target system's logical system name or with some other way.

Thanks and regards,

Keith

Reply
3 REPLIES 3
Read only

Former Member

‎2008 Apr 24 4:45 PM

0 Likes
521

hi ,

go to sm58 here we can check the messsage...if the message is present then that will be an error..if no error is present then it is a success in the idoc..

regards,

venkat

Read only

Former Member

‎2008 Apr 24 5:32 PM

0 Likes
521

Look at function

RFC_READ_R3_DESTINATION

Doug

Read only

Sm1tje
Active Contributor

‎2008 Apr 24 9:53 PM

0 Likes
521

This solely depends on the naming conventions you are using. Since the name of the RFC destination is arbitrary, there is 'no' way of determining the name of the destination.

To be flexible to some extend, I 'always' create a customizing table (which can be maintained without transport) in which I use a name (like name of function module which calls RFC) as key field. second field is the name of the destination.