OVERVIEW of SPAU activity(transaction) in upgrade process

OSS Notes section handling in SPAU : A note with gray icon specifies that it is obsolete for the system you are upgrading. The system is already in higher release than the release for which note is applicable. Note with Yellow icon needs to be checked if it can be applicable to the system. SNOTE or service marketplace is where you can see releases for which note is applicable and check if your system release is listed in it. Note with '?' says that system could not determine the adjustment mode of it. You can re-determine the status of it by clicking on it. A dialog box appears asking to run background job to determine the adjustment mode. There is color legend available which tells what each color specifies about adjustment mode of the object. The first activity to be done in SPAU is Note Correction before doing with/without modification assistant. It will display all the sap notes implemented in earlier version. Most of the notes becomes absolute in new version. Check the implementation status of the note by clicking on note number. If it is "can be implemented" need to implement and execute as per the steps. If it is "Cannot be implemented", it becomes absolute in new version. Click the traffic lights and reset. Please find below links for more info. OVERVIEW of SPAU activity(transaction) in upgrade process - Application Server Infrastructure - SCN

Wiki

Download SPDD and SPAU Adjustments Handbook from the below link. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/709abcf3-7d77-2c10-8d86-

b9d2cb01cf18?overridelayout=t

OVERVIEW of SPAU activity(transaction) in upgrade process

Upgrade:

In simple words SAP Upgrade is nothing but upgrading the software with a superior version

which has got more advantages when compared to the earlier version. This activity involves

various phases and sub-activities.

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). In this article we will be

concentrating on SPAU activity and how it is processed

during the upgrade

SPAU (adjustment of repository objects)

SPAU is an important activity during the upgrade process( which processes SPDD, Unicode

conversion etc. alongwith SPAU). During an upgrade or the import of a Support Package,

existing objects of the SAP standard are overwritten with the objects redelivered. To help the

customer retain the objects modified in a previous release, SAP provides all modified objects

which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of

transactions SPAU and SPDD. Repository objects are adjusted using transaction SPAU.

The various steps followed during the SPAU which in turn facilitate customers to enter their

modifications into the corresponding new objects being delivered at upgrade are described as

follows:

Steps

1) Enter the SPAU transaction; the screen will look like below.

The selection screen helps you to decide whether to display all or only specific objects to be

adjusted.

SELECTION CRITERIA: INPUT:

Agents Name of a user who was named in the function

User/Status in transaction SPAU

Last changed by _ _Name of the person or transport request that last

Last transport request In compliance with the above Input.

Package _ _Name of a package in particular.

Request/task_ _Name of a transport request , number of a task ,all

the relevant information is displayed

To restrict the display of the objects in transaction SPAU

Use the checkboxes of the tabs in the lower part of the screen.

Tab page: Description:

Modifications Note Corrections

It only displays a list of the notes, because the modification adjustment always

concerns all objects involved in the note correction. In the Modification Browser

(transaction SE95) you can expand a subtree under each note. It contains the

objects involved in the note correction.

Without Modification Assistant

This category displays objects that were modified in the current SAP System before

upgrade from a Release prior to 4.5A to Release 4.5A or higher. This category also

displays all Repository objects from those areas in the SAP standard where

modifications are not supported by the Modification Assistant.

Translations

Log of all modifications to translations.

The Customer Enhancements (SMOD) part is listed in the Migration

Objects category if converted by SAP into a corresponding Business Add-In

definition. The associated CMOD part is converted into a Business Add-In

implementation during modification adjustment.

Reset Objects If the action taken (for note corrections) is "reset to original", the note numbers with

the associated objects are displayed in the Reset Objects category. When you reset

modifications with Modification Assistant and without Modification Assistant to

original. The details of previous modifications are no longer available. Translations

and migration objects which are reset to original are listed in a category of their

own.

Adjustment

Filter

The Adjustment Filter tab is only displayed in the modification adjustment

transaction. Objects that still need to be adjusted can be shown in the tree with a

gray, green, yellow, or red traffic light. These symbols mean obsolete

notes, automatic, semi-automatic, or manual adjustment mode. By selecting the

corresponding fields, you restrict the object display to specific adjustment modes.

Display

Options

The display is normally structured by the modification type (note corrections,

modifications with and without Modification Assistant, and so on) and the object

type (programs, function groups, and so on). On the Display Options tab, you can

use various radio buttons to choose another display format. In the first hierarchy

level, the system displays all names of the persons who last changed the objects, all

last transport requests or all packages.

Once we enter the transaction we would encounter the following screen (after the initial screen)

with all the objects which require the action to be taken.

The Objects will appear in any of the three categories:

1. Note Correction

2. with Modification Assistant

3. without modification Assistant

For the adjustment of the notes listed the following steps are to taken:-

- NOTE CORRECTION: STEPS

2) Open the "Note Correction" section. Expand the

node.

2.1) Double click on the Note Number. Starting from the top. It will show the relevant details of

the note. Check the implementation status. If the Implementation status says "Can be Implemented".

Then you have to download the latest version of the SAP Note. This can be done by

pressing -Shift F7. 2.2) Use the Check functionality (Ctrl + F4) to check whether the note can be implemented

or not. (consistency check)

If the note is applicable and can be implemented, press "execute" and thus apply the note.

Once we do it we will get a pop up message to confirm the implementation, reply 'Yes'.

2.3) Assign it to the concerned CTS 2.4) The following screen will appear. Please take care that you should proceed further only

when you get a green light in all the lines. Even if one of the line is not green, please

don't go further. Please exit the implementation of this Note. If all the line are green,

the proceed.

2.5) Note has been successfully implemented. This note disappears from the SPAU transaction

and the changes will be added to CTS.

CASE: If the Note status is "Cannot be Implemented". Then following steps should be

taken.

2.6) click on the traffic lights, upon which you will get a message as follows:-

2.7) Click reset.

2.8) Add to the CTS.

Along with the note corrections node we have two more nodes under objects are placed,

naming,

With modification assistant.

Without modification assistant.

Before we go into details about the processing of the above nodes in SPAU activity we need to

familiar with the following terms:-

RESET TO ORIGINAL:

When we choose an option of resetting the object to original, it basically infers that we are reverting it back to the standard. This is done when we don't want to adopt any customer

modifications which have been applied to the objects.AfterReset to originalthe objects are

removed from the tree display of the Modification Browser (transaction SE95) and of the

modification adjustment transaction (transaction SPAU).

ADOPT MODIFICATIONS:

This option is contrary to the "reset to original" option. When we choose to set the object as "adopt Modifications", we are accepting the customer modifications performed to the

concerned object.(according to requirement).

Version Management :

Version management is a vital aspect of the SPAU activity.The plan behind this aspect is that

SAP maintains all the changes which have been done , and keeps track of all of them through

the maintainence of versions.Every standard or non-standard( customized change ) is

recorded.We have a facility of comparing the versions which have been associated with each

and every object in the SPAU list.This further gives us an option of deciding of whether we want

to adapt to the changes (adopt modifications) or just revert back to the original version ,standard

version(Reset to original).

- The version overview distinguishes between the versions in the development database

(Repository) and the historical versions saved in the version database.

The development database contains the active and/or the revised version.

The version overview also displays the date and time when the version was created and the

corresponding release.

If a transport request is specified for a version in the version database, then this version

corresponds to the status of the object:

- When a request is released and this request is from the current SAP System

- After a request is imported and this request is from a different SAP System

If a request is specified for the active or revised version, then the object is currently being

processed in the context of this request or it was imported using this request.

3.WITH MODIFICATION ASSISTANT:

For objects under "WITH MODIFICATION ASSISTANT" node analysis should be done as to

what changes have been done to the respective object. Below points explain various

possibilities and action to be taken.

3.1) PROGRAMS

Orange Status

Orange = Inactive version is most

recent

If the object is in orange, then it will:

- Need an object key

- has syntax errors

Action - Get key from Basis and activate object (prompt in generation screen)

3.2) SCREENS

Do nothing regardless of status

3.3) PROGRAM TEXT

Revert to standard (Reset to original)

3.4) INCLUDES

For includes do as following:

Double click on the Object Name

UtilitiesVersionsVersion

Management

Select most recent (date) 4.6c entry and Compare (F8) with Active version

Visually compare the 2 objects and reset to standard only if

1. There are additional comments but the ABAP code is the same as in there is no

customer modification (z- functionality)

2. The right panel code contains the same but less code entries than the left. In other

words, if the left panel contains new code and the code on the right is already included, return to

SAP standard.

If the above criteria is not applicable , no action is to be taken.

3.5) FUNCTION GROUPS

A.Function Modules: same rules as Programs.go ahead as in case of programs.

B.Screens: compare the active version with the most recent 4.6C version.

C.Data Elements. same as above.

Hence like this we can compare the versions of various objects and adjust them accordingly.

For objects under "WITHOUT MODIFICATION ASSISTANT" node analysis should be done as

to what changes have been done to the respective object.The method of doing this more or less

the same as objects under "with modification assistant".Below points explain various

possibilities and action to be taken.To adjust objectswithout the Modification Assistant, use

version management wherever possible. When modifying objects where version management

cannot be used, carefully document any changes that you make. This documentation can be of

great assistance the next time the object needs to be adjusted.

You can use the version management function for Repository objects when making modification

adjustments.

You can use the following functions in the version overview:

Function: Description:

Display The display mode of the ABAP Editor is used for displaying a version. Note that you

cannot modify versions subsequently.Using the editor functions (clipboard) you can

copy parts of an older version or the entire version to another window.

Compare Select two versions. You see two versions with identical and different line ranges. The

following additional pushbuttons are available:Single-column/Parallel formatSingle-

column: Sections with identical, modified, inserted or deleted lines are displayed one

below the other.Parallel: Both versions are juxtaposed. Differing parts are highlighted in

color.SettingsDisplay, Display all : Both versions are displayed in their entirety.Matches

condensed: Long parts with identical lines are shortened. Differing program parts are

displayed as a whole.Display differences only: Only the parts in which both versions

differ are displayed.Line numbering: You can optionally show or hide the line numbers.

In particular, if you choose parallel display, hiding the line numbers can increase

compactness.Ignore indentations/comments:You can choose not to include differences

in comments or indents in the comparison.Next equality:_Find/display the next

match._Next difference: Find/display the next difference.

Retrieve The functioning ofRetrieve depends on the object type:Dictionary objects: This function

is active if you call version management from object maintenance while in change mode.

The system first displays a dialog box explaining this function. The version selected is

loaded into the editor after you confirm that dialog box. You can then make further

modifications. When you save your changes, the active version is overwritten with the

content in the editor. For security reasons, the system creates a temporary version of the

status active before the retrieval which is saved in version management. When you

change the object, you must either have created a request, or the system prompts you to

choose or create a request once you save your changes.Other Repository objects:

TheRetrieve function cannot always be used for these objects. The system first creates a

temporary version of the active version. The active version is then overwritten with the

version retrieved.

REMOTE

comparison

Compares the object with a version from a different system. Enter the target system or

the RFC destination.

As shown in the screen shot below:

So this sum up the main processes and steps involved in conducting SPAU activity during the

upgrade procedure.

Hope this proves to be useful to all the people referring to it Suggestions and add-ons are most

welcome.