FAQ's: Modification Adjustment
Selection screen
[1] What is the difference between the 'Last transport request' and 'Request/task' input fields?
[2] Why do the modification browser (transaction SE95) or the modification adjustment (transaction SPAU) display an object with the last person who has changed the object or the last change request although other selection conditions were entered in the initial screen?
Modification adjustment
[3] Why do the SE95 and SPAU transactions display such a large number of objects after upgrading from a Release before Release 4.5A to a Release 4.5A or higher?
[4] Why does the SPAU transaction display objects with a question mark?
[5] Can I save the transferred changes in the modification adjustment so that another developer can transfer more changes?
[6] Do I HAVE to perform a modification adjustment after each upgrade or Support Package import?
[7] When do I have to import the SPAU adjustment transport of a development system into the consolidation or production system?
[8] Can I retrieve versions in the modification adjustment or for resetting to original?
[9] How do I proceed if versions of modifications with Modification Assistant were, nevertheless, retrieved?
[10] How can I mark the objects of an advance development in the system so that they are included in the adjustment when the next upgrade or Support Package is imported?
[11] Why does the SPAU transaction display Dictionary objects?
[12] How can I quickly delete objects from the SPAU and SE95 transactions?
[13] Does the system change the active object when resetting to original?
Resetting to original
[14] How can I display objects that were reset to original?
[15] Why was the 'Return to SAP standard' function replaced by 'Reset to original'?
[16] Why does the system have to be changeable for resetting to original?
[17] Why does the system request a transport request when resetting to original?
SPAU and note corrections
[18] Which are the advantages of the Note Assistant?
[19] Can I also install the Note Assistant in a system with a large number of modifications?
[20] Which requirements must be met for installting the Note Assistant?
[21 ] How do I know which notes are using an object?
[22] Why can I not reset to original a note correction with a yellow or green traffic light symbol in the SPAU transaction?
[23] Why can I not reset a modification with Modification Assistant to original if the object is contained in a note correction?
[24] Why can I not adjust a modification in the SPAU transaction if the object is contained in a note correction?
Tips and tricks
[25] Where do I find documentation for the SE95_UTIL transaction?
[26] Which checks should I perform if problems occur?
[27] How can I display the change history of an object?
[28] How can I display the developers who have modified an object?
[29 ] How can I display the requests in which the object was edited or imported?
[30] Which versions should I compare if a problem occurs in the modification adjustment?
[31] What do I have to bear in mind when comparing versions in the version management?
[32] What is important when comparing modification versions?
[33] Which information can I obtain from the transport logs?
[34] In which components should I open a message if problems occur?
[35] Which Notes contain release-dependent information?
Selection screen
[1] What is the difference between the 'Last transport request' and 'Request/task' input fields?
Answer:
In the upper part of the selection screen, you can , for example, enter the last person who has changed an object, the number of a transport request or the Package/development class. If you enter the number of the request in the 'Last transport request' field, the system only displays the objects of the request that were not changed again in later requests. If you enter the number of the request in the 'Request/task' field, the system displays all modified objects of the object list (the 'Request/task' input field is only available as of Release 4.6D and with the SAP Note Assistant). Are the checkboxes on all tab pages of the selection screen active at the same time or only the checkboxes on the active tab page?
The selected fields on all tab pages are active at the same time, regardless of which tab page is the active tab page.
[2] Why do the modification browser (transaction SE95) or the modification adjustment (transaction SPAU) display an object with the last person who has changed the object or the last change request although other selection conditions were entered in the initial screen?
Answer:
If the object was modified by several developers in a row, the hierarchy display only displays the name of the last person who has changed the object and the transport request used last. Certain transport objects, for example, function modules, report sources and screens, can consist of various modularization units (FORM routines, PAI and PBO modules, interfaces, and so on). These units may have been changed last by different persons or may have different transport requests used last. The transport object with the name of the last person who has changed the object and the transport request used last is always displayed in the hierarchy display if one of the user names or request numbers was selected in the selection screen.
See also:
Note 309315: SPAU/SE95 display more objects than were selected
Modification adjustment
[3] Why do the SE95 and SPAU transactions display such a large number of objects after upgrading from a Release before Release 4.5A to a Release 4.5A or higher?
Answer:
The modification adjustment (SPAU) was changed for the upgrade of releases before Release 4.5A to a Release 4.5A or higher. During the upgrade, the system adds all objects to the modification browser display (SE95) that were modified in customer requests. General objects with their own object directory entries (R3TR) are broken down into all existing subobjects (LIMU).
When the upgrade or Support Package is imported, a subset of the modified objects is provided for the modification adjustment in the SPAU transaction. These are the objects that were reimported with the upgrade or the Support Package.
[4] Why does the SPAU transaction display objects with a question mark?
Answer:
If the SPAU transaction displays objects with question mark, the comparison mode (automatic, semiautomatic, obsolete note, manual) is still undetermined.
A dialog box is displayed in the initial screen of the SPAU transaction or when clicking on the question mark. In the dialog, you can start the 'Specify comparison modes' background process.
In the background process, the SAPRUPGM report determines the comparison modes (automatic, semiautomatic, manual) for the objects. They correspond to the green, yellow or red traffic light symbols in the hierarchy display.
If the question marks are still displayed after the hierarchy display was updated, you should restart the 'Specify comparison modes' background process and wait for a little while. If the question marks are still displayed, you should check the status of the background process. Do do this, select the Tools -> CCMS -> Jobs -> Maintenance (SM37) transaction and display the spool list of the process.
Follow the instructions in note 209331, SPAU: Undetermined comparison mode.
Note: If the comparison mode is determined for at least one modularization unit of a transport object but not for another, the system issues a 'Manual' comparison mode and displays a red traffic light.
[5] Can I save the transferred changes in the modification adjustment so that another developer can transfer more changes?
Answer:
As of Release 6.10, you can save an intermediate status. All changes that can be executed automatically are transferred. This also includes the changes of other developers. The changes are saved in the splitscreen editor. After saving, the system displays a dialog box asking the user if all changes were made. Answer the question with 'No' if you want another developer to continue transferring the changes. Select 'Back' and confirm the saved intermediate status in the subsequent dialog box. The program will still be displayed in the SPAU transaction with an 'Intermediate status saved' symbol.
[6] Do I HAVE to perform a modification adjustment after each upgrade or Support Package import?
Answer:
You MUST compare Dictionary objects in the SPDD transaction to avoid possible loss of data. You do NOT have to compare the Repository objects in the SPAU transaction, but should do so as soon as possible. Objects to be adjusted should no longer be displayed in the SPAU transaction when the next Support Package or upgrade is imported.
[7] When do I have to import the SPAU adjustment transport of a development system into the consolidation or production system?
Answer:
The sequence of the imported upgrades or Support Packages should be identical in all systems. The adjustment transport should be imported into the target system at the time when it is exported from the source system.
[8] Can I retrieve versions in the modification adjustment or for resetting to original?
Answer:
You can retrieve previous versions for object types that were changed without the Modification Assistant.
You should not retrieve versions for objects that were changed with the Modification Assistant as inconsistencies may occur.
[9] How do I proceed if versions of modifications with Modification Assistant were, nevertheless, retrieved?
Answer:
Use a temporary version.
Reset the object to original.
Implement the changes manually by comparing them with the temporary version.
[10] How can I mark the objects of an advance development in the system so that they are included in the adjustment when the next upgrade or Support Package is imported?
Answer:
The SE95_UTIL transaction provides a utility which you can use, for example, to mark the prototypes of an advance development in the customer system.
If you want to add or update modification logs, you must enter the number of the transport request. In the third line of the selection conditions, you can exclude the objects whose originals are in a certain system. This may be, for example, your development system.
In the initial screen, you also set the new values for the log entries: the number of the last transport request, the name of last person who has changed the object and the date of the last change. You may choose the values randomly.
The objects of the transport request are displayed in the modification browser under 'Without Modification Assistant'. After the upgrade or Support Package was imported, the objects may be included in the adjustment in the SPAU transaction.
[11] Why does the SPAU transaction display Dictionary objects?
Answer:
During the ACT_<REL> (upgrade) or RUN_SPDD_? (Support Package) phases, Dictionary objects are displayed both in the SPDD and the SPAU transactions. You should, however, only adjust Dictionary objects in the SPDD transaction. If you do not adjust Dictionary objects during the ACT_REL or RUN_SPDD_? phases, data may be lost.
Once the adjustment in the SPDD transaction is complete, Dictionary objects (domains, data elements, tables, and so on) may be displayed in the 'Without Modification Assistant' subtree in the SPAU transaction. Here, you can reset the Dictionary objects to original. This does not change the object. The system merely deletes the log entry.
[12] How can I quickly delete objects from the SPAU and SE95 transactions?
Answer:
You can select the subtree under 'Without Modification Assistant' and choose the 'Reset to original' function. Using the SE95_UTIL transaction, you can delete the modification logs for modifications without Modification Assistant.
[13] Does the system change the active object when resetting to original?
Answer:
The modification behavior when resetting to original depends on the fact if the object was changed with Modification Assistant or without and if the object was already adjusted in the SPAU transaction.
- Modifications with Modification Assistant:
If the object was not yet adjusted in the SPAU transaction, the system displays a traffic light in front of the object. In the modification browser, these objects are highlighted with different colors. When resetting to original, the system confirms the active database version as new original version. The object remains unchanged. The system merely deletes the modification information.
If the object is adjusted, the system displays a green checkmark or a stop sign in front of the object in the SPAU transaction. If an adjusted object is reset to original, the active version is replaced by the original version saved in the modification logs. The modifications made with the Modification Assistant are lost when the object is reset to original.
- Modifications without Modification Assistant:
If the object is displayed in the hierarchy under 'Without Modification Assistant, translations or migration objects', the active version always becomes the original version when resetting to original. Regardless if the object was already adjusted or not, the system only deletes the modification log. The object itself remains unchanged. If the object is already adjusted, the system displays a warning. Unlike objects supported by the Modification Assistant, the original version no longer exists. The modified active version is confirmed as original version.
Resetting to original
[14] How can I display objects that were reset to original?
Answer:
As of Release 6.10 (with the delivery of the SAP Note Assistant), you can select in the selection screen if reset objects are to be displayed. (The system, however, only displays objects that were reset to original after the installation of the SAP Note Assistant).
In releases before Release 6.10 without installed SAP Note Assistant, you can display adjusted objects using the SE95_UTIL transaction.
[15] Why was the 'Return to SAP standard' function replaced by 'Reset to original'?
Answer:
As the delivery of the software does not assume a two-level (SAP, customer) but a multilevel (SAP, country versions, IS solutions, partner, customer, and so on) system infrastructure, 'Reset to original' is a more appropriate name. Each level of the system infrastructure may contain an original that can be modified.
[16] Why does the system have to be changeable for resetting to original?
Answer:
Even if the actual sources remain unchanged, the system changes the modification logs when resetting to original. The system must, therefore, be changeable for at least a short time so that the objects can be reset to original. You can also reset the objects to original in another system of the development landscape and import them with a transport request.
[17] Why does the system request a transport request when resetting to original?
Answer:
As of Release 4.5, the system requests a transport request when resetting to original. The transport request is necessary because the modification information for an object is to be available in the entire customer transport track. This also means that an object that was reset to original must be transported into subsequent systems. In a consolidation transport (transport category: K) or in a transport of copies (transport category: T), the system transports the information that the object was not modified together with the object. In the subsequent system, the object is then treated as an unmodfied original when the next Support Package or upgrade is imported, even if it is included in a request. The object is overwritten without a backup of the previous status and is no longer included in the adjustment in the SPAU transaction.
SPAU and note corrections
[18] Which are the advantages of the Note Assistant?
Answer:
The Note Assistant provides an automatic/semiautomatic installation of note corrections. The Note Assistant add-on provides additional functions for the SE95 and SPAU transactions:
You can display objects reset to original after the installation of the Note Assistant by entering the relevant data in the selection screen.
With the 'Request/task' input field in the selection screen, you can select all modified objects of an object list.
You can display modification versions using the Utilites -> Modification versions menu option.
Using the 'Search in Requests' function, you can determine the requests that contain an object.
[19] Can I also install the Note Assistant in a system with a large number of modifications?
Answer:
Yes. You can further process objects modified with Modification Assistant in note corrections.
[20] Which requirements must be met for installting the Note Assistant?
Answer:
Refer to note 364804, Note Assistant installation, for more information.
[21 ] How do I know which notes are using an object?
Answer:
Position the cursor on the object and select the 'Utilities -> Used in notes' function. This function is available for objects modified with Modification Assistant.
[22] Why can I not reset to original a note correction with a yellow or green traffic light symbol in the SPAU transaction?
Answer:
You can only reset note corrections to original in the modification adjustment (transaction: SPAU) if they have become obsolete after importing a Support Package. If you want to undo the implementation of the note, you must select the 'Undo implementation of note' function in the note itself.
[23] Why can I not reset a modification with Modification Assistant to original if the object is contained in a note correction?
Answer:
The note correction would become inconsistent if individual objects were reset to original. You can only undo the implementation of the entire note.
[24] Why can I not adjust a modification in the SPAU transaction if the object is contained in a note correction?
Answer:
When implementing a note automatically, the SAP Note Assistant should start with the unmodified status, that is, the original status of the last upgrade or Support Package import should not have been changed. Subsequently, you can again transfer modifications using the Modification Assistant.
Tips and tricks
[25] Where do I find documentation for the SE95_UTIL transaction?
Answer:
Refer to note 328680, SE95_UTIL: Modification browser utilities, and note 309143, SPAU: Displaying objects reset to original, for more information.
[26] Which checks should I perform if problems occur?
Answer:
For subobjects (function modules, Includes, screens, and so on) displayed in the modification browser and the SPAU transactions, use the 'Utilities -> Modification versions' function. This function is available as of Release 6.10 (with the installation of the SAP Note Assistant). If objects are no longer displayed in the browser, you can also execute the RS_VERSIONS_MODINFO_SHOW report.
You can track the changes made to these subobjects with the version management.
Check which requests contain an object. You can use the Transport Organizer tools (transaction: SE03) for this. Choose the 'Search for objects in requests/tasks' option. As of Release 6.10 (with the installation of the SAP Note Assistant), you can also position the cursor on an object in the SE95 and SPAU transactions and select the 'Utilities -> Search in requests' function.
Check the transport logs in the Transport Organizer (SE09). For this, select the relevant transport request and then choose the 'Transport logs' pushbutton.
[27] How can I display the change history of an object?
Answer:
You can track the changes to an object with the version management.
Use the 'Utilities -> Modification versions' function (or the RS_VERSIONS_MODINFO_SHOW report) for subobjects (function modules, Includes, screens, and so on). This function is available as of Release 6.10 (with the delivery of the SAP Note Assistant).
[28] How can I display the developers who have modified an object?
Answer:
The modification browser (SE95) and modification adjustment (SPAU) transactions only display the last person who has modified the object. Check the version management for more information on the last person who has modified the object, or position the cursor on the object and select 'Search in requests'. In addition, refer to the next question.
[29 ] How can I display the requests in which the object was edited or imported?
Answer:
As of Release 6.10: Position the cursor on the relevant object and select 'Search in requests'.
Before Release 6.10: Choose 'Search for objects in requests' in the SE03 transaction (Transport Organizer tool).
You cannot sort by date of the transport release or the import. Only include requests/tasks that were created or imported around the time of the modification adjustment.
[30] Which versions should I compare if a problem occurs in the modification adjustment?
Answer:
Compare the following versions:
The active version in the development database and the version of the SPAU adjustment in the version database after the Support Package/upgrade was imported.
The version of the SPAU adjustment and the version of the upgrade/Support Package. The version of the upgrade/Support Package and the modified version before the upgrade/Support Package.
Check which version in the version database matches the active version in the development database.
[31] What do I have to bear in mind when comparing versions in the version management?
Answer:
Look out for source code changes and for deleted or inserted modification parentheses. These are blocks that start with '*{' and end with '*}'.
[32] What is important when comparing modification versions?
Answer:
Check the following:
Were the modifications implemented with or without Modification Assistant?
Was the object reset to original? (All modifications will have been undone.)
Was the Modification Assistant deactivated, for example, for report sources or function modules?
Were the time stamp or the last person who has changed the object changed between modifications of consecutive versions?
[33] Which information can I obtain from the transport logs?
Answer:
You can identify the transport category (K, T, D) in the export log. 'K' represents consolidation transports, 'T' transports of copies and 'D' Support Packages.
Check the parameters used for transports. The SMODI parameter must have a 'Yes' value.
Check the export and import logs for individual transport objects.
In the following example, a consolidation transport (transport category 'K') was imported. The modification information contained in the SMODILOG and SMODIRISC tables were transferred from the source system and overwritten in the target system.
When importing a Support Package, the target system retains the modification information. It merely executes an update and sets the upgrade indicator.
[34] In which components should I open a message if problems occur?
Answers:
Response:
In the BC-DWB-CEX and BC-UPG components. Messages for the SAP Note Assistant should be opened in the BC-UPG-NA component.
[35] Which Notes contain release-dependent information?
Answer:
361112 SPAU: Modification adjustment for Release 6.10
361106 SPAU: Modification adjustment SAP Note Assistant
196903 SPAU: Modification adjustment for Release 4.6D
180679 SPAU: Modification adjustment for Release 4.6C
170193 SPAU: Modification adjustment for Release 4.6B
207763 SPAU: Upgrading from releases before 4.5A to Release 4.5A or higher
164863 Information on SPAU and SE95 as of Release 4.5