ECC 6.0 Installation on Windows

1. INTRODUCTION
1.1 SAP NOTES FOR THE INSTALLATION

    1680045: Release Note for Software Provisioning Manager 1.0
    1710950: Inst. SAP Systems Based on NW 7.1 and higher: Windows
    1710995: Inst. SAP Systems Based on NW 7.1 and higher: Win Oracle
    1431800: Oracle 11.2.0: Central Technical Note
    1365123: Installation of Diagnostics Agents
    855498 : Installation Prerequisite Checker
    1597765: Known problems with Support Packages in SAP NW 7.31 AS ABAP
    1448655: Inst. 7.30 SP2 - Diagnostics Agent installation
     69455:   Servicetools for Applications ST-A PI ST14, RTCCTOOL and ST12

1.2 INSTALLATION GUIDES

The Master Guide
The Master Guide is the central document for overall implementation process for your SAP system installation. It contains crucial information about the overall implementation sequence that is activities you have to perform before and after the installation process. First we need to read Master guide. You can find a printed version of the Master Guide in your installation package.
Location: service.sap.com/instguides

• Master Guide – SAP NetWeaver 7.3 service.sap.com/installNW73
• Master Guide – SAP Enhancement Package 1 for SAP NetWeaver 7.3 service.sap.com/installNW73
• Master Guide – SAP NetWeaver 7.4 service.sap.com/installNW74
• Installation guide
• Media guide

2. INSTALLATION OPTION
2.1 STANDARD SYSTEM:
In a standard system, all main instances run on a single host.

• Central services instance for ABAP (ASCS instance)
• Database instance (DB)
• Primary application server instance (PAS instance)

2.3 HIGH-AVAILABILITY SYSTEM

In a high-availability system, every instance can run on a separate host.

There are the following instances:

• Central services instance for ABAP (ASCS instance)
• Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory)
• Database instance (DB)
• Primary application server instance (PAS)

2.4 ADDITIONAL APPLICATION SERVER INSTANCE

An additional application server instance can run on:

• The host of any instance of the existing SAP system (exceptions see below)
• On a dedicated host

3. PLANNING

3.1 PREREQUISITES

• You have planned your SAP system landscape according to the Master Guide available at the appropriate download location under service.sap.com/instguides.
• You have decided on your installation option.

3.2 PROCESS FLOW

The following sections list the core software requirements, the choices available to you within the core requirements, and the installation methods that you can use.

1. Determine system requirements.
2. Set up account permissions.
3. Determine network permissions.
4. Choose a web application server.
5. Choose a database server.

3.3 PLANNING THE INSTALLATION

1. Check the hardware and software requirement
2. Make sure that the host name meets the requirements listed in SAP Note 611361.
3. Running the Prerequisite Checker in Standalone Mode (Optional)
4. Plan for Host name , SID , Instance Number
5. Host name : KUNAL_RAI

SID : KUN
Instance Number: 00

6. Master password(Dont give "@" in password)
7. Decide Installation mode – Typical or custom

4. PREPARATION

1. In a Standard system (Central System), all mandatory instances are installed on one host.
2. Change computer name to < 13 characters
3. If you use Windows Server 2008 (R2), you disable the Windows Server 2008 (R2) firewall
4. Change swap space to at least 25GB
5. You check that you have the required user authorization for running SAPinst. Here we created new user (basisadm) as shown in below screen with member of shown group shown below:
6. Change default Windows “Administrator” password
7. You install the latest SAP frontend software on the desktop of the end user. 

Download link for SAP frontend software:
https://websmp104.sap-ag.de/support
Path:
Software Downloads >Installations and Upgrades > Browse our Download Catalog > SAP Frontend Components > SAP GUI FOR WINDOWS > SAP GUI FOR WINDOWS 7.30 CORE >Installation
Select: NW 7.0 Presentation - 7.30 Compilation 2 Present

8. Install JRE
9. You make sure that the required installation media is available on Server.

4.1 HARDWARE CONFIGURATION USED
The following tables show the System configuration used for installation of
Enhancement Package 6 for SAP ERP 6.0

Hardware Requirement Hardware Configuration Used
Operating System              Windows Server 2008 (R2)
Disk Space                        1TB
Installed RAM                    8GB

5. INSTALLATION

Installation has following six parts

1. Preparing OS and system for SAP installation
2. Install JAVA
3. Set the Virtual Memory
4. Installation SAP Database
5. Installation of SAP Central Instance
6. Post-Installation tasks, i.e. Applying patches, upgrades etc.

