topic Re: Detailed ABAP Function module version controlling in Application Development and Automation Discussions

Detailed ABAP Function module version controlling

MikeB — Thu, 04 Jun 2020 12:54:06 GMT

Let's say, there is an ABAP function module A, which is created by the developer 1 on a date X, onwards ― the original version.

After some perturbations (e.g. merges, releases, transports), in SAP GUI version controlling the first version of the function module A belongs to the developer 2 on a date Y.

I have two questions:

Is there any way to retrieve the original version of the FM?
Is there any way to see a log of version controlling for this FM?
I want to understand by whom and what kind of changes have been applied to this FM.

Unfortunately, the standard Utilities → Versions → Version Management doesn't provide such detailed information or I just can't find a detailed log for a specific function module.

Perhaps, Solution Manager (SOLMAN) contains extended info?

P.S. It is not a problem to retrieve such info in Git VCS.

Re: Detailed ABAP Function module version controlling

MateuszAdamus — Thu, 04 Jun 2020 13:05:28 GMT

Hello mikeb.

What are these perturbations you're referring to?

From my experience, one can easily compare two different versions in the Version Management system of the ABAP objects. The user versions (temporary versions) are removed after every transport release, but the versions moved in the transports are always there.

Kind regards,
Mateusz

Re: Detailed ABAP Function module version controlling

MikeB — Thu, 04 Jun 2020 13:13:39 GMT

Hi mateuszadamus, under perturbations I mean merges, tasks reassignments, releases, and transports.

"The user versions (temporary versions) are removed after every transport release, but the versions moved in the transports are always there." that what I know, that's also written in the documentation (version "U" category).

The problem is that after release to TST environment, the first version I have in VCS is the version, which have been transported, but I'm interesting to see, if possible, the initial version, implemented by the specific developer, not by someone, who released and transported the request.

Re: Detailed ABAP Function module version controlling

MateuszAdamus — Thu, 04 Jun 2020 13:36:19 GMT

Hi Mike,

AFAIK only the versions released with transports are persisted. However, these can also be Transports of Copies, which could be somewhat of a solution for future.

Kind regards,

Mateusz

Re: Detailed ABAP Function module version controlling

michael_piesche — Fri, 05 Jun 2020 05:14:02 GMT

Current Short-Comings of SAPs ABAP "version control system" in SAP Logon:

While the transport is not released, the only way to compare versions at different development stages, is to manually create temporary versions, but it still doesnt tell you who exactly made what change, in case there are multiple developers working on the same code.
With the release of the transport, temporary versions will be deleted and only the final transport versions can be compared in the Dev System, never really knowing who made the actuall changes and not being able to compare against test or productive source code either

You are obviously looking for a more sophisticated Version Control System (or Source Code Management) Tool, with features such as "Local History", "Revision History" and "Cross-System Comparison".

And in this case you should look into the following:

Use ABAPGIT in SAP Logon and upload souce codes to GitHub for version control
https://blogs.sap.com/2019/08/19/versioning-your-local-objects-using-abapgit/
Move to developing in Eclipse and use either one of the two ABAP Development Tools (ADT) version control ressources (client or server), or use any other available version control system for eclipse
https://blogs.sap.com/2012/07/24/comparing-abap-source-code-using-adt/