Types of key available in SAP service market place :
1) Developer key
2) License key
3) SSCR key
4) Migration key
1) Developer key: is required for a developer to develop or modify objects in the customer name space. (Y or Z)
Note: this key stored in table “Dev Access”.
2) License key : this key used to get the license for sap systems
• In order to authenticate our production sytem we need to apply the license key
• After installation the license key will be valid for 14 days and again we need to apply for permanent key till 31/12/9999
• Even those license is expired the developer not lose any Data
• In order to apply original license we need to register our system or server in market place (service.SAP.com) and generate the key by providing the system number.
The command for SAP license key:
Saplicense – get = hardware key
Transaction to check license = S license
Steps to install license key using S license :
1) log into sap and goto S license
2) get the hardware key using the command saplicense-get.
3) Go to market place and get registered and get permanent license key
4) Get the installation number
5) Click on key icon to install license
3) SSCR key: (SAP software change registration key) :- in order to modify the objects in SAP main space we need to obtain SSCR key.
Note: in order to obtain SSCR key we need to follow certain steps
1) login to SAP market place with s user ID
2) select the system for which SSCR key needs to be generated
3) specife the program ID,object type and object name along with your SAP R/3 version
4) Migration key: in order to migrate one OS to another OS or from one DB to another DB we required a migration key.
Note: we need to enter the target system OS and DB to generate this key
SAP Data is segregated into three layers
1) SAP standard objects
2) Cross client objects
3) Client specific objects or Data
1) SAP standard objects: These are nothing but repository objects which includes functions, transaction, programs, screens etc………..
• All these are in the name space of A to X
Note: never try to change the repository objects unless and until it is required
2) Cross client objects : These are cross client tables which can be modified
Ex: currency table, measurement table, client administration table etc…...
• what ever changes we make of type cross client will effect all the users present under that clients
3) Client specific objects (or) Data: a change which are specific to a particular client is called client specific Data..
Ex: user master Data, application Data, customized Data
Will update soon... Check next post...