PBS archive add ons

Manual Part A
– Installation –

Compatible with
SAP ERP 6.x

©PBS Software GmbH 2024 Page 1 | 31

 PBS Software GmbH
Schwanheimer Str. 144 A
64625 Bensheim
Germany

Phone: +49 - 6251 - 174 0

Email: info@pbs-software.com
Website: pbs-software.com

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of PBS
Software GmbH. The information contained herein may be changed without prior notice.

PBS archive add ons is a registered trademark of PBS Software GmbH.

SAP, SAP ERP, R/3, SAP HANA, S/4HANA, SAP ILM, SAP NetWeaver, SAP NetWeaver Business Warehouse and other SAP
products and services mentioned in the text as well as the respective logos are trademarks or registered trademarks of SAP SE in
Germany and in other countries worldwide.

All other product and service names mentioned are the trademarks of their respective companies.

PBS Software GmbH shall not be liable for errors or omissions with respect to the materials. The only warranties for PBS Software
products and services are those that are set forth in the express warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional warranty.

© 2024 PBS Software GmbH. All rights reserved.

©PBS Software GmbH 2024 Page 2 | 31

PBS ILM Concept

Contents

1. PBS ILM Concept .................................................................................................................................5

2. Service and Contact.............................................................................................................................6

3. PBS Concept for Software Deliveries .................................................................................................7

4. Scope of Delivery – Installation Components.....................................................................................8

4.1 Final Release (Subdirectory Final) ....................................................................................................9

4.2 Support Packages (Subdirectory Patch) ............................................................................................9

4.3 Namespace /PBS/ (PBS_Namespc) .................................................................................................9

5. Installation ..........................................................................................................................................10

5.1 PBS Namespace ............................................................................................................................10

5.2 Initial Installation .............................................................................................................................12

5.3 Installation of Updates ....................................................................................................................15

5.4 Upgrade to higher Releases ...........................................................................................................16

5.4.1 SPAU Processing.....................................................................................................................16

5.5 Installation Check ...........................................................................................................................17

5.5.1 SAINT ......................................................................................................................................17
5.5.2 SPAM ......................................................................................................................................17
5.5.3 Transport Logs .........................................................................................................................18
5.5.4 Transport Research..................................................................................................................18

5.6 Transport to the Production System ................................................................................................19

5.7 Installing Transports .......................................................................................................................19

5.8 Summary of the Installation.............................................................................................................20

6. Module-specific Features ..................................................................................................................21

6.1 PBS SE16_PERSONAL – PBS Authorization Objects for Date Checks ...........................................21

6.2 PBS archive add on CDART ...........................................................................................................21

7. After the Installation...........................................................................................................................23

7.1 Necessary Authorizations ...............................................................................................................23

7.2 Preassignment Research Source ....................................................................................................23

© PBS Software GmbH 2024 Page 3 | 31

PBS ILM Concept

7.3 Generation Activities .......................................................................................................................25

7.4 Suppression of Message Output .....................................................................................................25

8. Customer-specific Enhancements and Modifications......................................................................26

9. Uninstallation .....................................................................................................................................27

9.1 Prerequisites – Attribute Change Packages ....................................................................................27

9.2 How do you determine which Attribute Change Package is necessary? ..........................................27

9.3 Uninstalling different PBS archive add ons ......................................................................................28

9.4 Uninstalling Procedure ....................................................................................................................28

10. Displaying the PBS Manuals ...........................................................................................................29

11. Annex................................................................................................................................................31

11.1 List of Figures ...............................................................................................................................31

© PBS Software GmbH 2024 Page 4 | 31

PBS ILM Concept

1. PBS ILM Concept

Information Lifecycle Management (ILM) means the administration of information related to the time when
it is used, taking into account its total costs and compliance. A conclusive, efficient ILM concept must, as a
result, control data growth, manage retention rules, and also ensure compliant data storage. Furthermore,
an easy access to archived data is decisive and its transfer during internal and external audits.

PBS Software GmbH offers SAP customers a wide spectrum of SAP add-on solutions to fulfill the require-
ments of a sophisticated ILM concept. As a recognized expert for complex, integrated data access to ar-
chived and online data, as well as for the decommissioning of SAP systems, PBS Software GmbH pro-
vides proven and extensively used products.

