Global User Manager

The Global User Manager provides an overview of users of the SAP system, existing user groups, roles and the systems in the system group. The system administrator can make changes in the overview using Drag&Drop. These changes take effect after being distributed to the dependent systems.

Use of the Global User Manager is not obligatory. You can still make assignments at individual user level with the existing user and role maintenance transactions.

Features

The Global User Manager gives you various grouping possibilities at user and system level for maintaining user and system assignments in a system group in the central system, in addition to the previous individual user view.

An advantage of the Global User Manager is that you do not need to consider the full complexity of the system environment when modeling authorizations. You consider only one part of the whole in each work step, two of the axes of an assignment triangle.

Source	Target
User/user group	System/System type
System/System type	Role/Composite role
Role/Composite role	User/user group

To model a complete assignment to be distributed into the target systems, you must create a closed assignment triangle as shown in the graphic. The Global User Manager reduces the complexity of this procedure so that you only need to make the two other assignments from each corner. When you have done so from all corners, the assignment is complete.

Do not distribute the user data in the Global User Manager until you have completely modeled the data for all users. Everything which is not defined in the Global User Manager is deleted in the target systems.

You cannot assign an authorization profile to users or user groups directly in the Global User Manager. The authorizations are assigned in roles. If you want to create a role automatically from an existing authorization profile, call the transaction SU25 and choose item 6: Copy data from existing profiles.

The Global User Manager Screen

The Global User Manager only runs in the central system of the central user administration.

Call the transaction SUUM to display the Global User Manager.

All users and user groups in the system group are displayed at the left-hand side of the screen. The systems and system types are displayed in the middle, and the roles and composite roles in the system group on the right.

Choose Extras ® Compare systems in the Global User Manager to display the roles and composite roles of the child systems. You can alternatively choose Compare texts in child systems in the Roles tab in the user maintenance transaction SU01. The data may not be immediately available because it is distributed asynchronously.

Using the Global User Manager

If you want to use the Global User Manager, the procedure depends on whether your system environment already contained users before the installation of the central user administration. If users already exist, you should migrate the current user master records into the Global User Manager, so that previously existing assignments are not deleted the first time you distribute user data with the Global User Manager.

System environment with existing users

To use the Global User Manager in a system environment with existing productive users:

1. Choose Extras ® Migration ® Users to get the current user master records of all systems in the Global User Manager.
2. Choose Extras ® Migration ® Roles to automatically assign the roles to the systems in which they exist, in the Global User Manager.

The data is compared with the current system status at individual user level in the Global User Manager after the migrations. To ensure that you do not lose any existing data, do not start to model user groups and system types until the migrations are finished.

Role names must be unique in the system environment. The system environment behaves like a single system, and a role can only exist once in this system. If a role with the same name exists in several systems in the system group, it appears several times in the Global User Manager role list.

You can make assignments at both individual user level and user group level in the Global User Manager. This can have unwanted effects after a user migration. Example: You have migrated all developers in your system in the Global User Manager as described above. You have then defined a user group for all developers containing the same authorizations which they had previously as individual users. When you assign all developers to the user group, the authorizations are assigned twice. So if you remove a developer from the user group, he or she still has the individual authorizations and can continue to develop. You should remove the individual user assignments after a migration as soon as you assign the users to their user groups. Use individual user assignments to give a user additional authorizations which differ from the standard authorizations of the user group.

System environment without (existing) users

If there are no active users in your system environment, you do not need to migrate the existing user master records. You can start to create new users in transaction SU01 and model the authorizations in the system environment in the Global User Manager. Each user must only be created once in the central system and can then be assigned to other systems in the Global User Manager. The Global User Manager creates the users in these systems and assigns roles to them.

Proceed as follows:

1. Create a user in the transaction SU01.



Only assign something in the System and Role tabs when it is only for this individual user. Define other authorization for user groups in the Global User Manager.

2. Enter a user group for the current user in the Groups tab, if one has already been created in the Global User Manager. You will not need to make this assignment again in the Global User Manager.

All data that you enter in SU01 is also in the Global User Manager. Conversely, all assignments made and distributed in the Global User Manager are also in SU01.

Definition on system types and user groups

Proceed as follows:

1. Create a system type/user group by choosing the appropriate pushbutton.
2. Assign systems or users to the system type/user group respectively by Drag & Drop.

A system can only be assigned to one system type. A user can belong to several user groups.

Modeling in the Global User Manager

To specify the systems and roles for a user group:

1. Mark the user group and choose Display assignments.

The current system/system type and role assignments of the selected user group are displayed. No systems or roles should be assigned to the user group yet.

2. To assign systems or system types to the user group, Drag & Drop a system or a system type to the entries under Assignments to user groups. Assign roles or composite roles to the user group similarly.

To restrict the number of entries displayed in a list (users, roles, and so on), choose the selection icon next to an entry and restrict the value range.

You have now defined two of the three sides of the above assignment triangle. This example focuses on the user group and we have so far assigned systems and roles. The axis which connects system and role is still missing. If you migrated the roles, this assignment is made automatically and the triangle is complete. If not, you must define it for each role.

You can display and change assignments from any corner of the triangle. When you display the assignments to a role you can edit the systems and user groups for this role. When you display the assignments to a system type you can define the users and roles for the systems of this system type.

Distributing data with the Global User Manager

Display and check your distribution data in a list before distributing it. Proceed as follows:

1. Choose Display distribution data.
2. Check whether the data for selected users is correctly flagged for distribution.

Only delete the user data when you have checked a sample of it in the list display.

You can distribute data from the Global User Manager immediately manually, or schedule a regular background job.

3. To distribute data immediately, choose Distribute immediately.

The data is distributed immediately. It can take a few minutes until the data reaches the target system because it is distributed asynchronously

Immediate distribution can damage the performance of your system. To avoid this, schedule a periodic background job to distribute the data, such as at night.

The data is distributed according to the modeling in the Global User Manager in the SU01 of the central system and from there to the child systems. Only the users are created and the roles assigned in the child systems. Other data is not distributed, it is retained in the central system. There is no log in the transaction SCUL.

Only changes since the last distribution are distributed. This minimizes the amount of data to be distributed.

To distribute data in a periodic background job, choose Extras ® Schedule distribution.

1. Enter a meaningful name for the background job under Job name.
2. Choose a job class to specify processing priority.
3. Choose the central system of the central user administration under Target server.
4. Choose to schedule the ABAP program RSUSR500.
5. Choose to specify when the job is to run.
6. Choose Save.

