{"id":542,"date":"2011-12-04T12:55:33","date_gmt":"2011-12-04T12:55:33","guid":{"rendered":"http:\/\/sapsecurityanalyst.com\/WP\/?page_id=542"},"modified":"2015-05-03T08:52:27","modified_gmt":"2015-05-03T08:52:27","slug":"rfc-maintenance-sm59","status":"publish","type":"page","link":"https:\/\/sapsecurityanalyst.com\/WP\/general-disclaimer\/rfc-maintenance-sm59\/","title":{"rendered":"SAP RFC Maintenance (SM59)"},"content":{"rendered":"<p><span style=\"color: #0000ff; font-family: verdana;\"><!--more--><\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #0000ff; font-family: verdana;\"><br \/>\n<span style=\"color: #4c4c4c;\">In this post we have discussed about SAP RFC maintenance.<\/span><\/span><\/p>\n<p><span style=\"color: #0000ff; font-family: verdana;\"><!--more--><br \/>\n<\/span><br \/>\n<span style=\"color: #0000ff; font-family: verdana;\"><span style=\"color: #4c4c4c;\">RFC connection is maintained using tcode<\/span> <strong>SM59<\/strong>.<span style=\"color: #4c4c4c;\"> Following screen comes when SM59 tcode is executed.<\/span><br \/>\n<\/span><!--more--><br \/>\n<a href=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-545\" title=\"sm59\" src=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59.jpg\" alt=\"\" width=\"442\" height=\"294\" srcset=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59.jpg 442w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59-300x199.jpg 300w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59-290x192.jpg 290w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/sm59-150x99.jpg 150w\" sizes=\"(max-width: 442px) 100vw, 442px\" \/><\/a><\/p>\n<p><!--more--><br \/>\n<span style=\"color: #4c4c4c; font-family: verdana;\">There are various type of RFC Connections &#8211; Type 3, G, H, I, L, T, X.<\/span><br \/>\n<span style=\"color: #4c4c4c; font-family: verdana;\"> <!--more--><\/span><\/p>\n<p><span style=\"color: #4c4c4c; font-family: verdana;\"><br \/>\nABAP Connections Type 3 is used for RFC connections for ABAP Systems. We will discuss about ABAP Connections Type 3 RFC. To create a new ABAP Connections Type 3 RFC, select ABAP Connections and click on create button as shown in the figure above.<\/span><\/p>\n<p><span style=\"color: #4c4c4c; font-family: verdana;\"><!--more--><br \/>\n<\/span><br \/>\n<script type=\"text\/javascript\">\/\/ < ![CDATA[\n\/\/ < ![CDATA[\ngoogle_ad_client = \"ca-pub-1241348474673689\";\n\/* All content above *\/\ngoogle_ad_slot = \"3293572617\";\ngoogle_ad_width = 468;\ngoogle_ad_height = 15;\n\/\/ ]]><\/script><br \/>\n<script src=\"http:\/\/pagead2.googlesyndication.com\/pagead\/show_ads.js\" type=\"text\/javascript\">\/\/ < ![CDATA[\n\/\/ < ![CDATA[\n\n\/\/ ]]><\/script><\/p>\n<p><span style=\"color: #0000ff; font-family: verdana;\"><span style=\"color: #4c4c4c;\">We get the following screen:<\/span><\/span><\/p>\n<p><span style=\"color: #0000ff; font-family: verdana;\"><!--more--><\/span><\/p>\n<p><span style=\"color: #0000ff; font-family: verdana;\"><br \/>\n<\/span><\/p>\n<p><a href=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-546\" title=\"RFC connection type3\" src=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3.jpg\" alt=\"\" width=\"652\" height=\"602\" srcset=\"https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3.jpg 652w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3-300x276.jpg 300w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3-290x267.jpg 290w, https:\/\/sapsecurityanalyst.com\/WP\/wp-content\/uploads\/2011\/11\/RFC-connection-type3-150x138.jpg 150w\" sizes=\"(max-width: 652px) 100vw, 652px\" \/><br \/>\n<\/a><!--more--><br \/>\n<span style=\"color: #0000ff; font-family: verdana;\"><br \/>\n<span style=\"color: #4c4c4c;\">In the above figure, we see the field<\/span> &#8220;<\/span><strong><span style=\"color: #0000ff;\">RFC Destination&#8221;<\/span><\/strong><span style=\"color: #0000ff;\"><span style=\"color: #4c4c4c;\">. Here we provide the RFC Destination name. The usual naming convention for RFC Destination is<\/span> <strong>&lt;SID&gt;CLNT&lt;Client No&gt;. <\/strong><span style=\"color: #4c4c4c;\">So if the Destination System Id is PRD and client No is 100, then RFC Destination will be PRDCLNT100. <\/span><\/span><\/p>\n<p><span style=\"color: #0000ff;\"><span style=\"color: #4c4c4c;\">This RFC Destination detail is maintained in table<\/span> <strong>RFCDES.\u00a0<\/strong><br \/>\n<\/span><!--more--><br \/>\n<span style=\"color: #0000ff; font-family: verdana;\"><br \/>\n<span style=\"color: #4c4c4c;\">In the <\/span><\/span><strong><span style=\"color: #0000ff;\">Description<\/span><\/strong><span style=\"color: #0000ff;\">\u00a0<span style=\"color: #4c4c4c;\">field, we maintain the RFC Description details.<\/span><\/span><\/p>\n<p><span style=\"color: #0000ff;\"><br \/>\n<\/span><!--more--><br \/>\n<span style=\"color: #0000ff; font-family: verdana;\"><span style=\"font-family: verdana; color: #4c4c4c;\">In the <\/span><strong><span style=\"font-family: verdana;\">Target Host <\/span><\/strong><span style=\"color: #4c4c4c;\">we maintain Hostname or IP Address of the Destination and in the<\/span> <strong>System No <\/strong><span style=\"color: #4c4c4c;\">we maintain System No of the Destination System.<\/span><\/span><\/p>\n<p>&nbsp;<\/p>\n<p><!--more--><\/p>\n<p>Based on the requirement, we select either Trusted or Untrusted system in the &#8220;<strong><span style=\"color: #0000ff;\">Logon &amp; Security<\/span><\/strong>&#8221; tab of SM59 screen. We have discussed in more details on this in our next post on SAP RFC maintenance.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><span style=\"color: #e63518;\">For more details on &#8220;Logon &amp; Security&#8221; tab, please refer to <span style=\"text-decoration: underline;\"><a href=\"https:\/\/sapsecurityanalyst.com\/WP\/general-disclaimer\/rfc-maintenance-contd\" target=\"_blank\"><span style=\"color: #e63518;\"><em>our next post on SAP RFC maintenance.<\/em><\/span><\/a><\/span><\/span><\/h3>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"parent":38,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/pages\/542"}],"collection":[{"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/comments?post=542"}],"version-history":[{"count":23,"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/pages\/542\/revisions"}],"predecessor-version":[{"id":2122,"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/pages\/542\/revisions\/2122"}],"up":[{"embeddable":true,"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/pages\/38"}],"wp:attachment":[{"href":"https:\/\/sapsecurityanalyst.com\/WP\/wp-json\/wp\/v2\/media?parent=542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}