ContextQMD
Back to Datahub

Sac Post

metadata-ingestion/docs/sources/sac/sac_post.md

1.7.02.1 KB
Original Source

Capabilities

Use the Important Capabilities table above as the source of truth for supported features and whether additional configuration is required.

Limitations

  • Only models which are used in a Story or an Application will be ingested because there is no dedicated API to retrieve models (only for Stories and Applications).
  • Browse Paths for models cannot be created because the folder where the models are saved is not returned by the API.
  • Schema metadata is only ingested for Import Data Models because there is no possibility to get the schema metadata of the other model types.
  • Lineages for Import Data Models cannot be ingested because the API is not providing any information about it.
  • Currently, only SAP BW and SAP HANA are supported for ingesting the upstream lineages of Live Data Models - a warning is logged for all other connection types, please feel free to open an issue on GitHub with the warning message to have this fixed.
  • For some models (e.g., builtin models) it cannot be detected whether the models are Live Data or Import Data Models. Therefore, these models will be ingested only with the Story subtype.

Limitations

Module behavior is constrained by source APIs, permissions, and metadata exposed by the platform. Refer to capability notes for unsupported or conditional features.

Troubleshooting

If ingestion fails, validate credentials, permissions, connectivity, and scope filters first. Then review ingestion logs for source-specific errors and adjust configuration accordingly.

Compatibility across tenant generations

The connector reads stories, applications, and models from the Resources OData data endpoints (for example api/v1/Resources) directly, rather than discovering them from the tenant's $metadata document. This keeps ingestion working across SAP Analytics Cloud tenant generations: newer (CAP-based) tenants no longer describe the Resources entity set in $metadata (it is replaced there by a non-queryable RESOURCES_INDEX catalog), but the Resources data endpoints remain available and are what the connector uses.