Planned Support
- Universe metadata extraction (.unv files)
- Report definition parsing (.rep files)
- Relationship and dimension mapping
- Export to CSV, Excel, JSON, and SQL
BusinessObjects is a business intelligence platform with a metadata-driven universe layer that defines semantic business models.
Planned Support
- Universe metadata extraction (
.unvfiles) - Report definition parsing (
.repfiles) - Relationship and dimension mapping
- Business model documentation
What You Get Out
Once the parser ships, DataMeans will extract your data into multiple modern formats:
| Output | Description |
|---|---|
csv/{TableName}.csv | One CSV file per table with all row data |
xlsx/{TableName}.xlsx | Excel workbook per table |
xls/{TableName}.xls | Legacy Excel format per table |
json/{TableName}.json | JSON array of records per table |
json/{TableName}.jsonl | Newline-delimited JSON (streaming-friendly) |
postgres.sql | PostgreSQL CREATE TABLE + INSERT statements |
schema/schema-graph.json | Relationship graph for visualization |
schema/er-model.json | ER model for diagram tools |
report.json | Structured extraction report |
report.md | Human-readable extraction summary |
File Requirements
.unv(universe metadata).rep(report files)
Current Status
Parser development is in the planning phase. The complex proprietary format requires specialized reverse-engineering.
Technical Notes
BusinessObjects universes contain complex expression language for calculated members and relationships. Documentation became fragmented after SAP acquisition.
Overview
SAP BusinessObjects is an enterprise business intelligence and analytics platform that provides self-service reporting, dashboards, and data visualization capabilities. It employs a semantic layer architecture with "universes" that create abstracted business views of underlying data sources, supporting OLAP analysis, ad-hoc queries, and complex calculations. Unlike traditional databases, BusinessObjects focuses on metadata-driven reporting with proprietary formats for storing business logic, data relationships, and presentation layers in enterprise environments.
History and Background
- 1990: Business Objects founded in France by Bernard Liautaud and Denis Payre; its first product, Skipper SQL 2.0, ships the same year.
- 1994: BusinessObjects 3.0 released; the company lists on the NASDAQ, the first French software company on a United States exchange.
- 1996: BusinessObjects 4.0 released as the company enters the OLAP market.
- 1997: WebIntelligence thin client introduced for web-based reporting.
- 2000: Business Objects acquires OLAP@Work for approximately $15 million.
- 2002: Business Objects acquires Acta Technologies.
- 2003: BusinessObjects Enterprise 6 released.
- 2003: Business Objects acquires Crystal Decisions for $820 million.
- 2004: Crystal v10 and BusinessObjects 6.5 released.
- 2005: BusinessObjects XI released, built on the Crystal Enterprise platform; BusinessObjects Enterprise XI Release 2 follows the same year.
- 2007: SAP announces its acquisition of Business Objects for $6.8 billion; the deal completes in January 2008.
- 2011: SAP BusinessObjects BI 4.0 released with the Information Design Tool and the
.unxuniverse format. - 2025: SAP BusinessObjects BI 2025 released, retiring the
.unvuniverse format and the Universe Design Tool.
File Format Specifications
BusinessObjects stores universes and report documents in proprietary formats managed through a central repository.
File Extensions:
.unv- Universe created with the Universe Design Tool (semantic layer).unx- Universe created with the Information Design Tool (BI 4.0 and later).rep- Desktop Intelligence report document.wid- Web Intelligence document.biar- Business Intelligence Archive Resource for content import and export.blx- Business layer resource in an Information Design Tool local project.dfx- Data foundation resource in an Information Design Tool local project.cnx- Local connection stored in an Information Design Tool project.cns- Connection shortcut referencing a connection published to the repository.lcmbiar- Life Cycle Management archive used by Promotion Management in BI 4.x
File Structure:
- Universe (
.unv): Proprietary binary file defining classes, objects, and joins - Universe (
.unx): Compiled from a business layer, data foundation, and connection resources - Report (
.rep): Desktop Intelligence document with query definitions and layout - WebI (
.wid): Web Intelligence document containing queries, data, and report layout - Security: Access control through CMS (Central Management Server)
- Connections: Metadata for data source connections stored in the repository
Key Components:
- Classes: Business groupings of objects
- Objects: Dimensions, measures, and details
- Joins: Relationships between tables in the schema
- Contexts: Resolve join path ambiguities
- Prompts: User-defined query parameters
- Derived tables: Virtual tables defined by an SQL expression rather than a physical table
- Lists of values: Data values associated with an object, used to choose values in query filters
Data Types and Structures
| Type | Description | Notes |
|---|---|---|
| Character | Text strings | Object data type |
| Number | Numeric values | Object data type |
| Date | Date and time values | Object data type |
| Long Text | Extended text content | Object data type |
| DateTime | Combined date and time values | Business layer data type (.unx) |
| Boolean | True or false values | Business layer data type (.unx) |
| Blob | Binary large object content | Business layer data type (.unx) |
| Dimension | Focus of analysis, such as customer or year | Object qualification |
| Measure | Numeric values aggregated by functions such as sum or count | Object qualification |
| Detail | Descriptive attribute associated with a dimension | Object qualification |
| Attribute | Descriptive information attached to a dimension, hierarchy, measure, or level | Object qualification in .unx universes |
Semantic Model:
- Universes provide business terminology over technical schemas
- Classes organize related objects hierarchically
- Objects can be dimensions (grouping), measures (calculations), or details
- Predefined conditions and filters restrict query results
- Hierarchies support drill-down analysis
Version Differences
| Version | Year | Key Changes | Compatibility |
|---|---|---|---|
| 4.0 | 1996 | OLAP support | Full-client .rep documents |
| 6.5 | 2004 | Released alongside Crystal v10 | Final pre-XI platform release |
| XI | 2005 | Platform merged with Crystal Enterprise | Internal version 11.0 |
| XI R2 | 2005 | Platform update (codename Jupiter) | Internal version 11.5 |
| XI 3.0 | 2008 | Platform update (codename Titan) | Internal version 12.0 |
| XI 3.1 | 2008 | Final XI-generation platform release | Internal version 12.1 |
| BI 4.0 | 2011 | Information Design Tool, .unx universes | Desktop Intelligence (.rep) removed |
| BI 4.1 | 2013 | Desktop Intelligence Compatibility Pack | Internal version 14.1 |
| BI 4.2 | 2016 | Parallel queries, BI Commentary | Supports both .unv and .unx universes |
| BI 4.3 | 2020 | Redesigned BI Launch Pad, SAP Analytics Cloud integration | Flash-based Dashboards and Explorer removed |
| BI 2025 | 2025 | Year-based release naming | .unv universes and Universe Design Tool removed |
Compatibility Notes:
.unvuniverses can be converted to.unxusing the Information Design Tool- Desktop Intelligence (
.rep) documents require conversion to Web Intelligence (.wid) via the Report Conversion Tool - BI 4.1 added a Desktop Intelligence Compatibility Pack, discontinued in BI 4.3
- BI 2025 supports only
.unxuniverses, so.unvcontent must be converted before upgrading - Only relational and stored-procedure
.unvuniverses can be converted to.unx; OLAP.unvuniverses must be rebuilt in the Information Design Tool - The Upgrade Management Tool imports XI Release 2 and XI 3.x content into BI 4.x, including
.biarfiles created with the Import Wizard - Promotion Management in BI 4.x cannot import
.biarfiles created in XI 3.1
Technical References
- SAP BusinessObjects Business Intelligence Platform Documentation
- Wikipedia: BusinessObjects
- Universe Design Tool User Guide
- Information Design Tool User Guide
- SAP Community: BusinessObjects Business Intelligence
To learn how to use this format with DataMeans, see the User Guide.
Not available for hosted uploads. This system is read over a direct database connection by the DataMeans Agent, which is still in development. Contact us to plan a migration.
Can I convert SAP BusinessObjects databases with DataMeans today?
Not yet. SAP BusinessObjects is not available for self-serve upload, and support is still in development. Get in touch and we'll tell you where it stands and help plan the migration.
What will DataMeans convert SAP BusinessObjects databases to?
Once SAP BusinessObjects is available, exports will match every other system we support: clean CSV, Excel, JSON & SQL, one file per table, with a structured report of exactly what was extracted.
Is my data secure?
Yes. Your files are encrypted in transit and at rest, and are automatically deleted once your conversion is complete. Your data is never sold, shared, or used for anything else.