At the earliest levels of athletics, coaches are asked to teach players the basic tenets of teamwork, sportsmanship, and developing fundamentals. At the highest levels, however, coaches are tasked with leading a team to success, oftentimes being some sort of national or professional championship. As the participants gain experience and their skill-sets become more refined, the roles of the coach change. In the beginning, we are teaching new fundamentals and skills, trying to stoke a passion for a sport in a young, impressionable mind. At the highest levels, the coach must rely on their experience and expertise to put their team and players in a position to be successful.
Recently I had a client decide to implement a major architecture change to their production environment. Of course, this change was going to be made to their production environment, during financial close, and on a weekend. As managers of EPM Systems surely know, there is no ‘good time’ to push major system changes. In this case, the change was moving all the EPM components to a new database (DB) server.
An interesting issue appeared for me recently. What happens when after a server crash / restart, Essbase refuses to start? The service shows Running, but Essbase isn’t listening and not responding. The start attempt produces no errors, no logs, it simply does not start.
In Part 1 of this blog, we discussed using the “runbatch” command to process files for three Locations. In Part 2, we will discuss using the “rundatarule” command to accomplish the same thing.
As with many solutions… it depends. “What a surprise,” you say. Your choice will probably be based upon your need, preferences, and also on how comfortable/proficient you are with writing batch scripts. If you need to execute a Data Load Rule(DLR) for one location as a part of a batch script, the answer will probably be “rundatarule.” If you need to execute DLRs for multiple locations, such as a part of a batch script to process monthly Trail Balances, then the answer becomes more subjective.
Regular readers of my blog posts will know that I like to spend a fair amount of space talking about the ‘how’s’ of owning and managing an EPM system. In all honesty, anyone can purchase a software solution, and many companies do, but the real test comes during implementation and support. Over my many years of consulting I’ve noticed that clients who enter the implementation stage with a support and maintenance plan already in mind tend to be more successful. The same success also follows clients who start a project with some sort of future product lifecycle in mind. But what happens when your company hasn’t had the luxury of time to be proactive, or if you have inherited a system that is out of date through an acquisition, or being used for cross-purposes? Now is the time to have an open conversation around these intricacies. The following article, and a Q&A panel I am hosting next week hope to answer some of those questions. So here are some opening thoughts to get the dialogue rolling:
New Financial Reporting Web Studio and end of life for Web Analysis
Essbase allows for active/passive clustering of the servers for use in a failover or DR scenario. Oracle uses OPMN to handle the failover from one node to another in the event of a failure. The EPM Config tool, used to configure ESSBASE, does not update the OPMN.xml file correctly and needs to be manually updated as a post install step.
Since 2002 corporate reporting functions have been challenged continuously. None of us have been excused from increased controls and requirements on the content that businesses report to our stakeholders. If organizations are to deliver rapid and accurate financial close data they need to be able to control and improve the entire ‘extended’ financial close process. Top organizations recognize that the ‘close’ actually begins with sub ledgers and ends with the transfer of statutory filings; therefore are adopting integrated financial close solutions that address this whole process.