Monitoring Metadata Extractions
On the Metadata Extractions page, you can select a source system from the Remote Systems table and view its system details and synchronization details. You can also review the extraction summary for the assets and use the system extraction logs to troubleshoot common errors.
Prerequisites
-
Data Warehouse General (-R------) - To access SAP Datasphere.
-
Catalog System (-RUDE--) - To view, edit, and delete source system connections and manually synchronize source system.
-
Catalog Log (-R-----) - To view source system extraction summary and extraction logs in the system details.
To see the details page for a source system, open the Metadata Extractions page from the side navigation by choosing (Catalog & Marketplace) (Metadata Extractions) and then choose the system you want.
System Details Header
The system details header provides status information about the latest metadata extraction and organizes the information in the following groups: extraction summary, synchronization activity, and system information.

|
Group |
Description |
|---|---|
|
(1) Extraction and Authentication Statuses |
Provides the latest synchronization status and the authentication status of the authorized user. These statuses appear beside the source system name. The extraction status can be one of the following:
The authentication status of the authorized user indicates whether you need to update that user's authentication because it's about to expire, set up a user's authentication because it's missing, or run a manual synchronization because a new user was authorized. To ensure the catalog is always current, be sure to check the authentication status regularly. |
|
(2) Summary |
Provides a summary of the extracted objects, including the following:
|
|
(3) Activity |
Provides the date and time of the most recent manual or automated synchronization, along with its synchronization status.
Choosing the link for the last manual synchronization updates the view of the Extraction Logs tab, so that the most current extraction is selected and any objects that failed appears on the right side of the tab. |
|
(4) System |
Displays system information, which can include the following:
|
Extraction Summary Tab
The Extraction Summary tab shows a summary view of all objects that were extracted within the last 90 days. You can use the free text search to find an object by its name, sort the columns, or show and hide columns. Use the Filter panel to limit the objects displayed.

|
Column |
Description |
|---|---|
|
Name |
The name of the object from the source system. If the object already exists in the catalog, choose its name to open the object's details page. |
|
Status |
The synchronization status (completed or failed) for the object. The synchronization for an object can fail or encounter an error for various reasons, including technical issues during extraction or issues with access permissions. For information on how to fix common synchronization errors, see the section Troubleshooting Common Errors. |
|
Error Message |
The error message indicates the reason the metadata for the object was not extracted. |
|
Date |
The date and time the metadata was extracted. |
|
Operational Type |
The operational type of metadata extraction performed on the object. The asset can be created, updated, or deleted. If an issue occurred during extraction, the asset the operational type is Error. |
|
Actions |
The actions available for the row. Choose to see the extraction activity for the asset in the last 90 days. |
|
Description |
The description of the object from the source system. |
|
Error UUID |
The error universally unique identifier (UUID) that appears in the logs. You can search for this identifier to find more details. |
|
Error Details |
The reason why the object encountered an error during synchronization. |
|
Column |
Description |
|---|---|
|
Asset Source ID |
The object identifier of the object in the source system. If a synchronization error occurs for the object, you can use this identifier to find the object in the source system. |
|
Container Path |
The location path of the object on the source system. This information is useful when the object name is not unique. |
|
Extraction Type |
The type of synchronization that was run on the source system: Manual or Automatic. |
|
Type |
The type of object in the source system. For a list of supported object types for a source system, see Connecting Source Systems. |
|
Column |
Description |
|---|---|
|
ORD ID |
The open resource discover (ORD) identifier for the API. |
|
Data Product |
The tag for the data product. This tag is used for obtaining the API information. |
|
System |
The name of the system. |
|
System Type |
The type of system. This value will always be Unified Customer Landscape System. |
-
Choose to get more information about the extraction activity for the object in the last 90 days. For objects that have an error operational type, you can use the history to troubleshoot the issue.
-
Choose the name link to view its details page, where you can enrich or publish the asset.
Extraction Logs Tab
The Extraction Logs tab displays all metadata extraction records. You can monitor and review extractions, identify issues, and troubleshoot errors. These records are available for 90 days from the date the synchronization task completed.