Authorizations in the CTS

This section is intended for customers with longer experience of the SAP System. If you have just installed the system, use the role maintenance transaction to maintain authorizations.

If you want to set up your own authorizations, bear in mind that in addition to the CTS authorizations, users also require the following authorizations to work with the extended view of the Transport Organizer:

• S_DATASET_AL (for accessing files)
• S_C_FUNCT_AL (for calling external programs)
• S_TCD_ALL (for calling transactions)

Since Release 4.0, the administration functions in the CTO have been safeguarded by a new authorization object called S_CTS_ADMI. The authorization object S_TRANSPRT introduced in 3.0 is now used exclusively to safeguard functions that directly change requests and tasks.

The authorizations are checked independently of the user name. User DDIC therefore does not automatically have administration rights. A user who wants to schedule the transport program (RDDIMPDP) needs administration authorization so that the program can run without errors.

The authorization object S_TRANSPRT consists of the fields Activity and Request type. The following values are used:

Activity	Description
01	Add or generate
02	Change
03	Display
05	Lock
06	Delete
23	Change/edit object list manually
43	Release
50	Change source client
60	Transport
65	Merge request
75	Release other user's requests
78	Edit transport proposal
90	Change owner

Request types	Description
CLCP	Client transports
CUST	Customizing requests
DLOC	Local change requests
DTRA	Transportable change requests
MOVE	Relocation transports
PATC	Support Packages
PIEC	Piece list
TASK	Task (repair or correction)
TRAN	Transports of copies

The authorization object S_CTS_ADMI, with safeguards administration functions, only has the field CTS_ADMFCT, whose values describe the various administration activities. Use the following values to assign the user authorization for particular administration functions.

Administration function	Description
TABL	Maintain the control tables of the Transport Organizer (for example, configure the transport routes) Schedule the transport dispatcher RDDIMPDP Call certain administration tools (Transaction SE03) Extended maintenance authorization when changing the object directory entries with the tool Change Object Directory Entries of Objects (Transaction SE03).
INIT	Initialize the Transport Organizer, for example, after a system copy
SYSC	Setting the System Change Option
PROJ	Manage projects in the Change and Transport System
INBX	Edit the TMS worklist
QTEA	Approve transports into the production system
IMPA	Import all requests in an import queue
IMPS	Import individual requests into the target system
TADM	Special transport functions in TMS
TDEL	Delete transport requests from the import queue
TADD	Forward transport requests to an import queue
TQAS	Activate or delete inactive transport requests
IMPT	Import requests into the target system using the Transport Management System (obsolete)
EPS1	Generate EPS objects
EPS2	Change EPS objects

Transport Operator

Technical name: SAP_BC_TRANSPORT_OPERATOR

Tasks

The Transport Operator is responsible for routine tasks such as imports, approving software changes, transports, tracking imports, and so on.

Activities in the Change and Transport System

The tasks of the Transport Operator include:

• Importing transport requests into systems in the transport domain
• Approving transports that are part of the transport workflow or quality assurance procedure
• Using the Alert Monitor to monitor the transport domain
• Using the import tracking functions to check transports
• Analyzing and editing the contents of transport requests.

The Transport Operator role has display authorization in the Transport Organizer and Transport Organizer tools.

Integration

Transport requests are created by the Customizing Project Administrator and the Development Project Leader. These users create tasks for the Customizing Project Members, ABAP Developers and Documentation Developers working on the project. In turn, these users record their changes in transport objects in tasks and then release the tasks. After the Customizing Project Administrator or the Development Project Leader has released it, the request is imported into other systems by the Transport Operator or Transport Administrator.

The Transport Operator supports the Transport Administrator in his or her routine tasks in the Change and Transport System (making transports, approving changes, monitoring, and so on). However, fundamental changes to the SAP Systems, such as reconfiguring the landscape, importing SAP software, creating transports, deletions, and so on, remain the responsibility of the Transport Administrator.

The Transport Administrator needs display authorization for the ABAP Workbench to be able to analyze transport objects. This authorization is in the role ABAP Developer: Display Authorization.

Transport Administrator

Technical name: SAP_BC_TRANSPORT_ADMINISTRATOR

Tasks

A user with the role Transport Administrator is a superuser of the Change and Transport System. The tasks of this user include:

• Configuration of the system landscape with the Transport Management System
• Import of new SAP software
• Routine transport tasks such as imports, approving changes, and so on.

The Transport Administrator role has all authorizations in the Change and Transport System.

Activities in the Change and Transport System

The main daily task of the Transport Administrator is importing transport requests into the systems of his or her transport domain. This includes actually importing the requests, approving transports that are part of the transport workflow or quality assurance procedures, using the Alert Monitor to monitor the transport domain, and tracking imports. The Transport Administrator has full authorization to analyze and edit transport requests in the Transport Organizer and the Transport Organizer tools.

The administrator also configures the system landscape for the Change and Transport System, including the transport domain and the transport routes. He or she sets the system and client change options.

The Transport Administrator imports new SAP software, such as Support Packages and add-ons, upgrades the system, and adjusts any modifications. Language transports are another area for which this administrator is responsible.

Note

The Transport Administrator has the Transactions STMS, SA38 and RZ20 in the LaunchPad, without which certain less frequent functions cannot be accessed. If you change the single role Transport Administrator into a composite role, and want to make the LaunchPad less complicated, you can delete these transactions from the composite role menu. This does not change the authorization to execute these transactions.

Integration

Transport requests are created by the Customizing Project Administrator and the Development Project Leader. These users create tasks for the Customizing Project Members, ABAP Developers and Documentation Developers working on the project. In turn, these users record their changes in transport objects in tasks and then release the tasks. After the Customizing Project Administrator or the Development Project Leader has released it, the request is imported into other systems by the Transport Operator or Transport Administrator.

The Transport Administrator is supported in his or her routine tasks in the Change and Transport System by the Transport Operator (making transports, approving changes, monitoring, and so on). However, fundamental changes to the SAP Systems, such as reconfiguring the landscape, importing SAP software, creating transports, deletions, and so on, remain the responsibility of the Transport Administrator.

One typical task of the Transport Administrator is to use the client copy function. All transactions and authorizations for this function are in the role Client Copy.