5.1 HARDWARE AND SOFTWARE REQUIREMENTS

Hardware Requirement	Requirement
Minimum disk space	Database software: 2 to 5 GB Central services instance for ABAP (ASCS) (not including paging file): 5 GB (x64) Database instance (not including paging file): 35 GB In addition you require 1.5 GB for the diagnostics agent Temporary disk space for every required installation medium that you have to copy to a local hard disk:4.3 GB
Minimum RAM	All instances, except SAP host agent, and diagnostics agent: 4 GB SAP host agent: 0.5 GB Diagnostics agent: 1 GB
Paging file size	For more information, see SAP Note 1518419.

Software Requirement	Requirement
Windows operating system	64-bit version of  Windows Server 2008 (R2) : For any version of Windows Server, you need the latest supported service pack
Database software	Database instance: Database server software for Oracle 11g

5.2 MEDIA LIST FOR ENHANCEMENT PACKAGE 6 FOR SAP ERP 6.0
Media List - Enhancement Package 6 for SAP ERP 6.0

Abbreviation Used in the Installation Guide	Label(Physical DVD)	SAP Service Marketplace Names (Names of Packages Downloadable from http://service.sap.com/swdc)
Software Provisioning Manager 1.0	SWPM10SP03_7-20009707.SAR	SW Prov. Mgr. 1.0 SP03 for systems based on NW7.1x or higher
SAP Kernel DVD for installation SWPM	·         SAP KERNEL 720_EXT ·         SL CONTROLLER 700	·         720_EXT UC Kernel for SWPM SP04 - Windows Server x64 64bit ·         SL CONTROLLER 700 for SWPM SP04
EHP6 FOR SAP ERP 6.0Installation Export	EHP6 FOR SAP ERP 6.0Installation Export	SAP ERP 6.0 EHP6 Installation Export 1 of 8  SAP ERP 6.0 EHP6 Installation Export 2 of 8  SAP ERP 6.0 EHP6 Installation Export 3 of 8  SAP ERP 6.0 EHP6 Installation Export 4 of 8  SAP ERP 6.0 EHP6 Installation Export 5 of 8  SAP ERP 6.0 EHP6 Installation Export 6 of 8  SAP ERP 6.0 EHP6 Installation Export 7 of 8  SAP ERP 6.0 EHP6 Installation Export 8 of 8
RDBMS Client DVD	ORACLE Client 11.2.0.3	ORACLE Client 11.2.0.3

5.3 INSTALLING THE ORACLE 11G DATABASE SOFTWARE
5.3.1 PREREQUISITE

• Windows Server 2008 (R2)
• Database Media – ORACLE

Abbreviation Used in the Installation Guide	Label(Physical DVD)	SAP Service Marketplace Names (Names of Packages Downloadable from http://service.sap.com/swdc)
ORACLE RDBMS DVD	ORACLE 11.2.0.3 64-BIT RDBMS Windows Server on x64 64bit	ORACLE RDBMS 11.2.0.3 Windows x64 1 of 6  ORACLE RDBMS 11.2.0.3 Windows x64 2 of 6  ORACLE RDBMS 11.2.0.3 Windows x64 3 of 6  ORACLE RDBMS 11.2.0.3 Windows x64 4 of 6  ORACLE RDBMS 11.2.0.3 Windows x64 5 of 6  ORACLE RDBMS 11.2.0.3 Windows x64 6 of 6

On the database server, place the Oracle RDBMS DVD and change to the directory :<DVD_DRIVE>:\database\SAP\
Start the Oracle Universal Installer (OUI) by double-clicking the file sapserver.cmd.

1) Specify the drive letter of the local disk where you want to install the Oracle software, and the <DBSID>.
2) Do not select the check box. Choose Next.
3) The installer issues a warning. Choose Yes and then Next.
4) Choose Skip Software updates and then Next.
5) Confirm the default selection Install database software only and then choose Next.
6) Confirm the default selection Single instance database installation and then choose Next.
7) Select Product Languages Confirm the default option English and then choose Next.
8) Select Database Edition Confirm the default option Enterprise Edition and then choose Next.
9) Choose Next
10) Perform Prerequisite Checks This window checks if all the required system prerequisites for the installation of the database software have been me
11) Choose Install
12) After the installation has finished successfully, close the Oracle Universal Installer.

5.4 INSTALLATION OF ENHANCEMENT PACKAGE 6 FOR SAP ERP 6.0

