Question:
If we are selling ABAP utilities and we would like people to unlock the ABAP with a valid key just like with most other software you need to get a software key to get the code functioning.
Please kindly share the approach to have such a software key based protection to ABAP various possibilities.
Thank You
Coder
Answer:
If we are selling ABAP utilities and we would like people to unlock the ABAP with a valid key just like with most other software you need to get a software key to get the code functioning.
Won't work.
Some vendors try to hide the license check routine's source code.
But that's easy to bypass.
Answer:
First check with SAP if it is legal to "SELL" ABAP codes/utilities to your customers
Rgds
Answer:
First check with SAP if it is legal to "SELL" ABAP codes/utilities to your customersWhy should SAP object, why should that be illegal, and why should the legality depend on SAP's opinion?
Answer:
Why should SAP object, why should that be illegal, and why should the legality depend on SAP's opinion?
If you developed your software on MiniSAP or the Netweaver sneak previews you'll be in violation of the license, for example.
In answer to your original question: why bother? Many third party vendors don't, and they still manage to be successful. Think: are you more likely to be able to sell to customers with a protection key, or without?
m@t
_________________
TULY The quality of answers is roughly proportional to the quality of the question.
The downside of being better than everyone else is that people tend to assume you're pretentious.
Answer:
If you manage to put your Namespace in table TRNSPACE.
For eg. If table TRNSPACE has got an entry /SUP/ then you can create your own programs such as /SUP/PROG1, /SUP/PROG2 etc.
Your customers can display this program, but CANNOT modify it.
(They can Modify ONLY if they are regular visitors to SAPFans )
KRK
Answer:
If you manage to put your Namespace in table TRNSPACE.
For eg. If table TRNSPACE has got an entry /SUP/ then you can create your own programs such as /SUP/PROG1, /SUP/PROG2 etc.
Your customers can display this program, but CANNOT modify it.
(They can Modify ONLY if they are regular visitors to SAPFans )
KRK
Or if they have a minimal clue about ABAP.
Nevertheless, a separate namespace is still a good idea[tm].