Highlights PBS archive add ons

▪ Seamless and fast data access to SAP database and archive data.
▪ Identical to SAP standard transactions and reports.
▪ Reduces operating costs, maintains system performance, and minimizes IT costs.
▪ Fast usage without user training.

© PBS Software GmbH 2024 Page 5 | 31

Service and Contact

2. Service and Contact

Should you have questions regarding the installation, please contact the Service Hotline of PBS Software
GmbH.

Within the scope of a valid maintenance contract, you may contact our hotline team with any questions you
may have regarding functionality, further development, or specific requirements.

To enable us to provide you the best service possible, please register under:
www.pbs-software.com/support. You have direct access to our helpdesk, the solution database and the
download area via your personal customer login. With the respective authorization you can download sup-
port packages in the download area.

Contact data of the Service Hotline

Phone: +49 - 6251 - 174 110

Email: hotline@pbs-software.com

Manuals

The modular manual of each PBS archive add on is composed of partial manuals:

▪ Part A: Installation
▪ Part B: Administration, Index Build and Maintenance (Administration Manual)
▪ Part C: Display and Evaluation (User Manual)

There are additional manuals for the PBS utilities such as Archive Browser, Translation Tool, and Conver-
sion Tool.

Release Compatibility

PBS archive add ons run with the basis programs of SAP SE in SAP ERP 6.x.

© PBS Software GmbH 2024 Page 6 | 31

PBS Concept for Software Deliveries

3. PBS Concept for Software Deliveries

The PBS archive add ons are supplied as OCS packages. In addition to the PBS modules such as CFI,
CSD, CMM, CCO, etc., so-called basis modules are needed to use the add-ons. They are also supplied as
OCS packages.

The basis modules are for example the PBS Utilities or the PBS ORDER package. They contain objects
that can be applied in two or more PBS archive add ons. They are not supplied separately. Furthermore,
the PBS Utilities include the complete application functionality, such as PBS Translation Tool, PBS Archive
Browser and PBS Conversion Tool.

The software packages for all modules are created as final releases and support packages.

The final release of a PBS archive add on is a complete and extensively tested program package for the
corresponding PBS module (CFI, CSD, CMM, CCO, etc.). Such a final release is always created for each
SAP release (ECC 6.0 to EHP 6, ECC 6.17). A final release contains all components described in the man-
ual (parts A, B, C) of the corresponding PBS module and can run on its own.

Having supplied a final release for a PBS archive add on, improvements, corrections and additions of the
different modules are produced within continuous development of the respective modules. To provide the
users of the news, supplementary support packages are delivered. They are numbered in chronological
order.

© PBS Software GmbH 2024 Page 7 | 31

Scope of Delivery – Installation Components

4. Scope of Delivery – Installation Components

The programs and documentations of the PBS archive add ons are supplied as FTP download as ZIP files.
The ZIP file contains the abbreviation of the name of the PBS archive add ons (for example CFI).

The delivery of each module contains:

▪ file directory \Docu with the subdirectories \German and \English for the documentations in Ger-
man and English. The documentation is delivered as PDF files.
▪ file directory \ECC with the subdirectories \Final for the packages of the final releases and \Patch
for the support packages.

Some modules have special subdirectories; please see the module-specific hints in this installation manual
regarding the description of these subdirectories.

Figure 1 displays the delivery directory for the basis module PBS Utilities:

Figure 1: Delivery Director y of the PBS Utilities

Figure 2 shows, as an example, the delivery directory for the PBS archive add on CSD.

Figure 2: Delivery Director y of the PBS archiv e ad d o n CSD

Important: Please retain the software packages on a permanent basis as you will require them again
for specific administrative tasks in your SAP system - for example, when you install new
languages.

© PBS Software GmbH 2024 Page 8 | 31

Scope of Delivery – Installation Components

4.1 Final Release (Subdirectory Final)

The final release contains a complete installation of a PBS module. It is supplied as an installation package
(IP) or upgrade package (UP).

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 each PBS archive add on or for
an update of the add on the current installation package should always be installed after changing the SAP
release. However, during an upgrade of the PBS software, the upgrade package should be installed within
the same SAP release.

