SAP BASIS & Security

Friday, August 26, 2016

SAP Press eBooks Collection

http://turbobit.net/0gxqk3fh1b86.html -> SAP Press - Mastering HR Management with SAP.djvu
http://turbobit.net/15zoz96h1x8z.html -> SAP Press - SAP CRM Middleware Optimization Guide.pdf
http://turbobit.net/1ctosj8axfno.html -> SAP Press - SAP Netweaver BW Administration and Monitoring.pdf
http://turbobit.net/1hk6u8tvf3dl.html -> SAP Press - The Official ABAP Reference (3rd Edition), 2011.pdf
http://turbobit.net/241pbbhkjczj.html -> SAP Press - Cobit and the Sarbanes-Oxley Act.djvu
http://turbobit.net/2uv71tltnd07.html -> SAP Press - SAP Performance Optimization Guide.pdf
http://turbobit.net/410se086axsj.html -> SAP Press - Product Cost Controlling with SAP.pdf
http://turbobit.net/4hwxkpdwzjuf.html -> SAP Press - Advanced BSP Programming.pdf
http://turbobit.net/511otn0yhgk3.html -> SAP Press - ABAP Objects - ABAP Programming in SAP Netweaver.djvu
http://turbobit.net/58repk7f32kg.html -> SAP Press - SAP Solution Manager.pdf
http://turbobit.net/5amjpoo6951w.html -> SAP Press - ABAP™ Performance Tuning.pdf
http://turbobit.net/5bmwhetoy8yn.html -> SAP Press - SAP BusinessObjects Planning & Consolidation.pdf
http://turbobit.net/6thugc88ihp5.html -> SAP Press - SAP BusinessObjects BI Security.pdf
http://turbobit.net/7mq3xx36v18c.html -> SAP Press - 100 Things You Should Know About Reporting with SAP® Crystal Reports®.pdf
http://turbobit.net/7rwhtc95yvw9.html -> SAP Press - Implementing and Configuring SAP MII .djvu
http://turbobit.net/89o90jk1j0px.html -> SAP Press - Maximize Your Plant Maintenance with SAP®.pdf
http://turbobit.net/8bghyfpskceg.html -> SAP Press - ABAP Development for SAP Business Workflow, 2011.pdf
http://turbobit.net/8yskjasti3ce.html -> SAP Press - Enterprise SOA Roadmap.djvu
http://turbobit.net/988tfe6jwevl.html -> SAP Press - HR Management with HCM.pdf
http://turbobit.net/agnszvcyt19d.html -> SAP Press - SAP ABAP™ Development for Materials Management in SAP - User Exits and BADIs.pdf
http://turbobit.net/aslmqc7tqkks.html -> SAP Press - Integration of Material Management with Financial Accounting in SAP.pdf
http://turbobit.net/az2mbd2q6k3r.html -> SAP Press - Financial Reporting with SAP.djvu
http://turbobit.net/c316fgchi4p7.html -> SAP Press - Capable to Match with SAP APO.pdf
http://turbobit.net/cm1qpcl4a1el.html -> SAP Press - Capable to Match with SAP APO.pdf
http://turbobit.net/e9es1d5sdkdt.html -> SAP Press - SAP Enterprise Asset Management.djvu
http://turbobit.net/f0wnxzryg9k9.html -> SAP Press - ABAP Data Dictionary.pdf
http://turbobit.net/f82mjleeogc3.html -> SAP Press - Business Process Management The SAP Roadmap.djvu
http://turbobit.net/fkovji3t1oqo.html -> SAP Press - SAP Governance, Risk and Compliance.djvu
http://turbobit.net/flvy9qr755dc.html -> SAP Press - Discover SAP CRM.djvu
http://turbobit.net/givn4ekrr6sl.html -> SAP Press - ABAP Development for SAP Business Workflow, 2011.pdf
http://turbobit.net/gkwpkdn8a13z.html -> SAP Press - mySAP CRM Official Guide Book.djvu
http://turbobit.net/gvamrwomf2w8.html -> SAP Press - Using Crystal Reports® with SAP®.pdf
http://turbobit.net/i4qsd4i1qajk.html -> SAP Press - Authorizations in SAP HR.pdf
http://turbobit.net/idaufuzfaw1z.html -> SAP Press - Advanced BSP Programming.pdf
http://turbobit.net/ifkswmp877qj.html -> SAP Press - Customizing Material Management processess in SAP ERP Operations.pdf
http://turbobit.net/ilqs6fna1h1r.html -> SAP Press - ABAP Basics.pdf
http://turbobit.net/io4s0kpao6x3.html -> SAP Press - 100 Things You Should Know About Reporting with SAP® Crystal Reports®.pdf
http://turbobit.net/itr20y3snnnl.html -> SAP Press - Effective Pricing with SAP ERP.pdf
http://turbobit.net/jzd5rnilml1j.html -> SAP Press - SAP HANA-An Introduction.pdf
http://turbobit.net/k4feipwwbk9a.html -> SAP Press - Consultants Guide to SAP SRM.djvu
http://turbobit.net/k6rhh0ye9uw2.html -> SAP Press - Managing SAP® ERP 6.0 Upgrade Projects.PDF
http://turbobit.net/kn7nxo12qvyb.html -> SAP Press - 100 Things You Should Know about Sales and Distribution in SAP ERP.pdf
http://turbobit.net/ko3yz7hs9n4k.html -> SAP Press - Getting Started with Web Dynpro ABAP.pdf
http://turbobit.net/ks1fd8yoifiv.html -> SAP Press - SAP MM - Functionality and Technical Configuration(Scanned).pdf
http://turbobit.net/la6gcq9xlkw0.html -> SAP Press - 100 Things You Should Know about Authorizations in SAP.pdf
http://turbobit.net/lprehq77z61o.html -> SAP Press - SAP Security and Risk Management.pdf
http://turbobit.net/lqyeaek2zpad.html -> SAP Press - Transitioning to IFRS in SAP ERP Financials.pdf
http://turbobit.net/lx1j0ghhcvy9.html -> SAP Press - Next Generation ABAP Development.pdf
http://turbobit.net/lxt2ooj3ptip.html -> SAP Press - Sales and Inventory Planning with SAP APO.pdf
http://turbobit.net/mvrl482bmsuz.html -> SAP Press - Integrating SAP BusinessObjects BI Platform 4_x with SAP NetWeaver.pdf
http://turbobit.net/n7fuu5o3wcrt.html -> SAP Press - Discover SAP CRM.djvu
http://turbobit.net/ny1irs2o3cyu.html -> SAP Press - Capable to Match with SAP APO.pdf
http://turbobit.net/o42ptmrtzrty.html -> SAP Press - Actual Costing with the SAP® Material Ledger.pdf
http://turbobit.net/o5pbp21rz58z.html -> SAP press - Maximizing Web dynpro for Java.djvu
http://turbobit.net/pdvs2m54idti.html -> SAP Press - SAP Netweaver BW.pdf
http://turbobit.net/pi4cmbimt0my.html -> SAP Press - Reporting for SAP - Asset Accounting.pdf
http://turbobit.net/piroutyk1m4m.html -> SAP Press - Cash Accounting and Cash Flow Planning with SAP Liquidity Planner.pdf
http://turbobit.net/pubyad5kva1i.html -> SAP Press - Maximize Your Plant Maintenance with SAP®.pdf
http://turbobit.net/pyv560qhspmj.html -> SAP Press - Project Management with SAP Project System.pdf
http://turbobit.net/q44tylkf0u4i.html -> SAP Press - Managing Organizational Change During SAP Implementation.pdf
http://turbobit.net/qawtt4qxvk1c.html -> SAP Press - SAP Enterprise Portal.djvu
http://turbobit.net/qmu4xl4t5qg4.html -> SAP Press - Customizing Material Management processess in SAP ERP Operations.pdf
http://turbobit.net/qn22t0gwpixf.html -> SAP Press - ABAP Cookbook.djvu
http://turbobit.net/qoigr9kqew09.html -> SAP Press - ABAP Development for SAP NetWeaver BI - User Exits and BAdls.pdf
http://turbobit.net/rsnxchqsx1fr.html -> SAP Press - Cross Enterprise Integration with SAP GRC Access Control.djvu
http://turbobit.net/rti8jqnx9a3l.html -> SAP Press - Enhancing the Quality of ABAP Development.djvu
http://turbobit.net/s8etya09tb1k.html -> SAP Press - SAP Administration - Practical Guiden.pdf
http://turbobit.net/spg96bp51lkd.html -> SAP Press - 100 Things You Should Know About Financial Accounting with SAP.pdf
http://turbobit.net/t1jzzyw64v55.html -> SAP Press - Capable to Match with SAP APO.pdf
http://turbobit.net/uiwcdh4vwazf.html -> SAP Press - Testing SAP Solutions.djvu
http://turbobit.net/vbfe3lrp23uw.html -> SAP Press - Reporting and ytics with SAP® BusinessObjects.pdf
http://turbobit.net/wfbxstnjkkhp.html -> SAP Press - Material Management Process in SAP ERP Operations.pdf
http://turbobit.net/xo5rpk2mkdj8.html -> SAP Press - 100 Things You Should Know about ABAP Workbench.pdf
http://turbobit.net/yb0yj3yapolg.html -> SAP Press - Actual Costing with the SAP® Material Ledger.pdf
http://turbobit.net/ye1ku84n3gzm.html -> SAP Press - 100 Things You Should Know About Reporting with SAP® Crystal Reports®.pdf
http://turbobit.net/yfzsn727euc9.html -> SAP Press - Practical Workflow for SAP.pdf
http://turbobit.net/yqz6buctbg16.html -> SAP Press - Maxmize Your Warehouse Operations With SAP ERP.pdf
http://turbobit.net/yzfgcywbhyd5.html -> SAP Press - SAP Interface Programming.djvu
http://turbobit.net/za4qwyn9i6f8.html -> SAP Press - Warehouse Management - Functionality and Technical Configuration.pdf
http://turbobit.net/zul821h5igf5.html -> SAP Press - SAP CRM Web Client Customizing and Development.pdf

