Complete Flexibility

Meta Data is the Key — iNet.BI does not just provide .NET data sets. For all SAP Info Objects it provides the Meta Views behind the data sets. Thus iNet.BI is also a Meta Provider. Meta Provisioning is what enables the data to be auto-transformed as OLAP ready, it is what enables the iNet.BI-BW Provider to auto-generate mdx sub queries for the user, and it is also what enables the iNet.BI Providers to auto-create SQL Server Tables for the delivered object sets. Meta Provisioning also streamlines and accelerates the creation of new Report Presentation Views.

Existing Info Assets — Your SAP system already has hundreds of existing Report Programs and Query Object Reports. Why not reuse them? The data and business definitions are already pre-determined for you; aggregations, etc. are already performed. The presentation component may or not be of interest but the data extract definitions are.

When it comes to creating new extract definitions report developers rarely know the underlying database schema of their SAP system. This schema is comprised of transparent, cluster, and pool tables, many of which cannot be accessed using traditional database tools like SQL Server Workbench. Others, such as HR payroll clusters are currently not accessible via traditional DBconnect methods.

Programmer-less Object Builder Wizards — In your SAP system are robust report writer and Query builder tool and wizard sets that can be even used by a business analyst. Within those tools are all the schema views and table associations you need, even those which are not viewable externally to the SAP system as previously explained. With the SAP wizards the new provider object can be set-up in just minutes, and then published to the standard SAP repository where they are accessible to the iNet.BI Providers.

BAPIs — The ones in your SAP system may have predefined business data views that are good-to-go and iNet.BPS can be used with those. But what if the BAPI you need is not there? Do you have the ABAP developer resources available to customize or write new ones? Instead, with iNet.BI you have the option to quickly create a new info Object based on Query or Report objects instead of waiting for custom ABAP to be written.

Reflect SAPGUI Reporting in a Portal — iNet.BI also allows the full Query and SAP Reporting framework to be used from a Portal. The SAP objects are executed just as if the user where inside SAP, however no SAPGUI is required, the result views can be held in the Portal document repository for other users and collaboration purposes. In this form the default data views mirror what they look like in SAPGUI.

Enhanced Reporting Views and Services — More flexible and user friendly presentation than is seen in SAPGUI, plus flexible distribution can be had, by linking the SAP info objects of choice to MS Reporting Services or any MS friendly Reporting/OLAP engine.