Show TOC

Procedure documentationDefining Transaction Launcher Logical Systems and URLs

 

System administrators use this procedure to define which systems and clients to use for the transaction launcher for ITS and IS-U front office process based launch transactions.

For more information, see Transaction Launcher.

Example Example

If you are working with your own SAP CRM system and another SAP system, you must make two entries in this activity for each system (development, test, and productive) that you plan to use.

End of the example.

Prerequisites

You have done the following:

  • Installed the Internet Transaction Server (ITS) to provide access to the local SAP CRM system or to another SAP system

  • Started the ITS

  • Noted the URL of the ITS

  • Defined your logical systems using transaction BD54

  • Defined your Remote Function Call (RFC) destinations using transaction SM59

  • Assigned RFC destinations to logical systems using transaction BD97

Procedure

Recommendation Recommendation

Define a mapped logical system called OWNLOGSYS that uses the logical system of the local system or client.

End of the recommendation.

  1. On the SAP Easy Access screen, choose Start of the navigation path Interaction Center Next navigation step Interaction Center WebClient Next navigation step Administration Next navigation step System Parameters Next navigation step Define Transaction Launcher Logical Systems and URLs End of the navigation path.

  2. Choose New Entries.

  3. Enter the relevant data in each field:

    Name

    Definition

    Use

    Mapped LogSys

    Variable in the code and in Customizing that points to the current logical system. You use this variable when you define launch transactions in Customizing for Customer Relationship Management under Start of the navigation path Interaction Center WebClient Next navigation step Basic Functions Next navigation step Transaction Launcher Next navigation step Configure Transaction Launcher (Wizard) End of the navigation path.

    Enter the variable that you want to use.

    Note Note

    Define this variable here once and then do not change it. Otherwise, you need to change it everywhere it occurs in the Customizing settings and the code as well.

    End of the note.

    Logical system

    Name of the defined logical systems you are using. This logical system corresponds to the variable you listed in field Mapped LogSys.

    Logical systems must be defined either by pointing to their own systems or to SAP systems. You can define logical systems in transaction BD54.

    Enter the logical system name.

    Note Note

    This entry must be the same as the logical system, or own logical system, of the target system defined in transaction SCC4.

    End of the note.

    ITS client

    The Internet Transaction Server (ITS) client is the system client where the launch transactions are executed when agents use the IC WebClient.

    Enter the client.

    URL of ITS

    Points to the system where the launch transactions are executed when agents use the IC WebClient.

    Maintain the URL that calls the service WEBGUI of the ITS in the remote system

    Note Note

    You need to log in to the remote system (for example, SAP ERP) to gather the information needed to maintain the URL, but the settings are made in the CRM system.

    End of the note.

    The URL has the format <protocol>://<host>:<port>/<path>/!?~transaction=<transaction>&~okcode=ICEXECUTE, with the following parts:

    • Protocol

      Use either HTTP or HTTPS.

    • Host and port

      Go to ICM Monitor (transaction SMICM) in the remote system or client. From the menu, choose Start of the navigation path Go To Next navigation step Services End of the navigation path, select the line that corresponds to your protocol, and display the details. Here you can find the host and the port.

    • Path

      Go to Maintain Services (transaction SICF) in the remote system or client. Search for the service name WEBGUI. If you get multiple results, choose the path containing GUI. Usually the service WEBGUI is under the path sap/bc/gui/sap/its/webgui.

    • Transaction

      There are three possible values, depending on the type of remote system:

      • IC_LTX

        Use this transaction if you want to call the ITS of your own CRM system.

      • IC_LTXE

        Use this transaction if you want to call the ITS of an ERP system of release 2005 (SAP_ABA_700) or higher.

      • IC_LTXR

        Use this transaction if you want to call the ITS of an ERP system with PI release track 2004_1_46C to 2004_1_500.

    Example Example

    The URL for ITS could look like the following:http://fh3tdc00.wdf.sap.corp:52080/sap/bc/gui/sap/its/webgui/!?~transaction=IC_LTXE&~okcode=ICEXECUTE.

    End of the example.

    Local ITS

    The Internet Transaction Server (ITS) of the local system.

    To maintain the URL of a remote ITS, you must transport entries to downstream systems and then adjust the entries to the corresponding system landscapes. Therefore, instead of entering ITS details of the remote system, we recommend that you use the ITS of the local system for rendering purposes (the system can still execute Business Object Repository (BOR) objects of remote systems).

    Note Note

    If you use the local ITS, then it is not necessary (nor possible) for you to maintain the following fields:

    • ITS client

    • URL of ITS

    End of the note.

  4. Repeat the above steps for each logical system you are using.

  5. Complete this administrative activity in each system (development, test, productive) you use.

    Note Note

    Use the same mapped logical system in all systems.

    End of the note.

Result

The system can properly execute launch transactions that you have defined because you have defined connections to other systems.