> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/sap-businessobjects/sap-businessobjects-lineage.md).

# 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

<table data-search="false"><thead><tr><th width="240.1328125">Configuration</th><th width="538.3203125">Required Detail</th></tr></thead><tbody><tr><td>CMS and Repository Access</td><td>Access to the SAP BusinessObjects CMS and repository is required for metadata extraction</td></tr><tr><td>Universe JSON</td><td>Universe JSON must be available for WebI lineage</td></tr><tr><td>Authentication</td><td>Authentication through <code>secEnterprise</code> or <code>secWinAD</code> is required</td></tr><tr><td>Connection Priority</td><td>Connection priority must be defined for lineage resolution</td></tr><tr><td>SQL Dialect</td><td>SQL dialect configuration is required for SQL parsing</td></tr><tr><td>Report Source</td><td>Access to report source files in XML or JSON format is mandatory</td></tr></tbody></table>

{% hint style="warning" %}
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.
{% endhint %}

## 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

<table data-search="false"><thead><tr><th>Component / Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>Crystal Reports</td><td align="center">✅</td></tr><tr><td>WebI Reports</td><td align="center">✅</td></tr><tr><td>Universe (UNX/UNV)</td><td align="center">✅</td></tr><tr><td>Command SQL Queries</td><td align="center">✅</td></tr><tr><td>Tables &#x26; Columns</td><td align="center">✅</td></tr><tr><td>Formula Fields</td><td align="center">✅</td></tr><tr><td>WebI Variables</td><td align="center">✅</td></tr><tr><td>Subreports</td><td align="center">✅</td></tr><tr><td>Stored Procedures</td><td align="center">⚠️</td></tr><tr><td>Derived Tables</td><td align="center">⚠️</td></tr><tr><td>Multi-database Reports</td><td align="center">⚠️</td></tr><tr><td>Relationships (Joins)</td><td align="center">⚠️</td></tr><tr><td>Parameters</td><td align="center">⚠️</td></tr><tr><td>BEx Queries</td><td align="center">❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## 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

<table data-search="false"><thead><tr><th>Transformation Type</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Direct Column Mapping</td><td align="center">✅</td></tr><tr><td>Aliasing (Rename Columns)</td><td align="center">✅</td></tr><tr><td>Formula Fields</td><td align="center">✅</td></tr><tr><td>WebI Variables</td><td align="center">✅</td></tr><tr><td>Aggregations (SUM, COUNT)</td><td align="center">⚠️</td></tr><tr><td>Conditional Logic (CASE/IF)</td><td align="center">⚠️</td></tr><tr><td>String/Date Functions</td><td align="center">⚠️</td></tr><tr><td>Running Totals</td><td align="center">✅</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited column-level lineage coverage in applicable scenarios.
{% endhint %}

## 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

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

{% hint style="info" %}
Lineage extraction depends on available CMS metadata, repository information, Universe metadata, report source files, SQL definitions, and supported BusinessObjects components.
{% endhint %}

## 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

<table data-search="false"><thead><tr><th width="229.72265625">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>Calculated Fields</td><td>Complex expressions may not fully resolve</td></tr><tr><td>Derived Columns</td><td>Multi-step transformation logic is partially supported</td></tr><tr><td>Aggregations</td><td>Aggregation operations may not be explicitly tracked in all scenarios</td></tr><tr><td>Dynamic SQL</td><td>Parameter resolution is limited</td></tr><tr><td>Cross-database Queries</td><td>Source and target mapping may be partial</td></tr><tr><td>BEx Queries</td><td>Limited support is available</td></tr><tr><td>Complex Nested Formulas</td><td>Complex formulas may require manual validation</td></tr><tr><td>Dataset Lineage</td><td>Lineage status may be incomplete when required metadata is missing</td></tr></tbody></table>

{% hint style="info" %}
Complex formulas, dynamic SQL, cross-database queries, and incomplete metadata may result in incomplete lineage paths or reduced column-level lineage accuracy.
{% endhint %}

## 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

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

{% hint style="info" %}
Unsupported scenarios do not produce complete lineage and may appear disconnected in lineage visualization.
{% endhint %}

## 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.

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

{% hint style="info" %}
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.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/sap-businessobjects/sap-businessobjects-lineage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.