The objects that are supplied in the respective modules with the final release are listed in an object list
which is contained as a text file in the subdirectory \ECC\Final.

4.2 Support Packages (Subdirectory Patch)

The support packages in directory \Patch, so-called customer patches, contain the modifications since the
creation of the final release. Information on the changed objects can be seen from an object list in the sub-
directory \ECC\Patch.

Support packages are not cumulative. Therefore, all support packages that are available for the current
final release and not yet installed in the system have to be imported in ascending order.

4.3 Namespace /PBS/ (PBS_Namespc)

The program and data objects of the PBS archive add ons are in the PBS-specific namespace /PBS/ so
that no naming collisions with customer-specific or third-party provider objects can occur. The namespace
must be defined before the installation of the PBS archive add ons (see chapter 5.1).

© PBS Software GmbH 2024 Page 9 | 31

Installation

5. Installation

Important: You should be logged on in client 000 for the installation!

Please note the installation sequence that is described in the following sections:
1. (Single) import of the namespace package
2. PBS Utilities
a) Final Release (Installation Package or Upgrade Package)
b) Support Packages
3. PBS Module(s)
a) Final Release (Installation Package or Upgrade Package)
b) Support Packages

The SAP Add-On Assembly Kit (AAK) is used to create the PBS archive add ons. 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. Cus-
tomer patches have the package type Add-On support package and are imported into the SAP system
using the transaction SPAM. See more details in the following chapters.

Before starting the installation of the software, you should always check if the current SAINT/SPAM version
is in the system. If it is not the case, import the current version of the SAINT/SPAM updates from the SAP
Service Marketplace before starting the installation.

SAP Support Package Level

PBS always develops the PBS archive add ons based on the current SAP Support Package Level. All
modules are downward compatible. However, in some cases conflicts and related problems may occur
when installing respectively running certain PBS programs due to different support package levels (cus-
tomer ≠ PBS). Should you be faced with such a situation please contact as soon as possible the PBS Ser-
vice Hotline so that the problems can be solved soon.

5.1 PBS Namespace

Before you can install the packages for the PBS Utilities and the first PBS module, you have to import the
installation package for the namespace /PBS/. All objects of the PBS archive add ons and the PBS Utilities
are within this namespace and begin with /PBS/.

Install the PBS namespace with the SAP transaction SAINT of the installation package PBS_NSP_IP_1.sar.
This package is in the delivery directory of the basis module PBS Utilities in the subdirectory
\ECC\Namespc (see Figure 1).

© PBS Software GmbH 2024 Page 10 | 31

Installation

Important: The installation package PBS_NSP_IP_1.sar has to be imported even if the namespace
already exists in your system due to the transfer from an older SAP release level. Then all
necessary definitions are available in the system to use the Modification Assistant. It is also
checked in the upgrade packages of the utilities whether this package exists. The package
PBS_NSP_IP_1.sar has to be imported only once; for further imports of other PBS modules
you can start with the installation of the current utilities packages at once.

Copy this package from the delivery in a directory in which you can access with SAINT.

Call the following menu option in the transaction SAINT:

Installation Package → Load packages → From Front End

Choose the directory in which you wish to copy the files supplied in the selection screen "Select CAR/SAR
archive". After having opened the file continue the installation in SAINT by selecting the button "Continue".
The procedure corresponds to the description for the import of an installation package in chapter 5.2.

After the import of the package PBS_NSP_IP_1.sar you can display the PBS namespace screen with
transaction SE03 selecting the menu option "Administration → Display/Change Namespaces". The de-
tailed view of the entry /PBS/ should be as follows:

Figure 3: Display of th e PBS Namesp ac e with SE03

You need the repair license if you intend to define own modifications in the PBS programs. As the
namespace role for the PBS namespace has the entry "C" in your system, the SAP Modification Assistant
is called automatically in case of any changes in the PBS programs - for example with transaction SE38 -.
Using the transaction SPAU and SPDD you are able to execute a modification adjustment after having im-
ported the PBS support package at a later date.

© PBS Software GmbH 2024 Page 11 | 31

Installation

5.2 Initial Installation

The final release of each PBS module is in the subdirectory \ECC\final. The corresponding directory for
CMM 6.0 has for example the following content:

Figure 4: Installation/U pgra de Pa ck ag e 3 for Mo dule CMM 6.0

Installation Package

The file PBS_CMM_IP_3.sar is the Add-On installation package for the module CMM. This package should
be imported during the first installation of CMM in your SAP system, even if CMM was already installed in
previous releases in this system. Then the package PBS_CMM_UP_3.sar should not be installed.

Upgrade Package

The file PBS_CMM_UP_3.sar is the Add-On upgrade package. This package should be installed if a CMM
package had already been installed earlier in this system, for example PBS_CMM_IP_1.sar. The upgrade
package is installed instead of the installation package and not as an additional package.

Installation and upgrade package contain the same objects. As described above, it is installed either the
installation package or the upgrade package.

The package PBS_CMM_IP_3.sar and PBS_CMM_UP_3.sar respectively can be imported directly with
transaction SAINT.

Please note:

▪ First import the installation package PBS_NSP_IP_1.sar to set up the PBS namespace.
▪ Import the current installation package or upgrade package or support package of the PBS Utili-
ties before each import of a module package, if it has not been installed in your system yet.

The procedure to install the package PBS_NSP_IP_1.sar or the package for the PBS Utilities corresponds
to the installation of a module which is described in the following.

© PBS Software GmbH 2024 Page 12 | 31

Installation

Import with transaction SAINT

The import of an installation package can be made from any directory with transaction SAINT. Please note
that you always install the latest version of SPAM/SAINT in your SAP system!

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

Installation Package → Load packages → From Front End

Figure 5: Lo ad Ad d-On In stallation Pac ka ge with Trans actio n SAINT, for exam ple PBS Modu le CMM

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

Load the available support packages of the module in the same way. In this example, the support pack-
ages PBS_CMM_SP_3_1.sar and PBS_CMM_SP_3_2.sar are available. These packages are in the sub-
directory \ECC\patch.

© PBS Software GmbH 2024 Page 13 | 31

Installation

Figure 6: Available Su pp ort Pack ag es in the D elivery Directory \ECC\patc h, Exam ple CMM 6 .0

Then you can continue the installation by selecting button "Start".

Figure 7: Install Add-On Installation Pa cka ge with Tran sactio n SAINT, for exam ple PBS Mod ule CMM

Mark the package to be installed and install it by selecting button "Continue". In the next screen, choose
the current support package as target support package. The current support package is the package with
the highest number, in the example it is CMM support package 2.

© PBS Software GmbH 2024 Page 14 | 31

Installation

Figure 8: Selection of Target Su pp ort Packa ge s

Follow all instructions so that the package is displayed as installed in your system.

The installation of the PBS module, in the example CMM, has now been finished.

5.3 Installation of Updates

Updates are supplied in two different transport types, depending on the update type – if it is a new final re-
lease or a support package:

▪ 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.

© PBS Software GmbH 2024 Page 15 | 31

Installation

Depending on the update level, a current support package, so-called customer patches exist for a final re-
lease of a PBS archive add on. These support packages must be installed after the installation of the final
release! As the support packages are not created cumulatively, they have to be imported one after another
in ascending order.

Call transaction SPAM in client 000 for the import of a 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 adjust them with
transactions SPAU and SPDD which you can call within the import process.

Please see the module-specific notes in chapter 6.

5.4 Upgrade to higher Releases

During the upgrade of the SAP system to a higher release the PBS archive add ons remain in the system

During the upgrade of your SAP system you will be requested to choose either an Attribute Change Pack-
age (ACP) depending on the installed PBS module or different options, for example "Delete", "Keep" or
"Keep (with vendor key)". Choose the option "Keep" and if this option cannot be selected, choose "Keep
(with vendor key)". You will need to contact the PBS Service Hotline to obtain the vendor key and the ACP.

Although the PBS archive add ons remain unchanged in the system, a new installation is required for a
higher SAP release, starting with the package PBS_NSP_IP_1.sar of the respective release level. For a
new installation you should also install the installation package for the PBS Utilities and the modules. If you
want to upgrade within the same SAP release level, you will need to install the current upgrade package.

