topic Re: upgradation in Application Development and Automation Discussions

upgradation

Former Member — Tue, 24 Jul 2007 10:43:55 GMT

Hi,

can u explain this?

my client previous version is 4.7ee,he wants to move to 6.0ecc version can u pls give the important step procedure for the upgradation.Pls

Re: upgradation

Former Member — Tue, 24 Jul 2007 10:48:15 GMT

Welcome to SDN forum

While doing Upgrade You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.

Some function modules may become obsolete, and some screens will change

and some new fields will be added in the new versions etc.

Also take care of SPAU and SPDD tcodes.

You should be able to know about Unicode concept in sap.

check this

http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22

also chk these 2 notes in service.sap.com

Technical Upgrade is only a version upgrade without any functionality changes.

The objects that are needed to be upgraded are:

Includes

Function Groups / Function Modules

Programs / Reports

OSS Notes

SAP Repository Objects

SAP Data Dictionary Objects

Domains, Data Elements

Tables, Structures and Views

Module Pools, Sub Routine pools

BDC Programs

Print Programs

SAP Scripts, Screens

User Exits

You can refer to the below links for more information on technical upgrade:

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&

https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII

http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca

<b>Reward points for useful Answers</b>

Regards

Anji

Re: upgradation

Former Member — Tue, 24 Jul 2007 10:48:25 GMT

Hi,

Basically when ever you do an upgrade you need to perform two Transactions after the upgrade.

SPDD and SPAU.

SPDD: is the transaction that you need to perform to adjust the Dictionary changes (Like changes to Datalements, domians, Strucutres , tables etc).

Then

SPAU: This is the transaction for Modification Adjustment where in if your customer has done any modifications to the code all that would have been overwritten in the upgare this transaction gives you options to retrive the customer changes.

Check out these transactions for more ideas.

Hi UCCHECK is to check if the program is Unicode complaint. Its not for checking Obsolete FM's.

Due to an upgradation from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.

So a developer should be aware of the following:

•Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.

•You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.

Check the below link to find more details on usage of SPAU & SPDD transactions

http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm

•Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.

For example:

--> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7

-->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.

•In case of tables, we need to specify the Enhancement category.

•Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.

•In case of BDC programs, some field names will be changed. So they have to be named appropriately.

Please check with the below link for more details:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca

http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htmhttps://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&

https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII

<b>Reward points if useful</b>

Regards

Ashu

Re: upgradation

Former Member — Tue, 24 Jul 2007 10:48:43 GMT

Hi Priya,

Refer the foll.threads,

hope this helps

Re: upgradation

Former Member — Tue, 24 Jul 2007 10:52:28 GMT

Hi,

you can certainly upgrade from R/3 4.7 to ECC 6.0. Keeping in mind that ECC 6.0 is part of mySAP ERP 2005, your best place to start is the mySAP ERP 2005 Upgrade Master Guide. This document will list all the relevant notes you should read prior to starting your upgrade, as well as a host of other relevant information.

To obtain this document, go to the SAP Service Marketplace at http://service.sap.com/instguides, then navigate to mySAP Business Suite Applications -> mySAP ERP -> mySAP ERP 2005 -> Upgrade

check this link

Regards

Re: upgradation

Former Member — Tue, 24 Jul 2007 11:10:02 GMT

If you have modified SAP objects from the add-on that you want to install, you must adjust these objects when you import them in order to ensure that your modifications are not overwritten by SAP objects. Transaction SPDD adjusts Dictionary objects, whereas transaction SPAU adjusts Repository objects.

If you have already performed the modification adjustment in a system (in a development system for example), you do not need to perform it manually in the follow-on systems (quality assurance and production systems). You can include the transport requests that you created for the modification adjustment (modification adjustment transports) in the installation queue. The modification adjustment then takes place automatically when the queue is imported. For more information, see Installing and Upgrading Add-Ons.

Prerequisites

Either you have not included any adjustment transports, or the ones you have included do not cover all the objects that need adjusting.

The Add-On Installation Tool asked you to adjust your modifications.

Procedure

Modification Adjustment for Dictionary Objects - Transaction SPDD

