Skip to Content

In the Web Dynpro Tools it is possible to change the default logical system name settings provided during import of an Adaptive RFC model. Two logical system names exist, one for Metadata, one for Application data. If either of these need to be adapted without explicitly reimporting the model, then the following procedure must be taken. Please be aware, that the procedure differs, depending on whether you change the logical system name for Meta-data or for Application data.

Application Data

  1. Select and open an arbitrary Model Class within the Adaptive RFC Model of which wish to change the default logical system name.
  2. When selecting the “Porperties” Editor on the lower right hand part of the IDE, you will see 2 categories: “ModelClass Settings” and “Model Settings
  3. In the category “Model Settings” (the lower part) you will find the property “modelInstance_defaultLogicalSystem“. You can edit this value and replace it with the new logical system name. Here is a screenshot:

image

Metadata

The Metadata connection is used to gather Dictionary information. Therefore, this value is not configured in the model, but in the Dictionary. In Adaptive RFC, each model automatically has a Dictionary carrying the same name as the model.

  1. You will find this dictionary under the Dictionary entry in the project hierarchy (same name as your Model). As soon as you select your model’s Dictionary, you will see the property “Logical System Name
  2. You can edit this value and replace it with the new logical system name. Here is a screenshot:

image

Remarks

Additionally, in the project references of your project, you will find a list of system names used by models contained in this project.Whenever you reconfigure one of the above mentioned logical system names, it will automatically be added to the list of JCO references. This is the list of required JCO destinations, which you will see at runtime in the WD Content Admin. This list is NOT THE place to configure which names your models require. Changing/adding/deleting entries in this list will have no effect, unless you make the change directly in the model as described above.

BE AWARE

  • Formerly used logical system names are NOT automatically removed from the list of JCO destinations when you change a logical system Name in the model.
  • You must determine, which JCO destinations are no longer being used by the models of your project and delete them on your own.
  • If you don’t delete them, your application will not fail, but an administrator could be confused, because the WD Content Admin will display even these no longer used destinations.

Enjoy Web Dynpro,

Bertram Ganz, SAP AG

To report this post you need to login first.

16 Comments

You must be Logged on to comment or reply to a post.

  1. Ravi murthy
    I have been trying to change the default JCO destinations on one of the modelled WD App that i have imported. I have changed them all at the points you have mentioned and the app compiles, i have deployed, redeployed etc but when i view the JCo references on the app via WD Console, it always referring to the old ones. Is the Server caching this info or what?
    Wd .properties file only has references to the new destination i have configured but deployment either is not updating this or its being cached.
    Any clues.
    (0) 
  2. Ravi murthy
    Please ignore my previous question as that was my own wrong doing.
    I can now see the updated JCo Destinations except when i run the application, its still trying to use the old ones and keeps giving me exception
    Failed to resolve JCO destination name ‘WD_RFC_METADATA_DEST’ in the SLD. No such JCO destination is defined in the SLD

    New JCo destination is SAP_R3_HumanResources_Metadata

    (0) 
  3. sreedevi sree
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 
  4. Gangadharayya Hiremath
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 

Leave a Reply