Show TOC

Naming ConventionLocate this document in the navigation structure

Transaction SM59 does not allow you to create several destinations with the same name, even if the connection types are different. For referencing associated destinations of different connection types, define multiple SM59 entries with the same base name and a suffix (_RFC, _HTTP, _HTTPS), and reference the base name only.

The following suffixes can be used:

  • _HTTP (XYZCLNT123_HTTP): For the definition of HTTP connection settings; can be applied for connection type H

  • _HTTPS (XYZCLNT123_HTTPS): For the definition of HTTPS connection settings; can be applied for connection type H

  • _RFC (XYZCLNT123_RFC): For the definition of RFC/SAP GUI connection settings; can be used for connection type 3

  • _BOE (XYZCLNT123_BOE): For the definition of an additional HTTP connection for BI, which is referenced in an FPM launchpad role for Crystal Report links; can be used for connection type H

For connection types ABAP (3) or HTTP (H), the suffix can be omitted and the runtime will still resolve the connection data properly. This fallback allows you to reuse existing definitions without extra configuration.

Example

If the base name is XYZCLNT123, the server runtime resolves the destination names in the following sequence:

  • For ABAP connections: XYZCLNT123_RFC, XYZCLNT123

  • For HTTP connections: XYZCLNT123_HTTPS, XYZCLNT123_HTTP, XYZCLNT123

Note Destination names in transaction SM59 and in tools using SM59 aliases are case-sensitive. We recommend to use upper case names and to type suffixes in all consumption points. The technical destination names NONE, LOCAL,and so on are resolved as the local system, meaning the application is located on the same system as the runtime.