> 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/release8.1/connectors/connector-repositories/etl-tool/informatica-intelligent-cloud-services/informatica-intelligent-cloud-services-lineage.md).

# Informatica Intelligent Cloud Services - Lineage

This article outlines the lineage coverage, configuration requirements, component support, transformation handling, supported scenarios, and known limitations for lineage extraction in Informatica Intelligent Cloud Services (IICS). The IICS connector provides automated lineage extraction for cloud-based ETL mappings using REST APIs. It tracks data dependencies across sources, transformations, and targets to provide end-to-end visibility into data flows. The connector supports parameterized mappings, SQL override parsing, and column-level lineage across supported data pipelines, enabling data flow analysis and impact assessment.

## Lineage Configuration Requirements

Accurate lineage extraction depends on access to the IICS Base URL, REST APIs, and a valid session or authentication token. Mapping Templates, Tasks, and Connections must be crawled to retrieve the metadata required for lineage resolution.

SQL dialect configuration is required for accurate parsing of SQL override queries and transformation logic. Parameter files must be available for substituting `$$` variables in parameterized mappings. Proxy configuration must also be provided where applicable. Source and target connection metadata must be pre-crawled to support physical object and column resolution.

### Configuration Requirements Table

<table data-search="false"><thead><tr><th width="177.58984375">Configuration</th><th width="604.47265625">Required Detail</th></tr></thead><tbody><tr><td>IICS Base URL</td><td>The IICS Base URL must be configured to establish connectivity with the IICS environment.</td></tr><tr><td>REST API Access</td><td>REST API access is required to retrieve mapping, task, connection, and associated metadata.</td></tr><tr><td>Authentication</td><td>A valid session or authentication token must be available for API access.</td></tr><tr><td>Mapping Templates</td><td>Mapping Templates must be crawled to retrieve mapping definitions and transformation metadata.</td></tr><tr><td>Tasks</td><td>Associated IICS Tasks must be crawled to identify mapping execution configurations and dependencies.</td></tr><tr><td>Connections</td><td>IICS Connections must be crawled to retrieve source and target connection metadata.</td></tr><tr><td>SQL Dialect Configuration</td><td>The supporting SQL dialect must be configured correctly for SQL override parsing.</td></tr><tr><td>Parameter Files</td><td>Parameter files must be available for <code>$$</code> variable substitution in parameterized mappings.</td></tr><tr><td>Proxy Configuration</td><td>Proxy settings must be configured where required for REST API connectivity.</td></tr><tr><td>Source and Target Metadata</td><td>Source and target connection metadata must be pre-crawled in OvalEdge for physical object and column resolution.</td></tr></tbody></table>

{% hint style="warning" %}
Missing REST API access, invalid authentication tokens, incomplete Mapping Template metadata, unavailable parameter files, or uncrawled source and target connections may result in incomplete lineage extraction or inaccurate source-to-target resolution.
{% endhint %}

## Lineage Components

The IICS connector supports lineage extraction across cloud-based ETL Mapping Templates, relational and file-based sources and targets, and supported transformation components. It analyzes mapping definitions, SQL override queries, parameterized mappings, and transformation metadata to identify dependencies between source and target objects.

### Component Support Matrix

<table data-search="false"><thead><tr><th>Component / Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>Sources (Relational / File)</td><td align="center">✅</td></tr><tr><td>Targets (Relational / File)</td><td align="center">✅</td></tr><tr><td>Lookup Transformation</td><td align="center">✅</td></tr><tr><td>Expression Transformation</td><td align="center">✅</td></tr><tr><td>Filter Transformation</td><td align="center">⚠️</td></tr><tr><td>Aggregator</td><td align="center">⚠️</td></tr><tr><td>Joiner</td><td align="center">⚠️</td></tr><tr><td>Union</td><td align="center">⚠️</td></tr><tr><td>Override Queries (Sources)</td><td align="center">✅</td></tr><tr><td>Override Queries (Lookups)</td><td align="center">⚠️</td></tr><tr><td>Stored Procedure Transformation</td><td align="center">❌</td></tr><tr><td>Parameterized Mappings</td><td align="center">✅</td></tr><tr><td>Temporary Tables</td><td align="center">✅</td></tr><tr><td>Temporary Files</td><td align="center">✅</td></tr><tr><td>Cloud Warehouse Connections</td><td align="center">✅</td></tr><tr><td>NoSQL / API Connectors</td><td align="center">⚠️</td></tr></tbody></table>

