emc viewpoint for sap software suite version 2.1 installation … · 2020-02-13 · this guide emc...

EMC ViewPoint for SAP Software SuiteVersion 2.1

INSTALLATION MANUALP/N 300-002-919

REV A04

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

ii

Copyright © 2006 EMC Corporation. All rights reserved.Published August, 2006

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC ViewPoint for SAP Software Suite Installation Manual

Contents

Preface.............................................................................................................................. v

Chapter 1 OverviewIntroducing ViewPoint for SAP ..................................................... 1-2Understanding ViewPoint for SAP versions ............................... 1-3Enterprise Release software delivery............................................ 1-5

Utility transport ........................................................................ 1-7Prior release software delivery ...................................................... 1-8

Utility transport ...................................................................... 1-10PBSWBMod.exe.............................................................................. 1-11

Chapter 2 InstallationPreparing ViewPoint for SAP files for installation ..................... 2-2

Passwords .................................................................................. 2-2Self-extracting files ................................................................... 2-2Zip files....................................................................................... 2-3

Importing ViewPoint for SAP installation files ........................... 2-5TP ................................................................................................ 2-5SE03............................................................................................. 2-6Transaction STMS ..................................................................... 2-7Transaction SAINT ................................................................... 2-7Transaction SPAM..................................................................... 2-8

Enterprise release installation flow ............................................... 2-9Namespace................................................................................. 2-9Utilities ....................................................................................... 2-9Modules...................................................................................... 2-9Updates .................................................................................... 2-10SAP release upgrade .............................................................. 2-10

EMC ViewPoint for SAP Software Suite Installation Manual iii

Contents

Installation verification.......................................................... 2-11Migrating from test to production environment ............... 2-13

Prior release installation flow ...................................................... 2-14Namespace .............................................................................. 2-14Modules ................................................................................... 2-15Updates .................................................................................... 2-15Utilities ..................................................................................... 2-16Upgrades.................................................................................. 2-16Installation verification.......................................................... 2-16ViewPoint for SAP transport history................................... 2-18Migrating from test to production environment ............... 2-19

EMC ViewPoint for SAP Software Suite Installation Manualiv

Preface

As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this manual may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this manual, please contact your EMC representative.

ViewPointfunctionality

This document describes how to install the various components that make up EMC ViewPoint for SAP modules. EMC’s technology allows you to effectively manage your application data by providing the ability to define the access, retention, and service level requirements for any business transaction at each point in its lifecycle.

Audience This guide is part of the ViewPoint documentation set and is intended for use by anyone installing the ViewPoint for SAP modules. It is assumed that the installer has a working knowledge of SAP Basis and has the appropriate levels of responsibilities to perform the tasks described.

EMC ViewPoint for SAP Software Suite Installation Manual v

vi

Preface

Relateddocumentation

Be sure to review the EMC ViewPoint for SAP Release Notes for the most up-to-date information on product features.

The latest release notes and documentation can be found at:

http://Powerlink.EMC.com

Introductory◆ EMC ViewPoint for SAP Release Notes

Installation◆ EMC ViewPoint for SAP Software Suite Installation Manual

Administrative◆ EMC ViewPoint for SAP Modules Administration Manual

User◆ EMC ViewPoint for SAP Modules User Manual

◆ EMC ViewPoint for SAP Modules Utilities User Manual

Conventions used inthis guide

EMC uses the following conventions for notes, cautions, warnings, and danger notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning.

DANGER

A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the message.


Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Normal font In running text:• Interface elements (for example, button names, dialog box

names) outside of procedures• Items that user selects outside of procedures• Java classes and interface names• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, menu names, utilities

• Pathnames, URLs, filenames, directory names, computer names, links, groups, service keys, file systems, environment variables (for example, command line and text), notifications

Bold In procedures:• Names of dialog boxes, buttons, icons, menus, fields• Selections from the user interface, including menu items and

field entries• Key names• Window namesIn running text:• Command names, daemons, options, programs, processes,

notifications, system calls, man pages, services, applica-tions, utilities, kernels

Italic Used for:• Full publications titles referenced in text• Unique word usage in text

Bold Italic Anything requiring extra emphasis

