‎2008 Jan 18 10:34 AM
what is the use of "SPAU" and "SPDD" ?? I am into an Upgrade project (first upgrade proj). Could anyone suggest some links for the explanation on the tcodes?Or give brief idea?
‎2008 Jan 18 10:43 AM
Hi,
HERE IS SOME DETAILS, GO THROUGH THIS.
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.
Preparing to Run Transaction SPDD
During the adjustment of ABAP Dictionary objects, the ABAP Workbench already has the new release (however, not the applications).
Setting the System Change Option
Before you begin adjustment, set the system change option for the SAP System to modifiable for all namespaces:
Start transaction SE03 as user DDIC and choose Administration ® Set system change option ® Global setting...
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.
Checking the User for the Upgrade
You must be able to log on to the system as user DDIC in client 000. In a new installed system, the initial password for user DDIC is 19920706. User DDIC must have the authorization SAP_ALL to be able to perform all operations during the upgrade.
If modification adjustment is required, log on in client 000 as the user who is designed to perform the adjustment in SPDD. This must be a different user than user DDIC. DDIC is not allowed to perform the modification adjustment.
If the profile SAP_NEW which contains the authorizations for the new release is available in your system, make sure it is assigned to the following users in addition to the existing profiles.
DDIC
SAP*
User who is to perform the modification adjustment with transaction SPDD
You perform the modification adjustment during the upgrade in a phase in which the system has an undefined state and the user maintenance transaction SU01 cannot be executed. To add a user, choose Tools ® Administration ® User Maintenance ® Users (SU01). You can also use the report UPGADDUSR provided you are authorized to create users. For the adjustment, UPGADDUSR creates the user upg_tmp_user with the password init in the client in which the report runs. The user is valid for one week.
If the profile SAP_NEW is not available in your system, we recommend that you temporarily assign the profile SAP_ALL to the user who is to perform the modification adjustment with transaction SPDD. Remove this assignment after the upgrade.
Activating Objects During Modification Adjustment
Save your work in the Dictionary maintenance transacton (SE11) but do not activate any objects. Activation is carried out automatically after the adjustment.
This does not apply if a Support Package is imported. Above all others, you must activate newly created objects.
-
-
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.
Regards,
Omkar.
‎2008 Jan 18 10:38 AM
Hi,
SPAU
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 for 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.
http://help.sap.com/saphelp_nw70/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm
SPDD
Processing in transaction SPDD is based on the release level imported at which the R3up upgrade control program has stopped.
Data elements that were changed using the Modification Assistant are displayed with a green or a yellow traffic light.
Objects that were changed using the Modification Assistant are displayed with a green or a yellow traffic light.
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
Pls reward points if solved your issue.
Regards,
Renjith Michael.
‎2008 Jan 18 10:39 AM
Hi Divya,
It's well explained in the SAP Help:
Spau: http://help.sap.com/saphelp_nw70/helpdata/en/c8/61ec66e33611d1954b0000e82de14a/frameset.htm
SPDD: http://help.sap.com/saphelp_nw70/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm
Regards,
John.
‎2008 Jan 18 10:43 AM
Hi,
HERE IS SOME DETAILS, GO THROUGH THIS.
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.
Preparing to Run Transaction SPDD
During the adjustment of ABAP Dictionary objects, the ABAP Workbench already has the new release (however, not the applications).
Setting the System Change Option
Before you begin adjustment, set the system change option for the SAP System to modifiable for all namespaces:
Start transaction SE03 as user DDIC and choose Administration ® Set system change option ® Global setting...
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.
Checking the User for the Upgrade
You must be able to log on to the system as user DDIC in client 000. In a new installed system, the initial password for user DDIC is 19920706. User DDIC must have the authorization SAP_ALL to be able to perform all operations during the upgrade.
If modification adjustment is required, log on in client 000 as the user who is designed to perform the adjustment in SPDD. This must be a different user than user DDIC. DDIC is not allowed to perform the modification adjustment.
If the profile SAP_NEW which contains the authorizations for the new release is available in your system, make sure it is assigned to the following users in addition to the existing profiles.
DDIC
SAP*
User who is to perform the modification adjustment with transaction SPDD
You perform the modification adjustment during the upgrade in a phase in which the system has an undefined state and the user maintenance transaction SU01 cannot be executed. To add a user, choose Tools ® Administration ® User Maintenance ® Users (SU01). You can also use the report UPGADDUSR provided you are authorized to create users. For the adjustment, UPGADDUSR creates the user upg_tmp_user with the password init in the client in which the report runs. The user is valid for one week.
If the profile SAP_NEW is not available in your system, we recommend that you temporarily assign the profile SAP_ALL to the user who is to perform the modification adjustment with transaction SPDD. Remove this assignment after the upgrade.
Activating Objects During Modification Adjustment
Save your work in the Dictionary maintenance transacton (SE11) but do not activate any objects. Activation is carried out automatically after the adjustment.
This does not apply if a Support Package is imported. Above all others, you must activate newly created objects.
-
-
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.
Regards,
Omkar.
‎2008 Jan 18 10:46 AM
Refer to the following links .... You will get more info
ABAP Dictionary Objects --> All Data Dictiaory Objects like tables, Structures etc.,
http://help.sap.com/saphelp_nw70/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm
ABAP Repository Objects - Program Includes, Function groups, Function modules etc.,
http://help.sap.com/saphelp_nw70/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm
Hope this helps
‎2008 Jan 18 10:50 AM
‎2008 Jan 18 10:55 AM
Hi,
Spdd and spau are important steps to be taken when applying hot packages.
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.
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 (used to identify dictionary objects) and
spau (repository objects), will identify any objects that 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 original SAP Code. If,
for instance, you are applying hot package 34 spau idenitifies an object
where you have applied an oss note. You must check the oss note and see if
sap have fixed that note in a hot package. If the oss note has been fixed in
HP34 then you should reset to object to original source code. This means
that there is no repair flag set against this object again and it is now
SAPstandard 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.
regards,
vasavi.
reward if helpful.