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.
After you adjusted or edited an object, you can use the User/Status function to modify the status of the object. Before doing this, you can also add other developers or testers that are allowed to edit the object, and create a short note.
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 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. |
|
|
Reset to Original |
|
Versions |
Using version management, you can compare the versions before and after the upgrade or Support Package. If you made modifications without Modification Assistant, version management allows you to recover earlier versions, if required. When versioning older releases (see below) the modification logs of objects edited with the Modification Assistant are not completely saved. Therefore, do not recover versions of such objects that 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 upgrade. Instead, reset the object in question to original. If it no longer exists, recreate it using the development environment tools. If you display the old version of the object in a separate mode, you can copy the program coding into the reset or newly created object. Versions created after the last import, for example for an enhancement, are retrieved completely. Versions of objects modified entirely without Modification Assistant are always retrieved completely. For all types of modifications the versions created after importing the following Support Packages are always completely retrieved: 4.5B SAPKH45B38 For more information see Version Management. |
|
Select 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 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 |
|
Goto ® 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. |
|
Modifications ® Delete 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. |
For more information see
Status of the Repository Objects.See also:
Reset to Original Special Features of Complete Objects