Courier Used for:• System output• Filenames• Complete paths• Command-line entries• URLs

Courier, bold Used for:• User entry• Options in command-line syntax

Courier, italic Used for:• Arguments used in examples of command-line syntax• Variables in examples of screen or file output• Variables in path names

Courier, bold, italic

Variables used in a command-line sample

EMC ViewPoint for SAP Software Suite Installation Manual vii

viii

Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink™ website (registration required) at:


Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.Your comments

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

Comments and suggestions about our product documentation are always welcome.

To provide feedback:

1. Go to:


2. Click the Feedback link.

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the ex-ample


http://powerlink.emc.com

http://powerlink.emc.com

1Invisible Body Tag

This chapter includes these topics:

◆ Introducing ViewPoint for SAP .......................................................1-2◆ Understanding ViewPoint for SAP versions..................................1-3◆ Enterprise Release software delivery ..............................................1-5◆ Prior release software delivery.........................................................1-8◆ PBSWBMod.exe................................................................................ 1-11

Overview

Overview 1-1

1-2

Overview

Introducing ViewPoint for SAPThe EMC® ViewPoint for SAP software suite is an archiving management system for SAP R/3 systems providing transparent, archive viewing support for standard SAP modules.

While it’s possible to keep documents posted indefinitely in an SAP system R/3 database, eventually this leads to performance problems. Keeping optimal SAP system performance requires the database be reorganized regularly and the application data archived. However, the archived data is often no longer completely available to SAP applications.

ViewPoint for SAP modules provide support for each SAP module with a special program package application. All ViewPoint modules can be easily installed in the SAP R/3 system, providing access to previously archived transaction data that is viewed transparently in its native SAP application transaction screens.


Overview

Understanding ViewPoint for SAP versionsThe version of ViewPoint for SAP you install must match the release of your SAP system to ensure your ViewPoint for SAP module functions correctly.

ViewPoint for SAP module software is delivered on CD, or downloaded from Powerlink™, as self-extracting, compressed files. For example, the ViewPoint for SAP Business Warehouse module software is delivered as CBW.exe. Double-clicking on a module file results in a password prompt.

Note: Obtain your password by sending email to [email protected].

Complete installation instructions can be found in Chapter 2, “Installation.”

Once you have extracted your module software you will find the ViewPoint for SAP Business Warehouse module directory structure as shown in Figure 1-1.

Figure 1-1 ViewPoint for SAP Business Warehouse module directory structure

ViewPoint for SAP extracted file directory structures typically contain one or more of the following:

◆ Version-specific folders

◆ Namespace folder

Understanding ViewPoint for SAP versions 1-3

1-4

Overview

◆ Final transport folder

◆ Patch transport folder

“Enterprise Release software delivery” on page 1-5 and “Prior release software delivery” on page 1-8 provide examples of the ViewPoint for SAP module software delivery structure and files.

Complete, step-by-step ViewPoint for SAP installation instructions for transport files are provided in Chapter 2, “Installation.”


Overview

Enterprise Release software deliveryThe Enterprise Release module final release software is delivered as an Installation Package (IP) or Upgrade Package (UP).

The Enterprise Release module update release software is delivered as a Support Package (SP).

Note: From the SAP Enterprise Release the ViewPoint for SAP utilities must be installed or updated before the ViewPoint for SAP modules are installed or updated.

Enterprise patch releases are not cumulative but contain only the modifications since the previous patch.

Namespace foldercontents

The ViewPoint for SAP utilities namespace transport files are shown in Figure 1-3.

Figure 1-2 ViewPoint for SAP namespace transport files

PBS_NSP_IP_#.sarThis is the namespace installation package.

SAPK_NSP10INPBSlog.txtThis is the log file containing the export protocol of the transport stored in the directory.

Enterprise Release software delivery 1-5

1-6

Overview

Final folder contents The ViewPoint for SAP utilities IP and UP transport files are shown in Figure 1-3.

Figure 1-3 ViewPoint for SAP utilities IP and UP transport files

PBS_UTIL_IP_#.sarThis is the utilities installation package.

PBS_UTIL_IP_#_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

PBS_UTIL_UP_#.sarThis is the utilities upgrade package.

PBS_UTIL_UP_#_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

