Performing Post-Installation Activities

Preparing the Training System for an Software Update

Objective

After completing this lesson, you will be able to prepare the training system for an Software Update

Named User Creation

After an SAP installation, only a few standard dialog users exist in the SAP system, for example, SAP* and DDIC. Although these users have many authorizations (authorization profile SAP_ALL), they are not allowed to perform certain tasks. For example, they are not allowed to perform customizing or development-related tasks. Therefore, you must create a normal dialog user account before you can perform some of the post-installation steps.

Create Named User in All Clients

In transaction SU01, copy SAP* or DDIC to a regular dialog user. This step is necessary to perform some of the subsequent post-installation steps.

Hint

When creating the first dialog user, maybe SU01 informs that no default company address exists. In this case create and maintain the default company address.

Create a Named User for SAP System S4X

Business Example

Before using the SAP system, you have to create your own user. This user is necessary for all development related activities, because the standard users SAP* and DDIC are not allowed to perform these activities.

Steps

  1. Switch the SAP Logon and SAP GUI to the SAP Signature Theme.

    1. On the WTS, open SAP Logon.

    2. Via the top left button, choose Options....

    3. At Visual Design→Theme Settings switch to SAP Signature Theme.

    4. Maybe you want to change settings as you like at Interaction Design in the areas Keyboard Settings and Visualization 2.

    5. Close and re-open SAP Logon.

  2. Create a log on entry for the newly installed SAP system S4X

    1. On the WTS, open SAP Logon.

    2. In SAP Logon, create a connection for SAP system S4X. Choose Local, then using the function New→Connection→User Specified System→Next→Custom Application Server. As Description enter SAP S/4HANA Server System S4X, as Application Server (host) enter s4xhost, as Instance Number enter 11, and as System Id enter S4X.

  3. Create a new user for SAP system S4X, client 000 by copying user DDIC. The user name should be ADMIN_000.

    1. Log on to S4X, client 000 with user DDIC.

    2. Call transaction SU01.

    3. Choose User→Copy.

    4. The pop up Copy Users is displayed.

    5. In the field From enter DDIC, in the field To enter ADMIN_000.

    6. Confirm the pop up with Copy.

    7. The screen Maintain Users is displayed with active tab Logon Data.

    8. Enter an initial password, e.g. InitialS4X10! twice.

    9. Choose Save.

      Result

      Now you have created your own user in S4X, client 000.

  4. Log off from S4X, client 000 with user DDIC.

Create two Named Users for SAP System SMA

Business Example

Before using the SAP system, you have to create your own user. This user is necessary for all development related activities, because the standard users SAP* and DDIC are not allowed to perform these activities.

Steps

  1. If not already done so, switch the SAP Logon and SAP GUI to the SAP Signature Theme.

    1. On the WTS, open SAP Logon.

    2. Via the top left button, choose Options....

    3. At Visual Design→Theme Settings switch to SAP Signature Theme.

    4. Maybe you want to change settings as you like at Interaction Design in the areas Keyboard Settings and Visualization 2.

    5. Close and re-open SAP Logon.

  2. Create an log on entry for the newly installed SAP system SMA

    1. On your WTS, open SAP Logon.

    2. In SAP Logon, create a new entry for SAP system SMA. Choose Local, then using the function New→Connection→User Specified System→Next→Custom Application Server. As Description enter SAP Solution Manager System SMA, as Application Server (host) enter smxhost, as Instance Number enter 81, and as System Id enter SMA.

  3. Create a new user for SAP system SMA, client 000 by copying user DDIC. The user name should be ADMIN_000.

    1. Log on to SMA, client 000 with user DDIC.

    2. Call transaction SU01.

    3. Choose User→Copy.

    4. The pop up Copy Users is displayed.

    5. In the field From enter DDIC, in the field To enter ADMIN_000.

    6. Confirm the pop up with Copy.

    7. The screen Maintain Users is displayed with active tab Logon Data.

    8. Enter an initial password, e.g. InitialSMA80 twice.

    9. Choose Save.

      Result

      Now you have created your own user in SMA, client 000.

  4. Log off from SMA, client 000 with user DDIC.

  5. Create a new user for SAP system SMA, client 001 by copying user DDIC. The user name should be ADMIN_001.

    1. Log on to SMA, client 001 with user DDIC.

    2. Call transaction SU01.

    3. Choose User→→Copy.

    4. The pop up Copy Users is displayed.

    5. In the field From enter DDIC, in the field To enter ADMIN_001.

    6. Confirm the pop up with Copy.

    7. The screen Maintain Users is displayed with active tab Logon Data.

    8. Enter an initial password, e.g. InitialSMA80 twice.

    9. Choose Save.

      Result

      Now you have created your own user in SMA, client 001.

  6. Log off from SMA, client 001 with user DDIC.

