Upgrade from R3 to mySAP ERP
What are the different types of Upgrades.
SAP had developed three different upgrade approaches to move from SAP R/3 to mySAP ERP2005.
Technical Upgrade- This is a fast upgrade without additional functionality but with minor user interface changes, to ensure business continuity.
Functional Upgrade - This is Built on the Technical Upgrade, The functional upgrade provides in addition the opportunity to implement new functionalities in areas like FI, HR, Logistics etc.,??? This upgrade type also represents an opportunity to maximize the use of SAP standard functionalities by replacing custom modifications and consolidate instance or systems.
Strategic Upgrade - This is driven by enterprise SOA to provide more flexibility to business process innovation. This type of upgrade approach represents a significant technology improvements step by leveraging SAP NetWeaver functionality to standardize, adapt, and enable new business processes and optimize scenarios.
Technical upgrade is a fast upgrade at constant functional perimeter, without additional functionality but with minor user interface changes, to ensure business continuity. This upgrade type includes a clean-up of the system without implementing additional functionality, as well as a technology upgrade with the opportunity to eliminate not used modifications and custom developments. If yo operate a system using SAP R/3 reviewing the technical aspect is a logical place to start a key step in any upgrade. This is a fast upgrade, but consume more time in testing.
Key Points on Technical upgrade.
Focus on pur Technology upgrade
No Change to used functionality
No Changes to system Modifications
Focus on risk mitigation and sustainability of existing system.
STEPS IN TECHNICAL UPGRADE
Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Run SPUMG Transaction for Unicode Conversion in non-unicode system, SPUM4 in 4.6c.
Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
Important Tables in Technical Upgrade:
SMODILOG: This tables has the record of all modifications to the objects. This includes customized objects and SNOTE corrections. These objects usually can be found in SE95 if the change is not obsolete.
TADIR: Very important system table. This table is the directory of all repository objects. All ABAP report, classes, function groups, etc are recorded in this table. Usually used during the upgrade to keep track of lost objects.
TRDIR: Not very often used. It has the information of all ABAP reports.
TSTC: It has the information of all transaction code, like the corresponding programs and screens.
ADIRACCESS: It has the access code information of all the objects in TADIR.
TFDIR: The information of all function modules
Technical upgrade is the fast upgrade without additional functionality but with minor user interface changes to ensure business continuity. In the past, all objects modified by a customer had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration using transaction SPAU and SPDD.
SPDD: This transaction allows you to adjust modifications to ABAP Dictionary objects during an upgrade.
Using this transaction we can adjust the Domains, Data Elements, Tables, Structures, Transparent tables, pooled and cluster tables including their technical settings, indexes of transparent tables. If you adjust data elements that have been changed with the Modification Assistant in an earlier release, the changes can be copied automatically.
Steps to run SPDD:
1. 1) Start transaction SE03 as user DDIC and choose Administration ® Set system change option
2. 2) Select Modifiable in the Global setting dialog box.
3. 3) Choose Continue.
4. 4) Choose Edit ® Select all.
5. 5) Save your changes.
6. Then log on as a normal user, since user DDIC may not perform any repairs.
SPAU: This transaction allows you to adjust programs, function modules, screens, interfaces, documentation and text elements after an upgrade.
After you adjusted or edited an object, you can use User/Status function to modify the status of the object. Before doing this, you can also add other developers or testers that are allowed to edit the object and create a short note.
Steps to run SPAU:
1) Start transaction SE03 as user DDIC and choose Tools ® Administration ® Set system change option.
2) Select Modifiable in the Global setting dialog box.
3) Choose Continue.
4) Choose Edit ® Select all.
5) Save your entries.
6) Then log on as a normal user, since user DDIC may not perform any repairs.
Other important topics in Technical Upgrade:
Upgrading the Development System: Perform the adjust in the development system using SPDD and SPAU transactions and assign to transport requests. The upgrade control program R3up exports the transport that you have marked in a later upgrade phase.
Upgrading the Production System: During this phase, the R3up upgrade control program checks whether there are any change requests registered for transport from the development system to the production system. If this is the case, R3up offers to import the transport automatically, instead of you carrying out adjustments with transactions SPDD/SPAU. If you choose this procedure, you still have the option of stopping SPDD/SPAU to check the changes accepted automatically before they are activated.
If you decide to import a transport automatically, a subsequent analysis checks whether there is an entry in the transport you specified for each modified object found in this SAP System. Only if this is the case is the transport marked as suitable.
If there are more modified objects in the production system than in the test system, they cannot be dealt with by the transport. This means that you have to adjust these objects.
If you had more modified objects in the test system than in the production system and these are also contained in the transport, you import these into the production system with the transport
Monday, March 17, 2008
SAP BASIS: Duet by SAP and Microsoft powered by HP
Accelerating time-to-benefits for Duet with plug-and-play ease
Duet software enables seamless access to SAP business processes and data via Microsoft Office. To gain the productivity and efficiency of Duet a tight integration with Microsoft Exchange is required.
An easy way to experience the benefits of Duet is the “Duet™ by SAP and Microsoft powered by HP”. HP created this solution, an integrated hardware and software package that you can plug into your existing infrastructure to begin evaluating and validating the benefits of Duet almost immediately—and with no imposition on your IT organization.
At the moment this solution is available in North America only.
Benefits of Duet™ by SAP and Microsoft powered by HP
· Out-of-the-box solution that can be implemented in a matter of days or hours
· Pre-tested and optimized to deliver reliable performance from day one
· Built-in wizards make set-up and deployment especially fast and easy
· Flexible solution to fit in your environment regardless of which version of SAP you’re using or whether you have a Microsoft Exchange test environment
· Proof-of-concept offer to evaluate Duet in your own facility before buying
· Transition to full-production Duet quickly and easily
Validate Duet results with a plug-in proof-of-concept
The Duet™ by SAP and Microsoft powered by HP proof-of-concept is a stand-alone offering that enables you to validate Duet against your particular business objectives. While this proof-of-concept minimizes any up-front investment on your part, it also streamlines implementation of the full solution because it includes all the hardware and software you’ll need for Duet, right out of the box. The Duet server is a single, high-performance HP server fully loaded to run Duet.
To further simplify and accelerate deployment, we offer an optional plug-in module that provides the latest SAP application software, including Enterprise SOA, SAP NetWeaver, and SAP NetWeaver Business Intelligence, foregoing the need for your IT organization to make immediate SAP upgrades. HP offers another optional plug-in module for Microsoft Exchange.
Duet software enables seamless access to SAP business processes and data via Microsoft Office. To gain the productivity and efficiency of Duet a tight integration with Microsoft Exchange is required.
An easy way to experience the benefits of Duet is the “Duet™ by SAP and Microsoft powered by HP”. HP created this solution, an integrated hardware and software package that you can plug into your existing infrastructure to begin evaluating and validating the benefits of Duet almost immediately—and with no imposition on your IT organization.
At the moment this solution is available in North America only.
Benefits of Duet™ by SAP and Microsoft powered by HP
· Out-of-the-box solution that can be implemented in a matter of days or hours
· Pre-tested and optimized to deliver reliable performance from day one
· Built-in wizards make set-up and deployment especially fast and easy
· Flexible solution to fit in your environment regardless of which version of SAP you’re using or whether you have a Microsoft Exchange test environment
· Proof-of-concept offer to evaluate Duet in your own facility before buying
· Transition to full-production Duet quickly and easily
Validate Duet results with a plug-in proof-of-concept
The Duet™ by SAP and Microsoft powered by HP proof-of-concept is a stand-alone offering that enables you to validate Duet against your particular business objectives. While this proof-of-concept minimizes any up-front investment on your part, it also streamlines implementation of the full solution because it includes all the hardware and software you’ll need for Duet, right out of the box. The Duet server is a single, high-performance HP server fully loaded to run Duet.
To further simplify and accelerate deployment, we offer an optional plug-in module that provides the latest SAP application software, including Enterprise SOA, SAP NetWeaver, and SAP NetWeaver Business Intelligence, foregoing the need for your IT organization to make immediate SAP upgrades. HP offers another optional plug-in module for Microsoft Exchange.
OSDB Migration: SAP on HP Integrity server case studies
Global energy leader pumps up ERP for rapid growth. Second-largest energy company in U.S. triples performance and capacity of SAP platform – while reducing administrative costs.
"Our biggest challenge is to keep up with the growth of our ERP data and systems. We needed to improve performance, but we also needed to consolidate servers so that we wouldn’t blow out the walls of our data center. The HP Integrity platform running HP-UX 11i allowed us to do both — without any large migrations or downtime to the business."
-- Paul Brody, Systems Analyst, Chevron Corporation
Chevron Corporation (http://www.chevron.com/) is the second-largest integrated energy company in the United States and one of the largest corporations in the world. Headquartered in San Ramon, California, Chevron employs more than 59,000 people and conducts business in 180 countries.
The rapidly growing energy leader, with global operations encompassing every sector of the oil and natural gas industry, generates vast amounts of data — both “upstream” in Chevron’s exploration and production operations and “downstream” in its refining, marketing, and transportation operations.
Integrating all information throughout the Chevron enterprise is a global ERP system based on SAP R/3, several multi-terabyte Oracle® databases, and a four-terabyte business warehouse. Backed by proactive support from HP Services, the resilient infrastructure maintains 99.999 percent availability and provides thousands of users with instant, 24x7 access to business-critical information.
ObjectiveKeep pace with rapid global expansion and mergers and acquisitions by implementing a more adaptable and cost-effective ERP infrastructure
ApproachConsolidate 50 SAP instances in multiple locations into one data center using HP Integrity servers and the HP-UX 11i v2 platform
IT improvements
· New servers triple performance and capacity of ERP infrastructure
· New footprint takes 2/3 less space
· Consistent 99.999% availability exceeds SLAs
Business benefits
· Faster applications and access to business intelligence improve productivity and decision-making
· More scalable yet streamlined platform supports business growth and eases integration of data from mergers and acquisitions
· Server consolidation cuts administrative, operating, and floor-space costs, shifting people and resources to more strategic initiatives
"Our biggest challenge is to keep up with the growth of our ERP data and systems. We needed to improve performance, but we also needed to consolidate servers so that we wouldn’t blow out the walls of our data center. The HP Integrity platform running HP-UX 11i allowed us to do both — without any large migrations or downtime to the business."
-- Paul Brody, Systems Analyst, Chevron Corporation
Chevron Corporation (http://www.chevron.com/) is the second-largest integrated energy company in the United States and one of the largest corporations in the world. Headquartered in San Ramon, California, Chevron employs more than 59,000 people and conducts business in 180 countries.
The rapidly growing energy leader, with global operations encompassing every sector of the oil and natural gas industry, generates vast amounts of data — both “upstream” in Chevron’s exploration and production operations and “downstream” in its refining, marketing, and transportation operations.
Integrating all information throughout the Chevron enterprise is a global ERP system based on SAP R/3, several multi-terabyte Oracle® databases, and a four-terabyte business warehouse. Backed by proactive support from HP Services, the resilient infrastructure maintains 99.999 percent availability and provides thousands of users with instant, 24x7 access to business-critical information.
ObjectiveKeep pace with rapid global expansion and mergers and acquisitions by implementing a more adaptable and cost-effective ERP infrastructure
ApproachConsolidate 50 SAP instances in multiple locations into one data center using HP Integrity servers and the HP-UX 11i v2 platform
IT improvements
· New servers triple performance and capacity of ERP infrastructure
· New footprint takes 2/3 less space
· Consistent 99.999% availability exceeds SLAs
Business benefits
· Faster applications and access to business intelligence improve productivity and decision-making
· More scalable yet streamlined platform supports business growth and eases integration of data from mergers and acquisitions
· Server consolidation cuts administrative, operating, and floor-space costs, shifting people and resources to more strategic initiatives
OSDB Migration: Migrate from HP-PARisc to HP Integrity
Homogeneous System Copy HP-UX PARisc to HP-UX PARisc and Installation Additional Application Server HP-UX IA64 11.23
No
Items
Prepare current Apps Server as next DB server
1
Full backup of SAP application server root file system/usr/sap//sapmnt/$INFORMIXDIR (kernel for database client)
2
Stop SAP application server
3
Shutdown Application server
4
Install and configure HBA Card to be able to read SAN
Installing SAP Application server in HP-UX Itanium
1
Collecting the required CD and downloaded software from SAP Service Market Place
2
Install the required patches in rx6600
3
Check requirement of HP-UX- RAM- Swap Space- Operating System and Patch- NFS- NLS- C++ Run Time Environment- Fonts
4
Installation Preparation- Adapting Unix Kernel Parameter- Setting up file system- Mounting directories (local and NFS)- Setting up Installation directory- Create useradm and informix and necessary group (sapsys, informix, informix_admin, super_archive) compare with current user id and group id
5
Dialog Instance Installation- Mounting directories- Install database client- Mounting kernel CD ROM- Running shell script INSTTOOL.SH- Setting Library Path Environment Variable- Running R3SETUP
6
Post Installation- Starting and stopping SAP system- Logging on to SAP system- Checking SAP System services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
HP-UX Itanium as SAP Application server
1
Activate logon balancing using SMLG (if needed)
2
Change Front End setting to use Logon Balancing (if needed)
3
Run application server in paralel with old application server
4
Shutdown Old Application server
5
Run application server using rx6600 only
Test Migration of current DB to SAP Application Server using disk in BCV
1
Lock user in Production system
2
Re-schedule all release background job in PRD
3
Make sure all updates are finished, make sure no pending or cancel record in PRD
4
Adapt operation mode make sure no switching of operation mode
5
Shutdown SAP and Database
6
Gathered and save all SAP related files configuration: /etc/passwd /etc/group /etc/fstab /etc/hosts /etc/services /etc/inittab /etc/rc.config.d/netconf /etc/exports /etc/resolv.conf /stand/system crontab and shutdown scripts /etc/lvmconf/*.conf $HOME/adm $HOME/sapr3 $HOME/informix
7
Full backup of SAP PRD
8
Copy all SAP + Informix (executable, parameter, etc) which based on filesystem using tar from current DB to the next DB (DON'T FORGET TO BACKUP THE ORIGINAL FILE / DIRECTORIES BY RENAME IT./usr/sap//sapmnt//informix/
9
Break disk mirorring
10
Move raw device sapdata using vgexport & vg import command from BCV disk
11
Change hostname and IP address (using IP address of previous DB server
12
- Starting and stopping SAP system- Logging on to SAP system- Checking SAP system services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
13
UAT Migration Testing
14
If Testing OK, setback to normal setting:- Shutdown SAP and Database- Set back hostname and IP address to normal setting- Rename the backup directories (#8) to the original name- Startsap
15
UAT Migration Testing after setback to normal condition
16
- Unlock user- Release background job in PRD- Adapt operation mode
16
Re-synchronize disk mirorring
Production Migration
1
Lock user in Production system
2
Re-schedule all release background job in PRD
3
Make sure all updates are finished, make sure no pending or cancel record in PRD
4
Adapt operation mode make sure no switching of operation mode
5
Shutdown SAP and Database
6
Gathered and save all SAP related files configuration: /etc/passwd /etc/group /etc/fstab /etc/hosts /etc/services /etc/inittab /etc/rc.config.d/netconf /etc/exports /etc/resolv.conf /stand/system crontab and shutdown scripts /etc/lvmconf/*.conf $HOME/adm $HOME/sapr3 $HOME/informix
7
Full backup of SAP PRD
8
Rename all previous copied file in testing migration that we tar before (DON'T FORGET TO BACKUP THE ORIGINAL FILE / DIRECTORIES BY RENAME IT./usr/sap//sapmnt//informix/
9
Break disk mirorring
10
Move raw device sapdata using vgexport & vg import command from main disk
11
Change hostname and IP address (using IP address of previous DB server
12
- Starting and stopping SAP system- Logging on to SAP system- Checking SAP system services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
13
UAT Migration Testing
14
- Unlock user- Release background job in PRD- Adapt operation mode
15
Re-synchronize disk mirorring
No
Items
Prepare current Apps Server as next DB server
1
Full backup of SAP application server root file system/usr/sap/
2
Stop SAP application server
3
Shutdown Application server
4
Install and configure HBA Card to be able to read SAN
Installing SAP Application server in HP-UX Itanium
1
Collecting the required CD and downloaded software from SAP Service Market Place
2
Install the required patches in rx6600
3
Check requirement of HP-UX- RAM- Swap Space- Operating System and Patch- NFS- NLS- C++ Run Time Environment- Fonts
4
Installation Preparation- Adapting Unix Kernel Parameter- Setting up file system- Mounting directories (local and NFS)- Setting up Installation directory- Create user
5
Dialog Instance Installation- Mounting directories- Install database client- Mounting kernel CD ROM- Running shell script INSTTOOL.SH- Setting Library Path Environment Variable- Running R3SETUP
6
Post Installation- Starting and stopping SAP system- Logging on to SAP system- Checking SAP System services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
HP-UX Itanium as SAP Application server
1
Activate logon balancing using SMLG (if needed)
2
Change Front End setting to use Logon Balancing (if needed)
3
Run application server in paralel with old application server
4
Shutdown Old Application server
5
Run application server using rx6600 only
Test Migration of current DB to SAP Application Server using disk in BCV
1
Lock user in Production system
2
Re-schedule all release background job in PRD
3
Make sure all updates are finished, make sure no pending or cancel record in PRD
4
Adapt operation mode make sure no switching of operation mode
5
Shutdown SAP and Database
6
Gathered and save all SAP related files configuration: /etc/passwd /etc/group /etc/fstab /etc/hosts /etc/services /etc/inittab /etc/rc.config.d/netconf /etc/exports /etc/resolv.conf /stand/system crontab and shutdown scripts /etc/lvmconf/*.conf $HOME/
7
Full backup of SAP PRD
8
Copy all SAP + Informix (executable, parameter, etc) which based on filesystem using tar from current DB to the next DB (DON'T FORGET TO BACKUP THE ORIGINAL FILE / DIRECTORIES BY RENAME IT./usr/sap/
9
Break disk mirorring
10
Move raw device sapdata using vgexport & vg import command from BCV disk
11
Change hostname and IP address (using IP address of previous DB server
12
- Starting and stopping SAP system- Logging on to SAP system- Checking SAP system services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
13
UAT Migration Testing
14
If Testing OK, setback to normal setting:- Shutdown SAP and Database- Set back hostname and IP address to normal setting- Rename the backup directories (#8) to the original name- Startsap
15
UAT Migration Testing after setback to normal condition
16
- Unlock user- Release background job in PRD- Adapt operation mode
16
Re-synchronize disk mirorring
Production Migration
1
Lock user in Production system
2
Re-schedule all release background job in PRD
3
Make sure all updates are finished, make sure no pending or cancel record in PRD
4
Adapt operation mode make sure no switching of operation mode
5
Shutdown SAP and Database
6
Gathered and save all SAP related files configuration: /etc/passwd /etc/group /etc/fstab /etc/hosts /etc/services /etc/inittab /etc/rc.config.d/netconf /etc/exports /etc/resolv.conf /stand/system crontab and shutdown scripts /etc/lvmconf/*.conf $HOME/
7
Full backup of SAP PRD
8
Rename all previous copied file in testing migration that we tar before (DON'T FORGET TO BACKUP THE ORIGINAL FILE / DIRECTORIES BY RENAME IT./usr/sap/
9
Break disk mirorring
10
Move raw device sapdata using vgexport & vg import command from main disk
11
Change hostname and IP address (using IP address of previous DB server
12
- Starting and stopping SAP system- Logging on to SAP system- Checking SAP system services (SM50, SICK)- Installing and using SAP License- Adjust memory (recommended by using RZ10 and adding work process)- File and directory adjustment
13
UAT Migration Testing
14
- Unlock user- Release background job in PRD- Adapt operation mode
15
Re-synchronize disk mirorring
Tuesday, March 4, 2008
Welcome to Boler Consulting Blog
Dear all,
Please be informed that this Boler Consulting Blog is intended to be a centralized of SAP knowledge sharing among SAP community and other who interested on.
Boler is very happy if any information on this website will be benefits for you and Boler is very appreciated for your input as well.
Thank you very much.
Cheers.
Boler Consulting Pte Ltd
Subscribe to:
Posts (Atom)