Patch folder contents From SAP Enterprise Release a backup is no longer required for customer-specific modifications. Use the SAP transactions spau and spdd during the import of new transports for entering modifications.


Overview

The ViewPoint for SAP utilities SP transport files are shown in Figure 1-4.

Figure 1-4 ViewPoint for SAP utilities SP transport files

PBS_UTIL_SP_#_#.sarThis is the utilities support package.

PBS_UTIL_SP_#_#_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

Utility transport Beginning with the Enterprise release, install the utility transport before the installation of the final release and/or customer patch.

The utility transport is applied in two or more ViewPoint for SAP archive modules to implement the ViewPoint Translation Tool, Archive Browser, and Conversion Tool.

Enterprise Release software delivery 1-7

1-8

Overview

Prior release software deliveryBefore installing the transport files for the ViewPoint for SAP utilities and the first ViewPoint for SAP module, import the installation package for the namespace /PBS/. All objects of the ViewPoint modules and the ViewPoint utilities are within this namespace and begin with /PBS/.

Note: A separate installation of the ViewPoint namespace is not needed for installation package-type module installation. These are ViewPoint for SAP software packages with a .sar extension. “Enterprise Release software delivery” on page 1-5 has more information.

Namespace foldercontents

The ViewPoint for SAP Business Warehouse module namespace file is shown in Figure 1-5.

Figure 1-5 ViewPoint for SAP Business Warehouse module namespace file

D47K9#####_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

K9#####.D47This is the R/3 transport command file.

R9#####.D47This is the R/3 transport data file.

Final folder contents When installing a ViewPoint for SAP module for the first time, install the contents of the final folder first.


Overview

The ViewPoint for SAP Financial Accounting and Material Documents (CFI) module final transport files are shown in Figure 1-6.

Figure 1-6 ViewPoint for SAP CFI module final transport files

E46K9#####_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

K9#####.E46This is the R/3 transport command file.

R9#####.E46This is the R/3 transport data file.

Patch folder contents Up to release 4.6C, patch releases contain all improvements, corrections, and additions since the delivery of the module final release files.

Always install patch release files after the final release files.

Note: For a ViewPoint for SAP module that is installed and in which you’ve made modifications, copy all changed objects under another name before importing the patch. After importing the patch, update the changes in the newly installed objects.

Prior release software delivery 1-9

1-10

Overview

The ViewPoint for SAP Financial Accounting and Material Documents (CFI) module patch transport files are shown in Figure 1-7.

Figure 1-7 ViewPoint for SAP CFI module patch transport files

E46K9#####_log.txtThis is the log file containing the export protocol of the transport stored in the directory.

K9#####.E46This is the R/3 transport command file.

R9#####.E46This is the R/3 transport data file.

Utility transport At release 4.6C and prior, install the utility transport after the installation of the final release and/or customer patch.

The utility transport is applied in two or more ViewPoint for SAP archive modules to implement the ViewPoint Translation Tool, Archive Browser, and Conversion Tool.


Overview

PBSWBMod.exePBSWBMod.exe is required to convert workbooks for archive support through the ViewPoint for SAP WB Administration Cockpit. Copy this file into a local directory of Microsoft Windows. The selected path must be registered in the Cockpit. Complete information is in the EMC ViewPoint for SAP Modules Administration Manual.

The ViewPoint for SAP PBSWBMod.exe file is shown in Figure 1-8.

Figure 1-8 ViewPoint for SAP PBSWBMod.exe file

PBSWBMod.exe 1-11

1-12

Overview


2Invisible Body Tag

This chapter contains the following topics:

◆ Preparing ViewPoint for SAP files for installation........................2-2◆ Importing ViewPoint for SAP installation files .............................2-5◆ Enterprise release installation flow .................................................2-9◆ Prior release installation flow.........................................................2-14

Installation

Installation 2-1

2-2

Installation

Preparing ViewPoint for SAP files for installationPreparing ViewPoint for SAP files for installation, either from the ViewPoint for SAP CDs or as downloads from Powerlink, requires a Windows-based system. Once the files are extracted they are ready for import into your SAP R/3 system.