The Transport Administrator needs display authorization for the ABAP Workbench to be able to analyze transport objects. This authorization is in the role ABAP Developer: Display Authorization.

Authorization Concept in the CTS

All functions in the CTS are safeguarded by detailed authorization checks.

With the help of authorizations, you can specify whether a user may perform administration functions and which request types this user can edit.

SAP provides roles for the different CTS user types. Each role has the appropriate authorizations for the different CTS activities. In most cases it is sufficient to set user authorizations by assigning roles. You can use the role maintenance transaction (PFCG) to change the authorizations of roles for your own requirements, or to create new roles.

Local and Transportable Change Requests

You can access the request overview in the Transport Organizer by choosing Own requests in the request query dialog box or by choosing:

Tools ® ABAP Workbench ® Overview ® Transport Organizer

The request overview is displayed in the form of a hierarchical list and is organized according to the categories "Transportable" and/or "Local". If you only have change requests belonging to one of the categories, only this category will appear.

The configuration of the transport routes in the SAP System determines whether changes to objects during modification adjustment are recorded in a local or transportable change request. You cannot and must not change these settings during the upgrade. In all cases, the change request can still be used for automatically transferring modifications to a subsequent system. For this procedure, the change requests are not released in the normal way, but handled specially.

Do not change the configuration of the transport routes in your system group during the upgrade.

Implementation Status of SAP Note

If an SAP Note contains correction instructions, the implementation status indicates whether all the relevant correction instructions in the note have been implemented in the system.

The system sets the implementation status automatically. It can have the following values:

• Incompletely implemented

Not all the relevant correction instructions have been implemented, or some correction instructions have only been partly implemented. The objects that need to be corrected are inconsistent. You must therefore implement this SAP Note in your system again.

• Obsolete version implemented

SAP has corrected an SAP Note that contained errors. Implement this note in your system again.

• Can be implemented

The SAP Note contains correction instructions that you can implement in your system.

• Implemented completely

The corrections in the SAP Note have been implemented completely in your system. No action is required.

• Cannot be implemented

The SAP Note does not contain any correction instructions that you can implement in your system. No action is required.

• Obsolete

After you implemented the corrections in the Note, you imported a Support Package that also contains these corrections. The errors have now been removed.

Processing Status of SAP Note

The user who is processing an SAP Note specifies its processing status. This status indicates whether you have implemented the SAP Note.

You can set the following processing statuses in the Note Assistant:

• New

You have loaded the SAP Note into your system, but have not yet processed it.

• In process

A user is processing the SAP Note.

• Completed

You have followed the instructions in the SAP Note and implemented any corrections in your system. The processing of the SAP Note has now been completed.

• Not relevant

You have read the SAP Note and decided that it is not relevant, for example because it refers to a function that you do not user.

Split-Screen Editor

Use

This function displays in detail all the corrections that are contained in an include. If necessary, you can adjust the corrections to your modifications here.

Features

The split-screen editor is divided into two areas:

• On the left-hand side you see the state of the source code after the changes have been implemented. The changes are indicated in color. You can edit the source code that you see on the left-hand side.

• On the right-hand side you see deleted program parts, and corrections that the Note Assistant cannot automatically implement. These are displayed as context, delete, and insert blocks. (See also:
Technical Details on Correction Instructions)

On the left-hand side you can do the following:

• Edit manually
• Select and cut, or copy and paste blocks

To select a colored block, position the cursor on the header and choose Select.

You can also select any lines. To do so, position the cursor on the first line of the block that you want to select and choose Select. Then position the cursor on the last line and choose Select again.

• Undo changes step by step that you made in the split-screen editor by choosing Undo.
• Restore changes that you have undone by choosing Redo
• Go to the next/previous change by using the arrow keys
• Link two lines together by choosing Concatenate.

The Undo/Redo button appears in the middle of the editor if you insert or delete a block. You can use this button to undo or redo changes one at a time. Individual delete and insert blocks are substituted.

Technical Details on Correction Instructions

This section contains information on the following topics:

• The format of correction instructions
• The validity of correction instructions
• Prerequisites for correction instructions

Format

Correction instructions describe the changes that must be made to the source code of ABAP programs to correct errors. Correction instructions are located at the end of an SAP Note. You can use them to automatically correct the source code of ABAP programs, ABAP includes, function modules, method implementations, and screen flow logic.

Each change specifies the object (include, function module, and so on) and the modularization unit (FORM routine, for example). To identify the code that needs to be changed, a unique number of preceding unchanged lines is specified (context block). These are followed by the lines that need to be deleted (delete block) and then the new lines (insert block).

Correction instructions can consist of multiple context, delete and insert blocks.

When the system implements correction instructions automatically, it searches for the context blocks in the function module or include, checks whether the delete blocks follow and then replaces them with the insert block.

If the function module or include has been modified by the customer, the system sometimes cannot find the context blocks or delete blocks specified in the correction instructions, and it cannot implement all the corrections. If this is the case, you can adjust the corrections from the SAP Note to your modifications.

As of the end of 1998, correction instructions were standardized for automatic implementation. Some older SAP Notes may not be in this standardized format. In this case, the Note Assistant cannot implement the SAP Note completely automatically. However, you can edit the source code manually using the Split-Screen Editor. You must do this so that the Note Assistant can register the SAP Note in your system.

Validity

All correction instructions specify the releases and Support Package levels in which you can implement them. These release and Support Package levels are known as the validity range of the correction instructions.

For example, if Support Package 5 corrects and error in Release 4.0B, the validity range of the correction instructions is 4.0B Support Packages 1 – 4.

The Note Assistant checks this validity automatically, and only implements correction instructions if the system is consistent with the validity range specified in the SAP Note.

Prerequisites

In some cases, you can only implement correction instructions if certain other correction instructions have already been implemented. This is due to related changes made to the same part of the source code, or semantic dependencies.

These dependencies are described in the header area of the correction instructions. These dependencies (prerequisites) mean that you need to implement a sequence of SAP Notes, and not just one SAP Note.

Checking Support Packages

A Support Package contains a correction of error corrections. You can only import complete Support Packages and in a specified sequence. Each correction in a Support Package is documented in an SAP Note.

Importing a Support Package can result in the following situations:

• Correction implemented by an SAP Note and included in a Support Package (traffic light without colors)

When you import a Support Package, the system automatically checks whether you have already used SAP Notes to implement individual corrections from the Support Package in your system. In the modification adjustment function (transaction SPAU), these SAP Notes are flagged as obsolete by a gray light.

