You may know what, but do you know why?

Many ERP Reporting solutions deliver multiple application views that are embedded within the system at no charge. Competing vendors sell application-specific views for a more costly charge. Typical report views are able to access the system layer within an application, but fall short when it comes to analyzing the core business layer of a corporation. The system layer merely offers data, while the business layer provides answers, and looks for insight as to why information is the way it is, which is the main goal of reporting.

Views, for the most part, are inextensible and cannot account for multiple contexts of data. How many times does the request of "can we add this segment to the current report" come to an IT department without being able to accommodate?

Views are also a poor means to aggregate data as they are often inefficient and consume server resources. Drill down capability is also impossible utilizing the same view as the aggregated view. How many times does the request of "can we get the detail behind this number" come to an IT department without being able to accommodate?

Why Kubes?

KBX=Y. For many of the same reasons that the Oracle® Database stores data in a relational format, the KBACE approach to reporting maintains a relational format to accommodate extensibility, aggregation, and ad-hoc query capability. While competitors sell multiple application views, KBACE is offering Kubes of data that incorporate the business layer of data a processed, relational format, providing insight as to why information is the way that it is.

Kubes:

• Extensible
• Aggregate Data (drill-down capability)
• Allow ad-hoc queries
• Incorporate the business layer within the solution

Views:

• Inextensible
• Cannot account for multiple contexts of data
• Have a poor way of aggregating data (no drill-down capability)
• Do not access the business layer of a corporation