Best practices in solution architecture for Oracle EBS, OBI, Hyperion Planning
A perfect design is an enemy of a good design. Often, we strive for a perfect design by customizing our systems, with what we currently know and forget quickly that the out of the box design may not provide the best solution to a given problem but it would probably have the best chance of meeting the schedule , regulatory compliance and cost constraints with acceptable quality.
I just completed US financial services solution architecture and noticing a trend with enterprise customers towards simplicity and making sure the business is provided tools to adapt to the new out of the box functionality reality. 2014 focus seems to be on essentials, mobile and providing a responsive design to the end user.
Having been lucky enough to have implemented multiple times EBS R12, Hyperion Products, OBI and CRM projects, I share some best practices on what in my view should not be modified and other areas that should be slightly improved from a business architecture standpoint:
One question that comes often what is each product main purpose: here is a quick 1 liner on the products.
Hyperion Financial management is Oracle’s consolidation tool and statutory reporting
Hyperion Planning is the Strategic Planning, Budgeting and forecasting tool
Hyperion Financial Data Management is a tool to map different chart of accounts between source systems (EBS and non EBS applications) and HFM
Oracle EBS R12 is the ERP that store the Financial, Project, Procurement, Supply chain transactions
OBI Oracle Business Intelligence is the BI platform that stores the OLAP analytics, provides enterprise reporting, mobile BI and different scorecards.
When implementing your enterprise software keep in mind the following best practices:
1) Times are changing; your approach to BI must change, Mobile Users Deserve the Same Quality of Browsing Experience as on your computer, one financial services company in the US is making sure most ERP, CRM transactions can be performed by mobile or tablet. Put in place mobile responsive design architecture when designing your solution. Your competitors are probably doing it or thinking about it. Technology has become the differentiator, not the business process.
2) Capture integration requirements, then challenge all requirements that don’t respect the out of the box functionality, always make use of the product API’s to customize your solution if required. Focus on essential requirements only.
3) All enterprise software now integratre with Microsoft Excel, Microsoft’s classic spreadsheet program, is a favorite of sales and finance teams everywhere, use it to minimize change management
4) One that I see often, not matching the growth strategy for the company to the capabilities of the system being implemented. Make sure everyone understands your functionality/ project scope and ROI to avoid the smoking mirror syndrome were the expectations and money spent do not correlate to the required outcome. Communicate with facts and data only!
Like usual please provide your thoughts and comments on solution architecture best practices.