Reset the objects to their original SAP versions. You can do this in the following ways:

• Click the traffic light icon.
• Select the SAP Note number. Choose Reset to Original.

A dialog box appears. Confirm that you want to reset the correction to its original status.

If you have selected more than one correction, choose Reset All. The dialog box no longer appears.

• SAP Note implemented, but not included in Support Package (yellow traffic light icon)

The system checks whether corrections you implemented with an SAP Note have been overwritten by a Support Package that does not contain these corrections. You must implement these corrections again. In the modification adjustment function (transaction SPAU), these SAP Notes are flagged with a yellow light.

Double-click the light to implement the SAP Note again.

Your worklist also indicates that you need to implement these SAP Notes again (status inconsistent). To do this, choose Note -> Implement SAP Note.

• SAP Note implemented, although parts included in Support Package (green traffic light icon)

An SAP Note contains multiple correction instructions with different validity periods, for example. When you import the Support Package, one set of correction instructions becomes obsolete and the other remains valid. In this exception case, the SAP Note appears with a green traffic light icon.

If you click the icon, the correction instructions that are no longer relevant are reset to their original status.

• Adjustment mode for SAP Note implementation uncertain (green question mark)

After you have imported the Support Package, the adjustment modes for corrections are calculated in a background process. If this process is not started or if errors occur, a green question mark appears in front of the object in the tree display.

Double-click the question mark to restart the process. This can take a few minutes.

• Objects with your modifications and corrections from SAP Notes

If objects contain your own modifications and SAP Note corrections, you must first process the displayed corrections with the modification adjustment function (transaction SPAU), and then adjust your own modifications.

The modification adjustment in the subtree With Modification Assistant is not supported if the object is contained in corrections that have not yet been adjusted or reset to their original status.

Modifications cannot be reset to their original status with the Modification Assistant if the objects are included in corrections that have been implemented. Before you reset the modification, you must remove the correction.

The objects that are contained in the SAP Note are entered in transport requests if you adjust modifications to these objects, or if you reset them to their original status. This guarantees that they are transported into follow-up systems.

SAP Note Queue

If an SAP Note has other SAP Notes as prerequisites, the Note Assistant determines these when you implement the note and loads them into your system. The Note Assistant displays the SAP Note that you selected, and all the prerequisite SAP Notes in a dialog box: the SAP Note queue. You must implement the SAP Notes in the sequence in which they are displayed.

Before you implement the SAP Note, read the prerequisite SAP Notes carefully.

You have the following options:

• Implement multiple SAP Notes at once

If you choose this option, the system implements as many of the specified SAP Notes as possible one after the other.

The system can only implement multiple SAP Notes at once if all the corrections that are contained in the SAP Notes can be included without having to be changed. If the relevant includes contain your own modifications, the system may not be able to include certain changes.

The system always implements these SAP Notes individually so that you can adjust your modifications.

• Implement all notes individually

The system implements the specified SAP Notes individually. This means that you can see in detail which source code change belongs to which SAP Note and then modify the source code change, if necessary.

• Cancel SAP Note implementation

The system does not make changes to the source code.

Classifying SAP Notes

Use

Use this function to specify the relevance or processing status of an SAP Note.

Procedure

1. Read the SAP Note carefully and decide whether its contents apply to the situation in your system.
2. Proceed as follows:

• If the SAP Note is relevant for your situation, set its processing status to In process.

This informs other users that you are processing this SAP Note.

Follow the precise recommendations in the SAP Note. If the SAP Note contains correction instructions, implement them in your system.

• If you want to assign the SAP Note to another user, specify the name of the user.

Every action that you perform is recorded in a log file for the SAP Note. You can also enter comments there for another user, for example.

• If the SAP Note is not relevant for your situation, set its processing status to Not relevant.

This indicates to you and all other users that this SAP Note can be ignored.

Registering Manually Implemented SAP Notes

Use

If you implemented corrections contained in SAP Notes in your SAP System before you installed the Note Assistant, you can make this known to the Note Assistant retroactively. This is important since the Note Assistant cannot automatically recognize whether a correction was implemented manually in your system without using the Note Assistant.

Registration offers the following benefits:

• All the SAP Notes that have been implemented in your system are displayed in the Note Browser.

• If a manually implemented SAP Note is a prerequisite for an SAP Note that you want to implement using the Note Assistant, the Note Assistant recognizes that the prerequisite SAP Note has already been implemented and does not prompt you to implement it again.

• For future Support Packages or upgrades, the manually implemented SAP Notes are displayed during the modification adjustment in the category Notes. The system determines whether these SAP Notes have to be implemented again or reset to their original status.

Prerequisites

You have implemented SAP Notes manually without the Note Assistant.

Procedure

1. Execute report SCWN_REGISTER_NOTES with the ABAP Editor (transaction SE38).

2. On the input screen of the report, enter the numbers of the completely implemented SAP Notes that you want to register.

The report first loads the SAP Notes that you want to register into the database of your system and checks whether the SAP Notes are valid for your release and Support Package level. The system also checks whether the SAP Notes have already been registered in the Note Assistant as implemented.

The system displays the results of these checks in a list.

3. Choose Execute (F8).

To register an SAP Note as implemented, the system must enter the SAP Note together with the objects that are corrected by this SAP Note in a change request. By transporting this request you also register the SAP Notes in your follow-up systems as implemented. If you cannot enter the SAP Note and its objects in a request (because some objects are locked by other requests, for example), the system terminates registration.

Result

The system registers the valid SAP Notes that have not been implemented yet as completely implemented in your system, and automatically sets the processing status to Completed. Every SAP Note has a log entry in which the time and the user who triggered the registration are recorded. Invalid SAP Notes cannot be registered as implemented. This is not necessary since these corrections have already been imported into your system in the form of a Support Package. The processing status of these SAP Notes is automatically set to not relevant.

Activating the Note Assistant

Use

If you want to download an SAP Note with RFC, you must first activate an RFC connection.

Procedure

1. Create an RFC connection to SAPNet - R/3 Frontend, so that you can load SAP Notes.

a) To do this, call transaction OSS1. This creates a connection to client 000 of SAPNet – R/3 Frontend. This connection is currently called SAPOSS. You have to change the client to 001.

b) To do this, call transaction SM59.

c) Display the destination SAPOSS.

