## What does Atlan crawl from SAP BW/4HANA?

URL: https://docs.atlan.com/apps/connectors/erp/sap-bw4hana/references/what-does-atlan-crawl-from-sap-bw4hana

> During a SAP BW/4HANA crawl, Atlan extracts metadata for InfoAreas, providers, DataSources, InfoObjects, queries, transformations, and DTPs.

# What does Atlan crawl from SAP BW/4HANA? 

Atlan integrates with SAP BW/4HANA to crawl and map BW data warehouse assets—from logical groupings (InfoAreas) down through providers (ADSOs, CompositeProviders), data acquisition (DataSources, InfoSources), reusable characteristics (InfoObjects), and analytic objects (Queries)—along with the transformations and DTPs that move data between them. This page outlines the supported asset types, the source-to-Atlan property mappings, and the lineage relationships Atlan builds.

## Lineage

Atlan builds two layers of lineage from SAP BW/4HANA:

- **Asset lineage:** From source provider → target provider via transformations, and from query → underlying provider.
- **Column-level lineage:** From source field → target field for each rule defined inside a transformation.

## Assets

Atlan extracts metadata from SAP BW/4HANA across the following asset types:

- **[InfoAreas](#infoareas):** Hierarchical folders that organize BW objects.
- **[InfoObjects](#infoobjects):** Reusable characteristics, key figures, and units that describe business entities and measures.
- **[Data sources](#data-sources):** Source-system extraction structures that bring data into BW.
- **[Data source fields](#data-source-fields):** Individual fields exposed by a DataSource.
- **[InfoSources](#infosources):** Logical layers that decouple DataSources from providers.
- **[InfoSource fields](#infosource-fields):** Fields defined on an InfoSource.
- **[ADSOs](#adso-fields):** Advanced DataStore Objects—the primary persistence layer in BW/4HANA.
- **[ADSO fields](#adso-field-details):** Columns of an ADSO.
- **[CompositeProviders](#compositeprovider-fields):** Virtual providers that union or join ADSOs and other providers.
- **[CompositeProvider fields](#compositeprovider-field-details):** Output columns of a CompositeProvider.
- **[Queries](#queries):** BEx and Eclipse-modeled analytic queries.
- **[Query elements](#query-elements):** Elements (selections, formulas, restricted key figures, conditional InfoObjects) inside a Query.
- **[Transformations](#transformations):** Source → target mapping logic between BW providers.
- **[DTPs](#data-transfer-processes):** Data Transfer Processes.

The following sections detail how each asset type is mapped in Atlan.

### InfoAreas

InfoAreas are folders that group related BW objects (InfoObjects, providers, queries) by business domain. Atlan maps InfoAreas to its `SAPBWInfoArea` asset type.

| Source property | Atlan property |
| --- | --- |
| `INFOAREA` | `name` |
| `TXTLG` | `description` |
| `OWNER` | `sourceCreatedBy` |

### InfoObjects

InfoObjects are the reusable building blocks of BW—characteristics (for example, customer, material), key figures (for example, revenue, quantity), and units. Atlan maps InfoObjects to its `SAPBWInfoObject` asset type.

| Source property | Atlan property |
| --- | --- |
| `IOBJNM` | `name` |
| `TXTLG` | `description` |
| `FIELDNM` | `sapBwFieldName` |
| `DATATYPE` | `sapDataType` |

### Data sources

DataSources define how raw data is extracted from a source system (SAP source, flat file, DB Connect, etc.) into BW. Atlan maps DataSources to its `SAPBWDataSource` asset type.

| Source property | Atlan property |
| --- | --- |
| `DATASOURCE` | `name` |
| `TXTLG` | `description` |
| `LOGSYS` | `sapBwLogicalSystem` |
| `TYPE` | `sapBwSourceType` |
| `DELTA` | `sapBwDeltaMethod` |
| `APPLNM` | `sapComponentName` |
| Field count | `sapFieldCount` |

### Data source fields

Each DataSource exposes a flat list of fields with data type and length. Atlan maps these to `SAPBWDataSourceField`.

| Source property | Atlan property |
| --- | --- |
| `FIELDNM` | `name` |
| `DATASOURCE` | `sapBwParentName` |
| `POSIT` | `sapFieldOrder` |
| `DATATYPE` | `sapDataType` |
| `LENG` | `sapBwLength` |
| Mapped InfoObject | `sapBwInfoObjectName`, `sapBwInfoObjectQualifiedName` |

### InfoSources

InfoSources decouple DataSources from providers, allowing one logical input to feed multiple targets. Atlan maps InfoSources to `SAPBWInfoSource`.

| Source property | Atlan property |
| --- | --- |
| `ISOURCE` | `name` |
| `TXTLG` | `description` |
| `OBJSTAT` | `sapBwObjectStatus` |
| Application component | `sapComponentName` |

### InfoSource fields

Fields defined on an InfoSource, typically aligned to InfoObjects. Atlan maps these to `SAPBWInfoSourceField`.

| Source property | Atlan property |
| --- | --- |
| `FIELDNM` | `name` |
| `ISOURCE` | `sapBwParentName` |
| `POSIT` | `sapFieldOrder` |
| `DATATYPE` | `sapDataType` |
| `LENG` | `sapBwLength` |
| `KEYFLAG` | `sapBwIsKeyField` |
| Mapped InfoObject | `sapBwInfoObjectName`, `sapBwInfoObjectQualifiedName` |

### ADSO fields

Advanced DataStore Objects (ADSOs) are the primary persistence layer in BW/4HANA, replacing classic InfoCubes and DSOs. Atlan maps ADSOs to `SAPBWADSO`. Columns of an ADSO are mapped to `SAPBWADSOField`.

| Source property | Atlan property |
| --- | --- |
| `ADSONM` | `name` |
| `TXTLG` | `description` |
| `PLANNING_MODE` | `sapBwPlanningMode` |
| Field count | `sapFieldCount` |

### ADSO field details

| Source property | Atlan property |
| --- | --- |
| `COLNAME` | `name` |
| `ADSONM` | `sapBwParentName` |
| Linked InfoObject | `sapBwInfoObjectName`, `sapBwInfoObjectQualifiedName` |

### CompositeProvider fields

CompositeProviders virtually combine ADSOs and other providers via union or join, optionally pushing logic to the HANA layer. Atlan maps CompositeProviders to `SAPBWCompositeProvider`. Output columns of a CompositeProvider are mapped to `SAPBWCompositeProviderField`.

| Source property | Atlan property |
| --- | --- |
| `HCPRNM` | `name` |
| `TXTLG` | `description` |
| `HANAMODELFL` (`'X'` / blank) | `sapBwIsHanaModel` (boolean) |
| Field count | `sapFieldCount` |

### CompositeProvider field details

| Source property | Atlan property |
| --- | --- |
| `COLNAME` | `name` |
| `HCPRNM` | `sapBwParentName` |

### Queries

BEx-style and Eclipse-modeled analytic queries that read from a provider. Atlan maps Queries to `SAPBWQuery`.

| Source property | Atlan property |
| --- | --- |
| `COMPID` (fallback `COMPUID`) | `name` |
| `COMPUID` | `sapBwQueryUid` |
| `TXTLG` | `description` |
| Field count | `sapFieldCount` |

### Query elements

Elements defined inside a Query (selections, formulas, restricted key figures, and other items). Atlan maps these to `SAPBWQueryElement`.

| Source property | Atlan property |
| --- | --- |
| `ELTUID` | `name` |
| `COMPUID` | `sapBwParentName` |
| `DATATYPE` | `sapDataType` |
| Related InfoObjects | `sapBwInfoObjectName`, `sapBwInfoObjectQualifiedName` |

### Transformations

Transformations describe the source → target mapping logic between BW providers, including rule-level field mappings. Atlan maps Transformations to `SAPBWTransformation`.

| Source property | Atlan property |
| --- | --- |
| `SOURCETYPE`, `SOURCENAME` → `TARGETTYPE`, `TARGETNAME` | `name` (formatted as `SOURCE -> TARGET`) |
| Rule rows (RSTRANRULE / RSTRANFIELD) | `sapBwRules` (array) |

### Data transfer processes

Data Transfer Processes. Atlan maps DTPs to `SAPBWDTP`.

| Source property | Atlan property |
| --- | --- |
| `DTP` | `name` |
| `TXTLG` | `description` |

## See also

* [Crawl SAP BW/4HANA](https://docs.atlan.com/llms/connectors/sap-bw4hana/crawl-sap-bw4hana/llms.txt): Run the crawler to extract these assets.
* [How Atlan connects to SAP BW/4HANA](https://docs.atlan.com/llms/connectors/sap-bw4hana/how-atlan-connects-to-sap-bw4hana/llms.txt): Understand the connection model and security boundaries.

---