> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SAP BW/4HANA Pipeline Connector | Hybrid Runner

> Connect SAP BW/4HANA to Collate as a pipeline connector using the Hybrid Runner. Extract Process Chain metadata and lineage directly from the HANA database underlying BW/4HANA.

export const MetadataIngestionUi = ({connector, selectServicePath, addNewServicePath, serviceConnectionPath}) => {
  return <>
   <p>
      To ingest metadata from your sources, you need to create a service connection.
      The service connects your source system with Collate. Once you create
      a service, you can use it to configure your ingestion workflows.<br />
      <br />
      To create a service connection and ingest your metadata, follow the steps below:
  </p>
  <Steps>
    <Step title="Select the Service">
    <ol>
          <li>
            On the left navigation bar, click <strong>Settings</strong>.
          </li>
          <li>
            On the next page, click <strong>Services</strong>, and then select the service.
            <img src="/public/images/connectors/visit-services-page.png" alt="Visit Services Page" />
          </li>
    </ol>
   </Step>


   <Step title="Create a New Service">

       To add a new service connection, click <strong>Add New Service</strong>.
      <img src="/public/images/connectors/create-new-service.png" alt="Create a new Service" />


   </Step>


     <Step title="Select the Connector">
       Select <strong>{connector}</strong> as the service type and click <strong>Next</strong>.


       {selectServicePath && <img src={selectServicePath} alt="Select Service" />}
   </Step>


   <Step title="Name and Describe your Service">
       Enter a unique, descriptive <strong>Service Name</strong> and <strong>Description</strong>.
       <ul>
         <li><strong>Service Name</strong>: Collate identifies services by their service name. Enter a name that distinguishes this deployment from other services, including other {connector} services you are ingesting metadata from.</li>
       </ul>


       <Note>
           The service name cannot be changed after it is set.
       </Note>


       {addNewServicePath && <img src={addNewServicePath} alt="Add New Service" />}
   </Step>


   <Step title="Configure the Service Connection">
       Set up the connection settings required for {connector}. <br /><br />

       Configure the following connection options to set up the service and start ingesting metadata from your sources. The right-hand panel displays help documentation for the selected connection type in the product UI

       {serviceConnectionPath && <img src={serviceConnectionPath} alt="Configure Service connection" />}
   </Step>
   </Steps>
   </>;
};

export const ConnectorDetailsHeader = ({name, icon, stage, availableFeatures, unavailableFeatures = [], availableFeaturesCollate = []}) => {
  const showSubHeading = availableFeatures?.length > 0 || unavailableFeatures?.length > 0 || availableFeaturesCollate?.length > 0;
  const totalAvailableFeatures = [...availableFeatures || [], ...availableFeaturesCollate || []];
  return <div className="container">
      <div className="Heading">
        <div className="flex items-center gap-3">
          {icon && <div className="IconContainer">
              <img src={icon} alt={name} noZoom className="ConnectorIcon" />
            </div>}
          <h1 className="ConnectorName">{name}</h1>
          <span className={`StageBadge ${stage === 'PROD' ? 'prod' : 'beta'}`}>
            {stage}
          </span>
        </div>
      </div>
      {showSubHeading && <div className="SubHeading">
          <div className="FeaturesHeading">Feature List</div>
          <div className="FeaturesList">
            {totalAvailableFeatures.map(feature => <div className="FeatureTag AvailableFeature" key={feature}>
                ✓ {feature}
              </div>)}
            {unavailableFeatures.map(feature => <div className="FeatureTag UnavailableFeature" key={feature}>
                ✕ {feature}
              </div>)}
          </div>
        </div>}
    </div>;
};

<ConnectorDetailsHeader icon="/public/images/connectors/sapbw4hana.png" name="SAP BW/4HANA Pipeline" stage="BETA" availableFeatures={["Pipelines", "Pipeline Status", "Lineage"]} unavailableFeatures={["Owners", "Tags", "Usage"]} />

In this section, we provide guides and references to use the SAP BW/4HANA Pipeline connector.

<Info>
  This connector is available exclusively on **Collate**. It is not part of the open-source OpenMetadata distribution.
</Info>

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](/connectors/database/sapbw4hana).

Configure and schedule SAP BW/4HANA pipeline workflows from the Collate UI:

