2012 Jun 21 10:04 AM
Dear all,
I need to write a program which mimics the "copy function (CTRL+F5)" of the ABAP editor (SE38). I encountered some difficulties. Please kindly give me some advises.
The requirement is that the backup program and the source program must be in the same package".
For example, my SA orders me to modify the source programs (Z_PR_ALV and Z_PR_ALV_TOP) in package 'ZMM'. Before I change the source programs, I have to backup the source programs.
My program must do the following.
1. Copy the source programs and rename them with Z_PR_ALV_OLD and Z_PR_ALV_TOP_OLD.
2. Put the backup program (Z_PR_ALV_OLD and Z_PR_ALV_TOP_OLD) in the package 'ZMM'.
I use "INSERT REPORT" statements to create the backup programs. However, they are saved as local objects. Is there any way to save the backup program in the package 'ZMM' using ABAP statements?
Thanks a lot.
ps. I know that I can reassign package in SE80. However, when you need to do backup more than 10 times everyday, you will write a program to do it for you.
2012 Jun 21 10:11 AM
You can reassign packages via SE80 "en masse", just mark a whole block of programs and use the context menu.
Also, what is the added value of this approach over the standard version management?
What is an SA?
Thomas
2012 Jun 21 10:11 AM
You can reassign packages via SE80 "en masse", just mark a whole block of programs and use the context menu.
Also, what is the added value of this approach over the standard version management?
What is an SA?
Thomas
2012 Jun 21 10:47 AM
Dear Zloch,
Thanks for your reply. On the second thought, standard version management is better. Sometimes I just want to make something done, but I forget that doing so has no value.
By the way, SA stands for system architect who is my senior colleague.
Thanks again.
2012 Jun 21 10:18 AM
Hi Michael,
I dont see any point in doing the above excercise. Also are you planning to transport the old programs ? I hope not. Then what is the point in assigning them to a package. It will unnecessarily complicates thing if some one accidentaly modifies the *_OLD program & includes in a transport request. Having it in a local package would atleast save you from above issue.
At any point of time if you want to clean up the DEV system, it would be difficult if objects are assigned to a package as compared to cleaning up local objects.
This isnt the standard practice followed in SAP to backup programs. As Thomas has mentioned above, you can rely on Standard version management to revert back to old version as & when you want.
Thanks,
Best regards,
Prashant