Вы находитесь на странице: 1из 4
Transaction Launcher Use Similar to the Interaction Center (IC) WinClient <a href=Action Box , the transaction launcher is a tool that system administrators use to allow agent access to business transactions directly from the IC WebClient screen. It is essentially a collection of shortcuts to available functions or transactions within SAP CRM and Enterprise R/3. The transaction launcher is only available in the IC WebClient. Integration When launch transactions are created, they are placed in the Navigation Bar so agents have access to them. Agents are not aware if the transactions in the navigation bar are standard IC WebClient functions, or functions made possible from the transaction launcher. Selecting a launch transaction opens the transaction directly in the IC WebClient interface. The main benefit of using launch transactions is to save agents from logging into multiple systems and repeating data entry. In the diagram below, using launch transactions, the IC WebClient can provide a single point of entry to transactions in the two systems. Overview The transaction launcher can start SAP GUI for HTML transactions via the Internet Transaction Server (ITS) from both Enterprise R/3 and SAP CRM, and People-Centric User Interface (UI) transactions from SAP CRM. " id="pdf-obj-0-2" src="pdf-obj-0-2.jpg">

Transaction Launcher

Transaction Launcher Use Similar to the Interaction Center (IC) WinClient <a href=Action Box , the transaction launcher is a tool that system administrators use to allow agent access to business transactions directly from the IC WebClient screen. It is essentially a collection of shortcuts to available functions or transactions within SAP CRM and Enterprise R/3. The transaction launcher is only available in the IC WebClient. Integration When launch transactions are created, they are placed in the Navigation Bar so agents have access to them. Agents are not aware if the transactions in the navigation bar are standard IC WebClient functions, or functions made possible from the transaction launcher. Selecting a launch transaction opens the transaction directly in the IC WebClient interface. The main benefit of using launch transactions is to save agents from logging into multiple systems and repeating data entry. In the diagram below, using launch transactions, the IC WebClient can provide a single point of entry to transactions in the two systems. Overview The transaction launcher can start SAP GUI for HTML transactions via the Internet Transaction Server (ITS) from both Enterprise R/3 and SAP CRM, and People-Centric User Interface (UI) transactions from SAP CRM. " id="pdf-obj-0-6" src="pdf-obj-0-6.jpg">

Use

Similar to the Interaction Center (IC) WinClient Action Box, the transaction launcher is a tool that system administrators use to allow agent access to business transactions directly from the IC WebClient screen. It is essentially a collection of shortcuts to available functions or transactions within SAP CRM and Enterprise R/3.

The transaction launcher is only available in the IC WebClient.

Integration

When launch transactions are created, they are placed in the Navigation Bar so agents have access to them. Agents are not aware if the transactions in the navigation bar are standard IC WebClient functions, or functions made possible from the transaction launcher.

Selecting a launch transaction opens the transaction directly in the IC WebClient interface. The main benefit of using launch transactions is to save agents from logging into multiple systems and repeating data entry. In the diagram below, using launch transactions, the IC WebClient can provide a single point of entry to transactions in the two systems.

Overview

Transaction Launcher Use Similar to the Interaction Center (IC) WinClient <a href=Action Box , the transaction launcher is a tool that system administrators use to allow agent access to business transactions directly from the IC WebClient screen. It is essentially a collection of shortcuts to available functions or transactions within SAP CRM and Enterprise R/3. The transaction launcher is only available in the IC WebClient. Integration When launch transactions are created, they are placed in the Navigation Bar so agents have access to them. Agents are not aware if the transactions in the navigation bar are standard IC WebClient functions, or functions made possible from the transaction launcher. Selecting a launch transaction opens the transaction directly in the IC WebClient interface. The main benefit of using launch transactions is to save agents from logging into multiple systems and repeating data entry. In the diagram below, using launch transactions, the IC WebClient can provide a single point of entry to transactions in the two systems. Overview The transaction launcher can start SAP GUI for HTML transactions via the Internet Transaction Server (ITS) from both Enterprise R/3 and SAP CRM, and People-Centric User Interface (UI) transactions from SAP CRM. " id="pdf-obj-0-27" src="pdf-obj-0-27.jpg">

The transaction launcher can start SAP GUI for HTML transactions via the Internet Transaction Server (ITS) from both Enterprise R/3 and SAP CRM, and People-Centric User Interface (UI) transactions from SAP CRM.

Information can be passed to and from the IC WebClient and the launch transaction, depending upon Customizing. For example, the confirmed business partner can be passed to an Enterprise R/3 sales order and the created document can be returned.

Activities

Maintain IC WebClient Customizing activity Transaction Launcher Configure Transaction Launcher.

