2015 Oct 02 11:00 AM
Hello,
we used the Statement *@#@@[SAP] to hide the abap code. We´ve delivered that Report in two another Systems and we have the Problem that in one System the Editor send the message that the code is protected and in the other System the code appears on the Screen and you can see the Statement in the first line.
Has anyone an idea about this behavior?
kr
Thorsten
2015 Oct 23 7:33 AM
Same problem for us. Code hidden in NW 7.4 SP10 systems and can see code in NW 7.4 SP11. What is NW version of the system where code is not hidden?
2016 Jan 29 8:47 AM
Hello,
The ability to hide code with this statement has been removed with a kernel patch. See Note 2198580
Regards
Pascal
2016 Jan 29 10:10 AM
And why would you want to hide code in the first place ?
Rich
2016 Jan 29 10:58 AM
We developed a proprietary tool which is more of technical solution than a process. Hiding is to protect from code theft.
~ Ram
2016 Jan 29 11:03 PM
Hmm, I wonder how SAP partners are surviving without such "code protection"...
2016 Jan 30 6:50 AM
Now go and read the note and search about hiding ABAP code and realise why this is such a stunningly bad idea.
In many places I've worked, hidden code is an instant criteria for rejecting purchase of a third party tool. Also, if used internally, it's a disciplinary offence.
2016 Jan 30 6:59 AM
There's two things that people might feel need protection:
1. The application code itself, so that people can't install it without a license. This is partially protected by using a namespace like /MATT/. You need a key to install in the namespace, another key to be able to modify objects in the namespace. Copying the application code to a Z namespace (for example) is quite an onerous job, so you'd need a dedicated, hard-working thief.
2. Algorithms. Frankly, there's nothing new under the sun. I doubt there's anything ever particularly clever in any third party solution. I do develop third party add ons.
I do develop third party add ons. We don't hide the code (though we have a few other protection mechanisms). But I'm quite happy for people to see and exploit my techniques.
2016 Feb 01 3:33 PM
Thanks, Matthew! I thought I missed something of value there but apparently not. I do agree that it was not a great idea to begin with.
I'm guessing that customers copy-pasting into their own Z code is what OP is concerned about, but it'd seem rather strange if a company that can afford SAP license would start engaging in such illegal activity. One would think they'd either purchase a solution or pay someone smart enough to come up with their own.
2016 Feb 01 5:01 PM
I just assume they don't want anyone seeing their execrable coding!
2016 Feb 01 5:04 PM
2016 Feb 02 8:32 AM