5.4.1 SPAU Processing

If you are requested to perform a modification adjustment with the transaction SPAU during the upgrade,
first check if you have made any modifications that you want to keep. If it is not the case, we recommend
processing all PBS-specific objects that are displayed in the modification adjustment with the option "Reset
to original". When doing this, make absolutely sure before selecting this option that you only select the
names of the displayed objects and under no circumstances the traffic light symbols displayed in front, be-
cause this would immediately start a SPAU adjustment.

© PBS Software GmbH 2024 Page 16 | 31

Installation

5.5 Installation Check

5.5.1 SAINT

Using the transaction SAINT you can determine the exact installation level of each module at any time. To
do this, simply scroll down to the required module in the initial screen of the transaction.

Figure 9: Installation C hec k with Transa ction SAINT

In Figure 9, you can see, for example, some information on the PBS archive add on CMM. The column
"Release" indicates that the current imported final release is number 3. The column "Level" shows that
support packages no. 1 and 2 were imported subsequently. The name of the OCS package of final release
no. 3 is in column "OCS package": SAPK-C03CHINPBSCMM.

5.5.2 SPAM

You can display detailed information on the imported support packages in transaction SPAM.

Figure 10: In stallation Ch eck with Trans actio n SPAM

© PBS Software GmbH 2024 Page 17 | 31

Installation

Figure 10 shows again, as an example, the PBS archive add on CMM: The current support package 2 of
final release no. 3 is the OCS package SAPK-C0302INPBSCMM. According to the prerequisite set 01, the
installation of final release no. 3 – PBSCMM, C03_600 – and the support package no. 1 – SAPK-
C0301INPBSCMM – are a prerequisite as import condition. Furthermore, the PBS Utilities need to be in
the system with the release level C07_600. All import conditions are displayed as met.

5.5.3 Transport Logs

You can display the transport logs of the OCS packages, for example, with the transaction SE01. For this,
enter the OCS package name in the field "Request/Task" in the tab "Display" and select the button "Logs".
For further details, please see the SAP SE standard documentation.

5.5.4 Transport Research

You can call the PBS transport research with the transaction /PBS/UTIL_Z9CP to get an overview on the
PBS packages and tp transports that are installed in your system. The display can be made according to
PBS modules.

To determine the transports for a specific PBS module, fill the fields "Transp. no.", "Transport target" and
"User" with * for the selection. Enter the name of the requested module in the field "Module".

In addition, you can select the option "Path name" and enter a path in your computer. The result list is
saved locally as *.xls file and can be provided to the PBS Service Hotline, if necessary.

Figure 11: Tran sa ction /PBS/UTIL_Z9CP – Extract from th e Trans port Res earc h for Mo dule CPP

© PBS Software GmbH 2024 Page 18 | 31

Installation

5.6 Transport to the Production System

In principle it is possible to differentiate here between two different system landscapes. Consequently, dif-
ferent procedures have to be chosen between:

System environment 1

Both your production system and your test system are on the same server, the only difference is the client
identifier. You have already imported the PBS archive add ons in your test system.

In this case no action is required as all changes are active immediately and are available in your produc-
tion system.

System environment 2

Your production system and your test system are not installed on the same server.

In this case you must first import all of the PBS archive add ons 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 of the PBS archive add ons that were executed in the
test system are then exported via the transport system.

5.7 Installing Transports

For technical reasons, PBS supplies partial components and corrections as tp transports. We recommend
using the SAP transaction STMS (Transport Management System) to install these transports.

© PBS Software GmbH 2024 Page 19 | 31

Installation

5.8 Summary of the Installation

For an easy control of the PBS archive add on installation, the most important installation steps are sum-
marized in the following:

1) Check the completeness of the transport files in the delivery:

Are transports of the installation/upgrade packages and possibly support packages for the PBS
namespace, PBS Utilities and the PBS archive add ons available? (chapter 4)

2) Create the PBS namespace by importing the transport PBS_NSP_IP_1.sar with transaction SAINT
(chapter 5.1).
The PBS namespace has to be imported before the installation of the PBS Utilities or the PBS ar-
chive add ons. The transport PBS_NSP_IP_1.sar has to be imported in your system once even if
the namespace exists due to the transfer from an older SAP release.

