Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
patil477pavan
Explorer
Introduction: 

  • SAP Technical Upgrade is a periodic project that helps us to upgrade the SAP system to the latest released version.

  • In other words, SAP Upgrade means upgrading the software with a latest version, which has more advantages (i.e. Bugs fixed compared to previous version).

  • E.g. : Just think, this is out of topic but easy to describe the above concept easily. Android Mobile with version 9.0 upgraded to 10.0 will have same features but interfaces change at a greater look.


Upgrade Issues:

  • After upgradation from one version to another latest version, some functionalities might not work properly just like their might be some function module which are not necessary or not valid in an upgraded system , might be some transactions which are not in usage and the syntax of particular command is changed & also their might be some issues related to data model changes and many more.

  • So, ABAP correction is needed to make these functionalities work as in Older version or system.

  • During an upgrade, existing SAP standard objects are overwritten. Customer can retain the modified objects as in older system or adapt to new changes through transaction SPDD, SPAU and SPAU_ENH.

  • Hence , it is very much necessary to carry out SPDD , SPAU and SPAU_ENH activities.


Types of Upgrades:

Upgrade projects have been divided as below :

  1. Release Upgrade

  2. Enhancement Packages – EHP Upgrade

  3. Support pack updates – SP upgrade

  4. Database Migration – From different database to HDB

  5. SAP S/4HANA – Conversion


Flowchart:

System Preparation -> SPDD Phase -> Upgrade of the system -> SPAU/SPAU_ENH Phase

Object Modes & its Meaning :

All the objects present under transaction SPDD,SPAU & SPAU_ENH will have certain traffic lights or object modes associated to it.



    • Grey  Light              –      Obsolete

    • Yellow Light            –      Semi Automatic Adjustment

    • Green Light            –       Automatic Adjustment

    • Red Light                –      Manual Adjustment

    • Green Tick Mark     –     Completely Adjusted




Transaction SPDD:

When upgrading the SAP system , one of the initial steps that needs to be completed is SPDD. This will allow you to adjust modifications to ABAP Dictionary Objects during an upgrade.

There are 4 categories in SPDD : a) SAP Notes b) With Assistant c) Without Assistant d) Deletions

Note : SPDD will be carried out in shadow instance.

To know more about shadow system , please refer the below blog ;

https://blogs.sap.com/2014/04/02/sum-introduction-to-shadow-system/

Transaction SPAU:

This process starts after completion of SPDD phase and is used to adjust repository objects like programs, screens, functions, classes, etc.

There are 5 categories in SPAU : a) SAP Notes b) With Assistant c) Without Assistant d) Deletions e) Translations

Note : Unlike SPDD , this can be carried out in the normal client .

Transaction SPAU_ENH:

This is used to adjust custom enhancements.

Key Points:

The keys aspects to take the action depends on two scenarios .

  • RESET : If the customer modifications does not exist in the object and the changes are same w.r.t latest customer TR and the latest upgrade TR , then we can do reset to original.

  • ADJUST : If the object contains any customer changes & the changes are not same w.r.t latest customer TR and the latest upgrade TR , then we need to perform adjust modification.


Ground Rules to be Followed : 

In any game , we will be having the set of rules to make sure the game is interesting & also to avoid any confusion in later part of the game , similarly in any upgrade project - we do have a set of rules to be followed w.r.t the categories of the object , that needs to be completed first for smooth process. So, SAP Notes and With Assistant has to be carried out first , at least SAP Notes has to be completed first - so that their is no dependency w.r.t SAP Notes and later even if we shuffle with other categories we don't face any issues.

Conclusion:

  • Since , SAP upgrade project(Technical or Functional) is very crucial and its important to make sure all the tasks are completed with no mistakes.

  • As the world is moving from SAP (ECC) ERP to SAP S/4HANA we would get many migration projects and this is the initial step to be carried out in any migration projects.

7 Comments
alok_kumar48
Explorer
Simple and Precise
patil477pavan
Explorer
0 Kudos
Thank You alok.kumar48
Billelinfo27
Participant
Hi Pavan

Thanks a lot for the explanations,

If I may, I would like to ask you a question regarding the SPAU/SPDD adjustements that need to be done during a migration projet of a 4 systems landscape "DEV, QAS, PREPROD, PROD"

if we noticed after the upgrade of the DEV, QAS  and a SandBox "created from PROD copy" systems that the spau/spdd results are not the same between the DEV, QAS and the SandBox, do we will need to align the 2 systems from PROD also before going through with the upgrade or maybe there is another solution to overcame the issue?

Best Regards

Billel Derbal
patil477pavan
Explorer

Hi Billel Derbal ,

In this scenario , suppose if we face any mismatch in any of the objects fixed in different systems , we need to revert the changes using Access Key , there is no other workaround.

Hope this answers your question.

Thank You.

Best Regards,

Pavan

Please dont stop the good work . it would not be greed to expect  more posts this way .

 

write some articles related to Migration and green field implementation as well as brown field too..

 

Regards,

Sarvana Kumar V S
former_member751826
Discoverer
0 Kudos
Hello Pavan,

 

Can we do SPAU_ENH before SPAU ?

Please advise.

 

Thanks
patil477pavan
Explorer

Hi Swati, 

In SAP system upgrades, the recommended sequence is to perform the SPAU activity before the SPAU_ENH activity.

The SPAU activity (Support Package Adjustment) is typically executed after applying a Support Package or Support Package Stack to your SAP system. During SPAU, you review and adjust the modifications made to SAP standard objects that have been affected by the Support Package. This process ensures that any customizations or enhancements you made to the standard objects remain compatible with the updated version.

Once you have completed the SPAU activity and ensured the compatibility of your customizations, you can proceed with the SPAU_ENH activity (Support Package Adjustment - Enhancements). The SPAU_ENH activity specifically deals with adjusting enhancements implemented using Enhancement Framework tools such as Enhancement Spots, Enhancement Implementations, or Business Add-Ins (BAdIs). It allows you to adapt your enhancements to the changes introduced in the upgraded SAP system.

Performing SPAU before SPAU_ENH ensures that you address any modifications to SAP standard objects first and then focus on adjusting your enhancements accordingly. This sequence helps maintain the integrity and compatibility of both the standard objects and the enhancements in your upgraded SAP system.

Hope it answers your question.

Best Regards,

Pavan Patil

Labels in this area