Complete all modification adjustments before you continuing with the import. If you do not do this, modifications to dictionary objects will be lost. This can lead to data loss.

To do so, perform all the steps as described below:

Modification Adjustment for Repository Objects - Transaction SPAU

You can:

· Adjust all modifications before you continue with the import.

This is recommended if you only need to adjust a small number of objects.

To do so, perform all the steps as described below:

· You perform the modification adjustment and the remaining phases in parallel.

This is recommended if you need to adjust a lot of objects.

This procedure is particularly suitable when using the Import Mode: Downtime-minimized. In the subsequent phases, the Add-On Installation Tool deletes from the system all versions of program code and program texts that have become obsolete. Since this can be a lengthy process, you can save time by simultaneously adjusting your modifications.

If you want to perform the import in parallel, choose Continue on the screen that prompts you to perform a modification adjustment to continue with the import. Then carry out steps 1 through 3 as described below.

To perform the modification adjustment, proceed as follows:

...

1. To enable your developers to adjust modifications, go to the Transport Organizer and create one or more requests that include tasks for the developers.

We recommend that you create one transport request for adjusting dictionary objects and another for adjusting repository objects.

If you want to include the transport requests in the import queue into the follow-on systems, create them as transportable workbench requests. If you do not do this, they cannot be exported from the system and cannot be used in follow-on systems.

2. If you want to include the created requests in the installation queue in the follow-on systems for an automatic modification adjustment, you must mark them as adjustment transports.

a. To do this, call transaction SPDD or SPAU and choose Utilities -> Select for transport.

This function is also used to select modification adjustment transports for the system upgrade. If you have already performed a system upgrade, the system might prompt you to decide whether you want to select the adjustment transport for use in the upgrade or for use in importing an add-on installation queue (OCS). Choose OCS.

b. On the selection screen, choose the request you created previously and confirm your selection.

The transport request is now selected for use as a modification adjustment transport.

You select a Workbench request as a modification adjustment transport by assigning it to the predefined CTS project SAP_ADJUST. This means that a Workbench request selected as a modification adjustment transport cannot be assigned to a customer-defined CTS project. An assignment such as this would always be overwritten by the SAP_ADJUST project when the selection is made.

c. If you have created several transport requests, repeat the process for all of them.

3. Ask the developers to adjust the modifications for their objects.

If you have not yet confirmed the installation, the developers can choose Extras -> Adjust Modifications in the Add-In Installation Tool initial screen to call either transaction SPDD or transaction SPAU, depending on the context.

After the adjustment is completed, the developers must release their tasks and inform you. Modifications can be adjusted in any client.

You only need to perform the following steps if you did not continue the installation after being prompted to perform a modification adjustment.

4. Call the Add-On Installation Tool.

5. View the status of the installation queue. To do so, choose Goto ® Status ® Installation Queue.

A screen appears that prompts you to perform a modification adjustment.

6. Choose Confirm Adjustment and confirm the prompt.

7. To continue importing the installation queue, choose Continue.

Result

The Add-On Installation Tool continues with the process (transaction SPDD) or completes it (transaction SPAU), and displays the status.

If you have created a modification adjustment transport, you can release and export it in the Transport Organizer after importing the installation queue.

Since the modification adjustment transport is a normal Workbench request, it is placed automatically in the import queue of the follow-on system during the export, where it can be imported as normal. However, performing this import only makes sense if the corresponding add-ons and Support Packages have been imported into the follow-on system. For this reason, make sure the import is not performed too early. To do this, use the mechanisms and functions contained in the Transport Management Systems (such as project management, QA mechanisms or deleting the request from the import queue).

During an upgrade or the import of an Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.

In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner, 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.

In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers support during the upgrade, which means that a semi-automatic adjustment is made. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.

Objects modified according to the old system used prior to the advent of the Modification Assistant must be manually maintained after an upgrade has been run.

Use transactions SPDD and SPAU during an upgrade to select these objects and modify them manually.

Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.

For more information, refer to:

Adjusting ABAP Dictionary Objects

Prerequisites

Procedure

Preparing to Run Transaction SPDD

Transaction SPDD

Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.

Additional information about the modification adjustment procedure using transaction SPAU can be found in Adjusting Repository Objects.