The Tasks panel shows the list of synchronization tasks that were run in the last 90 days. You can sort the table, filter the tasks by the status, or show and hide columns.
|
Column |
Description |
|---|---|
|
Start Date |
The date and time the task started. |
|
End Date |
The date and time the task ended. For tasks still in progress, the end date is empty. |
|
Status |
The status of the task can be completed, completed with errors, failed, or in progress. |
|
Progress |
A progress bar showing the percentage of the task completion. |
|
Run Mode |
The run mode (delta or full) for the synchronization. This column appears for BW (SAP Datasphere, SAP BW bridge or SAP BW∕4HANA) systems. |
|
Correlation ID |
Choose to copy the correlation ID. You can then use the correlation ID to search the extraction log for troubleshooting issues. This column appears for BW systems. |
|
Summary |
Choose to open a dialog that shows the summary of the selected line.
The top of the dialog shows the object totals for the following areas:
The lower part of the dialog provides a summary that shows the date and time for when the synchronization task started and ended. |
The Failed Assets panel shows the objects that failed to synchronize for the selected task. For these objects, you can see the reason the synchronization failed. Use the free text search to find an object by its name. You can also sort the table, filter the tasks by the error message, or show and hide columns.
|
Column |
Description |
|---|---|
|
Name |
The name of the asset. |
|
Extraction Date |
The date and time of the extraction. |
|
Error Message |
The error message of why the extraction failed. The error message can provide you with a starting point for troubleshooting failed extractions. For information on how to fix common synchronization errors, see the section Troubleshooting Common Errors. |
Troubleshooting Common Errors
For help with common errors, refer to the following table to review possible causes and actions you can take to resolve extraction issues.
|
Error Message |
Possible Cause and Resolution |
Category |
|---|---|---|
|
Unable to extract asset |
This error can occur for several reasons. To identify the cause of the error message, try reviewing the extraction log files for the source system.
To resolve this issue, try one of the following:
|
General |
|
Unable to extract asset due to network error |
This error can occur because of a power failure or network connectivity issues. To resolve this issue, try manually synchronizing the system when the power returns or network connectivity is restored. |
General |
|
Unable to extract asset due to invalid extraction resource |
This error is caused by an internal error. To resolve this issue, try manually synchronizing the system. If the problem persists, contact the system administrator of the source system for assistance. |
General |
|
Unable to extract metadata |
This error can occur for several reasons. To identify the cause of the error message, try reviewing the extraction log files for the source system.
To resolve this issue, try one of the following:
|
Metadata |
|
Unable to extract metadata due to missing privilege <privilege_name> |
This error can occur when the authorized user is missing access permission for the object on the source system. To resolve this issue, contact the system administrator for the source system and have them check the user's privileges. |
Metadata |
|
Unable to extract metadata due to missing required property <property_name> |
This error can occur because the object is missing required metadata in the source system.
To resolve this issue, try one of the following:
|
Metadata |
|
Unable to extract metadata due to network error |
This error can occur because of a power failure or network connectivity issues. To resolve this issue, try manually synchronizing the system when the power returns or network connectivity is restored. |
Metadata |
|
Unable to extract lineage |
This error can occur for several reasons. To identify the cause of the error message, try reviewing the extraction log files for the source system.
To resolve this issue, try one of the following:
|
Lineage |
|
Unable to extract lineage due to missing privilege <privilege_name> |
This error can occur when the authorized user is missing privileges to access the object on the source system. To resolve this issue, contact the system administrator for the source system and have them check the user's privileges. |
Lineage |
|
Unable to extract lineage due to missing required property <property_name> |
This error can occur because the object is missing required metadata in the source system.
To resolve this issue, try one of the following:
|
Lineage |
|
Unable to extract lineage due to network error |
This error can occur because of a power failure or network connectivity issues. To resolve this issue, try manually synchronizing the system when the power returns or network connectivity is restored. |
Lineage |
