diff --git a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md index be92c42..f550a76 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md @@ -46,7 +46,7 @@ Define the source for your replication flow \(connection, container, and objects To narrow down the selection, start typing a part of the folder name in the *Search* field. - - If you choose SAP Datasphere as the source connection, the source container is automatically defined as the space you are in. In addition, the load type is automatically set to *Initial Only* because *Initial and Delta* is currently not supported for SAP Datasphere as the source. \(This applies irrespective of whether the local table itself is enabled for delta capturing or not.\) + - If you choose SAP Datasphere as the source connection, the source container is automatically defined as the space you are in. - If CDS view entities have been made available using the SQL service exposure in SAP BTP, ABAP environment, you find these entities in a folder called SQL\_SERVICE. diff --git a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md index 74d68b7..0309b13 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md @@ -137,9 +137,9 @@ The 2 objects are consumed differently by SAP Datasphere apps: - As Source, you can choose between source with "Delta Capture" or "All Active Records". See [Add a Source](add-a-source-ec702fe.md) - As target, it depends of the combination of the load type used and the table type \(local table with or without delta capture\). See [Processing Changes to Sources and Target Tables](processing-changes-to-sources-and-target-tables-705292c.md) and [Add or Create a Target Table](add-or-create-a-target-table-0950746.md) - - *Replication Flow*: The Delta Capture Table can be used as source \(with load type *Initial Only*\) or as target, see [Creating a Replication Flow](creating-a-replication-flow-25e2bd7.md) and [Add a Source](add-a-source-7496380.md). + - *Replication Flow*: The Delta Capture Table can be used as source or as target, see [Creating a Replication Flow](creating-a-replication-flow-25e2bd7.md) and [Add a Source](add-a-source-7496380.md). - *Table Editor*: - - Data Preview: Once deployment is completed, it show only the delta capture tables. See [Viewing Object Data](../viewing-object-data-b338e4a.md) + - Data Preview: Once deployment is completed, it shows only the delta capture tables. See [Viewing Object Data](../viewing-object-data-b338e4a.md) - Data Maintenance: You can perform table maintenance on the delta capture table \(only\) once deployment is completed. See [Maintain Local Table Data](maintain-local-table-data-4bd5e64.md) - File upload: You can update the delta capture table by uploading a new csv file, after deployment is completed. See [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md) diff --git a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-local-table-2509fe4.md b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-local-table-2509fe4.md index 34cba7c..c9882af 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-local-table-2509fe4.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-local-table-2509fe4.md @@ -105,10 +105,10 @@ This procedure explains how to create an empty table by defining its columns. Yo Choose from the following: - - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Creating a Fact](../Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Creating a Dimension](../Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Creating an External Hierarchy](../Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Creating a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Create a Fact to Contain Measurable Data](../Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Create a Dimension to Categorize Data](../Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Create an External Hierarchy for Drill-Down](../Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Create a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Contains attributes used to provide textual content in one or more languages \(see [Create a Text Entity for Attribute Translation](../Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - \[default\] Contains columns with no specific analytical purpose. - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](../Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). @@ -159,17 +159,17 @@ This procedure explains how to create an empty table by defining its columns. Yo 3. Based on the *Semantic Usage* of your entity, review and modify its *Columns*, *Attributes*, and/or *Measures*: - - *Fact* - Review the lists of measures and attributes \(see [Creating a Fact](../Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Review the list of attributes \(see [Creating a Dimension](../Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Define the parent and child columns \(see [Creating an External Hierarchy](../Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Creating a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Review the lists of measures and attributes \(see [Create a Fact to Contain Measurable Data](../Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Review the list of attributes \(see [Create a Dimension to Categorize Data](../Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Define the parent and child columns \(see [Create an External Hierarchy for Drill-Down](../Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Create a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Review the list of attributes \(see [Create a Text Entity for Attribute Translation](../Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - Review the list of columns \(see [Columns](columns-8f0f40d.md)\). - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](../Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). 4. Complete or consult other sections as appropriate: - - *Associations* - Create associations to other entities \(see [Create an Association](../create-an-association-66c6998.md)\). + - *Associations* - Create associations to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](../Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - *Business Purpose* - Provide a description, purpose, contacts, and tags to help other users understand your entity. - *Table Services* - Enable the *Memory Storage* option to store the table data directly in memory \(see [Accelerate Table Data Access with In-Memory Storage](accelerate-table-data-access-with-in-memory-storage-407d1df.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/review-and-edit-imported-table-properties-75cea7b.md b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/review-and-edit-imported-table-properties-75cea7b.md index 8709484..995b2dc 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/review-and-edit-imported-table-properties-75cea7b.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/review-and-edit-imported-table-properties-75cea7b.md @@ -62,10 +62,10 @@ Provide business-friendly names for your table and its columns, identify its sem Choose from the following: - - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Creating a Fact](../Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Creating a Dimension](../Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Creating an External Hierarchy](../Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Creating a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Create a Fact to Contain Measurable Data](../Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Create a Dimension to Categorize Data](../Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Create an External Hierarchy for Drill-Down](../Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Create a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Contains attributes used to provide textual content in one or more languages \(see [Create a Text Entity for Attribute Translation](../Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - \[default\] Contains columns with no specific analytical purpose. - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](../Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/evaluating-catalog-assets-dc061a2.md b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/evaluating-catalog-assets-dc061a2.md index 836e5ff..058adee 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/evaluating-catalog-assets-dc061a2.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/evaluating-catalog-assets-dc061a2.md @@ -4,7 +4,7 @@ # Evaluating Catalog Assets -When you find the asset you want, you can select it to view its overview information, a preview of its detailed metadata, and a diagram of its impact and lineage. This information includes metadata that is extracted from the source system and data enrichments added in the catalog. +After finding the asset you want, select it to view an overview of its information, a preview of its detailed metadata, and a diagram illustrating its impact and lineage. This information encompasses metadata extracted from the source system as well as data enrichments incorporated in the catalog. @@ -31,15 +31,15 @@ From the \(*Catalog*\) home page, you can s When you open an individual asset from the catalog home page, you're taken to a page that provides many different types of information about the asset. This information can include extracted metadata, like the asset name, properties, description, and impact and lineage diagram. It also includes other data enrichments, such as glossary term, tag, and key performance indicator \(KPI\) relationships applied to the asset, and much more. You can use the information provided to evaluate and make an assessment on whether the asset is the right one you need for your business task at hand. -For example, as a data modeler, you can review the details of a catalog asset to determine whether it is the one you need to add to your model. You can also view the impact and lineage diagram of that asset to see other assets that are consumed or impacted by it. +For example, as a data modeler, you can review the details of a catalog asset to determine whether it is the one needed to add to your model. You can also view the impact and lineage diagram of that asset to see other assets it affects or is consumed by, as well as the data sources and transformations it underwent. -## Viewing the Catalog Asset Header +## Viewing the Header for an Asset -The asset header provides high-level information about the asset. +The header provides high-level information about the asset. ![](images/DataAssetHeader_e5ead6c.png) @@ -60,43 +60,55 @@ Description -Asset Name +Name and Type -Displays the asset name and type with an identifying icon. This name might not match the name of the underlying source object if it was enriched in the catalog. +Displays the asset name and type. The name might not match the name of the underlying source object if it was enriched in the catalog. -Asset Functional Status and Source System +Functional Status -Displays the functional status of the asset with the source system name and type. For information on the functional statuses, see [Publishing to the Catalog](https://help.sap.com/viewer/97d1d2f0e35d410c893e95a5ff3bee6f/DEV_CURRENT/en-US/f31d2d97afb0482a874acb0ec61465fe.html "You can determine what content is available to users who search the catalog. Single assets can be published directly from its information page or several assets can be published from the catalog home page. Once published, anyone who uses the catalog can discover the published content.") :arrow_upper_right:. +Displays the functional status of the asset. For information on the functional statuses, see [Publishing to the Catalog](https://help.sap.com/viewer/97d1d2f0e35d410c893e95a5ff3bee6f/DEV_CURRENT/en-US/f31d2d97afb0482a874acb0ec61465fe.html "You can determine what content is available to users who search the catalog. Single assets can be published directly from its information page or several assets can be published from the catalog home page. Once published, anyone who uses the catalog can discover the published content.") :arrow_upper_right:. -Tabs +Summary -Select a tab to view more information about the asset, such as an overview of the asset's properties and descriptions, a preview of the asset's details, and a diagram of the asset's lineage and its impact on other objects. +Displays a summary description of the asset. If you want a more detailed description, select the *Documentation* tab. -Actions +Catalog Activity + + + + +Displays date and time when the asset was added to the catalog and when it was last updated. For example, you can see when the asset was added to the catalog and when it was last changed. You can also find the date and time when the asset was enriched on and published and by which user. + + + + + + +Toolbar @@ -106,40 +118,46 @@ Select the action you want to perform on the asset. - *Open*: Opens the asset in the source system where you can view or edit it. This button appears if you have permission to access the asset in the source system. - \(Add to Favorites\): Adds frequently used assets to your favorites. +- *Open Impact and Lineage Analysis*: Opens a dialog that displays the *Impact and Lineage Analysis* diagram. - - - + + - +Tabs -## Viewing the Catalog Asset Overview + + -Use the *Overview* tab to view general information about the asset and relationship links to the asset. The *Overview* tab is divided into the following sections: +Select a tab to view more information about the asset, such as an overview of the asset's properties from the source system, a more detailed description of the asset, semantic enrichments, and more. -- Overview + + + -- Relationships + + -**Asset Overview** +## Viewing an Asset's Source Properties -Displays the properties and description of the asset. This information is extracted from a data source or the catalog. +You can view the source properties of the asset by selecting the *Overview* tab or *Overview* \> *Source*. This information is extracted from the source system. ![](images/CatalogCardPropertyDesc_1acb3e1.png) -**Overview** +The following table shows some common source properties that are extracted from the source system. Other source properties that are specific to the asset and the source system can also appear within these source properties or under a separate heading for **Additional Source Properties**. For more information about these properties not described here, see the documentation for the source system. + +**Common Source Properties** -
-Section Name +Property @@ -151,131 +169,91 @@ Description
-Properties +Name -Displays asset properties extracted from the source system and data enrichments added in the catalog. Properties are divided into source properties and catalog properties. - -**Source Properties** - -Source properties common among all assets include: - -- *Name*: The file name of the asset on the source system. The asset name can also include a *Business Name* or a *Technical Name*. For example, assets in SAP Analytics Cloud have one name that appears. Assets in SAP Datasphere have a business name, which is the descriptive name of the asset that helps you identify the asset, and a technical name, which is the name that is used in scripts and code and is synchronized with the business name. - -- *Created On*: The date and time on which the asset was created on the source system. The name of the user who created the asset is also shown. - -- *Changed On*: The date and time on which the asset was changed on the source system. The name of the user who changed the asset is also shown. - - -Source properties that show information about the source system include: - -- *Container Name*: Name of the location of the asset. For example, the container name for assets in SAP Datasphereis the space name. The container for assets in SAP Analytics Cloud is the parent folder name. - -- *Container Business Name*: Business name of the location of the asset. For example, the container business name for assets in SAP Datasphere is a descriptive name for the space. - -- *Path*: Folder location of the asset, if available. For example, this path appears for assets in the SAP Analytics Cloud. - -- *Type*: Type of location where the asset is saved. The location type appears for assets in the SAP Datasphere. - - -Source properties common among SAP Datasphere assets include: - -- *Semantic Usage*: The way the entity should be used. For example, Fact, Dimension, Hierarchy, or Text. - -- *Exposed for Consumption*: An indicator that shows whether the asset is made available for consumption in SAP Analytics Cloud and other BI clients. - - For more information on these properties, see [Creating a Graphical View](../creating-a-graphical-view-27efb47.md). - - -**Catalog Properties** - -If the asset data was enriched, the date of the change appears as a catalog property: - -- *Enriched On*: The date and time on which the data enrichment was added to the asset. The name of the user who enriched the asset is also shown. - - -**Additional Source Properties** - -Other source properties that can help you better understand and evaluate an asset appear under this section for additional source properties. For information about these properties, see the documentation for the source system. +The file name of the asset on the source system. The asset name can also include a *Business Name* or a *Technical Name*. For example, assets in SAP Analytics Cloud have one name that appears. Assets in SAP Datasphere have a business name, which is the descriptive name of the asset that helps you identify the asset, and a technical name, which is the name that is used in scripts and code and is synchronized with the business name.
-Descriptions +System Name and Type -Displays the asset description. - -- *Source Description*: This description is extracted from the source system and can't be edited. - -- *Description*: This catalog description is edited by users who have the *Catalog Administrator* role. - - - +The source system name and type of system \(for example, SAP Datasphere or SAP Analytics Cloud\).
- -**Asset Relationships** + + -Displays the relationships for the asset. These relationships can include glossary terms, tags, and KPIs that are linked to the asset. +Created On -![](images/Asset_Detail_Term_Tag_ac5b3b4.png) + + +The date and time on which the asset was created on the source system. The name of the user who created the asset is also shown. - + + - @@ -287,10 +265,10 @@ Displays a list of all key performance indicators \(KPIs\) that are linked to th ## Viewing Detailed Metadata for an Asset -Use the *Details* tab to see a preview of the detailed metadata about the asset, which can include columns, attributes, measures, dimensions, and properties specific to each object. This tab appears only if the asset has detailed metadata that can be shown. +You can see a preview of the detailed metadata about the asset by selecting *Overview* \> *Details*. The detailed metadata can include columns, attributes, measures, dimensions, and properties specific to each object. This tab option appears only if the asset has detailed metadata that can be shown. Each tab in this section represents the metadata type, such as measures or attributes, and has a table with its data. The number in brackets is the total number of rows for the table, with the preview showing up to 20 rows. If there are more than 20 rows for the table, select *Show All* to see the rest of the rows in a separate page. > ### Note: -> If you are viewing an SAP Analytics Cloud asset, this tab is available only for the following model types: planning and analytical models. For a list of supported object types, see [Connecting and Monitoring Source Systems](https://help.sap.com/viewer/97d1d2f0e35d410c893e95a5ff3bee6f/DEV_CURRENT/en-US/0b5de87f256f466f95b46d4bcaa52640.html "Users with the Catalog Administrator role can open the Remote Systems page to create connections to a variety of data sources in the same landscape. This page also includes tools for monitoring and managing data sources, allowing metadata for objects to be extracted and added to the catalog assets.") :arrow_upper_right:. +> If you are viewing an SAP Analytics Cloud asset, this section is available only for the following model types: planning and analytical models. For a list of supported object types, see [Connecting and Monitoring Source Systems](https://help.sap.com/viewer/97d1d2f0e35d410c893e95a5ff3bee6f/DEV_CURRENT/en-US/0b5de87f256f466f95b46d4bcaa52640.html "Users with the Catalog Administrator role can open the Remote Systems page to create connections to a variety of data sources in the same landscape. This page also includes tools for monitoring and managing data sources, allowing metadata for objects to be extracted and added to the catalog assets.") :arrow_upper_right:. ![](images/Catalog_Asset_Details_Tab_df97d1e.png) @@ -364,7 +342,7 @@ Select which columns you want to show in the table.
+ -Section Name +Changed On - - + + -Description +The date and time on which the asset was changed on the source system. The name of the user who changed the asset is also shown. - +
-Glossary Terms +Container Name and Container Business Name -Displays a list of business glossary terms that are linked to the asset. You can use the free text search to see if a particular term is linked to the asset. +The location name in the source system where the asset is saved. For example, the container name for assets in SAP Datasphere is the space name. The container name for assets in SAP Analytics Cloud is the parent folder name. + +The container can also include a *Container Business Name*. For example, the container business name for assets in SAP Datasphere is a descriptive name for the space. + +> ### Note: +> For SAP Datasphere, only information for the space appears. + +
-Tags +Path -Displays a hierarchical list of all tags that are linked to the asset. Tags help classify the types of assets that are in the catalog. You can use the free text search to see if a particular tag is linked to the asset. +Folder location of the asset, if available. This path does not appear for assets in SAP Datasphere.
-KPIs +Type -Displays a list of all key performance indicators \(KPIs\) that are linked to the asset. KPIs are used to track business requirements or goals. You can use the free text search to see if a particular KPI is linked to the asset. +Type of container where the asset is saved. The type appears for assets in the SAP Datasphere, and it is always Space.
-For information on the metadata that appears in this tab, see the help documentation for the source system and search for the data object or analytic object you want to know more about: +For information on the metadata that appears in this tab, see the help documentation for the source system and search for the object you want to know more about: - For SAP Datasphere, see [Acquiring, Preparing, and Modeling Data with SAP Datasphere](../acquiring-preparing-and-modeling-data-with-sap-datasphere-b4a5d02.md). @@ -373,19 +351,95 @@ For information on the metadata that appears in this tab, see the help documenta - For SAP Datasphere, SAP BW bridge, see [SAP Datasphere, SAP BW bridge](https://help.sap.com/docs/SAP_BW_BRIDGE/107a6e8a38b74ede94c833ca3b7b6f51/f2a4eb578452482fbbcb9078a8e51551.html). + + + + +## Viewing the Description and Semantic Enrichments for an Asset + +You can view the asset’s description and semantic enrichments to get a better idea of how you can use the asset for your business needs. + +**Viewing the Asset’s Description** + +The summary description in the header provides a short description of the asset. However, to get a more detailed description of the asset, select the *Documentation* tab. The information in this description can include rich text formatting, links to content, images, videos, and more. After reviewing this description, you can get a better idea of whether the asset meets your business needs and possibly get ideas on how you can use it. + +**Viewing the Asset’s Semantic Enrichments** + +Use the*Semantic Enrichment*tab to review glossary terms, tags, and KPIs that are assigned to the asset. The preview for each section shows up to 20 rows. To see more rows in a separate page, select *Show All*. + + + + + + + + + + + + + + + + + + + +
+ +Section Name + + + +Description + +
+ +Terms + + + +Displays a list of business glossary terms that are linked to the asset. If the terms originate from several different glossaries, each glossary will be represented by its own tab. The number in brackets for the tab is the number of terms assigned from that glossary. To find a particular term within a glossary tab, use the free text search. + +![](images/Semantic_Enrichment_-_Terms_82b734a.png) + +
+ +KPIs + + + +Displays a list of all key performance indicators \(KPIs\) that are linked to the asset. KPIs are used to track business requirements or goals. You can use the free text search to find a particular KPI linked to the asset. + +![](images/Semantic_Enrichment_-_KPIs_9e63d0c.png) + +
+ +Tags + + + +Displays a hierarchical list of all tags that are linked to the asset. If the tags originate from several different tag hierarchies, each tag hierarchy will be represented by its own tab. The number in brackets for the tab is the number of tags assigned from that tag hierarchy. To find a particular tag within a tag hierarchy tab, use the free text search. + +![](images/Semantic_Enrichment_-_Tags_047fb15.png) + +
+ -## Analyzing Data Impact and Lineage +## Analyzing the Impact and Lineage of an Asset -Use the *Lineage* tab to view the **Impact and Lineage Analysis** diagram. This diagram shows the data analysis of the asset and provides an end-to-end visualization of the asset dependencies across multiple systems and layers. It can help you better understand the lineage \(also known as data provenance\) and impacts of a selected asset in the catalog. Impact and lineage contain information about the source of the asset, the transformations it goes through, its final state, and objects affected by changes made to it. Impact and lineage serve distinct purposes. +Select the *Open Impact and Lineage Analysis* button in the header to see a diagram for the analyzed asset. This diagram shows the data analysis of the asset and provides an end-to-end visualization of the asset dependencies across multiple systems and layers. It can help you better understand the lineage \(also known as data provenance\) and impacts of a selected asset in the catalog. Impact and lineage contain information about the source of the object, the transformations it goes through, its final state, and assets affected by changes made to it. Impact and lineage serve distinct purposes. - *Lineage* is displayed to the left of the object \(or below it\). It shows objects that the analyzed asset uses as sources. It allows you to trace errors back to the root cause. - *Impact* is displayed to the right of the object \(or above it\). It shows objects that use the analyzed asset as a source. It allows you to understand the impact of changes on dependent objects. ![](images/Impact_and_Lineage_Catalog_View_4c0c62d.png) + + This diagram provides the data analysis of the asset and contains the following features. @@ -410,35 +464,41 @@ Description -Use the toolbar and diagram tools to control the layout of the diagram. Click \(Refresh\) to update the diagram with the latest changes. +Use the toolbar and diagram tools to control the layout of the diagram. Click *Reset* to restore the default layout. -\(2\) Source System +\(2\) Outermost Container -The source system is the outermost object and has an icon that represents the type of system \(for example, SAP Datasphere or SAP Analytics Cloud tenant\). The number in brackets indicates the total number of objects in the source system that are part of the impact or lineage of the analyzed object. +The outermost container represents one of the following: + +- A source system \(for example, SAP Datasphere or SAP Analytics Cloud tenant\) +- A data provider -You can expand or collapse a source system, using the \(Show/Hide All Objects\) menu on the top-right corner of the symbol. +The number in brackets indicates the total number of objects in the container that are part of the impact or lineage of the analyzed object. You can expand or collapse the container, using the \(Show/Hide All Objects\) menu on the top-right corner of the container. -\(3\) Container +\(3\) Inner Container -The container is directly inside the source system and has an icon that represents its type \(for example, SAP Datasphere space or SAP Analytics Cloud folder\). It contains assets that appear in the lineage of or that impact the analyzed object. The number in brackets indicates the total number of objects in the container that are part of the impact or lineage of the analyzed object. +The inner container represents one of the following: -You can expand or collapse a container, using the \(Show/Hide All Objects\) menu on the top-right corner of the container. +- A location in the source system \(for example, SAP Datasphere space or SAP Analytics Cloud folder\). It contains assets that either appear in the lineage or impact the analyzed object. If an asset is located within a sublocation \(for example, a subfolder\), you'll see a series of nested inner containers. +- A :package: data product. The data product is visible if you are a member of the context associated with the data product or if you are a member of the space where the data set has been installed and have **View** permission. Also, you will be able to view the details to see brief summary of the data product or open the data product page. + +You can expand or collapse a container, using the \(Show/Hide All Objects\) menu on the top-right corner of the container. The number in brackets indicates the total number of objects in the container that are part of the impact and lineage of the analyzed object. @@ -456,11 +516,16 @@ You can expand or collapse a container, using the  Authorized and unauthorized objects appear in the lineage or impact of the analyzed object. -- Authorized objects are published and can be discovered in the catalog. They have an icon that represents its type \(for example, \(View\)\). You can view the details page for the asset by clicking \(Open Asset Details\) icon. +- Authorized objects are published and can be discovered in the catalog. They have an icon that represents its type \(for example, \(View\)\). Click the \(Open Asset Details\) icon to view the details page. + + - For catalog assets, click the \(Open Asset Details\) icon to view its view the details page. -- Unauthorized objects are unpublished and are not available in the catalog. They are represented with the :lock: icon. + - For datasets, click a link that generates a remote table or view it in the different spaces where the data product has been installed. -- The analyzed object appears as a light blue object. They have an icon that represents its type \(for example, \(Story\)\). + +- Unauthorized objects are unpublished assets or datasets or are objects that you do not have access permission to in the source system. They are represented with the :lock: icon. + +- The analyzed object appears as a light blue object. They have an icon that represents its type \(for example, \(Story\)\) or \(Transformation\). You can show or hide the objects on either side of any object by clicking the \(Show Next Level\) or \(Hide All\) on the object. @@ -510,7 +575,7 @@ After you find the asset you want and have evaluated it, you might be able to op > ### Note: > For certain source systems, the *Open* button appears if the asset has been shared with you and you have permission to view or edit it. For example, if the asset is from SAP Datasphere or SAP Analytics Cloud, the *Open* button appears only if the asset has been shared with you in the source system and you have permission to view or edit it. > - > However, for some source systems, the *Open* button is not available regardless if the asset has been shared with you in the source system. For example, if the asset is from an SAP Datasphere, SAP BW bridge, the *Open* button does not appear. To view or edit the asset, you must open it directly in the source system. + > However, for some source systems, the *Open* button is not available regardless of whether the asset has been shared with you in the source system. For example, if the asset is from an SAP Datasphere, SAP BW bridge, the *Open* button does not appear. To view or edit the asset, you must open it directly in the source system. ![](images/Asset_Details_-_Open_Button_24913a7.png) @@ -523,9 +588,9 @@ After you find the asset you want and have evaluated it, you might be able to op ## Results -If you edited a file that is saved in SAP Datasphere or SAP Analytics Cloud, the catalog automatically detects the change. The metadata for the asset is automatically updated in real time, and the functional status label *Current* is applied. +Because the catalog monitors changes to objects saved in SAP Datasphere and SAP Analytics Cloud source systems, these changes are detected in real time. The metadata for the assets are automatically extracted, and the functional status label *Current* is applied. -If you edited a file that is saved in SAP Datasphere, SAP BW bridge, an user with the appropriate permission can run a manual synchronization to ensure the catalog assets are up-to-date. +The catalog does not monitor changes to objects saved in SAP Datasphere, SAP BW bridge source systems. To ensure that these assets are up-to-date, a user with the appropriate permission must run a manual synchronization, which will manually extract all metadata for the assets. @@ -549,7 +614,7 @@ After you evaluate and determine that the asset is the right one for your needs, > ### Tip: -> Before you search for an asset in the catalog, determine which application you want to use the asset in and open it in a new browser tab. By keeping the catalog open in a separate tab, you can find the asset you want and have its property information readily available as you switch between tabs. +> Before you search for an asset in the catalog, determine which application you want to use the asset in and open it in a new browser tab. By keeping the catalog opened in a separate tab, you can find the asset you want and have its property information readily available as you switch between tabs. > > Depending on the SAP application you are using, you can open it from the \(*Product Switch*\) or from the side navigation. For example, to use SAP Datasphere, in the side navigation area, right-click the application you want to use and click *Open App in New Tab*. Or to use SAP Analytics Cloud, in the side navigation area, right-click any application and click *Open App in New Tab*. In the shell bar click \(*Product Switch*\) and click *Analytics*. @@ -581,11 +646,14 @@ After you evaluate and determine that the asset is the right one for your needs, The catalog automatically detects the change in real time: -- If you created a new file, a new unpublished catalog asset is created and the functional status is set to *Current*. This asset won't be available in the catalog until a user with the *Catalog Administrator* role enriches the metadata and publishes it. +- If you created a new file, a new unpublished catalog asset is created and the functional status is set to *Current*. This asset will only be visible to users who have the *Catalog Administrator* role until they enrich it and then publish it to the catalog. After the asset is published, then it will be available for all catalog users to find. - If you edited an existing file, the metadata for the asset is automatically updated. +> ### Note: +> For files in SAP Datasphere, SAP BW bridge, a user with the necessary permission must run a manual synchronization to add a new asset to the catalog or update an existing asset. + **Related Information** diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md index 328d682..81ea574 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md @@ -267,7 +267,7 @@ You can change the view to see different information. **Related Information** -[Evaluating Catalog Assets](evaluating-catalog-assets-dc061a2.md "When you find the asset you want, you can select it to view its overview information, a preview of its detailed metadata, and a diagram of its impact and lineage. This information includes metadata that is extracted from the source system and data enrichments added in the catalog.") +[Evaluating Catalog Assets](evaluating-catalog-assets-dc061a2.md "After finding the asset you want, select it to view an overview of its information, a preview of its detailed metadata, and a diagram illustrating its impact and lineage. This information encompasses metadata extracted from the source system as well as data enrichments incorporated in the catalog.") [Evaluating your Data Product](../evaluating-your-data-product-335f49b.md "Each data product has a dedicated page that describes the data product in detail to allow a transparent elaboration.") diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Detail_Term_Tag_ac5b3b4.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Detail_Term_Tag_ac5b3b4.png deleted file mode 100644 index adebcd0..0000000 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Detail_Term_Tag_ac5b3b4.png and /dev/null differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Open_Button_24913a7.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Open_Button_24913a7.png index 21e7d6d..a203c44 100644 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Open_Button_24913a7.png and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Open_Button_24913a7.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Related_Object_Popup_8bcfe1a.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Related_Object_Popup_8bcfe1a.png index 069209a..13e213c 100644 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Related_Object_Popup_8bcfe1a.png and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Asset_Details_-_Related_Object_Popup_8bcfe1a.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/CatalogCardPropertyDesc_1acb3e1.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/CatalogCardPropertyDesc_1acb3e1.png index f0d7739..57a1804 100644 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/CatalogCardPropertyDesc_1acb3e1.png and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/CatalogCardPropertyDesc_1acb3e1.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Catalog_Asset_Details_Tab_df97d1e.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Catalog_Asset_Details_Tab_df97d1e.png index c606377..529e54f 100644 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Catalog_Asset_Details_Tab_df97d1e.png and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Catalog_Asset_Details_Tab_df97d1e.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/DataAssetHeader_e5ead6c.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/DataAssetHeader_e5ead6c.png index 136f191..204251f 100644 Binary files a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/DataAssetHeader_e5ead6c.png and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/DataAssetHeader_e5ead6c.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_KPIs_9e63d0c.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_KPIs_9e63d0c.png new file mode 100644 index 0000000..f6dda41 Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_KPIs_9e63d0c.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Tags_047fb15.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Tags_047fb15.png new file mode 100644 index 0000000..451262b Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Tags_047fb15.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Terms_82b734a.png b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Terms_82b734a.png new file mode 100644 index 0000000..46f19de Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/images/Semantic_Enrichment_-_Terms_82b734a.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/sharing-tables-and-views-to-other-spaces-64b318f.md b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/sharing-tables-and-views-to-other-spaces-64b318f.md index 2957d0b..fc3a410 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/sharing-tables-and-views-to-other-spaces-64b318f.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/sharing-tables-and-views-to-other-spaces-64b318f.md @@ -78,10 +78,10 @@ Now that the data is protected, the *Sales* view and the *Products* table can bo Entities with a semantic usage of *Fact* or *Dimension* commonly have dependencies on other entities and when sharing them, you must also share these associated entities in order to make the services they provide work in the target space: -- Dimensions - Providing categories to analyze measures \(see [Creating a Dimension](../Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\) +- Dimensions - Providing categories to analyze measures \(see [Create a Dimension to Categorize Data](../Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\) - Text entities - Providing translations of text values \(see [Create a Text Entity for Attribute Translation](../Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\) -- External hierarchies - Providing drill-down capabilities \(see [Creating an External Hierarchy](../Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\) -- Hierarchies with directories - Including all their supporting entities \(see [Creating a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\) +- External hierarchies - Providing drill-down capabilities \(see [Create an External Hierarchy for Drill-Down](../Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\) +- Hierarchies with directories - Including all their supporting entities \(see [Create a Hierarchy with Directory](../Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\) - Value help entities - Providing values for input parameters \(see [Create an Input Parameter](../create-an-input-parameter-53fa99a.md)\) - Lookup entities - Providing help in deriving values for variables \(see [Add a Variable](../Modeling-Data-in-the-Data-Builder/add-a-variable-cdd8fa0.md)\) diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-hierarchy-to-a-dimension-218b7e6.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-hierarchy-to-a-dimension-218b7e6.md index 04fb5a3..5683094 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-hierarchy-to-a-dimension-218b7e6.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-hierarchy-to-a-dimension-218b7e6.md @@ -14,7 +14,7 @@ You can specify the following types of hierarchy: - Parent-Child - the hierarchy is recursive, may have any number of levels, and is defined by specifying a parent column and a child column within the dimension. For example, a departmental hierarchy could be modeled with the `Parent Department ID` and `Department ID` columns. - Level-Based - the hierarchy is non-recursive, has a fixed number of levels, and is defined by specifying two or more level columns within the dimension. For example, a time hierarchy could be modeled with the: `Year`, `Quarter`, `Month`, `Week`, and `Day` columns. -- External Hierarchy - the parent-child hierarchy information is contained in a seperate entity, which needs to be associated with the dimension \(see [Creating an External Hierarchy](creating-an-external-hierarchy-dbac7a8.md)\). +- External Hierarchy - the parent-child hierarchy information is contained in a seperate entity, which needs to be associated with the dimension \(see [Create an External Hierarchy for Drill-Down](create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). > ### Note: > You can create more than one hierarchy for a dimension, but they must all be of the same type \(internal and external Parent-Child hierarchies can be mixed\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md index 9599514..dac7418 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md @@ -15,7 +15,7 @@ This topic contains the following sections: ## Use Facts with Analytic Models to Expose Data to SAP Analytics Cloud -Facts \(see [Creating a Fact](creating-a-fact-30089bd.md)\) allow you to model data in all the ways familiar from analytical datasets, but they are not intended to be consumed directly in SAP Analytics Cloud. +Facts \(see [Create a Fact to Contain Measurable Data](create-a-fact-to-contain-measurable-data-30089bd.md)\) allow you to model data in all the ways familiar from analytical datasets, but they are not intended to be consumed directly in SAP Analytics Cloud. The preferred way to expose data to SAP Analytics Cloud is now to identify your measures in a table or view with a semantic usage of *Fact* and then to use this fact in one or more analytic models, each of which can be consumed by one or more stories \(see [Creating an Analytic Model](creating-an-analytic-model-e5fbe9e.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md similarity index 89% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md index b942881..005d6e2 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md @@ -2,7 +2,7 @@ -# Creating a Dimension +# Create a Dimension to Categorize Data Select a *Semantic Usage* of *Dimension* to indicate that your entity contains attributes that can be used to analyze and categorize measures defined in other entities. @@ -32,7 +32,7 @@ Typical types of dimensions include: 1. In the table editor or view editor output node side panel, set the *Semantic Usage* property to *Dimension*. -2. Specify your attributes \(see [Specify Attributes](specify-attributes-cedc59c.md)\). +2. Specify your attributes \(see [Specify Attributes as Keys, Units, and Other Characteristics](specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md)\). 3. Set attributes as keys to indicate that the data they contain can uniquely identify records. @@ -44,7 +44,7 @@ Typical types of dimensions include: To set an attribute as a key column, select the checkbox in the *Key* column or hover over the attribute in the side panel and click \(Menu\)** \> *Set as Key*. -4. \[optional\] Create associations to point to other entities \(see [Create an Association](../create-an-association-66c6998.md)\). +4. \[optional\] Create associations to point to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). A *Dimension* can point to a: @@ -56,7 +56,7 @@ Typical types of dimensions include: - *Input Parameters* - Create input parameters to require the user to enter a value for use in calculated column, filter, and aggregation nodes \(see [Create an Input Parameter](../create-an-input-parameter-53fa99a.md)\). - *Data Persistence* - Persist the view data to improve performance \(see [Persist View Data](../persist-view-data-9bd12cf.md)\). - - *Associations* - Create associations to other entities \(see [Create an Association](../create-an-association-66c6998.md)\). + - *Associations* - Create associations to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - *Data Access Controls* - Add data access controls to apply row-based security and control access to individual rows based on various criteria \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\). - *Business Purpose* - Provide a description, purpose, contacts, and tags to help other users understand your entity. - *Dependent Objects* - If your entity is used as a source or association target for other entities, then they are listed here \(see [Review the Objects That Depend on Your Table or View](../review-the-objects-that-depend-on-your-table-or-view-ecac5fd.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md similarity index 83% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md index 1a70954..5756384 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md @@ -2,7 +2,7 @@ -# Creating a Fact +# Create a Fact to Contain Measurable Data Select a *Semantic Usage* of *Fact* to indicate that your entity contains numerical measures that can be analyzed. @@ -36,9 +36,9 @@ In this example, *Regional Sales* is a *Fact* with: > ### Note: > To consume your data in SAP Analytics Cloud, add it to an analytic model \(see [Creating an Analytic Model](creating-an-analytic-model-e5fbe9e.md)\). -3. Specify one or more measures \(see [Specify Measures](specify-measures-33f7f29.md)\). +3. Specify one or more measures \(see [Specify Measures to Analyze](specify-measures-to-analyze-33f7f29.md)\). -4. Specify your attributes \(see [Specify Attributes](specify-attributes-cedc59c.md)\). +4. Specify your attributes \(see [Specify Attributes as Keys, Units, and Other Characteristics](specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md)\). 5. \[optional\] Set attributes as keys to indicate that the data they contain can uniquely identify records. @@ -47,18 +47,18 @@ In this example, *Regional Sales* is a *Fact* with: To set an attribute as a key column, select the checkbox in the *Key* column or hover over the attribute in the side panel and click \(Menu\)** \> *Set as Key*. -6. \[optional\] Create associations to point to other entities \(see [Create an Association](../create-an-association-66c6998.md)\). +6. \[optional\] Create associations to point to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). A *Fact* can point to a: - *Dimension* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. - - *Text Entity* - An attribute in the \(source\) *Fact* must be mapped to the \(target\) *Text Entity* identifier key column. + - *Text Entity* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Text Entity* identifier key column. 7. Complete or consult other sections as appropriate: - *Input Parameters* - Create input parameters to require the user to enter a value for use in calculated column, filter, and aggregation nodes \(see [Create an Input Parameter](../create-an-input-parameter-53fa99a.md)\). - *Data Persistence* - Persist the view data to improve performance \(see [Persist View Data](../persist-view-data-9bd12cf.md)\). - - *Associations* - Create associations to other entities \(see [Create an Association](../create-an-association-66c6998.md)\). + - *Associations* - Create associations to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - *Data Access Controls* - Add data access controls to apply row-based security and control access to individual rows based on various criteria \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\). - *Business Purpose* - Provide a description, purpose, contacts, and tags to help other users understand your entity. - *Dependent Objects* - If your entity is used as a source or association target for other entities, then they are listed here \(see [Review the Objects That Depend on Your Table or View](../review-the-objects-that-depend-on-your-table-or-view-ecac5fd.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md similarity index 93% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md index 4a28c62..465191c 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md @@ -1,6 +1,6 @@ -# Creating a Hierarchy with Directory +# Create a Hierarchy with Directory Select a *Semantic Usage* of *Hierarchy with Directory* to indicate that your entity contains one or more parent-child hierarchies and has an association to a directory dimension containing a list of the hierarchies. @@ -13,12 +13,12 @@ For more information and walkthroughs, see also: This topic contains the following sections: -- [Example: SAP S/4HANA Cloud General Ledger Account Hierarchy](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_example) -- [Prepare the Leaf Node and Other Hierarchy Node Dimensions and Text Entities](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_dimension) -- [Prepare the Hierarchy Directory Entity and Text Entities](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_directory) -- [Prepare the Hierarchy Entity](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_hierarchy) -- [Use a Hierarchy in an Analytic Model](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_use_am) -- [Use a Hierarchy in an SAP Analytics Cloud Story](creating-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_use_sac) +- [Example: SAP S/4HANA Cloud General Ledger Account Hierarchy](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_example) +- [Prepare the Leaf Node and Other Hierarchy Node Dimensions and Text Entities](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_dimension) +- [Prepare the Hierarchy Directory Entity and Text Entities](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_directory) +- [Prepare the Hierarchy Entity](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_hierarchy) +- [Use a Hierarchy in an Analytic Model](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_use_am) +- [Use a Hierarchy in an SAP Analytics Cloud Story](create-a-hierarchy-with-directory-36c39ee.md#loio36c39eee184c485a80ebce9d0fec49ec__section_use_sac) @@ -64,7 +64,7 @@ In our example, `GLAccountInChartOfAccounts` is the leaf node dimension and `GLA Your leaf node dimension must have a key and will contain records of members that are related in one or more parent-child hierarchies. - For more information about dimensions, see [Creating a Dimension](creating-a-dimension-5aae0e9.md). + For more information about dimensions, see [Create a Dimension to Categorize Data](create-a-dimension-to-categorize-data-5aae0e9.md). 2. In the *Associations* section, click *New* \> *Hierarchy Association*, select your hierarchy entity and complete the mapping. 3. In the *Associations* section, click *New* \> *Text Association*, select the appropriate text entity and complete the mapping. diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-association-414df15.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-association-414df15.md deleted file mode 100644 index d4f7efe..0000000 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-association-414df15.md +++ /dev/null @@ -1,38 +0,0 @@ - - - - -# Create a Text Association - -Create a text association to link your entity to a text entity, which will provide text in one or more languages for an attribute. - - - -## Procedure - -1. In the *Associations* section of your entity, click:arrow_right: \> *Text Association* to open the *Select Object* dialog listing available text entities. - - Alternatively, in a view side panel, in the *Attributes* section, hover over an attribute and click \(More\) \> *Add Text Association*. - -2. Select a target entity and click *OK*. - - Find available objects by entering the object's name in the search bar or click \(Show filters\) and filter by *Semantic Usage* or other criteria. - -3. In the *Mappings* section, map the appropriate attributes from your entity to those in the text entity: - - - A default mapping is automatically created by matching a selected element to the first key element whose *Semantic Type* is *None*. - - To delete a mapping, select the link and then click \(Delete\). - - To manually map columns, drag a column from the left list and drop it onto a column in the right list. - - You can filter the *Mappings* section to show all, mapped, or unmapped pairs of columns. - - You can filter or sort the left or right column lists independently - - > ### Note: - > When you have defined a compound key for a dimension, you must map all key columns to the text entity. You can only provide translations for the representative key column. Other key columns cannot be translated. See [Compound Keys and Representative Keys](set-key-columns-to-uniquely-identify-records-d9ef2c9.md#loiod9ef2c91f6d647e584bad51999e441cd__section_compound_keys). - - The icon signals that an attribute is mapped to a text entity. - -4. Click \(Save\)** \> *Save* to save your entity or click \(Deploy\) to save and deploy it immediately. - - For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md). - - diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md index d753666..6e98f3f 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md @@ -19,7 +19,7 @@ For example: ![](images/Text_Entity_Example_2b15da2.png) > ### Note: -> When a dimension has a compound key defined, you can only provide translations for the representative key column. Other key columns cannot be translated. See [Compound Keys and Representative Keys](set-key-columns-to-uniquely-identify-records-d9ef2c9.md#loiod9ef2c91f6d647e584bad51999e441cd__section_compound_keys). +> When a dimension has a compound key defined, you can only provide translations for the representative key column. Other key columns in the compound key cannot be translated. See [Compound Keys and Representative Keys](set-key-columns-to-uniquely-identify-records-d9ef2c9.md#loiod9ef2c91f6d647e584bad51999e441cd__section_compound_keys). @@ -27,7 +27,7 @@ For example: 1. In the table editor or view editor output node side panel, set the *Semantic Usage* property to *Text*. -2. Specify your attributes \(see [Specify Attributes](specify-attributes-cedc59c.md)\). +2. Specify your attributes \(see [Specify Attributes as Keys, Units, and Other Characteristics](specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md)\). You must specify at least the following attributes: diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md new file mode 100644 index 0000000..3b8bc7e --- /dev/null +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md @@ -0,0 +1,196 @@ + + + + +# Create an Association to Define a Semantic Relationship Between Entities + +Click the *Create* button in the *Associations* section of the side panel of your table or view to create an association to another data entity and define a semantic relationship between them. + +This topic contains the following sections: + +- [Introduction to Associations](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_intro) +- [Create an Association to a Dimension](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_dimension) +- [Create an Association to a Text Entity](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_text) +- [Create an Association to a Hierarchy or a Hierarchy with Directory](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_hierarchy) +- [Copy Associations from a Source](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_from_source) +- [Consuming Associations in an Analytic Model](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_analytic_model) + + + + + +## Introduction to Associations + +When you create a join in a view, you are immediately combining the data from the two sources based on the definition of the join mapping. In contrast, creating an association will merely prepare the conditions for performing a join in the future. A join is a one-time operation, while an association can be used to do any number of joins in different contexts. + +You can create an association from any table or view to any other table or view at any level of the data layer, but they are required when defining the semantic relationships between facts, dimensions, text entities, and hierarchies. Since associations need to identify specific records in the entities they point to, they generally require key columns to be set in either or both entities in the relationship \(see [Set Key Columns to Uniquely Identify Records](set-key-columns-to-uniquely-identify-records-d9ef2c9.md). + +You can create associations in the: + +- E/R model editor \(for any table or view\), in the side panel *Associations* section or by drawing associations in the diagram \(see [Create an Association in an E/R Model Diagram](../create-an-association-in-an-e-r-model-diagram-82e6869.md)\). +- Table editor *Associations* section. +- Graphical view editor/SQL view editor, in the output node *Associations* section. + +In this simple star schema example: + +- The `Acme Sales` fact has associations to four dimensions. +- The `Acme Product` and `Time` dimensions have associations to text entities. +- The `Acme Salespeople` dimension has an association to a hierarchy. + +![](images/Star_Schema_9239037.png) + + + + + +## Create an Association to a Dimension + +You can create an association to a dimension from a fact, a dimension, or a hierarchy with directory to provide context and categories when analyzing data. The association is mapped from one or more attributes in the source entity \(which act as foreign keys\) to the one or more attributes in the dimension that are marked as keys. + +In this example, the `Acme Sales View` fact, has associations to four dimensions to allow the sales data measures to be analyzed by : + +- Geographical area - the attribute `City ID` is mapped to the primary key `City ID` in `Acme Geo Dimension`. +- Product, product line, and product category - the attribute `Product ID` is mapped to the primary key `Product ID` in `Acme Product Dimension`. +- Salesperson - the attribute `Salesperson ID` is mapped to the primary key `ID` in `Acme Salesperson Dimension`. +- Time - the attribute `Date` is mapped to the primary key `Date` in `Time Dimension - Day`. + +![](images/Associations_Example_-_Dimension_459c70f.png) + +For information about dimensions, see [Create a Dimension to Categorize Data](create-a-dimension-to-categorize-data-5aae0e9.md). + +1. Open the table or view from which you want to create the association.. + + Alternatively, select the entity in an E/R model to open its *Properties* panel. + +2. In the *Associations* section, click \(Create Association\) *Association* to open the *Select Object* dialog, listing all the entities available in the space. +3. Select the appropriate dimension from the list and click *OK* to create the association and open it in the side panel. + + You can filter the list using the search field or by clicking \(Show filters\) to open the filter panel, and selecting any of the available filter criteria. + +4. Review the proposed *Business Name* and *Technical Name* and the columns mapped by default in the *Mappings* section. + + > ### Note: + > You must complete the mappings as follows: + > + > - *Fact* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. + > - *Dimension* - One attribute in the \(source\) *Dimension* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. + > - *Hierarchy with Directory*: + > - A *Dimension* acting as its directory - The hierarchy name attribute in the \(source\) hierarchy entity must be mapped to the primary key column in the \(target\) dimension. + > - Any non-leaf *Dimension* providing nodes to the hierarchy - The appropriate node type values columns in the \(source\) hierarchy must be mapped to the key columns in the \(target\) *Dimension*. + +5. Click *< \(Back\)* in the table editor \(or use the breadcrumbs in the side panel\) to return to the list of associations, where the new association now appears. + + + + + +## Create an Association to a Text Entity + +You can create an association to a text entity from a fact or a dimension to provide text values for an attribute in one or more languages. The association is mapped from one or more attributes in the source entity that require text labels to the one or more attributes in the text entity that are marked as keys and have a semantic type of `None`. + +In this example, the `Time Dimension - Day` dimension has associations to three text entities to provide text labels in multiple languages for three attributes: + +- The attribute `Day of Week` is mapped to `Identifier` in `Translation Table - Day` to provide text labels for the names of days. +- The attribute `Month` is mapped to `Identifier` in `Translation Table - Month` to provide text labels for the names of months. +- The attribute `Quarter` is mapped to `Identifier` in `Translation Table - Quarter` to provide text labels for the names of quarters. + +: + +![](images/Associations_Example_-_Text_Entity_e1b5edc.png) + +For information about text entities, see [Create a Text Entity for Attribute Translation](create-a-text-entity-for-attribute-translation-b25726d.md). + +1. Open the table or view from which you want to create the association.. + + Alternatively, select the entity in an E/R model to open its *Properties* panel. + +2. In the *Associations* section, click \(Create Association\) *Text Association* to open the *Select Object* dialog, listing all the text entities available in the space. +3. Select the appropriate text entity from the list and click *OK* to create the association and open it in the side panel. + + You can filter the list using the search field or by clicking \(Show filters\) to open the filter panel, and selecting any of the available filter criteria. + +4. Review the proposed *Business Name* and *Technical Name* and the columns mapped by default in the *Mappings* section. + + > ### Note: + > You must complete the mappings as follows: + > + > - *Fact* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Text Entity* identifier key column. + > - *Dimension* - One attribute in the \(source\) *Dimension* must be mapped to each \(target\) *Text Entity* identifier key column. + > + > When you have defined a compound key for a dimension, you must map all key columns to the text entity. You can only provide translations for the representative key column. Other key columns cannot be translated. See [Compound Keys and Representative Keys](set-key-columns-to-uniquely-identify-records-d9ef2c9.md#loiod9ef2c91f6d647e584bad51999e441cd__section_compound_keys). + +5. Click *< \(Back\)* in the table editor \(or use the breadcrumbs in the side panel\) to return to the list of associations, where the new association now appears. + + The icon in the list of attributes signals that an attribute is mapped to a text entity. + + + + + + +## Create an Association to a Hierarchy or a Hierarchy with Directory + +You can create an association to a hierarchy \(or a hierarchy with directory\) from a dimension, to support drill down and up in the dimension members. The association is mapped from one or more primary key attributes in the source dimension to one or more child attributes in the hierarchy that are marked as keys. + +In this example, the `Acme Salesperson Dimension` has an association to a hierarchy to allow drill down and up in the sales organization structure, where the `ID` primary key attribute is mapped to the `Child ID` child key attribute in `Acme Salespeople Hierarchy`: + +![](images/Associations_Example_-_Hierarchy_4aee7d2.png) + +For information about hierarchies, see [Create an External Hierarchy for Drill-Down](create-an-external-hierarchy-for-drill-down-dbac7a8.md) and [Create a Hierarchy with Directory](create-a-hierarchy-with-directory-36c39ee.md). + +1. Open the table or view from which you want to create the association.. + + Alternatively, select the entity in an E/R model to open its *Properties* panel. + +2. In the *Associations* section, click \(Create Association\) *Hierarchy Association* \(or *Hierarchy with Directory Association*\) to open the *Select Object* dialog listing all the hierarchies \(or hierarchies with directories\) in the space. +3. Select the appropriate hierarchy from the list and click *OK* to create the association and open it in the side panel. + + You can filter the list using the search field or by clicking \(Show filters\) to open the filter panel, and selecting any of the available filter criteria. + +4. Review the proposed *Business Name* and *Technical Name* and the columns mapped by default in the *Mappings* section. + + > ### Note: + > You must complete the mappings as follows: + > + > - *Dimension* - Each key attribute in the \(source\) *Dimension* must be mapped to a \(target\) *Hierarchy* child attribute key column. + +5. Click *< \(Back\)* in the table editor \(or use the breadcrumbs in the side panel\) to return to the list of associations, where the new association now appears. + + + + + +## Copy Associations from a Source + +If your view has a source entity that itself has associations, you can copy one or more of those associations instead of creating it again: + +1. Open the view in its editor. +2. In the *Associations* section, click \(Create Association\) \> *Copy from Source* to open the *Copy Associations from Source* dialog. + + All associations available from all sources are listed, so long as the relevant attribute from the source has not been excluded from the current view. + +3. Select the associations to copy and click *Create* to return to the *Associations* section and add them to the list. + + + + + +## Consuming Associations in an Analytic Model + +Any number of analytic models can consume a single fact and the entities it connects to via associations \(see [Creating an Analytic Model](creating-an-analytic-model-e5fbe9e.md)\). + +When creating an analytic model, the modeler decides for each dimension towards which the fact has an association, whether to include it in the model \(see [Add a Dimension](add-a-dimension-4caf098.md)\). When a particular dimension is included, then the analytic model will follow the association to bring in the relevant data from the dimension. + +While it is possible to define multiple associations that use the same attribute as their source, the analytic model can use only one association per attribute. To be sure that the analytic model is using the correct association, review the attribute's *Text / Association* property. + +This property can contain: + +- An association pointing to a dimension \(see [Create an Association to a Dimension](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_dimension)\) +- A text association pointing to a text entity \(see [Create an Association to a Text Entity](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_text)\) +- An attribute with a semantic type of *Text* + +It is automatically filled when you create an association or a text association and map the attribute as the source of the association. If you want to specify an attribute with a semantic type of *Text* to act as a label for the column, then you must manually select the attribute here. + +> ### Note: +> In cases where multiple associations and/or text associations are defined on a single attribute, you can manually choose which association \(or local text attribute\) should be used by the analytic model by making the appropriate selection here. + diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md similarity index 98% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md index c1c6431..d88ec31 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md @@ -2,7 +2,7 @@ -# Creating an External Hierarchy +# Create an External Hierarchy for Drill-Down Select a *Semantic Usage* of *Hierarchy* to indicate that your entity contains parent-child relationships for members in a dimension. diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Dimension_459c70f.png b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Dimension_459c70f.png new file mode 100644 index 0000000..7304399 Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Dimension_459c70f.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Hierarchy_4aee7d2.png b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Hierarchy_4aee7d2.png new file mode 100644 index 0000000..9e6557e Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Hierarchy_4aee7d2.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Text_Entity_e1b5edc.png b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Text_Entity_e1b5edc.png new file mode 100644 index 0000000..fad512a Binary files /dev/null and b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/images/Associations_Example_-_Text_Entity_e1b5edc.png differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-data-in-the-data-builder-5c1e3d4.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-data-in-the-data-builder-5c1e3d4.md index 5d47c70..e339b60 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-data-in-the-data-builder-5c1e3d4.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-data-in-the-data-builder-5c1e3d4.md @@ -51,11 +51,11 @@ Use the *Semantic Usage* property to indicate the type of data contained in your ## Identify Measures to Analyze in a Fact -Facts are entities that contain numerical measures that can be analyzed and are the principal type of object that is consumed by BI clients \(see [Creating a Fact](creating-a-fact-30089bd.md)\). +Facts are entities that contain numerical measures that can be analyzed and are the principal type of object that is consumed by BI clients \(see [Create a Fact to Contain Measurable Data](create-a-fact-to-contain-measurable-data-30089bd.md)\). - To get started: Select a *Semantic Usage* of *Fact* to indicate that your entity contains numerical measures that can be analyzed. -- You must identify at least one measure \(see [Specify Measures](specify-measures-33f7f29.md)\). -- You can create associations to dimensions and text entities \(see [Create an Association](../create-an-association-66c6998.md)\). +- You must identify at least one measure \(see [Specify Measures to Analyze](specify-measures-to-analyze-33f7f29.md)\). +- You can create associations to dimensions and text entities \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - To expose your data for consumption in SAP Analytics Cloud, add it to an analytic model \(see [Creating an Analytic Model](creating-an-analytic-model-e5fbe9e.md)\). @@ -64,12 +64,12 @@ Facts are entities that contain numerical measures that can be analyzed and are ## Prepare Master Data for Grouping in a Dimension -Dimensions are entities that contain master data that categorize and group the numerical data contained in your measures \(see [Creating a Dimension](creating-a-dimension-5aae0e9.md)\). +Dimensions are entities that contain master data that categorize and group the numerical data contained in your measures \(see [Create a Dimension to Categorize Data](create-a-dimension-to-categorize-data-5aae0e9.md)\). - To get started: Select a *Semantic Usage* of *Dimension* to indicate that your entity contains attributes that can be used to analyze and categorize measures defined in other entities. - You must set at least one key column \(see [Set Key Columns to Uniquely Identify Records](set-key-columns-to-uniquely-identify-records-d9ef2c9.md)\). -- You can create associations to other dimensions, text entities, and hierarchies \(see [Create an Association](../create-an-association-66c6998.md)\). +- You can create associations to other dimensions, text entities, and hierarchies \(see [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - You can add parent-child or level-based hierarchies to support drill-down \(see [Add a Hierarchy to a Dimension](add-a-hierarchy-to-a-dimension-218b7e6.md)\). - You can make your dimension time-dependent, so that its members can change over time \(see [Enable Time-Dependency for a Dimension or Text Entity](enable-time-dependency-for-a-dimension-or-text-entity-11b2ff4.md)\). @@ -92,7 +92,7 @@ Text entities are entities that contain data to store strings in multiple langua ## Enable Drill-Down with a Hierarchy -External hierarchies are entities that contain data to define parent-child relationships for a dimension \(see [Creating an External Hierarchy](creating-an-external-hierarchy-dbac7a8.md)\). +External hierarchies are entities that contain data to define parent-child relationships for a dimension \(see [Create an External Hierarchy for Drill-Down](create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). - To get started: Select a *Semantic Usage* of *Hierarchy* to indicate that your entity contains parent-child relationships for members in a dimension. - You must specify the parent and child attributes and set the child attribute as a key. @@ -106,7 +106,7 @@ External hierarchies are entities that contain data to define parent-child relat ## Create Heterogeneous Hierarchies with a Hierarchy with Directory -A hierarchy with directory is an entity that contains one or more parent-child hierarchies and has an association to a directory dimension containing a list of the hierarchies. These types of hierarchy entities can include nodes from multiple dimensions \(for example, country, cost center group, and cost center\) and are commonly imported from SAP S/4HANA Cloud and SAP BW systems \(see [Creating a Hierarchy with Directory](creating-a-hierarchy-with-directory-36c39ee.md)\). +A hierarchy with directory is an entity that contains one or more parent-child hierarchies and has an association to a directory dimension containing a list of the hierarchies. These types of hierarchy entities can include nodes from multiple dimensions \(for example, country, cost center group, and cost center\) and are commonly imported from SAP S/4HANA Cloud and SAP BW systems \(see [Create a Hierarchy with Directory](create-a-hierarchy-with-directory-36c39ee.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-facts-dimensions-text-entities-and-hierarchies-f8a1a25.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-facts-dimensions-text-entities-and-hierarchies-f8a1a25.md new file mode 100644 index 0000000..eadf6bd --- /dev/null +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/modeling-facts-dimensions-text-entities-and-hierarchies-f8a1a25.md @@ -0,0 +1,31 @@ + + +# Modeling Facts, Dimensions, Text Entities, and Hierarchies + +You can enrich your entities with semantic information to make your data ready for analysis. + +SAP Datasphere helps you to: + +- Specify the semantic usage of each of your entities. See: + - [Create a Fact to Contain Measurable Data](create-a-fact-to-contain-measurable-data-30089bd.md) + - [Create a Dimension to Categorize Data](create-a-dimension-to-categorize-data-5aae0e9.md) + - [Create a Text Entity for Attribute Translation](create-a-text-entity-for-attribute-translation-b25726d.md) + - [Create an External Hierarchy for Drill-Down](create-an-external-hierarchy-for-drill-down-dbac7a8.md) + - [Create a Hierarchy with Directory](create-a-hierarchy-with-directory-36c39ee.md) + +- Identify measures and attributes, and assign semantic types to them. See: + - [Specify Measures to Analyze](specify-measures-to-analyze-33f7f29.md) + - [Specify Attributes as Keys, Units, and Other Characteristics](specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md) + - [Specify Semantic Types for Measures and Attributes](specify-semantic-types-for-measures-and-attributes-f7272c0.md) + +- Set key columns and create associations between entities. See: + - [Set Key Columns to Uniquely Identify Records](set-key-columns-to-uniquely-identify-records-d9ef2c9.md) + - [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md) + + +Your entities can be exposed for consumption: + +- Directly as relational objects via OData or ODBC \(views only\). See [Exposing a View For Consumption](exposing-a-view-for-consumption-40ec77e.md). +- Combined and further refined and enriched via an analytic model. See [Creating an Analytic Model](creating-an-analytic-model-e5fbe9e.md). +- Via further combination in the *Business Builder*. See [Modeling Data in the Business Builder](../Buisiness-Builder/modeling-data-in-the-business-builder-3829d46.md). + diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/set-key-columns-to-uniquely-identify-records-d9ef2c9.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/set-key-columns-to-uniquely-identify-records-d9ef2c9.md index fda87f5..23ad3df 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/set-key-columns-to-uniquely-identify-records-d9ef2c9.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/set-key-columns-to-uniquely-identify-records-d9ef2c9.md @@ -43,7 +43,7 @@ Mapping Keys When Creating Associations *Fact* -See [Creating a Fact](creating-a-fact-30089bd.md). +See [Create a Fact to Contain Measurable Data](create-a-fact-to-contain-measurable-data-30089bd.md). @@ -56,7 +56,7 @@ You may set one or more key attributes for a *Fact*, but none are required. A *Fact* can point to a: - *Dimension* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. -- *Text Entity* - An attribute in the \(source\) *Fact* must be mapped to the \(target\) *Text Entity* identifier key column. +- *Text Entity* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Text Entity* identifier key column. @@ -67,7 +67,7 @@ A *Fact* can point to a: *Dimension* -See [Creating a Dimension](creating-a-dimension-5aae0e9.md). +See [Create a Dimension to Categorize Data](create-a-dimension-to-categorize-data-5aae0e9.md). @@ -122,7 +122,7 @@ A *Text Entity* must not point to other entities. *Hierarchy* -See [Creating an External Hierarchy](creating-an-external-hierarchy-dbac7a8.md). +See [Create an External Hierarchy for Drill-Down](create-an-external-hierarchy-for-drill-down-dbac7a8.md). @@ -145,7 +145,7 @@ A *Hierarchy* will generally not point to other entities. *Hierarchy with Directory* -See [Creating a Hierarchy with Directory](creating-a-hierarchy-with-directory-36c39ee.md). +See [Create a Hierarchy with Directory](create-a-hierarchy-with-directory-36c39ee.md). @@ -188,6 +188,8 @@ A *Relational Dataset* can point to any other entity and should generally follow +See also [Create an Association to Define a Semantic Relationship Between Entities](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md). + @@ -317,5 +319,5 @@ To define a compound key and set its representative key: 6. Click *Close* to complete the definition of the compound key. > ### Note: -> When you define a compound key for a dimension and want to provide translations of the dimension members, you must map all key columns to the text entity. You can only provide translations for the representative key column. Other key columns cannot be translated. See [Compound Keys and Representative Keys](set-key-columns-to-uniquely-identify-records-d9ef2c9.md#loiod9ef2c91f6d647e584bad51999e441cd__section_compound_keys). +> When you define a compound key for a dimension and want to provide translations of the dimension members, you must map all key columns to the text entity and identify the representative key column in the text entity as well. You can only provide translations for the representative key column. Other key columns in the compound key cannot be translated. diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-cedc59c.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md similarity index 85% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-cedc59c.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md index 7406a42..034b3d7 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-cedc59c.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md @@ -2,7 +2,7 @@ -# Specify Attributes +# Specify Attributes as Keys, Units, and Other Characteristics Attributes are all columns that are not identified as measures, and can contain identifiers, master data, and other data that is used in support of analytics. Attributes appear in tables and views with any *Semantic Usage* except *Relational Dataset*. @@ -132,13 +132,16 @@ Specifies the purpose of the attribute when your entity is consumed by an analyt This property can contain: -- An association pointing to a dimension \(see [Create an Association](../create-an-association-66c6998.md)\) -- A text association pointing to a text entity \(see [Create a Text Association](create-a-text-association-414df15.md)\) +- An association pointing to a dimension \(see [Create an Association to a Dimension](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_dimension)\) +- A text association pointing to a text entity \(see [Create an Association to a Text Entity](create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md#loio66c6998af9974dac8f54a46515777560__section_text)\) - An attribute with a semantic type of *Text* -This property is automatically filled when you create an association or a text association. If you want to specify an attribute with a semantic type of *Text* to act as a label for the column, then you must manually select the attribute here. +It is automatically filled when you create an association or a text association and map the attribute as the source of the association. If you want to specify an attribute with a semantic type of *Text* to act as a label for the column, then you must manually select the attribute here. + +> ### Note: +> In cases where multiple associations and/or text associations are defined on a single attribute, you can manually choose which association \(or local text attribute\) should be used by the analytic model by making the appropriate selection here. + -In cases where multiple associations and/or text association are defined on a single attribute, you can manually choose which association \(or local text attribute\) should be used by the analytic model by making the appropriate selection here. diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-33f7f29.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-to-analyze-33f7f29.md similarity index 98% rename from docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-33f7f29.md rename to docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-to-analyze-33f7f29.md index 70974cd..a23e3aa 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-33f7f29.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/specify-measures-to-analyze-33f7f29.md @@ -2,7 +2,7 @@ -# Specify Measures +# Specify Measures to Analyze Measures appear in tables and views with a *Semantic Usage* of *Fact* and are columns containing numerical values that you want to analyze. Each *Fact* must contain at least one measure. @@ -17,7 +17,7 @@ Typical measures include: Measures are displayed in the *Measures* section of tables and views. > ### Note: -> In the graphical view and sql view editors, you can click the *Edit Columns* button in the *Measures* list to open it in a dialog. +> In the graphical view and SQL view editors, you can click the *Edit Columns* button in the *Measures* list to open it in a dialog. By default, all columns in a fact are identified as attributes, and you must convert one or more into measures: diff --git a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/using-the-data-preview-9f1fa73.md b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/using-the-data-preview-9f1fa73.md index 85dace3..fedebde 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/using-the-data-preview-9f1fa73.md +++ b/docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/using-the-data-preview-9f1fa73.md @@ -20,6 +20,14 @@ If you want to set filters, choose Add Fil + + +## Exporting Data + +By choosing \(Export\)** \> *Export Excel* or ** \> *Export CSV*, you can export the data as an Excel or CSV file. This enables you to share the intermediate results with colleagues, and to validate the calculations and measures. + + + ## Using the Builder Panel diff --git a/docs/Acquiring-Preparing-Modeling-Data/apply-a-data-access-control-8f79fc8.md b/docs/Acquiring-Preparing-Modeling-Data/apply-a-data-access-control-8f79fc8.md index 3d808f3..633053c 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/apply-a-data-access-control-8f79fc8.md +++ b/docs/Acquiring-Preparing-Modeling-Data/apply-a-data-access-control-8f79fc8.md @@ -34,4 +34,7 @@ For detailed information about defining and using data access controls, see [Sec Users opening your view in SAP Datasphere or in SAP Analytics Cloud or other analytics tools will only see the data permitted by the assignment of their username to the criteria defined in the data access control. + > ### Note: + > You can use the *View as User* tool in the *Data Viewer* panel to review the effects of the data access controls you apply by checking the records that another user will be allowed to see \(see [Viewing Object Data](viewing-object-data-b338e4a.md)\). + diff --git a/docs/Acquiring-Preparing-Modeling-Data/create-an-association-66c6998.md b/docs/Acquiring-Preparing-Modeling-Data/create-an-association-66c6998.md deleted file mode 100644 index da234eb..0000000 --- a/docs/Acquiring-Preparing-Modeling-Data/create-an-association-66c6998.md +++ /dev/null @@ -1,83 +0,0 @@ - - - - -# Create an Association - -Click the *Create* button in the *Associations* section of the side panel of your table or view to create an association to another data entity. You can create an association from any table or view to any other table or view at any level of the data layer, including to define the relationships between facts and dimensions among your consumable views. - - - -## Context - -You can create associations in the: - -- E/R model editor \(for any table or view\), in the side panel *Associations* section or by drawing associations in the diagram \(see [Create an Association in an E/R Model Diagram](create-an-association-in-an-e-r-model-diagram-82e6869.md)\). -- Table editor *Associations* section. -- Graphical view editor/SQL view editor, in the output node *Associations* section. - -In this example: - -- The `Sales Order` table has a semantic usage of *Fact* and has an association from its `Product ID` column to the `Product ID` key of the `Products` table, which is a *Dimension*. -- The `Products` *Dimension* has an association from its `PRODCATEGORYID` column to the `PRODCATEGORYID` key of the `Product Categories` table, which is also a *Dimension*. - -![](images/Associations_Example_7966865.png) - - - - - -## Procedure - -1. Open the table or view that will be the source of your association \(or select it in an E/R model to open its *Properties* panel\). - -2. In the *Associations* section, click \(Create Association\) to open the *Select Object* dialog. - - Find available objects by entering the object's name in the search bar or click \(Show filters\) and filter by *Semantic Usage* or other criteria. - -3. Select the appropriate target data entity from the list and click *OK* to create the association and open it in the side panel. - - The rules for creating associations depend on the *Semantic Usage* of the entity: - - - A *Fact* can point to a: - - - *Dimension* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. - - *Text Entity* - An attribute in the \(source\) *Fact* must be mapped to the \(target\) *Text Entity* identifier key column. - - - A *Dimension* can point to a: - - - *Dimension* - One attribute in the \(source\) *Dimension* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. - - *Text Entity* - One attribute in the \(source\) *Dimension* must be mapped to each \(target\) *Text Entity* identifier key column. - - *Hierarchy* - Each key attribute in the \(source\) *Dimension* must be mapped to a \(target\) *Hierarchy* child attribute key column. - - - A *Text Entity* must not point to other entities. - - - A *Hierarchy* will generally not point to other entities. - - - A *Hierarchy with Directory* must point to: - - - A *Dimension* acting as its directory - The hierarchy name attribute in the \(source\) hierarchy entity must be mapped to the primary key column in the \(target\) dimension. - - Any non-leaf *Dimension* providing nodes to the hierarchy - The appropriate node type values columns in the \(source\) hierarchy must be mapped to the key columns in the \(target\) *Dimension*. - - - A *Relational Dataset* can point to any other entity and should generally follow the rules for dimensions. - - -4. In the *General* section, review the default *Business Name* and *Technical Name* and modify them if appropriate. - -5. Specify the mapping of join columns in the *Join* section: - - - A default mapping is automatically created by matching column names if possible. For example if the originating entity contains a column, `Product ID`, and the target entity has a column with the same name, then a default mapping is created between these two columns. - - To delete a mapping, select the link and then click \(Delete\). - - To manually map columns, drag a column from the left list and drop it onto a column in the right list. - - You can filter the *Join* section to show only mapped or unmapped pairs of columns. - - You can filter or sort the left or right column lists independently - - > ### Note: - > To delete an association, select it in the list and click \(Delete Association\). - -6. If the view builds on another source view that itself has an association, you can copy that association: - - 1. Click \(Create Association\) \> *Copy from Source*. The *Copy Associations from Source* dialog opens and shows a table containing all source associations available to copy. - 2. Select the association\(s\) to copy and click *Create*. The new association\(s\) is added in the *Association* section in the output node's side panel. - - diff --git a/docs/Acquiring-Preparing-Modeling-Data/create-an-association-in-an-e-r-model-diagram-82e6869.md b/docs/Acquiring-Preparing-Modeling-Data/create-an-association-in-an-e-r-model-diagram-82e6869.md index 41ee686..4b78c73 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/create-an-association-in-an-e-r-model-diagram-82e6869.md +++ b/docs/Acquiring-Preparing-Modeling-Data/create-an-association-in-an-e-r-model-diagram-82e6869.md @@ -10,7 +10,7 @@ Create an association between two entities graphically in an E/R model diagram. ## Context -In addition to this method, you can also create associations in the side panel in an E/R model, or in the table editor, graphical view editor, or SQL view editor \(see [Create an Association](create-an-association-66c6998.md)\). +In addition to this method, you can also create associations in the side panel in an E/R model, or in the table editor, graphical view editor, or SQL view editor \(see [Create an Association to Define a Semantic Relationship Between Entities](Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). @@ -27,7 +27,7 @@ In addition to this method, you can also create associations in the side panel i - A *Fact* can point to a: - *Dimension* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Dimension* key column so that all target key columns are mapped. - - *Text Entity* - An attribute in the \(source\) *Fact* must be mapped to the \(target\) *Text Entity* identifier key column. + - *Text Entity* - One attribute in the \(source\) *Fact* must be mapped to each \(target\) *Text Entity* identifier key column. - A *Dimension* can point to a: diff --git a/docs/Acquiring-Preparing-Modeling-Data/creating-a-graphical-view-27efb47.md b/docs/Acquiring-Preparing-Modeling-Data/creating-a-graphical-view-27efb47.md index 0a978af..0e0dab1 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/creating-a-graphical-view-27efb47.md +++ b/docs/Acquiring-Preparing-Modeling-Data/creating-a-graphical-view-27efb47.md @@ -238,10 +238,10 @@ If you are comfortable writing SQL code or want to use SQL Script to create your Choose from the following: - - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Creating a Fact](Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Creating a Dimension](Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Creating an External Hierarchy](Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Creating a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Create a Fact to Contain Measurable Data](Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Create a Dimension to Categorize Data](Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Create an External Hierarchy for Drill-Down](Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Create a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Contains attributes used to provide textual content in one or more languages \(see [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - \[default\] Contains columns with no specific analytical purpose. - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). @@ -344,10 +344,10 @@ If you are comfortable writing SQL code or want to use SQL Script to create your 6. Based on the *Semantic Usage* of your entity, review and modify its *Columns*, *Attributes*, and/or *Measures*: - - *Fact* - Review the lists of measures and attributes \(see [Creating a Fact](Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Review the list of attributes \(see [Creating a Dimension](Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Define the parent and child columns \(see [Creating an External Hierarchy](Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Creating a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Review the lists of measures and attributes \(see [Create a Fact to Contain Measurable Data](Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Review the list of attributes \(see [Create a Dimension to Categorize Data](Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Define the parent and child columns \(see [Create an External Hierarchy for Drill-Down](Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Create a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Review the list of attributes \(see [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - Review the list of columns \(see [Columns](Acquiring-and-Preparing-Data-in-the-Data-Builder/columns-8f0f40d.md)\). - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). @@ -356,7 +356,7 @@ If you are comfortable writing SQL code or want to use SQL Script to create your - *Input Parameters* - Create input parameters to require the user to enter a value for use in calculated column, filter, and aggregation nodes \(see [Create an Input Parameter](create-an-input-parameter-53fa99a.md)\). - *Data Persistence* - Persist the view data to improve performance \(see [Persist View Data](persist-view-data-9bd12cf.md)\). - - *Associations* - Create associations to other entities \(see [Create an Association](create-an-association-66c6998.md)\). + - *Associations* - Create associations to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - *Data Access Controls* - Add data access controls to apply row-based security and control access to individual rows based on various criteria \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\). - *Business Purpose* - Provide a description, purpose, contacts, and tags to help other users understand your entity. - *Dependent Objects* - If your entity is used as a source or association target for other entities, then they are listed here \(see [Review the Objects That Depend on Your Table or View](review-the-objects-that-depend-on-your-table-or-view-ecac5fd.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/creating-an-sql-view-81920e4.md b/docs/Acquiring-Preparing-Modeling-Data/creating-an-sql-view-81920e4.md index 9d71535..06e3f7e 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/creating-an-sql-view-81920e4.md +++ b/docs/Acquiring-Preparing-Modeling-Data/creating-an-sql-view-81920e4.md @@ -216,10 +216,10 @@ If you are not comfortable with SQL, you can still build a view in SAP Dataspher Choose from the following: - - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Creating a Fact](Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Creating a Dimension](Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Creating an External Hierarchy](Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Creating a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Contains one or more measures and attributes. A fact typically has associations pointing to one or more dimensions and is consumed by analytic models \(see [Create a Fact to Contain Measurable Data](Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Contains attributes containing master data like a product list or store directory, and supporting hierarchies \(see [Create a Dimension to Categorize Data](Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Contains attributes defining a parent-child hierarchy \(see [Create an External Hierarchy for Drill-Down](Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Contains one or more parent-child hierarchies \(see [Create a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Contains attributes used to provide textual content in one or more languages \(see [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - \[default\] Contains columns with no specific analytical purpose. - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). @@ -322,10 +322,10 @@ If you are not comfortable with SQL, you can still build a view in SAP Dataspher 5. Based on the *Semantic Usage* of your entity, review and modify its *Columns*, *Attributes*, and/or *Measures*: - - *Fact* - Review the lists of measures and attributes \(see [Creating a Fact](Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md)\). - - *Dimension* - Review the list of attributes \(see [Creating a Dimension](Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md)\). - - *Hierarchy* - Define the parent and child columns \(see [Creating an External Hierarchy](Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md)\). - - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Creating a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md)\). + - *Fact* - Review the lists of measures and attributes \(see [Create a Fact to Contain Measurable Data](Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md)\). + - *Dimension* - Review the list of attributes \(see [Create a Dimension to Categorize Data](Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md)\). + - *Hierarchy* - Define the parent and child columns \(see [Create an External Hierarchy for Drill-Down](Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md)\). + - *Hierarchy with Directory* - Define all the necessary attributes and settings \(see [Create a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md)\). - *Text* - Review the list of attributes \(see [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md)\). - *Relational Dataset* - Review the list of columns \(see [Columns](Acquiring-and-Preparing-Data-in-the-Data-Builder/columns-8f0f40d.md)\). - *Analytical Dataset \(Deprecated\)* - Use *Fact* instead \(see [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md). @@ -334,7 +334,7 @@ If you are not comfortable with SQL, you can still build a view in SAP Dataspher - *Input Parameters* - Create input parameters to require the user to enter a value for use in calculated column, filter, and aggregation nodes \(see [Create an Input Parameter](create-an-input-parameter-53fa99a.md)\). - *Data Persistence* - Persist the view data to improve performance \(see [Persist View Data](persist-view-data-9bd12cf.md)\). - - *Associations* - Create associations to other entities \(see [Create an Association](create-an-association-66c6998.md)\). + - *Associations* - Create associations to other entities \(see [Create an Association to Define a Semantic Relationship Between Entities](Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - *Data Access Controls* - Add data access controls to apply row-based security and control access to individual rows based on various criteria \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\). - *Business Purpose* - Provide a description, purpose, contacts, and tags to help other users understand your entity. - *Dependent Objects* - If your entity is used as a source or association target for other entities, then they are listed here \(see [Review the Objects That Depend on Your Table or View](review-the-objects-that-depend-on-your-table-or-view-ecac5fd.md)\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/images/Associations_Example_7966865.png b/docs/Acquiring-Preparing-Modeling-Data/images/Associations_Example_7966865.png deleted file mode 100644 index da12286..0000000 Binary files a/docs/Acquiring-Preparing-Modeling-Data/images/Associations_Example_7966865.png and /dev/null differ diff --git a/docs/Acquiring-Preparing-Modeling-Data/impact-and-lineage-analysis-9da4892.md b/docs/Acquiring-Preparing-Modeling-Data/impact-and-lineage-analysis-9da4892.md index 0d9736a..57e5db0 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/impact-and-lineage-analysis-9da4892.md +++ b/docs/Acquiring-Preparing-Modeling-Data/impact-and-lineage-analysis-9da4892.md @@ -24,7 +24,7 @@ This topic contains the following sections: You can open the *Impact and Lineage Analysis* dialog from various screens: - In the *Repository Explorer* or the *Data Builder* start page, select an object to analyze and click \(Impact and Lineage Analysis\) in the toolbar. -- In the *Catalog*, click the *Lineage* tab of an asset page. +- In the *Catalog*, click the *Open Impact and Lineage Analysis* button on the asset details page. - In *Data Builder* object editors, click \(Impact and Lineage Analysis\) in the toolbar or, if the editor contains a diagram, select a table, view, or data flow symbol and click the tool in the symbol toolbar. In this example, a user opens the diagram to analyze the *Enriched Sales View* in the *Sales* space, which has two sources and which is a source for two objects in other spaces: @@ -362,7 +362,7 @@ In *Dependency Analysis* mode, it shows several other entities, to which it is l These additional link types display as follows:: -- \(Association\) - Association pointing to another entity to indicate a potential join between them \(see [Create an Association](create-an-association-66c6998.md)\). +- \(Association\) - Association pointing to another entity to indicate a potential join between them \(see [Create an Association to Define a Semantic Relationship Between Entities](Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md)\). - \(Data Access Control\) - Data access control providing row-level security \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\). diff --git a/docs/Acquiring-Preparing-Modeling-Data/index.md b/docs/Acquiring-Preparing-Modeling-Data/index.md index 6cc5ed9..57c74dc 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/index.md +++ b/docs/Acquiring-Preparing-Modeling-Data/index.md @@ -120,7 +120,6 @@ - [Create a Currency Conversion Column](create-a-currency-conversion-column-6e3d8be.md) - [Create a Unit Conversion Column](create-a-unit-conversion-column-23bc94f.md) - [Create an Input Parameter](create-an-input-parameter-53fa99a.md) - - [Create an Association](create-an-association-66c6998.md) - [Filter Data](filter-data-6f6fa18.md) - [Aggregate Data](aggregate-data-7733250.md) - [Visualize the Lineage of Columns and Input Parameters in a Graphical View](visualize-the-lineage-of-columns-and-input-parameters-in-a-graphical-view-a2426b7.md) @@ -154,19 +153,24 @@ - [Import Multiple Objects from a Connection](import-multiple-objects-from-a-connection-e720b13.md) - [Viewing Object Data](viewing-object-data-b338e4a.md) - [Modeling Data in the Data Builder](Modeling-Data-in-the-Data-Builder/modeling-data-in-the-data-builder-5c1e3d4.md) - - [Creating a Fact](Modeling-Data-in-the-Data-Builder/creating-a-fact-30089bd.md) - - [Specify Measures](Modeling-Data-in-the-Data-Builder/specify-measures-33f7f29.md) + - [Modeling Facts, Dimensions, Text Entities, and Hierarchies](Modeling-Data-in-the-Data-Builder/modeling-facts-dimensions-text-entities-and-hierarchies-f8a1a25.md) + - [Create a Fact to Contain Measurable Data](Modeling-Data-in-the-Data-Builder/create-a-fact-to-contain-measurable-data-30089bd.md) + - [Create a Dimension to Categorize Data](Modeling-Data-in-the-Data-Builder/create-a-dimension-to-categorize-data-5aae0e9.md) + - [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md) + - [Create an External Hierarchy for Drill-Down](Modeling-Data-in-the-Data-Builder/create-an-external-hierarchy-for-drill-down-dbac7a8.md) + - [Create a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/create-a-hierarchy-with-directory-36c39ee.md) + - [Specify Measures to Analyze](Modeling-Data-in-the-Data-Builder/specify-measures-to-analyze-33f7f29.md) + - [Specify Attributes as Keys, Units, and Other Characteristics](Modeling-Data-in-the-Data-Builder/specify-attributes-as-keys-units-and-other-characteristics-cedc59c.md) - [Specify Semantic Types for Measures and Attributes](Modeling-Data-in-the-Data-Builder/specify-semantic-types-for-measures-and-attributes-f7272c0.md) - - [Exposing a View For Consumption](Modeling-Data-in-the-Data-Builder/exposing-a-view-for-consumption-40ec77e.md) - - [Creating a Dimension](Modeling-Data-in-the-Data-Builder/creating-a-dimension-5aae0e9.md) - - [Specify Attributes](Modeling-Data-in-the-Data-Builder/specify-attributes-cedc59c.md) - [Set Key Columns to Uniquely Identify Records](Modeling-Data-in-the-Data-Builder/set-key-columns-to-uniquely-identify-records-d9ef2c9.md) + - [Create an Association to Define a Semantic Relationship Between Entities](Modeling-Data-in-the-Data-Builder/create-an-association-to-define-a-semantic-relationship-between-entities-66c6998.md) - [Add a Hierarchy to a Dimension](Modeling-Data-in-the-Data-Builder/add-a-hierarchy-to-a-dimension-218b7e6.md) - [Enable Time-Dependency for a Dimension or Text Entity](Modeling-Data-in-the-Data-Builder/enable-time-dependency-for-a-dimension-or-text-entity-11b2ff4.md) - - [Create a Text Entity for Attribute Translation](Modeling-Data-in-the-Data-Builder/create-a-text-entity-for-attribute-translation-b25726d.md) - - [Create a Text Association](Modeling-Data-in-the-Data-Builder/create-a-text-association-414df15.md) - - [Creating an External Hierarchy](Modeling-Data-in-the-Data-Builder/creating-an-external-hierarchy-dbac7a8.md) - - [Creating a Hierarchy with Directory](Modeling-Data-in-the-Data-Builder/creating-a-hierarchy-with-directory-36c39ee.md) + - [Converting Currency and Unit Values](Modeling-Data-in-the-Data-Builder/converting-currency-and-unit-values-1aff2ba.md) + - [Enabling Currency Conversion with TCUR\* Tables and Views](Modeling-Data-in-the-Data-Builder/enabling-currency-conversion-with-tcur-tables-and-views-b462239.md) + - [Exposing a View For Consumption](Modeling-Data-in-the-Data-Builder/exposing-a-view-for-consumption-40ec77e.md) + - [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md) + - [Create a Story Filter \(Deprecated\)](Modeling-Data-in-the-Data-Builder/create-a-story-filter-deprecated-8dfc684.md) - [Creating an Analytic Model](Modeling-Data-in-the-Data-Builder/creating-an-analytic-model-e5fbe9e.md) - [Create an Analytic Model Directly From a View or Table](Modeling-Data-in-the-Data-Builder/create-an-analytic-model-directly-from-a-view-or-table-1c674aa.md) - [Add a Source](Modeling-Data-in-the-Data-Builder/add-a-source-27075ee.md) @@ -183,10 +187,6 @@ - [Example for a Non-Cumulative Measure](Modeling-Data-in-the-Data-Builder/example-for-a-non-cumulative-measure-487d8a3.md) - [Add a Variable](Modeling-Data-in-the-Data-Builder/add-a-variable-cdd8fa0.md) - [Using the Data Preview](Modeling-Data-in-the-Data-Builder/using-the-data-preview-9f1fa73.md) - - [Converting Currency and Unit Values](Modeling-Data-in-the-Data-Builder/converting-currency-and-unit-values-1aff2ba.md) - - [Enabling Currency Conversion with TCUR\* Tables and Views](Modeling-Data-in-the-Data-Builder/enabling-currency-conversion-with-tcur-tables-and-views-b462239.md) - - [Analytical Datasets \(Deprecated\)](Modeling-Data-in-the-Data-Builder/analytical-datasets-deprecated-70dab71.md) - - [Create a Story Filter \(Deprecated\)](Modeling-Data-in-the-Data-Builder/create-a-story-filter-deprecated-8dfc684.md) - [Modeling Data in the Business Builder](Buisiness-Builder/modeling-data-in-the-business-builder-3829d46.md) - [Example for Using the Business Builder](Buisiness-Builder/example-for-using-the-business-builder-925f6a6.md) - [Business Builder Start Page](Buisiness-Builder/business-builder-start-page-90e63fd.md) diff --git a/docs/Acquiring-Preparing-Modeling-Data/persist-view-data-9bd12cf.md b/docs/Acquiring-Preparing-Modeling-Data/persist-view-data-9bd12cf.md index bcdd9af..ee63ba9 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/persist-view-data-9bd12cf.md +++ b/docs/Acquiring-Preparing-Modeling-Data/persist-view-data-9bd12cf.md @@ -45,6 +45,7 @@ Description Shows how you currently access your view. - *Persisted*: The view is persisted can be used immediately. +- *Partially Persisted*: Not all view data has been persisted. If your view contains an input parameter, only records that match the input parameter default value are persisted. - *Virtual*: The view is accessed directly, no intermediate persistency is used. Or the view was persisted and has now been turned into virtual to free up memory space, for example. @@ -90,9 +91,6 @@ You can perform actions on data by clicking *Data Persistence*: > ### Note: > You can set up a view as persisted even if it has been created on top of remote data. - > ### Restriction: - > A view, which contains input parameters can't be persisted. - - *Remove Persisted Data*: Remove the data that have been persisted in the view and switch the access back to virtual. @@ -122,6 +120,21 @@ For more information, see [Schedule a Data Integration Task (Simple Schedule)](h + + +## Persisted Views and Input Parameters + +Data persistence can be run in case a view contains a parameter only if the following prerequisites are met: + +- The view contains one single input parameter, +- The input parameter has a default value maintained. + +If a view contains several input parameters, or if the input parameter has no default value, the view can’t be persisted. + +Once persisted, the view takes the data access value *Partially Persisted* because only records that match the input parameter default value are persisted. + + + ## Persisted Views and Deployement diff --git a/docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md b/docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md index 13a1922..7cb2e2c 100644 --- a/docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md +++ b/docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md @@ -12,6 +12,7 @@ This topic contains the following sections: - [Sort Data](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_sort) - [Filter Data](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_filter) - [Choose Columns to Display](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_columns) +- [View Data as a Different User](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_impersonation) - [Preview Data in Data Flows](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_preview) @@ -101,6 +102,18 @@ You can view data in the table, graphical view, SQL view, E/R model, analytic mo + \(Preview as User\) + + + + + \[views\] Open the *Preview as User* dialog to select another user to preview the data with their permissions and see which records will be visible to them. Select a space user from the list or enter any other user identifier \(see [View Data as a Different User](viewing-object-data-b338e4a.md#loiob338e4aa7e7e494eb68c383720ebfd3a__section_impersonation)\). + + + + + + :gear: @@ -193,6 +206,23 @@ Click *OK* to update the viewer or *Cancel* to erase your changes. To return to + + +## View Data as a Different User + +You can review the effects of any data access controls you apply to a view by checking the records that another user will be allowed to see: + +1. Click \(View as User\) to open the *View as User* dialog. +2. Select a space user from the list or enter any other user identifier and then click *View*. + + The data viewer updates to show only the records visible to the selected user. + + > ### Note: + > *View as User* is only available in the graphic view, SQL view, and analytic model editors, and can only simulate data access controls that are applied in the current space and have a status of *Deployed*. If your view has one or more sources shared from other spaces, then a warning is shown to indicate that you may not see exactly the same records as the user you are impersonating. + + + + ## Preview Data in Data Flows diff --git a/docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md b/docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md index 53d4cc2..60d8213 100644 --- a/docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md +++ b/docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md @@ -55,7 +55,7 @@ Create a space, allocate storage, and set the space priority and statement limit - Enter the technical name of the space. Can contain a maximum of 20 uppercase letters or numbers and must not contain spaces or special characters other than `_` \(underscore\). Unless advised to do so, must not contain prefix \_SYS and should not contain prefixes: DWC\_, SAP\_ \(See [Rules for Technical Names](rules-for-technical-names-982f9a3.md)\). + Enter the technical name of the space. Can contain a maximum of 20 uppercase letters or numbers and must not contain spaces or special characters other than `_` \(underscore\). Unless advised to do so, must not contain prefix \_SYS and should not contain prefixes: DWC\_, SAP\_ \(See [Rules for Technical Names](rules-for-technical-names-982f9a3.md)\).As the technical name will be displayed in the Open SQL Schema and in monitoring tools, including SAP internal tools, we recommend that you do not include sensitive business or personal data in the name. diff --git a/docs/Administering/Creating-a-Database-User-Group/creating-a-database-user-group-1097a47.md b/docs/Administering/Creating-a-Database-User-Group/creating-a-database-user-group-1097a47.md index 9e1286e..986a5e0 100644 --- a/docs/Administering/Creating-a-Database-User-Group/creating-a-database-user-group-1097a47.md +++ b/docs/Administering/Creating-a-Database-User-Group/creating-a-database-user-group-1097a47.md @@ -12,7 +12,7 @@ Users with the DW Administrator role can create database user groups in SAP Data When creating a database user group, an administrator is also created. This administrator can create other users, schemas, and roles using SAP Datasphere stored procedures. The administrator and their users can create data entities \(DDL\) and ingest data \(DML\) directly into their schemas and prepare them for consumption by spaces. -For detailed information about user groups, see [User Groups](https://help.sap.com/viewer/c82f8d6a84c147f8b78bf6416dae7290/2020_04_QRC/en-US/b9174d035f274ce481387700c13b7d2c.html?q=user%20groups) in the *SAP HANA Cloud* documentation. +For detailed information about user groups, see [User Groups](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-database-administration-with-sap-hana-cockpit/user-groups) in the *SAP HANA Cloud* documentation. > ### Note: > Users with the DW Space Administrator role can create database users, which are associated with their space \(see [Integrating Data via Database Users/Open SQL Schemas](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/3de55a78a4614deda589633baea28645.html "Create a database user in your space to read and write directly to the SAP HANA Cloud database on which SAP Datasphere runs. Each database user has an Open SQL schema, which is attached to a space schema and provides a secure method for exchanging data with the space.") :arrow_upper_right:\). diff --git a/docs/Administering/Creating-and-Configuring-Your-Tenant/configure-the-size-of-your-sap-datasphere-tenant-33f8ef4.md b/docs/Administering/Creating-and-Configuring-Your-Tenant/configure-the-size-of-your-sap-datasphere-tenant-33f8ef4.md index 0f080e3..0d4984e 100644 --- a/docs/Administering/Creating-and-Configuring-Your-Tenant/configure-the-size-of-your-sap-datasphere-tenant-33f8ef4.md +++ b/docs/Administering/Creating-and-Configuring-Your-Tenant/configure-the-size-of-your-sap-datasphere-tenant-33f8ef4.md @@ -108,6 +108,10 @@ Set the memory allocated to your tenant. You can increase the amount of memory from 32 GB \(minimum\), by increments of 16 GB. +You can reduce the amount of memory, but the lower limit depends on how much space you have assigned to space management. + +For more information, see [Allocate Storage to a Space](../Creating-Spaces-and-Allocating-Storage/allocate-storage-to-a-space-f414c3d.md). + @@ -211,6 +215,113 @@ The process for allocating capacity units to SAP BW Bridge is not part of the co + + + + +**Elastic Compute Node** + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Property + + + +Description + +
+ +*Performance Class* + + + +> ### Note: +> If you try to modify the settings and discover that elastic compute node functionality has not been enabled on your SAP HANA Cloud Database, follow the steps described in[SAP Note 3432666](https://me.sap.com/notes/3432666). This functionality is not enabled by default on older tenants. + +\[optional\] Select a performance class for your elastic compute node block-hours: + +- Memory +- Compute +- High-Compute + +> ### Note: +> The performance class you select determines the number of vCPUs and the RAM allocated to your tenant. + +You can only use one performance class at a time. To use a different performance class, you must re-configure your *Tenant Configuration* settings. + +
+ +*Block Specifications* + + + +Displays the number of vCPUs and the amount of RAM allocated to your tenant. + +
+ +*Block-Hours* + + + +\[optional\] Set the number of blocks-hours scheduled for elastic compute node consumption. Each block-hour is an additional block of vCPu and RAM for your tenant to use in one hour. The maximum number of block-hours you can consume in one hour is four. + +
+ +*Elastic Compute Node Usage: Allocated Block-Hours* + + + +Displays the number of blocks currently scheduled for elastic compute node consumption. + +
+ +*Elastic Compute Node Usage: Used Block-Hours* + + + +Displays the total number of blocks consumed by elastic compute nodes. The total is independent of which performance-class is selected. + +
+ +*Elastic Compute Node Usage: Exceeded Block-Hours* + + + +Displays the block-hours you have used that exceed the amount allocated by your tenant configuration. + +> ### Note: +> This only appears if you have used more block-hours than allocated. + + +
diff --git a/docs/Administering/Creating-and-Configuring-Your-Tenant/create-an-elastic-compute-node-99ad61e.md b/docs/Administering/Creating-and-Configuring-Your-Tenant/create-an-elastic-compute-node-99ad61e.md index f26bec7..5d0d537 100644 --- a/docs/Administering/Creating-and-Configuring-Your-Tenant/create-an-elastic-compute-node-99ad61e.md +++ b/docs/Administering/Creating-and-Configuring-Your-Tenant/create-an-elastic-compute-node-99ad61e.md @@ -114,16 +114,20 @@ The *DW Administrator* global role, for example, grants these privileges \(see [ - Select the number of compute blocks. You can specify from 1 to 4 blocks. Each compute block provides 64 GB of memory and 4 CPUs. + Select the number of compute blocks. You can choose 4, 8, 12, or 16 blocks. The amount of memory and vCPU depends on the performance class you choose: - Default: 1 + - Memory: 1 vCPU and 16 GB RAM per block + - Compute: 2 vCPUs and 16 GB RAM per block + - High Compute: 4 vCPUs and 16 GB RAM per block + + Default: 4 The number of GB for memory and storage and the number of CPU are calculated based on the compute blocks and you cannot modify them. > ### Note: > You can modify the number of compute blocks later on by selecting the elastic compute node and click *Configure*. - The price you pay for additional resources depends on the duration of an elastic compute node run and the number of compute blocks. If a node that includes 4 compute blocks runs for 5 hours, you pay for 20 block-hours. If a node that includes 8 compute blocks runs for 5 hours, you pay for 40 block-hours. + The price you pay for additional resources depends on the compute blocks and the performance class. If a node that includes 4 compute blocks runs for 30 minutes, you pay for 2 block-hours. diff --git a/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-sap-sql-data-warehousing-on-your-sap-datasphere-tenant-e9a2878.md b/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-sap-sql-data-warehousing-on-your-sap-datasphere-tenant-e9a2878.md index 2d69a5c..d8e051f 100644 --- a/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-sap-sql-data-warehousing-on-your-sap-datasphere-tenant-e9a2878.md +++ b/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-sap-sql-data-warehousing-on-your-sap-datasphere-tenant-e9a2878.md @@ -70,7 +70,13 @@ For information about using this feature, see [Exchanging Data with SAP SQL Data Your SAP Business Technology Platform organization ID. - You can use the Cloud Foundry CLI to find your organization GUID \(see [https://cli.cloudfoundry.org/en-US/v6/org.html](https://cli.cloudfoundry.org/en-US/v6/org.html)\). + You can use the Cloud Foundry CLI to find your organization GUID: + + ``` + cf org --guid + ``` + + See [https://cli.cloudfoundry.org/en-US/v6/org.html](https://cli.cloudfoundry.org/en-US/v6/org.html). @@ -84,7 +90,13 @@ For information about using this feature, see [Exchanging Data with SAP SQL Data The SAP Business Technology Platform space inside the organization. - You can use the Cloud Foundry CLI to find your space GUID \(see [https://cli.cloudfoundry.org/en-US/v6/space.html](https://cli.cloudfoundry.org/en-US/v6/space.html)\). + You can use the Cloud Foundry CLI to find your space GUID: + + ``` + cf space --guid + ``` + + See [https://cli.cloudfoundry.org/en-US/v6/space.html](https://cli.cloudfoundry.org/en-US/v6/space.html). diff --git a/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-the-product-switch-to-access-an-sap-analytics-cloud-tenant-40db567.md b/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-the-product-switch-to-access-an-sap-analytics-cloud-tenant-40db567.md index f8ec39e..5e9d08a 100644 --- a/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-the-product-switch-to-access-an-sap-analytics-cloud-tenant-40db567.md +++ b/docs/Administering/Creating-and-Configuring-Your-Tenant/enable-the-product-switch-to-access-an-sap-analytics-cloud-tenant-40db567.md @@ -8,7 +8,7 @@ You can link your SAP Datasphere tenant to a SAP Analytics Cloud tenant and enab ## Procedure -1. Go to *System* \> *Configuration* \> *Tenant Links*. +1. Go to *System* \> *Administration* \> *Tenant Links*. 2. Enter the URL of your SAP Analytics Cloud tenant. diff --git a/docs/Administering/Creating-and-Configuring-Your-Tenant/run-an-elastic-compute-node-34b3585.md b/docs/Administering/Creating-and-Configuring-Your-Tenant/run-an-elastic-compute-node-34b3585.md index 7161d04..6f046b6 100644 --- a/docs/Administering/Creating-and-Configuring-Your-Tenant/run-an-elastic-compute-node-34b3585.md +++ b/docs/Administering/Creating-and-Configuring-Your-Tenant/run-an-elastic-compute-node-34b3585.md @@ -37,11 +37,17 @@ An elastic compute node can have the following statuses: - *Running* - The node is in its running phase: the data that have been replicated during the starting phase can be consumed in SAP Analytics Cloud for the spaces and objects specified. + > ### Note: + > The *Running* status displayed in red indicates that the elastic compute node contains issues. We recommend that you stop and restart the node, or, alternatively that you stop and delete the node and create a new one. + - *Stopping* - You’ve stopped the elastic compute node manually by clicking the *Stop* button or it has been stopped via a schedule: persisted view replicas, local table replicas and routing are being deleted from the node. - *Stopping Failed* \(displayed in red\) - You’ve stopped the elastic compute node manually by clicking the *Stop* button or it has been stopped via a schedule: issues have occurred. You can stop again the elastic compute node. +> ### Note: +> Up to 4 elastic compute nodes can run at the same time. + **Updates of local tables or persisted views while an elastic compute node is running** - An elastic compute node is in its running phase, which means that its local tables and persisted views have been replicated. Here is the behavior if these objects are updated while the node is running: - If a local table data is updated, it is updated on the main instance and the local table replica is also updated in parallel on the elastic compute node. The runtime may take longer and more memory may be consumed. diff --git a/docs/Administering/Managing-Users-and-Roles/create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md b/docs/Administering/Managing-Users-and-Roles/create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md new file mode 100644 index 0000000..1ebcc01 --- /dev/null +++ b/docs/Administering/Managing-Users-and-Roles/create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md @@ -0,0 +1,1214 @@ + + +# Create Users and Assign Them to Roles via the SCIM 2.0 API + +You can create, read, update, and delete users and add them to roles via the SCIM 2.0 API. + +This topic contains the following sections: + +- [Introduction](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_jzc_m3q_rbc) +- [Log in with a OAuth Client](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_th4_syw_tbc) +- [Obtain a CSRF Token](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_wzz_v2w_rbc) +- [List Users](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_js2_yfw_rbc) +- [Get a Specific User](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_esx_kxt_vbc) +- [Create a User](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_nqs_5lp_tbc) +- [Modify a User](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_zq5_rlp_tbc) +- [Delete a User](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_jhl_xlp_tbc) +- [Optional User Properties](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_vpq_skn_xbc) +- [Get Information About the SCIM API](create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md#loio1ca8c4a9467f43df9ae6d4ed3734f05a__section_n1l_vdy_rbc) + + + + + +## Introduction + +This API allows you to programmatically manage users using a SCIM 2.0 compliant endpoint. + +SAP Datasphere exposes a REST API based on the System for Cross-domain Identity Management \(SCIM 2.0\) specification. This API allows you to keep your SAP Datasphere system synchronized with your preferred identity management solution. + +Using this API, you can perform the following actions: + +- Create, read, update, patch, delete users. + +- Add users to existing scoped or global roles. + + > ### Note: + > You cannot create new roles using this API. + +- List users. + +- Get information on the identity provider, available schemas, and resource types. + + +This API uses SCIM 2.0. For more information, see [SCIM Core Schema](https://tools.ietf.org/html/rfc7643). + +To access the API specification and try out the functionality in SAP Analytics Cloud, see the [SAP Business Accelerator Hub](https://api.sap.com/api/Story_API/resource/Users). + + + + + +## Log in with a OAuth Client + +Beforehand you can log in with a Oauth client, a user with the administrator role must create an OAuth2.0 client in your SAP Datasphere tenant and provide you with the OAuth client ID and secret parameters \(see [Create OAuth2.0 Clients to Authenticate Against SAP Datasphere](../Creating-and-Configuring-Your-Tenant/create-oauth2-0-clients-to-authenticate-against-sap-datasphere-3f92b46.md)\). + +To log in to the OAuth client, send a GET request with the following elements: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Parameter + + + +key + + + +`?grant_type=client_credentials` + +
+ +Authorization + + + +type + + + +`Basic Auth` + +
+ +Authorization + + + +username + + + +** + +
+ +Authorization + + + +password + + + +** + +
+ +Syntax of GET request: + +``` +https:///oauth/token?grant_type=client_credentials +``` + +The response body returns the access token, which you'll then use as the bearer token to obtain the csrf token. + + + + + +## Obtain a CSRF Token + +To obtain a csrf token, send a GET request with the following elements: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +Header + + + +key + + + +`x-csrf-token: fetch` + +
+ +Syntax of GET request: + +``` +/api/v1/csrf +``` + +The CSRF token is returned in the `x-csrf-token` response header. This token can then be included in the POST, PUT, PATCH, or DELETE request in the x-csrf-token:<token> header. + + + + + +## List Users + +To retrieve users, use the GET request with the`/api/v1/scim2/Users` endpoint and the following elements: + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +To list all the users existing in the tenant, enter: + +``` +https:///api/v1/scim2/Users +``` + +You can control the list of users to retrieve by using one or more of the following optional URL parameters: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Parameter + + + +Description + +
+ +`sortBy` + + + +Specifies the user attribute to sort the results by. + +For example, to retieve the list of users sorted by user name: + +``` +sortBy=userName +``` + + + +
+ +`sortOrder` + + + +Specifies the order in which items are returned, either ascending or descending. By default, an ascending sort order is used. + +To retieve the list of users by descending order: + +``` +sortOrder=descending +``` + + + +
+ +`startIndex` + + + +Specifies the index of the first user to fetch. + +For example, so that the tenth user is the first user retireved: + +``` +startIndex=10 +``` + + + +
+ +`count` + + + +Specifies the number of users to return on each page. + +For example, to display a maximum of 8 users on a page: + +``` +count=8 +``` + + + +
+ +filter=<attribute> + + + +Adds a filter to the request. + +For example, to display the users whose user name include the letter K: + +``` +filter=userName co "K" +``` + +See the user schema for available attributes. All operators are supported. + +
+ +Example of a GET request with the various parameters: + +``` +https:///api/v1/scim2/Users/?filter=emails.value co "a"&sortOrder=descending&startIndex=3&count=2&sortBy=emails.value +``` + +> ### Caution: +> GET requests send personal identifiable information as part of the URL, such as the user name in this case. Consider using the POST request with the /api/v1/scim2/Users/.search endpoint instead for enhanced privacy of personal information. Syntax of POST request: +> +> ``` +> https:///api/v1/scim2/Users/.search +> ``` + +> ### Note: +> In the response body, if the users listed are assigned to roles, you can identify the roles as they are prefixed with `PROFILE`. + + + + + +## Get a Specific User + +To retrieve a specific user based on its ID, use the GET request with the /api/v1/scim2/Users/<user ID> endpoint and the following elements: + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +To retrieve a specific user based on its ID, enter the GET request: + +``` +https:///api/v1/scim2/Users/ +``` + +The user ID must be the UUID \(universally unique identifier\), which you can get by sending the GET request: + +``` +https:///api/v1/scim2/Users +``` + +> ### Note: +> In the response body, if the user is assigned to roles, you can identify with their prefix `PROFILE`. + + + + + +## Create a User + +To create a user, use the POST request with the`/api/v1/scim2/Users/` endpoint and the following elements: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +Header + + + +key + + + +`x-csrf-token: csrf token value` + +
+ +Syntax of POST request: https://<Tenant_URL>/api/v1/scim2/Users/ + +> ### Note: +> The following information are required: `userName`, `name`, and `emails` information. Other information that are not provided will be either left empty or set to its default value. +> +> If you are using SAML authentication, `idpUserId` should be set to the property you are using for your SAML mapping. For example, the user's *USER ID*, *EMAIL*, or *CUSTOM SAML MAPPING*. If your SAML mapping is set to *EMAIL*, the email address you add to `idpUserId` must match the email address you use for `email`. +> +> To find this information, log on to SAP Datasphere and go to *\(Security\)* \> *\(Users\)*. + +> ### Note: +> When creating or modifying a user, you can add optional properties to the user. + +The following example shows how to create a new user: + +``` +{ + "schemas": [ + "urn:ietf:params:scim:schemas:core:2.0:User", + "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" + ], + "userName": "LGARCIA", + "name": { + "familyName": "Garcia", + "givenName": "Lisa", + "formatted": "Lisa Garcia" + }, + "displayName": "Lisa Garcia", + "preferredLanguage": "en", + "active": true, + "emails": [ + { + "value": "lisa.garcia@company.com", + "type": "work", + "primary": true + } + ], + "urn:sap:params:scim:schemas:extension:sac:2.0:user-custom-parameters": { + "idpUserId": "lisa.garcia@company.com" + } +} + +``` + +The following example shows how to create a new user and assign it to a role: + +``` +{ + "schemas": [ + "urn:ietf:params:scim:schemas:core:2.0:User", + "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" + ], + "userName": "LGARCIA", + "name": { + "familyName": "Garcia", + "givenName": "Lisa", + "formatted": "Lisa Garcia" + }, + "displayName": "Lisa Garcia", + "preferredLanguage": "en", + "active": true, + "emails": [ + { + "value": "lisa.garcia@company.com", + "type": "work", + "primary": true + } + ], + "roles": [ + { + "value": "PROFILE:t.V:Sales_Modeler", + "display": "Sales_Modeler", + "primary": true + } ], + "urn:sap:params:scim:schemas:extension:sac:2.0:user-custom-parameters": { + "idpUserId": "lisa.garcia@company.com" + } +} + +``` + +The response body returns the ID of the user created, which is the user UUID \(universally unique identifier\). + +> ### Note: +> When creating or modifying a user via the API, you can also assign the user to one or more roles - either global or scoped, provided that the roles already exist in the tenant: +> +> - Before you can add one or more users to a scoped role, one space at least must be assigned to the scoped role. +> +> - When a user is added to a scoped role, the user is given access to all the spaces included in the scoped role. +> +> - All roles are prefixed with `PROFILE`. Custom and scoped roles have IDs in the following format: PROFILE::. + + + + + +## Modify a User + +You can modify a specific user either way: + +- To override all information related to a specific user, use a PUT request. The user properties are updated with the properties you provide and all the properties that you do not provide are either left empty or set to their default value. +- To update only some information related to a specific user, use a PATCH request. The user properties are updated with the changes you provide and all properties that you do not provide remain unchanged. + +You can use either the PUT \(override\) or PATCH \(update\) request with the/api/v1/scim2/Users/<user ID> endpoint and the following elements: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +Header + + + +key + + + +`x-csrf-token: csrf token value` + +
+ +Syntax of PUT or PATCH request: + +``` +https:///api/v1/scim2/Users/ +``` + +> ### Note: +> If you are using SAML authentication, and you are using *USER ID* as your SAML mapping, you cannot change the `userName` using this API. The `userName` you use in the request body must match the user **. +> +> The `active` attribute is not currently used and will not activate or deactivate users. + +> ### Note: +> When creating or modifying a user, you can add optional properties to the user. + +The following example shows how to assign a user to a role: + +``` +{ + "schemas": [ + "urn:sap:params:scim:schemas:extension:sac:2.0:user-custom-parameters", + "urn:ietf:params:scim:schemas:core:2.0:User" + ], + "id": "userID-00001", + "meta": { + "resourceType": "User", + "location": "/api/v1/scim2/Users/userID-00001" + }, + "userName": "LGARCIA", + "name": { + "familyName": "Garcia", + "givenName": "Lisa", + "formatted": "Lisa Garcia" + }, + "displayName": "Lisa Garcia", + "preferredLanguage": "en", + "active": true, + "emails": [ + { + "value": "lisa.garcia@company.com", + "type": "work", + "primary": true + } + ], + "roles": [ + { + "value": "PROFILE:t.V:Sales_Modeler", + "display": "Sales_Modeler", + "primary": true + } ], + "urn:sap:params:scim:schemas:extension:sac:2.0:user-custom-parameters": { + "idpUserId": "lisa.garcia@company.com" + } +} + +``` + +> ### Note: +> When creating or modifying a user via the API, you can also assign the user to one or more roles - either global or scoped, provided that the roles already exist in the tenant: +> +> - Before you can add one or more users to a scoped role, one space at least must be assigned to the scoped role. +> +> - When a user is added to a scoped role, the user is given access to all the spaces included in the scoped role. +> +> - All roles are prefixed with `PROFILE`. Custom and scoped roles have IDs in the following format: PROFILE::. + + + + + +## Delete a User + +To delete a user, use the DELETE request with the/api/v1/scim2/Users/<user ID> endpoint and the following elements: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Request Component + + + +Setting + + + +Value + +
+ +Authorization + + + +type + + + +`Bearer Token` + +
+ +Authorization + + + +token + + + +** + +
+ +Header + + + +key + + + +`x-sap-sac-custom-auth=true` + +
+ +Header + + + +key + + + +`x-csrf-token: csrf token value` + +
+ +To delete a specific user based on its ID, enter the DELETE request: + +``` +https:///api/v1/scim2/Users/ +``` + +The user ID must be the UUID \(universally unique identifier\), which you can get by sending the GET request: + +``` +https:///api/v1/scim2/Users +``` + + + + + +## Optional User Properties + +You can add optional parameters to the user when creating or modifying a user, in addition to the required properties \(`userName`, `name`, and `emails`\). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Parameter + + + +Description + +
+ +`preferredLanguage` + + + +Specifies the language in which to view the SAP Datasphere interface. + +Allowed values: + +- ISO 639-1 two-letter language code. For example, `en`. + +- Concatenation of an ISO 639-1 two-letter language code, a dash, and ISO 3166-1 two-letter country code. For example, `en-us`. + + +Default value: `en` + +Example + +``` +"preferredLanguage": "en", +``` + + + +
+ +The following parameters must be included in an `urn:ietf:params:scim:schemas:extension:sap:user-custom-parameters:1.0` block within the user schema. + +
+ +`dataAccessLanguage` + + + +Specifies the default language in which to display text data in SAP Analytics Cloud. + +Allowed values: + +- ISO 639-1 two-letter language code. For example, `en`. + +- Concatenation of an ISO 639-1 two-letter language code, a dash, and ISO 3166-1 two-letter country code. For example, `en-us`. + + +Default value: `en` + +
+ +`dateFormatting` + + + +Specifies the date display format. + +Allowed values: + +- `MMM d, yyyy` +- `MMM dd, yyyy` +- `yyyy.MM.dd` +- `dd.MM.yyyy` +- `MM.dd.yyyy` +- `yyyy/MM/dd` +- `dd/MM/yyyy` +- `MM/dd/yyyy` + +Default value: `MMM d, yyyy` + +
+ +`numberFormatting` + + + +Specifies the number format. + +Allowed values: `1,234.56`, `1.234,56` or `1 234,56` + +Default value: `1,234.56` + +
+ +`timeFormatting` + + + +Specifies the time display format. + +Allowed values: + +`H:mm:ss`, `h:mm:ss a` or `h:mm:ss A` + +> ### Note: +> - `H:mm:ss` corresponds to 24-Hour Format. For example, 16:05:10. +> - `h:mm:ss a` corresponds to 12-Hour Format. For example, 4:05:10 p.m. +> - `h:mm:ss A` corresponds to 12-Hour Format. For example, 4:05:10 PM. + +Default value: `H:mm:ss` + +
+ +Example: + +``` +"urn:ietf:params:scim:schemas:extension:sap:user-custom-parameters:1.0": { + "dataAccessLanguage": "en", + "dateFormatting": "MMM d, yyyy", + "timeFormatting": "H:mm:ss", + "numberFormatting": "1,234.56", + "cleanUpNotificationsNumberOfDays": 0, + "systemNotificationsEmailOptIn": true, + "marketingEmailOptIn": false + }, +``` + + + + + +## Get Information About the SCIM API + +Using the GET request, you can obtain the following information about the SCIM API: + +- `/scim2/ServiceProviderConfig` - Gets information about the identity provider being used with your SAP Datasphere tenant. + +- `/scim2/Schemas` - Gets information on the schemas used for user management. + +- `/scim2/ResourceTypes` - Gets information on all available resource types. + +- /scim2/ResourceTypes/<Type> - Gets information on a specific resource type. + + diff --git a/docs/Administering/Managing-Users-and-Roles/images/CascadingScopedPrivileges_Roles_cdde787.png b/docs/Administering/Managing-Users-and-Roles/images/CascadingScopedPrivileges_Roles_cdde787.png new file mode 100644 index 0000000..86a6a70 Binary files /dev/null and b/docs/Administering/Managing-Users-and-Roles/images/CascadingScopedPrivileges_Roles_cdde787.png differ diff --git a/docs/Administering/Managing-Users-and-Roles/images/Privileges_GlobalRoles_61551e0.png b/docs/Administering/Managing-Users-and-Roles/images/Privileges_GlobalRoles_61551e0.png new file mode 100644 index 0000000..c8035d0 Binary files /dev/null and b/docs/Administering/Managing-Users-and-Roles/images/Privileges_GlobalRoles_61551e0.png differ diff --git a/docs/Administering/Managing-Users-and-Roles/privileges-and-permissions-d7350c6.md b/docs/Administering/Managing-Users-and-Roles/privileges-and-permissions-d7350c6.md index 1e282a8..35e5ba3 100644 --- a/docs/Administering/Managing-Users-and-Roles/privileges-and-permissions-d7350c6.md +++ b/docs/Administering/Managing-Users-and-Roles/privileges-and-permissions-d7350c6.md @@ -603,7 +603,7 @@ Users with the *Share* permission can share objects to other spaces. Also allows access to the *Data Sharing Cockpit* app with the *Create*, *Read* and *Update* permissions. -See [Acquiring Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/1f15a29a25354ec28392ab10ca4e9350.html "Users with the DW Modeler role can import data directly into the Data Builder from connections and other sources, and use flows to replicate, extract, transform and load data.") :arrow_upper_right:, [Preparing Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/f2e359c899fa4351b5f514d1d86ed9e2.html "Users with the DW Modeler role can use views and intelligent lookups in the Data Builder to combine, clean, and otherwise prepare data.") :arrow_upper_right:, [Modeling Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/5c1e3d4a49554fcd8fcf199d664d1109.html "Users with the DW Modeler role can add semantic information to their entities and expose them directly to clients, tools, and apps, or combine, refine, and enrich them in tightly-focused analytic models for consumption in SAP Analytics Cloud, MS Excel, and other clients, apps, and tools.") :arrow_upper_right: and [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow that users assigned to the space use it as a source for their objects.") :arrow_upper_right:. +See [Acquiring Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/1f15a29a25354ec28392ab10ca4e9350.html "Users with the DW Modeler role can import data directly into the Data Builder from connections and other sources, and use flows to replicate, extract, transform and load data.") :arrow_upper_right:, [Preparing Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/f2e359c899fa4351b5f514d1d86ed9e2.html "Users with the DW Modeler role can use views and intelligent lookups in the Data Builder to combine, clean, and otherwise prepare data.") :arrow_upper_right:, [Modeling Data in the Data Builder](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/5c1e3d4a49554fcd8fcf199d664d1109.html "Users with the DW Modeler role can add semantic information to their entities and expose them directly to clients, tools, and apps, or combine, refine, and enrich them in tightly-focused analytic models for consumption in SAP Analytics Cloud, MS Excel, and other clients, apps, and tools.") :arrow_upper_right: and [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow users assigned to that space to use it as a source for their objects.") :arrow_upper_right:. diff --git a/docs/Administering/Managing-Users-and-Roles/roles-and-privileges-by-app-and-feature-2d8b7d0.md b/docs/Administering/Managing-Users-and-Roles/roles-and-privileges-by-app-and-feature-2d8b7d0.md index eb51b16..4618ab7 100644 --- a/docs/Administering/Managing-Users-and-Roles/roles-and-privileges-by-app-and-feature-2d8b7d0.md +++ b/docs/Administering/Managing-Users-and-Roles/roles-and-privileges-by-app-and-feature-2d8b7d0.md @@ -8,14 +8,67 @@ Review the standard roles and the privileges needed to access apps, tools, and o This topic contains the following sections: +- [Granting Privileges via Global and Scoped Roles](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_vdy_gmg_2bc) - [Apps](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_apps) - [Administration Tools](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_tools) - [Space Management Privileges and Permissions](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_space_management_permissions_SDP_ON) - [External Data Consumption](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_external_consumption) - [The Command Line Interface](roles-and-privileges-by-app-and-feature-2d8b7d0.md#loio2d8b7d04dcae402f911d119437ce0a74__section_cli) + + + + +## Granting Privileges via Global and Scoped Roles + + + + + + + + + + + +
+ +![](images/Privileges_GlobalRoles_61551e0.png) + + + +![](images/CascadingScopedPrivileges_Roles_cdde787.png) + +
+ +A user is granted a set of global privileges for the tenant via a global role. + +The global role can be: + +- A standard global role that is delivered with SAP Datasphere \(such as *DW Administrator*\). + +- A custom role that you create from a template \(a standard global role or another custom role containing global privileges\). + + +To assign a user to a global role, see [Assign Users to a Role](assign-users-to-a-role-57a7880.md). + + + +A user is granted a set of scoped privileges for one or more spaces via a scoped role. + +The scoped role inherits a role template, which can be: + +- A standard scoped role template that is delivered with SAP Datasphere, such as *DW Space Administrator*\). + +- A custom role template that you create from another template \(a standard scoped role or another custom role\). + + +To assign a user to a scoped role, see [Create a Scoped Role to Assign Privileges to Users in Spaces](create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md). + +
+ > ### Note: -> For complete lists of standard roles, privileges, and permissions, see: +> For complete lists of standard roles, privileges and permissions, see: > > - [Standard Roles Delivered with SAP Datasphere](standard-roles-delivered-with-sap-datasphere-a50a51d.md) > - [Privileges and Permissions](privileges-and-permissions-d7350c6.md) @@ -26,7 +79,7 @@ This topic contains the following sections: ## Apps -To access an app, tool, or editor, a user must have the following standard role or a custom role containing the listed privileges: +To access an app, tool, or editor, a user must have a global or scoped role inheriting from a role template which contains the listed privileges: @@ -416,7 +469,7 @@ The following feature needs an additional permission \(which is included in the ## Administration Tools -To access an administration tool, a user must have the following standard role or a custom role containing the listed privileges: +To access an app, tool, or editor, a user must have a global or scoped role inheriting from a role template which contains the listed privileges:
diff --git a/docs/Administering/Monitoring-SAP-Datasphere/monitoring-elastic-compute-nodes-ffa92d9.md b/docs/Administering/Monitoring-SAP-Datasphere/monitoring-elastic-compute-nodes-ffa92d9.md index 2f2afbd..f36be6a 100644 --- a/docs/Administering/Monitoring-SAP-Datasphere/monitoring-elastic-compute-nodes-ffa92d9.md +++ b/docs/Administering/Monitoring-SAP-Datasphere/monitoring-elastic-compute-nodes-ffa92d9.md @@ -163,7 +163,7 @@ To see detailed information about the errors, you can click *View Logs*, which t diff --git a/docs/Administering/Monitoring-SAP-Datasphere/monitoring-sap-datasphere-28910cd.md b/docs/Administering/Monitoring-SAP-Datasphere/monitoring-sap-datasphere-28910cd.md index 8581755..fc6989f 100644 --- a/docs/Administering/Monitoring-SAP-Datasphere/monitoring-sap-datasphere-28910cd.md +++ b/docs/Administering/Monitoring-SAP-Datasphere/monitoring-sap-datasphere-28910cd.md @@ -65,7 +65,7 @@ The following information is available in the *Dashboard* tab: - *Data in Spaces*: All data that is stored in spaces. - - *Audit Log Data*: Data related to audit logs \(see [Audit Logging](https://help.sap.com/viewer/0c3780ad05fd417fa27b98418535debd/cloud/en-US/c78a7c2a3cec4b0897db294d74e00d9b.html "Audit logs are records of read or change actions performed in the database. They allow you to see who did what and when.") :arrow_upper_right:\). + - *Audit Log Data*: Data related to audit logs \(see [Audit Logging](https://help.sap.com/viewer/0c3780ad05fd417fa27b98418535debd/cloud/en-US/c78a7c2a3cec4b0897db294d74e00d9b.html "Audit logs are records of read or change actions performed in the database. They allow you to see who performed which action at which point in time.") :arrow_upper_right:\). > ### Note: > Audit logs can grow quickly and consume a great deal of disk storage \(see [Delete Audit Logs](delete-audit-logs-589fa42.md)\). diff --git a/docs/Administering/Preparing-Connectivity/configure-cloud-connector-f289920.md b/docs/Administering/Preparing-Connectivity/configure-cloud-connector-f289920.md index dc175e7..a776915 100644 --- a/docs/Administering/Preparing-Connectivity/configure-cloud-connector-f289920.md +++ b/docs/Administering/Preparing-Connectivity/configure-cloud-connector-f289920.md @@ -299,7 +299,7 @@ For more information about the supported use cases depending on the connection t diff --git a/docs/Administering/index.md b/docs/Administering/index.md index a96af15..022e7b6 100644 --- a/docs/Administering/index.md +++ b/docs/Administering/index.md @@ -40,6 +40,7 @@ - [Create a Scoped Role to Assign Privileges to Users in Spaces](Managing-Users-and-Roles/create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md) - [Assign Users to a Role](Managing-Users-and-Roles/assign-users-to-a-role-57a7880.md) - [Assign Users to a Role Using SAML Attributes](Managing-Users-and-Roles/assign-users-to-a-role-using-saml-attributes-3315711.md) + - [Create Users and Assign Them to Roles via the SCIM 2.0 API](Managing-Users-and-Roles/create-users-and-assign-them-to-roles-via-the-scim-2-0-api-1ca8c4a.md) - [View Authorizations \(Users, Roles and Spaces\)](Managing-Users-and-Roles/view-authorizations-users-roles-and-spaces-c6538ea.md) - [Privileges and Permissions](Managing-Users-and-Roles/privileges-and-permissions-d7350c6.md) - [Roles and Privileges by App and Feature](Managing-Users-and-Roles/roles-and-privileges-by-app-and-feature-2d8b7d0.md) @@ -75,6 +76,7 @@ - [Prepare Connectivity for Generic SFTP](Preparing-Connectivity/prepare-connectivity-for-generic-sftp-5454a8c.md) - [Prepare Connectivity to Google BigQuery](Preparing-Connectivity/prepare-connectivity-to-google-bigquery-529cef1.md) - [Prepare Connectivity to Microsoft Azure SQL Database](Preparing-Connectivity/prepare-connectivity-to-microsoft-azure-sql-database-782bd8c.md) + - [Prepare Connectivity to Microsoft Azure Data Lake Store Gen2](Preparing-Connectivity/prepare-connectivity-to-microsoft-azure-data-lake-store-gen2-6b3fd2c.md) - [Prepare Connectivity to Microsoft SQL Server](Preparing-Connectivity/prepare-connectivity-to-microsoft-sql-server-ea69328.md) - [Prepare Connectivity to SAP Open Connectors](Preparing-Connectivity/prepare-connectivity-to-sap-open-connectors-fb1aa11.md) - [Prepare Connectivity to Oracle](Preparing-Connectivity/prepare-connectivity-to-oracle-9fca7c4.md) diff --git a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-hierarchy-data-access-control-0afeeed.md b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-hierarchy-data-access-control-0afeeed.md index 8f577c6..e04e9ee 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-hierarchy-data-access-control-0afeeed.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-hierarchy-data-access-control-0afeeed.md @@ -349,6 +349,9 @@ For example: For information about attaching a data access control to a view, see [Apply a Data Access Control](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/8f79fc80d6134a89a03837a205d340cd.html "You can apply one or more data access controls to a view to control the data that users will see based on the specified criteria.") :arrow_upper_right:. + > ### Note: + > You can use the *View as User* tool in the *Data Viewer* panel to review the effects of the data access controls you apply by checking the records that another user will be allowed to see \(see [Viewing Object Data](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/b338e4aa7e7e494eb68c383720ebfd3a.html "You can, at any time, view the data contained in (or output by) your tables, views, and other Data Builder objects. When working in the graphical view editor, you can view the data output by each node in the diagram.") :arrow_upper_right:\). + 5. The tools in the editor toolbar help you work with your object throughout its lifecycle: diff --git a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-single-values-data-access-control-5246328.md b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-single-values-data-access-control-5246328.md index 0d12663..c407126 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-single-values-data-access-control-5246328.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-a-single-values-data-access-control-5246328.md @@ -158,6 +158,9 @@ Before creating your data access control, you must have prepared a permissions e For information about attaching a data access control to a view, see [Apply a Data Access Control](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/8f79fc80d6134a89a03837a205d340cd.html "You can apply one or more data access controls to a view to control the data that users will see based on the specified criteria.") :arrow_upper_right:. + > ### Note: + > You can use the *View as User* tool in the *Data Viewer* panel to review the effects of the data access controls you apply by checking the records that another user will be allowed to see \(see [Viewing Object Data](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/b338e4aa7e7e494eb68c383720ebfd3a.html "You can, at any time, view the data contained in (or output by) your tables, views, and other Data Builder objects. When working in the graphical view editor, you can view the data output by each node in the diagram.") :arrow_upper_right:\). + 5. The tools in the editor toolbar help you work with your object throughout its lifecycle: diff --git a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-an-operator-and-values-data-access-control-501594b.md b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-an-operator-and-values-data-access-control-501594b.md index f741567..5b41f51 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-an-operator-and-values-data-access-control-501594b.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Access-Control/create-an-operator-and-values-data-access-control-501594b.md @@ -446,6 +446,9 @@ Based on these three records: For information about attaching a data access control to a view, see [Apply a Data Access Control](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/8f79fc80d6134a89a03837a205d340cd.html "You can apply one or more data access controls to a view to control the data that users will see based on the specified criteria.") :arrow_upper_right:. + > ### Note: + > You can use the *View as User* tool in the *Data Viewer* panel to review the effects of the data access controls you apply by checking the records that another user will be allowed to see \(see [Viewing Object Data](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/b338e4aa7e7e494eb68c383720ebfd3a.html "You can, at any time, view the data contained in (or output by) your tables, views, and other Data Builder objects. When working in the graphical view editor, you can view the data output by each node in the diagram.") :arrow_upper_right:\). + 6. The tools in the editor toolbar help you work with your object throughout its lifecycle: diff --git a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/exploring-views-with-view-analyzer-8921e5a.md b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/exploring-views-with-view-analyzer-8921e5a.md index a398fc9..d6a1bf2 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/exploring-views-with-view-analyzer-8921e5a.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/exploring-views-with-view-analyzer-8921e5a.md @@ -11,7 +11,8 @@ The *View Analyzer* provides you with statistics and useful information on each > ### Tip: > While working with complex views, see [Persisted Views and Memory Consumption](persisted-views-and-memory-consumption-e3d0495.md). - +> ### Note: +> The *View Analyzer* can't analyze a view that has input parameters. To use the *View Analyzer*, diff --git a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/persisting-and-monitoring-views-9af04c9.md b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/persisting-and-monitoring-views-9af04c9.md index 3309bd8..6c112a6 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/persisting-and-monitoring-views-9af04c9.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/persisting-and-monitoring-views-9af04c9.md @@ -140,13 +140,15 @@ Information > ### Note: > You can set up a view as persisted even if it has been created on top of remote data. -> ### Restriction: -> A view, which contains input parameters can't be persisted. - *Remove Persisted Data*: Remove the data that have been persisted in the view and switch the access back to virtual. *Start View Analyzer*: Analyzes each view definition, the consumed views and the data sources used by local and remote tables that compose your data model. You can then use the provided information and warnings to decide on some improvements for your data model. You can also generate an SQL Analyzer Plan File that you can download \(if you have the required authorizations\) for detailed analysis. For more infromation, see [Exploring Views with View Analyzer](exploring-views-with-view-analyzer-8921e5a.md). +> ### Note: +> The *View Analyzer* can't analyze a view that has input parameters. + + + @@ -246,6 +248,7 @@ Name of the persisted view.Technical or Business Name is displayed, depending on Shows how you currently access your view. - *Persisted*: The view is persisted can be used immediately. +- *Partially Persisted*: Not all view data has been persisted. If your view contains an input parameter, only records that match the input parameter default value are persisted. - *Virtual*: The view is accessed directly, no intermediate persistency is used. Or the view was persisted and has now been turned into virtual to free up memory space, for example. @@ -366,6 +369,21 @@ You can personalize the columns you want to display clicking on :gear: + + +## Persisted Views and Input Parameters + +Data persistence can be run in case a view contains a parameter only if the following prerequisites are met: + +- The view contains one single input parameter, +- The input parameter has a default value maintained. + +If a view contains several input parameters, or if the input parameter has no default value, the view can’t be persisted. + +Once persisted, the view takes the data access value *Partially Persisted* because only records that match the input parameter default value are persisted. + + + ## Persisted Views and Deployment diff --git a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/understanding-the-data-persistence-metrics-d65994c.md b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/understanding-the-data-persistence-metrics-d65994c.md index 78eb4b2..d645bae 100644 --- a/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/understanding-the-data-persistence-metrics-d65994c.md +++ b/docs/Integrating-data-and-managing-spaces/Data-Integration-Monitor/understanding-the-data-persistence-metrics-d65994c.md @@ -188,6 +188,18 @@ For more information, see [Persisted Views and Data Access Control](persisted-vi Displays the technical name of the elastic compute node used to persist the view. If no elastic compute node is used the value is empty. + + + + +
-Shows the amount of memory allocated to the elastic compute node, broken down between: +Shows the amount of memory allocated to the elastic compute node, if in a running state, broken down between: - *Unused Memory* - Shows the amount of memory available for the elastic compute node. @@ -172,6 +172,9 @@ Shows the amount of memory allocated to the elastic compute node, broken down be - *Memory Used for Processing* - Shows the amount of memory used by the processes that are currently running for the elastic compute node. For example: consumption of the queries running on the elastic compute node. +> ### Note: +> If the elastic compute node is not in a running state, no data is displayed. + - For the Kafka broker: TCP - - For the Schema Registry: HTTP + - For the Schema Registry: HTTPS diff --git a/docs/Administering/Preparing-Connectivity/finding-sap-datasphere-ip-addresses-0934f7e.md b/docs/Administering/Preparing-Connectivity/finding-sap-datasphere-ip-addresses-0934f7e.md index 65e4dc4..bd78953 100644 --- a/docs/Administering/Preparing-Connectivity/finding-sap-datasphere-ip-addresses-0934f7e.md +++ b/docs/Administering/Preparing-Connectivity/finding-sap-datasphere-ip-addresses-0934f7e.md @@ -4,9 +4,9 @@ # Finding SAP Datasphere IP addresses -Find externally facing IP addresses that for particular remote applications must be added to allowlists before you can to use connections to these remote applications. +Find externally facing IP addresses and IDs that must be added to allowlists in particular remote applications before you can use connections to these remote applications. -Particular remote applications or sources that you might want to access with SAP Datasphere restrict access to their instances and require external SAP Datasphere IP address information to be added to an allowlist in the remote application before first trying to access the application . +Particular remote applications or sources that you might want to access with SAP Datasphere restrict access to their instances and require external SAP Datasphere IP address information to be added to an allowlist in the remote application before first trying to access the application. @@ -32,3 +32,23 @@ Administrators can find the NAT IPs from the side navigation area by clicking + +## Microsoft Azure Deployments Only: Virtual Network Subnet ID + +If you're using SAP Datasphere on Microsoft Azure and want to connect to an Azure storage service in a firewall-protected Microsoft Azure storage account within the same Azure region, an administrator must allow the SAP Datasphere's Virtual Network Subnet ID in the Microsoft Azure storage account. This is required for connections to Azure storage services such as Microsoft Azure Data Lake Store Gen2. + +For more information, see SAP Note [3405081](https://me.sap.com/notes/3405081). + +Administrators can find the ID from the side navigation area by clicking \(*System*\)** \> ** \(*About*\)** \> ***More*** \> ** *Virtual Network Subnet ID \(Microsoft Azure\)*. + + + + + +## Related Links + +SAP Note [3456052](https://me.sap.com/notes/3456052) \(FAQ: About IP Addresses used in SAP Datasphere\) + diff --git a/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-confluent-3515f11.md b/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-confluent-3515f11.md index 664d2c6..221c731 100644 --- a/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-confluent-3515f11.md +++ b/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-confluent-3515f11.md @@ -17,6 +17,8 @@ Before you can use the connection for replication flows, the following is requir > ### Note: > Separate Cloud Connector instances might be used for the two endpoints. The Schema Registry might be used in one Cloud Connector location is while connecting to the Kafka brokers happens in another location. + For more information, see [Configure Cloud Connector](configure-cloud-connector-f289920.md). + **Related Information** diff --git a/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-microsoft-azure-data-lake-store-gen2-6b3fd2c.md b/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-microsoft-azure-data-lake-store-gen2-6b3fd2c.md new file mode 100644 index 0000000..8f0c144 --- /dev/null +++ b/docs/Administering/Preparing-Connectivity/prepare-connectivity-to-microsoft-azure-data-lake-store-gen2-6b3fd2c.md @@ -0,0 +1,24 @@ + + +# Prepare Connectivity to Microsoft Azure Data Lake Store Gen2 + +To be able to successfully validate and use a connection to Microsoft Azure Data Lake Store Gen2 certain preparations have to be made. + + + + + +## Data Flows and Replication Flows + +Before you can use the connection for data flows and replication flows, the following is required: + +- If you're using SAP Datasphere on Microsoft Azure and want to connect to Microsoft Azure Data Lake Store Gen2 in a firewall-protected Microsoft Azure storage account within the same Azure region: An Azure administrator must grant SAP Datasphere access to the Microsoft Azure storage account. + + For more information, see [Finding SAP Datasphere IP addresses](finding-sap-datasphere-ip-addresses-0934f7e.md) + + +**Related Information** + + +[Microsoft Azure Data Lake Store Gen2 Connections](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/cd06b3c5ab5147c0905e3fa8abd13eb1.html "Use the connection to connect to and access objects in Microsoft Azure Data Lake Gen2 (ADL Gen2).") :arrow_upper_right: + diff --git a/docs/Administering/Preparing-Connectivity/preparing-connectivity-for-connections-bffbd58.md b/docs/Administering/Preparing-Connectivity/preparing-connectivity-for-connections-bffbd58.md index 450f416..5dd1f16 100644 --- a/docs/Administering/Preparing-Connectivity/preparing-connectivity-for-connections-bffbd58.md +++ b/docs/Administering/Preparing-Connectivity/preparing-connectivity-for-connections-bffbd58.md @@ -712,7 +712,7 @@ no -no +yes \(Microsoft Azure deployments only: Virtual Network Subnet ID\) @@ -722,7 +722,7 @@ no -n/a +[Prepare Connectivity to Microsoft Azure Data Lake Store Gen2](prepare-connectivity-to-microsoft-azure-data-lake-store-gen2-6b3fd2c.md)
+ +*Input Parameter* + + + +if your view contains an input parameter, it displays the name of the parameter used to persist the view data. +
@@ -298,6 +310,18 @@ For more information, see [Persisted Views and Data Access Control](persisted-vi Displays the technical name of the elastic compute node used to persist the view. If no elastic compute node is used the value is empty. + + + + + +*Input Parameter* + + + + +if your view contains an input parameter, it displays the name of the parameter used to persist the view data. + diff --git a/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Connections/microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md b/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Connections/microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md index a6b30e0..5ffe1f6 100644 --- a/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Connections/microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md +++ b/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Connections/microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md @@ -13,6 +13,8 @@ This topic contains the following sections: - [Supported Features](microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md#loiocd06b3c5ab5147c0905e3fa8abd13eb1__ADL2_usage) - [Configuring Connection Properties](microsoft-azure-data-lake-store-gen2-connections-cd06b3c.md#loiocd06b3c5ab5147c0905e3fa8abd13eb1__connection_properties) +For information about the required prerequisites, see [Prepare Connectivity to Microsoft Azure Data Lake Store Gen2](https://help.sap.com/viewer/9f804b8efa8043539289f42f372c4862/cloud/en-US/6b3fd2c371284637bac465edb9cc9e50.html "To be able to successfully validate and use a connection to Microsoft Azure Data Lake Store Gen2 certain preparations have to be made.") :arrow_upper_right:. + diff --git a/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Database-Users/Open-SQL-Schema/allow-the-space-to-access-the-open-sql-schema-7eaa370.md b/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Database-Users/Open-SQL-Schema/allow-the-space-to-access-the-open-sql-schema-7eaa370.md index 5d0e8a3..4044b02 100644 --- a/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Database-Users/Open-SQL-Schema/allow-the-space-to-access-the-open-sql-schema-7eaa370.md +++ b/docs/Integrating-data-and-managing-spaces/Integrating-Data-Via-Database-Users/Open-SQL-Schema/allow-the-space-to-access-the-open-sql-schema-7eaa370.md @@ -96,7 +96,7 @@ You can grant write privileges by running an SAP Datasphere specific stored proc - - 'INSERT" + - 'INSERT' - 'UPDATE' @@ -205,7 +205,7 @@ You can grant write privileges by running an SAP Datasphere specific stored proc ``` CALL "DWC_GLOBAL"."GRANT_PRIVILEGE_TO_SPACE" ( OPERATION => 'GRANT', - PRIVILEGE => 'UPDATE, + PRIVILEGE => 'UPDATE', SCHEMA_NAME => 'SALE#ETL', OBJECT_NAME => 'MY_TABLE', SPACE_ID => 'SALES'); @@ -218,7 +218,7 @@ You can grant write privileges by running an SAP Datasphere specific stored proc ``` CALL "DWC_GLOBAL"."GRANT_PRIVILEGE_TO_SPACE" ( OPERATION => 'GRANT', - PRIVILEGE => 'EXECUTE, + PRIVILEGE => 'EXECUTE', SCHEMA_NAME => 'SALE#ETL', OBJECT_NAME => '', SPACE_ID => 'SALES'); diff --git a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/exporting-content-for-sharing-with-other-tenants-44e775c.md b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/exporting-content-for-sharing-with-other-tenants-44e775c.md index d214593..4310578 100644 --- a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/exporting-content-for-sharing-with-other-tenants-44e775c.md +++ b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/exporting-content-for-sharing-with-other-tenants-44e775c.md @@ -252,7 +252,7 @@ The definition of an authorization scenario contains the definition of its data If an object depends on other objects, then they will also be selected. For example, when you select a view, all its sources and any used data access controls will be selected. > ### Note: - > If an object selected for export depends on one or more objects that have been shared from other spaces \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow that users assigned to the space use it as a source for their objects.") :arrow_upper_right:\), then you must be a member of each of those spaces in order to include all the necessary objects in your package. + > If an object selected for export depends on one or more objects that have been shared from other spaces \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow users assigned to that space to use it as a source for their objects.") :arrow_upper_right:\), then you must be a member of each of those spaces in order to include all the necessary objects in your package. > > If you are not a member of one or more sharing spaces, then you can still export your package \(no error will be displayed\), but it will fail to import correctly unless all the missing objects are already present in the target tenant. > diff --git a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/importing-content-from-another-tenant-b607a12.md b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/importing-content-from-another-tenant-b607a12.md index 6f416a4..9ddb34b 100644 --- a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/importing-content-from-another-tenant-b607a12.md +++ b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/importing-content-from-another-tenant-b607a12.md @@ -145,7 +145,7 @@ Users with the *DW Administrator* global role \(or users with both a scoped *DW - **Overwrite objects and data** - All imported objects in the space will be deployed. > ### Note: - > This option does not support packages that contain objects from one or more spaces where objects are shared from one space to another \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow that users assigned to the space use it as a source for their objects.") :arrow_upper_right:. In this case, you should manually deploy the objects from the source space and then deploy the objects from the target space. + > This option does not support packages that contain objects from one or more spaces where objects are shared from one space to another \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow users assigned to that space to use it as a source for their objects.") :arrow_upper_right:. In this case, you should manually deploy the objects from the source space and then deploy the objects from the target space. diff --git a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/transporting-your-content-through-sap-cloud-transport-management-0538398.md b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/transporting-your-content-through-sap-cloud-transport-management-0538398.md index 11846cf..86c8b55 100644 --- a/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/transporting-your-content-through-sap-cloud-transport-management-0538398.md +++ b/docs/Integrating-data-and-managing-spaces/Transporting-Content-Between-Tenants/transporting-your-content-through-sap-cloud-transport-management-0538398.md @@ -27,12 +27,11 @@ Finally, you can return to SAP Cloud Transport Management to ensure the transfer 2. Configure the landscape for your transports, by creating transport destinations, routes, and nodes. 1. Create a destination in the SAP Business Technology Platform cockpit of the DEV subaccount of your cloud application, pointing to Cloud Transport Management. See [Create Transport Destinations](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-destinations). - - To integrate with SAP Datasphere, the destination must have an endpoint URL in this format: `https:///api/v1/content/deploy/` - - Add the additional property such as *PLATFORM\_TYPES* and value as *ACN\_NEO* only for Neo destinations. + To integrate with SAP Datasphere, the destination must have an endpoint URL in this format: `https:///api/v1/content/deploy/` ![](images/Destination_Config_da27266.png) - 2. Create nodes and routes. See [Create Transport Nodes](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-nodes) and [Create Transport Routes](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-routes). + 2. Create nodes and routes. See [Create Transport Nodes](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-nodes) and [Create Transport Routes](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-routes). Make sure to select the checkbox *Allow Upload to Node* when creating a source node. When defining a target node, the content type must be *Application Content* to be able to select the destination name you've created in the previous step. > ### Tip: > Go to *System*→*Administration*→*App Integration* to find the token URL and add the extension `?grant_type=client_credentials`. @@ -56,7 +55,8 @@ Finally, you can return to SAP Cloud Transport Management to ensure the transfer 1. In the side navigation area, click *Transport* \> *Export* and select the package you want to export. 2. Click *Upload to SAP Cloud Transport Management Node* from the menu bar: in the dialog box, you can see the list of selected packages. 3. In the *Export Node* dropdown, choose the source node of SAP Cloud Transport Management to which you want to export your packages. For more information on source and target nodes, see [Create Transport Nodes](https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/create-transport-nodes). -4. Click *Upload*. +4. Select the checkbox to agree to use your user rights \(based on IDP user ID\) to deploy the package in the target tenant. +5. Click *Upload*. @@ -67,3 +67,14 @@ Finally, you can return to SAP Cloud Transport Management to ensure the transfer Once the import is completed, you see the content of the package available in its corresponding destination in your SAP Datasphere account. +> ### Note: +> The user who uploaded the package must be a member of the target tenant. + + + +## Troubleshooting + +In case of import failure, you can access the logs to investigate the error by adding this endpoint to the target tenant URL: + +`/contentmanager/v4/jobs/{ProcessID}?brief=false` + diff --git a/docs/Integrating-data-and-managing-spaces/enable-audit-logging-2665539.md b/docs/Integrating-data-and-managing-spaces/enable-audit-logging-2665539.md index 141e979..a8e70b5 100644 --- a/docs/Integrating-data-and-managing-spaces/enable-audit-logging-2665539.md +++ b/docs/Integrating-data-and-managing-spaces/enable-audit-logging-2665539.md @@ -2,7 +2,7 @@ # Enable Audit Logging -You can enable audit logs for your space so that read and change actions \(policies\) are recorded. Administrators can then analyze who did what and when in the database. +You can enable audit logs for your space so that read and change actions \(policies\) are recorded. Administrators can then analyze who performed which action at which point in time. diff --git a/docs/Integrating-data-and-managing-spaces/export-audit-logs-0c5dc64.md b/docs/Integrating-data-and-managing-spaces/export-audit-logs-0c5dc64.md index 538040b..b6bbf40 100644 --- a/docs/Integrating-data-and-managing-spaces/export-audit-logs-0c5dc64.md +++ b/docs/Integrating-data-and-managing-spaces/export-audit-logs-0c5dc64.md @@ -19,7 +19,7 @@ To export audit log entries using the SAP HANA Database Explorer, follow these s **Related Information** -[Enable Audit Logging](enable-audit-logging-2665539.md "You can enable audit logs for your space so that read and change actions (policies) are recorded. Administrators can then analyze who did what and when in the database.") +[Enable Audit Logging](enable-audit-logging-2665539.md "You can enable audit logs for your space so that read and change actions (policies) are recorded. Administrators can then analyze who performed which action at which point in time.") [Delete Your Space](delete-your-space-3eb19b9.md "Delete a space if you are sure that you no longer need any of its content or data.") diff --git a/docs/Integrating-data-and-managing-spaces/importing-sap-and-partner-business-content-from-the-content-network-400078d.md b/docs/Integrating-data-and-managing-spaces/importing-sap-and-partner-business-content-from-the-content-network-400078d.md index 5ab1b7f..58077ce 100644 --- a/docs/Integrating-data-and-managing-spaces/importing-sap-and-partner-business-content-from-the-content-network-400078d.md +++ b/docs/Integrating-data-and-managing-spaces/importing-sap-and-partner-business-content-from-the-content-network-400078d.md @@ -114,7 +114,7 @@ We also provide content for download at our [Community Content](https://github.c - **Overwrite objects and data** - All imported objects in the space will be deployed. > ### Note: - > This option does not support packages that contain objects from one or more spaces where objects are shared from one space to another \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow that users assigned to the space use it as a source for their objects.") :arrow_upper_right:. In this case, you should manually deploy the objects from the source space and then deploy the objects from the target space. + > This option does not support packages that contain objects from one or more spaces where objects are shared from one space to another \(see [Sharing Tables and Views To Other Spaces](https://help.sap.com/viewer/24f836070a704022a40c15442163e5cf/DEV_CURRENT/en-US/64b318f8afd74bb78467cf56eb44294f.html "Share a Data Builder table or view to another space to allow users assigned to that space to use it as a source for their objects.") :arrow_upper_right:. In this case, you should manually deploy the objects from the source space and then deploy the objects from the target space.