We will discuss ideas and some of the difficulties that we face during SAP Upgrade in this blog.SAP upgrade needs a comprehensive and thorough system landscape assessment. The first stage is to understand what results are achieved from the upgrade and to be extracted from it. It’s not just a technical job.
All SAP regions (Functional, ABAP, BASIS) play a key part in planning the project for the SAP upgrade. Although the IT department drives the technical upgrade, it can not operate without enterprise side assistance and cooperation. Tasks concerning growth until testing are usually undertaken by the technical team in the development scheme. But the quality system testing is conducted by company customers to guarantee that all critical company functionalities function as anticipated and that no disruption has been created by the upgrade. I’ve tried to address some scenarios here in this blog that may be useful during the SAP Upgrade project.
Many objects such as data dictionary items, repository items, including feature modules, enhancements, reports, BDC, SAP scripts, types, etc. are impacted during SAP upgrade from a technical view. A technical upgrade is a quick upgrade, but testing requires a lot of time. During an upgrade, there are really a few variables to consider:
Unicode programming is followed by SAP ECC 6.0. Unicode mistakes are therefore usually confronted while upgrading to this large version SAP ECC 6.0 from small version. Short dumps are found while running certain programs. This might be due to Unicode mistakes in this fresh edition and the use of outdated feature modules to replace them with other functional modules. So we need to make adjustments here. The transaction is SPUMG for the conversion of Unicode.
For instance: in ECC6.0, the feature module is outdated when using WS UPLOAD and UPLOAD alert signal. Don’t use this. GUI UPLOAD substituted these feature modules.
The SPDD and SPAU operations are key component of the technical upgrade. SPDD– This operation is for data dictionary items to be adjusted and corrected. In case that any normal tables have been amended, this operation will list them. Both versions are listed and their attributes are analyzed in order to adjust them. One should be very cautious to make adjustments as the effect can be even more hazardous than altering a program. As in the upgrade phase, a domain’s duration says content has altered. Although SAP may take care of the standard programs, it can not be denied that this domain has been referenced to some custom programs and what impact the changes will have on custom programs and tables.
SPAU– This operation involves programs, features, courses, etc. for repository objects. Again, the modifications are discovered after the upgrade by comparing the two versions.
The interface is another significant factor to consider. The interface assessment should be performed before beginning an upgrade. Those interfaces that have problems with SAP ECC 6.0 compatibility should be recorded. Since this new model is case-sensitive, some issues are probable to arise during the transfer and attachment of files. The legacy system can also confront problems in terms of compatibility.
In the case of tables, the category of enhancement needs to be given. After the SAP upgrade, the customization includes may be lost. It is necessary to restore even selection texts, variations, report records of many programs.BDC’s field names can also be altered. It can be complicated, so it can be very helpful to maintain these entities like versions and also save a ton of time.
Some of the essential helpful tables in the SAP project upgrade are:
TADIR: This panel is the folder of all items in the database used to monitor items missed. TRDIR: Contains all ABAP reports data. ADIRACCESS: All items in TADIR have access code data.
Some of major challenges are:
Critical problems leading to disaster – If not taken care of, some of the problems may result in project failure. One is SAP add-ons that, if applied in the system, allow all the relevant compulsory documents to be enforced before the upgrade project starts. Otherwise, it may threaten the complete upgrade project and there is no other option to go home than resetting the upgrade process.
Testing Issues– Interface testing is a very important component of the upgrade plan. If the number of interfaces is very high, it is virtually difficult to verify each interface. In this situation, they are categorized based on company criticality. In this, it is necessary to finalize first the number of interfaces to be evaluated. Then suitable funds are recognized for cooperation. There should be certainty here to fully test the chosen interfaces. Testing the remaining of the interfaces can be performed on the basis of the time available to avoid company disruptions after go-live and extended maintenance assistance. Another problem is the inappropriate transaction operation. Testing them in both versions will require debugging and cross-checking information.