emc viewpoint for sap bw module version 2.0 installation ... · vi emc viewpoint for sap cbw module...

EMC ViewPoint for SAPBW Module

Version 2.0

INSTALLATION MANUALP/N 300-003-414

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

ii

Copyright © 2006 EMC Corporation. All rights reserved.Published February, 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 CBW Module Installation Manual

Contents

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

Chapter 1 ViewPoint for SAP BW Module ConceptSAP BW database............................................................................. 1-2SAP archiving ................................................................................... 1-3ViewPoint nearline storage concept.............................................. 1-4

Chapter 2 The ViewPoint Concept for Software DeliveriesFinal release ...................................................................................... 2-2Customer patch ................................................................................ 2-3Delivery ............................................................................................. 2-4

Chapter 3 Installation for SAP BW 3.0 and 3.1SAP put level and hot packages .................................................... 3-2ViewPoint namespace ..................................................................... 3-3Initial installation ............................................................................. 3-4

TP import ................................................................................... 3-5Installation of updates..................................................................... 3-6Check of installed transport ........................................................... 3-7ViewPoint transport history ........................................................... 3-9Transport into the production system......................................... 3-10

System environment 1............................................................ 3-10System environment 2............................................................ 3-10

Installation summary .................................................................... 3-12Peculiarities in operating system AS/400 .................................. 3-13

Chapter 4 Installation for SAP BW 3.5

EMC ViewPoint for SAP CBW Module Installation Manual iii

Contents

SAP put level and hot packages .................................................... 4-2Initial installation............................................................................. 4-3

Import with transaction SAINT ............................................. 4-4Installation of updates .................................................................... 4-6Transport into production system................................................. 4-7

System environment 1 ............................................................. 4-7System environment 2 ............................................................. 4-7

Summary........................................................................................... 4-8

EMC ViewPoint for SAP CBW Module 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 Construction and Maintenance (CBW) Module. 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 CBW Module. 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 CBW Module 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 following list of related documents are available on the EMC ViewPoint for SAP Documentation CD that was delivered with your EMC ViewPoint SAP software CD.

Both the release notes and documentation CD can be found at:

http://Powerlink.EMC.com

Introductory� EMC ViewPoint for SAP Documentation CD

� EMC ViewPoint for SAP Release Notes

Installation� EMC ViewPoint for SAP Modules Installation Manual

� EMC ViewPoint for SAP Analyzer Plus Installation and User Manual

� EMC ViewPoint for SAP BW Analyzer Installation Manual

� EMC ViewPoint for SAP Construction and Maintenance Installation Manual

� EMC ViewPoint for SAP Fiscal Year Reporter Module Installation and User Manual

Miscellaneous� EMC ViewPoint for SAP Material Master Data, Batches, Special

Stocks, and BOMs Module Modification Manual

Administrative� EMC ViewPoint for SAP Controlling Line Items Module

Administration Manual

� EMC ViewPoint for SAP Financial Accounting and Material Documents Module Administration Manual

� EMC ViewPoint for SAP Purchasing Module Administration Manual

� EMC ViewPoint for SAP Sales and Distribution Module Administration Manual

� EMC ViewPoint for SAP Production Orders Module Administration Manual

� EMC ViewPoint for SAP Agency Business Module Administration Manual

� EMC ViewPoint for SAP Construction and Maintenance Module Administration Manual


Preface

� EMC ViewPoint for SAP Costing-Based Profitability Analysis Module Administration Manual

� EMC ViewPoint for SAP Master Data Changes Module Administration Manual

� EMC ViewPoint for SAP Data Retention Tool Module Administration Manual

� EMC ViewPoint for SAP Contract Account Documents Module Administration Manual

� EMC ViewPoint for SAP HR Archiving Objects Module Administration Manual

� EMC ViewPoint for SAP Material Ledger Documents Module Administration Manual

� EMC ViewPoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module Administration Manual

� EMC ViewPoint for SAP Controlling Orders Module Administration Manual

� EMC ViewPoint for SAP Profit Center Line Items Module Administration Manual

� EMC ViewPoint for SAP Plant Maintenance Module Administration Manual

� EMC ViewPoint for SAP Production Orders Module Administration Manual

� EMC ViewPoint for SAP Process Orders Module Administration Manual

� EMC ViewPoint for SAP Project Systems Module Administration Manual

� EMC ViewPoint for SAP Line Items Module Administration Manual

