When opening a ticket

check if the error occurs as well without NWBC
- When Is an Error an NWBC Error?
  - Hint:
    NWBC as a top layer will not fix problems which do occur already on lower layers.

Quick test:

- - For instance if following content is integrated:
    - a webdynpro application:
      - Does the same error occur already if the Webdynpro is called directly/standalone (without NWBC on top)?
    - the portal:
      - Does the same error occur already if the Portal is called directly/standalone (without NWBC on top)?

- - - sap gui transactions:
      - Does the same error occur already if the sap gui transaction in the classical sap gui is called directly/standalone (without NWBC on top)?

- - - If the problem occurs in the standalone case (without NWBC) as well -> open the ticket on the respective application component.

If it turns out to be BC-FES-BUS* related- attach the following to the ticket:
- which NWBC client version do you use (7.0 or 7.70 or maybe old one)?
  - and which Patch Level of it (can be seen in the startup splash image)
    - retest with the most current PL (see Your NWBC issue may already be solved)
    - 3042824 - SAP NWBC ABAP Runtime Patch 76
- does the same issue occur as well in NWBC for html (browser only)
  - simply paste the connection URL into a plain browser
  - 1620576 - NWBC for HTML and Runtime: Prerequisites and restrictions
- attach Traces of type 2:
  - 1883689 - Possible trace types for analysing NWBC issues
    - you might be requested later for other trace types
- Step-by-step description about how to reproduce the issue:
  - Screenshots/navigation/click path
  - SID/CLIENT/URLs/USER/PW
  - open connection
    - http (Note 592085) + R/3 (Note 812732)
      - alternatively WTS (Note 605795)

mention your backend version in use - SAP_BASIS and/or SAP_UI
- check SERVER SIDE and mention your NWBC runtime level
in case of NWBC DESKTOP: