Details Description Of SPAU & SPDD

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

What objects will come in SPAU and SPDD?

All the objects which are modified, after tansporting to the current system, will be listed
in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like
tables, dataelements, domains,view...etc. The rest of all the modified repository objects
will be listed in SPAU.

What happens to the modifications done in the older version when we upgrade the
version? (with Modification assistant and w/o)

After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to

maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have
to either carry forward the changes to the new version, by choosing the option ADOPT
CHANGES (available on right click) or RESET TO ORIGINAL (available on right
click).

Will they come in these transactions?

Yes, they will be listed in these transactions, after the BASIS updgrade activity.

And what if we apply some patches(Notes) to the system? What is the impact of
these patches to the SPAU transaction?
Patches will be supported by the version upgrade. In case of notes, we have to verify
whether these notes are supported by the new version (you can go into
http://www.service.sap.com/notes to verify this. Also, we have to analyze whther the
code in the note is already incorporated in the new version. In this case you can ignore
the chanes choosing RESET TO ORIGINAL option

Apply Support Packs To My SAP SYSTEM

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,
DATABASE : ORACLE 8.1.7
OS : WINDOWS 2003 SERVER
What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003

- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported. *--
Markus

As mentioned, it's true that it won't get supported on Oracle 8. The best combination
would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have
the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two
ways.
1. Go to command prompt through cmd (if you are using windows) and go to the folder
where you have download these files ( could be in <drive>\downloaded folder\ ) type this
command on command prompt without quotes "sapcar -xvf <filename>.sar". Now it will
create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will
show two extracted files with extension " .att " and " .pat ". Copy this two files into
yours trans\eps\in folder which could be something like <drive>\usr\sap\trans\eps\in
folder.Then type spam on your session and navigate to Support Package\Load
Package\From Application Server and it will ask for Path confirm it Say " YES"Select
the patch imported and double click on it and then click on small truck Icon and it start
Import.

2. Type Spam on session then navigate to Support Package\Load Package\From

FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support
Pack.Now it will open a popup window and then click on decompress button ( It is front-
End process for extracting or decompressing .sar file in .pat and .att extension ) After that
click on Display-Define button on right hand side.) Select the BASIS or ABAP patch
( whichever you are applying *) what ever you are after and import it in queue. After that
click on Small truck Icon in menu i.e.. (import Queue) and it Starts
importing.
*--
Deepanshu Sharma
* Note :- Basis patch starts with KBxxxx.sar and Abap Patch start with KAxxxx.sar
likewise.
* Note :- If you are applying all support pack it may ask you to increase your spam level
(SUPPORT PACK MANAGER).

on this topic.

SUPPORT PACKS:- Support Packs provides enhanced functionality, Bug fixes,

changes to the existing Data Dictionary Elements, Repository objects like programs,
reports, transactions etc. Support Packs are of various types. Few of them are:

Basis Support Packages (SAP KB 62050)

ABAP Support Packages (SAP KA 62050)

Application Support Packages (SAP KH 47050)

HR Support Packages (SAP KE 47050)

Prerequisites:

1. SPAU and SPDD list should be checked before start of support package application.

2. Objects in repair state needs to be released.

3. It is recommended that latest SPAM/ SAINT version should be applied before starting
and Support Package application.

4. Enough space to hold the support packs in “EPS” in directory

USR/SAP/TRANS/EPS/IN. There should be no aborted packages from previous support
pack or Plug In applied.

5. Support Packages should be applied in the sequence of number of support packs.

6. Technical & functional consultants need to be informed while applying support

packages.

7. Schedule downtime and inform the users.

8. Go through composite note thoroughly before applying support packs. If the support
pack is greater than 10MB then uncar the file using command SAPCAR – XVF .sar.
When we uncar, two files are generated with extensions .ATT& .PAT

EXECUTING SUPPORT PACKS

1. Go to transaction code Spam

2. Load Packages from the presentation server/Application server

3. Display all the new support patches to be applied

4. Select the support package to be applied

5. Import the Queue Support Package starts upgrading the system and it goes into various
phases like TP connect to DB, DDIC import, DDIC Activation. These phases can be
found in Table PAT01. While applying support packages its stops to run SPAU/SPDD.

SPAU: This is the transaction to update repository objects like programs, reports,
transactions, function modules while applying support packs. This is the phase where
functional consultant’s assistance is required.

SPDD: This is the transaction which is used to update Data Dictionary Elements while
applying support packages. This is the phases where functional consultant’s assistance is
required.

Note: If the objects are changed earlier with the help of SAP notes, now these notes are
part of the support packs which are modifying the system. In this scenario each and every
object which were modified earlier with the help of Note are popped up on the screen
whether to keep the original or change to newer version.

Related posts:
Links

http://enjoysap.blogspot.com/2007/04/sap-system-administration-made-easy.html