get program/include versions

[Private_Member_19084]

Hi

Is there a report/TA, which gives me the active version of all includes/programs?

Like the "Version Management" in SE80, but for more includes/programs.

Thx in advance

[ThomasZloch]

Sounds like all you need is an SE16 for table VRSD.

Thomas

[former_member206439]

Yes in VRSD table you will get all the versions of the object with latest one also under the field LASTVERSNO.

[Private_Member_19084]

Hi Thomas

First of all, thank you very much for your fast and very helpful answer.

Can you please give me more information about this table.

My problem is, that I have in the developer-system around 50 000 entries and in the productive-system only 7 000.

First I've thougt, that only the active version is in the productive-system, but it isn't so.

I miss inlcudes in the VRSD.

Thx again

[Former Member]

oh well, a version gets written when transport request come into play.

In development you may have done 50 transports for a certain thing. It may be that you didnt transport all of them to productive system. In that case you would have less VRSD entries in prod than in dev, but still 50k vs. 7k is somewhat of a GREAT difference.

This sound like you have a huge problem and you have your finger right at the wound.

[Private_Member_19084]

Hi Florian

This was also my first thought, but this can't be.

I'm talking about includes, which has been transported by myself and now are active in the productive-system.

[ThomasZloch]

Normally (unless changed via some system parameter) only the DEV system maintains a complete version history, subsequent systems like QA and PRD only store the active (i.e. latest) version. Only when objects are changed directly in those systems as a repair, a version is written. This should be the exception.

So that difference sounds quite normal.

What exactly is the problem you are facing?

Thomas

[Private_Member_19084]

Exactly Thomas

Only the developer system normaly saves all versions.

The receiving (productive) system only protocols a version, when it gots changes due to the import.

You can activate a permanently version-protocol in the receiving-system, with the profile-parameter VERS_AT_IMP = Always.

see http://help.sap.com/saphelp_nw2004s/helpdata/en/87/0a6b3ae886e511e10000000a114084/content.htm

My problem is, that we have to transport many includes from the developer system into the productive-system.

And there are also very old includes.

To secure, that there are no inconsistency between the two systems, we would like to compare all versions from the developer- and the producitve-system.

It would also be great, when there is a report, which compares the syntax (like se80->version management), but for more then one object

A FM or class would also be ok, then I write a short program.

Thx again

[ThomasZloch]

I think I understand now, you need a mass-compare tool of program objects between two systems. The closest match I think is transaction SREPO, you might want to check it out.

Building something like this yourself is not so straightforward unfortunately.

Thomas

[Private_Member_19084]

Hi Thomas

Thank you very, very much for this.

This is exactly what I was looking for.

Have a nice day/evening

Christian

[former_member206439]

E070CTV and E071 these are the two table you can compare

E070CTV you can see the taret system if that request is released.

if not then target system will be space.

[Private_Member_19084]

Those tables only containing the transport-information.

SREPO, from thomas, is exactly taht what solves my problem.

[Former Member]

Transaction SREPO is a good step in the right direction but needs a few more days of coding to make it a lot more useful - anyone who has tried to use it will know what I'm talking about.

If you like what you see in transaction SREPO, I suggest you take a look at the free apps in Salt (saltapps.com) especially the Matrix app - it allows you to compare whole landscapes simultaneously, drill down and also analyze (also the new namespaces) without the long wait, it also provides the transport information and relative version so that you can see why the difference is there and what to do to fix it.

Cheers,

Dave