Software Logistics
Page tree
Skip to end of metadata
Go to start of metadata

Always verify the most up-to-date procedures by checking the SUM guide. Always have it on hand while performing the upgrade.

PURPOSE

This page provides symptoms and solutions during SPS updates/EHP installations/Release upgrade using Software Update manager (SUM) in the  phase MAIN_INIT/REPACHK2

 

Overview

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.

Note

 If you cannot log on with a specific user ID, you can change the owner of the repair in transaction SE09 as follows:

  1. In the list of open repairs, position the cursor on the repair.
  2. 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.

8.Choose 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.

Note

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.

 

Environment(optional)

 

Troubleshooting tips

 

 

Symptoms and solutions

SUM displayed error or Error in log file
Log file
Solution

Inactive objects found.

Error sample:

4 ETG010 "612 inactive objects found" " " " " " "
4 ETG010 "329 inactive SAP objects" "colliding with import queue
found." 
4 ETG010 "Please contact the development team" "to either activate or
discard the inactive object." " " " "
2EETG010 "The following objects are inactive" "in the system:" 
2EETG010 "LIMU" "CINC" "AIC_ONLY_DEV_IBASE_SYSTEM=====CCDEF"

<update directory>/log/
REPACHK2.LOG

  1. Go to transaction SE80, in the leftside menu, select "Repository Browser"(which is selected by default) and then select "Inactive Objects", input "*" in the next line to search all users, click the Display(eyeglass) button. All inactive objects in the system will be displayed in the list.
  2. Find out the objects in the upgrade error, then double click to check the Attributes tab. If you cannot see the inactive information, click "Active <-> Inactive"(Shift+F8) button to display the inactive version. You should be able to see who and when changed this object.
  3. You can either now activates this inactive version, or use option 'Utilities -> Versions -> Return to active version' for removing the inactive version.
    REMARK! Usually we would not recommend to change the SAP standard definition of the SAP objects, but the decision is on your side based on what was the changed for.
  4. Find out the transport request via version management containing the object. Check, if the tr.request contains SAP notes. If yes, execute report SCWB_NOTE_ACTIVATE for all involved SAP notes.

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.
If these orders are not released, you will not be able to adjust these objects if necessary.

The development environment has been unlocked now. Release the repairs and transport orders to ensure that you can adjust the contained objects, if necessary.

Sample log:
Transport Request|User |Date |Repair |User |Date
========================================================================
K01K900002 |SOLMAN_ADMIN|20150423|K01K900003|SOLMAN_ADMIN|20150423

<update directory>/log/
REPACHK2.LOG

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:

  • You cannot load data during the BW system upgrade before the downtime. 
  • When you try to change the filters for the selection of a Infopackage to start a load request, the system issues following errors:
    Upgrade running (phase xxx) - you can only make limited changes to objects (RSO 861)
    Object xxx cannot be edited during the upgrade (phase xxx) (RSO 862)
 

transaction RSA1

Folloe thw SAP KBA  1730554 Infopackage Object cannot be Edited during BW Upgrade

FAQ (Frequently asked questions) 

 

Related documents

REPACHK_CLONE phase

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

 

  

 

3 Comments

  1. Jörg Sauterleute

    Comment about "Inactive objects found"

    We found that "SE80 > inaktive objects" does not (always) show all / same objects as SUM has protocolled in REPACHK2.LOG
    You can check inactive objects in DEV System using FM 'SUBST_GET_INACTIVE_SAP_OBJECTS' (smile) 

  2. Laszlo Herbert

    Hello Jörg,

    thanks for your feedback.

     

    Regarding FM 'SUBST_GET_INACTIVE_SAP_OBJECTS': It is used by SUM (see also SAP KBA

    2384480    Error in SUM REPACHK_TRANS phase: "SUBST_GET_INACTIVE_SAP_OBJECTS" failed: TIME)

    , but we generally do not recommend to use FMs directly if there is no official documentation available.

    It is better to use transactions, e.g. SE80.

     

    Regarding difference in the inactive objects list from SUM and SE80:

    This has to be checked in detail if this helps to resolve errors.

    The SAP KBA 

    2432699    Active objects are wrongly marked as inactive 

    describes some situations and there are some errors reported on component BC-DWB-UTL*

    You can open a question on the SAP Community Q&A page
    https://www.sap.com/community/about/questions-and-answers.html

    by providing examples if you need further clarification.

    Best regards,

    Laszlo

     

     

  3. Christoph Ostrop

    we got a list of about >300 inactive objects (but not as mentioned in sapnote 538167 and Report RS_WORKING_AREA_CONSISTENCE)

    Reports RS_WORKING_AREA_CONSISTENCE were executed two times (onyDDIC and all - then run again with Option "delete" )

    so in Reports RS_WORKING_AREA_CONSISTENCE no more objects are listed.

     

    but SUM still delivers again a list of inactive objects ??

    why there is no Option to ignore that, so all entries are Z-programs, so what, dont care if they go lost.

    why SUM is forcing customers to waste so much time during Upgrade ?