* [Requirements](#requirements)
* [Metadata Ingestion](#metadata-ingestion)
* [Troubleshooting](/connectors/pipeline/sapbw4hana-pipeline/troubleshooting)

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

```sql theme={null}
-- Process Chain directory and descriptions
GRANT SELECT ON <abapSchema>.RSPCCHAIN TO <user>;
GRANT SELECT ON <abapSchema>.RSPCCHAINT TO <user>;

-- Step (variant) descriptions
GRANT SELECT ON <abapSchema>.RSPCVARIANTT TO <user>;

-- DTP step descriptions
GRANT SELECT ON <abapSchema>.RSBKDTPT TO <user>;
```

### Pipeline Status

```sql theme={null}
-- Latest run per Process Chain
GRANT SELECT ON <abapSchema>.RSPCRECENTRUN TO <user>;

-- Per-step execution log
GRANT SELECT ON <abapSchema>.RSPCPROCESSLOG TO <user>;
```

### Lineage (Process Chain → ADSO)

```sql theme={null}
-- DTP-to-ADSO target mapping
GRANT SELECT ON <abapSchema>.RSBKDTP TO <user>;

-- ADSO InfoArea lookup (needed to resolve lineage targets)
GRANT SELECT ON <abapSchema>.RSOADSO TO <user>;
```

<Tip>
  Replace `<abapSchema>` with your actual ABAP schema name (default: `SAPHANADB`). You can find the correct schema by running:

  ```sql theme={null}
  SELECT SCHEMA_NAME FROM SYS.TABLES WHERE TABLE_NAME = 'RSOADSO';
  ```

  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.
</Tip>

## Metadata Ingestion

<MetadataIngestionUi connector={"SAP BW/4HANA Pipeline"} selectServicePath={"/public/images/connectors/sapbw4hana-pipeline/select-service.png"} addNewServicePath={"/public/images/connectors/sapbw4hana-pipeline/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/sapbw4hana-pipeline/service-connection.png"} />

## Connection Details

<Steps>
  <Step title="Connection Details">
    <Tip>
      When using a **Hybrid Ingestion Runner**, any sensitive credential fields—such as passwords—must reference secrets using the following format:

      ```
      password: secret:/my/sap/hana/password
      ```

      This applies **only to fields marked as secrets** in the connection form. For a complete guide, see the [Hybrid Ingestion Runner Secret Management Guide](https://docs.getcollate.io/getting-started/day-1/hybrid-saas/hybrid-ingestion-runner#3.-manage-secrets-securely).
    </Tip>

    **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:

    ```sql theme={null}
    SELECT SCHEMA_NAME FROM SYS.TABLES WHERE TABLE_NAME = 'RSOADSO';
    ```

    **Pipeline Filter Pattern** (optional): Regex pattern to include or exclude Process Chains by their Chain ID. Supports `includes` and `excludes` arrays.
  </Step>

  <Step title="Test the Connection">
    Once the credentials have been added, click on *Test Connection* and *Save* the changes.

    <img src="https://mintcdn.com/collatedocs/L7psA65ao88vmcRI/public/images/connectors/test-connection.png?fit=max&auto=format&n=L7psA65ao88vmcRI&q=85&s=2133f0d65f18df1e57f69d2cc3bdeff4" alt="Test Connection" width="1494" height="310" data-path="public/images/connectors/test-connection.png" />
  </Step>

  <Step title="Configure Metadata Ingestion">
    In this step we will configure the metadata ingestion pipeline,
    Please follow the instructions below

    <img src="https://mintcdn.com/collatedocs/12mtkhFtvTP7FUxZ/public/images/connectors/configure-metadata-ingestion-pipeline.png?fit=max&auto=format&n=12mtkhFtvTP7FUxZ&q=85&s=b310e691eaec850bc9eda3ed0b8a340f" alt="Configure Metadata Ingestion" width="1508" height="1614" data-path="public/images/connectors/configure-metadata-ingestion-pipeline.png" />

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

  <Step title="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.

    <img src="https://mintcdn.com/collatedocs/piJyXg9wW6Ik1lg-/public/images/connectors/schedule.png?fit=max&auto=format&n=piJyXg9wW6Ik1lg-&q=85&s=f1add591824b44456f0e2ff259a21c6f" alt="Schedule the Workflow" width="2733" height="1083" data-path="public/images/connectors/schedule.png" />
  </Step>

  <Step title="View the Ingestion Pipeline">
    Once the workflow has been successfully deployed, you can view the
    Ingestion Pipeline running from the Service Page.

    <img src="https://mintcdn.com/collatedocs/cOe_QuHYxAbkMtTI/public/images/connectors/view-ingestion-pipeline.png?fit=max&auto=format&n=cOe_QuHYxAbkMtTI&q=85&s=8c754af74f99ee70e714f6f707b827e4" alt="View Ingestion Pipeline" width="2733" height="1271" data-path="public/images/connectors/view-ingestion-pipeline.png" />

    <Tip>
      If [AutoPilot](/how-to-guides/admin-guide/applications/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.
    </Tip>
  </Step>
</Steps>

## Troubleshooting

<Columns cols={2}>
  <Card title="SAP BW/4HANA Pipeline Troubleshooting" href="/connectors/pipeline/sapbw4hana-pipeline/troubleshooting">
    Learn more about how to troubleshoot common SAP BW/4HANA Pipeline connector issues and resolve configuration or ingestion errors.
  </Card>
</Columns>