Disclaimer:
SOLUTIONS ARE PROVIDED ON AN "AS IS" BASIS. NEITHER FLEXERA NOR ITS SUPPLIERS MAKE ANY WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. LICENSEE MAY HAVE OTHER STATUTORY RIGHTS. HOWEVER, TO THE FULL EXTENT PERMITTED BY LAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, WILL BE LIMITED TO THE SHORTER OF (I) THE STATUTORILY REQUIRED PERIOD OR (II) THIRTY (30) DAYS FROM LICENSEE’S ACCEPTANCE OF THE AGREEMENT.
The views below bring visibility on data for FlexNet Manager for SAP implementers or the SAP admin team.
The list of views included in this package
A use of this views is to create transaction profiles. For instance, it is possible to create a transaction profile based on the list of transactions a user has been provided through his role… From the list of transaction of a “self-service” role, FlexNet Manager for SAP will be able to evaluate all users, based on their actual activity, allocated with any roles, against the list of transactions of this “ESS” role.
To create the views, run SQL Server Management Studio, connect to the compliance database with an admin login (some views create stored procedures) and execute the query attached making sure you are logged on the compliance database.
FlexNet Manager Suite offers reporting only through Cognos today (operational objects on SAP Users and Systems). The code below will create the SAP
The script attached creates the User accounts & recommendations (Cust) object that includes all details that you can see in the recommendations details of FlexNet Manager for SAP
It also links to the SAP System Detail (Cut) object that includes all details on SAP Systems (SystemID, ClientID, Inventory date etc.) and also advanced metrics for the systems that indicate inventory quality metrics:
The script creates a function (dbo.nr_SAPLicenseRecommendationRuleMessageI18NForLatest()) that catches the optimization rules message with good performance, it creates two views that will be used (nrcv_SAPConsumptionDetails, , all strings used by the objects, creates the “SearchTypes”, the “SearchType Columns”
Reporting objects creation code
see attached Word document
To create the view, please copy and paste the code below making sure you are on the compliance database (see attached Word document)
Attention: The assumption is that accounts are de active with a valid to date and that they are not deleted from the systems… thus, the last inventory of systems contains the historical information on active accounts (based on valid from / valid to date)
The ideal sequence in a SAP optimization profile is to do a user profiling according to actual usage, change the license types of the users thanks to the recommended changes from FlexNet Manager Suite… change the users roles on systems to align the roles (and authorization) to the license types allocated. You close the loop then and avoid any painful discussion with SAP (this user did nothing but could have done a lot).
This view will catch, system per system, and current (or optimal) license types per current (or optimal) license types the top ten roles the most used (basically, if users used transaction A, B and C that belong to roles R, then the role R CPU time is “A CPU time + B CPU time + C CPU Time”.
Note that if a transaction belongs to multiple roles, its times will be reported on each role…
(can be restricted to “X months” by changing the code with a WHERE Clause on the SAPConsumption date)
This view gives role per role the usage statistics for used and unused T Codes. You can set a filter on dates for the analysis in the custom view filter prior to launching the view, for instance 2016-01-01*2017-01-01 for a one year period. No date means no filter, always use * as a separator.
Note: transaction usage for roles can be confusing.
SAP systems provide Role definitions and Transaction history to FNM SAP. FNM SAP reports on transaction history, showing CPU time for transactions.
FlexNet Manager Suite also computes a Transaction Usage for role based on transactions and their link to roles.
If the same “TTT” transaction appears in two roles a user is allocated to and there is a 10 second transaction history record for “TTT” there will be two “Role transaction usage” lines with 10 seconds CPU time. One for each of the roles.
This view shows CPU time per transaction and module across all systems for the last 3 months. You can sort descending to see rarely used transactions. Could help identifying self-service of travel reservation related transactions.
See code in attached Word document
Means: Start Date =2018-12-01, End Date = 2019-02-01,System =P01,User = ABCD
Filter can be omitted, order doesn’t matter
See attached Word Document
See attached Word Document
See attached Word Document
See attached Word Document
on Apr 15, 2022 08:39 AM - edited on Apr 26, 2022 01:53 AM by ChrisG