SAP Add on Installation Tool(BC UPG OCS)

8/9/2019 SAP Add on Installation Tool(BC UPG OCS)

1/21

SAP ® AG • Neurottstr. 16 • D-69190 Walldorf

SAP Add -On Ins t al l at io n Tool(BC-UPG-OCS)


2/21

SAP Add-On Installation Tool (BC-UPG-OCS) SAP AG

2 November 2001

Copyright© Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft ®, WINDOWS ®, NT ®, EXCEL ®, Word ®, PowerPoint ® and SQL Server ® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2 ®, OS/2 ®, DB2/6000 ®, Parallel Sysplex ®, MVS/ESA ®, RS/6000 ®, AIX®, S/390 ®, AS/400 ®, OS/390 ®, OS/400 ®, IBM eServer iSeries ®, IBM eServer zSeries ® and z/OS ® areregistered trademarks of IBM Corporation.

ORACLE ® is a registered trademark of ORACLE Corporation.

INFORMIX ®-OnLine for SAP and Informix ® Dynamic Server TM

are registered trademarks of Informix Software Incorporated.

UNIX®, X/Open ®, OSF/1 ®, and Motif ® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA ®, Program Neighborhood ®, MetaFrame ®, WinFrame ®, VideoFrame ®,MultiWin ® and other Citrix product names referenced herein are trademarks of Citrix Systems,Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ®, World WideWeb Consortium, Massachusetts Institute of Technology.

JAVA ® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT ® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAPEarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com aretrademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other products mentioned are trademarks or registered trademarks of their respective companies.


3/21

SAP AG SAP Add-On Installation Tool (BC-UPG-OCS)

November 2001 3

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as well asmenu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in the system. These include reportnames, program names, transaction codes, table names, andindividual key words of a programming language, whensurrounded by body text, for example, SELECT andINCLUDE.

Example text Screen output. This includes file and directory names andtheir paths, messages, names of variables and parameters,source code as well as names of installation, upgrade anddatabase tools.

Example text Exact user entry. These are words or characters that youenter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such asF2 ) or the ENTER key

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4/21


4 November 2001

Contents

SAP Add-On Installation Tool (BC-UPG-OCS) .............................. 5 Authori zations for the Add-On Inst allat ion Tool ................................ 7Making Settings for the Add-On Installation Tool .............................. 8Loading Installation Packages ........................................................... 10

Loading Installation Packages from the Appl ication Server ..................10Loading Installation Packages from the Front End .................................12

Installi ng and Upgrading Add-Ons .................................................... 13Installi ng a Preconfigured System (PCS) Using SAINT................... 15Modif ication Adjustment .................................................................... 17

Checking Logs ..................................................................................... 18Phases of the Add-On Installation Tool ............................................ 19Impor ting a SPAM/SAINT Update ...................................................... 21


5/21


November 2001 5

SAP Add-On Installation Tool (BC-UPG-OCS)UseSAP offers a wide range of add-ons that you can use to enhance your standard SAP System.These add-ons can be Industry Solutions, plug-ins, or customer-specific development projects.Many of these add-ons contain only a small number of objects, however, you must take severalimport conditions into account.

Since an operating system-based process for installing or upgrading these add-ons in an SAPSystem is too complicated, SAP has developed the SAP Add-On Installation Tool (transactionSAINT). This transaction lets you install and upgrade add-ons directly from the SAP System. Youdo not need to access the operating system or restart the system.

SAP offers Preconfigured Systems (PCS or best practices for mySAP.com ), which can also beinstalled using the Add-On Installation Tool. A PCS reduces the amount of work needed to installand customize an industry-specific solution. For more information on preconfiguration with bestpractices for mySAP.com, see the SAP Service Marketplace under the alias /bestpractices .

This transaction is updated frequently, which means that it is only available in thelanguages English and German .

PrerequisitesThe Add-On Installation Tool is available as of R/3 Release 4.0B, and is delivered in its ownSupport Package, the SPAM/SAINT Update [Page 21] .

