Skip to main content
In this section, we provide guides and references to use the SAP BW/4HANA Pipeline connector.
This connector is available exclusively on Collate. It is not part of the open-source OpenMetadata distribution.
The SAP BW/4HANA Pipeline connector extracts Process Chains from your BW/4HANA system as Collate Pipeline entities. Each Process Chain step maps to a Task, run history is captured as Pipeline Status, and the connector traces lineage from Process Chain DTP steps to the target ADSO objects cataloged by the SAP BW/4HANA database connector. Configure and schedule SAP BW/4HANA pipeline workflows from the Collate UI:

​
Requirements

The connector reads BW Process Chain catalog tables from the underlying SAP HANA instance. The HANA user requires SELECT privileges on the following objects:

​
Pipeline Ingestion

​
Pipeline Status

​
Lineage (Process Chain → ADSO)

Replace <abapSchema> with your actual ABAP schema name (default: SAPHANADB). You can find the correct schema by running:
For lineage between Process Chains and ADSO entities to resolve correctly, ensure both the SAP BW/4HANA database service and the SAP BW/4HANA Pipeline service are created in Collate, and configure the Database Service Name in the pipeline service’s lineage settings.

​
Metadata Ingestion

​
Connection Details

1

Connection Details

When using a Hybrid Ingestion Runner, any sensitive credential fields—such as passwords—must reference secrets using the following format:
This applies only to fields marked as secrets in the connection form. For a complete guide, see the Hybrid Ingestion Runner Secret Management Guide.
Host and Port (required): Host and port of the SAP HANA instance underlying BW/4HANA. Specify as hostname:port, e.g. hana-host:30015.Username (required): HANA database username with SELECT access to the BW Process Chain catalog tables listed in the Requirements section above.Password (required): Password for the HANA database user.ABAP Schema (optional): Schema name in HANA where the BW/4HANA ABAP metadata tables reside. Defaults to SAPHANADB. To confirm the correct value on your system, run:
Pipeline Filter Pattern (optional): Regex pattern to include or exclude Process Chains by their Chain ID. Supports includes and excludes arrays.
2

Test the Connection

Once the credentials have been added, click on Test Connection and Save the changes.Test Connection
3

Configure Metadata Ingestion

In this step we will configure the metadata ingestion pipeline, Please follow the instructions belowConfigure Metadata Ingestion

​
Metadata Ingestion Options

  • Name: This field refers to the name of ingestion pipeline, you can customize the name or use the generated name.
  • Pipeline Filter Pattern (Optional): Use to pipeline filter patterns to control whether or not to include pipeline as part of metadata ingestion.
    • Include: Explicitly include pipeline by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all pipeline with names matching one or more of the supplied regular expressions. All other schemas will be excluded.
    • Exclude: Explicitly exclude pipeline by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all pipeline with names matching one or more of the supplied regular expressions. All other schemas will be included.
  • Include lineage (toggle): Set the Include lineage toggle to control whether to include lineage between pipelines and data sources as part of metadata ingestion.
  • Enable Debug Log (toggle): Set the Enable Debug Log toggle to set the default log level to debug.
  • Mark Deleted Pipelines (toggle): Set the Mark Deleted Pipelines toggle to flag pipelines as soft-deleted if they are not present anymore in the source system.
4

Schedule the Ingestion and Deploy

Scheduling can be set up at an hourly, daily, weekly, or manual cadence. The timezone is in UTC. Select a Start Date to schedule for ingestion. It is optional to add an End Date.Review your configuration settings. If they match what you intended, click Deploy to create the service and schedule metadata ingestion.If something doesn’t look right, click the Back button to return to the appropriate step and change the settings as needed.After configuring the workflow, you can click on Deploy to create the pipeline.Schedule the Workflow
5

View the Ingestion Pipeline

Once the workflow has been successfully deployed, you can view the Ingestion Pipeline running from the Service Page.View Ingestion Pipeline
If AutoPilot is enabled, workflows like usage tracking, data lineage, and similar tasks will be handled automatically. Users don’t need to set up or manage them - AutoPilot takes care of everything in the system.

​
Troubleshooting

SAP BW/4HANA Pipeline Troubleshooting

Learn more about how to troubleshoot common SAP BW/4HANA Pipeline connector issues and resolve configuration or ingestion errors.