Saturday, July 2, 2016

New Functionalities of GRC 10.1

Enhancements in GRC 10.1

Purpose

The Purpose of this document is to explain what all new features/functionality has been added in GRC 10.1. It is just to give you a brief about the enhancements done.

Overview

As we all know, Access Control is the best way to govern the system access in our environment, so to make it more easy, enhanced and single stop for several activities, we have Incorporated many features for its better interactivity and more Intuitive design.

SAP GRC Access Control 10.1 has been enhanced and advanced. Now, it incorporates SAP NetWeaver 7.40 that provides the option to run on the SAP HANA database.

The New enhancements are:

SAP AC on HANA

Steps to Create HANA connector in GRC box are:
1.T-code DBCO, create the HANA connector.

2. Using Tcode SM59, create logical connector. Note: Logical connector can be created from Tcode SPRO (SAP Customizing Implementation Guide-->Governance, Risk and Compliance-->Common Component Settings-->Integration Framework-->Create Connectors).

3. To Integrate the HANA connector to GRC, execute the Tcode SPRO (SAP Customizing Implementation Guide-->Governance, Risk and Compliance-->Common Component Settings-->Integration Framework-->Maintain Connectors and Connection Types. Note: The Logical Port need to be the connector name provided in the tcode DBCO (refer step 1) while creating the HANA database connection.

4.Assign the required integration scenario to the HANA connector using the tcode SPRO (SAP Customizing Implementation Guide-->Governance, Risk and Compliance-->Common Component Settings –> Integration Framework–> Maintain Connection Settings.
Corbu Theme - Enhanced User Interface

Side Panels for My Process

These Side panels can be configured from Governance, Risk and Compliance -> General Settings -> UI Settings -> Configure Side panel for My Process.
Simplified Access Request

You can see this in NWBC -> Access Management -> Create Request - Simplified

Remediation View

It is targeted towards business user needs in terms of verbiage, more user-friendly and intuitive layout, available help information, default information displayed, layout of buttons and functions in order to enable them make intelligent decisions about risk resolution. During the Risk Analysis it is possible to remove or mitigate the user access.

Role Search Personalization
Now, you can customize your searching criteria based on the Attributes configured for Role Search in Access Requests, by following the path:

SPRO -> IMG -> GRC --> Access Control -> User Provisioning -> Configure Attributes for Role Search Criteria in Access Requests
Custom Group for SU01 attributes in Risk Analysis

In GRC 10.0, there was a limitation that risk analysis could not be performed in some SU01 Attributes, like Function, Department, Parameters etc. But now, with GRC 10.1 new feauture added of Custom Groups, we can perform the risk analysis on SU01 Attributes as well. Once a custom Group is created, risk analysis can be performed on the user and to the Attribute he belongs to. GRC 10.1 has been integrated with some key attributes of SU01 which we can use to create our custom group and can perform risk analysis on it.

Steps Involved:

SU01 Attributes options we have

Decentralized Firefighting (SAP Access Control 10.0 and 10.1)

GRC 10.1 has introduced a new feature in Emergency Access management (EAM), where you can maintain Firefighter ID role name per system/connector. Instead of maintaining the SPM role in configuration parameter you can utilize the new option to map FF ID role per connector.

Go To SPRO-->IMG-->GRC-->Access Control--> Emergency Access Management->Maintain Firefighter ID role name per connector.

Here you can select the connector name and associate role to it.

Business Role Improvement
The User to Business Role and Technical Roles relation can be checked in the GRC Box table GRACUSERROLE. Business Role would be stored in table GRACROLE. You can use the report "GRAC_CHECK_BROLE_ASSIGNMENT" (via SE38) in GRC Box (SP17 for 10.0 or higher and check for this in latest Sps for 10.1) to see any inconsistencies in the User to Business Role assignment. See note - 1981001 - Recommendations : Using business role provisioning in access request.

Sunday, July 5, 2015

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:

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

Update Saint Tool:

Download required version
Uncar and keep in eps/in
Go to SPAM
Go to Support Package
Click import saint/spam update
This step will take some time and then click on green ok button
Some time it will throw error ….no need to worry just go to spam steps 5 again and the version will change
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

Login from DDIC and enter Tcode SPAM, Click on Package level to know the existing level of the support packs and the add-ons.
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.
If the size is > 10mb, copy the support packages to /trans directory and uncar the support packages using the below command
cmd>cd usr\sap\trans
sapcar –xvf .car
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.
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.
Go to support package click import queue (or) Click on truck icon.
Click on continue after importing in to the Queue.
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

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

ABAP Stack SP Upgrade:

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

JAVA Stack SP Upgrade:

Download required sp's from marketplace.
Unpack the files or move them to the "saptranshost" depending of your release.
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.

EHP UPGRADE

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

6. Summary:

PRE STEPS:

1. Install maintenance license
2. Prepare stack.xml and download software.
3. Install SUM as adm
STEPS:
1. cd /sapcd/XXX702SPS08
2. SAPCAR –xvf //.SAR -R /usr/sap/
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 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://: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.

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”.