ASAP ROADMAP
The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. ASAP Methodology for Implementation is the SAP roadmap for implementing SAP solutions in a cost-effective, speedy manner.
Standard ASAP 8 Methodology Phases-The Standard ASAP 8 Methodology is structured into the following phases.
1. Project preparation - During this phase the team goes through initial planning and preparation for SAP project.
2. Business blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. In Standard ASAP 8 Methodology the result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops
3. Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration in Standard ASAP 8 Methodology is done in two work packages: Baseline configuration (major scope); and Final configuration (remaining scope). During this phase the solution is also tested.
4. Final preparation - The purpose of this phase is to complete the final preparation (including technical testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.
5. Go-live support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.
6. Operate - During this phase the system is operated with the help of the central operation platform, SAP Solution Manager, with the documented solution based on the transferred project documentation.
Need of phases
These phases are the main milestones for your SAP System implementation project. Each phase has:
•Work packages, which consist of activities, for which project teams are responsible.
•Activities, which consist of tasks, which are processed by one or more team members.
•Tasks, which are carried out by a project team member. You can also access the How-to sections and accelerators at this level.
What is an SAP EHP Upgrade?
It's the installation of a new SAP ERP software version, together with the accumulation of all the relevant fixes in the form of a Support Package Stack.
Upgrade Tools
•PANAYA
•SUM
•solution browser
•SAPUp – SAP Upgrade
•SAPEhpi - SAP enhancement package installer
•SUM – Software Update Manager
SUM
Traditionally for applying SPS we use SPAM for ABAP & JSPM for Java
Some of the benefits of using SUM tool over these tools among others are
•Two different tools are not required to apply SPS. One SUM tool is used.
•No need to uncar the SAR files.
•Minimum downtime (Single downtime for both ABAP & Java combined).
•Simultaneously the SPS are applied to both the stacks.
Note:
Before you start the SUM tool do ensure that
•Latest Kernel is applied to the Source System
•Latest SPAM patch is applied.
Clone Mode: The Software Update Manager checks the tables in the database which will be cloned to the shadow system later on during the update. Here a shadow instance will be created with tables copied from source system.
Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied
SUM STEPS:
0. Administrator user and pass
1. Welcome:
2. Specify credential:
3. Select target:
4. Conform target:
5. Execute process:
5.1 Initialization
5.2 Extraction
5.3 Configuration
5.4 Check
5.5 Preprocessing
5.6 Execution
5.7 Post processing
5.8 Finalization
5.2 Extraction
5.3 Configuration
5.4 Check
5.5 Preprocessing
5.6 Execution
5.7 Post processing
5.8 Finalization
6. Summary:
PRE STEPS:
1. Install maintenance license2. Prepare stack.xml and download software.
3. Install SUM as <sid>adm
STEPS:
1. cd /sapcd/XXX702SPS08
2. SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R /usr/sap/<sapsid>
3. SAPCAR -xvf SUM10SP08_1-20006543.SAR -R /usr/sap/xxx
4. Change ownership to sidadm:sapsys on /usr/sap/XXX/SUM
5. Change permission to 777 on /usr/sap/XXX/SUM
4. Create and/or give Basis user in 000 and 300 client, assign SAP_ALL and SAP_NEW in system being upgrade.
5. Recommendation for Oracle 11.2: Apply latest Patch Set
6. Turn off backup
6. Database Passwords: Do not use the '@' character in your database passwords, as the Software Update Manager cannot handle the passwords then.
7. Increase the OPEN_CURSORS Parameter:Alter system set open_cursors = 20000 scope=both;
8. UPDATE STATS
brconnect -u / -c -f stats -t oradict_stats
brconnect -u / -c -f stats -t system_stats
brconnect -c -u / -f stats -t all -f collect -p 4
Note:
Oradict_stats: Collects statistics for Oracle dictionary objects using DBMS_STATS package. For more information, see SAP Note 863811.
system_stats: Collects system (CPU, I/O) statistics using the DBMS_STATS package. For more information, see SAP Note 601395
9. Calculate Space Statistics before the Upgrade/Update
brconnect -u / -c -f stats -t all -m +I -s P1 -f allsel, collect, method, precision -p 4
10. Make copy of profiles.
11. SAPSR3 Tablespace free space should be more than 75GB free
12. Make sure there’s no lock objects – release all transports
13. Turn off archive mode (If you can’t, you’ll have a chance to do so before downtime)
14. Check disk space in the file systems, SUM and current SAP mounts need to have at least 200GB free or larger
15. Check DIR_TRANS, clean up /EPS/in directory
16. Add more data files to tablespaces
17. Check path and empty /usr/sap/trans/EPS/in
UPGRADE:
1. Start SUM as <sid>adm
STEPS:
1. cd /UPGRADE/SUM/SUM/
2. ./STARTUP (It Will Start SL Controller)
3. Run SUM GUI
5. CD /UPGRADE/SUM/SUM/SDT/EXE
6. ./DSUgui
OR from Browser
4. http://<host name>:4239
2. Start phases
SUM STEPS:
0. It will ask for Administrator user and pass we can give any user name and pass but this person will be responsible for whole upgrade. The role should be Administrator.
1. Welcome: In this phase we generally get the information of Detected SAP NetWeaver System. Like System technology: ABAP SYSTEM id: KUN, System Directory: /usr/sap/KUN It also recommended Reading note 1790828
2. Specify credential: this Part Used to ask about SIDADM Password so Provide KUNADM as user and password as *******
3. Select target: This part having two options one for Stack.xml file and manually prepared directory. We choose the location of Stack.XML File with XML name. EX-/usr/sap/KUN/ECCEHP6/SMSDXML_KUN_20130816212838.269.xml
4. Conform target: target release is confirmed here it will show current version and ehp of system and the target version of the system where we are going also it will say to enter a keyword from a snote mention in the screen.
5. Execute process
5.1Initialization:
5.2 Extraction: Once you click next to go to Extraction Phase, it will ask for DDIC user Password and also Database user SYSTEM password. The Extraction phase will extract the relevant files from the download directory.
Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied.
ERROR!!
Solution:
You’ll need to manually exchange R3trans & TP from /sapcd/sapcd/KUNUpgrade2013/KernelDuringKUNUpgrade***cp R3trans tp /usr/sap/KUN/SUM/abap/exe
Restart SUM step
5.3 Configuration: Here we mainly choose standard option and don’t check the check boxes about archiving and expert mode. Here it will ask number of Processes during up time and during down time like Batch, DDL, R3Trans etc. Usually we keep default Value. After 2 Hours we will get another screen which will ask for Addons. The Java configuration steps also starts. With SUM tool you can choose to automatically update the additional dialog instances if any. In older times we had to manually uninstall and install dialog instances
5.4 Check: It will check for the Spaces in database. If space is not available then create Tablespace for space
Solution:
create tablespace PSAPSR3731 extent management local autoallocate segment space management auto datafile '/oracle/XXX/sapdata2/xx3731_1/xx3731.data1' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_2/xx3731.data2' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_3/xx3731.data3' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_4/xx3731.data4' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_5/xx3731.data5' size 10000M autoextend off
OR Send an email to the DB2 Team to add the space
5.5 Preprocessing: In this phase SUM prepare the system for Upgrade.
Here we will have to move the SPDD TR#DR2K900020 into shadow system
Make sure the data & cofiles are available in /upgrade/SUM/SUM/abap/cofiles & /upgrade/SUM/SUM/abap/data with correct owner ship & permissions
Login to KUN shadow system with DDIC/000 client and create an dummy user (abapddic is created) user with su01 with an copy from DDIC
Goto SE06 ->System change option and check if it is modifiable
Import the SPDD TR into shadow system
Execute SE38-> UPGACTKORR
Give the SPDD TR(DR2K900020) in the Request name and execute. This will activate the request in the shadow system
Later on confirm with the Abap Team on SPDD TR and proceed further with the upgrade once everything is fine.
Error – “SQL10003C There are not enough system resources to process the request. The request cannot be processed. SQLSTATE=57011”.
Solution – Sent mail to DB2 DBA Team to increase the database buffer.
Possible Error: Batch job RSVBCHCK Failed with error code 8
SM13: Repeat or Delete all update records
1873772 - Last error code set: Single errors (code <= 8) found in logfile 'PSVBCHCK.ELG'
Transaction LBWQ; Delete all queues;
Transaction LBWG; Delete 06/13
5.6 Execution: In this phase SUM perform actual update in the system and downtime begin this phase take a long time.
Error occurred during the XPRAS execution
Solution – Continued by selecting Accept on “Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG”.
Other Solution:
This is due to multiple active BADI implementations. READ 1835882 - Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple active implementations
Steps to recover:
- Unlock TP
- Cd /usr/sap/trans/SRD/bintp unlocksys SID pf=TP_DOMAIN_SRD.PFL
- Login to client 000, unlock scc4 and se06SE18, Enhancement implementation à overview, double click the new /LOCSRM/***, deactivate that new BADI implementation, create new transport and release it before continue.
When finish, repeat the phase
Possible Error: Calling usr/sap/XXX/DVEBMG/tp failed with return code 8.
Solution: Note 912369 - FINB_TR_DEST, after import failures, transport errors
Transaction: /nFINB_TR_DEST at client 000
Create RFC FINBTR@XXXCLNT001 and FINBTR@XXCLNT300; Under RFC, input client with DDIC user/pwd.
1 .In the next Screen it will ask u to take Backup of ur database if you already done click action completed and hit Next.
2. End of downtime notification
5.7 Post processing:
In this phase system will unlock and downtime finished. In this phase some manual action required some of them are
1. we can reschedule the periodic job which has been DE schedule during downtime.to reschedule these job we can run a report BTSTRNS2 using DDIC user in transaction SE38.
2. Application specific post upgrade activity. Start ASU toolbox using transaction /ASU/UPGRADE
3. see the log of SUM from usr/sap/XXX/SUM/ABAP/log/LONGPOST.LOG and from message class and message number we and applied the relevant Snote.
5.8 Finalization
6. Summary: This phase will give the target version which completed and total time and system downtime.
POST UPGRADE
1. Implement note 1720495 before you start transaction SPAU (Note 1790828); Manual step is not needed. Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU
2. If you have SAP Kernel 7.10 or higher:
Execute the following commands:
cd <update directory>/abap/exe
./oraroot.sh <SAPSID>
If you have an MCOD system and/or the database name does not correspond to the SAP system name, use the following command to run oraroot.sh:
./oraroot.sh <SAPSID> <DBSID>
If you have one kernel directory: cd /usr/sap/<SAPSID>/SYS/exe/run
If you have two kernel directories: cd /sapmnt/<sapsid>/exe/(n)uc/<platform>
cp -p ./icmbnd.new ./icmbnd
chown root:sapsys icmbnd
chmod 4750 icmbnd
exit
cd $ORACLE_HOME/dbs
cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.sql sapdba_role.sql
sqlplus /nolog @sapdba_role.sql SR3
Execute the following commands:
cd <update directory>/abap/exe
./oraroot.sh <SAPSID>
If you have an MCOD system and/or the database name does not correspond to the SAP system name, use the following command to run oraroot.sh:
./oraroot.sh <SAPSID> <DBSID>
If you have one kernel directory: cd /usr/sap/<SAPSID>/SYS/exe/run
If you have two kernel directories: cd /sapmnt/<sapsid>/exe/(n)uc/<platform>
cp -p ./icmbnd.new ./icmbnd
chown root:sapsys icmbnd
chmod 4750 icmbnd
exit
cd $ORACLE_HOME/dbs
cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.sql sapdba_role.sql
sqlplus /nolog @sapdba_role.sql SR3
3. Call transaction STMS and choose OverviewSystems.
Double-click the system that has been upgraded and switch to the Change mode.
Do not change anything unless another action requires changes, and choose Save. Go back to the system overview.
4. Checking for Unused Indexes
Call transaction DB02.
Choose Missing Tables/Indexes.
Choose Unknown objects in ABAP Dictionary.
Check if there are unused indexes in the database. If this is the case, delete them manually.
For more information, see SAP Note 1227270
Double-click the system that has been upgraded and switch to the Change mode.
Do not change anything unless another action requires changes, and choose Save. Go back to the system overview.
4. Checking for Unused Indexes
Call transaction DB02.
Choose Missing Tables/Indexes.
Choose Unknown objects in ABAP Dictionary.
Check if there are unused indexes in the database. If this is the case, delete them manually.
For more information, see SAP Note 1227270
5. Oracle: Deleting Tablespaces
Select table_name, tablespace_name from dba_tables where TABLESPACE_NAME='PSAPSR3702';
Select index_name from dba_indexes where tablespace_name='PSAPSR3702';
Note 1819182 - Tables (TTREE*) remain in old exchange tablespace
In transaction SE13 or SE11, change the data type SSEXC to APPL0 for the tables and activate your data. After you do this, you can use
a) SE14
b) ICNV
c) DB tools
to move the table to a different tablespace (for TABART APPL0).
SE11-> Technical Setting -> change data class from SSEXC to APPL0
Check TAORA for APP0
1. Call transaction ICNV and read the online documentation ("I" button"). Converting a table using ICNV is a complex procedure during which, for example, changes to the table contents are made using a database trigger. It is important that you have a basic understanding of how the transaction works.
2. Call transaction SE14, enter the name of the table that you want to move and select "Edit" and then "Storage Parameters".
3. Select "For new creation" and use the "current database parameters" as a template (if required). Switch to "Change" mode.
4. After "TABLESPACE" and "INDEXSPACE", enter the new tablespaces required for the tables or index data.(Change PSAPSR3702 to PSAPSR3)
5. Save your entries.
6. Call transaction ICNV.
7. Select "Edit->Add table" and enter the name of the table that you want to move. Do not change the proposed scenario.
8. Follow the steps proposed by the wizard (choose "Assistant" or perform the following steps manually using the "Control" menu).
a) Initialization
b) Data transfer
c) Transfer
d) Delete entry
Shutdown Oracle;
brspace –f tsdrop
brspace -c force -o process, time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3
Problem:
ZPPSFIF004
But when I was trying to upload a file from application server to table using a z program found the below error.
Solution:
Fix RFC WEBMETHOD.
#1859173 - Taking into account of external services in SU25, improved display in step 2b
#1850378 - Handling of (historically created) defective modification flags in SU24 data by SU25
#1878702 - Optimizing the navigation in step 2b and the transport connection
6. Make sure client 000 is locked in SCC4Select table_name, tablespace_name from dba_tables where TABLESPACE_NAME='PSAPSR3702';
Select index_name from dba_indexes where tablespace_name='PSAPSR3702';
Note 1819182 - Tables (TTREE*) remain in old exchange tablespace
In transaction SE13 or SE11, change the data type SSEXC to APPL0 for the tables and activate your data. After you do this, you can use
a) SE14
b) ICNV
c) DB tools
to move the table to a different tablespace (for TABART APPL0).
SE11-> Technical Setting -> change data class from SSEXC to APPL0
Check TAORA for APP0
1. Call transaction ICNV and read the online documentation ("I" button"). Converting a table using ICNV is a complex procedure during which, for example, changes to the table contents are made using a database trigger. It is important that you have a basic understanding of how the transaction works.
2. Call transaction SE14, enter the name of the table that you want to move and select "Edit" and then "Storage Parameters".
3. Select "For new creation" and use the "current database parameters" as a template (if required). Switch to "Change" mode.
4. After "TABLESPACE" and "INDEXSPACE", enter the new tablespaces required for the tables or index data.(Change PSAPSR3702 to PSAPSR3)
5. Save your entries.
6. Call transaction ICNV.
7. Select "Edit->Add table" and enter the name of the table that you want to move. Do not change the proposed scenario.
8. Follow the steps proposed by the wizard (choose "Assistant" or perform the following steps manually using the "Control" menu).
a) Initialization
b) Data transfer
c) Transfer
d) Delete entry
Shutdown Oracle;
brspace –f tsdrop
brspace -c force -o process, time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3
Problem:
ZPPSFIF004
But when I was trying to upload a file from application server to table using a z program found the below error.
Solution:
Fix RFC WEBMETHOD.
#1859173 - Taking into account of external services in SU25, improved display in step 2b
#1850378 - Handling of (historically created) defective modification flags in SU24 data by SU25
#1878702 - Optimizing the navigation in step 2b and the transport connection
7. Set SE06>System Change Option back to original
8. Shutdown SAP
As root, run ./saproot.sh SID in /sapmnt/SID/exe
Rename folder /oracle/netbackup_script.bak to netbackup_script.bak
Create link for netbackup
IMPORTANT QUESTION:
Q. How we will know that shadow instance has been created in preprocessing Phase?
A. Pf – ef | grep shd Note: Shadow instance will +1 more than instance, 00 will 01
Q. There is a report we need to run in preprocessing Phase during SPAU/SPAD?
A. UPGACTKORR Its Activate Request in Shadow System.
Q. How to unlock shadow system and why we use it?
A. usr/sap/sid/upg/abap/bin
./sapup unlockSHD SSH
Q. How many Minimum Background work processes needed in EHP Upgrade?
A. 4
Q. What used to happen during Downtime?
A. 1. Kernel Switch from old kernel to new kernel
2. Table conversion
3. User will not able to login
Q. What is /ASU/upgrade?
- It use for Start ASU Toolbox in Upgrade Mode.
- It interacts with tables, function modules, methods, classes etc.
- It comes in Post processing phase of the UPGRADE
ASU Toolbox
- It is SAP tool in ST-PI
- It generates client-specific task list
- Transaction /n/ASU/UPGRADE
Q. Reset Administrator password of SUM.
- Stop SUM
- Rename two files .sdt_storage & .sdt_keystorage from <SUM Directory>\SUM\sdt\data OR
- Delete the file ".sdt_storage"
- Start SUM