1. Day 2 SAM for SAP Practitioner Workshop

2. Welcome to the sam for sap practitioner workshop

3. Day 2 SAM for SAP Practitioner Workshop

4. Day 2 Goals Comprehensive demonstration of RULES engine by lead DLS software engineer Understanding of key RULE engine concepts and components Duplicate Search and Analysis Systems Measurement Analysis Online/Offline working modes Administration and Systems Connections

5. Webcast/call with chief architect of the dynamic licensing Suite Joachim Paulini

6. BREAK

7. The rules engine Overview and Examples

8. The Dynamic Licensing Suite supports 3 distinct activities

9. Aggregate-> Analyze-> Administer • Baseline Development • Detailed Usage Data • Logon History • Change Queue • Recommendations • License Recycle/Retire • Master User Data Changes • Duplicates • Logon Analysis • Rules Engine • Role Tuning • License Type Optimization • Indirect Access Analysis

10. Rules act on DATA IF (Condition) THEN (Action) As an example: IF (User has not logged in for 180 days) THEN (Set User License type to Test – 91) Based on the data being constantly aggregated, these rules can be applied daily, weekly....

11. Built-in Rules in theDynamic Licensing Suite There are rules pre-built and included in the Dynamic Licensing Suite for Software Asset Management (SAM) professional and SAP Administrator to use New Rules can be created in the Dynamic Licensing Suite and saved and accessibleby all Rules can be either LOCAL or GLOBAL.

12. LOCAL and GLOBAL Rules LOCAL GLOBAL Global Rules: Over-Ride the local rules Are applied systems-wide typically at a contract level Local Rules: • Are applied to one SAPUSER ID at a time • Are applied within one SAP System Example: If (User has not logged on for 180 days), then (set user type to test – 91) Example: Only 50% of user IDs can be set as Special, others set as Professional (54)

13. Rule Engine Recommendations feed Change list

14. Change list batch-updates SAP

15. BREAK

16. Duplicate search and analysis

17. Why do duplicates exist? Multiple administrators may have assigned named differently Mergers & Acquisitions lead to initial redundancy across systems Some times duplicate are intentional, so they have to be reviewed one-by-one!

18. Identical emails, transposed names, similar SAP User IDs all can be identified EMAILS

19. Viewing Built-in Rules, add more... Open Duplicate Search Menu from the DLS Menu tree Open Duplicate Rules

20. EXECUTE Duplicate Search in Background! Duplicate Search is VERY CPU and TIME Intensive, ALWAYS execute in background!

21. Duplicate Search Results

22. Potential dupes are grouped Total users Potential duplicates Group numbers Licenses used Possible issues

23. DLS DEMO Duplicate Search Analysis

24. System Measurement Analysis System Measurement holds the key to understanding potential indirect access violations

25. How can Systems Measurement Data be used? The Systems Measurement Program determines the number of users and chargeable objects of the engines in a system. The Dynamic Licensing Suite can highlight issues with Systems Measurement data that are likely to come up in an SAP Audit In particular, the Systems Measurement results can be key to identifying SAP Indirect Access Issues for an upcoming SAP Audit

26. Three key System Measurements scrutinized IN SAP Audits User ID: JoeCool User ID: JoeCool User ID: JoeCool Multiple Logons Same SAP UserID logged in and working at the same time

27. Three key System Measurements scrutinized IN SAP Audits User ID: Workaholic 2. Very LONG working hours! Logged in SAP Users works relentlessly without a break.

28. Three key System Measurements scrutinized IN SAP Audits User ID: Joe_Productive 3. The SUPER PRODUCTIVE worker! Workload carried out by a user is remarkable !

29. MeTERING: Non-compliance • Indirect Access candidates from: • Multiple logons • Work Time • Volume of work

30. Drilling down: non-compliance Example: Volume of Work Alert likely to trigger Indirect Access Charges

31. Drilling down: non-compliance Example: License Type (Role) Alert Usage of tables exhibits professional License type behavior

32. Dynamic Licensing Suite Administration and Operations

33. DLS DEMO Systems Measurement

34. BREAK

35. DLS Administration and Operations

36. Export/import of objects • Objects include: • Aggregation Rules • Duplicate Rules • Local Rules • Global Rules • License Type Hierarchy Allows you to develop best-practice rules and processes and move them from client to client DLS designed for Partners to succeed!

37. ENTERPRISE DEPLOYMENT SAM CONSULTANT import OFFLINE COPY export

38. Working online/offline You can take the collection of SAP USER/USAGE data and save it and reload it back at your offices Allows you to minimize time and consultants on-site DLS designed for Partners to succeed!

39. BREAK

40. Data Source AdministrationInterconnecting SAP Satellite Systems

41. The Dynamic Licensing Suite creates a holistic view of SAP users, user licenses, and usage. It does this by first aggregating data from dozens to hundreds of SAP satellite system

42. Controlling data sources This is easiest done by installing the Dynamic Licensing Suite on the Solution Manager Server, which usually has access to other systems DLS can operate agentless, which is substantially easier to deploy User and Usage data is pulled in from all defined sources into one aggregate DB

43. Data sources point to systems and satellite systems

44. Defining SAP systems

45. BREAK

46. HANDS On lab Classroom Exercises

47. Rules Engine – Review Results

48. Rules Engine – View/edit rule

49. Duplicate search – results

50. Systems measurement - review