Update from SAP DITA CMS (squashed):

commit 2a4f411ea35700be85c7c09f34c066de9df2b002 Merge: ef19678 8d082fe Author: REDACTED Date: Thu Mar 23 14:32:47 2023 +0100 Merge pull request #1 from UACP/corrections Corrections for readme and dep5 commit ef19678dea837ef22f8a9f288ef1a49420213df7 Author: REDACTED Date: Mon Mar 20 23:59:24 2023 +0100 Update from SAP DITA CMS ( 2023-03-20_23:59:23 ) Project: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (bjs1675733153534.project) * Project map: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (rlq1676938506089.ditamap) * Output: loiob8faae83b519439fb4ea9d0eb1a5f26e * Buildable map: loio4e1c1e1d5d1947f5875e93e7597c4f4c (gem1676938505857.ditamap) * Language: en-US commit c67b67ded4bb87a687fb65c623a143cf047fd05c Author: REDACTED Date: Mon Mar 20 12:39:39 2023 +0100 Update from SAP DITA CMS ( 2023-03-20_12:39:38 ) Project: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (bjs1675733153534.project) ################################################## [Remaining squash message was removed before commit...]
SAP-docs · Mar 23, 2023 · 4da28fc · 4da28fc
1 parent 8bc108a
commit 4da28fc
Show file tree

Hide file tree

Showing 610 changed files with 72,081 additions and 9 deletions.
diff --git a/.reuse/dep5 b/.reuse/dep5
@@ -1,8 +1,8 @@
 Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: YOUR-REPOSITORY
-Upstream-Contact: NAME SURNAME (EMAIL)
-Source: https://github.com/sap-docs/YOUR-REPOSITORY
+Upstream-Name: sap-datasphere
+Upstream-Contact: Venet Cindy ([email protected])
+Source: https://github.com/sap-docs/sap-datasphere
 
 Files: *
-Copyright:  2023 SAP SE or an SAP affiliate company and YOUR-REPOSITORY contributors
+Copyright:  2023 SAP SE or an SAP affiliate company and sap-datasphere contributors
 License: CC-BY-4.0
diff --git a/README.md b/README.md
@@ -1,8 +1,13 @@
 [![REUSE status]()]()
 
-# Contributions to YOUR-DOCUMENTATION
+# Contributions to the SAP Datasphere Documentation
 
