Transaction sm12 and Version management

Former Member — Thu, 28 Sep 2006 13:09:50 GMT

Hi All

I am new to sap. I am into sap abap.I want to know:

WHAT ALL INDORMATION CAN WE GATHER BY GOING TO TRANSACTION SM12

AND HOW CAN IT BE USEFUL TO US?

And WHAT IS THE PURPOSE OF VERSION MANAGEMENT? AND WHERE IS IT USEFUL?

Waiting for ur reply.

Thanks and Regards

Ankit

Re: Transaction sm12 and Version management

Former Member — Thu, 28 Sep 2006 13:13:27 GMT

hi Ankit,

Welcome to SDN..

Version Management will help you to track between the programs of two different versions ... support you have created a program and save it with the help of change request and modified it later with another request ... if you wnat to revert the modifications you can do that by version management ..

T-Code SM12 is for <b>Display and Delete Locks</b>

Regards,

Santosh

Re: Transaction sm12 and Version management

Former Member — Thu, 28 Sep 2006 13:19:20 GMT

Hello,

Welcome to SAP and SDN.

The idea simple, when one is working on some object, other person should not be able to change it at the same time.

Check the appln help below for SM12:-

The SAP System is equipped with a special lock mechanism that synchronizes access to data on the database. The purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously.

Implementation Considerations

Locks are defined generically as "lock objects" in the Data Dictionary. A lock request is a specific instance of a lock object and locks a certain database object, such as a correction or a table entry.

Lock entries are usually set and deleted automatically when user programs access a data object and release it again.

Integration

The SAP lock mechanism is closely related to the update mechanism in R/3. A description of handling lock objects is provided in the ABAP Dictionary Documentation under Lock Objects.

The ABAP documentation explains the key elements of the lock concept with regard to programming ABAP transactions in the section entitled The R/3 Lock Concept.

Features

You can use the Lock Management functions (transaction SM12) to check and delete lock entries if the SAP dispatcher, operating system, or network connection fails and the dispatcher is not able to delete these entries. In this case, invalid lock entries remain effective and block access to the locked data when the system is restarted.

For a better understanding of the R/3 lock concept, please refer to the section entitled Functions of the SAP Lock Concept.

The most important profile parameters for the R/3 lock concept are described here. You can use these parameters to tailor your system resources to your needs.

Regarding Version Management:-

When a new development is made, it is the first version. There will be subsequent changes and those changes need to tracked, also at some point of time your are not happy with changes you can easily go back to the old version.

From the menu utilities - versions - version management as all the features to move back to old version, compare the changes made between versions etc..

Hope the above information helps and dont fail to award points for useful informations.

Thanks,

Thirumal

Re: Transaction sm12 and Version management

Former Member — Fri, 29 Sep 2006 07:00:02 GMT

hi Thirumal

Thanks for the reply. I have rewarded the points

to u. Keep njoing.........

Regarda

Ankit

topic Transaction sm12 and Version management in Application Development and Automation Discussions

Transaction sm12 and Version management

Re: Transaction sm12 and Version management

Re: Transaction sm12 and Version management

Re: Transaction sm12 and Version management