Brian has already address one possible meaning of your request. I am going to take a shot at another possible one. Did you mean Editor Lock? Regular ABAP programs and Function modules of course have the Editor Lock checkbox on the Attributes screen. Since Global ABAP Object Classes don't visibly have this same option on their attributes screen, it isn't really suprising that it does not appear to be in BSP either. I suspect that SAP hasn't really carried this concept forward in their new development tools.
I have never really understood the value in the editor lock. Any developer worth his/her salt can figure out where the flag is stored and remove it with a little bit of SQL. I have found it to be more of an irritation than anything. It never fails that you get a call in the middle of the night to fix some program, when you find that the long-gone consultant who wrote it left an editor lock behind for no appearant reason.
(Even if you didn't mean Editor Lock, at least this posting has given me the opportunity to rant incoherently. For that I thank you.)
How can you protect an ABAP program?
I am not sure what "protect" means to you, but once it is understood, the question be more clear. Suspect you are refering to Authorization Objects. If yes, either configure one in the ICF node for your specific BSP application, or just write the code directly onto all your pages. Alternative idea with be to implement an application class with the interface if_bsp_application_events. Hook the startup or on_request events and do the checks there. Then it works for all pages within your BSP application, and continues working when new pages are added.
b.
Add a comment