USU (formerly Aspera) helps you overcome SAP licensing challenges with solutions that minimize licensing costs and audit risks.
USU (formerly Aspera) is the leading provider of software and services for IT & Customer Service Management. More than 50 Global Fortune 500 companies use our software asset management solution portfolio to minimize licensing costs and audit risks. Our SAM solution helps you overcome SAP licensing challenges and ensures that you are prepared for contract negotiations.
We balance your SAP compliance, optimize your licenses, analyse the S/4HANA migration, compare Indirect Access with Direct Access and evaluate your SAP SaaS options. Our solution has been certified by SAP for its interoperability and by renowned analysts for its functionality. USU has over 40 years of experience in SAP license management and optimization.
We offer tailor-made services with the largest in-house team in the industry and manage software licenses from all providers across the data center, cloud and hybrid environments.
License Management
Process and IT consulting
Risk Management & Compliance
S/4 Hana
SAM (Services & Asset Management)
Data analysis/testing
Project management
Reviews and compliance
Reviews/quality assurance
Services
Downloads
Videos
Authors
All E3 articles by the authors
Why we still need a SAM tool for SAP
I read more and more often - also from former companions,
that cloud computing makes a software asset management (SAM) tool unnecessary.
But how can a cloud work without administration?
Above the clouds
Cancellation of SAP on-prem licenses converts them into cloud subscriptions, but this means that the existing SAP customer loses all autonomy over its own ERP system.
The way is called S/4
Are you about to decide which path to use to migrate to S/4 Hana? Contract Conversion, Product Conversion or Rise with SAP? Take a look at the PKL Q2/2023.
Rent brake for SAP?
SAP wants to introduce an annual price increase for cloud products. But also
Every partner who sells a go-to-market solution must pay a revenue share, regardless of whether SAP facilitated the transaction.
Digital Access: Now it's getting serious
In February last year, the SAP Help Portal officially announced that special attention would be paid to digital access documents in measurement from 2020:
Hypercare audits start now!
Thank you, SAP! There are still a few questions...
After more than 25 years of SAP ERP/ECC, it's time to say thank you. SAP's success is also the success of the SAP community. The ERP provider has done many things right. No reason not to ask a question in the future.
SAP S/4 Hana Contract Conversion
The S/4 migration not only brings technological advantages, it also offers opportunities to renew outdated processes. Interesting: Bringing the license portfolio up to date with Contract Conversion and disposing of legacy processes.
Digital Access: Excellent for SAP revenue
One lever to bring "motion-weary" existing SAP customers into the ERP cloud is "indirect use": SAP is threatening huge license back payments while promising an end to all problems when switching to the cloud.
S/4 migration and the licensing question
The migration to S/4 Hana can take SAP customers around two to three years, depending on the size of the landscape. In addition to the technical migration, the SAP contract will also be converted. This is a great opportunity to finally clean up existing legacy issues.
Creating good ground for the architecture of the future
All SAP customers are facing extensive S/4 migration projects and contract conversions. These can be managed with the combination of Enterprise Architecture Management (EAM) and strategic license management.
Dr. Jekyll and Mr. Hyde?
Since April 10, everyone has been talking about the preliminary license model that SAP had agreed on with its user groups ASUG and DSAG: There is a rudimentary concept, a price list. What is still missing, however, is a technical evaluation.
New SAP licensing model, old challenges
Surrounded by walls of legally questionable clauses and numerous stumbling blocks - which he can only escape with excessive payments - the SAP customer faces the mission of escaping SAP unscathed.
Massive licensing needs for all companies
SAP plans to enforce a license condition on its customers in the new year 2018, which is already included in the Price and Conditions List (PKL) 2017/4 on page 25.
A first concession
For months, DSAG and SAP have been in talks about how to deal with the contentious issue of the "NetWeaver Foundation For Third Party Applications" in the future.
Healthy licensing landscape
SAP focuses on the cloud-first strategy and offers its customers a wide range of solutions. Many do not have a real choice not to use these solutions. But how do customers achieve a healthy SAP licensing landscape that takes their licenses into account and optimizes them highly effectively?
Unjustly underestimated: Uniform SAP User Management
Time and again, we find that one of the main causes of overlicensing among our SAP customers is inadequate SAP user management. However, this is the basis for correct licensing because it can be used to determine the exact number of SAP users required in the landscape.
The magic stairs in the castle SAP
![[shutterstock:464471567, vexworldwide]](https://e3mag.com/wp-content/uploads/2017/02/shutterstock_464471567.jpg)
Is SAP financing its new strategy through hidden price increases for existing customers? Some people are reminded of Harry Potter when they try to find their way unscathed up the magical stairs in Hogwarts Castle - but they suddenly and unexpectedly change direction.
Indirect use: What makes complicated things even more complicated
What is indirect use? Which licenses should one buy? With the change of the description for SAP NetWeaver Foundation for Third Party Applications in the Price and Conditions List (PKL) 2016/2, the confusion has increased.
Eight challenges in SAP license management
SAP has always left it up to customers to allocate SAP user licenses manually in accordance with the agreement (contract). Vague descriptions of what an SAP user may and may not do with a license type do not make the allocation any easier.
