Navigation with BI Content in the
Portal
The following functions are available for navigation with BI Content:
During eventing in the portal, navigation occurs within a portal page. The information is exchanged between iViews using JavaScript. The contents of the iView in which the event was triggered remains visible. A BEx Web Application can be both the source and the target of an event. Authors can exchange user-defined events between BEx Web Applications. Some applications in the portal (such as Manager Self Service (MSS)) send and receive their own events, which can also be sent or received from BEx Web Applications. The author of a BEx Web Application is responsible for the implementation of the JavaScript for sending and receiving. The sending of a portal event can be displayed as a link or as an extension of the context menu.
For more information, see Eventing in the Portal.
Navigation in the portal enables swapping iViews with other iViews. The initial navigation bar and detailed navigation are adapted accordingly. Within a BEx Web Application, you use JavaScript for implementation. Multiple parameters can be transferred to other iViews (such as BEx Web Applications or SAP transactions in SAP ERP, SAP CRM and so on). Navigation in the portal can be displayed as a link or as an extension of the context menu.
For more information, see Navigation in the Portal.
When jumping using the report-report interface in the portal, the jump targets are administrated in BI within the transaction Maintaining Sender/Receiver Assignments (transaction code RSBBS) You can define BEx Web Applications, SAP transactions or external targets on the Web as jump targets. The report-report interface automatically transfers all parameters that can be assigned. The jump targets of the report-report interface are displayed in the context menu of the BEx Web Application.
For more information, see Jumping Using the Report-Report Interface in the Portal