Show TOC

Procedure documentationDefining a Parameterized Launch Transaction Locate this document in the navigation structure

 

The purpose of your parameterized launch transaction is to assemble the URL for accessing business-on-behalf Web shops (BoB shops) and to call that URL in a Web browser. The Web browser then displays a logon prompt to the business user and, after successful logon, it displays a list of available BoB shops. When the business user selects a BoB shop from that list, the BoB shop opens for orders on behalf of the account that is referenced in the parameter of the launch transaction.

To assemble the URL for BoB shops, the launch transaction requires the information listed in the following overview. We use nested lists to show how this information is grouped in Customizing. The nesting results in a tree structure that has the launch transaction as its root node. For ease of reference in the steps of the procedure for setting up the launch transaction, we attach numeric labels to the nodes in the tree structure. However, the order of the numbers in the labels does not matter for the order of the steps in setting up the launch transaction.

Note Note

The order in this overview reflects the order of elements in the resulting URL and is therefore probably easiest to understand.

However, for the steps that you need to perform to set up the launch transaction, we suggest a different order, which is quicker because it visits each Customizing activity only once.

End of the note.

  • Launch transaction

    • [1] Type of launch transaction

    • [2] URL ID

      • [2.1] ABAP Objects Class for constructing a URL

      • [2.2] Selection indicating that you want to construct a URL that points to a Java application, not to a BSP application

      • [2.3] Selection indicating whether or not you want portal integration for the URL

      • [2.4] Names of parameters that you want to allow for a launch transaction that includes [2]

    • [3] J2EE Web application

      • [3.1] Protocol (HTTP or HTTPS) that you want to use for BoB shop access

      • [3.2] Host where the J2EE Server of your SAP NW AS Java system runs

      • [3.3] Port where the J2EE Server of your SAP NW AS Java system listens for requests through the protocol stated in [3.1]

      • [3.4] Path to the E-Commerce Business-to-Business Application on the J2EE server of the SAP NW AS Java system

      • [3.5] XCM application configuration that you want the E-Commerce Business-to-Business Application to use for BoB shops

    • [4] Assignment of values to the parameters that you allowed for the launch transaction in [2.4]

    • [5] Any additional parameters that you want to attach to the URL

The reference to the current account must be in [4]. The difference between [4] and [5] is that the system only resolves references in [4], but not in [5]. So you can use [5] only for character strings that you want to attach to the URL exactly as they are.

Procedure