Import of Profiles

Import and Maintenance of Profiles

The technical configuration of an SAP system is controlled by profile parameters. There are around 2,000 profile parameters.

Most of them have a default and are compiled in the SAP kernel. They are not set explicitly by the SAP system administrator. About 100 profile parameters are explicitly set in profiles.

The default profile contains the profile parameters that configure all application servers of an SAP system. In addition, each application server has its own instance profile to individually configure the corresponding application server. Each application server has its own start profile to configure what must be started while starting that application server. For example, check if the database is started already. Up to AS ABAP 7.03 the start profile was a separate file. Starting with AS ABAP 7.10 the parameters from the start profile are now part of the instance profile – the profiles were merged together.

After the installation, the profile parameters are only present at file system level in the profiles generated by SAPinst. To use the profile administration inside the SAP system (transaction RZ10), the profiles must be imported into the database of the SAP system.

Transaction RZ10 performs a consistency check during this import. Changes to profile parameters can then be performed inside the SAP system. The profile parameters are then stored in the database and are written back to file system level. The changes only take effect when they are read by the SAP system at SAP system start. The affected application servers of the SAP system have to be restarted after changing profile parameters.

Perform the administration and maintenance of profiles in transaction RZ10. In the first step, you import the profiles into the database by choosing Utilities→Import profiles→Of active servers. You can change and add individual profile parameters after selecting the profile to edit. For example, SAPinst installs a SAP system with a very small number of work processes.

SAP recommends that you adapt SAP profiles using the transaction RZ10. It is possible to change SAP parameters in the corresponding files on file system level. For example, SAP parameters can be changed when the SAP system cannot be started because of a wrong configuration.

Note

Best practice: Often customers have created a template text file, holding profile parameters concerning password rules to meet security standards and other parameters. After the installation of an application server an initial configuration at file system level is done using this template file. Afterwards the profile parameters are imported using transaction RZ10 – and from now on are maintained via RZ10.

Import and Change Profile Parameters for S4X

Business Example

You want to change some profile parameters for your SAP system S4X.

Steps

  1. Decrease the profile parameter PHYS_MEMSIZE to the value 40%. Increase the number of dialog work processes to 18, batch work processes to 16, update work processes to 4 and update two work processes to 2.

    1. Log on to SAP system S4X, client 000 with your newly created user ADMIN_000. If you are requested to change the initial password to a productive password, set the password according to the master password of the installation of SAP system S4X.

    2. Call transaction RZ10. Choose Utilities→Import profiles→Of active servers. Choose Back.

    3. Choose the instance profile of instance 11, Extended maintenance, and Change.

    4. Change the parameter rdisp/wp_no_dia to 18, rdisp/wp_no_btc to 16, rdisp/wp_no_vb to 4, and rdisp/wp_no_vb2 to 2.

    5. From the menu, choose Parameter→Create, as Parameter Name enter PHYS_MEMSIZE, as Parameter Value enter 40%.

    6. Choose Copy, Copy again, Back, Copy, Back, and Save. Confirm the activation pop up with Yes. Confirm the information pop up. Confirm the note pop up.

  2. Restart the SAP system S4X.

    1. Via MobaXterm, log on to the server s4xhost using the user install and the password provided by your instructor.

    2. Switch to user s4xadm via

      su - s4xadm

    3. Stop the SAP system S4X via

      sapcontrol -nr 11 -function StopSystem

    4. After the SAP system S4X has stopped, start the SAP system S4X via

      sapcontrol -nr 11 -function StartSystem

    5. Switch back to user install via

      exit

  3. Check the results in SAP system S4X.

    1. Log on to SAP system S4X, client 000 with user ADMIN_000.

    2. Call transaction RSPFPAR and check the changed profile parameters.

  4. Later in this course you will install an AAS for this SAP system. After installing the AAS, set the profile parameter PHYS_MEMSIZE of the AAS to 40%, also.