Check your SAP environment for the most current version of SAINT/SPAM before installing a ViewPoint module. Otherwise, import the current version SAINT/SPAM update available from SAP.

Passwords Self-extracting files with a .exe extension are password-protected. Contact [email protected] for the passwords for the modules you purchased. Obtain these passwords before beginning “Self-extracting files”.

Be sure to include the module names for which you need passwords in the email you send to [email protected].

Self-extracting files Follow this procedure to extract the contents of ViewPoint for SAP .exe files to your local Windows system to prepare the transport files for import into your SAP R/3 system.

1. Either insert the ViewPoint for SAP CD into your CD-ROM drive or log in to Resources/Tools > CS Support > Downloads and Patches in Powerlink.

Note: You must be a registered ViewPoint for SAP customer and Powerlink user to log in to the Downloads and Patches area of Powerlink.

2. Double-click on the self-extracting file you want to prepare for import into your SAP R/3 system—for example, CFI.EXE.

Note: If you prefer to copy the contents of both CDs, or download all the files from Powerlink, to your local drive, make sure you have 1.2 GB of available disk space.

You will need an additional 1.8 GB of available disk space if you choose to extract all files to your local drive.


Installation

The Zip 2 Secure EXE window appears, as shown in Figure 2-1.

Figure 2-1 Zip 2 Secure EXE window

3. Browse to a temporary folder you create to which you want to extract the SAP transport files—for example, ViewPoint_SAP.

4. Select Unzip.

The Enter Password window appears, as shown in Figure 2-2.

Figure 2-2 Enter Password window

5. Enter your ViewPoint for SAP password and select OK. “Passwords” on page 2-2 contains additional information.

The Status window appears with confirmation that the transport files have been extracted to the temporary folder you created.

6. Select OK > Close to exit the file extraction utility.

Repeat this procedure for each file you want to extract to your local drive and prepare for import into your SAP R/3 system.

Zip files Follow this procedure to extract the contents of ViewPoint for SAP .zip files to your local Windows system to prepare the transport files for import into your SAP R/3 system.

Preparing ViewPoint for SAP files for installation 2-3

2-4

Installation

Extract these two patch .zip files included on the ViewPoint for SAP CDs using the following default paths in your SAP R/3 system code tree:

◆ CFI_46C_DELTAPATCH.ZIP — EMC\Produkte_R3\CFI\46c\R3\patch

◆ CHECKADKTOOL_PATCH.ZIP — EMC\Produkte_R3\Utilities\47all\R3\patch

Extract these two patch .zip files included on the ViewPoint for SAP CDs to a temporary directory. Copy to the following module paths in your ViewPoint code tree. For example:

◆ ORDER.zip —\ViewPoint\Order\Order\47all\R3_Order\final\

PBS_ORD_IP_2.sar

\ViewPoint\Order\Order\47all\R3_Order\final\

PBS_ORD_UP_2.sar

\ViewPoint\Order\Order\47all\R3_Order\patch\

PBS_ORD_SP_2_1.sar

\ViewPoint\Order\Order\47all\R3_Order\patch\

PBS_ORD_SP_2_2.sar

◆ UTILITIES.zip —\ViewPoint\Utilities\Utilities\47all\R3\final\

PBS_UTIL_IP_2.sar

\ViewPoint\Utilities\Utilities\47all\R3\final\

PBS_UTIL_UP_2.sar

\ViewPoint\Utilities\Utilities\47all\R3\PBS_Namespc\

PBS_NSP_IP_1.sar

Extract these two patch .zip files included on the ViewPoint for SAP CDs to a temporary directory.

◆ ViewPoint_Patch1.zip

◆ ViewPoint_Patch2.zip

Copy to the appropriate module path in your ViewPoint code tree. For example:

◆ \ViewPoint\ViewPoint_Patch2\EMC_OEM2\CAB\46C\K901473.K46

◆ \ViewPoint\ViewPoint_Patch2\EMC_OEM2\CAB\46C\R901473.K46


Installation

Importing ViewPoint for SAP installation filesViewPoint for SAP uses SAP standard transport management tools for installation.

The EMC ViewPoint for SAP Release Notes list the latest module transport files available for installation.


TP Follow these steps to import the transport files into your SAP system using TP.