d) Change the logon data to client 001.

e) Save the destination.

For more information on RFC destinations, choose Help -> Application Help.

2. Directly before you use the Note Assistant for the first time, you have to specify the software components and their release data in the system.

To do this, you also require an RFC connection.

To specify the software components, choose Extras -> Get Release Data.

3. If you have already implemented SAP Notes in your system but you did not use the Note Assistant, you also have to announce to the system the SAP Notes that you implemented manually.

To do this, execute report SCWN_REGISTER_NOTES with the ABAP Editor (transaction SE38). See also: Registering Manually Implemented SAP Notes .

Loading an SAP Note

Use

You can load SAP Notes into your system from the SAP Service Marketplace or SAPNet - R/3 Frontend. You can do this using an RFC connection (upload the SAP Note) or with the file transfer method.

When you download an SAP Note, you can use the Note Assistant to load it directly into your system from SAPNet - R/3 Frontend.

If you want to upload an SAP Note, you must first download it from the SAP Service Marketplace and save it on the hard disk of your PC. You then use the Note Assistant to upload the SAP Note using a file transfer.

Prerequisites

You have created an RFC connection to SAPNet - R/3 Frontend (only for downloading SAP Notes). (See also: Activating the Note Assistant)

Procedure

Note Download

1. Specify the numbers of the SAP Notes that you want to download.

Use the selection function to load one SAP Note or a list of SAP Notes.

2. Confirm the selection.

The SAP Notes are loaded from the system into your database.

Note Upload

Note that you can only use this function in the SAP Service Marketplace.

1. Select the correct SAP Note in the SAP Service Marketplace.
2. Choose Download.

The SAP Note is downloaded as a file using the Web browser.

3. Save this file locally on your PC.
4. Use the upload function (Goto -> Upload SAP Note) to load the file into your system.

Result

After you have successfully downloaded or uploaded an SAP Note that did not previously exist in your system, the processing status of this SAP Note is set as new in the SAP Note overview.

Working with SAP Notes

If you want to use the Note Assistant to correct an error in the program, proceed as follows:

Prerequisites

You know the number of the SAP Note that contains the correction for the error.

You have created an RFC connection (for downloading SAP Notes).

You have informed the Note Assistant which SAP Notes have been implemented manually. (See also: Registering Manually Implemented SAP Notes )

Procedure

1. 
   
Load the SAP Note into your system.

When you do this, the Note Assistant checks whether the validities that are specified in the SAP Note (software component, release version, and Support Package level) correspond with those in the system. The Note Assistant indicates whether the corrections can be implemented.




Only SAP Notes that contain source code corrections ( Correction Instructions) can be implemented automatically.

2. Read the description of the SAP Note carefully.

The Note description may contain prerequisites, interactions, and references to postprocessing activities (making changes to a table, for example) that are not automatically recognized by the Note Assistant. If you do not take this information into consideration, fatal errors may occur. You must therefore read the SAP Note before you start to implement it.

3. Decide whether the SAP Note is relevant for you.
Classify the SAP Note according to the processing status.

4. 
   
Implement the corrections.
5. If postprocessing activities are specified in the SAP Note, perform them now.

5. Test whether the error has been corrected.

6. Set the processing status to Completed.
7. Release the transport request, and import the corrections into the receiving systems in your system landscape.

Adjusting Other SAP Systems

The functions described below are only active for the upgrade and not when applying patches.

If you have a production and development system, the maintenance level is first imported into the development system where quality tests are performed. After testing, it is imported into the production system or other SAP Systems.

The process of adjusting objects in the production system is the same as in the development system. If your development system and production system have the same technical status, you can use a simplified adjustment procedure.

The same technical status means that:

• Before the upgrade was imported, the development system and the production system were running on the same version of a Release

• All objects modified in the development system are the same in the production system or will be transferred there.

If your systems meet the above requirements, you need not use the transactions SPDD/SPAU to adjust the second system by hand. You can simply transport the changes made from the development system to the production system. If you do this, you are not asked to run the transactions SPDD/SPAU during the upgrade, even if objects have been modified. In this way, the time required for upgrading the production system can be reduced.

Preparing to Run Transaction SPAU

Before you begin adjustment, set the SAP System change option to "All objects (with Transport Organizer)":

1. Start transaction SE03 as user DDIC and choose Tools
® Administration ® Set system change option.
2. Select Modifiable in the Global setting dialog box.
3. Choose Continue.
4. Choose Edit
® Select all.
5. Save your entries.
6. Then log on as a normal user, since user DDIC may not perform any repairs.

When you make adjustments, keep the following in mind:

• Work under your normal user name and not as user DDIC.

• When an object is modified for the first time, a request query dialog box appears asking you to specify the change request where modifications should be recorded. Create the new change request with the function Create request. It is not important here if you want to retain the modifications for this object or if you want to reset the object to its original. When you change the next object, the system automatically uses the same change request provided the correction and transport system has been configured accordingly. The dialog box prompting you for a request is then not displayed.
  
  You should use the same request for all further changes you make in connection with transaction SPAU.
• If several developers are involved in the modification adjustment process, you can create a changeable transport request with several tasks before modification adjustment begins.
• If each developer creates his or her own transport request during modification adjustment, these requests must be consolidated into a single request. This single request which contains all modification adjustment objects can be selected for transport to subsequent systems.

Selection Screen of Transaction SPAU

After you call transaction SPAU, the following selection screen helps you to decide whether to display all or only specific objects to be adjusted.

You can enter the name of one or several system users who last modified the object in the selection fields. It is also possible to select one or several transport requests which were last used to process the object. A developer's task number cannot be selected here.

If the object was subsequently modified by several developers, the tree display only shows the user who last changed the object and the transport request used last. Certain transport objects such as function modules, report sources and screens can consist of several modularization units (FORM routines, PAI and PBO modules, interfaces, and so on). These units may have been last changed by different users or last used by different transport requests. The transport object is always shown in the tree display if at least one of these user names or request numbers has been selected on the selection screen.

Another selection criterion are one or several packages which are determined through the object catalog entry of the complete object (such as the function group for function modules).

In the Request/task field, you can enter any transport request or a work breakdown structure BOM. Then all objects of this request are displayed in the tree. Objects processed at a later time in other transport requests are not displayed if the same request number is entered in the Last transport request field.

The Modifications and Reset Objects tabs contain a number of checkboxes. You can use them to determine which subtrees to display. The fewer checkboxes you select, the faster the tree is set up initially when you call the transaction.

