- Please ignore Asaduzzaman's advice, since that might well be the worst practise. If you have a landscape of several productive systems (say: ERP, BI, SRM etc.), errors in user-classifcation always can happen: lost IDOCs, forgot one system ... and so on. So, of course, you only send the one run with the results of which you are satisfied. Run it as often as you wish without sending it. Correct all the errors and only send the last and error-free run.
- USMM does not only measure user licenses. Depending on your price list, it might well measure the use of installed components or -if you have a named user agreement- on how many workstations the same user has been logged on at the same time or does one user have unrealistic logon times (like more than 12 hours) and so on. This is well documented someplace in SMP.
- Do not (repeat: not) send measurement data to SAP without being prompted by them. They get extremely irritated if they receive measurement data for which they have no request in their own systems. This might lead to some unpleasent (and completely obsolete) e-mail exchanges. So don't. They will notify you and send you a measurement plan when they want you to run USMM. However, it can't hurt to keep your user data in excellent condition at all times.
- Consider (especially when running several landscapes) the use of LAW, even LAW 2.0. This is a centralised license audit engine and it works like a charm (millions of bugs aside). It's absolute pro is: you have an overview over all systems and the status of the license audit jobs in all the systems on one single point and that's priceless if you have - say 27 systems.
- Finally - the jobs you posted look like they would measure applications. I don't know whether your contract with SAP runs on that base. Please check and adjust your price list in USMM accordingly. This is of maximum importance, so please make it right.
- Please ignore