We enhance and improve the transaction constantly, and recommend that you always import thelatest version from the SAP Service Marketplace or SAPNet R/3 – Frontend before you performan installation or upgrade.

Functions• The transaction checks the import prerequisites, such as the release of the Basis System,

and the Support Package level of each software component, and includes or excludes theuse of other add-ons.

• To simplify the import process, the complete installation is first put together in the customer system from the add-on installation package, any Support Packages that are needed, andany Conflict Resolution Transports (CRTs).

• The installation itself is a process that can be restarted, in a similar way to the import of Support Packages.

Activi ties• Loading Installation Packages [Page 10] .

• Installing and Upgrading Add-Ons Using SAINT [Page 13]

• Installing a Preconfigured System (PCS) Using SAINT [Page 15]


6/21


6 November 2001

• Modification Adjustment [Page 17]

• Checking Logs [Page 18]


7/21


November 2001 7

Authorizations for the Add-On InstallationToolTo use all the functions of the SAP Add-On Installation Tool, you require the followingauthorizations:

• S_TRANSPRT

• S_CTS_ADMIN

Both authorizations are in the authorization profile S_A.SYSTEM.

Assign this authorization profile to the system administrator only.

If you log on without the correct user profile you can use the display functionsonly.


8/21


8 November 2001

Making Settings for the Add-On Installation ToolUse

You can make settings for the Add-On Installation Tool, which influence the actions when youdownload or import installation packages.

Procedure

On the initial screen of the Add-On Installation Tool, choose Extras → Settings . A dialog boxappears in which you can make or check the following settings:

Tab: Load Packages• Directory on the application server for Release 6.10 as of PSAM/SAINT update 03

You can check in which directory on the application server the OCS packages are located.

• Load CAR/SAR archiv e from f ront end

– Display contents before decompressingYou can decide whether to display a dialog box with the contents of the CAR/SARarchive before you decompress it. This is the default setting. – Delete archive after decomp ressing

You can choose whether you want to delete the CAR/SAR archive, which wastransferred to the application server, after decompressing it. This is the default setting. – Back up previous upload directory

You can decide whether to save the last used upload directory of your front-end host.This directory then appears as the start directory in the dialog box where you select anarchive. This is the default setting.

You can enter your own choice of upload directory in the Upload directory field. Thisupload directory then appears as the start directory in the dialog box where you select anarchive.

Tab: Import Queue• Create new data file

You can determine whether you want the data files to be unpacked from the EPS parcelseach time you import Support Packages. This is the default setting.

If you use a multiple system landscape with a common transport directory, it is best to onlyactivate this option in the first system into which you import packages, and to deactivate it inthe following systems. This saves time because the data files do not need to be createdagain in these systems.

• Delete data file after imp ort

You can decide whether you want the data files to be deleted after importing the packages.This saves hard disk space and is the default setting.

If you use a multiple system landscape with a common transport directory, it is best todeactivate this option, since then you do not need to create new data files in the other systems (see Create new data file above).


9/21


November 2001 9

• Create object versions duri ng im port for Release 6.10 as of PSAM/SAINT update 03

You can choose to create versions of the objects in the OCS packages in the installationqueue when they are imported. This option is deactivated by default, since it is a good ideaonly if version creation is active for all imports. This can take a long time and use up a lot of

space in the database.

Remember that if you activate version creation, the parameter VERS_AT_IMPmust be set to ALWAYS in the transport tool configuration in the TransportManagement System (transaction STMS).

• Generate ABAP/screen

Select this option if you want the programs and screens delivered in the OCS Packages to begenerated when they are imported.

– Never perfor m

If you use this option, the programs and screens are generated only when they are called

for the first time. – Always per fo rm

If you use this option, the programs and screens are always generated. Note that thegeneration can take a long time and may cause errors. – Acco rd in g t o SAP ins tr uc ti on s

If you use this option, the programs and screens are generated if the option of generatingduring import has been activated by SAP.

