1000009 asu toolbox sapnote

25.06.2008 of 6

Note 1000009 - ASU Toolbox 2008

Note Language: English Version: 9 Validity: Valid from 18.04.2008

Summary

Symptom

See also Note 1132617, which provides current information about the ASU Toolbox.

Description of the ASU Toolbox:When you upgrade an SAP system, you must often perform additional,application-specific steps before and after the upgrade, in addition to theactual technical upgrade. The ASU Toolbox enables the customer torecognize the necessary steps and perform them in the system in acontrolled manner. On the one hand, we provide application-specific upgradecontent (ASU content definition) in the form of an XML file, which can beupdated daily and is available on SAP Service Marketplace. On the otherhand, with the ASU Toolbox we provide a tool that interprets this XML fileand supplies it to the user for processing.

ASU Content DefinitionAn ASU content definition consists of an XML file describing all steps thatmust be executed by the SAP system (either manually or automatically)before or after a SAP system upgrade.

An ASU content definition is described by a 20-character field label (ASUscenario) and a 14-character version counter (ASU version - that is, thegeneration time stamp of the ASU content definition). The ASU Toolbox canalso be used for any customer-specific content definitions, irrespective ofthe upgrade scenarios described.Take into account the following naming convention: For customer-specificASU scenarios, use a description with the initial letters X, Y or Z.

An ASU content definition consists of several ASU steps in addition to thisdescription. Each ASU step is described by different attributes. The mostimportant attributes are described in the "Solution" section.

Two-Step Processing ConceptThe ASU Toolbox uses a two-step processing process: In the first step, thesteps to be processed (ASU content definition) are loaded into the SAPsystem and saved there cross-client. In the second step, the systemgenerates a client-specific task list to be processed within the upgrade.The ASU Toolbox is thus a framework that supports this two-step process.However, the ASU Toolbox itself does not deliver any correction programs orsimilar; the individual SAP applications are responsible for makingcorrection programs available. The ASU Toolbox is only responsible for thecoordinated and correct start of these correction programs - not foradjustments implemented by you in the SAP system.

Application CasesThe ASU Toolbox covers two application cases:

o Stand-Alone Application Case

25.06.2008 of 6


In this application case, the steps are executed independentlybefore or after the upgrade, and before the actual technicalupgrade.The ASU Toolbox in used in two steps:1. You can import the XML file of the ASU content definition on theSAP Service Marketplace into the file system of the frontend PC,and then load it into the SAP system. To do this, use transaction/ASU/START.Keep in mind that the link on SAP Service Marketplace is notavailable yet. Use the attached ZIP files for the download instead.2. Using transaction /ASU/START, you can generate a task list forthe selected ASU content definition. You navigate to the generatedtask list directly from this transaction, and then process thesteps specified in the task list. The task list is displayed infull: Both the pre-upgrade and post-upgrade steps are listed forprocessing by the user.

o Integration in the SAP UpgradeIn this application case, the XML file is already provided ininitial form by the SAP upgrade process and is automaticallyupdated by newer versions, if available.The SAP system upgrade requests the user to process the ASU stepsin a new PRE-upgrade or POST-upgrade phase. To do this, usetransaction /ASU/UPGRADE. Unlike transaction /ASU/START, thistransaction automatically loads the XML file into the SAP systemduring the first implementation. It generates a task listautomatically and then branches directly to the task listmaintenance.To ensure that the end user sees only the relevant processing stepsfor each upgrade situation, the task list is displayed differentlyfrom the stand-alone application case: If the ASU Toolbox is calledin the PRE-upgrade phase, only the PRE-steps of the task list aredisplayed. If the Toolbox is used in the POST-upgrade phase, thePOST-steps are displayed and the PRE-hierarchy is hidden.

Note the following: The integration of ASU with the SAP systemupgrade is currently only supported for upgrading ERP systems toERP2005 SR3 (SAP component SAP_APPL) and upgrading Netweaver BIsystems to Netweaver 7.0 SR3 (SAP component SAP_BW). During theupgrade, make sure you include an equivalent ST-PI Support Packagefor the target release (for details, see below).

