You may end up with the below error message when you are performing an import/export of an SAP systems, in such cases, execute "R3load -merge_bck -
You may end up with the below error message when you are performing an import/export of an SAP systems, in such cases, execute "R3load -merge_bck -e|i
file C:\Program Files\sapinst_instdir\ERP\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\SAPAPPL1.TSK possibly corrupted a previous run may not have been finished cleanly(TSK) ERROR: file C:\Program Files\sapinst_instdir\ERP\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\SAPAPPL1.TSK.bck already seems to exist
Example : R3load -merge_bck -i SAPAPPL1.CMD
Quick Tip : If you are running an import manually using R3load command, then you can use -merge_bck parameter in the command line itself (i.e. R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -merge_bck -loadprocedure fast)
Please note that .bck file is a key for the successful restart of an export/import, so make sure to handle it with care.
Important Points To Consider When You Plan For An Upgrade
When I was scanning through few documents on release/EHP upgrades, got to know many of the important tasks that should be taken care during the cou
When I was scanning through few documents on release/EHP upgrades, got to know many of the important tasks that should be taken care during the course of any EHP upgrade projects (any release upgrade for that matter). I just wanted to collect and list them in this blog, if you think that there is something missing in the list, do post your comments, so that I can keep the blog updated to make it comprehensive and useful for others.
During the preparation of the projects, below are few important items to be considered to ensure smoother upgrade.
Agree and decide as early as possible with business what the downtime requirements are. Only then it is possible to decide the upgrade strategy and to decide on the measures that are to be taken for downtime optimization and to have enough time to perform the optimization.
Maintenance optimizer update in Solution Manager
Upgrade Package Download and Generation of Stack Configuration File (xml) is performed using Maintenance Optimizer, hence it is imperative to ensure maintenance optimizer is configured in solution manager.
Archiving / Housekeping
Plan for archiving and housekeeping for largest tables (or) basis tables (i.e. BALDAT, BALHDR), early identification of tables and objects will help to drive efficiency during the upgrade process (downtime reduction).
Backup and recovery
Backup and recovery starategy need to be checked and re-defined for the project (backup before upgrade, after upgrade) as well as post-go-live landscape.
Start sizing assessment excercise early enough to determine additional requirements needed during and after the EHP upgrade. Monitring the CPU, Disk, User and Memory utilization and judge the hardware resources that will be needed during the upgrade. For the post-go-live hardware requirement, Ideally benchmark the bread-and-butter transactions in both releases and calculate the additional load.
Transports to be released
Plan to release transport requests which contain SAP standard objects, this is to avoid any object locked error during the upgrade
How to handle support during upgrade (or) Reducing Code-Freeze Period
In order to implement emergency fixes and to reduce the timelines for the code-freeze, it is recommended to build a parallel upgrade landscape. Any emergency change that is implemented in production landscape should also be applied in upgrade landscape.
Business functions activation
As business functions are not reversible, it is recommended to use sandbox system to explore new functions. Never play around with "Business Function" activation in Upgrade Landscape. If possible, it is recommended to order "Business Function Prediction for ERP" service from SAP (which is available at free of cost)
Dependency on third party add-ons connected to SAP system are to be validated well in advance. This will help us to get necessary support from third party software provider to ensure smoother transition to next release.
Allocate enough time for documentation (i.e. Technical Upgrade Process, Lessons Learned, Issue Log, Downtime Optimization Techniques, Upgrade Time Analysis, etc.,). This is the key for success.
I've also listed down some of the non-functional tests that should be performed during the mock-run / final preparation phase.
The failure test plan is a documented plan to test the failure scenarios of technical components that can cause all or part of the SAP solution to fail. Components include hardware, software, and operational procedures. Failure scenarios should be simulated to develop recovery procedures. A list of each failure scenario and its impact should be part of the plan.
The connectivity test plan is a documented plan to ensure that all of the technical components of the solution can connect to one another as required in the technical design.
Response Time Snapshots Before and After Upgrade
The response time snapshot is required to ensure that the system is performing as it was
Disaster Recovery Test
The purpose of this task is to test and retest the disaster-recovery plan and procedures defined for the production environment.
The purpose of the test is to check whether the transport mechanism is functioning as expected
Backup and Restore Test
The purpose of this task is to test and retest the backup-and-restore procedures defined for the production environment, until the results are acceptable.
Printing and Faxing Test
The printing and faxing test plan is a documented plan to accurately test the all the business critical printers, fax machines, and output of forms.
System Constellation is Empty, calculation will not run
In our case, we faced this issue while running MOPZ transaction for an SAP BW System
System Constellation is Empty, calculation will not run
In our case, we faced this issue while running MOPZ transaction for an SAP BW System (while preparing for the release upgrade to 7.3), the problem was actually with the product assignment in SMSY transaction, follow below steps to overcome the issue.
SMSY - > Product System - > SID - > Change
Change Product Assignment
Check the Active flag for the product that your system actually belongs to
I would also recommend you to perform landscape verification check to have clarity on the error reported.
Failed To Start StorageService During Release Upgrade
While doing a Upgrade of CRM from 4.0 or earlier to CRM 7.0EHP1 or above, ensure that first step that you execute after post upgrade is running the
While doing a Upgrade of CRM from 4.0 or earlier to CRM 7.0EHP1 or above, ensure that first step that you execute after post upgrade is running the report COM_PRODUCT_UPGRADE. Else you will be facing functional issues post upgrade.