The Note Corrections category is only available with the add-on SAP Note Assistant. Transaction SPAU merely displays a notes list since modification adjustment always affects all objects involved in the note correction. In the Modification Browser (transaction SE95), you can expand a subtree below each note which contains the objects involved in the note correction.

The Without Modification Assistant category displays objects that were modified in the current SAP System before upgrade from a Release prior to 4.5A to Release 4.5A or higher. This category also displays all Repository objects from those areas in the SAP standard where modifications are not supported by the Modification Assistant.

In the Translations tree, all modifications made to translations are logged.

The Business Add-Ins and Appends categories are only available in the Modification Browser (SE95). These customer enhancements are retained during a release upgrade.

Migration objects are only displayed in the modification adjustment transaction (SPAU) After match code objects for tables, structures, views, and search helps have been migrated, the new objects created are displayed in the tree. The Customer Enhancements (SMOD) part is listed in the Migration Objects category if converted by SAP into a corresponding Business Add-In definition. The associated CMOD part is converted into a Business Add-In implementation during modification adjustment.

If you reset note corrections to original, the note numbers with the associated objects are displayed in the Reset Objects category. Note corrections that have become obsolete after the import of the Support Package are displayed in a separate subtree. When you reset modifications with Modification Assistant and without Modification Assistant to original, the system writes a log entry for the complete transport object. The details of previous modifications are no longer available. Translations and migration objects which are reset to original are listed in a category of their own.

The Adjustment Filter tab is only displayed in the modification adjustment transaction. Objects that still need to be adjusted can be shown in the tree with a black, green, yellow, or red traffic light. These symbols mean obsolete notes, automatic, semi-automatic, or manual adjustment mode. By selecting the corresponding fields, you restrict the object display to specific adjustment modes. If you select the Objects already adjusted option, objects are displayed with a green checkmark or a stop sign.

The display is normally structured by the modification type (note corrections, modifications with and without Modification Assistant, and so on) and the object type (programs, function groups, and so on).

On the Display Options tab, you can use various radio buttons to choose another display format. In the first hierarchy level, the system displays all names of the persons who last changed the objects, all last transport requests or all packages.

You can create a selection variant for this screen by choosing Goto ® Variants® Save as Variant. The next time you call transaction SPAU, your selection options are then automatically set which allows you to skip the selection screen.

Transaction SPAU: General Functions

Transaction SPAU allows you to process Repository objects needing adjustment. An overview shows all objects that have been modified by you, SAP, an IBU or an SAP partner.

For information on the selection of options on the selection screen in transaction SPAU, see Selection Screen of Transaction SPAU.

You can display modified objects in transaction SPAU by double-clicking them.

In addition to the common functions for displaying the structure tree, such as Expand/Collapse subtree, and so on, other functions are available for modification adjustments that are explained in more detail below:

	With Select subtree you can select several objects or a subtree and simultaneously change the status of several objects. Selecting multiple objects is only supported for the Adjust modifications, Reset to original, Delete from display, and Delete modification logs functions.
	With Update list you remove objects that were reset to original from the display. Tree nodes that list only adjusted objects are highlighted in color.
	With Filter, you can call the selection screen of transaction SPAU again. This makes sense if the node No object with selected filter settings found appears in the tree display. If this is the case, choose the basic settings on the selection screen so that all objects are displayed.
	With No. of log entries, you get an overview of how many objects have been modified and how many objects need to be adjusted. The system displays a list with the number of log entries that are below a tree node. The number of log entries shown in transaction SPAU, the modification adjustment status, and the adjustment mode are displayed separately. The number of log entries can exceed the number of the objects displayed in the tree. This is the case since for one transport object, several log entries can exist for each modularization unit. They are grouped together for the tree display and are represented as a single object. The name of the user that has made the last change, and the associated transport request are displayed.
	With Color legend, you can display explanatory information on the colors used in the tree structure. Depending on their status, the objects are highlighted in different colors.

The application toolbar provides common functions of the ABAP development environment: Display, Change, Check, Activate, Test and Where-Used List.

	You can display a changed object by double-clicking it or by choosing Object ® Display from the menu.
	All modified objects can be further edited using the Object ® Change function. This does, however, not apply to modifications made with the Modification Assistant and to objects in note corrections which have not yet been adjusted. In these cases, you must first perform the release upgrade adjustment.
	The Object ® Check menu provides the Check object and Extended program check functions. After you have adjusted objects or reset them to original, you should check the syntax of these objects. The system quickly finds inconsistencies and consequently avoids runtime errors. The Extended program check function can only be used for programs and function groups.
	Modified objects are saved as inactive versions initially if the object types are linked to the active/inactive procedure. If you choose Activate, you see the entire worklist of your inactive objects and can then activate them.