SAP Default Settings

At tr ib ute Defau lt val ue

Display contents before decompressing OnDelete archive after decompressing On

Back up previous upload directory On

Create new data file On

Delete data file after import On

Create object versions duringimport

Off

Generate ABAP/screen Never perform


10/21


11/21


November 2001 11

Procedure

Installation packages from the SAP Service Marketplace have a compressed

format. You have to unpack these packages before proceeding with further processing.1. Load the packages from the SAP Service Marketplace or mount the relevant CD.

2. Log on using the following user:

Operating System User

UNIX adm

AS/400 OFR

Windows NT adm

3. Switch to the following subdirectory in your system:

Operating System SubdirectoryUNIX and AS/400 /usr/sap/trans

Windows NT :\usr\sap\trans

4. Disassemble the archive that contains the packages using the following command:

Operating System Command

UNIX CAR -xvf ///.CAR

AS/400 CAR '-xvf /QOPT///.CAR'

Windows NT CAR -xvf :\\.CAR

The disassembled packages automatically appear in the EPS inbox of the transport directory(UNIX and IBM eServer iSeries: /usr/sap/trans/EPS/in ; Windows NT::\usr\sap\trans\EPS\in ).

5. To load the packages into your system, call the Add-On Installation Tool and chooseInstallation Package → Load Packages → From Application Server .

You see a list of the packages you uploaded that are now known in the SAP System with allof their attributes, and can be handled in the correct way by the SAP Add-On InstallationTool.

6. To return to the initial screen of the Add-On Installation Tool, choose Back .


12/21


12 November 2001

Loading Installation Packages from the Front EndUse

You want to load archives (*.CAR oder *.SAR) from the front end to the application server so thatyou can use the Add-On Installation Tool to install the corresponding package.

If these archives are smaller th an 10 MB , proceed as described here.If the archives are larger than 10 MB , proceed as described in LoadingInstallation Packages from the Application Server [Page 10] , since the procedurethat is described here is not suitable for large installation packages.

Procedure1. Call the SAP Add-On Installation Tool with transaction SAINT.

2. Choose Installation Package → Load packages → From Front End . The system displays a

dialog box for selecting an archive.3. Select the corresponding archive. The system displays a dialog box that shows you the

contents of the archive.

To suppress this dialog box, you must make the appropriate settings in the Add-On Installation Tool [Page 8].

4. To copy the archive to the application server and then decompress it, choose Decompress . After the package you want to install has been decompressed, it appears in the Add-OnInstallation Tool.

Result

The archive has been copied to the application server and decompressed. The original archivehas been deleted. (See also Making Settings for the Add-On Installation Tool [Page 8]).


13/21


November 2001 13

Installing and Upgrading Add-OnsUse

The Add-On Installation Tool can process two different types of add-on delivery packages: add-on installations and add-on upgrades.

Prerequisites• You are logged on to client 000.

• You loaded the relevant installation packages [Page 10] into your system.

Only import the packages when the system load is low since all the applicationservers should be shut down during the import except for the central applicationserver. Also, make sure that no other users are logged on.If not, problems can arise (terminated transactions, problems withsynchronization, for example).

ProcedureSince the add-on installation is identical to that of the add-on upgrade, the installation is used asan example here.

1. Call the Add-On Installation Tool (transaction SAINT). The system displays the initial screen.

In the upper half of the screen you see the installed add-ons. The lower half displays the add-on packages to be installed.

2. To search in the EPS directory of the current system for additional installation packages,choose Load . If new packages are found, they are then displayed.

See also: Loading Installation Packages [Page 10] .

3. To prepare the installation queue for an add-on, select the relevant add-on and chooseContinue .

This can lead to different results:

− The add-on may not be installed in this system since you have not met all of the importrequirements. In this case, these import requirements are then named.

− Additional packages (Support Packages or CRTs) are needed for the installation. Youare shown which packages are missing. The installation does not start.

First load the missing packages.