� EMC ViewPoint for SAP Special Ledger Module Administration Manual

� EMC ViewPoint for SAP Warehouse Management Module Administration Manual

� EMC ViewPoint for SAP Custom Module Administration Manual

User� EMC ViewPoint for SAP Analyzer Plus Installation and User Manual

� EMC ViewPoint for SAP Analyzer Lite Installation and User Manual

EMC ViewPoint for SAP CBW Module Installation Manual vii

viii

Preface

� EMC ViewPoint for SAP Analyzer BW User Manual

� EMC ViewPoint for SAP Controlling Line Items Module User Manual

� EMC ViewPoint for SAP Financial Accounting and Material Documents Module User Manual

� EMC ViewPoint for SAP Purchasing Module User Manual

� EMC ViewPoint for SAP Sales and Distribution Module User Manual

� EMC ViewPoint for SAP Production Orders Module User Manual

� EMC ViewPoint for SAP Modules Utilities User Manual

� EMC ViewPoint for SAP Agency Business Module User Manual

� EMC ViewPoint for SAP Construction and Maintenance Module User Manual

� EMC ViewPoint for SAP Costing-Based Profitability Analysis Module User Manual

� EMC ViewPoint for SAP Master Data Changes Module User Manual

� EMC ViewPoint for SAP Contract Account Documents Module User Manual

� EMC ViewPoint for SAP HR Archiving Objects Module User Manual

� EMC ViewPoint for SAP Material Ledger Documents Module User Manual

� EMC ViewPoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module User Manual

� EMC ViewPoint for SAP Controlling Orders Module User Manual

� EMC ViewPoint for SAP Profit Center Line Items Module User Manual

� EMC ViewPoint for SAP Plant Maintenance Module User Manual

� EMC ViewPoint for SAP Production Orders Module User Manual

� EMC ViewPoint for SAP Process Orders Module User Manual

� EMC ViewPoint for SAP Project Systems Module User Manual

� EMC ViewPoint for SAP Special Ledger Module User Manual

� EMC ViewPoint for SAP Export Interface for Special Ledger Data User Manual

� EMC ViewPoint for SAP Warehouse Management Module User Manual


Preface

� EMC ViewPoint for SAP Fiscal Year Reporter Module Installation and 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.

Typographical ConventionsEMC uses the following type style conventions in this guide:

bold • User actions (what the user clicks, presses, or selects)• Interface elements (button names, dialog box names)• Names of keys, commands, programs, scripts, applications,

utilities, processes, notifications, system calls, services, applications, and utilities in text

italic • Book titles• New terms in text• Emphasis in text

Courier • Prompts • System output • Filenames • Pathnames• URLs • Syntax when shown in command line or other examples

EMC ViewPoint for SAP CBW Module Installation Manual ix

x

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:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required.

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 guide to:

[email protected]

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

Courier italic • Arguments in examples of command-line syntax• Variables in examples of screen or file output• Variables in pathnames

<> Angle brackets for parameter values (variables) supplied by user.

[] Square brackets for optional values.

| Vertical bar symbol for alternate selections. The bar means or.

... Ellipsis for nonessential information omitted from the example.


http://powerlink.emc.com

1Invisible Body Tag

This chapter includes these topics:

� SAP BW database...............................................................................1-2� SAP archiving .....................................................................................1-3� ViewPoint nearline storage concept ................................................1-4

ViewPoint for SAP BWModule Concept

ViewPoint for SAP BW Module Concept 1-1

1-2

ViewPoint for SAP BW Module Concept

SAP BW databaseIn principle, you can keep records stored in a SAP BW system in a database as long as you want, as there are only wide limits with regard to the capacity of the database in the BW system. Depending on the document volume, this leads sooner or later to performance problems. Moreover, in case of large data stocks, a daily back up can only be carried out with difficulties. To keep the complete SAP BW system performance all the time, the database must be reorganized regularly and the application data has to be archived with SAP means (transaction SARA). However, in such cases the archived data is no longer available to the queries in SAP BW. This collides with the users’ justified demand to have the transaction data available for online processing as long as possible.



SAP archivingDuring SAP archiving, a sequential archive data stock is created. This stock is stored in the file system on magnetic disks or in a separate archive system (HSM; optical archive).

However, after archiving the SAP BW system no longer provides the possibility to access the data directly and selectively for executing BW evaluations (queries). It is only possible to reload the data, if necessary, from the archive into a copy of the original InfoProvider. Using the MultiProvider consisting of the original InfoProvider and the copy the data can be made available again for evaluation purposes. But the data puts load on the database again during this period and additional administrative work is necessary.