Note the following: Due to the namespace /ASU, ensure that you enter"/n/asu/upgrade" or "/n/asu/start" in the OK code field for thetransactions.

More TermsTransactions: /ASU/START, /ASU/UPGRADE, /ASU/SSMASU Simple Schedule Manager

ERP2005 SR3Netweaver 7.0 SR3

Note the following: You can use transaction /ASU/SSM to branch to the tasklist maintenance directly. However, you must also enter the technical name(0-ASU*) of the task list generated by the SAP system.

25.06.2008 of 6


Cause and PrerequisitesUpgrade

Required ST-PI Support PackagesWe provide the ASU Toolbox with the following ST-PI add-ons:ST-PI 2005_1_[46C,620,640] SP08, 2005_1_700 SP06 and 2005_1_710 SP04

AuthorizationsTo operate the ASU Toolbox you require authorization for transactions/ASU/START, /ASU/UPGRADE and /ASU/SSM, and also for the ASU-specificauthorization objects that are checked in these transactions.When you execute individual steps, other step-specific applicationauthorizations are checked. These authorizations are also required.Therefore, we recommend that the ASU Toolbox is operated by a user withSAP_ALL authorizations.

RestrictionThe ASU Toolbox is currently only available for the ABAP stack.

Other Planned Developments

o Generating a task list from different ASU content definitions

o Improved filtering and display options for the task list

o Generating an overall log for all listed tasks and their results

o Checking for dependent steps

o Client-specific steps

o Archiving

o Transport connection for generated task lists

o The ASU Toolbox does not replace the SAP Upgrade Guide. However,improved integration of both of these tools is planned for asubsequent release.

SolutionUsage of the ASU Toolbox depends on the application cases described above:

o Stand-alone application caseCall transaction /ASU/START. The screen of this transactionconsists of two parts:A tree on the left displays all ASU content definitions that arealready in the system. The details for a selected ASU contentdefinition are described on the right.

You can load new ASU content into the system by choosing "Importnew ASU Content Definition". If you double-click one of thepreviously selected ASU content definitions in the left screenarea, the details for this content version are displayed in the

25.06.2008 of 6


right screen area. The following five functions are available:1. Create new tasklist2. Jump to tasklist3. Start automatical PRE reports4. Start automatical POST reports5. Implement SAP Notes

Instead of importing an ASU content definition from the filesystem, you can also transport an ASU content definition withinyour system infrastructure in the stand-alone application case. Youcan access this transport connection by choosing ASU->TRANSPORT forthe selected ASU content definition. When you transport an ASUcontent definition, ensure that the ASU content definition, whichalready exists in the target system, is overwritten with the samecombination of ASU scenario and ASU version.

o Integration in the SAP UpgradeFor the SAP upgrade, you must call transaction /ASU/UPGRADE for anERP upgrade to at least ERP2005SR3 or for a BI upgrade to at leastNetweaver7.0 SR3. As described above, the system loads the XML file(ASU.XML) contained in the upgrade directory, generates a task listautomatically and then branches to the task list maintenance.Depending on the status of the system regarding the upgrade(PRE-UPGRADE or POST-UPGRADE phase), only the PRE-UPGRADE orPOST-UPGRADE steps of the task list are displayed.

Processing the Task ListYou access the task list using either transaction /ASU/START or/ASU/UPGRADE. The task list is displayed as a tree, and distinguishesbetween PRE-upgrade and POST-upgrade steps as well as manual and fullyautomatic steps. You must then process this list top-down according to thecurrent upgrade phase. The most important functions are:

o Read the description of how to execute this step (click therelevant cell in the column "Description" for this step). If otherOffice or PDF documents are attached to this step, these documentsare also displayed. Note the following: To display these additionaldocuments, click the cell in the "Documentation" column.

