How to check changes made in abap program based on sydatum/user id or changes captured in TR

[Former Member]

Hi Experts,

I would like to know, how to check changes done in any ABAP Program which is saved in a TR.

Can we check what  changes are done made in program on any particular day?

Cheers,
KR.

[Former Member]

Hi, go to version history of that program and compare the versions to know the differences/changes between any two versions.

[Former Member]

Surendra,

Thanks for replying back...

I know we can list out changes by comparing versions.

Say...I have only 1 TR ...on Day 1 ... wrote 100 lines of code and on Day 2 ...i wrote anothe 100 lines of code.

Now if someone wants to know which part of code was last written.

How to find out which peice of code was written when?

Cheers,

KR

[matt]

Unless you create a new version every day, it can't be done.

[Former Member]

Hi Karthik,

In Transport Request Version Management you can check complete details of program.

To know which part of code is last written, you need to compare versions in Version Management comparing with Development, Quality and Production servers.

Regards,

HARISH KUMAR. NARAHARI

[matt]

No. You don't need to check between different instances. You can solely in the development instance check the difference between different transports.  You can also generate temporary versions - though these get removed when the transport is finally released.

[Former Member]

Hi,

   Yes, you can create user version by using utilities -> generate version, with this it will create user version 'U' and you can compare the changes further.

    If you are confident then this approach will be ok, otherwise it may lead to confusions what this 'U' type versions and how this will be transported...etc.,

    So its better to maintain some comments (change history) in the code to identity who did what....etc.

    Hope its clear.

[matt]

Surendra Gupta wrote:

    If you are confident then this approach will be ok, otherwise it may lead to confusions what this 'U' type versions and how this will be transported...etc., 

There should be no confusion as the generated (U) versions are removed when the transport is released.

Surendra Gupta wrote:

    So its better to maintain some comments (change history) in the code to identity who did what....etc.

I completely disagree with this statement. A header change log is fine. But it is my considered opinion that in-line comments showing what has been changed are worse than useless - actively harming the maintainability and readability of the code, while gaining nothing. On projects I have run, I have banned this practice.

[Former Member]

Hi MB,

     Thanks for your comments but it seems there is some misunderstanding because I thought people grasp what i am saying.

Coming to the remarks, I agree that U type versions will be removed after transport but according to me generating U type version is not regular practice so most of the users are not aware hence it might lead to confusion.

I didn't mean to write the inline comments about the changes who did what, but what i meant was to have some search key which includes developer id/initials.  It will help to track the changes.

Hope it is clear.

[matt]

Good.

However, I disagree still with the idea that people not being aware of some really useful tool is a reason not to use it.

I use it rarely, however. Only when I'm about to take a leap into something quite speculative, and want to make sure I can get back!