![]() When a developer is leaving, you should also delete the corresponding entry in DEVACCESS table to avoid it from being counted in the license measurement. For security reasons, you should delete all entries in DEVACCESS table in all non-development systems. The measurement of developers has to run on the development system. ![]() SAP has given update notes on the USSM user measurement programs that use the S4HANA logic, which is described below.īy applying OSS note 3038370 – USMM2: Development Workbench Check alte Version wieder herstellen, you can revert back to the original way of working that measures entries in DEVACCESS table and changes to REPOSRC. This mechanism is hackable, but in the end in the system table DEVACCESS is filled with everybody who has filled in the keys. This means a developer key needs to be called off at sap support site for keys. On a non-S4HANA based system, the developer key concept still exists. Developer measurement on non-S4HANA system The measurement should follow the definition. Most likely the definition in your contract clearly states developer is only for creation and changing custom code (Z code). What are the complexities on S4HANA with measuring developers?.How can I go back to the DEVACCESS measurement on my non-S4HANA systems?.What is a developer and why is it so hard to measure?. ![]() Questions that will be answered in this blog are: The developer licenses are the most expensive licenses and also the ones which are under continuous debate with SAP.
0 Comments
Leave a Reply. |