E-Business Suite

Oracle Hyperion DRM Technical Issue | Integration with EBS

Hi everyone!

We just stumbled upon an interesting change in the latest version ( 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

We hope this is useful.

Tagged , , ,

Positive or Negative | which way to turn?

In a recent meeting I was asked whether there is a standard approach to signage in reporting. I think we can all agree this is a big question.  “Reporting” covers a wide range of purposes and platforms.  Did the client mean management, statutory or transactional?  Were they looking at the consolidation tool, budgeting and forecasting or analytical?  The implications of the decision are wide ranging for the usability of your financial applications, and therefore it needs significant thought.

However, it is a common question. There is no standard! With my consulting hat on, the solution is clear: an organisation needs to adopt a single reporting standard which addresses its management, financial and transactional reporting purposes. What that standard is, from my selfish point of view, is immaterial! I have included an example of signage standards, but this is by no means the only approach.

In my past life as a management accountant, I spent many a late night during month-end trying to reconcile reports across Oracle Hyperion Essbase, HFM (Hyperion Financial Management and Oracle E-Business suite (EBS).  Were the numbers I was seeing correctly sign-flipped?  As each application was using its own approach to sign-flipping, how could I be sure that the rules had not fallen out of alignment?

Then I discovered masterdata governance. I found that by centralising all our financial masterdata (including our report definitions) into a single location we could create a single definition of our core financial constructs, including a single definition of the signage rules. These rules were then published for use in all our financial reporting applications, thereby ensuring that they were using the standard definition. Once implemented, I spent less time reconciling and more time analysing, a benefit that I think all my fellow accountants and the business would see as a “positive”! Smile

Until next week.

Tagged , , , , , ,

Cash Flow design | where is the elephant?

This week I have been working on a driven or calculated cash flow design. As is the common pattern in my experience, the requirement was initially expressed as a need for a consolidation tool, Oracle Hyperion Financial Management (HFM). When digging into the requirement, I asked whether this report definition needed to be shared with their relational reporting tool, OBIEE (Oracle Business Intelligence Suite Enterprise Edition) looking at Oracle E-business Suite (EBS) and their analytical reporting tool, Essbase? Would the cash flow report not be a valuable operational and analytical tool, rather than just a retrospective month-end report? Everyone agreed it would be, but this is when I noticed the elephant in the room. Everyone agreed that the cash flow could be calculated, but had assumed that the ledger did not have sufficient detail to populate the model.

Don’t get me wrong, I have yet to encounter a client that can calculate a full cash flow without some manual analysis, however this is the 5%. The other 95% is usually available in the ledger. I think what deters us, is that we are used to mapping to HFM at an account level only. The information that drives cash flow is often only available at sub-ledger and journal type. Using a masterdata management tool allows you to easily map all kinds of information, including sub-ledgers and journal types. If in doubt about the source of data, start by analysing the support for your cash flow journals or calculation …then get ready to look for elephants!

Tagged , , , ,

FTSE 100 Global Financial Services Client, Seismi & Oracle DRM

Some more good news to share!

We have been selected by a FTSE 100 global financial services client to implement Oracle Hyperion DRM (Data Relationship Manager) as the single repository to maintain all financial masterdata. Oracle Hyperion DRM will be responsible for publishing masterdata definitions and mappings to a wide range of applications, including Oracle Hyperion Essbase, HFM (Hyperion Financial Management), FDM (Financial Data Quality Management) and Oracle ERPi (Enterprise Resource Planning Integrator).

Seismi are responsible for delivering the Oracle Hyperion DRM solution, alongside an Oracle Hyperion Essbase reporting environment, which will be built using Oracle Hyperion EPMA (Enterprise Performance Management Architect) and Oracle ERPi.  As always, Oracle Hyperion DRM will provide them with a comprehensive governance solution enabling efficient maintenance of all their core financial masterdata, whilst Essbase will provide an incredibly powerful analytical tool to transform their month-end financial reporting requirements.

The project has already started we look forward to sharing more details and a case study in due course..

Off for another celebration Smile!

Tagged , , , , , ,

UK's Favourite Retailer selects Seismi and Oracle DRM!

Some good news to share! We have started a comprehensive BI (Business Intelligence) Finance initiative for the UK’s favourite retailer. We have been asked to design a solution to use Oracle Hyperion DRM  (Data Relationship Manager) as the single repository of all the retailer’s financial masterdata.  Oracle Hyperion DRM will provide them with a comprehensive governance solution enabling efficient maintenance of all their core financial masterdata.

Oracle Hyperion DRM’s scope will encompass Oracle EBS, ERPi (Enterprise Resource Planning Integrator), FDM (Financial Data Quality Management), HFM, Essbase and OBIEE (Oracle Business Intelligence Suite Enterprise Edition) applications and tools.

This represents another great opportunity to show how masterdata management (MDM)  should be a primary consideration at the start of any EPM (Enterprise Performance Management) initiative, not, an afterthought.

We look forward to sharing more over the course of the project. Off to celebrate!

Tagged , , , , , , , ,

Video | Using Masterdata Governance to overcome Business Challenges (Part 4)

This week we will building on what we saw last week where we looked at using Oracle Hyperion Data Relationship Manager (DRM) to govern an ERP system – Oracle E-Business Suite (EBS) but it could be any ERP suite. In addition to governing Oracle EBS, Oracle Hyperion DRM will be used to govern the Hyperion Financial Management (HFM) consolidation tool and a reporting tool (Oracle Essbase).

As you will see in the video the user interface is very intuitive and we aim to build on your understanding of the true power and potential of Oracle Hyperion DRM. We will see that we can control structures in our transactions, consolidation and reporting applications. This demonstration will also show how easy it is to implement business rules and that users, of Oracle Hyperion DRM are forced to consider the impact of their changes on all other related applications.

See you next week where we will be looking at how using an integrated Oracle Hyperion DRM template allows us to extract data out of Oracle EBS, supply it with a mapping and load it into Essbase & HFM in an automated and reliable way.


Tagged , , , , , , , ,

Video | Using Masterdata Governance to overcome Business Challenges (Part 3)

In last week’s video blog Ross Gilfillan continued on our theme of how Oracle Hyperion Data Relationship Manager (DRM) can be used to solve business issues. Specifically he looked at how integrated templates can be used to both reduce implementation risks and costs as well as rapidly deploy solutions.

This week he starts to explore integrated templates in more detail and starts at looking how they can be used to govern Oracle E-Business Suite. As you will also see Oracle Hyperion DRM’s user interface is much more user friendly and intuitive than the native Oracle EBS interface.

Ross will continue to look at the flexibility, adaptability and other benefits of integrated templates in his next video where he will show that integrated templates can be used to govern multiple applications when it will be used to govern Oracle Hyperion Essbase and Oracle Hyperion Financial Management (HFM).

As always we encourage people to get in touch if they want to explore these key benefits in more detail.


Tagged , , , , , , , ,

Video | Using Masterdata Governance to overcome Business Challenges (Part 2)

In our last video blog Ross Gilfillan looked at how Masterdata Governance, using Oracle Hyperion Data Relationship Manager (DRM) can be used to solve key business issues.

This week Ross will show how Oracle Hyperion DRM can be rapidly deployed using integrated templates and the benefits this provides. In addition he will make the distinction between integrated templates and standalone templates and specifically the additional functionality that integrated templates deliver to clients.

As always we encourage people to get in touch if they want to explore these key benefits in more detail.

Tagged , , , , , , , ,

Video | Using Masterdata Governance to overcome Business Challenges (Part 1)

This week Ross Gilfillan will be introducing the start of a series of video blogs that explore how masterdata governance, using Hyperion Oracle’s Data Relationship Manager (DRM) tool, can be used to overcome a number of common business challenges.

These challenges include ongoing governance of disparate and distinct chart of accounts; integrating acquisitions; implementing and updating charts of accounts; and mapping.

Over the next few weeks Ross will look in detail at how Oracle Hyperion DRM can be used to govern Oracle’s E-Business Suite, Hyperion Financial Management and Hyperion Essbase.

Please do contact us if you would like to explore these topics in more detail. Ross’s contact details are also included at the end of the video.

Tagged , , , , , , , ,

Governing EBS | Using Masterdata Governance to solve the ‘Human Middleware’ Problem (Part 1)

Oracle E-Business Suite (EBS) has in-built functionality to maintain a chart of accounts. This includes: defining the segment structure of the chart of accounts; the value sets; creating basic reporting terms using parents and summary accounts; controlling the relationships between segments (using either cross validation rules or a combinations table).

So why bother with governing EBS? Very few EBS instances operate in isolation. For example, you need to forecast, consolidate and report using the data in the EBS General Ledger, and you need to load data from your forecasting systems and non-Oracle subledgers into EBS. The number of interfaces can be truly breath-taking yet for many large companies this business problem is managed using ‘human middleware’: accountants who spend month-end extracting and transforming data in spreadsheets to load into other systems, followed by reconciliation, error checking, re-running  and more reconciliation…

This reliance on ‘human middleware’ has a pervasive effect on the finance function:

  1. Reduction in analysis – By focusing on data transformation, reconciliation and report creation, the finance function surrenders its role as proactive business analysts who direct the strategy of the organisation and who are first to identify and react to tactical threats and opportunities;
  2. Obstacle to change – The consequence of the highly manual month end process is that the finance function is reluctant to change the way the business is measured or forecast because of the additional risk and addition effort this entails. The finance function thus unwittingly becomes an obstacle to change, rather than the champion it should be; and
  3. Loss of confidence – ‘human middleware’, despite incredible dedication, inevitably results in errors. As a result, the business starts to doubt finance function reports and starts performing its own reconciliation, data collection and analysis…

In next week’s blog we will explore what we see as the three key issues of manual governance, report definitions and integration as well as how masterdata can provide a real solution to ‘human middleware’.

Tagged , , , , ,