Show TOC

Procedure documentationInstalling a Preconfigured System (PCS) Locate this document in the navigation structure

 

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 provides you with detailed descriptions of the process models. For more information on Preconfigured Systems, see the SAP Service Marketplace under http://service.sap.com/bestpractices.

Note Note

Only use the PCS as a basis for configuring a system installation.

Always install the PCS in your test system first, so that you can check that its settings meet your requirements.

End of the note.

Prerequisites

  • You have loaded the relevant packages into your system.

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

    Note Note

    Preconfigured Systems are not normally compatible with each other. They cannot be installed together. However, if you wish to enable related PCSs, SAP organizes them in groups in order to guarantee compatibility. If a PCS is assigned to a different group to that of an installed PCS, or has no group assignment at all, you cannot install it.

    End of the note.

  • You are logged on to the SAP system in a client other than 000 or 066. These clients are always protected against PCS imports. In client 000, you can use Add-On Installation Tool to install add-ons.

    Note Note

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

    End of the note.

  • The client where you install the PCS is not protected against imports. If you are unsure, call 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 in a protected client, you can only use the Add-On Installation Tool display functions.

Note Note

Only install packages when there is a low system load. There must be no other users logged on to the system, and there must be no background jobs running. Otherwise, problems can arise, such as terminated transactions or problems with synchronization.

End of the note.

Procedure

  1. Call Add-On Installation Tool (transaction SAINT). The initial screen is displayed, listing the preconfigured systems and add-ons that are already installed.

  2. Choose Start to begin the installation process. The screen shows you the installable PCS packages.

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

    For more information, see Loading Installation Packages.

  4. To begin installing a PCS, select the PCS you want from the list of installable packages and choose Continue.

    This can have varying results:

    • The PCS may not be installed in this system, as some installation conditions have not been met. If this happens, the system specifies the conditions in question.

    • You need additional packages for the installation. The system specifies which packages are missing. The installation does not start.

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

    • Once all the conditions are met, the relevant installation queue appears (in a PCS installation, this queue only contains the PCS installation package). You can now 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 errors occur in any of these phases, the installation process terminates, and a description of the error is provided.

    Once the problem has been corrected, choose Continue to restart the installation process.

    If you are not able to correct the problem, choose Reset to reset the installation up to phase SCHEDULE_RDDIMPDP (see Phases).

    Caution Caution

    In later phases, the content of the database has already been changed, meaning that you have no choice but to continue the installation process.

    End of the caution.