The Reporting Hub is a standard web application that allows you to set up various tools to support business processes that are not (or cannot) be supported in your organisation’s standard system. We call this our “peg” tool.
The Reporting Hub is a standard web application that allows you to set up various tools to support business processes that are not (or cannot) be supported in your organisation’s standard system. We call this our “peg” tool, i.e. used to attach other applications to. The aim is usually to enable a certain level of operational, tactical and strategical reporting using information that is not available in existing systems.
As opposed to a normal hub (which is generally a “dumb machine”), a variety of functionality can be added to the Reporting Hub, making it really an intelligent hub.
We have already created a number of different solutions for our customers, based on this Reporting Hub. See below for some examples.
Our CIC Audit Tool was previously only available as a SaaS solution, where customers could upload their data via our website. Then – after a maximum of 3 days – the resulting analysis would become available, offering a snapshot of the customer’s security structure. We have now recreated CIC Audit Tool functionality in the Reporting Hub. This Reporting Hub is installed at the customer site, allowing them to decide when and how frequently an audit run should be performed. Additional functionality is also available in the Reporting Hub, such as comparing previous audit runs and monitoring mutations on suppliers’ bank account numbers. But the Reporting Hub can of course easily be extended and customised according to your specific requirements.
For one of our customers, we built a specific reporting, forecasting and consolidation (RFC) solution within the Reporting Hub. Such solutions are often available on the market (such as SAP BPC, Tagetik, Cognos TM1 or Oracle Hyperion), but these are generally large and comprehensive applications which for many of our customers prove to be too expensive to purchase and implement. We offered our customer a solution which we set up within the Reporting Hub relatively quickly. The reporting facility is based on Power Query technology, using the Reporting Hub database.
For another customer, we used the Reporting Hub to facilitate the recording of Capex information. Various types of information (such as description, budget, start date, end date) are recorded on a specific Capex ID. This ID is then available in Unit4 Financials (Coda) to record purchase orders related to Capex. Subsequently, SAP BusinessObjects reports on information from the Reporting Hub (Capex data), Unit4 Financials Procurement (accounts payable) and Financials (invoice and payment).
Internally within Diesis, we use the Reporting Hub for recording expenses (including a link to scanned receipts), resource planning and customer management.
We also see various possible uses in relation to the Unit4 Financials application. For example, it may not be appropriate or possible to record certain detail information in this application, but at the same time you wish to be able to report on such detail information in combination with Unit4 Financials data. Such a scenario would be easily facilitated with the Reporting Hub.
The Reporting Hub allows us to communicate with the Unit4 Financials database in a controlled way, so that we can use the hub to define web screens based on Unit4 Financials tables whose maintenance (e.g. browse, add, edit and delete rows) can also be performed in a controlled way with built-in validations.