All systems

SAP BusinessObjects

Business Objects data
Coming soon

Prepare

  1. Upload SAP BusinessObjects files
Guide

BusinessObjects is a business intelligence platform with a metadata-driven universe layer that defines semantic business models.

Planned Support

  • Universe metadata extraction (.unv files)
  • Report definition parsing (.rep files)
  • Relationship and dimension mapping
  • Business model documentation

What You Get Out

Once the parser ships, DataMeans will extract your data into multiple modern formats:

OutputDescription
csv/{TableName}.csvOne CSV file per table with all row data
xlsx/{TableName}.xlsxExcel workbook per table
xls/{TableName}.xlsLegacy Excel format per table
json/{TableName}.jsonJSON array of records per table
json/{TableName}.jsonlNewline-delimited JSON (streaming-friendly)
postgres.sqlPostgreSQL CREATE TABLE + INSERT statements
schema/schema-graph.jsonRelationship graph for visualization
schema/er-model.jsonER model for diagram tools
report.jsonStructured extraction report
report.mdHuman-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.


Last updated: January 2026

Technical reference

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 .unx universe format.
  • 2025: SAP BusinessObjects BI 2025 released, retiring the .unv universe 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

TypeDescriptionNotes
CharacterText stringsObject data type
NumberNumeric valuesObject data type
DateDate and time valuesObject data type
Long TextExtended text contentObject data type
DateTimeCombined date and time valuesBusiness layer data type (.unx)
BooleanTrue or false valuesBusiness layer data type (.unx)
BlobBinary large object contentBusiness layer data type (.unx)
DimensionFocus of analysis, such as customer or yearObject qualification
MeasureNumeric values aggregated by functions such as sum or countObject qualification
DetailDescriptive attribute associated with a dimensionObject qualification
AttributeDescriptive information attached to a dimension, hierarchy, measure, or levelObject 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

VersionYearKey ChangesCompatibility
4.01996OLAP supportFull-client .rep documents
6.52004Released alongside Crystal v10Final pre-XI platform release
XI2005Platform merged with Crystal EnterpriseInternal version 11.0
XI R22005Platform update (codename Jupiter)Internal version 11.5
XI 3.02008Platform update (codename Titan)Internal version 12.0
XI 3.12008Final XI-generation platform releaseInternal version 12.1
BI 4.02011Information Design Tool, .unx universesDesktop Intelligence (.rep) removed
BI 4.12013Desktop Intelligence Compatibility PackInternal version 14.1
BI 4.22016Parallel queries, BI CommentarySupports both .unv and .unx universes
BI 4.32020Redesigned BI Launch Pad, SAP Analytics Cloud integrationFlash-based Dashboards and Explorer removed
BI 20252025Year-based release naming.unv universes and Universe Design Tool removed

Compatibility Notes:

  • .unv universes can be converted to .unx using 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 .unx universes, so .unv content must be converted before upgrading
  • Only relational and stored-procedure .unv universes can be converted to .unx; OLAP .unv universes 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 .biar files created with the Import Wizard
  • Promotion Management in BI 4.x cannot import .biar files created in XI 3.1

Technical References


To learn how to use this format with DataMeans, see the User Guide.