Installing a Preconfigured System (PCS)


SAP offers Preconfigured Systems (PCS or SAP Best Practices) for certain industries. These systems contain special industry information for typical structures in an industry, and the corresponding default values for these structures in the SAP System.

A PCS consists of the following elements:

·        An industry-specific solution

·        An industry-specific SAP client

·        Industry-specific Customizing data

A PCS also contains test data and industry-specific documentation. You can use this test data to try out examples of processes and scenarios. The documentation gives you detailed descriptions of the process models. For more information on Preconfigured Systems, see the SAP Service Marketplace:

Only use the PCS as a basis for the configuration of a system installation.

Import the PCS into your test system first, so that you can check that its settings meet your requirements.


·        You have loaded the relevant packages into your system.

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

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

·        You are logged on to the SAP System in a client other than 000 or 066. These clients are protected against the import of a PCS. In client 000, you can use the Add-On Installation Tool to install add-onssapurl_link_0003_0002_0005.

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

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

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

If you are logged on to a protected client, you can use only the display functions of the Add-On Installation Tool.

Only import the packages at times when there is a low system load, as during the import no other users must be logged on to the system and no background job must be running. If not, problems can arise (terminated transactions, problems with synchronization, for example).



       1.      Call the Add-On Installation Tool (transaction SAINT). The initial screen is displayed, listing the Preconfigured Systems and add-ons that have already been installed.

       2.      Choose Start to begin the installation process. The subsequent screen shows you the PCS packages that can be installed.

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

See also: Loading Installation Packages.

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

This can lead to different results:

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

Ў        You need additional packages for the installation. You are shown which packages are missing. The installation does not start.

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

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

       5.      To start the installation, choose Continue.

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

Once the problem is corrected, choose Continue to continue the installation.

If you cannot correct the problem, you can reset the installation up to the phase SCHEDULE_RDDIMPDP (see Phases in the Add-On Installation Tool) by choosing Back.

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