SAP archiving 1-3

1-4


ViewPoint nearline storage conceptBy developing the ViewPoint BW Module, EMC® has created a Nearline Storage concept for SAP BW systems avoiding the problems mentioned before. In SAP R/3 systems, the ViewPoint modules, representing an analogue archiving concept, have been used with great success for several years.

From experience, data stocks of previous years which are in the database of a productive SAP BW system are required very scarcely for evaluation purposes. Archiving regularly with the SAP transaction SARA a considerable part of the InfoProvider data can be archived and deleted from the database. This results in a noticeable acceleration of the query runtimes.

After SAP archiving, the ViewPoint index generation programs transfer this archive data into the ViewPoint BW Module. The ViewPoint index dataset is stored in flat files in the SAP file system. The direct access to the archive data is realized via queries, which are completely integrated into the BW system by the MultiProvider concept. They allow the user to display not only the data from the SAP system but also the archive data. The user has the impression that the archived data would still exist in the SAP database.

In the ViewPoint BW Module, secondary indices are constructed for the archive data in the file system. They guarantee an extremely good performance for access to the archive data.

A regular back up of the archive data and index data is not necessary, as the archive data is not changed anymore. You thus gain the time required for data back up which normally (without archiving and ViewPoint BW Module) would be spent to save the SAP BW database.

The archive data and index data are stored in compressed form in flat files on magnetic disks. During this process, you achieve an optimal use of the storage capacity of the magnetic disk with compression rates from 80 percent to 90 percent.


2Invisible Body Tag

This chapter includes these topics:

� Final release ........................................................................................2-2� Customer patch ..................................................................................2-3� Delivery ...............................................................................................2-4

The ViewPoint Conceptfor Software Deliveries

The ViewPoint Concept for Software Deliveries 2-1

2-2

The ViewPoint Concept for Software Deliveries

Final releaseThe final release of the ViewPoint BW Module is a complete and extensively tested program package for the ViewPoint BW Module and is always created for each different SAP BW Release (3.0, 3.1, 3.5, …). The final release contains all components described in the user manual (parts A, B, C) and can run on its own. When installing the ViewPoint BW Module for the first time, the "Final Release" must be installed first.

From release 3.5 an Installation Package (IP) or Upgrade Package (UP) is supplied as Final Release. The only exception is the first Final Release for which only the Installation Package is supplied.

Installation and Upgrade Package contain the same objects with the same development level. Therefore, only one of both packages is always required. For the initial installation of the ViewPoint module or for an update the current Installation Package should always be installed after changing the SAP release. However, for an upgrade of the ViewPoint software the Upgrade Package should be installed after an installation in SAP BW 3.5 was already made before.



Customer patchHaving supplied a "Final Release" for the ViewPoint BW Module, improvements, corrections and additions of the module are produced within the ViewPoint development strategy. To provide the users of the ViewPoint modules with these news in an easy way for each "Final Release" so-called "Customer Patches" are supplied. The "Customer Patches" are numbered in chronological order. Up to release 3.1 each current "Customer Patch" contains all improvements, corrections and additions since the delivery of the corresponding "Final Release".

From SAP BW 3.5 the customer patches are no longer provided cumulatively as support packages, but only contain the modifications since the creation of the previous customer patch. Therefore, all support packages have to be imported which are supplied with the current final release and which have not been installed in the system yet.

If you have once purchased and installed a ViewPoint BW Module, you can ask for new "Customer Patches" within certain periods or if necessary (either by phone or Internet). You will only have to import these relatively small correction transports in order to update your ViewPoint BW Module. A "Customer Patch" is to be installed always after the installation of the "Final Release".

Customer patch 2-3

2-4


DeliveryThe programs and documentation for the ViewPoint BW Module are supplied on CD ROM or as FTP download. The delivery of each module contains:

Transport files with all required programs and data files (tables, table entries, data definitions etc.) File directory: \BW with the subdirectories \final for the transports of the Final Release and \patch for those of the Customer Patches.

If you are not able to import the transport files into your system from CD ROMs, we also supply components of the ViewPoint BW Module on 3,5" diskettes or per email (zipped data) on request.

