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

> Troubleshoot common SAP BW/4HANA Pipeline connector issues in Collate — connection failures, permission errors on Process Chain tables, and status or lineage problems.

## Troubleshooting

### Workflow Deployment Error

If there were any errors during the workflow deployment process, the
Ingestion Pipeline Entity will still be created, but no workflow will be
present in the Ingestion container.

* You can then Edit the Ingestion Pipeline and **Deploy** it again.
* From the Connection tab, you can also Edit the Service if needed.

## Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in Collate. Below are some of the most frequently observed troubleshooting scenarios.

## How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in Collate:

1. **Navigate to Services**
   Go to **Settings > Services > Service Type** (e.g., Database) in the Collate UI.

2. **Select a Service**
   Choose the specific service for which you want to enable debug logging.

3. **Access Ingestion Tab**
   Go to the **Ingestion tab** and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.

4. **Enable Debug Logging**
   In the configuration dialog, enable the **Debug Log** option and click **Next**.

5. **Schedule and Submit**
   Configure the schedule if needed and click **Submit** to apply the changes.

## Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

## SAP BW/4HANA Pipeline-Specific Issues

### Permission Denied on Process Chain Tables

**Symptom**: Test connection step `GetProcessChains` fails with a permission error.

**Cause**: The HANA user does not have `SELECT` access on `RSPCCHAIN` or the related catalog tables in the configured `abapSchema`.

**Resolution**: Grant the required permissions listed in the [Requirements](/connectors/pipeline/sapbw4hana-pipeline#requirements) section. Verify the correct schema name by running:

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

### Pipeline Status Not Populated

**Symptom**: Process Chains are ingested but Pipeline Status shows no run history.

**Cause**: The HANA user may be missing `SELECT` on `RSPCRECENTRUN` or `RSPCPROCESSLOG`, or the Process Chains have never been executed.

**Resolution**: Grant the Pipeline Status permissions from the [Requirements](/connectors/pipeline/sapbw4hana-pipeline#requirements) section. Verify runs exist by running:

```sql theme={null}
SELECT * FROM <abapSchema>.RSPCRECENTRUN WHERE CHAIN_ID = '<your_chain_id>';
```

### No Lineage from Process Chains to ADSOs

**Symptom**: Process Chains are ingested but no lineage edges appear linking them to ADSO tables.

**Cause**: Either the lineage permissions are missing, the SAP BW/4HANA database service has not been configured in Collate, or no DTP-load steps of type `DTP_LOAD` with ADSO targets exist in the Process Chains.

**Resolution**:

1. Grant the Lineage permissions from the [Requirements](/connectors/pipeline/sapbw4hana-pipeline#requirements) section.
2. Ensure the SAP BW/4HANA database service ([`/connectors/database/sapbw4hana`](/connectors/database/sapbw4hana)) is configured and has ingested the ADSO entities.
3. Configure the **Database Service Name** in the pipeline service's lineage settings to point to your SAP BW/4HANA database service.