Page tree
Skip to end of metadata
Go to start of metadata

Purpose

This page is created to identify the possible causes of rendering problems using NWBC or Portal and provide solution for common rendering problems.

Overview

By default the SRM-MDM Catalog is called from the SRM Server in a pop-up window. The rendering can be affected by

  1. SRM-MDM Catalog version
  2. Basis and Browser compatibility
  3. Unified rendering
  4. Frame settings
    1. NWBC
    2. Portal 

SRM-MDM Catalog version

  1. In case there is a rendering problem on the SRM-MDM Search UI the version compatibility has to be checked first. To decide whether your deployed files correspond each other you have to check the version of
    •MDM Server (MDS),
    •MDM Java API (MDM_JAVA_API),
    •MDM Connector (MDM_CONNECTOR),
    •SRM-MDM Catalog UI (SRM_MDM_CAT).
    For more detailed information check SAP SCN Wiki page SRM-MDM Catalog version compatibility.

  2. Besides these rendering problems were also solved with new releases. To find out whether there is a code correction for the problem search for relevant notes. 

Basis and Browser compatibility

The supported browsers for each Basis version are to find on the SAP Product Availability Matrix (PAM). More information about Browser compatibility check the wiki page How to check browser compatibility.

Unified rendering

To avoid rendering issues the Unified Rendering should be up to date too. For more information about Unified Rendering see the wiki page Unified Rendering Notes.

Frame Settings 

The newest versions of SRM-MDM Catalog works in edge mode

Internet Explorer has three different rendering modes: Quirks, Standard (Edge) and QME.
For more information about the document modes in IE check the SAP SCN Wiki Page - Internet Explorer document modes

The note 1672817 - Browser: Microsoft Edge and Internet Explorer Support Policy Note describes the support of IE and Edge. The using of Enterprise Mode is not supported by SAP.

Creating an Httpwatch trace can show the used modes during the catalog scenario. For more information about Httpwatch trace see the Wiki Page Httpwatch trace - SRM Catalog.

  1. NWBC
    When a new window is opened by an application in IE11, the new window is opened in standards mode by default (before IE11, the new window was opened according to the parent window’s mode). If the application that is opened in the new window doesn’t support standards mode – it will be rendered incorrectly. 
    NWBC for HTML 3.5 uses the Internet Explorer 8 rendering engine by default. (NWBC for HTML 3.5 is no longer supported as of SAP_UI 753. The successor version 3.6 replaces the previous named version.) Certain applications or application types, in particular HTML5 based applications, require Internet Explorer 11 with standards mode for proper rendering. For more information see the SAP Note 1854758 - Standard Mode support for WebDynpro Java applications

    In case of NWBC the note 1898981 - Internet Explorer standards mode in NWBC for HTML and the KBA 2354559 - Internet Explorer standards mode rendering in NWBC for HTML describe how to force the standard mode for the catalog call.

    See following NWBC patch collection about the recent corrections:  SAP Note 1353538 - NWBC -Patch Collection- SERVER SIDE (ABAP)+NWBC for HTML


  2. Portal
    The supported modes depends on the portal version, it can be quirks or standard too. The notes 2400253 - Determining where to set and configure the Navigation Mode under Portal environment and 1737445 - Internet Explorer standards mode rendering for EP describe how to force the portal to open the catalog in edge mode if the portal itself is opened in quirks .
    For more information about Portal related browser compatibility check SAP SCN Blog - IE and Portal – Standards/Quirks Mode Evolution (or Love-Hate Relationships)
    More information about the maintenance of the SAP NetWeaver version can be found here:
    1648480 - Maintenance for SAP Business Suite 7 Software including SAP NetWeaver

    In case of SRM-MDM Catalog 7.0 EHP1 and EHP2 the Enhancement Switch should be activated. For more information see the note 1753440 - Activating SRM-MDM Catalog Enhancements. (After the activating J2EE restart rquired.)
    To avoid critical rendering pop-up issue also see the note 2255492 - X-UA-Compatible response header is set twice in classic framework page.

    Detailed informations are to find in the SAP note 2016845 - Using Portal with Internet Explorer in Quirks or Standards as browser document mode

Related Content

Related Documents

SAP SCN Wiki Page - SRM-MDM Catalog version compatibility
SAP SCN Wiki Page - How to check browser compatibility
SAP SCN Wiki Page - Unified Rendering Notes
SAP SCN Wiki Page - Internet Explorer Document Mode
SAP SCN Wiki Page - Httpwatch trace - SRM Catalog
SAP Documentation - SAP Product Availability Matrix (PAM)
SAP SCN Blog - IE and Portal – Standards/Quirks Mode Evolution (or Love-Hate Relationships)

Related SAP Notes/KBAs 

SAP KBA: 1898981 - Internet Explorer standards mode in NWBC for HTML

SAP KBA: 2354559 - Internet Explorer standards mode rendering in NWBC for HTML

SAP Note: 2400253 - Determining where to set and configure the Navigation Mode under Portal environment

SAP Note: 1737445 - Internet Explorer standards mode rendering for EP  

SAP KBA: 1753440 - Activating SRM-MDM Catalog Enhancements

SAP Note: 2255492 - X-UA-Compatible response header is set twice in classic framework page

SAP Note 1854758 - Standard Mode support for WebDynpro Java applications

SAP Note 2016845 - Using Portal with Internet Explorer in Quirks or Standards as browser document mode

SAP Note 1672817 - Browser: Microsoft Edge and Internet Explorer Support Policy Note

SAP Note 1353538 - NWBC -Patch Collection- SERVER SIDE (ABAP)+NWBC for HTML

SAP Note 1648480 - Maintenance for SAP Business Suite 7 Software including SAP NetWeaver