1) Uncar Software Provisioning Manager 1.0 SWPM10 with following command
Sapcar –xvf 70SWPM10SP01_3-20009707.sar–R < Location of New Folder>
2) Run the correct version of “sapinst.exe” (Install master folder\Data_Units\BS2011_IM_Windows_x86_64
After Completion of extraction run the installation tool SAPinst from < Location of New Folder>
3) Go to SAP Business Suit 7i 2011>Enhancement Package 6 for SAP ERP 6.0>SAP Application  Server ABAP > Oracle >Central Systems >Central Systems >Choose Next
4) Choose Typical > Choose Next
5) Give SAP System ID and  Installation Drive as Input > Choose Next
6) Give  Master Password as Input  >  Choose Next
7) Give Database ID given during Installation Database Software > Choose Next
8) Choose  LABEL.ASC in folder label  SAP KERNEL 720_EXT  for  Package Location in Medium UC Kernel NW 7.20 /7.21
9) Choose LABEL.ASC in folder label EHP6 FOR SAP ERP 6.0 Installation Export  for Package Location in Medium Installation Export 1 ECC 6.0 EhP6 > Choose Next
Here when you unzip/extract EHP6 FOR SAP ERP 6.0 Installation Export 1-8 files ,you will get two folders (for example: 51041989_1,51041989_2) which is Installation Export 1 ECC 6.0 EhP6, Installation Export 2 ECC 6.0 EhP6 respectively.
10) Choose LABEL.ASC in folder label EHP6 FOR SAP ERP 6.0 Installation Export  for Package Location in Medium Installation Export 2 ECC 6.0 EhP6>  Choose Next
11) Give Password for  ABAP Schema is SAPSR3
12) Choose Next
13) Choose LABEL.ASC in folder label SL CONTROLLER 700  for  Package Location in Medium  Kernel NW 7.20 /7.21 > Choose Next
14) Choose LABEL.ASC in folder label RDBMS Client DVD (ORACLE Client 11.2.0.3 )
15) Choose Next  here we install Diagnostic agent
16) Choose Yes
17) Choose No SLD Destination >  Choose Next
18) Choose Next
19) Installation is in Progress
20) Files created (Ex: d:\oracle\KUN\sapdat1\sr3_10)
21) Roughly 15 hours to reach the “Perform ORA  Post load activities” phase
22) Roughly 19 hours to reach the “create database statistics” phase
20) Completion of Installation
Finally the installation complete, a message pop-up showing the installation is successful and the SAP system is up and running. (The installation takes almost 24 hours to complete)
21) Choose Ok

6 POST INSTALLATION
6.1 CHECK WHEATHER YOU CAN LOGIN TO SAP SYSTEM
6.2 PERFORM A CONSISTENCY CHECK

To perform a consistency check, call transaction SICK

6.3 APPLY THE SAP LICENSE

After you raise a request to SAP for SAP License, SAP will send you the license key text to the provided mail ID. Once the text is available on your mail
Please download the text file on desktop install the license with T-code – SLICENSE

6.4 CLIENT COPY

1) ISU : Create a new client: 300 (Productive Client No)
For Example: here we are taking ISU as system SID and 300 as client no.
Transaction: SCC4
2) Added the parameter login/no_automatic_user_sapstar = 0 for logging in with sap* user .
Change the Parameter login/system_client from 001 to 300
3) Restarted the SAP system ISU.
4) Once SAP SYSTEM is up and running. Login in Client 300 as sap* and password pass
5) Transaction : SCCL
Copy client 000 (transaction SCCL) and use profile "SAP_ALL"
Choose Schedule as Background Job
6) Choose Schedule Job
7) Choose OK
8) Follow screens shows successful completion of Job.

6.5 EXECUTION OF SAP LOAD GENERATOR

1) Login to Client 001 and Execute t-code SGEN
2) Select Generate All Objects of Selected Software Components and click "Continue" button
3) Select All Software Components and click "Continue" button
4) Select All Software Components and click "Continue" button
5) For quicker execution, the load generator bases itself on a parallelprocedure which incorporates available servers as much as possible. The defaultselection is the server used for this transaction and the computers with the same type Select Application Server and click "Continue" button
6) Select Job and execute option Start Job Directly
After execution we get message as: The generation job was successfully scheduled or started
7) Use the Job Overview to view the running status of Job and wait until it is finished.
8) Login with DDIC in client 000 and execute “se06” and click on Perform Post installation Action
9) Click Yes

Support Packs installations

Support Packs
Support pack installations are mini-upgrades, the purpose of a Support Pack is to provide a bundle of fixes that have all been tested together. A Support Package corrects errors in the SAP System or makes necessary adjustments, for example, due to legal changes. The objects affected are replaced in your system.Each Support Package is valid for only one release (but for all databases and operating systems) and requires an exactly defined number of predecessors.