-Found a mistake in our documentation? Always wanted to add a step in one of our procedures that could save many others much time? Then you're at the right place! All contributions made to the Markdown files in the [docs](docs) directory are reviewed, and if deemed valuable be added to our [official documentation on SAP Help Portal](YOUR-LINK). The easiest way is to start there, and choose _Edit_ to find the right Markdown file to contribute to.
+Found a mistake in our documentation? Always wanted to add a step in one of our procedures that could save many others much time? Then you're at the right place! All contributions made to the Markdown files in the [docs](docs) directory are reviewed, and if deemed valuable be added to our official documentation on SAP Help Portal. The easiest way is to start there, and choose _Edit_ to find the right Markdown file to contribute to.
+
+You can currently make contributions to the following guides in this repository:
+- [Integrating Data and Managing Spaces](https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0?locale=en-US&state=PRODUCTION&version=cloud)
+- [Acquiring, Preparing, and Modeling Data](https://help.sap.com/docs/SAP_DATASPHERE/c8a54ee704e94e15926551293243fd1d?locale=en-US&state=PRODUCTION&version=cloud)
+- [Administering SAP Data Warehouse Cloud](https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862?locale=en-US&state=PRODUCTION&version=cloud)
 
 ## Requirements
 
@@ -11,10 +16,13 @@ For contributions, it's required that you have a GitHub account. For more inform
 
 ## Contributing
 
-We recommend using the YOUR-DOCUMENTATION documentation on SAP Help Portal as a starting point for contributions:
+We recommend using the SAP Datasphere documentation on SAP Help Portal as a starting point for contributions:
 
-1. Open the [YOUR-DOCUMENTATION Documentation](YOUR-LINK).
-1. You can either:
+1. Open the SAP Datasphere Documentation:
+   - [Integrating Data and Managing Spaces](https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0?locale=en-US&state=PRODUCTION&version=cloud)
+   - [Acquiring, Preparing, and Modeling Data](https://help.sap.com/docs/SAP_DATASPHERE/c8a54ee704e94e15926551293243fd1d?locale=en-US&state=PRODUCTION&version=cloud)
+   - [Administering SAP Data Warehouse Cloud](https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862?locale=en-US&state=PRODUCTION&version=cloud)
+3. You can either:
     * Choose *Edit* to suggest a change for the current page you see in the Help Portal viewer, or
     * Choose *Feedback* to open a GitHub issue in this repository.
 

diff --git a/...the-Data-Builder/accelerate-table-data-access-with-in-memory-storage-407d1df.md b/...the-Data-Builder/accelerate-table-data-access-with-in-memory-storage-407d1df.md
@@ -0,0 +1,55 @@
+<!-- loio407d1dff76a842699ea08c17eb8748dd -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Accelerate Table Data Access with In-Memory Storage
+
+By default, table data is stored on disk. You can improve performance by enabling in-memory storage.
+
+
+
+## Procedure
+
+1.  Open your table in the table editor and scroll to the *Table Services* section.
+
+2.  Enable the following option:
+
+
+    <table>
+    <tr>
+    <th valign="top">
+
+    Property
+
+
+
+    </th>
+    <th valign="top">
+
+    Description
+
+
+
+    </th>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    In-Memory Storage
+
+
+
+    </td>
+    <td valign="top">
+
+    Enable this option to store the table data directly in memory \(hot store\). By default, table data is stored on disk \(warm store\).
+
+
+
+    </td>
+    </tr>
+    </table>
+
+3.  Click <span class="SAP-icons"></span> \(Deploy\) to deploy the table and move its data into in-memory storage.
+
+
diff --git a/...in-the-Data-Builder/acquiring-and-preparing-data-in-the-data-builder-1f15a29.md b/...in-the-Data-Builder/acquiring-and-preparing-data-in-the-data-builder-1f15a29.md
diff --git a/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-1eee180.md b/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-1eee180.md
@@ -0,0 +1,52 @@
+<!-- loio1eee180ff2cd450496967afdaab903e3 -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Add a Source
+
+Drag a table or view from the *Source Browser* panel and drop it on the diagram.
+
+
+
+## Procedure
+
+1.  If the *Source Browser* panel is not visible on the left of the screen, click *Source Browser* in the toolbar to show it.
+
+2.  Browse or search for the object you want to add on either of the tabs.
+
+    -   The *Repository* tab lists all the tables, views, and intelligent lookups that are available in the space \(including objects shared to the space\). You can search and expand the categories \(see [Add Objects from the Repository](add-objects-from-the-repository-13fcecd.md)\).
+
+    -   The *Sources* tab lists all the connections and other data sources that have been integrated to the space from which you can import tables. You can:
+
+        -   Expand the data sources to browse through their objects \(see [Import an Object from a Connection or Other Source](import-an-object-from-a-connection-or-other-source-3e6f8f2.md)\).
+        -   Open the *Import Objects from Connection* dialog on a particular connection to select multiple objects for import \(see [Import Multiple Objects from a Connection](import-multiple-objects-from-a-connection-e720b13.md)\).
+
+
+3.  Select the object of your choice, and then drag and drop it onto the diagram.
+
+     ![](images/Create_Source_Gif_fec4071.gif)The source is added to the diagram, its symbol is selected, and its properties are displayed in the side panel. In addition, an output node, initially entitiled ***View 1***, which represents the final output structure of the view, is created in the diagram and linked to the source.
+
+    > ### Note:  
+    > If you choose a table or view from the *Sources* tab, it is automatically imported into the repository and deployed, and will be available on the *Repository* tab for future use by you or others.
+
+4.  If the source is a view containing one or more input parameters \(see [Create an Input Parameter](create-an-input-parameter-53fa99a.md)\), the *Map Input Parameters* dialog is displayed, and you must decide how each input parameter will be processed:
+
+    -   *Map To* - Map the source input parameter to an input parameter in the view. You can select an existing input parameter or create a new one.
+
+        Users of this view will need to provide a value for the input parameter.
+
+    -   *Set Value* - Enter a value to resolve the input parameter.
+
+        The input parameter is resolved and users of this view will no longer need to provide a value for it.
+
+
+    > ### Note:  
+    > You can click *Cancel* in the dialog and not map the input parameters immediately, but then an error is displayed on the source, and you must subsequently map them in the source side panel *Input Parameters* section.
+
+    The source symbol displays the number of input parameters present in the source. In this example, the source view and output view both contain two input parameters::
+
+    ![](images/Input_Parameters_Source_Symbol_d4621d9.png)
+
+5.  Click <span class="FPA-icons"></span> \(Preview Data\) to open the *Data Preview* panel and review the data output by this node. For more information, see [Viewing or Previewing Data in Data Builder Objects](viewing-or-previewing-data-in-data-builder-objects-b338e4a.md).
+
+
diff --git a/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md b/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7496380.md
@@ -0,0 +1,54 @@
+<!-- loio749638060e8746e48b0f9bf0e50c6d0c -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Add a Source
+
+Define the source for your replication flow \(connection, container, and objects\).
+
+
+
+<a name="loio749638060e8746e48b0f9bf0e50c6d0c__context_x4r_ghf_vvb"/>
+
+## Context
+
+-   Connections are created by your system administration. You can only use a data source if a connection has been created for it in your space and if you have the necessary authorizations.
+
+-   Containers are the parent objects that hold the data. For a CDS view, for example, the container is the relevant CDS root folder.
+
+-   Replication objects are the datasets that you choose for replication, for example CDS views or database tables.
+
+
+
+
+## Procedure
+
+1.  Choose *Select Source Connection* at the bottom left of the screen. A list of available source connections appears. Select the relevant one for your use case.
+
+    If you are not sure which one to choose, or if none of the connections in the list is suitable for your purposes, contact your administrator.
+
+    Alternatively, you can get started by clicking <span class="FPA-icons"></span> \(Browse source connections\)
+
+2.  Choose *Select Source Container*. A list of available source containers appears. Select the relevant one for your use case.
+
+    To narrow down the selection, start typing a part of the folder name in the *Search* field.
+
+3.  Choose *Add Source Objects*. A list of available objects appears. Select the relevant ones for your use case and choose *Next*. A list of the objects you selected appears.
+
+    > ### Note:  
+    > Objects for which replication is not supported are not shown in the list. For example, when replicating data from an SAP S/4HANA source you will only be shown CDS views that have the required annotations for data extraction.
+
+4.  If you decide that you do not want to include an object after all, select it and choose *Remove from Selection*. If you want to include more objects, go back to the *Available* tab and select the relevant objects. When you are done, choose *Add Selection*. The system then imports the object definitions so that they are available for the subsequent process steps.
+
+    > ### Note:  
+    > An object can only be included in one replication flow at any given point in time \(not multiple ones\).
+
+
+
+
+<a name="loio749638060e8746e48b0f9bf0e50c6d0c__result_d5p_s5r_lvb"/>
+
+## Results
+
+You have all necessary information about your data source in place and can move on to add your target.
+