The FTP download or the CD ROM you have received contains a directory with the abbreviation of the name of the ViewPoint BW Module as well as a reference number referring to the SAP BW release, as shown in Figure 2-1, “Structure of delivery of ViewPoint BW Module.”

Figure 2-1 Structure of delivery of ViewPoint BW Module


3Invisible Body Tag

The version of the ViewPoint BW Module must match the release of your SAP BW system to guarantee a correctly working ViewPoint module. Currently, the releases 3.0B and 3.1C are supported.

For the installation the transport control program "tp" (= transports and puts) of SAP AG is used. tp is a tool to control and realize transports between SAP systems.

This chapter contains the following topics:

� SAP put level and hot packages ......................................................3-2� ViewPoint namespace .......................................................................3-3� Initial installation ...............................................................................3-4� Installation of updates.......................................................................3-6� Check of installed transport .............................................................3-7� ViewPoint transport history .............................................................3-9� Transport into the production system...........................................3-10� Installation summary.......................................................................3-12� Peculiarities in operating system AS/400 ....................................3-13

Installation for SAP BW3.0 and 3.1

Installation for SAP BW 3.0 and 3.1 3-1

3-2

Installation for SAP BW 3.0 and 3.1

SAP put level and hot packagesEMC always develops the ViewPoint BW Module based on the current SAP Put Level, supplemented with the latest available Hot packages. ViewPoint attempts to keep all modules downward compatible to the corresponding Hot packages. However, in some cases conflicts and related problems may occur when installing respectively running certain ViewPoint programs due to different Hot package levels (Customer <> ViewPoint). Should you face such a situation please contact EMC Professional Services as soon as possible so that the problems can be solved soon.



ViewPoint namespaceAs a software partner of SAP AG, a special namespace for development purposes was reserved for ViewPoint. All objects of the ViewPoint BW Module are within this namespace and begin with /PBS/. You have to define this namespace in your SAP system before installing the ViewPoint BW Module. Please take care that the repair license number is entered correctly, as shown in Figure 3-1, “Creating the ViewPoint namespace.”

Note: Instead of manually creating the namespace via SE03, you can install transport D47K900005 supplied with the ViewPoint modules (CD ROM directory: CBW - BW - Namespc). All necessary definitions are then carried out automatically.

If you want to define the new namespace manually, as shown in Figure 3-1, “Creating the ViewPoint namespace,” use transaction SE03 (Transport Organizer Tools > Display/Change Namespace).

Enter the license number "37592095353215894074" and qualify namespace with "C".

Then set the system changeability for this namespace (Transport Organizer Tools > Set System Change Option).

Figure 3-1 Creating the ViewPoint namespace

ViewPoint namespace 3-3

3-4


Initial installationEnter the subdirectory on the CD ROM of the transport files (e.g., \CBW\30all\BW\final). The corresponding directory has for example the content shown in Figure 3-2, “Transport files on ViewPoint CD ROM.”

Figure 3-2 Transport files on ViewPoint CD ROM

File K9000191.BW1 is the R3Trans command file , file R900191.BW1 is the corresponding data file. Transfer both files into the Unix-, AS/400- or Windows/NT environment via FTP. Depending on the module, the directory additionally contains some text files (transport BOM, protocol) for your information. For example, the file BW1K900191_log.txt contains the export protocol of the transport stored in the directory.

The file PBSBWMod.exe is required to convert workbooks for archive support, which is done through the ViewPoint CBW Administration Cockpit. The file has to be copied into a local directory of the MS Windows frontend. The selected path must be registered in the Cockpit. Since workbooks will be modified with the frontend please make sure that MS Excel is correctly installed. Detailed information can be found in the EMC ViewPoint for SAP Construction and Maintenance Module Administration Manual.

The file transfer must be performed with the Unix user: <target system>adm (e.g. bw1adm) carried out in binary mode (ftp > bin).

Please import command file K9zzzzz.yyy into directory

/usr/sap/trans/cofiles

and data file R9zzzzz.yyy into directory

/usr/sap/trans/data

zzzzz = current transport number, yyy = ViewPoint system.



Note: During the transport, the letters used in the file name could be converted from capital letters to small letters. It is absolutely necessary that you undo this automatic change to be able to start the import via ’tp’ without problems. In Windows/NT environments you have to deactivate "read only" in the file attributes!

TP import Please carry out the following steps for the current import of the transport files into the SAP BW system:

� Switch over to directory /usr/sap/trans/bin

� Transfer the transport into the buffer with:

