Usage Notes and Restrictions

  1. Customers with legacy Hyperion pre-System 9 product licenses must pay a Foundation Enablement migration fee to migrate to the corresponding Oracle Hyperion licenses, which include Hyperion Foundation Services. Additional information can be found on eSource at http://esource.oraclecorp.com > License > Migration > Migration Pricing Practices > Acquisition Specific Migration Practices > Hyperion Migration Practices. A detailed license mapping spreadsheet can be found on eSource at http://esource.oraclecorp.com > License > Migration > Product Migration Listing > Hyperion Pre-System 9. If you are an Oracle partner, please contact your Oracle Representative for additional information.

  2. Hyperion product option license quantities must match the number of licenses of the associated Hyperion product. This rule applies to all license models: Component, Customer Application Suite, and Enterprise. Examples include the following:

    • <dev. note: added this to enable rendering as the line above is removed, leaving only one bullet in UL where at least two are required. re-write to comply with rendering requirements, and remove this LI>
    • The number of Data Relationship Management for Hyperion Enterprise Financial Close Suite Application User licenses must match the number of Hyperion Enterprise Financial Close Suite Application User Licenses. Similarly, the number of Data Relationship Management for Hyperion Enterprise Financial Close Suite Enterprise $M in Revenue licenses must match the number of Hyperion Enterprise Financial Close Suite Enterprise $M in Revenue licenses.

  3. Authorized use of DRM APIs: Data Relationship Management Web Services APIs are available to Oracle Data Relationship Steward or Oracle Data Relationship Governance licensed users who have been provisioned with an appropriate role in one or more Data Relationship Management applications. Individual licensed users must be used when performing API operations which modify data in a Data Relationship Management application. Proxy users with an Oracle Data Relationship Steward license are *not* permitted to perform create, update or delete operations in real-time or in batch using the DRM API or DRM Batch Client.

    Proxy users are permitted to use the DRM Request API. This API offers the ability to create and update requests which would be used by external workflow applications to persist pending changes to DRM. Proxy users may *not* be used to commit changes to DRM that were approved via an external workflow. Final approvers or committers must be licensed Oracle Data Relationship Steward users with user roles authorized to interactively make changes within DRM to ensure audit integrity.

    Similarly, a proxy user with the Governance User role may be used to programmatically submit changes from external systems into the Oracle Data Relationship Governance application. Further, proxy users may also invoke the DRM API/web services via the Anonymous User role provided one has licensed the Oracle Data Relationship Management Read Only Access option. In addition to enabling public browse access to specific target audiences, this license authorizes read access using the DRM web services API.