o Read the assigned SAP Note: If an SAP Note is assigned to the step,an icon with the relevant note number appears in the cell of thecolumn "Note". If you click this cell, the system loads the Notefrom SAP Service Marketplace and displays it in a separate window.

o Execute the action assigned to the step by double-clicking therelevant line. If the step is a manual step, the assignedtransaction, IMG activity, and so on, are started. If the step is afully automatic step, background job scheduling is executed for therelevant report or class. You can access the spool or the job logof the generated background job by clicking the cells in thecolumns "Log" or "Job Log". The cell "Job Status" describes thecurrent status of the background job.

After you perform the action for this step, the date/time of thisaction is logged in the cell of the column "Last Execution". If thestep is executed several times, an overview icon appears in thiscell. When you click the icon, all previous executions are

25.06.2008 of 6


displayed.

o For a selected step, you can add a remark in SAP script form bychoosing "Add user remark". Here, you can enter remarks forspecific steps.

o By choosing "Show step details", you can display all details for aselected step in a dialog box.

In addition to these step-specific functions, three other functions areprovided:

- Display a short documentation on this transaction

- Display the icons used

- Refresh the display (for example, to display the current statusof the background job)

Many of the functions mentioned are also available as a context menu.Select a line and click the secondary mouse button. A special function ofthe context menu is the download function of the SAP Note assigned to therelevant line. Here, you can use the Note Assistant functions. Thisfunction is particularly useful if the correction report is delivered by anSAP Note and is not already available in the system. Ensure that thedownload function loads only the relevant SAP Note into the SAP system. Toimplement the note, navigate to the Note Assistant (transaction SNOTE).Then restart the ASU Toolbox and execute the relevant step.

Note the following: The task list is intended to display only those stepsthat are relevant to the user in terms of system configuration and systemusage. All non-relevant steps should be filtered out. In the currentversion, all steps are filtered according to their assigned softwarecomponents in relation to the software components available in the system(see menu SYSTEM->STATUS->COMPONENT_INFORMATION). To deactivate thisfiltering for analysis purposes, choose EXTRAS->FILTERING_OFF.

The most important attributes of an ASU step:

o Object Type - the following step types are currently supported:Display of any documentation (NOTE) or execution of an ABAP report(PROG), transaction (TCOD), IMG activity (IMGH), function module(FUNC), ABAP class (CLAS).

o Object Name - this attribute describes the object key suitable forthe object type. For example: For PROG, the name of the ABAPprogram.

o Execution Type: Describes whether the step is a manual (MANUAL) ora fully automatic (AUTOMATIC) step.

Note the following: Fully automatic steps may only be type PRG orCLAS. The class must also implement the interface IF_UACC_STEPS.

o Execution Severity: Describes whether the step is an optional(OPTIONAL) or an obligatory (OBLIGATORY) step.

25.06.2008 of 6


o SAP Note: An additional SAP Note may be entered here.

o Component: Describes the SAP component for which the step isrelevant.

o Description: Short and long description of the step; you can alsoadd an Office or PDF document of the description. Ensure that thefile name has 32-characters maximum. The additional documents forthe upload must be contained in the same directory as the ASUcontent definition.

Header Data

Release Status: Released for CustomerReleased on: 18.04.2008 08:15:00Priority: Recommendations/additional infoCategory: Upgrade information

Main Component SV-SMG-ASU Application Specific Upgrade (ASU)Additional Components:

XX-PROJ-IMS-UPGR Application Specific Upgrade Tools

The note is not release-dependent.

Related Notes

Number Short Text

1132617 General information for ASU Toolbox 2008

1088904 Add. info. on upgrading to SAP ECC 6.0 SR3 ABAP

623723 Upgrade: Application-specific problems

Attachments

File Type File Name Language Size

ZIP ASU_ERP.zip E 23 KB

ZIP ASU_BI.zip E 17 KB

1000009 asu toolbox sapnote

Documents