3) Import the support packages of the PBS Utilities into the SAP system with transactions SAINT and
SPAM.

4) Import the final release and all available support packages of each PBS module into the SAP sys-
tem with transactions SAINT and SPAM.

© PBS Software GmbH 2024 Page 20 | 31

Module-specific Features

6. Module-specific Features

6.1 PBS SE16_PERSONAL – PBS Authorization Objects for Date Checks

Authorization objects or fields to carry out date or time checks do not exist in the SAP standard system.
These checks can be very important, for example for evaluations of tables from the FI area. PBS provides
the authorization class ZPBS for this. Several authorization objects, each of which has one authorization
field, are contained in this authorization class. For technical reasons, the objects are assigned to package
ZZ_SE16_AUDIT in the customer namespace Z*.

A separate transport for the import of authorization objects will be supplied, which can be imported with the
transport program tp, if necessary. You can find it in the directory SE16_PERSONAL\ECC\PBS_author-
ity_objects.

For detailed information about the PBS authorization objects, please refer to the administration and user
manual for SE16_PERSONAL.

6.2 PBS archive add on CDART

The PBS archive add on CDART needs to be installed in line with the SAP Data Retention Tool (DART)
level. Therefore, a password is required for the installation. You can get it from the PBS Service Hotline
when you state the DART level. If necessary, you get an additional tp transport that has to be imported af-
ter the installation of the PBS archive add on CDART.

Execute report /PBS/DART_RELEASE using the transaction SE38 or SA38 to determine the DART level
and other important information. The following Figure 12 shows, for example, a screenshot of the output.

Figure 12: List Out put of Progr am /PBS/DART_RELEASE

Send a screenshot of the information that was found in your system to the PBS Service Hotline.

© PBS Software GmbH 2024 Page 21 | 31

Module-specific Features

If the program /PBS/DART_RELEASE does not exist in your system, please refer to type group DART1 for
the DART level. For this, display the type group using the transaction SE11. You can see the installed Data
Retention Tool (DART) level as value of the constant DART1_RL.

Figure 13: Displa y of DART Level in the Typ e Gro up DART1 with Transactio n SE11

© PBS Software GmbH 2024 Page 22 | 31

After the Installation

7. After the Installation

7.1 Necessary Authorizations

