Always verify the most up-to-date procedures by checking the SUM guide. Always have it on hand while performing the upgrade.
This page provides symptoms and solutions during SPS updates/EHP installations/Release upgrade using Software Update manager (SUM) in the phase MAIN_INIT/REPACHK2
This phase is relevant in release upgrades
This phase displays all the repairs and corrections that are not released and writes them to the REPACHK2.LOG file.
In REPACHK2 phase objects have to be released and the repairs confirmed at the latest by the REPACHK2 phase.
The first prompt for releasing open repairs happens in phase REPACHK1, but at that phase the message was ignored.
Before you continue, you have to release and confirm all the open repairs; otherwise, the objects in them are locked.
Procedure to release change requests
1.Log on to the SAP system as the owner of the open repair. You can find the user names of the owners in CHECKS.LOG.
If you cannot log on with a specific user ID, you can change the owner of the repair in transaction SE09 as follows:
- In the list of open repairs, position the cursor on the repair.
- Choose Change owner. To be able to change an owner in transaction SE09, you need project authorization for the Workbench Organizer (S_CTS_PROJEC)
2. Call transaction SE09.
3. Choose Request/taskFind requests.
4. For Request type, only select Repair.
5. For Request status, select everything except Released.
6.Choose Execute. A list of all open repairs for the selected user appears.
7.Position the cursor on the request that you want to release.
9.Release the request to which the repair is assigned.
REMARK! If you ignore open repairs, you could lose modifications.
Once you have released and confirmed all the open repairs, you have to repeat the REPACHK2 phase.
Any modifications made to SAP objects in your repairs might be overwritten during the update.
During this check, it can occur that SUM reports inactive objects, which cannot be found in the SAP system. For information about removing these inconsistencies, see SAP Note 538167.
Symptoms and solutions
SUM displayed error or Error in log file
Inactive objects found.
4 ETG010 "612 inactive objects found" " " " " " "
4 ETG010 "329 inactive SAP objects" "colliding with import queue
discard the inactive object." " " " "
2EETG010 "The following objects are inactive" "in the system:"
2EETG010 "LIMU" "CINC" "AIC_ONLY_DEV_IBASE_SYSTEM=====CCDEF"
REMARK! If you cannot find the inactive object listed in the log, please follow the SAP note 538167.
See also SAP KBA 2432699 - Active objects are wrongly marked as inactive
Locked SAP objects have been found in open repairs, corrections, or transport orders.
The development environment has been unlocked now. Release the repairs and transport orders to ensure that you can adjust the contained objects, if necessary.
Follow the section Procedure to release change requests
After all these, you can repeat SUM phase and it will check whether any inactive objects or Open repairs left. If nothing found, it will move on.
For BW and after phase REPACHK2:
|Folloe thw SAP KBA 1730554 Infopackage Object cannot be Edited during BW Upgrade|
FAQ (Frequently asked questions)
Related SAP notes/KBAs
SAP KBA 2432699 - Active objects are wrongly marked as inactive
SAP KBA 2177563 - REPACHK_CLONE: Inactive objects and Open repairs found
SAP Note 538167 - Active objects are displayed as inactive
SAP KBA 1730554 - Infopackage Object cannot be Edited during BW Upgrade
SAP KBA 1943694 - Perform transport import during pre-processing phase