topic Re: SPAU adjustent problems when comparing versions in Application Development and Automation Discussions

SPAU adjustent problems when comparing versions

mohamed_jbeli — Fri, 29 Jul 2016 12:04:45 GMT

Hello, After upgrading the system some problems appear when running the SPAU t-code, i have fixed some but i am confused on some others(HTML Templates), the problem is that when comparing the versions it tells that there isn't difference:

When i push adjust it tells:

but no modifications, and when i search for he template in the SE80 and i compare the versions there i just find only one version and it is released in 2014.

So, the problem is that the only solution is to reset the object but am confused because there is only one version.

Any help?

Regards,

Re: SPAU adjustent problems when comparing versions

Szczerbowski — Fri, 29 Jul 2016 12:57:32 GMT

Hi,

Maybe someone registered this standard object for change, but didn't modify.

Can't you compare remotely against QA or Prod?

If you reset, and it's the same, then it's good, no?

Re: SPAU adjustent problems when comparing versions

Jelena_Perfiljeva — Fri, 29 Jul 2016 21:26:47 GMT

+1 to Michal. There is probably more accurate technical explanation but in layman's terms - it could happen, for example, if someone decided to modify the object but ended up not doing it. It could've been rolled back to the previous version but for some reason the record of modification still "sticks" somewhere.

What I'd do is capture the "as is" information (take screenshots and copy any code into a text file) just in case and then do "Reset" to restore the original. De facto there won't be any changes but this will clean up any modification flags.

Re: SPAU adjustent problems when comparing versions

Matt_Fraser — Fri, 29 Jul 2016 22:24:30 GMT

Jelena's right in that, in fact, if an object is modified and then later rolled back to a prior (standard) version, the modification flag is nevertheless still set. Also, sometimes the modification is as simple as an attribute change.

So, generally in this situation, 'reset to original' is the way to go.