Information can be passed to and from the IC WebClient and the launch transaction, depending uponTransaction Launcher Logical Systems and URLs . Maintain IC WebClient Customizing activity Transaction Launcher  Configure Transaction Launcher. Defining Transaction Launcher Logical Systems and URLs Use System administrators use this procedure to define which systems and clients to use for the Transaction Launcher . You only have to maintain these settings if you use the transaction launcher. 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 R/3 system with CRM plug-ins For more information about the SAP ITS, see the SAP Help Portal (http://help.sap.com) under SAP NetWeaver  SAP Web Application Server  <relevant release and language> SAP NetWeaver Components  ITS / SAP@Web Studio (BC-FES-ITS)  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 ... 1. From the SAP Easy Access menu, choose Interaction Center  Interaction Center WebClient  Administration  System Parameters  Define Transaction Launcher Logical Systems and URLs . 2. Choose New Entries . 3. Enter the relevant data in each field: Name Definition Use LogSys Variable in the code Enter the variable you want to use. Mapping and in Customizing that points to the Define this variable here once and then do not change it, " id="pdf-obj-1-15" src="pdf-obj-1-15.jpg">
Information can be passed to and from the IC WebClient and the launch transaction, depending uponTransaction Launcher Logical Systems and URLs . Maintain IC WebClient Customizing activity Transaction Launcher  Configure Transaction Launcher. Defining Transaction Launcher Logical Systems and URLs Use System administrators use this procedure to define which systems and clients to use for the Transaction Launcher . You only have to maintain these settings if you use the transaction launcher. 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 R/3 system with CRM plug-ins For more information about the SAP ITS, see the SAP Help Portal (http://help.sap.com) under SAP NetWeaver  SAP Web Application Server  <relevant release and language> SAP NetWeaver Components  ITS / SAP@Web Studio (BC-FES-ITS)  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 ... 1. From the SAP Easy Access menu, choose Interaction Center  Interaction Center WebClient  Administration  System Parameters  Define Transaction Launcher Logical Systems and URLs . 2. Choose New Entries . 3. Enter the relevant data in each field: Name Definition Use LogSys Variable in the code Enter the variable you want to use. Mapping and in Customizing that points to the Define this variable here once and then do not change it, " id="pdf-obj-1-17" src="pdf-obj-1-17.jpg">

Defining Transaction Launcher Logical Systems and URLs

Information can be passed to and from the IC WebClient and the launch transaction, depending uponTransaction Launcher Logical Systems and URLs . Maintain IC WebClient Customizing activity Transaction Launcher  Configure Transaction Launcher. Defining Transaction Launcher Logical Systems and URLs Use System administrators use this procedure to define which systems and clients to use for the Transaction Launcher . You only have to maintain these settings if you use the transaction launcher. 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 R/3 system with CRM plug-ins For more information about the SAP ITS, see the SAP Help Portal (http://help.sap.com) under SAP NetWeaver  SAP Web Application Server  <relevant release and language> SAP NetWeaver Components  ITS / SAP@Web Studio (BC-FES-ITS)  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 ... 1. From the SAP Easy Access menu, choose Interaction Center  Interaction Center WebClient  Administration  System Parameters  Define Transaction Launcher Logical Systems and URLs . 2. Choose New Entries . 3. Enter the relevant data in each field: Name Definition Use LogSys Variable in the code Enter the variable you want to use. Mapping and in Customizing that points to the Define this variable here once and then do not change it, " id="pdf-obj-1-21" src="pdf-obj-1-21.jpg">

Use

System administrators use this procedure to define which systems and clients to use for the Transaction Launcher. You only have to maintain these settings if you use the transaction launcher.

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 R/3 system with CRM plug-ins

For more information about the SAP ITS, see the SAP Help Portal (http://help.sap.com) under SAP NetWeaver SAP Web Application Server <relevant release and language> SAP NetWeaver Components ITS / SAP@Web Studio (BC-FES-ITS)

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

...

  • 1. From the SAP Easy Access menu, choose Interaction Center Interaction Center WebClient Administration System Parameters Define Transaction Launcher Logical Systems and URLs.

  • 2. Choose New Entries.

  • 3. Enter the relevant data in each field:

Name

Definition

Use

LogSys

Variable in the code

Enter the variable you want to use.

Mapping

and in Customizing that points to the

Mapping and in Customizing that points to the Define this variable here once and then do

Define this variable here once and then do not change it,

 

current logical system. You use this

otherwise you will need to change it everywhere it occurs in the code as well.

variable when you define launch transactions in Customizing for

For an example of the LogSys Mapping variable, see the DEFAULT profile in IMG activity Define

For an example of the LogSys Mapping variable, see the DEFAULT profile in IMG activity Define Transaction Launcher Profiles. There you will find two mapping variables:

the Interaction Center WebClient, IMG activity Define Transaction Launcher Profiles.

OWNLOGSYS and R3SYS46C.

Logical

Name of the defined

Logical systems must

Enter the logical system name.

System

logical systems you are using. This logical system

This entry must be the same as the logical system, or own logical system, of the

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

corresponds to the variable you listed in field LogSys Mapping.

be defined either by pointing to their own systems or to SAP R/3 systems.You can define logical systems in transaction BD54.

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

Enter the URL in the following format, depending on the system you are using:

transactions are

SAP R/3 system (4.5B and above)

executed when agents use the IC WebClient.

http://<server name and full domain>:<port>/scripts/wgate/CCMP_RABOX/!

SAP CRM system (3.1 and above)

http://<server name and full domain>:<port>/scripts/wgate/CRM_CIC_RABOX/!

  • 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.

current logical system. You use this otherwise you will need to change it everywhere it occurs

Use the same mapped logical system in all systems.

Result

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

Example

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

Result The system can properly execute launch transactions that you have defined because you have defined