The user profile of users has to be added for indexing and display of archived data. In addition to the gen-
eral authorization for the transaction namespace /PBS/*, the authorizations S_ARCHIVE and S_DATASET
with the activity 01 (Create) have to be added to the profile of administrators. End users need the authori-
zation objects S_ARCHIVE activity 3 for "Display", and S_DATASET with activity 33 for "Read".

7.2 Preassignment Research Source

The archive parameter (1 = Database + Archive, 2 = Database, 3 = Archive) that is used to determine the
data selection scope can be preconfigured using a customizing option. User-specific preferences are cov-
ered by making the default value globally valid. The default value can be set at PBS module, object name,
user, group, and role levels.

All programs, logical databases or module pools which are intended for setting an individual 1/2/3 default
value are supplied with the customer-specific value from the customizing table /PBS/UTIL_APARAM within
the program initialization.

The table can be called after the installation of the PBS archive add on via the transaction
/PBS/UTIL_APARAM or the PBS main menu.

© PBS Software GmbH 2024 Page 23 | 31

After the Installation

Figure 14: Def ault Value Re sear ch So urce

The default value can be defined per application, object name, and user/group/role. The most detailed pre-
assignment level is the user. If the field user should not be differentiated, this field can be prepopulated by
*. This wildcard procedure can also be applied on the level of the object name and the application. A partial
wildcard is not intended. Alternatively, a user group or a role can also be specified. In this way, you can
perform assignments for different users with one entry.

Figure 15: M ainten an ce of th e Res earc h Sour ce

When setting the default value in the application program, it is checked and proposed according to the fol-
lowing logic:

1) Parameter IDs (SET/GET parameters), which are supplied with a value in the user master.

2) User-/Group-/Role-specific value for an object

3) Object-specific value for an application

4) Application-specific value

© PBS Software GmbH 2024 Page 24 | 31

After the Installation

5) General value for all PBS archive add ons

6) Default value: 1 = Database + Archive

Concerning the parameter IDs supplied by each PBS archive add on, please see the module-specific ad-
ministration manuals.

7.3 Generation Activities

In some PBS modules, for example for the PBS archive add ons CCMD, CFI, CCOPA, CSL, CUMD, CUS-
TOM (IDK) and CVMD, some generation activities first need to be performed before the actual product de-
ployment. Please refer the module-specific manuals for more details.

7.4 Suppression of Message Output

Archived data is evaluated using the function modules of SAP function group ARCH. These function mod-
ules include all access routines to archived application data.

When evaluating the data in the background, the message with number 165 of message class BA is dis-
played for each data object to be read, this means for each document to be read. This can lead to disk
space problems for the job log file if there are large data volumes. Therefore, we recommend deactivating
this message.

For this, the program LARCHF01 can be changed via the SAP Modification Assistant, as displayed in the
figure below. Here, note that the output of the message can occur more than once in the coding, depend-
ing on the release. The modification has to be made in several places.

Figure 16: Pro pos ed Co din g Modificatio n to su ppr ess th e Me ssa ge O utput

© PBS Software GmbH 2024 Page 25 | 31

Customer-specific Enhancements and Modifications

8. Customer-specific Enhancements and Modifications

Enhancements and modifications that are realized in the SAP standard programs by user exits, customer
exits and similar techniques are not taken into account automatically in the PBS programs (module pools,
function groups, etc. in the PBS namespace).

Enhancements that have been performed in implicit and explicit enhancement points and enhancement
sections in the SAP standard programs using enhancement implementations are also not executed auto-
matically in the analog PBS programs.

All enhancements and modifications in SAP standard programs must also be adapted in the corresponding
PBS programs so that the additional program logic is also taken into account in the document display using
the PBS transactions. If necessary, additional archive accesses must be programmed provided that the
enhancements contain database selections. For this, the programs are modified in the PBS namespace.

The PBS program modification can be executed by the customer or it can be ordered at PBS.

We recommend executing modifications using the Modification Assistant. The realized modifications can
be adjusted using the SAP transactions SPAU and SPDD during the import of new packages.

Please note that the modified programs might be overwritten if you import any advance corrections and
customer patches. In this case the modifications must be implemented again after having imported the
transports or packages.

New PBS software packages that are appropriate for the target release have to be imported for a release
upgrade. Modified PBS objects must be reset to original in the modification adjustment and then the modifi-
cations have be made again.

The customer is responsible for the administration of the modified PBS programs.

© PBS Software GmbH 2024 Page 26 | 31

Uninstallation

9. Uninstallation

9.1 Prerequisites – Attribute Change Packages

From version 0053 of the SAP Add-On Installation Tool it is generally possible to uninstall ABAP add-ons.
See SAP note 2011192 for further details. Please check if your system meets the technical prerequisites.

For the uninstallation you receive an Attribute Change Package (ACP) from PBS for each module that indi-
cates this module as being able to be uninstalled. These ACPs change subsequently the import conditions
of PBS packages that have already been imported. In addition, you receive a tp transport with a plugin
class, if necessary. This tp transport has to be imported first in the system.

9.2 How do you determine which Attribute Change Package is necessary?

Determine all entries of view E070CTV with request/task = SAPK-*INPBS* using the transaction SE16 and
send the results to the PBS Service Hotline. Based on this information, the appropriate ACPs are created
and supplied for the PBS packages that should be deleted.

Figure 17: Sele ction of imp orted Pa cka ge s

© PBS Software GmbH 2024 Page 27 | 31

Uninstallation

9.3 Uninstalling different PBS archive add ons

Due to the dependencies of the modules among one another, the uninstall sequence must be performed in
exactly the reverse order of the install sequence:

1) PBS modules (CFI, CSD, etc.)

2) PBS ORDER, if available

3) PBS Utilities

4) PBS namespace

9.4 Uninstalling Procedure

ACPs have to be uploaded in the target system and do not need to be installed. For this, start the transac-
tion SAINT and choose the menu option "Installation Package → Load packages → From Front End". The
upload is sufficient to activate the changed conditions in the system. Now the tab "Deinstallable compo-
nents" is displayed in the transaction SAINT. There you can select the add on to be deleted and trigger the
uninstallation.

You can find further information on performing the uninstallation in the SAP SE documentation.

With some PBS modules, a notification can be displayed that non-deletable objects are available. Linked to
this is the option to display a complete log. Please send this log to the PBS Service Hotline to get a corre-
sponding deletion transport. After importing the deletion transport, you can continue the uninstalling pro-
cess.

© PBS Software GmbH 2024 Page 28 | 31

Displaying the PBS Manuals

10. Displaying the PBS Manuals

In addition to the installation files you will find the necessary documentation in PDF format (Portable Docu-
ment Format) in the delivery.

In the SAP system, you can access the manuals of the implemented PBS archive add ons via the PBS
Documentation Guide. It can be called via the PBS menu or when you enter the transaction code
/PBS/UTIL_ACCESS_DOC.

Figure 18: PBS Docum ent ation Guid e in Area M enu /PBS/PBS

Figure 19: PBS Docum ent ation Guid e, Trans action /PBS/UTIL_ACCESS_DOC

All manuals are available in German and English. The language can be chosen via the pushbutton "Ger-
man" or "English".

© PBS Software GmbH 2024 Page 29 | 31

Displaying the PBS Manuals

The chosen manual is displayed in the Internet browser on the PBS homepage www.pbs-software.com.
Functional preconditions for the use of this option are:

1) The workplace has a freely accessible Internet connection to display the URL of each documenta-
tion via the Internet browser.

2) An Internet browser is installed at the workplace.

Alternatively, the manuals can be displayed via the local network or the customer-specific intranet. For this
purpose, save all manuals in German and English that are located in the directory "Docu" on the respective
server. Then set the URL by calling the menu option "Customizing → Set URL":

Figure 20: Set URL of Ma nu als

Figure 21: Set Path for th e PBS Docume ntation G uide

Enter the value CPATH in the field "Characteristic" and the URL in the field "Value". Make sure that you
store the data in a generally accessible directory in order to minimize problems with access authorizations.
An intranet address or a local network path can be entered as a path.

© PBS Software GmbH 2024 Page 30 | 31

Annex

11. Annex

11.1 List of Figures

Figure 1: Delivery Directory of the PBS Utilities ..........................................................................................8

Figure 2: Delivery Directory of the PBS archive add on CSD ......................................................................8
Figure 3: Display of the PBS Namespace with SE03 ................................................................................11
Figure 4: Installation/Upgrade Package 3 for Module CMM 6.0.................................................................12
Figure 5: Load Add-On Installation Package with Transaction SAINT, for example PBS Module CMM......13
Figure 6: Available Support Packages in the Delivery Directory \ECC\patch, Example CMM 6.0 ...............14
Figure 7: Install Add-On Installation Package with Transaction SAINT, for example PBS Module CMM ....14
Figure 8: Selection of Target Support Packages .......................................................................................15
Figure 9: Installation Check with Transaction SAINT ................................................................................17
Figure 10: Installation Check with Transaction SPAM ...............................................................................17
Figure 11: Transaction /PBS/UTIL_Z9CP – Extract from the Transport Research for Module CPP............18
Figure 12: List Output of Program /PBS/DART_RELEASE .......................................................................21
Figure 13: Display of DART Level in the Type Group DART1 with Transaction SE11 ................................22
Figure 14: Default Value Research Source...............................................................................................24
Figure 15: Maintenance of the Research Source ......................................................................................24
Figure 16: Proposed Coding Modification to suppress the Message Output ..............................................25
Figure 17: Selection of imported Packages...............................................................................................27
Figure 18: PBS Documentation Guide in Area Menu /PBS/PBS ...............................................................29
Figure 19: PBS Documentation Guide, Transaction /PBS/UTIL_ACCESS_DOC.......................................29
Figure 20: Set URL of Manuals ................................................................................................................30
Figure 21: Set Path for the PBS Documentation Guide .............................................................................30

VersionsID1924

© PBS Software GmbH 2024 Page 31 | 31