The following icons indicate the status of the individual Repository objects:

	Automatic adjustment This icon only appears in the With Modification Assistant category in most cases. The modification of the customer can be adopted automatically for these objects. Clicking on the icon causes the system to automatically adjust the object. In the following case which occurs rather rarely note corrections appear with a green traffic light symbol: A note contains several correction instructions with different validity periods, for example. When a Support Package is imported, one correction instruction becomes obsolete, while others remain valid. You can select a subtree or several objects, or you can place the cursor on a single object. The adjustment log tells you which modifications were adopted.
	Semi-automatic adjustment If only a semi-automatic adjustment is possible for modifications made with the Modification Assistant, a yellow traffic light symbol appears before the object. Semi-automatic means that the individual tools offer adjustment support. When adjusting programs, the split-screen editor is called, whereas in the other tools any entries made in the collision dialog box lead to the necessary adjustments being made automatically. Also read the information provided in the following sections. The system might display note corrections with a yellow traffic light symbol during modification adjustment (transaction SPAU). The correction implemented previously based on a note was overwritten by a Support Package that does not contain these corrections. Note implementation is restarted if you click the yellow traffic light. When adjusting Repository objects in transaction SPAU, semi-automatic adjustment is only available for the categories Note Corrections and With Modification Assistant. The yellow traffic light is also used for adjusting Dictionary objects in transaction SPDD. When you click the traffic light symbol, the system executes special reports that support the adoption of the modifications. Customer enhancements for Business Add-Ins (CMOD) are also migrated in transaction SPAU. The enhancement objects concerned are displayed in the Migration objects category with a yellow traffic light.
	Manual adjustment Objects in the Without Modification Assistant subtree can only be post-processed manually after the adjustment process. Manual adjustment means that you must make modifications without any special support from the system. Using Version Management, you can retrieve old versions or use your recordings to process the newly imported objects. In exceptional cases, the red traffic light may also appear in the With Modification Assistant category if the tools of the Modification Assistant are unable to fully support the adjustment process. In these cases, you should always check the adjustment log.
	This icon only appears in the Note Corrections category. If a dark traffic light is displayed for note corrections, the associated correction instructions are obsolete. The correction is contained in the upgrade or in the Support Package imported. When you click the traffic light symbol or choose the Reset to original function, a dialog box appears. Confirm that you want to reset the note correction to original. If you have selected more than one note correction, you can choose Reset all. The dialog box is not displayed then.
	This symbol indicates that the modification adjustment has not yet been completed by the first developer who edited the object. If required, a second developer must postedit the object. You can display the adjustment log by clicking the corresponding symbol. Having left the display screen, the system asks you if you want to replace the stop sign or the symbol for the incomplete adjustment of a note correction with the green checkmark. This function is not yet implemented.
	Unknown adjustment mode The adjustment mode (manual, semi-automatic, automatic, obsolete note) for this object could not be determined for modification adjustment with the Modification Assistant or for the adjustment of note corrections. The adjustment modes are determined in phase SPAUINFO during an upgrade and in phase RUN_SPAU_? during the import of a Support Package. The report SAPRUPGM is executed in the background. Since the calculation process may last several minutes, you should regularly refresh the tree display in transaction SPAU and wait until the green question marks are replaced by traffic light symbols. After the adjustment modes are determined, green or yellow traffic light symbols are displayed before the objects modified with the Modification Assistant. In rare cases, a red traffic light might appear. The background process does not only determine the adjustment modes but also makes the following reassignments: The modification logs of function modules are assigned to a different function group if the respective function module was delivered in the new function group. Modularization units (FORM routines, PAI and PBO modules, and so on) can be in a different include after the upgrade or Support Package import. The modification logs must then be reassigned to this new include. New function modules created by the customer are marked as modified if they are redelivered with the upgrade or Support Package. When you click the traffic light symbol, they are recreated in the system or modified. When you choose the Reset to original function, the new function module created is only retained if included in the upgrade or Support Package. If the new function module created is not contained in the delivery of the function group, it is deleted when reset to original. Note corrections are displayed with a yellow or grey traffic light rather than with a green traffic light. The system determines all objects which do no longer exist but for which modification logs were written. They are marked with a delete flag and displayed in the tree in the Deleted objects category. What to do if errors occur: If you still see the question marks after some time, it may be the case that the system was unable to start the background process or that the process terminated with an error. Check the status of the background process by choosing Tools ® CCMS ® Jobs ® Maintenance (transaction SM37), and display the spool list of the process for determining the adjustment modes or SAPRUPGM. The report SAPRUPGM displays a log in list format. This list contains the number of the note correction or the name of the transport object such as LIMU REPS LSEMMF07, followed by the adjustment mode determined or any errors that might have occurred. The automatic adjustment mode corresponds to a green traffic light in the tree display of transaction SPAU. The semi-automatic and the manual adjustment modes are indicated by a yellow and a red traffic light symbol. Obsolete note corrections are preceded by a grey traffic light symbol. If the report SAPRUPGM determines an automatic or a semi-automatic/manual adjustment mode and no traffic light is shown in the tree display, the function modules that define the adjustment mode for the individual tools (ABAP Editor, Screen Painter, Menu Painter, and so on) possibly contain an error. Note 190359 SPAU adjustment mode cannot be completely determined might be helpful here. Check if detailed modification logs exist for the objects concerned. To do this, choose Display Differences in the Utilities menu. By clicking the green question mark you can restart the background process manually. You can also execute report SAPRUPGM directly. At the beginning of the report SAPRUPGM, a lock is set on program SAPRUPGM to ensure that no other user can execute the report. This lock is removed when processing is finished. If you find that the lock is still set, you must remove it manually. To do this, choose Tools ® Administration ® Monitor ® Lock entries (transaction SM12). If function modules created by the customer or program sources reassigned are reset to original, the object might be deleted unintentionally. For more information, see the notes 333639 SPAU: Object deleted after reset original, 385770 Function module is deleted after SPAU (1) and 396327 Function modules deleted after SPAU (2). Note: Do not retrieve versions of objects edited with the Modification Assistant or in note corrections. Use version management only for displaying and comparing versions. See below under Version Management.
	Object adjusted After the adjustment has taken place, the traffic light symbols are replaced with either a green checkmark or a stop sign. For objects supported by the Modification Assistant, you can display the adjustment log by clicking the checkmark or choosing the pushbutton. Important note: Check the upgrade log every time you adjust objects edited with the Modification Assistant. Perform a syntax check for the main program. The green checkmark may appear also if you need to postedit the object manually.
	Adjustment problems If not all objects in the With Modification Assistant category can be successfully adjusted, then a dialog box is displayed informing you that unresolved problems still exist. The stop sign indicates adjustment problems. In most cases, you must solve these problems manually. You can display the log by clicking the stop sign or choosing the pushbutton. This function informs you what problems occurred at upgrade and what actions are necessary to correct them. Pay special attention to the Open (unresolved) problems category. A dialog box appears after the log display. The stop sign might be replaced by a green checkmark.

Reset to Original

The Reset to original function is supported in the Modification Browser and modification adjustment transaction for almost all objects. Exceptions are Business Add-Ins (Impl.) and Appends. These are customer enhancements which can only be reset in the respective tool.

The original is the version that was last imported into the SAP System during an upgrade or the application of a Support Package. The object is not necessarily an SAP standard object. It can also be an object created or modified by an IBU or an SAP partner which is displayed in the Modification Browser (transaction SE95). The customer or SAP partner can make modifications to these objects.

For the Reset to original function, you can select a subtree or several objects, or you can place the cursor on a single object.

In case of modifications, when an object is reset to original, system behaviour depends on whether the object was edited with the Modification Assistant and whether it was already adjusted in SPAU.

Modifications with Modification Assistant

