Post Installation Steps

Post Installation Steps :-

After Installing R/3 into a new system, Basis has to perform some post Installation steps before handing over to end users for operation. Post Installation steps make sure that System is ready, properly configured, Tuned and take load of user requests.

Below are some standard steps which has to perform immediately after the installation is finished.

PART 1:-

1. Login to SAP system using DDIC/000

2. Execute SE06 , Select Standard Installation and click on execute Perform Post Installation Steps. Click yes on each next screen.

3. Execute STMS , to configure TMS configuration system. If there is no Domain controller in organization then configure this new system as DC.

4. Execute SICK to check for any Installation error , If anything is reported then trouble shoot those errors.

5. Execute sapdba or brtools to check/increase tablespace size if any is >90%

6. IF sapdba then check the tablespace utilization by selecting c. Tablespace Adminitration - c. Free space fragmentation of Tablespaces

7. List out all the tablespaces filled above 90%

8. Add datafiles to corresponding tablespaces to increase the tablespace size and bring the utilization of tablespaces below 80%

9. Login as SAP*/000

10. Execute SCC4 -> Click on change button -> Confirm the warning and click on new entries to create a new client.

11. Execute RZ10 -> Utilities -> Import profiles -> Of Active Servers

12. check the system log in SM21

13. Check any dumps in ST22

14. Login at command prompt using ora<sid> or <SID>adm

PART 2:-

1. login to new client to perform a client copy using SAP*/<new client number>/PASS

2. Perform local client copy procedure to copy new client from 000 client.

3. Once client copy is over , login to new client using SAP* and password of SAP* which was

 used in client 000

4. Execute RZ10 -> Select Instance Profile -> check Extended maint -> click on change.

5. Add parameter login/system_client parameter to make new <client_number> as default client to login.

6. Make changes to dialog process and background if you need to change than default one.

7. Save the profile and activate it.

8. Create one or two super users using SU01 with profiles SAP_ALL and SAP_NEW

9. Create some developer users if you can, else leave it.

10. Stop and Start SAP R/3 for profile parameter to be in effect.

11. Upgrade the kernel to the latest level

12. Upgrade the SPAM version to latest level

13. Apply latest support pack to components SAP_BASIS, SAP_ABAP, SAP_APPL and some other components if it is required.

14. Follow the kernel, SPAM and support pack application methods

15. Now system is ready to login and work for developers and administrator

16. Keep on changing the parameters , system configuration as per requirement later.

17. Run SGEN to regenerate the objects . In this process SAP keeps all the required objects access in SAP buffer. So that transaction accessing becomes faster.

Support Pack Upgrade Process

Support Pack Upgrade Process :-

Support Pack Application:-

1. Check the current patch in your system.

a. Check SPAM Version

b. Check SAP_BASIS patch level

c. check SAP_ABAP patch level

d. Check SAP_APPL Patch level.

To get all the above information follows the following steps:-

Execute SPAM - Check the SPAM level at the top.

Click on Package Level to display all the patches in the system

Note down SAP_BASIS, SAP_ABAP, SAP_APPL patch level in the display.

2. Find out what is the latest patch level available for above components.

Download -> Support Packages and Patches -> Entry by Application Group-> Application Components ->SAP R/3 Enterprise -> SAP R/3 Enterprise 47 X 110 -Entry by component -> SAP R/3 Enterprise Server-> SAP_BASIS620 ->

3. From the list select which component you want and click on it.

E.g.click on SAP BASIS 6.20 and select the patch level 25 you want comparing your current patchlevel. Select all the patches you are behind to current and add to download basket.

All the patches are in .CAR format.

Repeat the same step for all components you want to apply for your system.

4. Download all the patches you added to download basket by using SAP Download Manager.

5. Save all the .CAR files to your local hard drive say C:\supportpacks

6. now transfer all these .CAR files to Your Unix Server where your SAP is running using ftp.

ftp steps

go to command prompt

cd c:\supportpacks

c:\supportpacks\> ftp solsrv (solsrv is the unix servername)

username : SIDADM

password : (Password of SIDADM)

ftp> cd /downloads/supp_pack

ftp> bin

ftp> mput *.CAR (press y for all the confirmations)

ftp> bye

7. Now extract the .CAR files by using executable CAR.EXE

#cd /download/supp_pack