Result

Import and Change Profile Parameters for SMA

Business Example

You want to change some profile parameters for your SAP system SMA.

Steps

  1. Decrease the profile parameter PHYS_MEMSIZE to the value 4096. Increase the number of dialog work processes to 18, batch work processes to 16, update work processes to 4 and update two work processes to 2.

    1. Log on to SAP system SMA, client 000 with your newly created user ADMIN_000. If you are requested to change the initial password to a productive password, set the password according to the master password of the installation of SAP system SMA.

    2. Call transaction RZ10. Choose Utilities→Import profiles→Of active servers. Choose Back.

    3. Choose the instance profile of instance 81, Extended maintenance, and Change.

    4. Change the parameter rdisp/wp_no_dia to 18, rdisp/wp_no_btc to 16, rdisp/wp_no_vb to 4, and rdisp/wp_no_vb2 to 2.

    5. From the menu, choose Parameter→Create, as Parameter Name enter PHYS_MEMSIZE, as Parameter Value enter 4096.

    6. Choose Copy, Copy again, Back, Copy, Back, and Save. Confirm the activation pop up with Yes. Confirm the information pop up. Confirm the note pop up.

  2. Restart the SAP system SMA.

    1. On the WTS, start the SAP MC by opening the file explorer at N:\SAP\SAPMC\servicehttp\sapmc and open the file training_sapmc.jnlp.

    2. Confirm, that you want to run the application.

    3. Wait some seconds (about 10-15).

    4. Ignore warnings.

    5. Left click the entry for SMA and enter user smaadm and password. Click Log on.

    6. Right click the entry SMA and choose Restart.

    7. Confirm the following pop up with hard restart.

    8. In case you are asked to Logon at Database SMA(ABAP) on smxhost (there might be a pop up) enter the user control with the master password set during installation.

  3. Check the results in SAP system SMA.

    1. Log on to SAP system SMA, client 000 with your newly created user ADMIN_000.

    2. Call transaction RSPFPAR and check the changed profile parameters.

  4. Later in this course you might install an AAS for this SAP system, too. After installing the AAS, set the profile parameter PHYS_MEMSIZE of the AAS to 4096, as well.

Result

Standard Job Scheduling

Schedule Standard Jobs

Several different kinds of statistical and technical data is accumulated in the SAP system, such as performance data, job logs, ABAP short dumps, spool data, and so on. This data must be reorganized regularly; therefore, standard reorganization jobs are offered in the SAP system. These standard jobs should run regularly in an SAP system. The job definition or transaction SM36 provides a list of important standard jobs that you should schedule.

Complete the following steps to schedule jobs:

  1. In transaction SM36, select the Standard Jobs screen.
  2. Choose the Component BC in the SAP Component field.
  3. Choose Default scheduling to schedule all the standard jobs with a single click.

    The SAP system schedules all standard jobs along with their specified variants and intervals. You can also schedule the different jobs individually.

Note

In a newly installed SAP S/4HANA Server system, the standard Job scheduling might require some help by you. In case the Job Scheduling does not work as designed, consider SAP Note2311392 — SAP S/4HANA: Job Repository Jobs (Standard Jobs) released with huge delay and not executing.

Note

Please note, that depending on the release of SAP S/4HANA Server you have installed, the button Job Repository as shown above might require the following manual settings: the profile parameter rdisp/job_repo_activate_time has a value greater 0 AND in table BTCOPTIONS the parameter JOB_REPO_ACTIVATE with value PERIODIC_RUN has been set to ON.

Check Standard Jobs in the SAP S/4HANA Server System

Business Example