If the object has not yet been adjusted in transaction SPAU, a traffic light appears before it. The Modification Browser highlights such objects in color. When an object is reset to original, the active version in the database is confirmed as the new original version. The object remains unchanged. Only the modification information is deleted. During modification adjustment, the version imported with the upgrade or a Support Package is saved as the original in the modification logs. The modifications adopted during the adjustment are added. The Modification Browser (transaction SE95) provides an overview of these modifications.

When the object is adjusted, it is displayed with a green checkmark or a stop sign in transaction SPAU. If an adjusted object is reset to original, the active version is replaced with the original version saved in the modification logs. Modifications made with the help of the Modification Assistant are lost when an object is reset to original.

Modifications Without Modification Assistant, Translations, Migration Objects

If the object is displayed in the Without Modification Assistant, Translations or Migration Objects category in the tree, the active version becomes the original version when you reset the object to original. Irrespective of whether the object has been adjusted or not, the modification log is deleted. The object itself remains unchanged. If the object has already been adjusted, the system displays a warning. The original version of this object then no longer exists, which makes it differ from those objects supported by the Modification Assistant. The modified active version is confirmed as the original version.

Modification Adjustment During the Next Upgrade or Support Package Import

Having been reset to original, the objects are removed from the tree display of the Modification Browser (transaction SE95) and the modification adjustment transaction (transaction SPAU). During a subsequent upgrade or the import of a Support Package, these objects can be overwritten by a new original version and then no longer appear in the modification adjustment.

What About a Transport Request When Resetting Objects to Original?

You must enter a transport request when resetting objects to original. The transport request is necessary to ensure that the modification information for an object is available throughout the entire transport process of the customer. However, this means also that an object that was reset to original must be transported into all subsequent systems. In the case of a consolidation transport (transport type K) or a transport of copies (transport type T), the information that the object has not been modified is included in the transport. In the subsequent system, the object is treated as an unmodified object during the next Support Package import or upgrade although it is contained in a request. The object is overwritten and no longer available for adjustment in transaction SPAU. The old status of the object is not saved.

Version Management

You can use version management to compare the versions existing before and after an upgrade or Support Package import. For modifications made without the Modification Assistant, you can retrieve older versions if required.

Note: When you manage versions in older releases (see below), the modification logs of objects edited with the Modification Assistant are not saved completely. Do not retrieve versions of these objects which were generated during or before the last import. Since the modification logs would be inconsistent, data could be lost during the next Support Package import or the next upgrade.

Reset the object to original instead. If it does no longer exist, recreate it using the tools of the development environment. If you display the old version of the object in a separate session, you can copy the program code to the object reset or recreated.

Versions created after the last import, for example, in the context of development projects, are retrieved completely.

Versions of objects modified only without the Modification Assistant are always retrieved incompletely.

For all modification types, versions created after the import of the following Support Packages are always retrieved completely:

Release	Support Package
4.5B	SAPKH45B38
4.6B	SAPKB46B25
4.6C	SAPKB46C15
4.6D	SAPKB46D05

For more information, see Version Management.

Selecting for Transport

The Select for transport function helps you to adjust other SAP Systems. In this case, do not use the transport release function in the Workbench Organizer. If you choose the Select for transport function, the adjustment process needs not be executed again in the subsequent systems (for example, the production system).

Create only one transport request that you use to record all modifications.

If you have created several transport requests already, you must consolidate your object lists into one request. For example, if you have adjusted different objects in your development and your consolidation system, you must add the objects to a common transport request to include it in the adjustment process of the production system. For more information, see Choosing a Change Request to Transfer Modification Adjustments to Other SAP Systems.

To automatically transfer modification adjustments to subsequent systems, choose Select for transport after releasing the tasks for the request. When an upgrade is carried out for the subsequent system, the marked transport is imported. A new adjustment is not necessary. For detailed information on transporting adjusted objects, see the following sections:

Handling Change Requests During Modification Adjustment

Choosing a Change Request for Modifications

Local and Transportable Change Requests

Releasing Tasks at the End of Modification Adjustment

Choosing a Change Request to Transfer Modification Adjustments to Other SAP Systems

Deleted Objects

Display outside the tree

If you choose Goto, you get a list of the deleted objects. Alternatively, you can directly execute the report RS_SMODILOG_FIND_DEL_OBJ. It may take several minutes to find the objects.

The report RS_SMODILOG_FIND_DEL_OBJ displays the deleted subobjects (LIMU) and the higher-level complete objects with a separate object catalog (R3TR), for which only the modification logs exist. These objects were modified by the customer and deleted during an upgrade or the import of a Support Package.

Double-clicking a subobject in a line of the list takes you to version management. You can retrieve an old version of the subobject from the version database.

You can select some or all objects in the list and delete their modification logs.

Display within the tree

When the report SAPRUPGM is executed, the deleted objects are determined in the system. The report SAPRUPGM is started automatically in the background after each upgrade or Support Package import.

The deleted objects are displayed in the Modification Browser in the Deleted Objects category. In the tree display, you can select one or all objects of this subtree and delete the modification logs. You can find the corresponding function in the Utilities menu. If the object persists due to an error, you must confirm in a dialog box that you want to delete this object.

Special Aspects of Complete Objects

If new complete objects (programs, function groups, and so on) are created, the transport object is added to the transport request. If function modules are deleted or view maintenance modules are generated, the associated function group is added to the transport request.

In these cases, the Created / Generated node in the modification adjustment is displayed below the associated complete object. If an upgrade is performed or a Support Package is imported, the system may display the Created / Generated node in transaction SPAU with a red traffic light. This is also the case if only a subobject (source code, screen, and so on) or the associated object catalog entry has been imported. Double-clicking the tree node displays a dialog box containing recommendations.

Check in the Modification Browser if other modified subobjects exist for the complete object (function group, program, logical database, and so on) besides the Created / Generated node. To do this, browse through the subtrees With Modification Assistant and Without Modification Assistant.

Check to which degree you have to accept your modifications. If your new object was overwritten, create it again with another name.

If you want the complete object to remain being marked as a modified object in the Modification Browser, click the red traffic light in transaction SPAU and choose the Adjusted pushbutton.

If you do not want to accept any modifications, or if you have created the complete object with a new name or have restored the modifications in the subobjects of the complete object, set the Created / Generated node in SPAU back to original.

Removing Adjusted Objects From Display

Before you exit transaction SPAU, you should choose Modifications ® Delete from display to remove all objects from display for which modification adjustment is complete. To do this, you can select a subtree or several objects, or you can place the cursor on a single object.