Note: If the filename converts from uppercase to lowercase during the transport, manually change the filename back to uppercase.

In a Windows/NT environment you may have to deactivate the read-only file attribute.

1. Change directory to /usr/sap/trans/bin.

2. Transfer the transport into the buffer with this tp command:

tp addtobuffer yyyK9zzzzz <target system>

Where:

yyy = name of the ViewPoint delivery system

zzzzz = current transport number

3. Start the import with the following command:

tp import yyyK9zzzzz <target system> client=xxx

Where:

xxx = client

yyy = name of the ViewPoint delivery system


Importing ViewPoint for SAP installation files 2-5

2-6

Installation

Note: The ViewPoint for SAP module can be imported in any client you like.

Possible TP error If the TP command terminates with this error message:

E-TPSETTINGS could not be opened.

ERRORS: Highest tp internal error was: 0212 tp finished with return code: 212

Use this additional parameter:

pf = TP_DOMAIN_XYZ.PFL

Where XYZ = system name of the domain controller

The profile file TP_DOMAIN_XYZ.PFL (with the correct name) is stored in the directory /usr/sap/trans/bin.

SE03 Follow these steps to define a new namespace manually for ViewPoint for SAP.

1. Use transaction SE03 as follows:

Transport Organizer Tools > Display/Change Namespace

2. Enter the license number 37592095353215894074 and qualify namespace with C as shown in Figure 2-3.

3. Set the system changeability for this namespace as follows:

Transport Organizer Tools > Set System Change Option

Figure 2-3 Manual creation of the ViewPoint for SAP namespace


Installation

Transaction STMS Follow these steps to import an installation package from any directory with transaction STMS.

1. Log in to your SAP system as client 000.

2. Call transaction STMS and load the installation packages into the SAP system with this menu option:

Import queue > display

Extras > other requests > add (search and specify the request name)

Transaction SAINT Follow these steps to import an installation package from any directory with transaction SAINT.


2. Call transaction SAINT and load the installation packages into the SAP system with this menu option:

Installation Package > Load packages > From the front end

3. After marking the package to be installed, select Öffnen (Open) and then Dekomprimieren (Decompress), as shown in Figure 2-4.

Figure 2-4 Loading a module installation package with SAINT

Importing ViewPoint for SAP installation files 2-7

2-8

Installation

4. Select Continue, as shown in Figure 2-5, and then Start.

Figure 2-5 Module installation with package SAINT

5. Mark the package to be installed and install it by selecting Continue.

Transaction SPAM A Support Package for a final release of the ViewPoint for SAP module is installed after the installation of the final release. Support Packages are not cumulative and are imported one after another in ascending order.

Follow these step to import a support package from any directory with transaction SPAM.


2. Call transaction SPAM and load the support package into the SAP system with the menu option:

Support package > Import queue

Note: If you made modifications in the namespace /PBS/, you will be able to compare modifications with transactions SPAU and SPDD.


Installation

Enterprise release installation flowFollow this installation flow for a ViewPoint for SAP installation into an SAP enterprise release.

Namespace Import the PBS_NSP_IP_1.sar installation package for the namespace /PBS/before installing the ViewPoint for SAP utilities and the first ViewPoint for SAP module. All objects of the ViewPoint for SAP modules and the ViewPoint for SAP utilities are within this namespace and begin with /PBS/.

Note: Import the PBS_NSP_IP_1.sar installation package even if the namespace already exists in your system from a previous, older SAP release level to make all necessary definitions available in the system for use with the Modification Assistant. The newer namespace is also checked in the upgrade packages of the utilities.

The package PBS_NSP_IP_1.sar has to be imported only once prior to all utility and module installations.

Use the SAP transaction SAINT to import the PBS_NSP_IP_1.sar installation package located in the Utilities\47all\R3\Namespc directory.

You can find more information on “Transaction SAINT” on page 2-7.

After importing the installation package PBS_NSP_IP_1.sar you can display the ViewPoint for SAP namespace screen and repair license with transaction SE03.

You can find more information on “SE03” on page 2-6.

Utilities Use the SAP transaction SAINT to import the PBS_UTIL_IP_2.sar installation package located in the Utilities\47all\R3\final directory.


