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 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:
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 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 A dialog box appears after the log display. The stop sign might be replaced by a green checkmark. |
pushbutton. 
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.
1 comment:
Oh man! This blog is sick! How did you make it look like this !
P0wer bi onlinetraining from india
P0wer bi onlinetraining
Post a Comment