The following types of Support Packages are available:

• SPAM/SAINT Update: A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool.
• FCS Support Package: An FCS Support Package (FFD) updates an FCS system to its General Availability release so that other Support Packages can be imported.
• Component Support Package: This type of Support Package (COP) is valid for one software component (SAP_BASIS, SAP_HR, SAP_APPL) and contains corrections to errors in the Repository and Dictionary in this software component only.
• BW Support Package: A BW Support Package (BWP) is a Support Package for the software component SAP Business Information Warehouse (SAP_BW) and only contains corrections for this component.
• Add-On Support Package: An Add-On Support Package (AOP) is valid for an add-on with a particular release and contains corrections for this add-on.
• Conflict Resolution Transport: A Conflict Resolution Transport CRT is exclusively used for add-ons, for example, IS-IS or IS-OIL. It resolves conflicts that can occur between Support Packages and an add-on.

Before going to applying support packages you should follow the some prerequisites:

1. SPAM/SAINT should be latest version( always apply support packages to the level n-1)
2. No aborted packages in your system
3. Minimum two background work process are available
4. Free space in EPS directory
5. Must read the note for following sequence of support packs
6. Latest Kernel version (Upgrade "Kernel")

Update Saint Tool:

1. Download required version
2. Uncar and keep in eps/in
3. Go to SPAM
4. Go to Support Package
5. Click import saint/spam update
6. This step will take some time and then  click on green ok button
7. Some time it will throw error ….no need to worry just go to spam steps 5 again and the version will change  
8. http://www.sapbasistuts.com/home/abap-stack/abap-stack-wiki/sap-spam-saint-update

SPAM Steps 
The SAP Patch Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.
The following list explains the steps executed by SPAM in the order in which they are performed.
1.PROLOGUE: In this step, the system checks if you are authorized to import Support Packages.
2.CHECK_REQUIREMENTS: In this step, various requirements are checked for importing a Support Package, for example, the transport control program tp logging on to your system.
3.DISASSEMBLE: In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in the directory.
4.ADD_TO_BUFFER: In this step, the queue is put into the transport buffer of your system.
5.TEST_IMPORT: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
6.IMPORT_OBJECT_LIST: In this step, the object lists for the Support Packages in the queue are imported into the system.
7.OBJECTS_LOCKED_?: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
8.SCHEDULE_RDDIMPDP: In this step, the transport daemon (program RDDIMPDP) is scheduled.
9.ADDON_CONFLICTS_: In this step, the system checks if there are conflicts between objects in the queue and installed add-ons.
10.SPDD_SPAU_CHECK: In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).
11.DDIC_IMPORT: In this step, all the ABAP Dictionary objects of the queue are imported.
12.AUTO_MOD_SPDD: In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
13.RUN_SPDD_: In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.
14.IMPORT_PROPER: In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.
15.AUTO_MOD_SPAU: In this step, the system checks if modifications can be adjusted automatically.
16.RUN_SPAU_: In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.
17.EPILOGUE: In this step, the import of the Support Package is ended. The system checks if the queue has been completely processed.

• Log files will be under /usr/sap/trans/log. Log files are not created for all the phases.
• If you want to know which steps are executed for which scenario, run the program RSSPAM10 

Steps to applying SAP Support packages