Modules Use the SAP transaction SAINT to import the PBS_<module>_IP_#.sar installation package located in the <module>\47all\R3\final directory.


Enterprise release installation flow 2-9

2-10

Installation

Note: You need the repair license listed in “SE03” on page 2-6 if you intend to define own modifications in the ViewPoint for SAP programs.

Creation of theViewPoint-specific file

path

In order to store ViewPoint for SAP module flat files separately from other data, you must create a physical path directly in the SAP file system. Create an own file directory like ".../pbs/cfi/" for each ViewPoint for SAP module. Some ViewPoint for SAP modules can address logical path names (in analogy to SAP ADK). In this case, you may eventually omit the creation of an own physical path.

Updates Updates are supplied as an Upgrade Package (UP) or Support Package (SP), depending if the update type is a final release or a new customer patch.

Upgrade package(UP)

A new final release is supplied as an upgrade package and is imported with transaction SAINT.


Support package (SP) Depending on the update level, a current Customer Patch may exist as a Support Package. This Customer Patch must be installed after the installation of the Final Release. Support Packages are not cumulative for SAP Enterprise Release support, and must be imported one after another in ascending order.

Call transaction SPAM in client 000 for the import of the support package.

You can find more information on “Transaction SPAM” on page 2-8.

If you have made modifications in the namespace /PBS/, compare them with transactions SPAU and SPDD during the Support Package import process.

You need the repair license listed in “SE03” on page 2-6 if you intend to define own modifications in the ViewPoint for SAP programs. As the namespace role for the ViewPoint for SAP namespace has the entry C in your system, the modification assistant is called automatically in case of any changes in the ViewPoint for SAP programs - for example, with transaction SE38.

SAP release upgrade

ViewPoint for SAP modules remain in the SAP system during the upgrade of the SAP system to a higher release.


Installation

During the SAP system upgrade choose one of the following options:

◆ Delete — To delete the ViewPoint for SAP module

◆ Keep — To keep the ViewPoint for SAP module

◆ Keep (with vendor key) — To keep the ViewPoint for SAP module when Keep can’t be selected. Contact EMC Support to obtain the vendor key.

Although the ViewPoint for SAP module remains unchanged in the SAP system, a new namespace installation is required for the higher SAP release, starting with the correct PBS_NSP_IP_1.sar installation package release level. Also install the correct installation package for the ViewPoint for SAP utilities and modules. To upgrade within the same SAP release level, install the current Upgrade Package.

A new setup of the archive data is not usually required.

Installation verification

Use the following methods to verify your ViewPoint for SAP installation.

SAINT Use transaction SAINT to determine the exact installation level of each module at any time. Scroll down to the required module in the initial screen of the transaction as shown in Figure 2-6.

Figure 2-6 Installation check with SAINT

The ViewPoint for SAP CCO module information is displayed in the bottom line of this example. The column Release indicates that the current imported final release is No. 3. The column Level shows that Customer Patch No. 1 was subsequently imported. If you scroll a little to the right, you can also see the name of the OCS package of the


2-12

Installation

CCO Final Release No. 3: SAPK-CCO3UINPBS as shown in Figure 2-7.

Figure 2-7 OCS Package Name

SPAM You can display detailed information on the imported Support Packages in transaction SPAM as shown in Figure 2-8.

Figure 2-8 Installation check in SPAM

The current imported Customer Patch No. 1 for Final Release No. 3 consists of the OCS package SAPK-CCO31INPBS.

This example shows that both import conditions were met for requirement set 01.


Installation

The CCO Final Release No. 3 (PBS_CCO,CCO_3_470) and the ViewPoint for SAP utilities with release level UTI_1_470 were imported in advance.

Transport logs Follow this procedure to read the transport logs of the OCS packages.

1. Call transaction SE01.

2. Select the Display tab.

3. Enter the OCS package name in Request/Task field.

4. Select Logs.

Migrating from test to production environment

Follow the scenario that best matches your system environment.

Scenario 1:Production and test

system on samecomputer

If both the production system and test system in which you have imported the ViewPoint for SAP CBW are on the same computer, the only difference is the client number.

No action is required as all changes are active immediately and are available in your production system.