# CAR -xvf <Filename1>.CAR (files are extracted to .../EPS/in folder)

Repeat extraction for all .CAR files

You will get the files with extension .ATT and .PAT

8. Now go to /usr/sap/trans/EPS/in directory and remove the existing files out there.

login as <SID>adm and pasword

# cd /usr/sap/trans/EPS/in

# rm -rf *

9. Now Copy all .ATT and .PAT files to /usr/sap/trans/EPS/in directory

# cp /download/supp_pack/* /usr/sap/trans/EPS/in

# ls –l

10. Login to SAP using a superuser other than SAP* and DDIC to 000 client.

11. Execute SPAM in SAP command line

12. Click on Support Package -> Load Packages -> From Application Server.

Here all the .ATT and .PAT files are converted into proper Patch format and available on SAP level to apply suuport packs as per the requirement.

Click on Back button

13. Now Click on Display/define

14. Ask all the users to logoff from the system OR lock all the users in all business clients using customizing program or SAP tool.

15. Make sure you have full backup of system before applying the patch

and enough downtime to apply the patch

SPAM Update

16. Select support package ->Import SPAM update to update the SPAM version.

Applying Patch

Before Applying the Patch to system, we have to check if there are any objects under modification or any Transport Request in modification condition. IF any then we may have to adjust those prior to applying

the SAP Patch.

Execute SPAU and see if any objects are there to adjust

Execute SPDD to see if any dictionary objects are there to adjust.

Execute SPAM

Click on display/Define

Select the component (e.g. SAP_BASIS)

Select the Patch number (e.g. SAPKB62012)

Click on confirm Queue (\/)

Select Import queue by selecting truck button

Confirm it by clicking on (\/) mark

Patch application is started.

If you encounter error during patch application, start applying again.

Confirm the message

SPAM status is in yellow

Click "confirm queue” button to confirm the queue.

Check the spam status. It should be green.

Support pack application is successful

Click on Package level to see the change.

Phases during sap patch deployment

Phases during sap patch deployment :-

In the status bar, Support Package Manager informs you of the status of the current phase. To find out which phases are executed for which scenario (test or standard scenario), run program RSSPAM10.

The following list provides an overview of all the modules and phases in the order in which Support Package Manager executes them:

Preparation Module:-

1. PROLOGUE

This phase checks whether you are authorized to import Support Packages.

2. CHECK_REQUIREMENTS

This phase checks various requirements for importing a Support Package, for example, whether transport control program tp can log on to your system.

3. DISASSEMBLE

This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.

4. ADD_TO_BUFFER

This phase adds the queue to your system’s transport buffer.

5. MODIFY_BUFFER

This phase prepares the transport buffer so that the following import phases can be processed correctly.

6. TEST_IMPORT

In this phase, a test import is run for the current queue with transport control program tp. The system checks for objects that are in open repairs and that are overwritten during the import, or for other factors that might prevent an object being imported.

7. IMPORT_OBJECT_LIST

This phase imports the object lists for the Support Packages in the queue into the system.

8. OBJECTS_LOCKED_?

This phase checks for objects that are overwritten by the import and are still in unreleased requests.

9. ADDON_CONFLICTS_?

This phase checks for conflicts between objects in the queue and installed add-ons.

10. SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP).

Module Import 1

11. CREATE_VERS_BEFORE

This phase generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).

12.  SPDD_SPAU_CHECK

In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).

13.  DDIC_IMPORT

This phase imports all ABAP Dictionary objects in the queue.

14. AUTO_MOD_SPDD

This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

15. RUN_SPDD_?

In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

16. LOCK_EU (only for import mode downtime-minimized)

This phase locks the development environment.

17.  INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state.

18. DDIC_ACTIVATION

This phase activates the imported ABAP Dictionary objects.

Module Import 2

19. IMPORT_PROPER

This phase imports all the Repository objects and table entries not already imported during the INACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of the name tabs.

20. PREPARE_XPRA

This phase prepares the execution of the XPRAs and after-import methods.

21. UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment.

22. AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.

23. XPRA_EXECUTION

This phase executes the XPRAs and after-import methods.

24. ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source code and screens).

Clean Up Module:-

25.  RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

26. CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts in the database.

27.  EPILOGUE

This phase completes the import. Among other things, it checks whether the queue has been processed completely.