SAP BusinessObjects - Lineage

This document outlines the lineage coverage, configuration requirements, metadata handling, supported scenarios, component behavior, transformation coverage, and known limitations for lineage extraction in SAP BusinessObjects. The SAP BusinessObjects connector provides production-ready lineage extraction across Crystal Reports, Web Intelligence (WebI), Universes, SQL queries, formulas, variables, and subreports. It supports both report-level and column-level lineage to provide visibility into data flow from source databases and semantic layers to business intelligence reports.

Lineage Configuration Requirements

Accurate lineage extraction depends on access to the SAP BusinessObjects Central Management Server (CMS), repository metadata, report source files, Universe metadata, and supported SQL definitions. The required authentication and lineage resolution configurations must be available before lineage generation.

Configuration Requirements Table

Configuration	Required Detail
CMS and Repository Access	Access to the SAP BusinessObjects CMS and repository is required for metadata extraction
Universe JSON	Universe JSON must be available for WebI lineage
Authentication	Authentication through secEnterprise or secWinAD is required
Connection Priority	Connection priority must be defined for lineage resolution
SQL Dialect	SQL dialect configuration is required for SQL parsing
Report Source	Access to report source files in XML or JSON format is mandatory

Missing CMS or repository access, unavailable Universe JSON, inaccessible report source files, or incomplete connection information may result in incomplete lineage generation or source-target resolution.

Lineage Components

The SAP BusinessObjects connector supports lineage extraction across Crystal Reports, WebI reports, Universes, SQL queries, report components, and supported transformation types.

Component Support Matrix

Component / Feature	Availability
Crystal Reports	✅
WebI Reports	✅
Universe (UNX/UNV)	✅
Command SQL Queries	✅
Tables & Columns	✅
Formula Fields	✅
WebI Variables	✅
Subreports	✅
Stored Procedures	⚠️
Derived Tables	⚠️
Multi-database Reports	⚠️
Relationships (Joins)	⚠️
Parameters	⚠️
BEx Queries	❌

The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.

Column Creation Support

The SAP BusinessObjects connector supports column-level lineage for direct mappings, aliases, formula fields, WebI variables, and supported report transformations. Complex calculations, conditional expressions, and certain aggregation scenarios may provide partial lineage coverage.

Column Creation from Lineage

Transformation Type	Supported
Direct Column Mapping	✅
Aliasing (Rename Columns)	✅
Formula Fields	✅
WebI Variables	✅
Aggregations (SUM, COUNT)	⚠️
Conditional Logic (CASE/IF)	⚠️
String/Date Functions	⚠️
Running Totals	✅

The ⚠️ icon indicates partially supported functionality with limited column-level lineage coverage in applicable scenarios.

Supported Use Cases

The SAP BusinessObjects connector supports lineage extraction across Crystal Reports, WebI reports, Universes, SQL-based reports, report calculations, and report dependencies.

Supported Lineage Scenarios

Supported Scenario	Details
Crystal Reports → Table & Column Lineage	Lineage from Crystal Reports to source tables and columns
Command SQL → Query-based Lineage	Lineage extraction from Command SQL queries to source database objects
WebI (Universe) → Semantic Layer Lineage	Lineage across WebI reports and the associated semantic layer
WebI Free-hand SQL → Direct Query Lineage	Direct lineage from WebI Free-hand SQL queries to source objects
Universe (UNX/UNV) → Object-to-Table Mapping	Mapping between Universe objects and underlying database tables
Subreport Lineage Integration	Lineage extraction across supported subreport dependencies
Stored Procedures → Lineage Extraction	Lineage extraction from supported stored procedure-based report sources
Formula Fields and Variables → Expression Lineage	Lineage for supported formula fields and WebI variables
Filters and Parameters → Lineage Context	Filters and parameters are captured as part of the lineage context

Lineage extraction depends on available CMS metadata, repository information, Universe metadata, report source files, SQL definitions, and supported BusinessObjects components.

Partial or Limited Coverage

Certain BusinessObjects report components and transformation patterns provide partial lineage coverage. Limitations primarily apply to complex calculations, dynamic SQL, cross-database dependencies, and scenarios where required metadata is unavailable.

Scenarios

Scenario	Limitation Description
Calculated Fields	Complex expressions may not fully resolve
Derived Columns	Multi-step transformation logic is partially supported
Aggregations	Aggregation operations may not be explicitly tracked in all scenarios
Dynamic SQL	Parameter resolution is limited
Cross-database Queries	Source and target mapping may be partial
BEx Queries	Limited support is available
Complex Nested Formulas	Complex formulas may require manual validation
Dataset Lineage	Lineage status may be incomplete when required metadata is missing

Complex formulas, dynamic SQL, cross-database queries, and incomplete metadata may result in incomplete lineage paths or reduced column-level lineage accuracy.

Unsupported Scenarios

The connector does not provide complete lineage coverage for certain BusinessObjects configurations and external processing patterns where source metadata or dependency information cannot be resolved.

Unsupported Lineage

Not Supported	Impact	Workaround
Missing Universe JSON	WebI lineage cannot be generated	Provide the required Universe JSON
Cross-Universe Relationships	Relationships between Universes are not tracked	Document cross-Universe dependencies separately
Encrypted Connections Without Decryption	Schema resolution fails	Provide accessible connection metadata
Custom SDK-based Report Logic	Custom report logic is not captured in lineage	Document custom dependencies separately
External Script-based Transformations	Transformations outside SAP BusinessObjects are not captured	Document external transformations separately
Highly Complex Multi-step Calculations	Complete dependency resolution may not be available	Validate and document complex calculations separately
Dynamic Column References	Runtime-generated column references are not resolved	Use statically defined column references where applicable

Unsupported scenarios do not produce complete lineage and may appear disconnected in lineage visualization.

Current Functional Status

The SAP BusinessObjects connector provides strong lineage coverage across Crystal Reports, WebI reports, Universes, SQL queries, formulas, variables, and subreports. It supports report-level and column-level lineage for standard BusinessObjects reporting and semantic-layer scenarios. Advanced calculations, dynamic SQL, cross-database relationships, and certain external or runtime-dependent dependencies have partial or unsupported coverage.

Status Area	Details
Overall Coverage	Partial coverage across Crystal Reports, WebI, Universes, SQL queries, and supported report components
Lineage Depth	Strong report-level and column-level lineage for supported BusinessObjects workloads
Supported Inputs	Crystal Reports, WebI reports, UNX/UNV Universes, Command SQL queries, tables, columns, formulas, variables, and subreports
Functional Scope	Lineage extraction across supported report, semantic-layer, query, and transformation dependencies
Column-level Coverage	Direct mappings, aliases, formula fields, WebI variables, and supported transformations
Limitation Areas	Dynamic SQL, complex formulas, derived columns, aggregations, cross-database queries, BEx queries, and missing metadata
Resulting Output	Production-ready lineage for supported SAP BusinessObjects workloads with partial coverage for advanced reporting and transformation scenarios

The SAP BusinessObjects connector provides production-ready lineage across Crystal Reports, WebI, Universes, SQL queries, formulas, variables, and subreports, with strong report-level and column-level lineage support. Coverage remains partial for dynamic SQL, complex formulas, cross-database relationships, and advanced transformation scenarios that depend on runtime behavior or unavailable metadata.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA