Integrated SAP Datasphere Catalog data

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

After synchronization, the resulting assets are available in the same community as the SAP Datasphere tenant domain. However, the integration creates a different domain per space.

Note 
  • The assets have the same technical names as their counterparts in SAP Datasphere Catalog.
  • By default, all ingested assets have an initial asset status Candidate. You can, however, configure which initial status you want assets to have when they are ingested, and the asset status progression.
  • Relations that were created between SAP Datasphere Catalog assets and other assets via a relation type in the SAP Datasphere Catalog operating model, are deleted upon synchronization. The same is true of any attribute types in the operating model that you add to the SAP Datasphere Catalog assets mentioned in the following table. To ensure that the characteristics you add to the following assets are not deleted upon synchronization, be sure to use characteristics that are not part of the SAP Datasphere Catalog operating model.
  • SAP Datasphere Catalog allows duplicate asset names. For example, you can have two folders with the full name "Workspace A > Folder A". The ingested assets in Collibra will have the same display names, but different full names. The API returns version information to help you differentiate between two such assets.
  • If you move assets to another domain, they will automatically be moved back to the original domain at the next synchronization.
  • If a temporary communication issue results in a partial synchronization, the status of the assets that were not synchronized becomes Missing from source. If the assets are identified in the source system during the next fully successful synchronization, the previous statuses are restored.

By default, the assets have the status Implemented.

Synchronized metadata per asset type

This table shows the metadata for each SAP Datasphere Catalog asset type and the resource ID for each asset type and characteristic.

Note For assets in SAP Datasphere Catalog that have a "summary" and a "description", if the API returns both of these values, they are both shown in the "Description from Source System" attribute on the respective asset pages in Collibra Data Catalog. To differentiate between the two, the value of the "summary" attribute in SAP Datasphere Catalog, will be shown with the prefix "summary:".

SAP system type

Asset type

Synchronized metadata

Resource ID
  • SAP Datasphere
  • SAP Analytics Cloud

SAP Tenant

Resource ID: 00000000-0000-0000-0000-100000000060

Description 00000000-0000-0000-0000-000000003114
SAP System Type 00000000-0000-0000-0011-000500000020
Technology Asset groups / is grouped by Technology Asset 00000000-0000-0000-0000-000000007054
  • SAP Datasphere
  • SAP Analytics Cloud

SAP Container

Resource ID: 00000000-0000-0000-0000-100000000061

Description

00000000-0000-0000-0000-000000003114
Storage Container contains / is part of Storage Container 00000000-0000-0000-0001-002600000001
Technology Asset groups / is grouped by Technology Asset 00000000-0000-0000-0000-000000007054
 SAP Datasphere

 SAP Datasphere Space

Resource ID: 00000000-0000-0000-0000-100000000068

Description 00000000-0000-0000-0000-000000003114
SAP Datasphere Space contains / is part of Data Asset 00000000-0000-0000-0000-121000000000
Technology Asset groups / is grouped by Technology Asset 00000000-0000-0000-0000-000000007054
Storage Container contains / is part of Storage Container 00000000-0000-0000-0001-002600000001
SAP Datasphere

SAP Datasphere Analytic Model

Resource ID: 00000000-0000-0000-0000-100000000069

Description 00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Owner in Source 00000000-0000-0000-0000-200000000001
Document modification date 00000000-0000-0000-0000-000000000261
Document creation date 00000000-0000-0000-0000-000000000260
SAP Datasphere Space contains / is part of Data Asset 00000000-0000-0000-0000-121000000000
Data Model contains / is used in Table 00000000-0000-0000-0000-121000000001
SAP Datasphere

SAP Datasphere Intelligent Lookup

Resource ID: 00000000-0000-0000-0000-100000000072

Description 00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Owner in Source 00000000-0000-0000-0000-200000000001
Document modification date 00000000-0000-0000-0000-000000000261
Document creation date 00000000-0000-0000-0000-000000000260
SAP Datasphere Space contains / is part of Data Asset 00000000-0000-0000-0000-121000000000
Data Model contains / is used in Table 00000000-0000-0000-0000-121000000001
SAP Datasphere

SAP Datasphere Perspective

Resource ID: 00000000-0000-0000-0000-100000000071

Description 00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Owner in Source 00000000-0000-0000-0000-200000000001
Document modification date 00000000-0000-0000-0000-000000000261
Document creation date 00000000-0000-0000-0000-000000000260
SAP Datasphere Space contains / is part of Data Asset 00000000-0000-0000-0000-121000000000
Data Model contains / is used in Table 00000000-0000-0000-0000-121000000001
Data Asset is source for / source BI Report 00000000-0000-0000-0000-120000000013
SAP Datasphere

Database View

Resource ID: 00000000-0000-0000-0001-000400000009

Description 00000000-0000-0000-0000-000000003114
Data Model contains / is used in Table 00000000-0000-0000-0000-121000000001
Data Asset is source for / source BI Report 00000000-0000-0000-0000-120000000013
Table is source for / is derived from Database View 00000000-0000-0000-0000-121000000002
SAP Datasphere

Table

Resource ID: 00000000-0000-0000-0000-000000031007

Description

00000000-0000-0000-0000-000000003114
Data Model contains / is used in Table 00000000-0000-0000-0000-121000000001
Data Asset is source for / source BI Report 00000000-0000-0000-0000-120000000013
Table is source for / is derived from Database View 00000000-0000-0000-0000-121000000002
SAP Datasphere

Column

Resource ID: 00000000-0000-0000-0000-000000031008

Original Name

00000000-0000-0000-0001-000500000032
Technical Data Type 00000000-0000-0000-0000-000000000219
Size 00000000-0000-0000-0001-000500000009
Is Nullable 00000000-0000-0000-0001-000500000011
Default Value 00000000-0000-0000-0001-000500000014
Is Primary Key 00000000-0000-0000-0001-000500000015
Column is part of / contains Table 00000000-0000-0000-0000-000000007042
SAP Analytics Cloud

SAC Folder

Resource ID: 00000000-0000-0000-0000-100000000062

Description

00000000-0000-0000-0000-000000003114

BI Folder assembles / is assembled in BI Folder

00000000-0000-0000-0000-120000000001
Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002

BI Folder contains / contained in Data Asset

00000000-0000-0000-0000-120000000014
SAP Analytics Cloud

SAC Story

Resource ID: 00000000-0000-0000-0000-100000000063

Description

00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Document creation date 00000000-0000-0000-0000-000000000260
Document modification date 00000000-0000-0000-0000-000000000261

Owner in source

The only harvested metadata are the email addresses of all Admins and one Owner.

00000000-0000-0000-0000-200000000001

URL: The link to the data in SAP Datasphere Catalog.

Note The URL uses the base URL that was entered in the SAC Analytics Cloud URL field in the integration settings.

00000000-0000-0000-0000-000000000258
Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
Report uses / used in Report 00000000-0000-0000-0000-120000000007
Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
SAP Analytics Cloud

SAC Data Model

Resource ID: 00000000-0000-0000-0000-100000000065

Description

00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Document creation date 00000000-0000-0000-0000-000000000260

Document modification date

00000000-0000-0000-0000-000000000261

Owner in source

The only harvested metadata are the email addresses of all Admins and one Owner.

00000000-0000-0000-0000-200000000001

URL: The link to the data in SAP Datasphere Catalog.

Note The URL uses the base URL that was entered in the SAC Analytics Cloud URL field in the integration settings.

00000000-0000-0000-0000-000000000258
Source Type 00000000-0000-0000-0000-000000000230
BI Folder contains / contained in Data Asset 00000000-0000-0000-0000-120000000014
Data Model contains / is part of Data Entity 00000000-0000-0000-0000-000000007046
Data Asset is source for / source BI Report 00000000-0000-0000-0000-120000000013
Data Asset groups / is grouped by Data Asset 00000000-0000-0000-0000-000000007017
SAP Analytics Cloud

SAC Data Attribute

Resource ID: 00000000-0000-0000-0000-100000000067

Description

00000000-0000-0000-0000-000000003114
Description from Source System 00000000-0000-0000-0001-000500000074
Role in Report 00000000-0000-0000-0000-000000000266
Source Type 00000000-0000-0000-0000-000000000230
Data Entity contains / is part of Data Attribute 00000000-0000-0000-0000-000000007047
Data Element targets / sources Data Element 00000000-0000-0000-0000-000000007069
Data Asset is source for / source BI Report 00000000-0000-0000-0000-120000000013
Data Asset groups / is grouped by Data Asset 00000000-0000-0000-0000-000000007017

The following image shows the relation between the relevant SAP Datasphere assets and an SAC Story asset. The relation type is Data Asset is source for / source BI Report.

Recommended hierarchy within a domain

By default, the assets in the resulting domains are shown in a plain list, but as shown in the following image, you can enable a hierarchy to show them in a tree structure. Doing so makes it easier to understand the relation between your SAP assets, when viewing the assets in a domain.

Steps

  1. Open the relevant domain page.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. In the Relation Type field, add the following relation types:
    For system type...Start typing and select these relation types
    • SAP Datasphere
    •  
    • Technology Asset groups Technology Asset
    • SAP Datasphere Space contains Data Asset
    • Data Model contains Table
    • Table contains Column
     SAP Analytics Cloud
    • Technology Asset groups Technology Asset
    • Storage Container assembles BI Folder
    • Business Dimension groups Report
    • BI Folder contains Data Asset
    • BI Folder assembles BI Folder
    • Report contains Report Attribute
    • Data Asset groups Data Asset
    • BI Report source Data Asset
    SAP Business GlossaryBusiness Asset represents Data Asset

    The following example image show the required relation types to show SAP Datasphere assets in hierarchy.
  6. Click Apply.
Note 
  • In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
  • When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.