With portal navigation you can call SAP transactions from BEx Web Application iViews.
Before you include the JavaScript for portal navigation in the Web template, call the URL to test it in a Web browser. You can call the URL directly with the SAP ITS URL of the SAP transaction. For testing it is not necessary to call the URL in the portal.
The syntax of an SAP transaction parameter always comprises a name/value pair for a value:
<screenfield>=<value>
Example of an 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).
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.
The name/value pairs of the SAP transaction parameters represent the value of the portal URL parameter DynamicParameter. This fixed component of the command URL for filtering must be coded as the value of a URL parameter.
· ’=’ must be replaced with ‘%3D’
· ’&’ must be replaced with ‘%26’
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.
You have determined the parameter and maintained the iView in order to jump from a BEx Web Application iView to an SAP transaction iView using portal navigation.