SAP Knowledge Base Article - Preview

3832631 - SPDD: "Reset to Original" greyed out due to inconsistent modification log entries

Symptom

During SPDD modification adjustment (for example, as part of an ABAP system upgrade using SUM), one or more table objects cannot be adopted:

  • Attempting to adopt a modification fails with the error: "Customer version of table [table name] could not be accessed"
  • The resolution described in KBA 3500004 requires resetting the affected object to its original version in transaction SE11 via Edit (entry screen) → Modification Operations → Reset to Original; however, the Reset to Original option is unavailable (greyed out)
  • In transaction SE95_UTIL, the modification log shows entries for the affected tables, but the version history of those tables contains only the SAP-delivered (original) version — no customer version is present


Read more...

Environment

SAP NetWeaver ABAP-based system

Product

ABAP platform all versions ; SAP NetWeaver all versions

Keywords

SPDD, SPAU, modification adjustment, modification log, SE95_UTIL, Reset to Original, "Customer version of table could not be accessed", SUM, Software Update Manager, upgrade, TABL, version history, inconsistent, adopt modification, CWBNTAPPLOG, CWB_DWNLD_FTYPE, CWB_DWNLD_PROC
, KBA , BC-DWB-CEX-ADJ , Tools for Modification Adjustment (SPAU/SPDD) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.