SAP Note Nr.

Number Version Processor Processing Status Implement. Status Language Short Text Component 1329317 4


Page 1


new Cannot be implemented EN Adjusting the RFC destinations to special requirements CA-TDM-FRM-PCL

________________________________________________________________________ Long Text Symptom
You want to configure specific settings for the RFC destinations but these settings are not provided in RFC destination maintenance in RFC management. To do this, you require an entry in the user profiles and the relevant authorizations. This note describes which settings are necessary to adjust the destinations to meet your requirements.

Other terms
RFC management, SM59, TDMS, CMIS, RFC destination, DMIS, HCM, logon group, SAProuter, SAProuter strings

Reason and Prerequisites
You have the authorizations required to maintain destinations.

Two possible scenarios exist for the individual settings. In the first scenario, you want to make settings to fields for the RFC destination. These settings are not provided in RFC management but they are to be distributed to all relevant systems. In the second scenario, you must configure settings that are different for the destinations in the different systems. For example, this is the case if the connection in the network takes place using the SAProuter and SAProuter strings are used for the host names. For the individual settings, you must ensure that the RFC destinations can be edited in RFC management. This is the same for both scenarios. Ensuring that the RFC destinations can be edited. You are using the control framework in RFC management. Create the user profile parameter PCL_RFC_EXPERT with the parameter value 'X'. 1.a) Call profile parameter maintenance. Menu path: System -> User Profile -> Own Data 1.b) Choose the "Parameter" tab. 1. c) Create a new parameter with the following contents: Parameter ID = PCL_RFC_EXPERT Parameter value = X 1.d) Save the new parameter. Unlock the destinations. You are using the control framework in RFC management. 2.a) Choose the "Definition" tab.

the names of the RFC destinations are displayed in the left column. you can identify this by the red cross in the overview of the distributed . MBT_XXX_PCL = control framework).f) You are now able to change the selected destinations in the control framework. the system displays a red cross on the right next to certain boxes. 3. otherwise.b) Choose the "SM59" pushbutton.a) Select the checkbox of the destination that you want to change. 3.SAP Note Nr.c) Logon to the system with the destination that is to be changed. 4. you must logon to all of the relevant systems and change the destinations manually. 4.2011 Page 2 ________________________________________________________________________ 2. 4. the system no longer displays any red crosses in the overview of the distributed destinations. If the overview for the control framework destinations displays a red cross in the "Receiver" column. To ensure that your destinations also work in scenario two.b) Choose "Synchronize". If a connection is still not possible with a destination or if a destination refers to a different system. The following is valid only for scenario two.d) Save your changes. In the overview of the distribution and synchronization status of the destinations. otherwise. If all destinations have been changed successfully. select the radio button "Unlocked".f) Save your changes. 2. The overall status is green everywhere.c) Make your changes. 4. the receiver system could not establish a connection to the control framework. you must maintain the password again.g) After you have changed all of the destinations.h) For the unlocked destination. Ensure that you specify the password before you save. IMPORTANT: The client and the system number must not be changed.e) Make your changes. 2.e) Choose "Yes" to confirm the message. it is initial.g) Choose "Back" to return. it is initial.b) Choose the "Set lock status" pushbutton. Make the individual settings for an RFC destination. The red cross indicates the destination and the system for which no connection can be established. The names of the roles are entered in the columns that follow. 4. Reason: After the destinations are synchronized. 2.d) Call transaction SM59.a) "Synchronization" tab page 4. IMPORTANT: The client and the system number must not be changed. You can use the last three letters to identify the role of the system (for example. You must distribute the new RFC settings to the relevant systems. 3. 4.e) You can choose "Back" or use F3 to return to RFC management.c) For the destination that you want to unlock.d) Save your settings. Example: In the overview. 1329317 03. Ensure that you specify the password before you save. You are using RFC management and are on the screen area to define destinations. 2. 2. You are using the control framework to maintain the RFC destinations.05. 3. 3. Choose the "Refresh" pushbutton. 2. the system checks the target systems to determine whether it can establish a connection to them.

The system then unlocks the user. Enter the RFC user name in the input field. Log on to the affected system or client.SAP Note Nr. In the application toolbar. Go back to the control system and to RFC management. It is a prerequisite that you have the required authorizations to do this. Useful information: To set up logon groups. RFC destination. For FAQ. ________________________________________________________________________ Valid Releases SAP Test Data Migration Server 2006_1_46C 2006_1_620 2006_1_640 2006_1_700 ________________________________________________________________________ Links to Support Packages Software Component Release Package Name ________________________________________________________________________ ________________________________________________________________________ . IMPORTANT FOR ALL CHANGES THAT WERE MADE: If a red traffic light is displayed after you have made the settings in RFC management. IMPORTANT: After you have changed the settings of the destinations in all of the relevant systems. the destination becomes unusable again. the system overwrites the manual changes that you made and. Determine the role (sender. If you do this. choose the button with the lock symbol (F6). The system provides information about whether or not the user is locked. Call transaction SU01. To do this. 1329317 03. this is often due to the fact that the RFC user is locked in the client that is involved. as a result. see Note 26317.2011 Page 3 ________________________________________________________________________ destinations. system data). and RFC error. It is also useful to choose the refresh button to determine the current status. you can unlock the user directly. receiver. and check whether a red traffic light is still displayed. SM59.05. Q+A. choose the button with the lock symbol (Ctrl+F5). and so on) for which the error has occurred. Check the destination in the relevant system (connection test (does not check the password). see Note 564612. you are no longer permitted to perform synchronization. If the user is locked.