− If all the import requirements are met and all the necessary Support Packages areavailable, the relevant queue is displayed (all the packages that make up the installationin the correct order). You can start the installation process.

4. To start the installation, choose Continue .

After starting the installation, the transaction runs through a set series of phases. If an error occurs in one of these phases, the installation terminates and the error is described, as far aspossible.

When the problem is corrected, choose Continue .


14/21


15/21


November 2001 15

Installing a Preconfigured System (PCS)Using SAINTUseSAP offers Preconfigured Systems (PCS or best practices for mySAP.com ) for certainindustries. These systems contain special industry information for typical structures in anindustry, and the corresponding default values for these structures in the SAP System.

A PCS consists of the following elements:

• An industry-specific solution

• An industry-specific SAP client

• Industry-specific Customizing data

A PCS also contains test data and industry-specific documentation. You can use this test data totry out examples of processes and scenarios. The documentation gives you detailed descriptionsof the process models. For more information on Preconfigured Systems, see the SAP ServiceMarketplace under the alias /bestpractices .

Only use the PCS as a basis for the configuration of a system installation.Import the PCS into your test system first, so that you can check that its settingsmeet your requirements.

Prerequisites• You have loaded the relevant packages [Page 10] into your system.

• You have not yet installed a PCS or have not installed a compatible PCS.

Preconfigured Systems are not compatible with each other. They cannot beinstalled together. To enable you to install related PCSs anyway, SAP organizesthem in groups that guarantee compatibility. If a PCS belongs to a different groupthan an installed PCS, or to no group, you cannot install it.

• You are logged on to the SAP System in a client other than 000 or 066. These clients areprotected against the import of a PCS. In client 000, you can use the Add-On Installation Toolto install add-ons [Page 13] .

A PCS is always installed in the client in which you started the Add-On InstallationTool.

• The client in which you install the PCS is not protected against imports. If you are unsure,you can use transaction SCC4 to check the client settings and change them if necessary.

• The system is not being used as a production system. In other words, no clients are flaggedas production clients (see transaction SCC4).

If you are logged on to a protected client, or an incompatible PCS is already installed, you canonly use the display functions of the Add-On Installation Tool.


16/21


16 November 2001

Only import the packages at times when there is a low system load. If possible, allapplication servers (except for the central server) must be shut down, and noother users must be logged on to the system. If not, problems can arise

(terminated transactions, problems with synchronization, for example).Procedure1. Call the Add-On Installation Tool (transaction SAINT). The system displays the initial screen.

In the upper half of the screen you can see the add-ons and PCS that have already beeninstalled. The lower half displays the PCS packages to be installed.

2. To search in the EPS directory of the current system for additional installation packages,choose Load . If new packages are found, they are then displayed.

See also: Loading Installation Packages [Page 10] .

3. To begin the installation of a PCS, select the PCS you want from the list of packages that youcan install, and choose Continue .

This can lead to different results:

− The PCS may not be installed in this system since you have not met all of the importrequirements. In this case, these import requirements are then named.

− You need additional packages for the installation. You are shown which packages aremissing. The installation does not start.

Use the Support Package Manager (transaction SPAM) to import these packages.

− Once you have met all the import requirements, the corresponding installation queueappears (in a PCS installation this queue only contains the PCS installation package).You can start the installation process.

4. To start the installation, choose Continue .

After starting the installation, the program runs through a set series of phases. If an error occurs in one of these phases, the installation terminates and the error is described, as far aspossible.

When the problem is corrected, choose Continue .

If you cannot correct the problem, you can reset the installation up to the phaseIMPORT_PROPER (see Phases in the Add-On Installation Tool [Page 19]) by choosingBack .

In later phases the contents of the database have already been changed. Thismeans that you must continue with the installation.


17/21


November 2001 17

Modification AdjustmentUse

You only need to adjust modifications for add-ons .If you have modified SAP objects from the add-on that you want to install, you must adjust theseobjects when you import them. (Transaction SPDD adjusts Dictionary objects, Transaction SPAUadjusts Repository objects.)

