SAP License Keys
To operate SAP NetWeaver or individual components you need one or more of the following SAP NetWeaver license keys: License type Standard (AAP (AAP license key for components SAP W! SAP "W! and SAP We# AS$ License type J2EE type J2EE Engine Engine (license (license key for standalone SAP %&'' 'ngine$ After you have installed the components! the system is euipped with a temporary license! which is valid for four weeks) *uring this time you have to apply for a permanent license from SAP and install it) +n SAP NetWeaver NetWeaver ,)- and higher! there is a new type license key in addition to the old type) This new license key is #ased on a digital digital signature) oth types of license key are installed installed and administered administered with with SL+.'NS'! SL+.'NS'! as previously! previously! and are availa#le as temporary and permanent license keys) The functions for the new license keys can #e found #y choosing the New the New Licenses Licenses #utton and are descri#ed in the procedure the same as the e/isting functions are) To allow allow a seamless transition! #oth types of license ke ys initially function in parallel after the upgrade) +f license keys of the old type were already installed! you can continue to use these) 0owever! we recommend that you also import license keys of the new t ype! since the license keys of the old type will #e deactivated in the future) 1or this reason! only keys of the new type are assigned for new installations) The fle/i#le license mechanism is now availa#le for high availa#ility environments and Adaptive .omputing! where systems and system components are freuently moved #etween servers (more information: 1le/i#le License 2echanism$) 2echanism $) +t e/tends the previous license procedure so that the license for a system is no longer linked to the hardware of a message server) This means that the license remains valid! even if you move the message server to another server) Requesting an SAP License Key +nformation a#out reuesting the license key from SAP is availa#le on the SAP Service 2arketplace at http:33service)sap)com3licensekey and http:33service)sap)com3licensekey and in SAP Note 45446 45446)) Installing and Managing the License 0ow you import the license key into your system depends on the installation option of SAP NetWeaver) 7ou can find information a#out installing! testing! and deleting SAP licenses in SAP License Procedure) Procedure ) • •
SAP Licensing Procedure Prerequisites To use your SAP software legally and in accordance with the contractual stipulations! SAP Systems can only #e operated with a license key granted #y SAP) SAP)
+f you have installed the SAP We# We# Application Server in the %&''8only variant! you can find the relevant license details in Licensing the SAP %&'' 'ngine ) Process Flow When you install your SAP System a temporary license is automatically installed that allows you to operate the system for four weeks (as of the date of installation$) efore the temporary license e/pires! you must apply for a permanent license license key from SAP) SAP) We recommend that that you do so as soon as possi#le after after you install install your system (or (or transfer the message server to a different host$) See Applying for an SAP License) License) When you receive the license key from SAP! you can install and manage the license using transaction SL+.'NS' SL+.'NS' (see License Administration with Transaction SL+.'NS' $)
More information:
SAP Notes on the SAP License SAP Note Num#er 45446 ;;&;< ;&6;<=,54== ;=&;5 5<&<-6 <<; <6-6= ,;=<; 5&64;; 56&<< ,5&-&5 =6=5< =46=5-
Topic (Short Te/t$ Te/t$ 9euest license key for systems 3 delete systems SAP license in upgrade to 9elease ;)/ (or higher$ .ore dump in SlicShm+nit 1ormation of the hardware key (customer key$ Performance pro#lems accessing ta#le L+.'NS' SAPL+.'NS' ;)=-: new field S7ST'28N9 +mporting the SAP license from a file 0igh availa#ility SAPL+.'NS' License e/piry date is not displayed correctly Transaction SL+.'NS': installation is not working Ta#le 2L+.0'." in wrong ta#le space on >racle *ownloading the license key License key for high availa#ility environment 9eassigning systems
Applying for an SAP License se 7our installation is assigned to one SAP software product) A license is granted for e/actly one SAP system #ased on your installation) 1or your installation num#er! either contact your contracts department or refer to the delivery note) 7ou can only configureone production system (see System Types$ Types$ under each installation num#er) 7ou can only reuest more than one productive system with SAP NetWeaver and mySAP '9P) Prerequisites 7ou have to apply for a separate license for each system) To determine your license key! we need the following data: ? Installation num!er: =- digit num#er assigned #y SAP ? "ontact person: first and surname of the person reuesting the license ? #elephone #elephone and fa$ num!er nu m!er as well as e%mail address: dialing code of reuester and their e8mail address ? System I&: system name (.==! T==! )))$ ? SAP product product (SAP NetWeaver! NetWeaver! AP>! W! and so on$ Software product: Name of SAP ? Software product release: release of the software product ? 'asis Release: 9elease of the underlying SAP asis software (@) ) 5)-! 5)! 5);.! ;)=-! ;)5-)$ ? (ardware data: operating system! licensed data#ase system ? hardware change! and so on Reason for the request: new installation! hardware ? (ardware )ey: ==8character ==8character hardware key of your host computer ? #ype of system: Productive! test (see appendi/: System System Types$ Types$ ? License type: Standard (license key for AAP installation$ installatio n$ %&'' 'ngine (for the pure %&'' 'ngine installation$ Procedure *etermine your hardware your hardware key and key and then reuest your SAP license key) key ) See also: ? 7ou can find details of license keys with a restricted validity period under Balidity Period of License "ey ? 7ou can find find details details of the the =6 digit system num#er created when the license key is is generated generated under Cniue System Num#ers for >ld License "eys and Cniue System Num#ers for New "eys "eys)) Requesting SAP License Keys Procedure 9euest your license key directly from the SAP Service 2arketplace: The +nternet address!
http:33service)sap)com3licensekey
will take you to the initial screen for license keys) 0ere you can find all the information you need to reuest license keys! plus a link to online reuests) Result 7ou 7ou now have all the data you need and can proceed to install the license in your system)
Please also refer to the information on License "ey Balidity) Balidity) *alidity *alidity of the SAP License Key SAP customers customers with rental or purchase contracts usually receive an unlimited license key for their systems) SAP customers with demonstration or test contracts receive a temporary license key that is valid for the agreed test period) A new license key must #e applied applied for when this this period e/pires) e/pires) >nce the license key e/pires or changes are made to your hardware platform! the standard license is no longer valid) +n this case you c an use transaction SL+.'NS' to +nstall a Temporary SAP License) License ) 7ou can then continue to work fro four weeks with this temporary license key) *uring this time! you must apply for and install a new license key) 7ou 7ou can check the validity of your license #y logging onto the SAP System and reading the copyright or #y choosing System D System D Status D Status D SAP system data) data) License Administration with #ransaction SLI"+,S+ se Cp to now you have managed licenses of the old t ype in transaction SL+.'NS') SL+.'NS') y choosing the New Licenses push#utton! you can can now switch to to the initial screen for digitally8signed digitally8signed license license keys (see SAP License "eys$) "eys $)
+f you have not installed a license yet! you can log on as the sap- or work with a temporary license! which is installed automatically when you install or upgrade your system) The sap- user is not authori@ed to delete licensesE Prerequisites 7ou 7ou are logged onto the SAP System and are authori@ed to use this transaction (authori@ation o#Fect SGA*2+G1.*HSL+.$) Features 7ou can use this transaction to I *isplay all installed installed licenses (initial screenJ the currently currently active active installed installed license is highlighted$ highlighted$ I +nstall a new permanent new permanent SAP SAP license I *elete an +nstalled SAP license I *etermine the hardware key for any computer in the system (*etermining 0ardware "eys$ "eys$ Acti.ities +n the SAP menu choose Administration D Administration D SAP Licenses or Licenses or call transaction SLI"+,S+) &etermining the (ardware Key
7ou can use the transaction SL+.'NS' to determine the hardware keys of all hosts for which an 91. connection is maintained) The command saplicense command saplicense -get +2 +2 i: saplicense i: saplicense '-get' '-get' $ is then e/ecuted on the computer in uestion and the result is returned) Prerequisites 7ou are on the first screen of transaction SL+.'NS' and have chosen the New Licenses Licenses #utton) #utton) 7ou have administrator authori@ation) Procedure =) .hoose th the Determine Remote Remote H !ey #utton) !ey #utton) The Determine The Determine Remote Remote Hardware Hardware !ey !ey screen screen appears) All of the computers that are maintained as 91. destinations in transaction S24 are listed here) The highlighted computers are the servers that #elong to the same SAP System System (these are also displayed in the >verview of SAP Application Servers S2=$) Servers S2=$) &) 7ou 7ou can determine determine several several hardware keys here 8 for e/ample! for those computers computers on which you want the message server to run (for e/ample! for failover configurations$) Result • •
The determined hardware keys are in the list Alternati"e Hardware !eys) When reuesting the license key! you can copy the desired hardware key from the list and insertd it in the relevant field) 7ou are now a#le to reuest the SAP license key (see 9euesting the SAP License "ey$)
Installing Permanent /Fi$ed Period0 SAP Licenses se To operate your SAP system on a permanent #asis you need to install a permanent license) This license can #e for a fi/ed period (see Balidity Period of SAP License "eys$) Prerequisites ? 7ou are in transaction SL+.'NS' and have chosen the New Licenses #utton) ? 7ou have received the license key for your installation from SAP) Installing &igitally%Signed License Keys ))) =) .hoose #nstall $emporary License) A dialog #o/ appears! in which you specify the local file to #e loaded from the file system) &) 'nter the license key file and confirm your entry) A success message appears for you to confirm) The new license is displayed under #nstalled Licenses) <) Then check whether you can log onto the SAP System) ))) The license has #een correctly installed if you can log on) +f pro#lems arise (if an error message is displayed during the installation procedure! if you cannot log on! and so on$! please refer to the section entitled 1AKs 9egarding the SAP License) Result The permanent license is installed and displayed in the list of licenses) The license is activated straight away) Installing a #emporary SAP License se 7ou can use a temporary license to #ridge the time period until the permanent license reuested from SAP is received) The temporary license is valid for four weeks) A temporary license may #e reuired in the following cases: ? +f the hardware configuration of the host on which the message server is running changes The hardware key of the computer can also change) ? +f the mesage server is moved to another host ? +f the validity period of the permanent license runs out) 7ou can use the temporary license to e/tend the e/piration date #y 5 weeks) Prerequisites ? 7ou are in transaction SL+.'NS' and have chosen the New Licenses #utton) ? Within the last four weeks there has #een a valid! applied for license and it has #een checked The following message tells you that a temporary license cannot #e granted #ecause the date of the last successful license check was more than one month ago) saplicense: Temporary license N>T installed! >ld license older than 5 weeks ? The SAP system was not created from a copy of an e/isting SAP system)
Apply for a license #efore you are a#out to work with a copied SAP System) Install a temporary license ))) =) .hoose #nstall $emporary License) The new license is displayed under +nstalled Licenses) &) Then check whether you can log onto the SAP System) ))) The license has #een correctly installed if you can log on) +f pro#lems arise (if an error message is displayed during the installation procedure! if you cannot log on! and so on$! please refer to the section entitled 1AKs 9egarding the SAP License) Result •
•
•
•
The (temporary$ license is installed and displayed in the list of licenses) The license is activated straight away)
&eleting an SAP License se 7ou can delete licenses that are no longer needed) A license should #e deleted for instance! if the SAP system was created from a copy of an e/isting SAP system! or if the computer that the hardware key #elongs to is no longer in use)
Never delete Mo#solete licenses if you do not have an active license) Csing this information the system decides whether a temporary license can #e installed (see +nstalling Temporary SAP Licenses in the Prere%uisites section$) Prerequisites 7ou are in transaction SL+.'NS'! have chosen the New Licenses push#utton and have a list of installed licenses) 9ead the section Notes >n *eleting SAP Licenses) Procedure ))) =) .hoose the licenses you want to delete in the list) &) 1rom the menu! choose Edit D Delete License Result The selected license is deleted) >n the SAP Service 2arketplace enter the details of the SAP system for which you have deleted the license) See *eleting SAP Systems on the SAP Service 2arketplace )
,otes 1n &eleting SAP Licenses ? Never delete Mo#solete licenses if you do not have an active license) The system needs this information to decide whether a temporary license can #e installed (see +nstalling Temporary SAP Licenses in the Prere%uisites section$) ? 7ou should not delete the currently active license (this is the one highlighted in transaction SL+.'NS'$) +f you want to do so! you should first install a (temporary$ license so that other users can log onto the system) ? The status of a license is not checked when a license is deleted) +n particular! there is no check to esta#lish whether you are deleting a license that is currently in use) >nce you delete a valid license that is currently in use! no additional users will #e a#le to log onto the system from this point on (e/ception: user sap$) Csers who are currently logged on! however! can continue to work) +f! #y mistake! you delete a valid license that is currently in use! you can reinstall it at any time) See transaction SL+.'NS') #he prerequisite is that you ha.e )ept your license )ey2 ? >ld licenses that are no longer used do not affect the operation of your SAP system) Nevertheless! it is advisa#le to delete licenses that are no longer used (performance optimi@ation during the license check$) 7ou can recogni@e temporary licenses that are #ased on old license keys #y the characteristic! .CST>2'9 "'7 H T'2PL+.'NS') 7ou can recogni@e temporary licenses that are #ased on new license keys in the ta#le Licenses in the *ata#ase in column Type (Perm or Temp$) *eleting temporary licenses does not mean that you can install further temporary licenses (see also +nstalling a Temporary License$) &eleting SAP Systems on the SAP Ser.ice Mar)etplace se 1or licensing reasons! SAP reuires complete details on systems that have #een shut down) Procedure >n the SAP Service 2arketplace under service)sap)com3licensekey reuest your SAP system to #e shut down) 1or more information a#out the deletion procedure see SAP note 45446)
+f you have any uestions or pro#lems! create a message in the SAP Support Portal (component 33%S+R%LIK+4$) nique System ,um!ers for 1ld License Keys
As of SAP We# AS ;)=- the licensing department assigns the uniue system num#er) The S7ST'28N>) is uniue) 7ou can only enter an S7ST'28N>) for an S+*) +f a license with a S7ST'28N>) already e/ists when you install the license! the new S7ST'28N>) must #e identical with the e/isting one) There are two e/ceptions to this: ? The S7ST'28N>) of the new license is O+N+T+ALGS7ST'2G+*O ? All old licenses have O+N+T+ALGS7ST'2G+*O) 0owever only one S+* is ever affected) +f there are licenses for several S+*s in the system! only the S+* specified in the new license is relevant) The new field is displayed on the initial screen of Transaction SL+.'NS') 1ld Licenses 5ithout System ,um!ers 7ou can still install old licenses that do not have a S7ST'28N>) When you are asked to enter the details leave the S7ST'28N> empty (do not enter #lank characters! Fust confirm with 'nter$ and then enter the other data) The S7ST'28N> will #e given the value O+N+T+ALGS7ST'2G+*O) The old license is then valid as normal) (ow &oes the pgrade 5or)6 When a system is upgraded! all old licenses in the system are also upgraded) +n other words! S7ST'28N>) gets the value O+N+T+ALGS7ST'2G+*O) The ta#le is then updated) The following occurs: ))) =) 9ead out licenses) &) Cpgrade licenses! that is! assign them a S7ST'2 N>) <) *elete ta#le) 5) 9ecreate ta#le) ) +nsert licenses) nique System ,um!ers for ,ew License Keys As of SAP NetWeaver ,)- after the system has #een installed! an =6 digit system num#er and a =- digit installation num#er is assigned with the value M-) When you receive your permanent license key from SAP! you will also #e assigned the system and installation num#ers! which are loaded from the license key file) +f you create a temporary license key later! #oth num#ers are copied to it) To change the num#ers you first have to delete all the e/isting license keys and then import the new license key with the correct num#ers) +f you unintentionally import a license key with an Mincorrect system or installation num#er! you will get an error message) (igh A.aila!ility "onfigurations
+n the conte/t of the license procedure! you can install multiple license keys) This is reuired! for e/ample! if your configuration is a cluster environment of hosts that can #e switched to stand#y hosts if an error occurs (high availa#ility strategy$) +f stand#y hosts are defined for the message server (or SAP System$ in high availa#ility configurations! you need to set up a license key for each stand#y host) 7ou can determine the hardware key of the stand#y host either as descri#ed in *etermining the 0ardware "ey! or #y e/ecuting the command saplicense 8get (+2 i: saplicense Q8getQ$) 9euest your high availa#ility license key as descri#ed in SAP Note =6=5<) Alternati.e +f you do not know in advance which hardware key is relevant after the failover! you can install a temporary license key on the stand#y host) Then you have two weeks in which to either switch #ack to the old host or to install a new permanent license key on the stand#y host) More Information 2ore information a#out how to automatically install a temporary license key in the case of a failover: SAP Note <6-6=)
Fle$i!le License Mechanism
The fle/i#le license mechanism e/tends the previous license procedure in such a way that the license for a s ystem is no longer connected to the hardware for a message server) This means that the license remains valid! even if you move the message server to another server) This is primarily important for high8availa#ility environments and for Adaptive .omputing! since systems and system components often have to #e moved #etween servers in these situations) The fle/i#le license mechanism does not assess the hardware +* of the message server! #ut rather uses a separate +* generator! which is implemented in the SAP0ost.ontrol process) This generator calculates a uniue +* for each message server #ased on the following data: 0ardware +* of the +* generator (which acts as an anchor$ Network parameters of the message server itself Network connection #etween the message server and the +* generator +f you are using virutal +P addresses! you can move the network +* together with the message server to another host! and therefore retain the uniue +*) The only thing you cannot move is the +* generator) • • •
Architecture of the License 2echanism The illustration shows the following process: As soon as a user logs on! the license is checked) The AS AAP application servers can #e started with or without a valid license) The SAP user can also log on to the system without a license check) The applicaiton server (consisting of a dispatcher and work processes$ searches in the data#ase for a suita#le! valid license) The validity of the license depends! among other things! on the hardware +* provided #y the message server) +f the fle/i#le license mechanism is set up! the message server no longer uses its local hardware +*! #ut rather uses the SAP0ost.ontrol +* generator to determine a network +* that is used instead of the hardware +*) The message server reuests a network +* when starting and at periodic intervals) +f you are using multiple +* generators! the first valid response is used) +f the message server does not receive a valid response when starting! or •
•
•
•
during a &5 hour period of operation! it uses the local hardware +*) The message server then reuests a valid network +* every five minutes) Integration Licenses #ased on network +*s are not a solution for scenarios for which licenses need to #e independent of #oth the hardware and the network) This means that in a *0.P environment! you cannot move the message server to a different su#net (for which a different +P address is usually reuired$) Adaptive .omputing and most high8availa#lity solutions do not use this approach) 0owever! some 0A solutions support this using dynamic *NS reconfiguration) These scenarios are not covered #y the network +* approach) 0A solutions can! however! use multiple (usually two$ +* generators) +n this case! each system reuires two licenses! one for each +* generator)
Setting p the Fle$i!le License Mechanism
Parameter slic3netidGservers in the message server profile defines the +* generators to #e used) The synta/ of the value is a list of +* generator host names and their ports separated #y spaces) Since SAP0ost.ontrol uses the fi/ed! registered +ANA port saphostctrl! the value is always ==&6) 7ou activate the fle/i#le license mechanism #y setting parameter slic3netidGservers to Ridhost=:==&6 Ridhost&:==&6 )))) RidhostN:==&6 in the profile of the message server! restarting the system! and reuesting a new license) To allow a seamless transition to the fle/i#le license mechanism! and to reuest licenses for all configured +* generators! or if you do not have access to the system! you can proceed as descri#ed in the procedure #elow) Prerequisites The appropriate kernel patch for the changes at the message server has #een installed) The +P address of the message server (rdisp3mshost$ must #e fi/ed (that is! no *0.P! for e/ample$) To #e a#le to move the message server to another server with only one installed license! it must #e set to the virtual +P address! which is moved together with the message server) At least one SAP0ost.ontrol with release ,)= is installed in the system landscape (more information: SAP Note =-<=-4;$) 1or high8availa#ility scenarios! at least two SAP0ost.ontrol agents must #e installed and configured at the message server with slice3netideGservers to safeguard against the failure ofone SAP0ost.ontrol) 7ou can decide yourself whether you install SAP0ost.ontrol once for your entire system landscape! install multiple copies for su#areas for the system landscape! or install a separate SAP0ost.ontrol for each system) The +P address of SAP0ost.ontrol must also #e fie/ (that is! no *0.P! for e/ample$) 'nsure that there is an unrestricted network connection #etween the message server and the SAP0ost.ontrol in #oth directions! without any address conversion) SAP0ost.ontrol must also #e accessi#le from the +P address of the mesage server) 7ou can configure this with parameter rdisp3mshost) Procedure =) +n transaction 9==! set the profile parameters rdisp3msserv! rdisp3msservGinternal! and rdisp3mshost and the corresponding +P addresses and ports in accordance with your reuirements) Profile Parameters for .onfiguring the 1le/i#le License 2echanism Profile Parameters &escription rdisp3mshost Specifies the host on which the message server is running rdisp3msserv Name of the service where the message server can #e reached) Csed to separate the communication types of the message server) The default value is -: no internal port rdisp3msservGinternal A value other than -: +n addition to its port sapmsRS+*! the message server opens another port (port num#er n$ used only for internal communication with the application servers) &) *etermine the message server port as a decimal value) +f the profile parameter rdisp3msservGinternal is configured and is not -! use this value) >therwise! use the value of profile parameter rdisp3msserv) • •
•
'/ample =) &) <) 5)
rdisp3msserv H sapms+N rdisp3msservGinternal H 3etc3services: sapms+N <;-53tcp H <;-5
'nd of the e/ample) <) *etermine the +P address of the message server #y checking the profile parameter rdisp3mshost) '/ample =) rdisp3mshost H #inmain &) ping #inmain: =-);;);;)4= <) H =-);;);;)4= 'nd of the e/ample) 5) 1etch the new network +* of each +* generator #y using the +P address of the message server and the port with the script sapcontrol) '/ecute the command sapcontrol on the client and not on the server) '/ample =) sapcontrol Unr 44 Uhost idhost= Ufunction VetNetwork+d =-);;);;)4= <;-5 H hardware key: @eVTCeA;W &) sapcontrol Unr 44 Uhost idhost& Ufunction VetNetwork+d =-);;);;)4= <;-5 H hardware key: lLT>kWF26> 'nd of the e/ample) ) 9euest new licenses from SAP for each hardware key! and install these licenses in the system (more information: +nstalling Permanent (1i/ed Period$ SAP Licenses $) ;) .onfigure the message server so that it connects to your +* generators) Set the profile parameter slic3netidGservers to do this! for e/ample slic3netidGservers H idhost=:==&6 idhost&:==&6) ,) 9estart the message server so that your changes take effect) This usually reuires a system restart) 6) +n the message server trace devGms! check whether errors occurred! and whether the new hardware key is listed! such as .CST>2'9 "'7: @eVTCeA;WR) 4) *epending on your system and the release in use! check with transaction SL+.'NS' of AS AAP! with the Bisual Administrator! or with SAP NetWeaver Administrator! whether the system is using the newly8 installed licenses)
Monitoring with the System Log
The message server outputs the following new system log messages for monitoring and trou#leshooting: SL shows that the network +* has #een changed! which is not a pro#lem as long as a suita#le license is installed: Severity: +nformation o Te/t: Network +* changed! new +* is o SL; indicates an error during the periodic update of the network +*! if it is not possi#le to access an +* generator) An e/isting network +* is still valid! since the &5 hour grace period has not yet e/pired) Severity: Warning o Te/t: Cpdate of the network +* failed o SL5 indicates reversion to using the hardware +* of the local message server! since it was not possi#le to update the network +* for more than &5 hours! or the first reuest for a network +* failed) To continue to use the system you reuire a corresponding license for the local hardware +*) Severity: 'rror o Te/t: 'rror in network +* update H switch to local hardware +* o •
•
•
FA7s Regarding the SAP License The following is a list of freuently asked uestions regarding the SAP license) ? To install the license you do not have to shut down or restart the SAP system) The installed license is activated straight away) ? What is the system num#erX A system +* for which there are >ld License "eys and New License "eys depending on the release) ? *oes the customer need a separate license key for the 'nterprise Portal SAP NetWeaver &--5 Support Package Stack -4X No! he3she does not) As of 'nterprise Portal SAP NetWeaver &--5 Support Package Stack -4! the portal no longer asks for a license key)
?
Which SAP notes a#out licenses could help solve pro#lems that may occurX ,ote ,um!er "ontent --=<,5< No valid license installedJ no logon --=56<6 No valid license after hardware change3upgrade --655; Pro#lem with saplicense during the upgrade -===;< saplicense cannot delete inde/ -=&,& saplicense 8get on *'.8CN+ gives no key -=5,,&9. 44 when installing the license -=,54== 1ormation of the customer key (0W key$ -=4<6-saplicense: Trace functions --;6& SAP license key invalid after A+ upgrade --=&6-4 0ow to install license -=<==;& +nstallation num#er is +N+T+AL --45446 9euest license key for system3delete system ? What should you do if the notes cannot helpX .reate a message in the SAP Service 2arketplace under service)sap)com3message under component: .8.ST8SL! if an error occurs with the license that you cannot solve with the help of the notes) 8S'98V'N8.>NT9! if you have uestions a#out the license agreement or your contract) 8S'98L+"'7! if you have uestions a#out the license key) Tips on creating a message for old type license keys: 7ou also have the option of Testing the License "ey) This may help you locate the source of the pro#lem) 7ou can also create a trace file with detailed information #y using saplicense %test pf89Profile #RA"+8; ) +n most cases! saplicense %show and a trace file are necessary to solve any pro#lems with old type license keys) To speed up the pro#lem solving you can include these details in the message) +f you have pro#lems creating the trace file read note =4<6--)
#esting 1ld%#ype SAP License Keys
.aution 7ou cannot administer digitally8signed SAP license keys of the new type at operating system level) 'nd of the caution) +f you cannot log onto your SAP system! you can use the saplicense option 8test pfHRProfile (+2 i: Q8test pfHRProfileQ$ for trou#leshooting purposes) When you call up this option! the saplicense program determines the hardware key of the message server! simulates a logon to the SAP System! and carries out the necessary license check) 7ou can follow all of these steps on the screen) Procedure =) At the operating system level! log on as Rsapsidadm (CN+ and Windows$ or RS+*>19 (+2 i$ to the computer running the central SAP instance) &) CN+ and +2 i: Start your SAP System and the data#ase with startsap) 2icrosoft Windows: Start your SAP System and the data#ase with the SAP Service 2anager) <) .all up saplicense as follows: CN+ and 2icrosoft Windows: saplicense 8test pfHRprofile +2 i: saplicense Q8test pfHRprofileQ 7ou must specify the profile file) Specify the profile file (with the complete path$ of the SAP System you want to test) '/ample 1or an SAP System with the name P9* (instance num#er --$ on the host sapr
The following message specifies the license key used for the test: L+.'NS' system: P9* hardware key: *=664<4-<55 e/pirationGdate: 4444=&<= installation no: ------&= key: 4"%*7+TLBLP9S4WBS6SNTN productid: 99A 'nd of the e/ample) +f you receive an error message during the license key check! you can use the data output #y the program to determine the cause of the error) (.onnection setup to the message server! connection to data#ase! and so on$) *epending on the message! check whether the message server is running! or whether the data#ase has started! and so on) 7ou can use the T9A.'H& option to carry out a detailed error analysis) The command synta/ is as follows: saplicense 8test pfHRProfile T9A.'H& +2 i: Q8test pfHRprofile T9A.'H&Q saplicense then creates the file devGslic in the current directory) This file contains detailed error messages)
Appendi$ The section System Types descri#es the different types of SAP Systems) System #ypes The following types of SAP System e/ist) PR1&: Production system A system in which the real8life #usiness processes of a company are mapped and in which real8time data is recorded) &+*+L1P: &e.elopment system A system in which in8house developments and .ustomi@ing settings are made) #+S#: #est system A system that is used for prototyping and testing system settings and processes) #RAI,: #raining system A system that is used to teach system settings and processes) I&+S A system that is used e/clusively for the SAP +nternational *emonstration and 'ducation System) +*'S uses a model company to descri#e common #usiness process and e/plain how they are mapped in the SAP System) &+M1: &emonstration system A system that is used e/clusively for internal employee training or presentations for interested parties) 'A"KP A separate #ackup system for a (live$ system) ackup systems were used previously to map high8availa#ility configurations) Since *ecem#er =444! high availa#ility configurations can #e mapped correctly #y reuesting several license keys for one system) See also note =6=5<)
System Measurement
With the measurement program (transaction CS22$! you determine the num#er of users and the chargea#le o#Fects of the 'ngines of the SAP software for each system) The measurement program contains counting modules to automatically determine the 'ngines used (generic SAP! SAP New *imension! and SAP +S Add8>n products$) The measurement program is used e/clusively to determine the num#er of users and the utili@ed units of SAP products) As of SAP 93< 5);! the system measurement of the users is performed in dialog) The measurement of the SAP 'ngines runs in the #ackground) The measurement program automatically detects the 'ngines used in the system! measures them in the #ackground! and lists them in the measurement log) Programs for measuring 'ngines are either delivered with the product or are also availa#le for lower releases through Support Packages) 1or information a#out the currently availa#le programs for measuring 'ngines and other information a#out the measurement program! see the SAP Service 2arketplace) http:33service)sap)com3licenseauditing) 7ou must only use the tools provided #y SAP! in their original state! for measurement) 7ou should transfer the result of the measurement to SAP immediately and in an unchanged format) Integration With system measurement! you determine the num#er of users and the chargea#le o#Fects of the 'ngines of the SAP software) Then consolidate the results of the system measurements in the License Administration Work#ench to ultimately transfer the consolidated measurement result to SAP) .entral maintenance of the license data in the conte/t of central user maintenance is supported as of SAP NetWeaver Y-5 (#y Support Package! as of SAP We# Application Server ;)&-! see SAP Note ,-55=&$) Scope of Application This document is #ased on the revised and e/tended functions of the measurement program of SAP NetWeaver Z-5) +ndividual functions are also availa#le for lower releases through Support Packages (see SAP Note 5&65,4$) >verview of the Availa#le 1unctions in the 2easurement Program for each 9elease Function "lassification Recommendation In Standard From Su#seuent measurement or for releases Cser 2aintenance (SC-=$ without mass changes: when users are SAP 93< <)-1 created List of users of measurement program >verview of all usersQ classifications SAP 93< 5)- SAP We# Cser maintenance using reference users Csers with identical authori@ations Application Server ;)=SAP We# >n first measurement for classification of 2ass change Application Server user groups ;)=.hange user classification from type A to 2ass change of user types SAP 93< 5);. type AdFust user types after price list has #een Price list migration SAP 93< 5);. changed Technical user types communication! system! SAP We# service! and reference e/cluded from Application Server measurement ;)=SAP We# SAP[s own users automatically e/cluded from Application Server the measurement ;)&SAP We# Standard users are classified as test users in Application Server non8production clients ;)&SAP We# .ountry surcharge for user types Application Server ;)&*isplay the S*.. transfer status in the SAP NetWeaver Q-5 measurement program
>verview of the Availa#le 1unctions in the 2easurement Program for each 9elease Function "lassification Recommendation *isplay the num#er of users of the 2o#ile 'ngine in the measurement log .lassification help
In Standard From
SAP NetWeaver Q-5 SAP NetWeaver Q-5
Process of System Measurement
The following process provides an overview of the preparation and performance of the system measurement! which you must perform for each SAP system) Prerequisites 7ou have the authori@ation SGCS'9GV9P) 7ou have the authori@ation SGT.0G%>) Process =) Start the measurement program (transaction CS22$ #y choosing Administration Administration System &easurement ) &) The System Data ta# page contains information on the systemQs uniue +* for your information) As of release 5)-! a s ystem is automatically identified as productive! as soon as one client is identified as productive) 7ou can change this setting only using the role of the client in the client administration) <) Specify the clients to #e measured) To do this! mark all measurement8relevant clients on the lients ta# page as included) y default! the clients --- and -;; are e/cluded) 7ou can also e/clude the following clients from the measurement! #y removing the #ncluded indicator: o Test clients in a production system .lients that have #een copied for test purposes o • •
Note +n releases from 5); to 5) (inclusive$! you select the clients to #e e/cluded) +n release <)=+ and #elow! specify the clients to #e e/cluded with the E(clude lients option) 'nd of the note) 5) Activate at least one price list that is valid for your contract #y setting the Acti"e indicator on the Price Lists ta# page) When you do this! the user types that #elong to the relevant price list are displayed on the )ser $ypes ta# page) The following price lists are availa#le for the SAP We# Application Server: SAP Software .omponent Price List (SW .omponent Price List$ o mySAP)com Solution Suite Price List (mySAP)com Solution Suite$ o mySAP)com +ndividual Solutions Price List (mySAP)com Solutions$ o 1or SAP 93< 5);.! the following price lists are availa#le: SAP Software .omponent Price List (SW .omponent Price List$ o mySAP)com price list o 1or releases #elow SAP 93< 5);! the user types from the various SAP price lists! especially those from the mySAP)com price list! are availa#le through Support Packages (see SAP Note 5&65,4$) +f you reuire additional mySAP users types for the usiness Suite and the +ndividual Solutions for user classification! which are not yet availa#le in the measurement program for your release status! you can download these individually or together from the SAP Service 2arketplace) http:33service)sap)com3licenseauditing System &easurement Named )ser &easurement Program $ips * $ric+s ) >n the )ser $ypes ta# page! set the Acti"e indicator for the relevant user types) To keep the list of user types as short as possi#le! deactivate the special module and +S user types! if you do not have any contractually defined special module users) The active indicator controls the display of the selected users in the user classification and the input help of user maintenance) Note
As of SAP 93< 5)-! you can specify e/actly the contractual special module and +S user types) To do this! select the te/t of a standard special module user type (such as SP'.+AL 2>*CL' T7P' =$! and overwrite it with the name of the contractual user type) Then save your entries) 'nd of the note) ;) +f you do not want to further consolidate the measurement results with the License Administration Work#ench! #ut rather want to transfer them immediately! specify the address of the measurement recipient on the Addresses ta# page) ,) .lassify the users) To #e a#le to measure all users of your SAP installation clearly and e/actly! you must classify your users in accordance with the current use and the underlying price list #efore every system measurement) +f your contract changes! you must reclassify the users that have already #een classified in accordance with the user types in the new license) 1or security reasons! you can generally only change the user type in the client to which you are logged on) 7ou have the following options for user classification: .lassify the users individually) o o Cse a reference user ) .lassify the users #y group) o Perform a 2ass .hange of the Cser Types) o Cse the user lists from the system measurement) o 2igrate Price Lists) o 1or information a#out the user types! see *efinition and Availa#ility of the Cser Types ) 6) Start the measurement in the measurement program (transaction CS22$ #y choosing System &easurement ) y choosing this! you automatically also start plausi#ility checks) Note the information a#out the evaluation rules and the measurement results) 4) .heck the results using the measurement statistics) To do this! choose the &easurement Statistics option) +f there are discrepancies! you must repeat the steps as of the user classification (step ,$) The measurement statistics contain more data than the measurement log! so that you can more easily investigate discrepancies) =-) .heck the user classification with the List lassi,ication Help function (see .hecking Cser .lassification$) ==) To format the finally determined measured data into a print format! choose the reate Log option on the initial screen of the system measurement) The measurement log contains mainly the same data as the measurement statistics! however it is anonymi@ed here! and com#ined system8wide: 0eader with date and address data o System8specific data o 2easurement8relevant information and results o 9esults of the #ackground checks o 2easurement results of the e/cluded clients o =&) Specify the e/ternally defined users that communicate with e/ternal software products that #undle! temporarily store! or summari@e the communication activities and then forward them to the SAP installation) Cse! for e/ample! the comments function of the License Administration Work#ench (LAW$ to do this) =<) This is the last point at which you can use the omments function to enter additional information a#out the measurement results (#y entry or file upload$ that you want to send to SAP) =5) Transfer the measurement results to SAP: +f you are only using one SAP installation! transfer the measurement results directly to SAP (see o Transferring 2easurement 9esults$) +f you are using multiple SAP installations! first consolidate the measurement results in the o License Administration Work#ench) Then send the consolidated result to SAP) 9ecommendation Transfer the measurement results of the SAP component system as soon as possi#le after the measurement to the LAW central system) This means that the pro#a#ility of changes to the user master records is low and there are no (or only a few$ differences #etween the user t ypes statistics of the CS22 measurement results of the individual systems and the consolidation results of the LAW)
'nd of the recommendation) =) .heck the transfer status)
"lassifying Indi.idual sers
7ou can assign a user type to a user when you create the user) This is especially useful! if you have already performed a system measurement! and have classified all users that e/ist when doing so) Procedure =) Start the user maintenance (transaction SC-=$ #y choosing $ools Administration )ser &aintenance )sers ) &) Specify a user or an alias! and choose .hange! .reate! or .opy) As of SAP We# Application Server ;)=-! the contractual user type and the special version are copied when you copy a user) <) .hoose the License Data ta# page in change mode) 5) Cse the input help to select the contractual user type! and! if necessary! assign a special version or a country surcharge) Note Alternatively! you can assign a reference user to the user on the Roles ta# page) 'nd of the note) ) Save your entries)
"lassifying sers with Reference sers
7ou can classify your users #y assigning a reference user with an appropriate classification) A user can inherit the classification of the reference user if: No additional roles or profiles are created for it +t is not manually classified Prerequisites A reference user with the reuired user classification e/ists) 7ou can use the system measurement transaction (transaction CS22$ to check this #y displaying all reference users that e/ist in the system) To do this! choose oto Re,erence )ser lassi,ication and then E(ecute) Procedure "reating a Reference ser =) .reate a user in user maintenance (transaction SC-=$) &) >n the Logon Data ta# page! choose the Re,erence user type! and deactivate the password) <) >n the License Data ta# page! use the input help to select the contractual user type! and! if necessary! assign a special version or a country surcharge) 5) Save your entries) Assigning sers a Reference ser Assign the relevant classified reference users to your users in the user maintenance or user mass maintenance on the Roles ta# page) Result 7ou have classified the users indirectly using a reference user) 7ou can use the e/tended list of the measurement program to display a list of all users that inherit their classification using a particular reference user: =) +n the system measurement transaction (transaction CS22$! choose the )ser lassi,ication option) &) .hoose E(tended List ) <) Specify the name of the reference user (with the input help$! and choose E(ecute) • •
"lassifying sers with the ser Mass Maintenance
The )ser &ass &aintenance is well8suited for the initial user classification) +n this way! you can classify users #y group! such as #y department or cost center) To avoid accidentally overwriting correct user type! we recommend that you later maintain the user types using )ser &aintenance or the )ser List ) Procedure =) Start the Cser 2ass 2aintenance (transaction SC=-$ #y choosing Administration System Administration )ser &aintenance )ser &ass &aintenance ! and select the users (more information: 2ass .hanges! function Select )sers$) &) >n the )ser &aintenance. &ass /anges #nitial Screen! select the users whose user t ype you want to change) <) .hoose /ange) 5) >n the License Data ta# page! choose the contractual user type and! if necessary! the special version or the country surcharge for the selected users of the group! or assign an appropriate classified reference user to these users) ) Save your entries)
"lassifying sers with the ser List
0alid ,or SAP Netea"er 1345 SAP Netea"er 144 SP365 SAP Netea"er 764 SP235 and SAP e8 AS 724 SP76 The measurement program generates a list of all users created) With this user list! you can classify your users clearly and effectively) A user list that displays the important user data is availa#le to you) 7ou can display details for a user #y dou#le8 clicking the user) +n addition to the information shown #y the previous user list! the list now also shows the role assignments! the classification type! the user group! and a status column for the classification) SAP We# Application Server provides two lists: The Simple List for manual classification of the dialog and system users The '/tended List for checking classifications Procedure =) Start the measurement program (transaction CS22$) &) .hoose )ser lassi,ication) The user list displays all users of your SAP system with the assigned user types) '/planations for the List "olumn Additional ,otes green H >" yellow H inconsistent classification red H incorrect classification! for e/ample with a contractual user type from an invalid price list) .lassification red H incorrect classification! for e/ample with a contractual user type from an invalid price list) status +f the status is yellow or red! you can display additional information to help you find the source of the error #y dou#le8clicking the user) +f you then determine that! for e/ample! the reference user is not correct! you can go to the user maintenance #y dou#le8clicking the Re,erence )ser field and change the reference user) +* +* of contractual user type .ontractual 9esulting contractual user type of user Cser Type Technical Cser +ndicator for the technical user type! such as dialog! system! service Type *: *efault user type 9: 9eference Cser .lassification 2: 2anual classification Type A: +nherited through the role attri#ute : '/cluded user Cser Vroup Name of the user group to which the user #elongs) 9ole Assigned role on the #asis of which the classification was made • •
Note +f you need to! you can change the layout of this ALB List) +n self8defined layouts! you can add additional fields to this view) 'nd of the note) =) +n the list! select the users for which you want to change the classification) &) .hoose Selected Records) <) Cse the input help to specify the user type) *epending on your individual contract! you may still have to specify the special version or the country surcharge) 5) Save your entries) Setting p Role%'ased License "lassification
0alid ,or SAP Netea"er 1345 SAP Netea"er 144 SP365 SAP Net ea"er 764 SP235 and SAP e8 AS 724 SP79 With the following procedure! you can assign a contractual user type to a few key roles (such as composite roles$) When these roles are then assigned to users! these users can #e classified using the assigned user types) +f multiple classified roles are assigned to a user! the roles are consolidated in a similar way to what is License Administration Work#ench (role is contained in role A! therefore role A is used for classification$) +f the system cannot consolidate the roles! for e/ample! #ecause too many roles are classified! it indicates this in a list) The roles are classified #y activity area and not #y authori@ation) Prerequisites A user can only inherit the classification of the role if: The user is not classified using a reference user The user is not manually classified Process =) Start transaction L+.'NS'GATT9+CT'S) The system displays a client8specific list of all e/isting single and composite roles) &) +n the row of the role to #e classified! use the input help to select the contractual user type in the )ser $ype column) <) Save your entries) 5) 7ou can now assign the classified role to users in user maintenance (transaction SC-=$ to assign a contractual user type for licensing to them) ) To display the classification result of the roles! start transaction CS22 and choose )ser Data Analyses \lassi,ication Help \ Role #n/eritance) The system displays a list of the users that have #een assigned classified roles) The users can have the following classification statuses: Vreen H >" 7ellow H manual classification of the user is reuired! since the different roles cannot #e consolidated 9ed H A manual user classification e/ists that does not match the role classification Result 7ou have classified a small num#er of important roles for licensing users to assign a contractual user t ype to the users) • •
Performing Mass "hanges of the "ontractual ser #ypes
As of SAP 93< 5);.! you can use the measurement program to perform mass changes of user types of a price list) 7ou can use this function to assign a user type to all users that have not yet #een classified! and to change the classification of all users of type A to type ) 1or security reasons! you can only change the user type in the client to which you are logged on) Prerequisites 7ou have chosen En"ironment &ass /ange on the initial screen of the measurement program and the system is displaying the dialog #o/ System &easurement. &ass /ange o, )sers! which offers the following options: .lassify unclassified users .hange old classification Procedure • •
"lassifying nclassified sers =) Cse the input help to specify the new user type and! if reuired! the special version or country surcharge) &) .hoose E(ecute) <) .heck the security uery! and confirm the mass change) The change to the users is confirmed in the status #ar) "hanging an 1ld ser "lassification =) Cse the input help to specify the previous and the future user type) &) .hoose E(ecute) <) .heck the security uery! and confirm the mass change) The change to the users is confirmed in the status #ar) Migrating Price Lists
When the active price list is change! you must adFust the contractual user types) A tool is availa#le in the measurement program for migrating the uesr types of the SAP Software .omponent price list to user types in the mySAP)com price list) 7ou can use this function to change the old user types to user new user types in the current price list) Prerequisites 7ou can migrate user types in the client to which you are logged on) Procedure =) >n the initial screen of the measurement program! choose En"ironment &igration Price List ) The dialog #o/ System &easurement. &igration Price List appears)) &) Cse the input help to specify the new user type for each of the old user types to #e changed) +f you do not specify a new user type in a row! users with this user type are not migrated) <) .hoose E(ecute &igration The system displays a message that the user type of your users has #een changed) 5) .heck the new classification of your users)
"hec)ing ser "lassification
7ou can use the lassi,ication Help function to check your user classification (as of SAP NetWeaver ,)-$) >n the #asis of this user data! the lassi,ication Help function provides lists of users that access functions and o#Fects that they may not #e permitted to use in accordance with their classification) 7ou can use the list to check the classification of the listed users) As soon as you are satisfied with the classification of the users! you can perform the measurement again! and then transfer the measurement results as usual) The user lists are anonymi@ed when this is doneJ that is! the data is transferred to SAP without the user names) lassi,ication Help provides you with the following options for checking your user classification: .lassification 0elp 1unction Function Additional ,otes *isplays a list of the users that were stored as the last to change source code within Work#ench user the last twelve months) Professional3Limited *isplays a list of users that are classified either as employees or as 'SS users! and Professional user that have made changes to ta#les that do not relate to self8services) 9ole inheritance *isplays a list of the users to which classified roles are assigned) 2o#ile 'ngine Csers *isplays a list of the users that use mo#ile applications) Procedure =) +n the measurement program (transaction CS22$! choose )ser Data Analysis) >n the E(isting &easurement Data dialog #o/! the system displays a ta#le of the previous measurements performed! with num#er! date! and time of the relevant measurement) The most up8to8date measurement is at the top of the ta#le) &) To remove superfluous data from the classification help! choose Delete) .aution
'nsure that you do not accidentally delete the logs of the measurement that you have transferred to SAP) +f you did so! you would not have any reference material if there are ueries) 'nd of the caution) <) Select the measurement to #e checked! and choose the desired list option on the lassi,ication Help ta# page! such as )ser or+8enc/) Result The results list in each case shows the users with the properties descri#ed in the ta#le a#ove) The user names are specified for internal use in your organi@ation! so that you can investigate these anomalies and! if necessary! reclassify the relevant users) The Work#ench Csers! Professional3Limited Professional Csers! and 2o#ile 'ngine Csers lists are included in anonymi@ed form in #oth the measurement statistics and the measurement log)
+.aluating the Measurement Result
7ou can use the )ser Analysis function to check the results of the system measurement yourself (as of SAP NetWeaver ,)-$) 7ou have the following options for evaluating the measurement result: Cser Analysis 1unctions Function Additional ,otes *isplays a list of users that have #een deleted in the last week! last four weeks! or last twelve *eleted Csers weeks) *isplays a list of users whose validity period e/pired in the last week! last four weeks! or last '/pired Csers twelve weeks #efore the measurement) Logon After *isplays a list of users that have logged on to the system after their validity e/pired '/piration *isplays a list of users for which there were multiple logons to the SAP system during the 2ultiple Logons measurement period) *isplays a list of users that were unusually active in freuently8used ta#les and the name of Bolume of Work the relevant ta#le *isplays a list of users that worked over a two8day period without at least an 6 hour #reak and Working Time the name of the relevant ta#le .ross8.omponent *isplays a list of users that were simultaneously active in different ta#les and the names and Csage the relevant ta#les Procedure =) +n the measurement program (transaction CS22$! choose )ser Data Analysis) >n the E(isting &easurement Data dialog #o/! the system displays a ta#le of the previous measurements performed! with num#er! date! and time of the relevant measurement) The most up8to8date measurement is at the top of the ta#le) &) To remove superfluous data! choose Delete) .aution 'nsure that you do not accidentally delete the logs of the measurement that you have transferred to SAP) +f you did so! you would not have any reference material if there are ueries) 'nd of the caution) <) Select the measurement to #e checked! and choose the desired list option on the )ser Analysis ta# page! such as Deleted )sers) Result The result lists contain the user names for internal use in your organi@ation! so that you can investigate and remove anomalies) The lists are included in anonymi:ed ,orm #oth in the measurement statistics and in the measurement log)
#ransferring Measurement Results
Transfer the measurement results to SAP: +f you are only using one SAP installation! transfer the measurement results directly to SAP) +f you are using multiple SAP installations! first consolidate the measurement results in the License Administration Work#ench) Then send the consolidated result to SAP) Receipt "onfirmation for the Measurement Results 7ou can choose to receive an e8mail confirmation that your measurement results have #een received) To do this! maintain your e8mail address on the Addresses ta# page) As soon as the measurement results are received #y SAP AVJ an e8mail is automatically sent to the stored address) #ransferring Results with S&"" As of SAP We# Application Server ;)=-! you can transfer the measurement results online using the Service *ata .ontrol .enter (S*..$ procedure) 1or previous SAP releases as of SAP 93< 5)- (inclusive$! the S*.. procedure is availa#le through Support Packages (see SAP Note <=5;,&$) Prerequisites At least version &)= of the S*.. is availa#le in your system) 1or releases up to and including SAP 93< 5);! you reuire the authori@ation profile SGS*..GS'9B+) Procedure To transfer the measurement data to SAP online! proceed as follows: =) >n the initial screen of the measurement program (transaction CS22$! choose $rans,er to SAP ) &) .onfirm the prompt) +n the status #ar! the system displays the message that the transfer has #een successfully scheduled) The S*.. session num#er is specified in the long te/t of this message) <) To check the status of your transfer! choose All $rans,ers on the initial screen of the measurement program) The system displays the status of all measurements) The S*.. session num#er of the transfer uniuely identifies the transferred measurement results) This num#er is useful if you need to analy@e a pro#lem) 7ou can perform the pro#lem analysis in S*.. (transaction S*.. or! for releases up to and including SAP 93< 5);.: En"ironment Ser"ice Data ontrol enter $) • •
• •
"hec)ing the #ransfer Status
7ou can use the All $rans,ers function to check the status of the different steps of the system measurement and the data transfer in the measurement program) The staus data is taken directly from the Service *ata .ontrol .enter (S*..$) Prerequisites 7ou have transferred data directly to SAP at least once (see Transferring 2easurement 9esults$) Procedure =) +n the measurement program (transaction CS22$! choose All $rans,ers) The dialog #o/ Status o, t/e $rans,er o, All &easurements appears) +f the status light is green! you can terminate the procedure here! since everything is >") >therwise! perform step &) &) *ou#le8click the S*.. Session num#er of your transfer to call the dialog #o/ SD $rans,er. Details) The following status information is displayed there: Status of the #ackground Fo# o Status of the S*.. transfer! where the first light shows the overall status of data retrieval and o transfer! the second light shows the status of the data retrieval! and the third light shows the status of the transfer) +f all of the status lights are green! you can terminate the procedure here) >therwise! perform step < and3or step 5) <) To analy@e the error status of the #ackground Fo#! choose Jo8Log ) The Fo# overview appears! in which you can select the Fo# and display the corresponding log #y choosing Jo8 Log ) +f you identify an error! correct it! or create a customer message under the component SB8VST8S**) Then perform the transfer again) 5) To analy@e one or more error states of the S*.. transfer! choose SD Log ) The individual steps of the transfer process are displayed in the $rans,er Log ta#le) +f you identify an error in the $e(t column! correct it or create a customer message) Then perform the transfer again) More Information 1or more information a#out checking the data transfer! see SAP Note ;&<&-=)
+.aluation Rules
The following are important for evaluation of measurement results: All chargea#le users (non8chargea#le users are! for e/ample! su#stitute! test! and multi8client users$ and 'ngines in the productive clients of the s ystem) The num#er of AAP Work#ench users in all systems The relevant num#er of these users is therefore the total of AAP Work#ench users in all systems) •
•
Note +f you do not use the License Administration Work#ench to consolidate the users! note the following when classifying users that operate in multiple clients and systems: a user must #e classified only once in the highest group as a chargea#le user in a production system (e/ception: AAP Work#ench users! see #elow$) +n all other systems! this user can then #e classified as a multi8client or multi8system user) Note that AAP Work#ench users in particular are created in multiple systems) 'nd of the note) The measurement program counts defined users and 'ngines and identifies users with developer authori@ation (SS.9 "ey$ in the result) Cnclassified users are counted in production clients with the standard user type of the respective price list (either as operational users or as mySAP)com .at ++3Professional users$! in non8productive clients as test users) .ertain users (such as **+.$ are automatically e/cluded from the measurement (see SAP Note <;-;$) Locked users are counted #y the measurement program) As of SAP 93< 5)-! the measurement program no longer counts users whose validity date has passed) +n the case of earlier releases! the measurement program counts users whose validity date has passed for another 4days after the e/piry date) 1or SAP releases lower than SAP We# Application Server ;)=-: When a user is copied! the user type and special version are not copied) The user is initiali@ed as an operational user or a mySAP)com .at) ++3Professional user! and you must then maintain it manually) •
•
• • •
•
Measurement Results
The measurement program enters the measurement results in a ta#le and the previous results are overwritten) The checks in the measurement program are performed in the #ackground and determine the following information! which is presented in the measurement log: *eleted users Num#er of users that have #een deleted in the last week! last four weeks! or last twelve weeks) Csers with e/pired validity dates Num#er of users whose validity period e/pired in the last week! last four weeks! or last twelve weeks) Num#er of users that have logged on to the system after their validity e/pired Num#er of measured users of the 2o#ile 'ngine 0ighest num#er of a user[s multiple logons to the s ystem List of users #y category Shows the distri#ution of users to the technical user types) Automatically e/cluded! SAP technical users Shows the technical users automatically delivered #y SAP! which are made availa#le free8of8charge 2essage a#out recording the 'ngine measurement >utputs a warning if the recording of the data for time8dependent 'ngine measurements only #egan after the specified measurement period) As of SAP 93< 5);.: Num#er and distri#ution of the users for which a developer key (SS.9 key$ was installed) Num#er of chargea#le o#Fects created #y anonymous and known users As of Support Package =
•
• • • •
•
•
•
•
System information .omments (if any e/ist$ +ncluded .lients '/cluded .lients The results of the included and e/cluded clients are divided into: Cser data 'ngine data Activity checks The activity checks consist of: o 9esults for Work#ench users Num#er of measured users that were recorded as the last user to change source code in the past twelve months 9esults for mo#ile device users o Num#er of measured users of the 2o#ile 'ngine *istri#ution of technical users types o Shows the distri#ution of users to the technical user types Automatically e/cluded SAP technical users o Shows the technical users automatically delivered #y SAP! which are made availa#le free8of8 charge 0ighest num#er of a user[s multiple logons to the system o *eleted users Num#er of users that have #een deleted in the last week! last four weeks! or last twelve weeks Csers with e/pired validity dates o Num#er of users whose validity period e/pired in the last week! last four weeks! or last twelve weeks Num#er of users that have logged on to the system after their validity e/pired o 9esults of the activity checks o Shows the results of the checks: Bolume of Work Working Time .ross8.omponent Csage The results are shown in corresponding value pairs (num#er3ta#le$) 9esults for Professional3Limited Professional users o Num#er of measured users that are classified either as employees or as 'SS users! and that have made changes to ta#les that do not relate to self8services) • • • •
• • • •
7ou have measured the system and can now check the results determined with the client8specific measurement statistics) The results determined (measured users! 'ngines$ are listed #y client in the measurement statistics) &efinition and A.aila!ility of the "ontractual ser #ypes
.lassify your users in accordance with your contractual agreements and their authori@ation and meaning with regard to the underlying pricelist) As of SAP We# AS ;)=-! the user types are listed for each price list on the )ser $ypes ta# page) The user types of the various SAP price lists! and in particular from the mySAP)com price list! are availa#le to you as a Support Package for SAP releases #elow 5); (see SAP Note 5&65,4$) +f you reuire additional mySAP users types for the usiness Suite and the +ndividual Solutions for user classification! which are not yet availa#le in the measurement program for your release status! you can download these individually or together from the SAP Service 2arketplace and install them) http:33service)sap)com3licenseauditing System &easurement Named )ser )ser lassi,ication After discussion with your SAP contact! use the special module user types for the measurement of user types that are not yet part of your measurement program: Specify or overwrite the availa#le special module user types with the appropriate name) Cser the special module user types to clearly classify your users) • •
When measuring mySAP)com users for releases #elow 9elease 5)-! note SAP Note <4&,=! or contact your SAP contact person for system measurement) The assignment of the standard user types depends on the status of the client) The standard user type from the valid price list is assigned to users that have not yet #een classified only in clients with the status Producti"e) The user type $est is assigned as the standard user type to all other users (in clients with other statuses$) The prereuisite for this standard user type assignment: CS22: SAP We# AS ;)&- SP , LAW: SAP We# AS ;)&- SP =4 Plug8+n: as of Bersion 5)-< • • •
Note As of SAP NetWeaver &--5 SPS 6 or SAP NetWeaver ,)- SP4! you can also specify a standard user type for the price list mySAP)com +ndividual Solutions and for any price list com#ination (more information: SAP Note 64;6,&$) 7ou can select this standard user type using the input helpJ all professional user types from the selected price lists are displayed) +f you only select the SW .omponents price list or mySAP)com Solution Suite price list! the standard user type is predefined! and the system shows it in a grayed out input field) 'nd of the note) ser #ypes of the mySAP2com Solution Suite Price List 1or a detailed description and definition of the user types of the mySAP)com Solution Suite and the special user types and e/amples! see the SAP Service 2arketplace) http:33service)sap)com3licenseauditing System &easurement Named )ser )ser lassi,ication mySAP ;usiness Suite As of SAP We# AS ;)&-! users without classification in production systems are counted as mySAP)com .ategory ++3Professional) '/amples of user types of the mySAP)com Solution Suite Special 2odule price list are: mySAP)com .at) ++3Professional mySAP)com .at) +++3Limited Professional mySAP)com .at) +B3'mployee The user types Special 2odule type = to 4 are only permissi#le if corresponding contractual agreements have #een reached with SAP or after discussion with the SAP contact person responsi#le for system measurement) +f these user types are used without contractual agreement! the evaluation rules of the user type mySAP)com .ategory ++3Professional are used) ser #ypes of the mySAP2com Indi.idual Solutions Price List 1or a detailed description and definition of the user types of the mySAP)com +ndividual Solution price list and the special user types and e/amples! see the SAP Service 2arketplace) http:33service)sap)com3licenseauditing System &easurement Named )ser )ser lassi,ication mySAP Solutions <#ndi"idual Solutions= '/amples of user types of the mySAP)com +ndividual Solutions are: mySAP .92 Professional mySAP .92 Limited Professional mySAP 09 Limited Professional mySAP 1inancials Professional mySAP + Professional .lassify all valid users in accordance with your licensed mySAP)com solution) When measuring mySAP)com +ndividual Solutions! there are no standard user types that the s ystem can use for unclassified users) Therefore! an error message is displayed if there are unclassified users) ser #ypes of the SAP Software "omponents Price List 1or a detailed description and definition of the user types of the mySAP)com Software .omponents price list! the SAP New *imension products! and the special user types and e/amples! see the SAP Service 2arketplace) Named )ser http:33service)sap)com3licenseauditing &easurement )ser lassi,ication R>9 Enterprise <#ncl New Dimension= As of SAP We# AS ;)&-! users without classification in production systems are counted as ?perational ) • • •
• • • • •
'/amples of user types for SAP 93< general function #locks are: >perational +nformation *evelopment Work#ench '/amples of user types for SAP New *imension users are: SAP AP>: V)ATP SAP .12: T2 (incl) >P$ Special 2odule and +S user types: Special 2odule type = to 4 +S Cser Type 6= to 6 These user types are only permissi#le if corresponding contractual agreements have #een reached with SAP or after discussion with the SAP contact person responsi#le for system measurement) +f these user types are used without contractual agreement! the evaluation rules of the user type ?perational are used) Special ser #ypes #ype ser #ype Additional ,otes I& .an only #e created in the SAP system for a limited period of time (such as for vacation representation$) *uring this time! this user can use the functions of another user as a -5 Su#stitute su#stitute) This other user must not #e active in the SAP system during this time) Su#stitutes and su#stituted users must #e created in the same client) Since the other user is already evaluated in accordance with its assignment! its su#stitute is free8of8charge) Non8chargea#le user that is used for the users that have already #een classified once as a 2ulti8 chargea#le user in a difference client or system) 'very multi8client3multi8system user that is == .lient3System created in a different client or system must #e assigned to a chargea#le user in the same or a different system and can only use! at most! the same functions as that user) .an only #e created in production systems in the following e/ceptional cases: There are no test systems availa#le) 4= Test The user is #eing used e/clusively to prepare the production use of modules that are not yet productive in the production system) 7ou should agree the classification of test users with SAP) #echnical sers As of SAP NetWeaver ,)=- SP! SAP NetWeaver ,)-- SP=5! SAP We# AS ;)5- SP&&! SAP We# AS ;)&- SP;
• •
• •
• •
• •
• • • • •
SAP states that technical system access #y multiple persons as one defined user is not permissi#le) This also applies for system access #y technical systems and their users) Special *ersions of the ser #ypes
+f you are using special versions within your installation! classify the users with the relevant special version) y default! no special version is assigned to a user) The following special versions e/ist: *ou#le8yte Ara#ic .yrillic Vreek -] surcharge =--] surcharge • • • • • •
"ountry Surcharges for the ser #ypes
As of SAP We# AS ;)&-! the measurement program supports country surcharges) *uring the user classification! you can assign the user either a special version or a country surcharge! depending on the contractual user type: 7ou can only assign a special version to user t ypes of the software components price list) 7ou can only assign a country surcharge to user types of the mySAP)com price list) 7ou can assign either a special version or a country surcharge to user of the special modules! #ut not #oth) • • •
'mployee of the customer! its affiliates! or of a third8party company authori@ed to access! direclty or indirectly! the licensed software! independent of the technical interface chosen) Named users are also technical systems that e/change information with the SAP system! and their users) +ngine >ptional software for which you must purchase an additional! separate license) The licensed units of the 'ngines are determined in accordance with si@es! such as orders! contracts! contract accounts! or patients handled) A license as named users is reuired for users that access 'ngines) SAP Installation
.om#ination of SAP systems! which must #e installed on homogeneous platforms (data#ase! operating system! and hardware$ An SAP installation consists of SAP systems! usually production! test! and training or development systems) A ma/imum of eight production systems can #e operated under one installation) +f you have any additional production systems! you must reuest a new installation from your SAP contracts department) The customer must register a separate installation in writing with SAP for each software product) SAP will then give you a uniue installation num#er)
SAP System
+ncludes all components (application servers! messages servers! that have direct or indirect access to a data#ase instance) 'ach data#ase ta#le occurs only once in a data#ase instance) SS"R Key
SAP Software .hange 9egistration key *eveloper key! which is usually reuired #y users of the AAP Work#ench)
SAP ,otes Rele.ant for System Measurement
List of the SAP Notes ,um!er #itle ,-55=& .CA Support for License *ata 2aintenance ;64==LAW: *ifferences in the 9esults etween CS22 and LAW ;&<&-= System 2easurement Pro#lem Analysis with S*.. *ata Transfer ;--&45 System 2easurement LAW and Standard Cser Types 6=6; System 2easurement: Num#er of Csers in Statistics Truncated ,=,=< System 2easurement: Bariances etween CS22 and LAW <;-; System 2easurement: Automatic '/clusion of Csers <6<4System 2easurement: Standard Cser Type .lient8Specific 5&65,4 System 2easurement: mySAP)com Cser .ategories in 'arlier 9eleases <,;&& System 2easurement: 2ass .hange of Cser .ategories <4&,= Cser classification for mySAP)com users <&,4=, New Cser Types for 9elease 5);. <=5;,& System 2easurement: *ata Transfer #y S*.. <=<6 System 2easurement: Automatically .reated '/ternal Csers &--46System 2easurement: Service Csers and 9eference Csers
License Administration 5or)!ench &efinition The License Administration Work#ench (LAW$ supports you during the License Audit Process for comple/ system landscapes) 7ou use the LAW to collect and consolidate license8relevant measurement data (users and engines$ for the component systems and the central system (LAW system$ in which LAW is run) This provides system administrators with a #etter overview! and the system measurement is simpler and also more relia#le)
efore you start LAW! you should classify the users in all measurement8relevant systems in accordance with their tasksJ that is! assign them to a contractual user type (in transaction CS22! SC-=! or SC=-$) *uring the consolidation that then takes place in LAW! the users for a person are listed and assigned one contractual user type) The multiple assessment of a person is therefore practically eliminated 8 the 2ulti8.lient32ulti8System classification is superfluous) The measurement results are .ollected in the central LAW system and consolidated The consolidation is the automatic analysis and optimi@ation of the individual user types) +t includes the deletion of redundancies and contained contractual user types) Send directly to SAP after release As a result! an anonymous com#ination of the same user types! as displayed in the results log! is transferred) The LAW screen consists of two large su#screens: ontrol LA 7ou can call all steps for user consolidation in order here) As an alternative to step =! you can! as of SAP NetWeaver Y-5! use the functions of the ta# pages to transfer the measurement data) Ta# pages Systems5 #n8o(! 9esult (as of SAP NetWeaver ,)-$! Vroups (as of SAP NetWeaver ,)-$! and &essages (as of SAP NetWeaver Q-5$ >verview of the systems for which data has already #een imported into the LAW or for which you must still transfer data) The significantly e/tended functions for transferring measurement data from the component systems are also availa#le to you here) •
•
•
•
Prerequisites for sing LA5
1or you to #e a#le to use the License Administration Work#ench (LAW$! the prereuisites listed #elow must #e fulfilled) 7ou must also have authori@ation for authori@ation o#Fect SGCS'9GV9P! A.TBT H -< (*isplay$! and for transferring the results! you also reuire the authori@ations S*..G*'B H 9'A* and S*..G9CN H 9'A*! W9+T' for the o#Fect SGS*..) LA5 System 7ou have defined a system as the central system) This LAW system has at least SAP release 5);.) The transaction L+.'NS'GA*2+N or SLAW e/ists in the LAW system) As of SAP We# AS ;)=-! transaction L+.'NS'GA*2+N is included in the standard SAP system) As of SAP NetWeaver Y-5! transaction SLAW is also included in the standard SAP system) 1or older SAP releases! the transactions are availa#le through Support Packages) Additional information is availa#le in the SAP Service 2arketplace under http:33service)sap)com3licenseauditing License Administration or+8enc/ ) "omponent Systems The component systems have a release status of at least SAP release <)=+) The report 9SLAWGPLCV+N e/ists in the component systems to collect the measurement data) The report 9SLAWGPLCV+N is the plug8in for the License Administration Work#ench and #uilds the interfaces #etween the LAW central system and the connected component systems) +t is essentially used for formatting the measurement results and transferring them from the component system to the LAW) As of SAP NetWeaver Y-5! it is also used as a type of 91. module for communication #etween remote systems) To use the new functions of the LAW (;)5-$! and the future corrections for older release statuses! use SAP Note ,;;6&& to migrate report 9SLAWGPLCV+N for the releases in which it already e/ists (5);.! 5);*! ;)=-! and ;)&-$) 1or releases <)=! 5)-! 5)! and 5);! in which the report did not previously e/ist! you can use SAP Note ,,,=;< to create the program o#Fect) All current and future corrections for the plug8in are #ased on these two SAP Notes) Alternatively! you can continue to use program o#Fects in the customer namespace) 0owever! we no longer recommend this) ser &ata The user master records need a uniform criterion! such as the same user +*! the same e8mail address! or the same telephone num#er) A.aila!ility of the &ata to 'e +.aluated 7ou have determined the measurement8relevant data for the component systems and the LAW systems as follows: • •
• •
=)
7ou have classified the user master records in every relevant system in accordance with the activities of the users in the system) *o not use any multi8client3multi8system users (+*==$ when doing so) &) 7ou have run the system measurement (transaction CS22$ in every measurement8relevant system) 1or information a#out system measurement with transaction CS22! see the SAP Li#rary under System 2easurement)
"ollecting Measurement &ata in the "omponent System
7ou can either collect the measurement results directly in each component system and Save it in a local file! which you load from the central system (see Loading System *ata from a 1ile$ Send the data to the central system #y 9emote 1unction .all Alternatively! you can perform only the first two steps of this procedure! and then start the report not directly in the component system! #ut rather from the central system (see Starting 9emote Actions in the .omponent System $) Procedure =) Start report 9SLAWGPLCV+N #y choosing System &easurement E(port to LA @ile or start the corresponding report that you have created (using transaction SA<6$) &) To transfer the data #y 9emote 1unction .all (91.$! you must first maintain the 91. destination of the LAW central system) To do this! select &aintain R@ Destination ,or LA entral System! and choose E(ecute) A dialog window on which you enter the name of the 91. destination appears) <) .hoose the type of the data transfer and then E(ecute) 7ou have the following options: y download to a file o Save the measurement data to a local file! which you specify in the following dialog #o/) y '8mail to an address o Allows you to send the measurement data to one or more e8mail addresses! if the system is connected to an e8mail server) y 91. to the LAW central system o Sends the measurement data to the central system) 7ou can choose whether you send the data # y 91. or 91.) y function module o Allows you to specify your own function module for postprocessing the measurement data) 1or more information! see the documentation in the program 9SLAWGPLCV+N (+ #utton$) Schedule a #ackground Fo# for license measurement and to transfer the data to the LAW) o Result 7ou have collected the license8relevant data from the component system and can perform the ne/t step! which depends on which option you have chosen: .om#ining the 2easurement *ata in the LAW! if you want to transfer the data to the LAW #y 91. Loading System *ata from a 1ile! if you saved the data to a local file • •
• •
1.er.iew of the LA5 Procedures
To consolidate the measurement results with the License Administration Work#ench (LAW$! you must perform the steps #elow in the order in which they are listed) Process After you have performed the system measurement in the component systems and in the LAW system! you can evaluate and consolidate the measurement data centrally in the LAW) =) 7ou com#ine the measurement data of all component s ystems and of the central system in the License Administration Work#ench &) 7ou com#ine the users and can then check the user list) <) 7ou manually correct and amend the com#ined users) 5) 7ou consolidate the data and can check the results using the result list and the 9esult ta# page) ) +f necessary! you correct the user classification of the users if necessary in the original system) ;) 7ou transfer the consolidated data to SAP and can then check the list of all transfers) ,) 7ou can utili@e the LAW data for additional internal uses with AP+s (see LAW +nterface$)
6)
7ou group the systems! so that you can perform partial consolidations later)
"om!ining the Measurement &ata in the LA5
7ou have the following options for transferring the data of the component systems and of the central system to the License Administration Work#ench: 7ou load the data for each component system from a local file (see Loading System *ata from a 1ile$ and transfer the central system[s data with the LA System Data function in step =) 7ou transfer the measurement data of the component systems and of the central system #y 9emote 1unction .all (see Transferring 2easurement *ata to the LAW #y 91.$) Significantly e/tended functions for transferring data from the systems are availa#le to you) 7ou can also import data for non8SAP systems in your system landscape into the LAW) •
•
Loading System &ata from a File Procedure 7ou import the measurement files of the component systems and the data of the LAW system into the License Administration Work#ench (LAW$ as follows: =) .all the License Administration Work#ench (transaction SLAW or L+.'NS'GA*2+N$) &) To import the files with the measurement data for the component systems! choose the option omponent System Data in the ontrol LA #o/) <) To import the measurement data for the LAW system! choose the LA System Data option in the ontrol LA #o/) Result The data of the systems relevant for the measurement is displayed on the Systems ta# page in the &easurement Results view) 1or more detailed information a#out a system! dou#le8click the corresponding line) +n the ne/t step! you com#ine the users)
Loading System &ata for a ,on%SAP System from a File
+f you have non8SAP systems in your system landscape from which the users use the SAP system indirectly through interfaces (for e/ample! with an 91. user$! you can also use the LAW as the central measurement system for these systems) To do this! collect the data reuired #y the LAW in a .haracter Separated Balues file (.SB file! see Prereuisites$) As of SAP We# AS ;)5-! use report 9SLAWG+2P>9TG'T'9NALG*ATA to convert into a S+* file that can #e read #y the LAW and then automatically load it into the LAW) 1or releases 5);. and SAP We# AS ;)&-! the report 9SLAWG.>NB'9TG'T'9NALG*ATA is availa#le #y Support Package) This report generates a S+* file) 7ou can then load the file into the LAW #y choosing &easurement Data #mport Data @rom an E(ternal System ) Prerequisites The .SB file is a te/t file that contains data structured as a ta#le and primarily used for data e/change) The individual values are separated #y a special separator (in this case! a ta#$) There is no official standard for the file format) Note +f you create the file with 2icrosoft '/cel! you must ensure that you use the correct date format) 7ou may have to define your own format) 'nd of the note) The individual fields of the .SB file have the following format and must #e separated #y a ta#: Cser name (.0A9=&$: 9euired field that must #e correctly filled) +f it is empty or incorrectly filled! you receive an error message) Cser type (.0A9&$: +f this field is empty! the report fills it with a default value! which you need to enter using the selection screen of the report) '8mail address (.0A9&5=$ •
•
•
1irst name (.0A9<-$ Last name (.0A9<-$ Last logon date (777722**$: +f you enter an incorrect date! you receive an error message) .reation date (777722**$: +f you enter an incorrect date! you receive an error message) .ost center (.0A96$ Telephone num#er (.0A9=;$ Name = (.0A9&-$ Balue = (.0A9=&6$ Name & (.0A9&-$ Balue & (.0A9=&6$ Name < (.0A9&-$ Balue < (.0A9=&6$ Name 5 (.0A9&-$ Balue 5 (.0A9=&6$ Name (.0A9&-$ Balue (.0A9=&6$ All fields other than the user name field are optional and can #e replaced #y a ta#! unless the values are reuired later for grouping users) The name8value pairs at the end of the list are personali@ation data! which is availa#le to you for additional information (which you can also use for grouping$) 2issing user types are filled with a default value when the report is run) 7ou must enter this default value on the report[s selection screen) A correct system measurement file also contains the following data! which is automatically added! since it is constant) Name: Balue 0ardware key ---------+nstallation num#er 'TS7ST'2S System status P9>* .lient --.ategory of the client P 9elease .urrent system release Selection System +* Cniue system num#er *escription *ate of the measurement (**227777$ Time of the measurement (0022SS$ Name of the user who performed the measurement *efault user type Cser types not permitted Pricelist selection Path specification of the upload file 1ields marked with an asterisk ($ are reuired entry fields) +nput help is availa#le to ensure the specification of a correct data and a correct time! the entry of the user type! and the e/act path specification) The system also checks whether the user type and the selected pricelist(s$ match) 7ou can also e/clude user types from use) • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • •
'/ample '/ample of a .SB 1ile This representation contains a header line that must not #e included in the file) CNA2' CT7P' '2A+L 1NA2' LNA2' LL>V+N .*AT' .>ST.N T'LN> *'&;<= ,& helga)muster^firma)com 0elga 2ustermann &--5-=-= &--&-<-< P'9S- 2'+'9 & 0orst 2eier &--5-6-6 &--=-=-= P'9S-< 'nd of the e/ample) Procedure
=)
To convert the .SB file and to import the generated S+* file into the LAW! choose the following path in transaction L+.'NS'GA*2+N (SLAW$: &easurement Data #mport Data @rom E(ternal System 'nter the necessary data) Select the relevant pricelists) To display the generated ta#le! select this option)
)
&) <) 5) Result 7ou can optionally display the ta#le generated in S+* format) The data is then automatically transferred to the LAW (either directly or into the +n#o/$) +f the .SB file contains errors! a detailed error log appears) +n this case! the transfer does not take place)
#ransferring Measurement &ata to the LA5 !y RF"
7ou have the following options for transferring measurement data to the LAW central system #y 9emote 1unction .all (91.$: Start the measurement in the component system and transfer the data with the report 9SLAWGPLCV+N (see .ollecting 2easurement *ata in the .omponent System$) Start the measurement in the component system from the central system) 7ou then transfer the measurement data to the central system #y 9emote 1unction .all (see .ollecting 2easurement *ata in the .omponent System$ or initiate its transfer from the central s ystem (see Starting 9emote Actions in the .omponent System$) •
•
Note To ensure data protection! the LAW triggers only the reuest for the data to #e sent #y 9emote 1unction .all) The component system then creates a separate 91. connection to the configured LAW central system for the data transfer) 'nd of the note) Prerequisites The report 9SLAWGPLCV+N (version )- or higher$ e/ists in the LAW central system and the component systems) There is a functioning 91. infrastructure #etween the LAW central system and the component system) +f they e/ist! you can use the 91. destinations of the SAP Solution 2anager for this purpose) 7ou have made the 91. destination for the LAW central system known in the component system (see .ollecting 2easurement *ata in the .omponent System$) To load the system data from a file! you must have received the LAW electronic measurement plan from SAP #y e8mail) This contains the system data (system num#er! installation num#er! hardware key! system +*$) The LAW measurement plan is the #asis of every consolidated measurement and is provided #y License Auditing Services) Alternatively! you can also enter the measurement plan manually in e/ceptional cases) Procedure =) Load the LAW measurement plan! and maintain the 91. destinations of your components systems and of the central system! as descri#ed in 'ntering .omponent Systems) &) Start the measurement in the component systems and in the central system! as descri#ed in Starting 9emote Actions in the .omponent System) <) To transfer the measurement data to the LAW central system! select the systems with the status new on the #n8o( ta# page! for which you want to transfer measurement data! and choose $rans,er &easurement
•
•
•
Note The use of the in#o/ is optional! #ut recommended) +f you do not use the +n#o/! the data is directly transferred) +f you do not want to use the in#o/ generally! choose )tilities lo8al Settings ! and select the option Do Not )se #n8o() The #n8o( ta# page is no longer displayed as of this point! and the incoming measurement data is
transferred directly to the LAW) *ata that already e/ists for the same component system is replaced without a uery in this case) 'nd of the note) 5) >n the &essages ta# page! you can display a log for all actions! to #e a#le to react to possi#le errors) The functions of the application log are availa#le to you here! in particular the #utton New Selection) 7ou can use it to specify the period for which the log entries are to #e displayed) Result The data of the systems relevant for the measurement is displayed on the Systems ta# page in the &easurement Results view) 1or more information a#out a system! dou#le click the corresponding line) +n the ne/t step! you com#ine the users)
"opying RF" &estinations of the SAP Solution Manager =2>
7ou can copy the 91. destinations from the system landscape of the SAP Solution 2anager into LAW and reuse them) Prerequisites 7ou have configured the System Landscape of the Solution 2anager ) Procedure =) Switch to the Systems ta# page in the &aintain R@ Data view of transaction SLAW) &) .hoose Add R@ Destinations) The $rans,er R@ Destinations ,rom Solution &anager screen appears) +f this function is not displayed! no system landscape has #een maintained! or there is no Solution 2anager on this system) <) Select the 91. destinations for the component systems to #e copied) 'nsure that only one 91. destination is selected for each system: +f there is e/actly one destination for each component system! you can copy these in one step) o +f multiple destinations e/ist! you need to select e/actly one to #e copied) To do this! select the o relevant check#o/) +f the tree display of the systems and their destinations is displayed! all destinations that can pro#a#ly #e used are selected (check#o/es$) +f individual systems are already assigned a destination! these are specified and highlighted in color) The program uses the assigned icons to indicate the status of the individual systems and destinations (the uick info provides details$) The destinations for a system are only displayed (e/panded$ if there are pro#lems or if the assignment is not uniue) +f there is a long te/t for a message! the message is displayed as a link) 5) .hoose Sa"e Destinations to copy the selected 91. destinations and! if applica#le! overwrite the e/isting destinations) Note Any communication errors that are displayed might only #e temporary) 7ou can therefore always copy all destinations without restrictions) 'nd of the note) ) 7ou can check the usa#ility of the selected destinations #y choosing /ec+ Destinations) When you do so! the program first creates a connection to the component system) +f the connection is successfully created! the program then checks the authori@ations reuired for the LAW in the component system) The authori@ation check is optional) 0owever! it does reuire authori@ation for the function group SCS9) +f this authori@ation is missing! the communication user has not #een assigned the role SAPG.GLAWG.>22CN+.AT+>N or the profile SGLAWG.>22) Note o
o
+f you miss out the check step! the system displays a warning message when you save the destinations) To repeat a check! you first need to reset the check results #y choosing Delete /ec+ Results! since the program records which destinations it has already checked)
'nd of the note) ;) +f the program identifies pro#lems during the data collection or a check! it records this in a log) 7ou can call this log #y choosing Display Log )
Result 7ou have copied the 91. destinations of the SAP Solution 2anager)
+ntering "omponent Systems
7ou can either load the data for the component systems from a file or! in e/ceptional cases! include it manually) Procedure 5ith an +lectronic LA5 Measurement Plan =) Start the License Administration Work#ench) &) Switch to the Systems ta# page in the &aintain R@ Data view) <) To load the system data from the file! choose Load &easurement Plan) A dialog #o/ appears! in which you specify the local file to #e loaded) All system data of your component s ystems to #e measured and the central system are displayed in the LAW in this way) +f system data! that is! an old LAW measurement plan! already e/ists! the LAW compares the plans and copies the manually added data! such as the 91. destination) 0owever! it does not delete any component systems when doing so) 7ou must always perform the deletion manually) Note +f you accidentally loaded a file other than the LAW measurement plan and destroyed the display #y doing so! switch the view wit/out sa"ing or restart the transaction) 'nd of the note) 5) Add the name of the R@ Destination for each system! and! if necessary! replace the default name of the report 9SLAWGPLCV+N with the actual report name used in the relevant system) 7ou can specify the 91. destination N?NE for the central system) Note Perform a function! such as Re,res/! after the input so that your data can #e transferred and checked) The status display of the traffic lights has the following meaning in this view: Vray: No data has yet #een maintained) o 7ellow: *ata has #een maintained! #ut not yet checked) o Vreen: The data has #een successfully checked) o 9ed: 'rrors occurred when checking the data) o 'nd of the note) =) To compare the system identification data with the data from the component systems! and to fetch and add missing data (release and system status$! select all systems and choose /ec+ System ?"er"iew 8y R@ ) +f the function could not #e e/ecuted or inconsistencies were found (for system num#er! installation num#er! and so on$! the traffic light is red! and an icon is displayed in the #n,o column! with which you can display more detailed information) 7ou must manually clean inconsistencies displayed with a red traffic light: =) *elete the relevant line! and choose Add New System) &) 'nter the correct data in the following dialog #o/) +f the checks ran successfully! the traffic lights are green) &) Save the system overview) 5ithout an +lectronic LA5 Measurement Plan +f you need to e/tend the electronic LAW measurement plan! perform the following steps for each system to #e added: =) Cse the function Add New System to enter the data for each individual system) +f you do not specify a system num#er! the LAW assigns a temporary system num#er) &) To compare the system identification data with the data from the component system! and to fetch and add missing data (release and system status$! select the systems and choose /ec+ System ?"er"iew 8y R@ ) The prereuisite for this is that you have set up the 91. connections) +f the function could not #e e/ecuted or inconsistencies were found (for system num#er! installation num#er! and so on$! the traffic light is red! and an icon is displayed in the #n,o column! with which you can display more detailed information) 7ou must manually clean inconsistencies displayed with a red traffic light: =) *elete the relevant line! and choose Add New System) &) 'nter the correct data in the following dialog #o/)
+f the checks ran successfully! the traffic lights are green) <) Save the system overview)
Starting Remote Actions in the "omponent System Procedure =) Start the License Administration Work#ench (transaction SLAW$) &) Switch to the Systems ta# page in the Remote Actions ta# page)
Note The status display of the traffic lights is independent of the status display in the &aintain R@ Data view and has the following meaning: Vray: No action has yet #een started) o 7ellow: An action has started! #ut not yet finished) o Vreen: The last action was successfully e/ecuted) o 9ed: The last action was not successfully e/ecuted) o +f the status is red! there is an icon in the #n,o column! with which you can display the associated error te/t) 'nd of the note) <) Select the component system to #e measured and choose under 2easurement Tools! select! for e/ample! the action Start and $rans,er &easurement ) Note 7ou can only start one action for each component s ystem) +f you start a new action #efore an action is completed! the system displays a warning) +f you ignore this warning! the new action replaces the previous action) +f a response is still received from the component system for the previous action! it is ignored) That is! it does not change the status! although measurement data that still arrives may #e saved in the in#o/) 'nd of the note) Possi#le Actions in the .omponent System Action Additional ,otes Starts the measurement on the component system! waits for the end of the measurement! and transfers the measurement results to the LAW central system) The results are availa#le on the Start and Transfer +n#o/ ta# page 2easurement Note: This function is always started asynchronously and is not availa#le in component systems with SAP release <)=) Start 2easurement Starts the measurement on the component system) This corresponds to the measurement with >nly the local transaction CS22) +nstructs the component system to transfer the most recent availa#le measurement to the LAW Transfer Last central system) This corresponds to the sending of a measurement #y 91. with the report 2easurement 9SLAWGPLCV+N) .hecks the 91. infrastructure) 91. communication to the component system is created for this Test .onnection test! which in turn creates an 91. communication #ack to the LAW central system) ranches to the 91. monitor) The status of the asynchronous 91. reuests is displayed there! 91. Analysis and you can analy@e possi#le pro#lems) All remote actions! with the e/ception of the function /ec+ System ?"er"iew 8y R@ ! are performed asynchronously as 91.) ranches to the t91. monitor) The status of the transactional 91. reuests is displayed there! t91. Analysis and you can analy@e possi#le pro#lems)
&eleting a "omponent System or Measurement &ata from the LA5
+n the LAW! you can either completely delete one or more component systems from the overview! or delete only the measurement data of these systems) Prerequisites
7ou have already entered the data for the component systems or transferred the measurement data to the LAW) Procedure &eleting a "omponent System =) Start the License Administration Work#ench (transaction SLAW$) &) >n the Systems ta# page! choose the Delete Systems function in the &aintain R@ Data view or Remote Actions view) <) Select the systems to #e deleted) The selected systems are removed from the LAW central system with all of their data) &eleting 1nly Measurement &ata =) Start the License Administration Work#ench (transaction SLAW$) &) .hoose the Systems ta# page in the &easurement Results overview) <) Select the systems for which you want to delete data) 5) .hoose the Delete &easurements function) The measurement data for all selected systems is deleted from the LAW central system) Note >n the #n8o( ta# page! the Delete &easurements function means only that the measurement data that has not yet #een transferred into the LAW is deleted from the in#o/)
"om!ining sers
7ou can com#ine multiple user master records for the same employee with this procedure) Note The criteria for com#ination originate from the user maintenance (transaction SC-=$ of the source system) 7ou can e/tend these criteria if necessary (see '/tended Vrouping of Csers$) 'nd of the note) Procedure "om!ining sers =) .all the License Administration Work#ench (transaction SLAW or L+.'NS'GA*2+N$) &) +n the ontrol LA #o/! choose the om8ine )sers option) The system displays the om8ine t/e )sers dialog #o/) <) +n the dialog #o/! choose whether you want to com#ine your users automatically or manually) 9ecommendation We recommend that you first automatically com#ine the users and then! if necessary! manually correct or amend the com#ined users) A manual correction is reuired if! for e/ample! different spellings of the user name are used in different systems (for e/ample! in system A enita 0artmann! and in system 0artmann! enita or 0A9T2ANN$) .hoose the grouping criterion or criteria that #est suit your situation! such as the criterion )ser Name! if your users have the same user names in all systems) (+f you are using .entral Cser Administration! this is automatically the case)$ 'nd of the recommendation) Automatic com#ination #y the following criteria: o Cser name Last name! first name Account Num#er 'mail Address Telephone Num#er The system displays the message )sers success,ully com8ined in the status line) 2anual com#ination: o The system displays the om8ine )sers &anually screen) *epending on whether you have imported new users from new systems into the LAW! choose one of the following options when filling out this selection screen:
7ou have not imported any users from new systems into the LAW) 7ou therefore do not need to make any entries on this screen! #ut should choose E(ecute immediately! to com#ine all imported systems automatically) 7ou have Fust imported the data for a new system into the LAW and had earlier already automatically com#ined the data for the previous systems) 7ou must now automatically com#ine the users of the new system #y the same criteria) To do this! set the indicator automatically assign 8y on the om8ine )sers &anually screen! and choose the criteria for the com#ination) Then choose E(ecute) +n #oth cases! the screen om8ine )sers &anually appears) Select all user master records of an employee) .hoose roup Selected ) After you have com#ined all user master records for an employee! you can specify the contractual user t ype to #e licensed (see .onsolidating .ontractual Cser Types$) &isplay ser "om!ination To check the com#ination of the users! choose the Display )ser List option in the ontrol LA #o/) The user list provides the following information a#out the user and the systems in which it is created: *etails for user: Cser name (+*$ o Last name! first name o .ontractual user type o Account num#er o .ontractual special version surcharge o .ountry surcharge (as of SAP We# AS ;)&-$ o .reation date of the user o *ate of the last logon o '8mail address o Telephone num#er o .ost center o .ategory (Productive! Test$ o .lassification (2anual! 9eference! and so on$ o Work#ench user o *etails for personali@ation o#Fects (as of SAP NetWeaver ,)-$ Name of personali@ation o#Fect = (if it e/ists$ o Name of personali@ation o#Fect & (if it e/ists$ o o Name of personali@ation o#Fect < (if it e/ists$ Name of personali@ation o#Fect 5 (if it e/ists$ o Name of personali@ation o#Fect (if it e/ists$ o *etails for system: +nstallation num#er o System Name o 0ardware "ey o .lient o System Num#er o The LAW data is availa#le to you for internal! automated processing through the LAW interface (see LAW +nterface$) 1or internal processing! you can make a detailed selection of the LAW data in the LAW system: As of SAP We# AS ;)&-! SP5&! using report 9SLAWGT'STGAP+ As of SAP NetWeaver &--5 in the LAW! #y choosing oto #n,ormation Systems "orrecting the ser Summary To correct errors that you have found when checking the user list: =) 9epeat the com#ination of the users and choose &anual om8ination) +f you previously com#ined the users automatically! the results of this com#ination are automatically displayed) &) 7ou can revise the old result)
•
•
•
• •
Result 7ou have com#ined the users and can consolidate the contractual user types in the ne/t step) +$tended
7ou can e/tend the e/isting criteria for com#ining users to then group the users as follows: y more than one criterion! such as Name and Telephone Num#er y personali@ation o#Fects y a com#ination of #oth 7ou can implement your individual user groupings with personali@ation o#Fects! which are availa#le as of SAP 93< 5);.) 1or more information a#out how to use personali@ation o#Fects! see Csing Personali@ation >#Fects in the LAW) When grouping! grouping fields are only displayed if personali@ation data e/ists in the LAW) The num#er of these fields corresponds to the num#er of different personali@ation o#Fects! #ut is restricted to a ma/imum of five) • • •
.aution +f you are using personali@ation o#Fects! these must #e maintained in all systems and for all users) >therwise! grouping will #e incomplete) '/tended grouping! especially with personali@ation o#Fects! is significantly more e/pensive and time8consuming) 7ou should therefore only use the e/tended grouping if you a#solutely reuire it! for e/ample! if you are only consolidating using more than one criterion) sing Personali?ation 1!@ects in the LA5
7ou can use personali@ation o#Fects! which have #een availa#le since SAP release 5);.! to assign completely individual information to an SAP user) These personali@ation o#Fects are also availa#le through SAP Note 6<6,<;) 7ou can either maintain personali@ation o#Fects manually in user maintenance or automatically using the AAP class interface .LGP'9SGA*2+N) To #e a#le to assign special personali@ation o#Fects to the users! you must register the associated data structure with transaction P'9S9'V once) As of SAP NetWeaver Y-5! the LAW can assign personali@ation o#Fects to the SAP users to #e grouped and further process the personali@ation o#Fects) The **+. ta#le structure LAWGTGP'9S and the associated row structure LAWGSGP'9S used #y the LAW already e/ist in this release) The personali@ation o#Fect LAWGP'9S is also already registered) +n user maintenance! the following entry is in the ta#le of e/isting personali@ation o#Fects on the Personali:ation ta# page: Personali@ation o#Fect for license administration LAWGP'9S *ou#le8click this entry to start the display or maintenance) To use personali@ation o#Fects for LAW consolidation in general! you must create these structures and register the personali@ation o#Fect LAWGP'9S in all component systems with older releases) Since you must do this in the customer namespace! the original names must #e renamed) Process =) +n the AAP *ictionary! create the following o#Fects in succession! each with the relevant values listed #elow (see also .reating a *ata 'lement$: =) *ata type LAWGP'9SGBA9 as LAWGP'9SGBA9 rief *escription LAW: Name of a personali@ation varia#le *omain: .0A9&1ield *escription: Name of the Baria#le &) *ata type LAWGP'9SGBAL as LAWGP'9SGBAL Short description: LAW: Balue of a personali@ation varia#le *omain: T'T=&6 1ield *escription: Balue <) 9ow structure LAWGSGP'9S! for e/ample! as LAWGSGP'9S Short description: LAW: 9ow of a personali@ation varia#le .omponent: .omponent type NA2': LAWGP'9SGBA9 BALC': LAWGP'9SGBAL
.aution 7ou must not change the component names) 'nd of the caution) 5) Ta#le type LAWGTGP'9S! for e/ample! as LAWGTGP'9S Short description: LAW: Personali@ation o#Fect 9ow Type: LAWGSGP'9S &) 9egister the personali@ation o#Fect LAWGP'9S! for e/ample as LAWGP'9S! with transaction P'9S9'V (see 9egistering Personali@ation >#Fects$) The appearance of the transaction is different in release 5);. from older releases) 9elease 5);. The system may display the following warnings! which you can ignore: M.ross8client ta#le or M*o not make any changes (SAP data$) =) .hoose New Entries) &) 'nter the following data! and set the following indicators: "ey: LAWGP'9S *escription: Personali@ation o#Fect for license administration Standard repository: (set indicator$ 12 for *ialog: LAWGP'9SG*+AL>V (more information: SAP Note ,&=;45$ Access via user maintenance: (set indicator$ Bisi#le in user maintenance: (set indicator$ SAP We# Application Server ;)=- and ;)&<) .hoose reate) 5) Specify the value of the key as LAWGP'9S) ) >n the ne/t screen! enter the following data! and set the following indicators: *escription: Personali@ation o#Fect for license administration Veneric 9epository: (set indicator$ *ialog 1unction 2odule: SP'9SGSTAN*A9*G*+AL>V Take into account when user changed: (set indicator$ Bisi#le in user maintenance: (set indicator$ Type name: LAWGTGP'9S 7ou do not need to specify an application component and can ignore the warning MApplication component is not active) <) AdFust the LAW plug8in (report 9SLAWGPLCV+N$ to the registered name! such as LAWGP'9S! in the AAP 'ditor)
Synta/ =) &) <) 5) ) ;) ,) 6) 4)
8888888888888888888888888888888888888888888888888888888888888888888888 "ey of the LAW personali@ation o#Fect This key has to #e adFusted when using the plugin in a release lower than ;)5-) Cse the name that was registered using transaction P'9S9'V)
*ATA: gGpersGkey T7P' tyGspersGo#F8persGkey BALC' QLAWGP'9SQ) 8888888888888888888888888888888888888888888888888888888888888888888888
Maintaining Personali?ation 1!@ects Manually Procedure =) +n change mode in the user maintenance (transaction SC-=$! specify the name of the user for which you want to maintain a personali@ation o#Fect) &) .hoose the Personali:ation ta# page) <) Select the row Personali:ation ,or License Administration #y dou#le8clicking it) The Edit Personali:ation Data dialog #o/ appears)
5)
+n the Name o, t/e 0aria8les field! enter! for e/ample! P'9SNC2'9! and in the 0alue field! the personnel num#er of the user) ) Save your entries)
Maintaining Personali?ation 1!@ects Automatically 7ou can also create! change! and delete personali@ation o#Fects automatically) The AAP8>> class .LGP'9SGA*2+N and its methods are availa#le to you for this purpose) +n the following e/ample! a personnel num#er is assigned to every SAP user)
Synta/ =) T7P'S: 'V+N >1 tyGuser! &) #name T7P' usr-&8#name! <) persnum#er T7P' )))))! 5) 'N* >1 tyGuser) ) .>NSTANTS: gcGpersGkey T7P' spersGkey BALC' QLAWGP'9SQ ;) *ATA: gtGusers T7P' TAL' >1 tyGuser) ,) *ATA: gsGuser T7P' tyGuser) 6) *ATA: gtGlawGpers T7P' lawGtGpers) 4) *ATA: gsGlawGpers T7P' lawGsGpers) =-) ==) uild ta#le gtGusers =&) )))))) =<) =5) L>>P AT gtGusers +NT> gsGuser) =) .L'A9 gtGlawGpers_`) =;) gsGlawGpers8name H QP'9SNC2'9Q) =,) gsGlawGpers8value H gsGuser8persnum#er) =6) APP'N* gsGlawGpers T> gtGlawGpers) =4) &-) set data &=) .ALL 2'T0>* clGpersGadminHsetGdata &&) 'P>9T+NV &<) pGpersGkey H gcGpersGkey &5) pGuname H gsGuser8#name &) pGpersGdata H gtGlawGpers &;) pGappend H QQ &,) pGmodify H QQ &6) pGwriteGthrough H QQ &4) '.'PT+>NS <-) persGkeyGnotGfound H = <=) dataGtypeGerror H & <&) userGdoesGnotGe/ist H < <<) others H 5) <5) .AS' sy8su#rc) <) W0'N -) <;) A** = T> gGnum#erGok) <,) W0'N = >9 &) <6) 2'SSAV' ))) <4) '+T) 5-) W0'N <) 5=) A** = T> gGuserGerror) 5&) 'N*.AS') 5<) 'N*L>>P) 'nd of the code) For more information, refer also to:
'/ample program 9SLAWGS'TGP'9SG*ATA)
7ou can use consolidation groups to consolidate #y groups of systems within a LAW) 1or e/ample! you can evaluate #y parts of the company or similar structures) Prerequisites The roups ta# page appears! since the option onsolidation in roups Possi8le is activated under )tilities Settings ) Procedure =) .reate the desired group) =) Switch to change mode) &) .reate a new empty line #y choosing #nsert Line) <) 'nter a uniue group name and a short description of the group in the new line) 5) To save the groups permanently! first choose a grid function! such as Re,res/ and then Sa"e roup De,inition) &) Assign the systems to the groups) =) Select the relevant line and choose Assign Systems to a roup) A dialog #o/ with two lists appears) The left list is empty to #egin with and later contains all systems that #elong to the group) The right list initially contains all systems that currently e/ist in the ALWJ #ut which are not yet assigned to this group) &) To transfer systems to the group! select the desired systems in the list on the right! and choose opy Selection Systems) 7ou can also select s ystems in the left list and remove them from the group #y choosing Remo"e Selected Systems) Note 7ou can use the filter function a#ove the list to presort the right column after installation and then assign all systems in the installation to the group #y choosing opy All Systems) 'nd of the note) <) >nce all desired systems are in the list on the left! save the group assignment #y choosing Sa"e) 5) .onfirm the message a#out the system assignment) <) .hoose the group(s$ for the consolidation) =) +n change mode! select one or more groups for which a partial consolidation is to #e performed #y checking the groups in the column $a+e #nto Account During onsolidation ) &) To save consolidation settings! first choose a grid function and then Sa"e roup De,inition) Result 7ou can now return to the Systems ta8 page and start the partial consolidation in the conte/t of the ontrol o, t/e LA )
"onsolidating "ontractual ser #ypes
With this procedure! you consolidate the contractual user types of the individual users) The LAW takes account of the fact that certain contractual user types are already contained in others) +n this way! license costs are only incurred for the inclusive user types of the user) Procedure =) .all the License Administration Work#ench (transaction SLAW or L+.'NS'GA*2+N$) &) To start the consolidation! choose the Start onsolidation option in the ontrol LA #o/) A dialog #o/ appears where you can choose whether to schedule consolidation as a #ackground Fo#) Note +f you consolidate only a few groups instead of all LAW data! the status light is yellow)
+f you receive the message No consolidation groups were determined Per,orm t/e ,unction anyway! you can either specify one or more groups to #e consolidated on the roups ta# page! or choose ontinue to consolidate all data in the LAW) +f you receive the message ountry surc/arges and special "ersions must 8e t/e same in all systems! correct the user classification and restart the consolidation) 'nd of the note) <) .hoose Display Results) The Result o, t/e )ser onsolidation screen appears) 7ou can display the following lists of consolidated results #y choosing /ange Display) .onsolidated Csers: 'rrors: List of the consolidation errors in which only the consolidation groups o that could not #e consolidated are displayed) 7ou can select this list as the default list #y choosing )tilities Settings and then the option ?nly Display Errors in onsolidation List ) .onsolidated Csers: .ompressed list that shows only one line for each group) This list is the o default list in the delivered system) Vrouped Csers: .omplete list with all users o 5) y dou#le8clicking a line! you can display a detailed list of the relevant group) This detailed list contains all attri#utes for the individual users of this group) Result The consolidated results are displayed for each user) The Status column specifies whether the contractual user types of the users are consistent: +f the light is green! the contractual user types of the user are consistent) +f the light is red! the contractual user types of the user are inconsistentJ that is! special versions and country surcharges do not match in all systems) As you can only transfer results with consistent contractual user types to SAP! correct the user classification) • •
'/ample The user is! for e/ample! classified as operational without special version and as +nformation Cser with special version *ou#le yte) 'nd of the e/ample) The LAW data is availa#le to you for internal! automated processing through the LAW interface (see LAW +nterface$) 1or internal processing! you can make a detailed selection of the LAW data in the LAW system: As of SAP We# AS ;)&-! SP5&! using report 9SLAWGT'STGAP+ As of SAP NetWeaver &--5 in the LAW! #y choosing oto #n,ormation Systems • •
"onsolidation Result
The Result ta# page shows the result of the last (current$ user consolidation) The ta#le is divided into upper and lower parts (indicated #y different colors$) The upper parts shows only individual user types! while the lower contains all consolidated user type com#inations) +f there are no user type com#inations! the lower part is not displayed) .olumns of the 9esult Ta#le "olumn Additional ,otes +ndicator Shows whether the row is for standalone user or users created #y an upgrade Specifies a user type or a com#ination of user types that was determined during the consolidation .om#inations and for which the following num#ers apply) +ndividually Shows the num#er of users with this type or this type com#ination) +n Shows the additional num#er of users of this type that have resulted from type com#inations (only in .om#ination the upper part of the ta#le$) Note The totals in this column are calculated purely arithmetically #ased on the com#inations found and do not take into account special features of contracts in any way) 7ou can change the values at any
.olumns of the 9esult Ta#le "olumn Additional ,otes time in change mode and therefore adFust them to the applica#le contractual conditions) 'nd of the note) Shows the total of the user types individually measured and found in com#ination (total of the two Total previous columns$) Licensed 7ou can display or enter the num#er of e/isting licenses here) alance Shows the difference #etween e/isting and measured licenses) Features The following functions are availa#le in the list of results: &isplay #ypes as I&#e$t Switches the display in the om8inations column #etween the description of the user types and special versions (te/t$ and the identifier (+*$) Maintain +$isting Licenses Switches the ta#le to change mode! so that the fields of the licensed column in the upper part of the columns Licensed and #n om8ination #ecome ready for input) 7ou can enter the num#er of e/isting licenses for the individual types) Sa.e Licenses in Archi.e The function has two tasks) 1irst! it saves the maintained licenses so that you do not always have to re8enter them) +t also saves the result of the current consolidation! so that you can display it again at a later time) At every save! you need to enter a description) This description makes it easier for you to select the results you want later from all of the saved results) The date and time are automatically added at every save) Fetch Licenses from Archi.e As soon as consolidation results have #een saved and therefore e/ist in the archive! you can use this function to retrieve and display a particular result) 7ou select the desired result in a dialog #o/) Although the current display is lost when you do this! you can save it first) To display the current consolidation result again! call the Result ta# page again) When you do so! the maintained licenses from the most recently saved archive are automatically transferred to the display) +f user types that did not previously e/ist have #een added due to new measurement data! you can perform the maintenance of e/isting licenses for these types) &elete Licenses from the Archi.e *eletes saved consolidation results from the archive using a selection dialog #o/)
"orrect ser "lassification
+f you find errors in the results display during the classification of a user! you can only correct these in the source system) Procedure =) .orrect the user classification in the source system and restart the system measurement (transaction CS22$) &) .ollect the measurement data in the component system) <) *elete the relevant system in LAW) 5) +mport the corrected measurement data and repeat the following procedures: .om#ining Csers o .onsolidating Cser Types o Result 7ou can transfer the corrected results to SAP) #ransferring Results to SAP
After you have consolidated the data! transfer the results to SAP) The LAW supports two procedures: one the one hand! the Service *ata .ontrol .enter (S*..$! and on the other! the Service *ata 2anager (Service *ata .ontrol .enter! S*..N$ (see SAP Note 6;=,<$) The data is transferred anonymously! as displayed in the LAW log) 7ou
can also create comments a#out the measurement data using the omments push#utton) These are also transferred to SAP) Note To display the data as it is transferred to SAP! you need to call up the log)) To do this! choose &easurement Data Send Results LA Log reate LA Log ) 'nd of the note) Prerequisites The Service *ata .ontrol .enter (S*..$ or its successor! the Service *ata 2anager (S*..N$ is active (see SAP Note =,6;<= or ,;<;=$) 7ou have authori@ations S*..G*'B H 9'A* and S*..G9CN H 9'A*! W9+T' for the o#Fect SGS*..! with which you can transfer data) Procedure =) .all the License Administration Work#ench (transaction SLAW or L+.'NS'GA*2+N$) &) To send the files with the measurement data to SAP! choose the option $rans,er Directly to SAP in the ontrol LA #o/) <) +f you have created remarks! you can now decide in a dialog #o/ whether you want to send these to SAP unchanged) 5) To display the list of all transfers! choose the Display $rans,ers option in the ontrol LA #o/) •
•
LA5 Interface
The LAW data is availa#le to you through the LAW interface for additional! automated processing! such as additional internal allocation of the licenses) The LAW interface is a collection of function modules with which you can access the information stored in the LAW with read accesses) Seven o#Fects and the corresponding AP+s have #een defined for this read8only access) The AP+s return either one or more ta#les or an 2L document as a result) usiness o#Fects 1!@ect Additional ,otes Function Module Csers in the LAW) The o#Fect contains all relevant data LAWCser AP+GLAWCS'9GV'TL+ST for an SAP user in the LAW) Systems in the LAW) The o#Fect contains all relevant data LAWSystem AP+GLAWS7ST'2GV'TL+ST for an SAP system in the LAW) 'ngines in the LAW) The o#Fect contains all relevant data LAW'ngine AP+GLAW'NV+N'GV'TL+ST for an engine in the LAW) Cser types in the LAW) The o#Fect contains all relevant LAWCserType AP+GLAWCT7P'GV'TL+ST data for an SAP user type (license type$ in the LAW) .onsolidated users in the LAW) The o#Fect contains all LAW.onsCser AP+GLAW.>NSCS9GV'TL+ST relevant data for a consolidated SAP user in the LAW) .onsolidated engines in the LAW) The o#Fect contains all LAW.ons'ngine AP+GLAW.>NS'NVGV'TL+ST relevant data for a consolidated engine in the LAW) .onsolidated user types in the LAW) The o#Fect contains all relevant data for a consolidated SAP user type in the LAW.onsCserType LAW) Cser types with their special versions and AP+GLAW.>NSCS9GV'TL+ST surcharges are! if possi#le! consolidated to a common user type) All AP+s have similar +2P>9T+NV and 'P>9T+NV interfaces) The following parameters e/ist for all modules) AP+ +nterfaces Interface Parameters Additional ,otes 2a/imum num#er of rows in the set of hits) 7ou can use this parameter to determine the ma/imum num#er of rows of the set of +2P>9T+NV 2AG9>WS hits) +n this way! you can limit the si@e of the relevant results ta#le or of the result document)
AP+ +nterfaces Interface Parameters P9'TT7GP9+NT
Additional ,otes 1ormatting of an 2L document in accordance with the document structure)
Ta#le with selection parameters This is an e/tended 9ANV' ta#le) The name of a field from the relevant AP+ o#Fect is entered in the PA9A2'T'9 field! if selections are to #e made using this attri#ute) All other fields are the usual fields for 9ANV' ta#les) With a small num#er of e/ceptions! all fields of the relevant o#Fect can #e used for making selections) This ta#le offers a very fle/i#le option for specifying selection conditions) 1or information a#out which fields can #e used for selection! see the documentation for the individual function S'L'.T+>NG9ANV' modules) +f a field is not permitted for selection and is used anyway! an error message is generated) The first three AP+s! which allow access to the data that has not yet #een consolidated! have fields for identifying a component system! either using the uniue S7ST'2GN> (system num#er$! or! if this does not yet e/it! using the three fields +NSTGN> (installation num#er$! SAPGS7ST'2 (System +*$! and 0WG"'7 (0ardware key$) '/ception: AP+GLAWG.>NSCT7GV'TL+ST does not know this ta#le) Num#er of selected rows) This parameter provides you with an 'P>9T+NV 9>WS overview of the result set to #e e/pected) Si@e of the 2L document generated) +f an 2L document is reuested as a result! this parameter contains the si@e of the S+' document generated) +n come cases! this si@e is reuired for the additional processing of the document) 9'TC9N 9eturns the usual ta#le of (error$ messages for AP+s) CS'9L+ST! CS'9L+STG2L 9esults ta#le or 2L document for the AP+ LAWCS'9) 'NV+N'L+ST! 9esults ta#le or 2L document for the AP+ LAW'NV+N') 'NV+N'L+STG2L CS'9T7P'L+ST! 9esults ta#le or 2L document for the AP+ LAWCT7P') CS'9T7P'L+STG2L .>NSCS'9L+ST! 9esults ta#le or 2L document for the AP+ LAW.>NSCS'9) .>NSCS'9L+STG2L .>NS'NV+N'L+ST! 9esults ta#le or 2L document for the AP+ LAW.>NS'NV) .>NS'NV+N'L+STG2L .>NSCT7P'L+ST! 9esults ta#le or 2L document for the AP+ LAW.>NSCT7) .>NSCT7P'L+STG2L S7ST'2L+ST! .L+'NTL+ST! .>2P>N'NTL+ST! 9esults ta#le or 2L document for the AP+ LAWS7ST'2) 9'SCLTL+STG2L 1or more information! refer to the documentation for the function modules in the AP+ '/plorer (transaction AP+$! on the Hierarc/y ta# page under ;asis Security )
Licensing the B;++ +ngine
