Documenting the program changes -Standard procedure

[Former Member]

Hi Gurus1

I have a very general question which I am aware of but apart from documenting teh changes within the program in the start of the program , is there any other procedure that is used to document the change ina report or program that is more standard and which si available to all so that even apart from the programmers ppll accross know what are the changes that have been made to a report or a program or a transaction right from the begining so that a history is maintained and the time is available when the changes have been made to a program .

Similary is there a procedure to document the changes a querry goes through in its life cycle which can be documented in a correct way and a history maintained so that all can see what were thenchnages and when was it done and who did it and who requested it .

Actually iw as trying to find out if someone is currently using some systematic procedure to document all changes and in order and how they were doing so that I can apply that for my purpose too.

Thanks

Aarav

[Former Member]

Hi,

We maintain changes in following way.

When a new program is created, the programmer writes his name, date, object id and description.

and does coding now if some else wants to edit program he will add his change description on top of program right below original mod-log.

and all the changes made by him or under the comment structure.

like this

*begin of change <change id> by programmer id

changes

*end of change <change id> by programmer id

or for single line change

changes " change <change id> by programmer id.

This way all the changes are documented in a quite clean manner.

кu03B1ятu03B9к

Edited by: kartik tarla on Feb 6, 2009 10:30 PM

[Former Member]

Yes this si teh procedure that even I use it , but this information wont be easy to be found by functional ppl who are not into using the programing transaction . I wanted to documentation which will be available to all for proper knowledge of whats going on with any transaction and its history of changes so taht if there si problem even they can know who did it and when was it doen ect. I know that the one used now is the best practice and is useful but has someone used nay other process to document it.

ALos what would be the best practice to document a Query in SAP.?

Thanks