1. Login from DDIC and enter Tcode SPAM, Click on Package level to know the existing level of the support packs and the add-ons.
2. Go to transaction SPAM and Load the support packages from frontend if it is < 10 MB. The support packages which are in the form of .car will be decompressed into eps/in directory.  
3. If the size is > 10mb, copy the support packages to /trans directory and uncar the support packages using the below command 
4. cmd>cd usr\sap\trans
5. sapcar –xvf <filename>.car
6. The command SAPCAR will decompress the CAR file and put two files (with extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory.
7. Go to SPAM from DDIC and client 000 and click on Display/define A box will appear with the Support Package categories, Click on the category for the support packages that you uploaded and it will list them in order. You can apply them individually or the whole list at one time.
8. Go to support package click import queue (or) Click on truck icon.
9. Click on continue after importing in to the Queue.
10. Click Continue.

Note: - While applying support packages it triggers two phases SPAU and SPDD 

• SPDD

When the support packages contain any changes in the data dictionary then this phase is invoked.

• SPAU

When the support packages contain the changes related to repository objects SPAU phase is invoked.  it prompts whether to keep to existing changes modified by notes or adapt to changes.

Modification Adjustment during Import of Support Packages Use: - If SAP modified objects that have also been modified by the customer, a modification adjustment is executed in the transactions SPDD and SPAU during import of Support packages.

Procedure

• As far as the modification adjustment is concerned, you use the common procedure described below to import Support Packages:
• Create two change requests in the Workbench Organizer (transaction SE09), one for the modification adjustment with transaction SPDD and the other one for the modification adjustment in transaction SPAU.
• Create a task for each developer who is involved in the modification adjustment.
• The developers must use transactions SPDD and SPAU to determine whether to retain or delete the modifications.
• After modification adjustment is finished, the developers must release their tasks.
• Use transaction SPAM to access the SAP Patch Manager.
• Choose Patch -> Import Patch Queue. A confirmation dialog window appears.
• Choose Enter to finish the import process of the Support Package.
• Release the change requests that result from the modification adjustment using transactions SPAU and SPDD.

It prompts you the Queue is imported successfully and asks to confirm the queue.
Go to -> SPAM -> Support Package -> Confirm the Queue
This shows the support package has implemented for the one of the queue and you need to do the same as for the other queue (software components).

Post processing for support package 

1. Check if any alerts or error messages in SICK and SM21.
2. Release all the background jobs (BTCTRNS2).
3. Unlock all the users.
4. Run SGEN (SGEN compiles all programs.SGEN reduces abap load on the system).

ABAP Stack SP Upgrade:

1. Download required sp's from service marketplace.
2. Extract downloaded files to your "saptranshost"
3. Logon your system (client 000) with user that has "SAP-ALL" authorization.
4. Run transaction SPAM, define queue, and start import.

JAVA Stack SP Upgrade:

1. Download required sp's from marketplace.
2. Unpack the files or move them to the "saptranshost" depending of your release.
3. Run SAPINST or JSPM depending on your release.

ABAP+JAVA Dual Stack systems SP Upgrade:

• Patch ABAP Stack as described.
• Patch JAVA Stack as described.

Question and answer:
Q. When you will apply patches? Give short of examples the situation, where to troubleshoot you have applied patches!
Q.Why it`s required to shut down all SAP, Database instances & services during kernel up-gradation.
A. Because SAP system and database uses kernel service starsapsrv.exe for their functioning, if the service file to be updated is in use, kernel upgrade is not possible then. 
Q. Why it`s required to keep all instances up during the updating hot package?
A. Because SAP system process the system tables/object and modifying them during updating hot package besides hot packages are the most basis packages required for SAP system to work fine. 
Q. Can we apply higher version Patch Level using lower version of SPAM? 
A. NO
Q. What is importance of Import Queue?
Maintain the support packs selected. 
Check the dependency, actually queue can’t be defined unless the dependencies of selected components meet and let them apply in order. 
Q. Can we apply higher level of HR or other Financial Patch with lower version of ABAP/BASIS patch level?
A. Never. Because SAP Basis/ABAP are the most basic components that need to be updated before you can update any components. 
Q. Is there any sequence to apply hot packages?
A. Means, BASIS – ABAP – HR – FIN or HR – FIN – ABAP – BASIS vice versa Basis and ABAP should be at first then others. 
Q. BASIS and ABAP patch level should be same. So first which patch level should be updated ABAP or BASIS? If BASIS then why? If ABAP then why?
A. Not necessary for them to be at same patch level. Though standard says they should be at same level.  Generally we apply BASIS and ABAP together. If we have to apply one at first, it should be basis. 
Q. Why you update SPAM version before applying other patches? What is the logic behind this?
A. A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool. 
Q. How you will decompress the downloaded compressed patch files? After decompression what are the two files generated. State the names of that files & type of the files? 
A. SAPcar –xvf filename.sar
They will contain PTT and ATT files.
Q. Why we login as DDIC user at the time of patch administration? If we logged as different user, what will the problem?
A. Users are locked generally for SPAM upgrade. Hence use DDIC, its standard SAP user. 
Q. Updating the patch level means Updating of SAP system or Upgrading SAP system?
A. Updating the SAP system
Q. Why Support packages are required
A. A support packages is a quantity of corrected SAP objects.
Support packages are required to correct errors in various components. This is done by replacing erroneous objects with corrected versions of these objects.
Each software component has a separate sequence of Support Packages. 
Q. How from Client 000, all clients exists in SAP system get effected?  In which table these stored?
A. It updates standard table’s objects and data dictionary objects which are accessible by all the clients.