Skip to end of metadata
Go to start of metadata

SAP Screen Personas


Re-implementing the Basis Enablement Note



The SAP Screen Personas 3.0 Basis enablement notes are changing the core classes of the basis that are critical for the rendering of DYNPRO screens. As result, any inconsistent state of these classes can crash your system. Implementing the notes is a straight forward process that has no known issues, however, if for any reason you need to re-implement the note, then you need to be extremely careful. This document is intended to help you through the process.


This document guides you through the process of cleanly de-implementing and then re-implementing an SAP Screen Personas 3.0 Basis enablement note if required. Possible reasons are: (1) an older version of the note is currently implemented or (2) a critical step of the Pre- and post-installation Checklist has been forgotten.


As mentioned in the beginning of the document, when executing the steps below, critical Netweaver classes are modified, therefore it is extremely important that every step is executed carefully. If at any point in time, the SAP system notifies you that the next step e.g. activating an object will cause problems, then please STOP right away. In addition, I would strongly recommend to have a backup that can be restored if something goes wrong.  

Resetting the note / undoing the changes

Do NOT reset the note with SNOTE because SNOTE will undo and activate the changes step by step which causes a system crash when doing it with the basis enablement note. To properly undo all changes, you need to manually revert all objects to the last version before implementing the note and then activate them all together.

1 - Find all changed classes and reports

The objects differ between the notes for SP3 and SP4+ as well as the version of the SP4+ note that has been implemented but it should always be a subset of

    • CL_GUI_FW

    • CL_GUI_DATAMANAGER============CL (local classes of CL_GUI_DATAMANAGER)



To find the objects modified by your note implementation, please open the transport organizer SE01 and find the transport containing the implementation of the note. It should look like the image below.

2 - Reverting the changes

Next you have to go through each class/report one by one. First, double click the report/class/method that opens the class builder or the ABAP editor. Then go to the main menu: Utilities->Versions->Version Management->Public Section. Now you should see the available versions and it should look like the image below. Please select the last version before the note implementation and click on Retrieve.

Since you are editing a class shipped by SAP it will ask you to register the change and you have to retrieve the key from the Support Portal with your S-User.

You should see now a new modified version. To verify that it is the correct code, select it as well as the last version before the note release and click on Compare. You should see a screen indicating that there are no differences.

Finally repeat these steps for the Protected and Private Section of the same class and for all other classes, methods and programs.

3 - Activating the new (old) version

Next, open SE80 (if not already open) and show all inactive objects for your user. Select all and click on activate. You should see all changes that you did in the last step and a check is executed. If a problem is found then you will be notified and you should CANCEL and NOT activate the changes. Go back to step 2 and check if you forgot a class, method or report. If everything is good, the changes are activated and you have to wait. This might take a moment because sources referencing your changed code will be recompiled.

4 - Implementing the note again

As the last step, please open SNOTE and download the latest version of note 2044643 (which is 10). If possible select the note and click on 'Implement SAP Note'. It might happen that SNOTE shows that the note is already implemented, but the moment you click 'Implement SAP Note' it will switch its status and allow implementing it. If all went well then you should see something like the image below:

Related Content

Related Search Terms:

SAP Screen Personas, SNOTE, Basis, Note, Problem

Related SAP Notes/KBAs





Important News

This knowledge base is not solely SAP provided content - but community driven. Please also check on SMP and for SAP released information and notes on SAP Screen Personas.

Create New Article

Compare SAP Screen Personas versions

Search the KB

How to Open OSS Message

 What information is needed for creating OSS message?

  1. Make Sure you are on the latest patches and notes.
  2. Kernel Patch Level
  3. Two Types of connections to your environment: HTTP and R/3
  4. All the connections should be tested with proper credentials provided
  5. Steps to re-create the issue
  6. Attach related logs
  7. File tickets against BC_PER