Implementation

Oracle Hyperion DRM Technical Issue | Integration with EBS

Hi everyone!

We just stumbled upon an interesting change in the latest version (11.1.2.3) of Oracle Hyperion Data Relationship Manager (DRM). For performance reasons,
Oracle has decided to limit the number of tables Oracle Hyperion DRM can detect when you define an external connection to 2000.

This is usually not a problem. However, if you follow the DRM Oracle General Ledger Integration Guide you’ll see that you ‘must’ use the APPS schema to integrate DRM to E-Business Suite (EBS). This schema usually has more than 2000 tables associated. This means there is a risk that the two target tables used by DRM (GL_DRM_SEGVALUES_INTERFACE and GL_DRM_HIERARCHY_INTERFACE) will be missing from the list of tables for the external connection.

Despite what the integration guide says, however, you can in fact define a different database user with write access to just these two tables and gain access to them that way.

Note that Oracle has logged an enhancement request to remove this restriction, so future releases may not come with this limitation. We experienced this with DRM 11.1.2.3.303.

We hope this is useful.

Tagged , , ,

Estimating the Costs of implementing Oracle Hyperion DRM

Estimating the cost of an Oracle Hyperion Data Relationship Manager (DRM) implementation can be difficult. This blog will highlight the areas and risks you should consider.

When developing the business case for the costs can broadly be separated into 3 distinct areas:

  1. Software and licensing costs;
  2. Hardware costs; and
  3. Implementation costs.

The first of these can be difficult to understand as you need to have some indication of how many nodes will be required for you solution.  This information is not often available until after implementation as the agreed design will affect the number of nodes required.

The second, hardware costs, can be identified relatively easily using the software vendor’s prior experience.

The main issue comes with estimating implementation costs.  At the point at which the decision is being taken to purchase the relevant software, it is unlikely that you have expertise already on the site. You therefore have a few options available. In some instances we have seen organisations ask for an estimate from the software vendor.  This can be a huge mistake for two reasons. The software provider is unlikely to have a detailed understanding of your requirements and in addition they are conflicted as they are trying to sell you the software.  They have a vested interested in trying to minimise the estimate to ensure you buy the software.

Alternatively, you may be tempted to use a formula to try and determine the final implementation costs. This approach is fine as long as the formula used is not arbitrary, and is based on a good understanding of both the requirements and the technology.

In our opinion, the best method of understanding the implementation costs is to approach an independent organisation that has demonstrable experience of implementing the same software in a similar environment.  Most consulting organisations should be willing to give you guidance for free to help you understand expected costs.  In some instances, this may require more analysis time to understand the requirement, but surely a minimal cost upfront, to avoid a huge under, or over, estimation is a necessary investment?

If you need any help understanding the potential implementation costs of Oracle Hyperion DRM can help your organisation please do not hesitate to contact us.

Tagged , , , ,