Scenario 2:Production and testsystem on different

computers

If the production system and test system are not installed on the same computer, first import all of the ViewPoint for SAP CBW packages (installation/Upgrade Package as well as the Support Packages) into the production system in the same sequence as in the test system.

All customer-specific modifications (and other repairs) to the ViewPoint for SAP CBW that were executed in the test system are then exported via the transport system. A transport request that must be released in the Transport Organizer has usually been created for this purpose. After the export process has been completed successfully you can import this transport request into your production system using the tp transport program.

You can find more information on “TP” on page 2-5.


2-14

Installation

Prior release installation flowFollow this installation flow for a ViewPoint for SAP installation into an SAP 4.6C or prior release.

Namespace All objects of the ViewPoint for SAP modules and utilities are within the ViewPoint for SAP namespace and begin with /PBS/. Define this namespace in your SAP system to carry out changes or customer-specific modifications in the ViewPoint for SAP modules.

Automatic creation To automatically create the ViewPoint for SAP namespace with all necessary definitions, install transport HE4K902993 located in directory PBS/utilities/R3/Namespc using either transactions STMS or TP.


You can find more information on “Transaction STMS” on page 2-7.

Manual creation To define the ViewPoint for SAP namespace manually use transaction SE03 as shown in Figure 2-9.

1. Enter repair license number 37592095353215894074

2. Qualify namespace with C.

3. Set the system changeability for this namespace with Transport Organizer Tools > Set System Change Option.

You can find more information on “SE03” on page 2-6.

Figure 2-9 Creating the ViewPoint for SAP namespace


Installation

Modules Transfer both the command and data files into the SAP system using either TP or STMS.

Note: ViewPoint for SAP modules can be imported in any client you like except for CFI, which must be installed in a client other than 000. Otherwise the tables for the line construction variants cannot be updated. If the option 'client =xxx' is left out, the programs will be installed into client 000.

Creation of theViewPoint-specific file

path

In order to store ViewPoint for SAP module flat files separately from other data, you must create a physical path directly in the SAP file system. Create an own file directory like ".../pbs/cfi/" for each ViewPoint for SAP module. Some ViewPoint for SAP modules can address logical path names (in analogy to SAP ADK). In this case, you may eventually omit the creation of an own physical path.

Updates Depending on the update level, a current customer patch may exist for a specific final release of a ViewPoint for SAP module and must be installed after the installation of the final release.


Update installation is similar to initial installation, the only exception being the following TP import command parameters:

tp import yyyK9zzzzz <target system> U26 client=xxx

xxx = client

yyy = name of the ViewPoint for SAP delivery system


The parameter U26 signifies unconditional modes 2 and 6, meaning during the import existing objects and repaired objects are overwritten.

Note: To repeat an imported transport because the previous installation was incomplete or cancelled, use parameter U126.


Prior release installation flow 2-15

2-16

Installation

Utilities Use transaction TP or STMS to import the K902993.HE4 and R902993.HE4 installation packages located in the Utilities\46C\R3\namespc directory.



Upgrades Upgrade the ViewPoint for SAP modules when you upgrade the SAP system to a higher release. Since the previous ViewPoint for SAP module releases are overwritten, reinstall the ViewPoint for SAP modules beginning with the procedure listed in “Updates” on page 2-15.

A new construction of the archive data usually is not necessary

Installation verification

The transport protocols in the SAP system display whether the installation of the ViewPoint for SAP module was successful.

1. From the start menu, call the transport administration as follows:

Tools > ABAP/4 Workbench > Overview > Transport Organizer > Request/Task > Display individually

or using transaction SE09 as follows:

> Request/Task > Display individually


Installation

2. Enter the transport number of the ViewPoint for SAP module as shown in Figure 2-10.

Figure 2-10 Selection of the imported ViewPoint for SAP transport request

3. In the selection result, move to the number of the transport request and right-click transport logs as shown in Figure 2-11.

Figure 2-11 Transport logs selection

4. In the resulting list, click on system identification > Import.


2-18

Installation

5. Open the resulting list for the required information, as shown in Figure 2-12.

Figure 2-12 Analysis transport order

ViewPoint for SAP transport history

