Show TOC

Adapting the Side PanelLocate this document in the navigation structure


This procedure describes how you adapt side panels and CHIPs to your specific requirements.


To be able to adapt the side panel, you need the following authorizations:

  • All authorizations for the authorization objects S_WDR_P13N, S_PB_CHIP and S_PB_PAGE

  • Authorization for transaction LPD_CUST (Overview of Launchpads)


Customizing a Side Panel

You can adapt side panels to your individual requirements, for instance by replacing reports that are displayed as IGS diagrams with reports displayed as HTML5 diagrams. In the SAP NetWeaver Business Client, select the transaction and open the side panel. Choose Start of the navigation path Customizing End of the navigation path to change to Customizing mode. There you can make the following changes (for example):

  • Add additional CHIPs to your side panel that are provided in the CHIP catalog, but are not delivered on a side panel page in the standard system:

    Choose AddAdd CHIP to open the CHIP catalog. There select a CHIP.

  • Remove CHIPs from a side panel:

    From the CHIP menu, choose Remove.

  • Change the sequence of CHIPs using drag and drop

Save your changes. To leave Customizing mode, choose Start of the navigation path Change Adaptation Level Next navigation step Personalization End of the navigation path.

Customize CHIPs

In the SAP NetWeaver Business Client, select the transaction and open the side panel. Choose Start of the navigation path Customizing End of the navigation path to change to Customizing mode.

In the CHIP menu, you make the following settings:

  • Customize Form for master data details and reports displayed as forms

  • Customize Chart for reports displayed as charts

  • Customize Table for attachments and collaboration

  • Customize Link List for related services/link lists

In the CHIP menu under Settings, you determine the following:

  • Notes/Attachments:

    • Changes are allowed by the author only (yes, no)

    • Changes are allowed for the newest note/attachment only (yes, no)

    • Related objects are shown as well (yes, no)

    • Access to Generic Object Services (GOS) (no access, only display authorization, write access)

      GOS storage is only available for ERP systems with EHP6 and above. For more information, see Generic Object Services.

  • All CHIPs that are represented as a form, list, chart, or link list:

    Suffix for tags

  • Collaboration:

    • CHIP does not accept any incoming port events (yes, no)

      If you choose Yes, the system displays feeds and groups noncontextually (all of your own groups and feeds are displayed). You can then use the CHIPs on a start page, for example.

In addition, you can specify the following in Customizing mode in the CHIP menu under Visibility:

  • For all CHIPs that are represented as a form, list, or chart:

    Hide CHIP, if it does not receive any data (yes, no)

Launchpads / Link Lists: Alias Entries, Parameter Mapping (Web Services, Reports), etc.

For the Web services and reports, you have to make the following settings in the relevant launchpad (transaction LPD_CUST):

  • Web Services:

    The application category must be URL.


    You must enter the URL without the parameter that is to be filled dynamically at runtime (such as or

    Under Advanced Parameters, you must define a parameter mapping by choosing the Parameter Mapping pushbutton next to the Application Parameters field. Note that you must assign corresponding target parameters of the Web service to the source parameters defined by SAP (such as BSSP_COMPANY for the company). For more information, see Setting Up the Side Panel in the “Create parameter mapping for Web services” section.

  • Reports:

    For reports based on a personal worklist (POWL) (application category Web Dynpro ABAP, application POWL), we recommend defining the value BSSP_POWL as the application alias to ensure the correct transfer of advanced parameters.

    For reports of the application category BI Web Template, you must define a parameter mapping for the correct transfer of parameters under Advanced Parameters. To do so, choose Parameter Mapping next to the Application Parameters field. A target parameter (the corresponding parameter in the BI Query that usually has a different name from the source parameter) must be assigned to the source parameter (that usually has the name of a BOR field – for more information, see Business Object Repository). For the value types, you usually have to select Single Value and Variable as the type.


Note that the parameter transfer for reports does not work in the following cases:

  • If the reports cannnot be called with parameters

  • If not all parameters exist in the report

This is the case, for instance, for Xcelsius.

Further Customizing Options

The following further Customizing options for reports and link lists are available to you in the Web Dynpro ABAP component configuration:

FPM Feeder Parameters of CHIPs

  • Reports (displayed as a chart or form): POWL application, POWL type or analytic query

  • Launchpad links: BOR object type, feeder class for navigation to POWL (object class must be CL_BSSP_DETAIL_FORM_POWL)

Technical Information

All the CHIPs delivered by SAP are based on the Business Object Repository (BOR). For more information, see Business Object Repository.

The key fields of a BOR object are used to create CHIP inbound ports dynamically at runtime. The field name specified under Reference Field is relevant in the definition of key fields of a BOR object. For the business object BKPF (Accounting Document) , such a CHIP inbound port would contain, for instance, the BOR key fields BUKRS (Company Code), BELNR (Document Number), and GJAHR (Fiscal Year), in each case with the prefix /BSSP/:.

In the display method of the BOR repository, you can navigate to the SAP GUI application (for instance, by using the relevant link in a master data detail CHIP).

In Customizing under Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step Side Panel for Business Suite  Next navigation step Define Additional SAP GUI Tags End of the navigation path (View NWBC_VC_GUI_TAG), you usually define BOR object types as constants for the respective transaction.

The tag is /BSSP/:BORTYPE and the property is of the value: format (for instance value:BKPF). Properties with the prefix value: are interpreted as constants.

Generic CHIPs (for instance, those for notes or attachments) require such entries in the tagging table; for specific CHIPs (such as for the master data CHIP Customer), the information is defined in the BOR object type in the feeder class of the CHIP.