tp addtobuffer yyyK9zzzzz <target system>

Now start the import with:

tp import yyyK9zzzzz <target system> client=xxx

xxx = client

yyy = Name of the ViewPoint delivery system

zzzzz = current transport number

Note: The ViewPoint BW Module can be imported in any client you like.

The installation of the Final Release has now been finished.

Note: In some cases the ’tp’ terminates with the following error message:

E-TPSETTINGS could not be opened.

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

In this case please use the additional parameter

pf=TP_DOMAIN_XYZ.PFLXYZ = 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.

Initial installation 3-5

3-6


Installation of updatesDepending on the update level, a current Customer Patch (see chapters 2 and 3) may exist for a specific Final Release. This Customer Patch (and analogue to this all subsequent transports and updates you have received) must be installed after the installation of the Final Release. The procedure is described in the following.

For the installation, please carry out all steps analogue to the initial installation described in “Initial installation” on page 3-4.

In case you carried out modifications in ViewPoint objects we recommend to copy all changed objects (customer specific modifications!) under another name before running the import procedure for safety reasons. Then, you can update the necessary changes in the new objects after installation of the new Customer Patch.

In this case please carry out all steps similar to the standard. The only exception is the command "tp import...". This command has to be parameterized as follows:

tp import yyyK9zzzzz <target system> U26 client=xxx

xxx = client

yyy = name of the ViewPoint delivery system

zzzzz = current transport number

Parameter U26 signifies the unconditional modes 2 and 6. This means that during import already existing objects (originals) and repaired objects are overtyped. If you want to repeat an already existing transport again (e.g., because the previous installation was incomplete or has been cancelled), you must substitute parameter U26 by U126.

After the installation of a Customer Patch the complete installation of a ViewPoint module has been finished.



Check of installed transportFrom the transport log in the SAP system you can see whether the installation of the ViewPoint BW Module was successful. From the start menu, please call the transport management via:

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

and enter the request number of the ViewPoint BW Module you have installed (you can also start via transaction SE09, then selecting > Request/Task > Display individually), as shown in Figure 3-3, “Selection of imported ViewPoint transport request.”

Figure 3-3 Selection of imported ViewPoint transport request

Check of installed transport 3-7

3-8


In the selection result, please move to the number of the transport request and press the right mouse key, thus selecting the "Transport Logs" from the selection list, as shown in Figure 3-4, “Selection list.”

Figure 3-4 Selection list

In the list, which is then displayed, you can click on your system identification and "Import". Open the result list until you get the required information, as shown in Figure 3-5, “Analysis transport request.”

Figure 3-5 Analysis transport request



ViewPoint transport historyTo manage and control the history of the installed transport requests of the ViewPoint BW Module the transaction /PBS/UTIL_Z9CP is contained. Start the ViewPoint transport history from the ViewPoint main menu as follows:

ViewPoint BW Module > Utilities > Transport Search

You can also call the transport history via transaction code /PBS/UTIL_Z9CP, as shown in Figure 3-6, “ViewPoint transport history.”

Figure 3-6 ViewPoint transport history

In the list, all ViewPoint transport requests installed in your system are displayed according to the request number in declining order. Using the selection fields above the list, you can limit the number of transport requests shown in the list. The column "Transport no." contains the number of the ViewPoint transport request. "System", "User", "Date" and "Description" contain more information to exactly identify a certain request.

You will need this information about a certain transport request for e.g., transferring the ViewPoint BW Module into your production system and/or reporting problems to EMC Professional Services.

ViewPoint transport history 3-9

3-10


Transport into the production systemIn this respect, you basically have to distinguish between two different system environments, thus you have to chose between two different procedures.

System environment 1

Your production system is located in the same system as your test system, in which you imported the ViewPoint BW Module before, and only differs in the client:

In this case, a transport is not necessary since all changes are immediately active and available in your production system as well.


Your production system is installed in another system than your test system.

In this case you have to proceed as follows. Before you import the ViewPoint BW Module you have to export all customer specific modifications (and other repairs) via the transport system. Normally, for this purpose a transport request has to be created and released by the Workbench Organizer. There after, you can transport the ViewPoint BW Module into the production system, regarding the following steps:

Determine the number of the transport request used to install the current ViewPoint BW Module in your system. For that purpose, please use the transport history described in “ViewPoint transport history” on page 3-9.

Now create a new transport request in your system. Start the transaction SE01 (Transport Organizer) or via: Tools > Administration > Transports > Transport Organizer. Create a Request: > Request > Create. Select "Transport of copies" and enter a