You want to check standard jobs in the SAP system S4X.

Steps

  1. Check the standard background jobs in the SAP system S4X using the job repository.

    1. Log on to the SAP system S4X, client 000 with user ADMIN_000.

    2. Call transaction SM36.

    3. On the Define Background Job screen, choose Goto→→Job Repository.

    4. In the Technical Job Repository screen choose Execute and check for scheduled jobs in column Job Status.

Schedule Standard Jobs for the SAP Solution Manager System

Business Example

You want to check and schedule standard jobs in your SAP system SMA.

Steps

  1. Schedule standard background jobs for SAP system SMA.

    1. Log on to the SAP system SMA, client 000 with user ADMIN_000.

    2. Call transaction SM36.

    3. On the Define Background Job screen, choose Goto→→Standard jobs.

    4. If the Updated Reorganization Jobs pop up is presented, choose Copy (Enter).

    5. Choose SAP Component, BC, and use the Default scheduling button to create the default scheduling. Confirm the pop up Specify a step user.... Enter DDIC (in capital letters) as the step user.

      Result

      The All standard jobs scheduled message is displayed.

    6. Note the scheduled start time for standard jobs. You might want to modify them in the future using transaction SM37.

Post-Installation Activities for Transport Organizer

System and Client Change Options

If you have installed the SAP system from installation media, the Change and Transport System (CTS) is initialized by SAPinst. For this reason, you do not need to initialize the CTS after the installation. Basic settings for the CTS are generated during this initialization of the TMS.

If you have installed your SAP system as a copy of an existing SAP system, you must initialize the CTS after installation.

If you set up an SAP system that originated from a database copy by selecting the Standard Installation radio button, problems may arise when you transport objects or upgrade the SAP system.

Select the Database Copy or Database Migration radio button if the SAP system was created based on a copy. SAPinst provides utilities to copy and migrate databases of SAP systems.

Once for the entire SAP system, you have to set the system change options. These options control the changeability of repository objects.

You have to maintain the client change options once per the client. Besides others, they control the changeability of repository objects and customizing from within the specific client.

Transport Management System (TMS) Configuration

TMS Configuration – Transport Domain

You should already set up the TMS after the first SAP system of a transport landscape is installed. TMS describes the role of the SAP systems within a transport landscape, for example, development system, quality assurance system, and production system.

Hint

It is not necessary that all SAP systems that should be part of the transport landscape exist from the beginning. The SAP systems that will be installed later can be represented as virtual systems until they exist physically.

After defining the role of SAP systems, the transport sequence is defined by creating transport routes. Optionally, you should also define the quality assurance (QA) procedure to prevent untested objects and customize settings to be imported into the production system.

Hint

The basic configuration of TMS must be done in transaction STMS in client 000. This is especially because a user TMSADM is created in client 000. All subsequent configuration steps can be performed in any client.

TMS Configuration – Transport Routes

TMS Configuration – Transport Routes

The initialization of TMS is done when you call the transaction STMS for the first time. TMS initialization includes the setup of the transport domain controller (TDC).

To create virtual SAP systems or to approve SAP systems choose Overview→Systems in transaction STMS.

To create standard transport routes between SAP systems, choose Overview→Transport Routes→Configuration→Standard Configuration. Select Single System or Development and Production System or Three Systems in Group.

For more complex SAP system landscapes there is a graphical editor available.

Set up TMS for SAP System S4X

Business Example

You want to configure TMS for the SAP system S4X.

Task 1: Set up TMS for SAP System S4X

