Developer Access Key

SAP developers require two things before they can actually do development work in SAP - right authorizations and a developer access key. As with everything else in SAP, when a developer tries to execute a transaction, she will need the required authorizations in her profiles. In addition, she needs to be assigned a developer access key. The authorizations can be checked in the user master records while the developer access key can be checked using table DEVACCESS. Table DEVACCESS will show the user ID and the developer key assigned to the user ID. You should only expect to see name of developers in this table.

But what happens when the entry for a developer is deleted in the DEVACCESS table but the developer continues to use the same user ID? The answer is that the developer can still use the old developer access key.

The reason: Developer access key is nothing but an algorithm based on system number and SID and some other system values (SAP does not reveal the information). The developer access key is validated by SAP using a Kernel level C system program ''CHECK_DEVELOPER_KEY'. So, even if the developer access key has been deleted for a user ID in the DEVACCESS table, she can still use the same developer access key.

So the control should be to:
1. If the developer still works in the company and only the job role has changed, remove the developer authorizations in the user master records.
2. You may also want to assign a new user ID with the required access instead of using the existing user ID - just in case she gets the authorizations by mistake!

One more suggestion, turn on table logging for table DEVACCESS to review all the changes.


Which Table is the Developer Key Stored In
If you would like to look up at your developer key and save it and have it available for the next system refresh. 
The table name is DEVACCESS and can be viewed with SE16 and SE11.
For new ABAP developer, you will be prompt for the developer if you are trying to create a program using the standard SAP naming convention.
Customer own created program should all start with a "Y" or "Z".

Generating a Developer’s Key for a Programmer

1.       Log on to the SAP Marketplace using an OSS ID with Administration rights –http://service.sap.com/sscr.

2.       In the navigator tree on the right-hand side of the SSCR screen, click on Registration.

3.       On the SSCR – Registration screen, click the Register developer radio button and click an Installation hyperlink.  Make sure you select the correct Installation Number for the SAP “flavor” you need or the generated key will not work.

4.       On the SSCR – Register Developer screen, type in the developer’s SAP user ID and click the Register button.

5.       A new Details section will appear.  Note the generated developer’s key or cut-and-paste for other storage.

6.       You may now close your web browser session.

 

Generating an Object Key to Change a SAP-owned Object

1.       Log on to the SAP Marketplace using an OSS ID with Administration rights –http://service.sap.com/sscr.

2.       In the navigator tree on the right-hand side of the SSCR screen, click onRegistration.
3.       On the SSCR – Registration screen, click the Register object radio button and click an Installation hyperlink. Make sure you use the MS SQL installation and not R/3.
4.       On the SSCR – Register Object screen, fill in the information necessary to generate an object key.  If you need help, this information is contained in the Register Object popup the programmer received on his workstation.  Or, if this is a repair, the information can be found in the SAP Note containing the advanced correction.  Click the Register button once all information has been enter.
5.       A new Details section will appear.  Note the generated object key or cut-and-paste for other storage.
6.       You may now close your web browser session.