To implement the tree structure that was presented as an overview, perform the following steps in your SAP CRM system:

  1. In Customizing for Customer Relationship Management, under   Web Channel   Basic Settings   Activate Links from CRM WebClient UI to Web Channel Applications  , choose Define URLs and Parameters for the data under node [2] of the overview tree structure.

    Note Note

    Alternatively, you can access the same activity in Customizing for Customer Relationship Management under   Partner Channel Management   Basic Settings   Activate Links from SAP CRM UI to SAP CRM Web Channel Applications  .

    End of the note.

    Note Note

    The standard delivery of SAP CRM offers the CHM-BOB-A2O entry in this Customizing activity for the purposes of orders-on-behalf.

    End of the note.

    • The Class field in the details of a URL ID is for node [2.1] of the overview tree structure. For constructing BoB Shop URLs, use the CL_CRM_CHM_ECO_LINK_XCM class.

    • The Non-BSP URL radio button in the details of a URL ID is for node [2.2] of the overview tree structure. For BoB Shop URLs, select the Non-BSP URL radio button, but do not make any entries in the fields that belong to that radio button.

      Note Note

      The reason why we recommend that you do not make any entries in the fields that belong to the Non-BSP URL radio button is this:

      If these fields are empty, the system gathers the information for node [3] and node [5] of the overview tree structure from your settings in later Customizing steps. Technically, you could provide that information here instead of later, but then it would not be shared with other URL launch transactions that involve the same SAP NW AS Java system.

      End of the note.

    • The Portal Integration checkbox in the details of a URL ID is for node [2.3] of the overview tree structure. For BoB Shop URLs, you can leave the Portal Integration checkbox unselected.

    • The Define Parameters subdialog for a URL ID is for node [2.4] of the overview tree structure. For BoB Shop URLs, create a parameter named CRM_OBJECT_ID.

      In the Element type field for the CRM_OBJECT_ID parameter, select Import or Export and Import to pass this parameter from the CRM WebClient UI to the Java application for the Web shops.

  2. In Customizing for Customer Relationship Management, under   Web Channel   Basic Settings   Activate Links from CRM WebClient UI to Web Channel Applications  , choose Define Protocol, Host Name, Port, and XCM Application Configuration for the data under node [3] of the overview tree structure.

    Note Note

    Alternatively, you can access the same activity in Customizing for Customer Relationship Management under   Partner Channel Management   Basic Settings   Activate Links from SAP CRM UI to SAP CRM Web Channel Applications  .

    End of the note.

    Note Note

    The standard delivery of SAP CRM offers the BOB entry in this Customizing activity for the purposes of orders-on-behalf.

    End of the note.

    • The Protocol field is for node [3.1] of the overview tree structure. For BoB shop URLs, select HTTPS.

    • The Host name of Web AS Java Server field is for node [3.2] of the overview tree structure. For BoB shop URLs, enter the name of the host that you used in Creating a Web Shop for Business on Behalf and Creating an Application Configuration in XCM.

    • The Port number field is for node [3.3] of the overview tree structure. For BoB shop URLs, enter the number of the HTTPS port.

    • The XCM Application Configuration field is for node [3.5] of the overview tree structure. For BoB shop URLs, enter the name of the application configuration that you created or plan to create in Creating an Application Configuration in XCM.

      Note Note

      It does not matter whether you have created this XCM application configuration yet. You can also enter a name that does not exist yet and create an XCM application configuration of that name afterwards. All that matters is that an XCM application configuration of that name exists by the time that a business user tries to access the BoB shop.

      End of the note.

    • The URL field is for node [3.4] of the overview tree structure. For BoB shop URLs, enter /b2b_2/b2b/portalEntry.do.

  3. In Customizing for Customer Relationship Management, under   UI Framework   Technical Role Definition   Transaction Launcher  , choose the Configure Transaction Launcher wizard for the data in nodes [1] and [4] of the overview tree structure.

    1. In the Launch Trans. ID field on the Entries page of the wizard, enter a name for the launch transaction that you want to define.

      Note Note

      The selection list for the Launch Trans. ID field contains the names of existing launch transactions. If you enter or select one of those names and click the Continue pushbutton, the wizard displays the details of that existing launch transaction.

      End of the note.

      Note Note

      The standard delivery of SAP CRM offers the CHM-BOB-A2O launch transaction for the purposes of orders-on-behalf.

      Do not confuse the CHM-BOB-A2O launch transaction with the CHM-BOB-A2O URL ID that the standard delivery offers in Customizing for Customer Relationship Management under   Web Channel   Basic Settings   Activate Links from CRM WebClient UI to Web Channel Applications   Define URLs and Parameters  . The launch transaction is the root node of the overview tree structure, but the URL ID is node [2] of the overview tree structure.

      End of the note.

    2. In the Class Name field on the Technical Details page of the wizard, enter or select the CL_CRM_CHM_TL_CHM_BOB_A2O class.

    3. If you want the E-Commerce Business-to-Business Application with the BoB shop to open in a separate browser window, select the Stateful checkbox on the Technical Details page of the wizard.

    4. The Transaction Type field on the Further Technical Details page of the wizard is for node [1] of the overview tree structure. For BoB shop URLs, select URL Transaction.

      Selecting URL Transaction in this field makes the Details area on the same wizard page editable.

      Note Note

      If you have selected the Show Keys in All Dropdown Lists checkbox on the Expert tab page of the Options... function from the Customize Local Layout menu of the SAP GUI, the system displays B URL Transaction instead of URL Transaction.

      End of the note.

    5. In the URL ID field of the wizard, select the URL ID that is node [2] in the overview tree structure to assign it to the launch transaction.

    6. In the Parameter field on the Transaction Parameters page of the wizard, select a parameter name, then enter a character string in the Value field to assign that character string to the parameter.

      Note Note

      The selection list for the Parameter field is what you set up as node [2.4] of the overview tree structure. For BoB shop URLs, you created a parameter named CRM_OBJECT_ID in a previous step, so you now have CRM_OBJECT_ID in your selection list.

      End of the note.

      For BoB shop URLs, select CRM_OBJECT_ID in the Parameter field and enter //clipboardBuilHeader/BP_GUID in the Value field.

      Note Note

      //clipboardBuilHeader/BP_GUID is a variable that evaluates to the GUID of the current account when the system checks the variable in a situation where there is a current account.

      End of the note.

    7. Continue to complete the definition of the launch transaction.

  4. In Customizing for Customer Relationship Management, under   Web Channel   Basic Settings   Activate Links from CRM WebClient UI to Web Channel Applications  , choose Define URLs for the data under node [5] of the overview tree structure.

    Note Note

    Alternatively, you can access the same activity in Customizing for Customer Relationship Management under   Partner Channel Management   Basic Settings   Activate Links from SAP CRM UI to SAP CRM Web Channel Applications  .

    End of the note.

    1. In the Launch Trans. ID column, look up the row for the launch transaction that you defined in the wizard as the root node of the overview tree structure.

      Note Note

      In the standard delivery of SAP CRM, this is the CHM-BOB-A2O launch transaction.

      End of the note.

    2. In the row of your launch transaction, in the J2EE Web Application column, enter or select the name that is node [3] in the overview tree structure to assign it to your launch transaction.

    3. The URL Parameter column in the row of your launch transaction is for node [5] of the overview tree structure. For the URL for orders-on-behalf, enter the following character string: forward=account2Basket

    4. Save your entries.

Result

If you set node [1] of the overview tree structure to URL Transaction, the launch transaction invokes the class that you entered as node [2.1] of the overview tree structure.

If you set node [2.2] of the overview tree structure to Non-BSP URL and left the fields under the Non-BSP URL option empty in the corresponding Customizing activity, then the class in node [2.1] uses the values in the following nodes of the overview tree structure to assemble the URL, otherwise it ignores them:

  • [2.3]

  • [3.1] to [3.5]

  • [4]

  • [5]

Note Note

Your entry in node [2.4] of the overview tree structure does not become part of the URL. It is only required as a control for your entry in node [5] of the overview tree structure.

End of the note.

Note Note

The protocol that you selected in node [3.1] overrides the HTTPS checkbox in the Customizing activity for node [2].

End of the note.