The document discusses several key contractual terms and assumptions made in the license entitlement health check:
1) It compares the current metric definitions used in the support renewals to the original license ordering documents.
2) It assumes all software licenses can be used by all entities within the organization, but usage may be restricted for licenses bought by lower level entities.
3) It assumes licenses are for the organization's internal use only, and separate hosting licenses may be required for third party use.
The document discusses several key contractual terms and assumptions made in the license entitlement health check:
1) It compares the current metric definitions used in the support renewals to the original license ordering documents.
2) It assumes all software licenses can be used by all entities within the organization, but usage may be restricted for licenses bought by lower level entities.
3) It assumes licenses are for the organization's internal use only, and separate hosting licenses may be required for third party use.
The document discusses several key contractual terms and assumptions made in the license entitlement health check:
1) It compares the current metric definitions used in the support renewals to the original license ordering documents.
2) It assumes all software licenses can be used by all entities within the organization, but usage may be restricted for licenses bought by lower level entities.
3) It assumes licenses are for the organization's internal use only, and separate hosting licenses may be required for third party use.
We have used your latest Support Renewals to determine your license entitlement. The Support Renewals show Oracle’s current metric definitions, which we have taken into account for this Health Check. In some cases, this current metric definition might differ from the one in the original ordering document, which still is applicable to your licenses. 2. Customer Definition: We have assumed that all software licenses were bought by the highest-level entity and can therefore be used by all legal entities, business units and/or (majority owned) subsidiaries within your organization. If however part of the licenses were bought by lower level entities, usage may be restricted to these entities and licenses cannot be transferred to other entities. 3. Internal Business Operations vs Hosting: We have assumed that all software licenses are being used for your own internal business operations only. In case you are using the Oracle programs for the business operations of a third party, Oracle may require separate (proprietary application) hosting licenses which allow such usage. 4. License Level: Full Use, Application Specific Full Use (ASFU) or Embedded: Can you explain the difference between them? Also with e.g. We have assumed that all software licenses were bought on a Full Use basis and can therefore be used in conjunction with any application. However, you may have obtained other additional usage rights through a third party solution provider, which includes the (restricted use) right to make use of the Oracle Database programs and/or associated options. These licenses are called Application Specific Full Use or Embedded Software Licenses. 5. Third party Support: If we see technical support maintenance renewal documents, which are not from Oracle Support itself (e.g. Rimini Street or Spinnacker) then contact the onboarding team for further guidance. What does it mean third party?