Steps

  1. Log on to S4X, client 000 with user ADMIN_000.

  2. You do not have to define the transport domain controller - this was done by SWPM, already. SWPM has created user TMSADM in client 000. The transport domain was created by SWPM, consisting out of only one SAP system, S4X. Check the TMS configuration and change the short text of S4X to Development, as S4X should be the future development system.

    1. Call transaction STMS.

    2. The message You are logged onto the domain controller indicates, that TMS was configured and S4X is the transport domain controller.

    3. Choose Overview→Systems.

    4. Select SAP system S4X by double clicking it and switch to change mode by pressing the Display <-> Change button.

    5. In the field Description below the field System enter Development.

    6. Choose Save.

    Result

    You checked, that S4X was defined as transport domain controller by SWPM.

  3. Define two virtual SAP systems, S4Y and S4Z.

    1. To define the SAP systems of the transport domain, call transaction STMS and choose Overview→Systems.

    2. Choose SAP System→Create→Virtual System. The pop up TMS: Configure Virtual System is displayed. In the field System enter S4Y, in the field Description enter Quality Assurance and confirm the pop up with Save.

    3. Choose SAP System→Create→Virtual System. The pop up TMS: Configure Virtual System is displayed. In the field System enter S4Z, in the field Description enter Production and confirm the pop up with Save.

    Result

    Now the SAP systems of the transport domain are defined.

  4. Define the transport routes with S4X as development system, S4Y as quality assurance system, and S4Z as production system.

    1. To define the transport routes, call transaction STMS and choose Overview→Transport Routes.

    2. Choose Configuration→Display <-> Change.

    3. Choose Configuration→Standard Configuration→Three Systems in Group.

    4. The pop up Three-System Group is displayed. As Development system enter S4X, as Quality assurance enter S4Y, as Production system enter S4Z.

    5. Confirm the pop up with Continue.

    6. Choose Save to save the configuration.

    7. The pop up Configuration Short Text is displayed.

    8. In the field Short description enter SAP S4/HANA Server Transport Landscape and confirm the pop up with Enter.

    9. The pop up Distribute and Activate is displayed.

    10. Choose Yes.

    Result

    The standard transport routes are configured and the configuration is distributed among the SAP system landscape.

Result

Now TMS is set up for S4X.

Set up TMS for SAP System SMA

Business Example

You want to configure TMS for the SAP system SMA.

Task 1: Set up TMS for SAP System SMA

Steps

  1. Log on to SMA, client 000 with user ADMIN_000.

  2. You do not have to define the transport domain controller - this was done by SWPM, already. SWPM has created user TMSADM in client 000. The transport domain was created by SWPM, consisting out of only one SAP system, SMA. Check the TMS configuration and change the short text of SMA to Development, as SMA should be the future development system.

    1. Call transaction STMS.

    2. The message You are logged onto the domain controller indicates, that TMS was configured and SMA is the transport domain controller.

    3. Choose Overview→Systems.

    4. Select SAP system SMA by double clicking it and switch to change mode by pressing the Display <-> Change button.

    5. In the field Description below the field System enter Development.

    6. Choose Save.

    Result

    You checked, that SMA was defined as transport domain controller by SWPM.

  3. Define two virtual SAP systems, SMB and SMC.

    1. To define the SAP systems of the transport domain, call transaction STMS and choose Overview→Systems.

    2. Choose SAP System→Create→Virtual System.

    3. The pop up TMS: Configure Virtual System is displayed.

    4. In the field System enter SMB, in the field Description enter Quality Assurance and confirm the pop up with Save.

    5. Choose SAP System→Create→Virtual System.

    6. The pop up TMS: Configure Virtual System is displayed.

    7. In the field System enter SMC, in the field Description enter Production and confirm the pop up with Save.

    Result

    Now the SAP systems of the transport domain are defined.

  4. Define the transport routes with SMA as development system, SMB as quality assurance system, and SMC as production system.

    1. To define the transport routes, call transaction STMS and choose Overview→Transport Routes.

    2. Choose Configuration→Display <-> Change.

    3. Choose Configuration→Standard Configuration→Three Systems in Group.

    4. The pop up Three-System Group is displayed.

    5. As Development system enter SMA, as Quality assurance enter SMB, as Production system enter SMC.

    6. Confirm the pop up with Continue.

    7. Choose Save to save the configuration.

    8. The pop up Configuration Short Text is displayed.

    9. In the filed Short description enter SAP Solution Manager Transport Landscape and confirm the pop up with Enter.

    10. The pop up Distribute and Activate is displayed.

    11. Choose Yes.

    Result

    The standard transport routes are configured and the configuration is distributed among the SAP system landscape.

Result

Now TMS is set up for SMA.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn