Community

Connector Improvement: SAP Connector : Metadata Capture and transport to destination

Answered

Shristi Drolia User

March 19, 2026 20:51

We would like Fivetran to support propagation of SAP field descriptions/labels into the target system as column descriptions or comments during sync.

Today, when SAP tables are replicated to the target, the technical column names are available, but the business-friendly SAP field descriptions are not captured and do not flow through automatically. As a result, we have to query SAP metadata tables separately for each table in order to retrieve field descriptions and then manage that metadata outside the pipeline.

This creates extra effort and makes the replicated data harder to understand for downstream users, especially analysts, engineers, and business teams working directly in the target system.

Why this would help

Having SAP field descriptions available directly in the target would:

improve data usability and readability
reduce the need to query SAP metadata tables separately
save time during onboarding, analysis, and model development
make target datasets more self-documenting
improve consistency between SAP source metadata and replicated target metadata

Please sign in to leave a comment.

Comments

1 comment

Official comment

Edwin Fivetranner
- March 27, 2026 19:47
Hi Shristi,

Thank you for the detailed write-up.

As I understand it, you are asking to have SAP field descriptions propagated into the target system as column descriptions or comments, so that replicated tables are self-documenting and do not require separate SAP metadata queries.

There is already a related feature request for this:
https://support.fivetran.com/hc/en-us/community/posts/38427914785815-Connector-Improvement-Automatic-destination-documentation

This is a known requirement and one we have already identified as a potential product improvement. Implementing it would require changes across the connector, processing layer, and data writer, which makes it more difficult to scope for the near term. I will leave this feature request open to reflect customer demand and support internal prioritization.

In the meantime, as you suggested, you can generate the field descriptions yourself by replicating the SAP Dictionary tables DD02L, DD02T, DD03L, and DD03T. We also have documentation on how to join and use these tables to retrieve field-level descriptions, though I understand this may require additional effort on your side.

Best regards,

Edwin

Official comment

Edwin Fivetranner

March 27, 2026 19:47

Hi Shristi,

Thank you for the detailed write-up.

As I understand it, you are asking to have SAP field descriptions propagated into the target system as column descriptions or comments, so that replicated tables are self-documenting and do not require separate SAP metadata queries.

There is already a related feature request for this:
https://support.fivetran.com/hc/en-us/community/posts/38427914785815-Connector-Improvement-Automatic-destination-documentation

This is a known requirement and one we have already identified as a potential product improvement. Implementing it would require changes across the connector, processing layer, and data writer, which makes it more difficult to scope for the near term. I will leave this feature request open to reflect customer demand and support internal prioritization.

In the meantime, as you suggested, you can generate the field descriptions yourself by replicating the SAP Dictionary tables DD02L, DD02T, DD03L, and DD03T. We also have documentation on how to join and use these tables to retrieve field-level descriptions, though I understand this may require additional effort on your side.

Best regards,

Edwin