SAP Knowledge Base Article - Preview

3574663 - Objects have an old "changed on" date post-upgrade

Symptom

You notice one or both scenarios:

  1. After a system install/upgrade/update, you notice the "changed on" date of the object (or the date for the active version under Version Management) is different from the time range of when install/upgrade/update occurred.
  2. After a system release upgrade, you notice the "changed on" date of the object (or the date for the active version under Version Management) went 'back in time'. For example:
    • Source release (SAP_BASIS 702): The object has a "changed on" date of May 11 2019
    • Target release (SAP_BASIS 750): The object has a "changed on" date of June 01 2015


Read more...

Keywords

KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-ABA-LA , Syntax, Compiler, Runtime , 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.