PrerequisitesSAINT prompts you to adjust your modifications.

Procedure

1. Stop importing the installation queue by using F12 . (SAINT resumes at the step RUN_SPAUor RUN_SPDD.)

2. To enable your developers to adjust modifications, go to the Transport Organizer and createa request that includes tasks for the developers.

3. Ask the developers to adjust the modifications for their objects.

If you have not yet confirmed the installation, call transaction SAINT and choose Extras → Adjust modifications to go to either transaction SPDD or transaction SPAU.

After the adjustment is completed, the developers must release their tasks and inform you.Modifications can be adjusted in any client.

4. Call transaction SAINT. The screen at which the processing stopped is automaticallydisplayed.

5. Choose Continue . The Support Package Manager again prompts you to adjust themodifications. Since this has already been done, ignore this prompt and choose Continue .

SAINT completes processing and displays the status.


18/21


19/21


November 2001 19

Phases of the Add-On Installation ToolThe following list explains the phases executed by the Add-On Installation Tool in the order inwhich they are performed.

1. PROLOGUE

Initializes installation

2. CHECK_REQUIREMENTS

Checks the Change and Transport System

3. DISASSEMBLE_PATCH

Decompresses the OCS packages

4. ADD_PATCH_TO_BUFFER:

Creates import buffer for the installation

5. IMPORT_OBJECT_LIST

Imports object lists of the OCS packages into the database

6. OBJECTS_LOCKED_?

Checks if objects to be imported are in open transport requests

7. SCHEDULE_RDDIMPDP

Checks if the job RDDIMPDP is scheduled properly

8. ADDON_CONFLICTS_?

This phase exists only when you install or upgrade add-ons (not for PCS).

It checks for object conflicts with imported Support Packages that have a higher version thanis specified in the import prerequisites for the add-on.

If another add-on is already installed, SAINT checks whether there are conflicts between thisadd-on and any Support Packages that were included as import prerequisites for the newadd-on. It also checks whether the new add-on has direct object conflicts with the add-on thatis already installed.

9. CREATE_VERS_BEFORE

Creates versions for the objects of the OCS packages in the installation queue (if this optionhas been selected)

10. SPDD_SPAU_CHECK


Checks if an SPDD/SPAU adjustment is necessary

11. DDIC_IMPORT


Imports the Dictionary objects

12. AUTO_MOD_SPDD



20/21


21/21


Importing a SPAM/SAINT UpdateUse

A SPAM/SAINT Update (SPAM update for short) contains updates and improvements to theSupport Package Manager and the SAP Add-On Installation Tool. There is always one SPAMupdate for each maintenance level release. This update is updated accordingly. You can find theversion in the short description, for example:

SPAM/SAINT update - version /0001

A SPAM update is always the first Support Package in the list of Support Packages in SAPNet -R/3 Frontend. The latest SPAM update is also available in the SAP Service Marketplace under the alias /swcenter-main . The latest version for each component is in the list of the SupportPackages that are available for SAP_BASIS.

Make sure you always have the newest version of SPAM before you import

Support Packages or Installation Packages.

PrerequisitesYou can only import a SPAM update successfully if there are no terminated packages in thesystem.

A dialog box informs you if there are any terminated packages. You then have two options:

• First import the complete queue and then the SPAM update.

• Reset the queue status, import the SPAM update first and then the queue.

Note that you can only delete the queue up until the step SPDD_SPAU_CHECK.

For more information, see Support Package Manager: Steps in the SupportPackage Manager documentation.

Procedure1. Call the Support Package Manager (transaction SPAM).

2. Check if the SPAM update offered is newer than the one in your system. (The current SPAMversion is displayed in the title bar of the initial Support Package Manager screen.)

3. To import the newest SPAM update, choose Support Package → Import SPAM update .

SPAM updates are automatically confirmed after being successfully imported.

Documents

SAP Add on Installation Tool(BC UPG OCS)