A special transaction is contained in all ViewPoint for SAP modules to manage and control the history of the installed module transport orders.

1. Start the ViewPoint for SAP module transport history from the ViewPoint for SAP main menu as follows:

ViewPoint for SAP Menu > Utilities > General Tools > Transport Search

or use transaction code Z9CP for 3.x releasesor /PBS/UTIL_Z9CP for release 4.0B and later


Installation

The ViewPoint for SAP transport requests installed in your system are displayed according to the transport number, in declining order, as shown in Figure 2-13.

Figure 2-13 ViewPoint for SAP transport history

2. Use the selection fields above the list to limit the number of transport requests shown in the list.

The Transport no. column contains the number of the ViewPoint for SAP transport order.

The System, User, Date, and Description columns contain additional ViewPoint for SAP module transport information for identification purposes.

Use this information when transferring the ViewPoint for SAP module into production or when contacting EMC support.

Migrating from test to production environment

Follow the scenario that best matches your system environment.

Scenario 1:Production and test

system on samecomputer

If both the production system and test system in which you have imported the ViewPoint for SAP CBW are on the same computer, the only difference is the client number.

No action is required as all changes are active immediately and are available in your production system.

Scenario 2:Production and testsystem on different

computers

If the production system and test system are not installed on the same computer, export all customer-specific modifications and other repairs of the ViewPoint for SAP modules using the transport system before you transport the ViewPoint for SAP modules into production.


2-20

Installation

Create a transport orderCreate a transport order for release using the Workbench Organizer and transport the ViewPoint for SAP modules into the R/3 production system with the following procedure.

1. Determine the number of the transport order used to install the ViewPoint for SAP module in your test system using one of the following methods.

a. Use the transport history as described in “ViewPoint for SAP transport history” on page 2-18.

b. Find the number in the SAP system using:

Tools > ABAP Workbench > Utilities > Maintenance > Corrections > Request > Find > Transport Request (up to release 3.1z)

or

Tools > ABAP Workbench > Utilities > Maintenance > Transport Organizer > Request/Task > Find Requests (from release 4.0b and later)

2. Enter the ViewPoint for SAP source system in the Correction/TR name field.

3. Record the required ViewPoint for SAP transport number displayed.

Continue with “Create a transport request up to release 3.1z” or with “Create a transport request from release 4.0B” on page 2-22.

Create a transport request up to release 3.1zCreate a transport request up to release 3.1z using the following procedure:

1. Call transaction SE01 (transport system) > Request > Create.

Table 2-1 ViewPoint for SAP module source systems

Release 3.1 4.0 4.5 4.6 Enterprise ECC 5.0

Up to now E31 HE4 E45 - - -

New delivery concept ID1 ID4 ID5 E46/I46 I47 K50


Installation

2. Select Transport of copies in the resulting screen, as shown in Figure 2-14.

Figure 2-14 Create transport order under release 3.x

3. Enter a note for the transport request being created under Short description.

4. Save your transport request.

5. Select > Transport request > Include template.

6. Enter the transport of the original ViewPoint for SAP transport you recorded in “Create a transport order” Step 3 on page 2-20 into the template window.

The transport request can now be released and exported.

Note: To make additions or changes to the object list of the transport request, carry out the modifications before release and export.


2-22

Installation

Once the export procedure is complete, import this transport request into your productive system using TP or STMS.



Create a transport request from release 4.0BCreate a transport request from release 4.0B using the following procedure:

1. Call transaction SE01 (transport organizer) or use:

Tools > Administration > Transports > Transport Organizer

2. Select Transports of copies and relocs.

3. Create an order with > Request > Create.

4. Select Transport of copies as shown in Figure 2-15.

Figure 2-15 Create transport order from 4.0B


Installation

5. Enter a note for the request created into the Short description field.

6. Save your transport.

7. Integrate the original PBS transport number you recorded in “Create a transport order” Step 3 on page 2-20 into the current transport request using the following:

> Request/Task > Object List > Include Objects

or use key combination CTRL + F11.

The transport request is automatically released and exported.

Note: To make additions or changes to the object list of the transport request, carry out the modifications before release and export.

Once the export procedure is complete, import this transport request into your productive system using TP or STMS.




2-24

Installation