{% hint style="warning" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios. The ❌ icon indicates functionality that is not supported for lineage extraction.
{% endhint %}

### Column Creation Support

The IICS connector supports column-level lineage across supported mapping transformations, SQL override queries, lookup transformations, and intermediate objects. It identifies direct column mappings, aliases, lookup columns, and SQL override columns.

Expression columns, aggregated columns, and conditional columns provide partial lineage coverage depending on the transformation logic and the availability of metadata through the REST APIs. Temporary table columns and file columns are supported, while stored procedure columns are not supported.

#### **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>Expression Columns</td><td align="center">⚠️</td></tr><tr><td>SQL Override Columns</td><td align="center">✅</td></tr><tr><td>Lookup Columns</td><td align="center">✅</td></tr><tr><td>Alias Resolution</td><td align="center">✅</td></tr><tr><td>Aggregated Columns</td><td align="center">⚠️</td></tr><tr><td>Conditional Columns</td><td align="center">⚠️</td></tr><tr><td>Temporary Table Columns</td><td align="center">✅</td></tr><tr><td>File Columns</td><td align="center">✅</td></tr><tr><td>Stored Procedure Columns</td><td align="center">❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality. Expression, aggregation, and conditional column lineage depend on the availability of transformation metadata and the ability to resolve the associated expressions.
{% endhint %}

## Supported Use Cases

The IICS connector supports lineage extraction across cloud-based ETL mappings involving relational and file-based sources and targets. It tracks dependencies across supported transformations, parameterized mappings, SQL override queries, and intermediate objects.

### Supported Lineage Scenarios

<table data-search="false"><thead><tr><th width="241.62109375">Supported Scenario</th><th width="552.44140625">Details</th></tr></thead><tbody><tr><td>Database → Database ETL Lineage</td><td>Lineage extraction between relational database sources and targets across supported ETL mappings.</td></tr><tr><td>File → Database Lineage</td><td>Lineage extraction from file-based sources to database targets.</td></tr><tr><td>Parameterized Mappings</td><td>Lineage extraction across mappings that use <code>$$</code> variables for parameter substitution.</td></tr><tr><td>Custom SQL Override Lineage</td><td>Lineage extraction from supported source SQL override queries.</td></tr><tr><td>Lookup Transformations</td><td>Lineage extraction across supported Lookup transformations and associated source and target columns.</td></tr><tr><td>Multi-Source → Single-Target Mappings</td><td>Lineage tracking from multiple source objects to a single target through supported mapping transformations.</td></tr><tr><td>Column-Level Lineage</td><td>Column-level dependency tracking across supported mapping transformations.</td></tr><tr><td>Cloud Warehouse Integrations</td><td>Lineage extraction across supported cloud warehouse connections.</td></tr><tr><td>Temporary Table Lineage</td><td>Lineage tracking across temporary tables used in intermediate transformations.</td></tr><tr><td>Temporary File Lineage</td><td>Lineage tracking across temporary files used in intermediate transformations.</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction depends on accessible IICS Mapping Template metadata, valid REST API connectivity, correctly configured SQL dialects, available parameter files, and pre-crawled source and target connection metadata.
{% endhint %}

## Partial or Limited Coverage

Certain IICS transformation components and query patterns provide partial lineage coverage. Limitations primarily apply to Lookup override queries, dynamic SQL, aggregation logic, Joiner and Union transformations, conditional expressions, and non-relational connections.

### Scenarios

<table data-search="false"><thead><tr><th width="217.24609375">Scenario</th><th width="585.53515625">Limitation Description</th></tr></thead><tbody><tr><td>Lookup Override Queries</td><td>Lookup override query parsing logic is available in the code but is currently disabled.</td></tr><tr><td>Dynamic SQL</td><td>Complex parameterized SQL queries may not be fully parsed, resulting in incomplete lineage.</td></tr><tr><td>Column-Level Lineage</td><td>Column-level lineage coverage depends on the availability and completeness of metadata retrieved through REST APIs.</td></tr><tr><td>Aggregations</td><td>Parsing of aggregation logic is limited and may not capture all source-to-target column dependencies.</td></tr><tr><td>Join and Union Logic</td><td>Join and Union logic is embedded in the mapping definitions but is not explicitly tracked in all scenarios.</td></tr><tr><td>Conditional Logic</td><td>Conditional transformation logic is stored in the mapping metadata but is not fully interpreted for lineage extraction.</td></tr><tr><td>Non-RDBMS Connections</td><td>Schema resolution for non-relational connections may be inconsistent.</td></tr><tr><td>Encrypted Parameters</td><td>Encrypted parameters cannot be decrypted for variable substitution.</td></tr><tr><td>SaaS / API-Based Connectors</td><td>Testing coverage is limited for SaaS and API-based connectors.</td></tr><tr><td>Expression Transformations</td><td>Complex expressions may provide incomplete column-level lineage depending on the available metadata and parsing support.</td></tr></tbody></table>

{% hint style="warning" %}
Partial coverage may result in incomplete column-level lineage or limited source-to-target dependency resolution. Complex parameterized SQL, aggregation logic, conditional expressions, and non-relational connections may require manual validation.
{% endhint %}

## Unsupported Scenarios

The IICS connector does not provide lineage coverage for stored procedure transformations, non-Mapping Template objects, dynamically generated columns, encrypted or obfuscated mappings, and complex NoSQL or API-based integrations.

### Unsupported Lineage

<table data-search="false"><thead><tr><th width="196.078125">Not Supported</th><th width="328.5625">Impact</th><th width="305.8984375">Workaround</th></tr></thead><tbody><tr><td>Stored Procedure Transformations</td><td>Lineage extraction from stored procedure transformations is not supported.</td><td>Document stored procedure dependencies separately.</td></tr><tr><td>Non-Mapping Template Objects</td><td>Objects outside the Mapping Template scope do not provide lineage coverage.</td><td>Document dependencies outside Mapping Templates separately.</td></tr><tr><td>Dynamic Runtime-Generated Columns</td><td>Columns generated dynamically at runtime cannot be resolved for lineage extraction.</td><td>Use explicitly defined column mappings wherever possible.</td></tr><tr><td>Encrypted / Obfuscated Mappings</td><td>Mapping definitions that are encrypted or obfuscated cannot be fully analyzed for lineage extraction.</td><td>Provide accessible mapping definitions where supported.</td></tr><tr><td>Complex NoSQL / API Integrations</td><td>Full lineage extraction for complex NoSQL and API-based integrations is not supported.</td><td>Document external source and target dependencies separately.</td></tr><tr><td>Advanced Transformation Logic</td><td>Advanced transformation logic that cannot be resolved through supported parsing is not fully captured.</td><td>Manually validate and document the affected transformation dependencies.</td></tr><tr><td>Cross-Mapping Dependencies Beyond Template Scope</td><td>Dependencies extending beyond the Mapping Template scope are not captured.</td><td>Document cross-mapping dependencies separately.</td></tr></tbody></table>

{% hint style="warning" %}
Unsupported components and configurations do not provide complete lineage coverage and may result in incomplete or disconnected lineage paths.
{% endhint %}

## Current Functional Status

The IICS connector provides partial lineage coverage across supported IICS Mapping Templates, sources, targets, and transformation components. It supports REST-based metadata extraction, parameterized mappings, source SQL override parsing, and column-level lineage across supported ETL transformations.

The connector supports relational and file-based sources and targets, Lookup and Expression transformations, temporary tables, temporary files, and cloud warehouse connections. It also supports direct column mapping, SQL override columns, lookup columns, alias resolution, and parameterized mappings using `$$` variables.

Partial coverage applies to Filter, Aggregator, Joiner, and Union transformations, Lookup override queries, dynamic SQL, conditional logic, and non-relational connections. Stored procedure transformations, dynamic runtime-generated columns, encrypted or obfuscated mappings, and full lineage for complex NoSQL and API-based integrations are not supported.

### Functional Status Summary

<table data-search="false"><thead><tr><th width="182.97265625">Status Area</th><th width="604.76953125">Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Partial lineage coverage across supported IICS Mapping Templates, sources, targets, and transformation components.</td></tr><tr><td>Lineage Depth</td><td>Table-level and column-level lineage across supported ETL mappings and intermediate transformation objects.</td></tr><tr><td>Supported Inputs</td><td>IICS Mapping Templates, Tasks, Connections, relational and file-based sources, targets, SQL override queries, and parameterized mappings.</td></tr><tr><td>Functional Scope</td><td>Automated lineage extraction across supported cloud-based ETL mappings, transformations, and source-to-target dependencies using REST APIs.</td></tr><tr><td>Column-Level Coverage</td><td>Direct column mappings, SQL override columns, lookup columns, alias resolution, temporary table columns, and file columns.</td></tr><tr><td>Transformation Support</td><td>Lookup and Expression transformations, with partial coverage for Filter, Aggregator, Joiner, and Union transformations.</td></tr><tr><td>Limitation Areas</td><td>Lookup override queries, dynamic SQL, aggregations, conditional logic, non-RDBMS connections, encrypted parameters, and SaaS/API-based connector testing.</td></tr><tr><td>Unsupported Areas</td><td>Stored procedure transformations, non-Mapping Template objects, dynamic runtime-generated columns, encrypted or obfuscated mappings, complex NoSQL/API integrations, and cross-mapping dependencies beyond template scope.</td></tr><tr><td>Resulting Output</td><td>Partial table-level and column-level lineage across supported IICS Mapping Templates, sources, targets, and transformations, with limited coverage for complex transformation logic and external dependencies.</td></tr></tbody></table>

{% hint style="warning" %}
The IICS connector provides production-ready lineage extraction across supported Mapping Templates using REST-based metadata extraction, parameter handling, SQL parsing, and column-level lineage. Coverage depends on the completeness of REST API metadata, available parameter files, and pre-crawled source and target connection metadata. Manual validation may be required for Lookup override queries, dynamic SQL, complex aggregation and conditional logic, and non-relational integrations.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/etl-tool/informatica-intelligent-cloud-services/informatica-intelligent-cloud-services-lineage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