note for the request to be created under "Short description" as shown in Figure 3-7, “Create transport request.”

Figure 3-7 Create transport request

Save your request.

Now you can integrate the original ViewPoint transport number (which you have determined before) via menu > Request/Task > Object list > Include Objects (or key combination CRTL +F11) into the current transport request. Your transport request can now be released, followed by an automatically induced export. If you want to make additions or changes to the object list of the transport request, you have to carry out these modifications before releasing the request.

Having completed the export procedure correctly, please import this transport request into your production system as described above.

Transport into the production system 3-11

3-12


Installation summaryTo easily check the installation of the ViewPoint BW Module, the most important steps are summarized below.

� Check the CD ROM you have received: Completeness of the transport files; Does the CD contain transports of the "Final Release" (and possibly "Customer Patch").

� Transfer the transport files into the corresponding target directories of your SAP system (usr/sap/trans/data respectively /usr/sap/trans/cofiles). Transfer in binary mode. Attention: The size of the transferred files must be the same both on the PC and in the SAP system.

� Set up the ViewPoint namespace before installing the ViewPoint BW Module.

� Import the transport request into the SAP system with the transport utility tp.

� First, import the "Final Release" and then (if available) the "Customer Patch". Check the transport logs via the "Workbench Organizer".

� Transfer the ViewPoint BW Module in your production system.



Peculiarities in operating system AS/400The installation in the operating system AS/400 can be generally carried out as under UNIX or Windows NT. Copy the transport files in the directories /usr/sap/trans/cofiles and /usr/sap/trans/data. It is important that the user has the <TARGETSYSTEM>OPR (instead of <targetsystem>adm in case of UNIX) rights for writing and reading files, i.e. they must have the Primary Group R3GROUP.<TARGETSYSTEM> indicates as variable the 3 digit name of the BW system in which the software is to be installed. While carrying out the transport, the same user has to start the tp command from the directory /usr/sap/trans/bin. The command syntax is:

Switch to the transport directory with cd ’/usr/sap/trans/bin’

Transfer the transport into the buffer with:

tp ’addtobuffer yyyK9zzzzzz <targetsystem>’

Carry out the import with:

tp ’import yyyK9zzzzzz <targetsystem> client=xxx’

yyyK9zzzzzz indicates the number of the order which we supply. This number can vary from shipment to shipment. <Targetsystem> is your system name. If it is not an initial installation but an update, it is necessary to add u26 (i.e. unconditional mode 2 and 6) in the tp commands so that the ViewPoint programs already available can be redefined. It is not necessary to indicate the user by adding client =xxx.

Peculiarities in operating system AS/400 3-13

3-14



4Invisible Body Tag

The SAP Add On Assembly Kit (AAK) is used to create the ViewPoint BW Module from SAP BW Release 3.5. The final release of an add on is delivered in an OCS package named Add On Installation Package (AOI) and Add On Upgrade Package (AOU) respectively. The import of this package can be made with SAP transaction SAINT. Customer patches have the package type Add On Support Package and is imported into the SAP BW system using transaction SPAM. See more details in the following chapters.

You should always check if the current SAINT/SPAM version is available in your system before installing a ViewPoint module. If this is not the case, first import the current version of the SAINT/SPAM update from the SAP Service Marketplace.

This chapter contains the following topics:

� SAP put level and hot packages ......................................................4-2� Initial installation ...............................................................................4-3� Installation of updates.......................................................................4-6� Transport into production system ...................................................4-7� Summary .............................................................................................4-8

Installation for SAP BW3.5

Installation for SAP BW 3.5 4-1

4-2

Installation for SAP BW 3.5

SAP put level and hot packagesEMC always develops the ViewPoint modules based on the current SAP Put Level, supplemented with the latest available Hot packages. ViewPoint attempts to keep all modules downward compatible to the corresponding Hot packages. However, in some cases conflicts and related problems may occur when installing respectively running certain ViewPoint programs due to different Hot package levels (Customer <> ViewPoint). Should you be faced with such a situation please contact EMC Professional Services as soon as possible so that the problems can be solved soon.



Initial installationThe Final Release of the ViewPoint BW Module is located in the subdirectory of the BW package (for example \CBW\35all\BW\final) in the delivery. The corresponding directory has for example the content shown in Figure 4-1, “Installation package 1 for BW Module.”

Figure 4-1 Installation package 1 for BW Module

The file PBS_CBW_IP_2.sar is the Add On installation package for the module CBW. This package should be imported during the first installation of CBW 3.5 on your SAP BW system (or in any other SAP system in which the software component SAP BW 350 has been installed, for example an SAP ECC system release 5.0). Even if CBW was already installed in previous releases per tp in this system. Then PBS_CBW_UP_2.sar should not be installed.

A separate installation of the ViewPoint namespace as in previous releases, as described in “Initial installation” on page 4-3, is no longer necessary in release 3.5 as the namespace is contained in each Installation Package of the ViewPoint BW Module.

PBS_CBW_UP_2.sar is the Add On Upgrade Package. This package should be installed if a CBW 3.5 Package had already been installed earlier in this system, for example PBS_CBW_IP_1.sar. As already explained in the previous paragraph, you do not need to import PBS_CBW_IP_2.sar in addition as both packages contain the same objects.

The file PBSBWMod.exe is required to convert workbooks for archive support, which is done through the ViewPoint BW Administration Cockpit. The file has to be copied into a local directory of the MS Windows frontend. The selected path must be registered in the Cockpit. If workbooks will be modified with the frontend you should make sure that MS Excel is correctly installed. Detailed information can be found in the EMC ViewPoint for SAP Construction and Maintenance Administration Manual.


4-4


The package PBS_CBW_IP_2.sar and PBS_CBW_UP_2.sar respectively can be imported directly with transaction SAINT.

Import with transaction SAINT

The import of an installation package can be made from any directory with transaction SAINT.

You should be logged on in client 000 for this transaction!

Call the transaction SAINT and load the packages into the SAP BW system with the menu options:

Installation Package > Load packages > From the front end.

After marking the package to be installed, select the button Öffnen (Open) and then the button Dekomprimieren (Decompress) in the following screen.

Figure 4-2 Load of the module installation package with SAINT



Then you can continue the installation by selecting button "Start", as shown in Figure 4-3, “Module installation with package SAINT.”

Figure 4-3 Module installation with package SAINT

Mark the package to be installed and install it by selecting button Continue. Follow all instructions so that the package is displayed as installed in your system. In the upper list the CBW is displayed as installed in the system.

The installation of the Final Release has now been finished.


4-6


Installation of updatesUpdates are supplied in two different transport types, depending on the update type - if it is a final release or a new customer patch:

� Upgrade package (UP)

� Support package (SP)

A new Final Release is supplied as an Upgrade Package and is imported with transaction SAINT analogue to the installation package.

Depending on the update level, a current Customer Patch may exist as a Support Package for a Final Release of the ViewPoint BW Module. This Customer Patch must be installed after the installation of the Final Release. As the Support Packages are no longer provided cumulatively from Release 3.5, they have to be imported one after another in ascending order.

Call transaction SPAM in client 000 for the import of the support package and load the package analogue to the transaction SAINT. Then the installation is made by selecting menu option Support package > Import queue.

If you have made modifications in the namespace /PBS/, you will have the possibility to compare them with transactions SPAU and SPDD which you can call within the import process.

After the installation of a Customer Patch the complete installation of the ViewPoint BW Module has been finished.



Transport into production systemIn this respect, you basically have to distinguish between two different system environments, thus you have to choose between two different procedures.


Your production system is located in the same system as your test system, in which you imported the ViewPoint BW Module before, and only differs in the client.

In this case, a transport is not necessary since all changes are immediately active and available in your production system as well.


Your production system is installed in another system than your test system.

In this case you have to import all packages of the ViewPoint BW Module (installation/upgrade package and support packages) in the same order in the production system as it was made in the test system.

Then you have to export all customer specific modifications (and other repairs) of the ViewPoint BW Module, which were executed in the test system, via the transport system. Normally, for this purpose a transport request has to be created and released by the Workbench Organizer. Having completed the export procedure correctly, please import this transport request into your production system with the transport program "tp".

Transport into production system 4-7

4-8


SummaryTo easily check the installation of the ViewPoint BW Module from Release 3.5, the most important steps are summarized below:

� Check the delivered transports you have received: Completeness of the transport files; does the ViewPoint delivery contain transports of the "Final Release" (and possibly "Customer Patches").

� At first, import the "Final Release" with SAINT and then (if available) the "Customer Patches" with SPAM.

� Transfer the ViewPoint BW Module into your production system.
