tcode : spau ?

[Former Member]

Hi Experts,

Please help me in knowing this tcode SPAU.

How to use it.insted of links pls send me a documents.

Thank You for helping in advance.

[Former Member]

<b>SPAU and SPDD</b>

When you apply a package, a large number of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.

SPDD is used to identify dictionary objects

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

Refer this too

http://help.sap.com/saphelp_nw04/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm

Reward if this helps.

[Former Member]

Hi,

SPAU transaction contains the list of all the standard Programs , Function Modules that were changed .

After Upgrade the SPAU transaction can be used to accept the changes that were done in the previous versions or can be rejected .On accepting the changes all the changes done in the previous version to the standard SAP objects are transferred.

The changes to standard objects through SPAU needs to be done within 14 days of Upgrade.

Regards,

Sowmya.

[Former Member]

I hope below link gives yoy good document. Have a look.

http://help.sap.com/saphelp_nw2004s/helpdata/en/fe/4b284837bf11d5b3bf0050dae02d7c/frameset.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/c8/61ec66e33611d1954b0000e82de14a/frameset.htm

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

[Former Member]

Read this steps .

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

Start transaction SE03 as user DDIC and choose Tools ® Administration ® Set system change option.

Select Modifiable in the Global setting dialog box.

Choose Continue.

Choose Edit ® Select all.

Save your entries.

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.

Handling Change Requests During Adjustment

When you carry out modification adjustment during and after an upgrade, the functions of the Transport Organizer are active. In this context, questions are frequently asked about the Transport Organizer functions. Typical questions are:

Which change request should I choose to record changes made during modification adjustment?

What are local and transportable change requests?

How are tasks (repairs and corrections) released when modification adjustment has been completed?

How do I select a change request to transfer modification adjustment from the development system to other SAP Systems?

The following section enables you to carry out modification adjustment for the upgrade without having an in-depth knowledge of Transport Organizer functions.

Refer to service.sap.com/spau for more information .

Please reward if useful.

[Former Member]

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 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.

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

4.6B SAPKB46B25

4.6C SAPKB46C15

4.6D SAPKB46D05

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 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

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.

also check....

http://help.sap.com/saphelp_nw04/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm

SPAU and SPDD

When you apply a package, a large number of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.

SPDD is used to identify dictionary objects

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.