Show TOC

 Maintaining Sender-Receiver Assignment for SAP Transaction iViewLocate this document in the navigation structure

Use

With the report-report interface, you can call SAP transactions from BEx Web Application iViews. To call the SAP transaction in the portal desktop, you need a Web address with portal URL.

In contrast to the Filter command for BEx Web Applications, there is no fixed component in the Web address for SAP transactions.

Procedure

Test URL

Before you create the Web address and maintain the assignment details, call the URL in a Web browser to test it. You can call the URL directly with the SAP ITS URL of the SAP transaction. For testing it is not necessary that you call the URL in the portal.

The syntax of a SAP transaction parameter always comprises a name/value pair for a value:

<screenfield>=<value>

Example of a SAP transaction parameter:

…?RMMG1-MATNR=4711

The SAP transaction parameter corresponds to the Material input field in the SAP transaction Display Material (transaction code MM03).

Field Transfer

Material RMMG1-MATNR (name of the screen field)

The value 4711 is automatically filled by the report-report interface.

Determine Technical Name of the Screen Field

  1. Call the SAP transaction and choose the screen field.
  2. Open help with F1.
  3. To determine the name of the screen field, choose Technical Information.

Maintain Sender-Receiver Assignment (transaction code RSBBS)

  1. Insert an empty URL parameter DynamicParameter into the Web address. For more information, see Creating Web Address as Receiver .
    Tip

    Example: <portal_protocol>://<portal_server>/irj/portal?NavigationTarget=ROLES://portal_content/…/RRI_Target_SAP_ERP&DynamicParameter=

  2. Maintain the parameter name for the screen field in the Field Assignments dialog box. For more information, see Maintaining Assignment Details .
    Tip

    Example:

    The field name RMMG1-MATNR is assigned to the InfoObject Material.

Maintain Settings on the iView (Portal Content Studio)

Change the property Process First Screen for the target iView to Yes. When all of the input fields of an SAP transaction are full, the first screen of the transaction is processed automatically.

With certain SAP transactions, the screen can be skipped using an OK code (such as SHOW for Display or UPDATE for change). You can maintain the required OK code for the SAP transaction in the OK Code property. Using the ABAP debugger, you can determine the required OK code. The executed OK code for an SAP transaction is displayed under the field name OK CODE in the ABAP debugger.

Result

You have maintained the sender-receiver settings to jump from one BEx Web Application to a SAP transaction.