Merge branch 'sap-tutorials:main' into main

Author: julieplummer20

.reuse/dep5

@@ -6,7 +6,7 @@ Default templates for SAP open source repositories, including LICENSE, .reuse/de
 
 ## To-Do
 
-In case you are the maintainer of a new SAP-toturials open source project, these are the steps to do with the template files:
+If you are the maintainer of a new SAP-toturials open source project, these are the steps to do with the template files:
 
 - Check if the default license (Apache 2.0) also applies to your project. A license change should only be required in exceptional cases. If this is the case, please change the [license file](LICENSE).
 - Enter the correct metadata for the REUSE tool. See our [wiki page](https://wiki.wdf.sap.corp/wiki/display/ospodocs/Using+the+Reuse+Tool+of+FSFE+for+Copyright+and+License+Information) for details how to do it. You can find an initial .reuse/dep5 file to build on. Please replace the parts inside the single angle quotation marks < > by the specific information for your repository and be sure to run the REUSE tool to validate that the metadata is correct.

README.md

@@ -0,0 +1,11 @@
+version = 1
+SPDX-PackageName = "abap-core-development"
+SPDX-PackageSupplier = "julie.plummer@sap.com"
+SPDX-PackageDownloadLocation = "<https://github.com/sap-tutorials/abap-core-development"
+SPDX-PackageComment = "The code in this project may include calls to APIs (\"API Calls\") of\n SAP or third-party products or services developed outside of this project\n (\"External Products\").\n \"APIs\" means application programming interfaces, as well as their respective\n specifications and implementing code that allows software to communicate with\n other software.\n API Calls to External Products are not licensed under the open source license\n that governs this project. The use of such API Calls and related External\n Products are subject to applicable additional agreements with the relevant\n provider of the External Products. In no event shall the open source license\n that governs this project grant any rights in or to any External Products,or\n alter, expand or supersede any terms of the applicable additional agreements.\n If you have a valid license agreement with SAP for the use of a particular SAP\n External Product, then you may make use of any API Calls included in this\n project's code for that SAP External Product, subject to the terms of such\n license agreement. If you do not have a valid license agreement for the use of\n a particular SAP External Product, then you may only make use of any API Calls\n in this project for that SAP External Product for your internal, non-productive\n and non-commercial test and evaluation of such API Calls. Nothing herein grants\n you any rights to use or access any SAP External Product, or provide any third\n parties the right to use of access any SAP External Product, through API Calls."
+
+[[annotations]]
+path = "**"
+precedence = "aggregate"
+SPDX-FileCopyrightText = "2022 SAP SE or an SAP affiliate company and abap-core-development contributors"
+SPDX-License-Identifier = "CC-BY-4.0"

REUSE.toml

@@ -4,10 +4,10 @@ auto_validation: true
 time: 20
 tags: [ tutorial>beginner, topic>cloud, tutorial>license, products>sap-business-technology-platform, products>sap-business-application-studio  ]
 primary_tag: topic>abap-extensibility
-author_name: Ulrike Liebherr
-author_profile: https://github.com/Liebherr
+author_name: Peter Persiel
+author_profile: https://github.com/peterpersiel
 ---
-<!--DONE with E1Y-->
+<!--DONE with E1Y (https://dlm.wdf.sap.corp/launchpad/portal/#/Search/e1y -> https://my300098.s4hana.ondemand.com/ and btp trial -->
 # Connect SAP Business Application Studio and SAP S/4HANA Cloud System
 <!-- description --> For key user extensibility connect SAP Business Application Studio and an SAP S/4HANA Cloud system using SAML assertion authentication to develop custom UIs.
 
@@ -21,7 +21,7 @@ author_profile: https://github.com/Liebherr
 
 **Additional Infos**
 > - If you want to create a custom SAP Fiori app with developer extensibility check out [Develop an SAP Fiori App to Trigger Purchase Requisitions API](https://developers.sap.com/group.sap-fiori-app-purchase-req.html)
-> - Tutorial last updated with SAP S/4HANA Cloud Release 2302
+> - Tutorial last checked for feasibility with SAP S/4HANA Cloud Release 2408
 
 **Prerequisites for SAP BTP customer account**
 
@@ -71,24 +71,24 @@ Although this tutorial describes the flow with a trial account, the sequence is
 
     |  Field Name     | Value
     |  :------------- | :-------------
-    |  Name           | **`<YOUR_SYSTEMS_ID>_SAML_ASSERTION`**
-    |  Type           | **`HTTP`**
-    |  Description    | **`SAML Assertion Destination to SAP S/4HANA Cloud system <YOUR_SYSTEMS_ID>`**
-    |  URL          | In the SAP S/4HANA Cloud system, navigate to the **Communication Systems** app and copy the **Host Name** from **Own SAP Cloud System** = `Yes`<div>![Own System Host Name in Communication Systems App](s4hc-cs-own-system-host-name.png)</div> and paste it with prefix `https://` for example `https://my12345-api.s4hana.ondemand.com.`
-    |  Proxy Type   | **`Internet`**
-    |  Authentication | **`SAMLAssertion`**
-    |  Audience   | Enter the URL of your system and remove `-api`, for example `https://my12345.s4hana.ondemand.com`.
+    |  `Name`           | **`<YOUR_SYSTEMS_ID>_SAML_ASSERTION`**
+    |  `Type`           | **`HTTP`**
+    |  `Description`    | **`SAML Assertion Destination to SAP S/4HANA Cloud system <YOUR_SYSTEMS_ID>`**
+    |  `URL`          | In the SAP S/4HANA Cloud system, navigate to the **Communication Systems** app, click the **Own SAP Cloud System** button, copy the **Host Name** <div>![Own System Host Name in Communication Systems App](s4hc-cs-own-system-host-name.png)</div> and paste it with prefix `https://` for example `https://my12345-api.s4hana.ondemand.com.`
+    |  `Proxy Type`   | **`Internet`**
+    |  `Authentication` | **`SAMLAssertion`**
+    |  `Audience`   | Copy and paste the `OAuth 2.0 SAML2 Audience` from the **Own SAP Cloud System**.
     |  `AuthnContextClassRef` | **`urn:oasis:names:tc:SAML:2.0:ac:classes:PreviousSession`**
 
     Select **New Property** and maintain the following **Additional Properties** and values.
 
     |  Field Name     | Value          | Remark
     |  :------------- | :------------- | :-------------
-    |  HTML5.DynamicDestination           | **`true`**   |&nbsp;
-    |  HTML5.Timeout           | **`60000`**   | value stated in milliseconds. 60000 equals 1 minute. Required as deployment needs longer than the standard of 30 seconds.
+    |  `HTML5.DynamicDestination`           | **`true`**   |&nbsp;
+    |  `HTML5.Timeout`           | **`60000`**   | value stated in milliseconds. 60000 equals 1 minute. Required as deployment needs longer than the standard of 30 seconds.
     |  `WebIDEEnabled`    | **`true`**   |&nbsp;
     |  `WebIDEUsage`          | **`odata_abap,dev_abap`**   |&nbsp;
-    |  `nameIDFormat`     | **`urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`**  | Required in case your subaccount sends the e-mail address as SAML Subject Name Identifier for authentication (configured as **Subject Name Identifier** in its SAP Cloud Identity Service Application, see [Tutorial: SAP Business Technology Platform Neo Environment](abap-custom-ui-trust-settings)), although SAP S/4HANA Cloud system expects user login by default. **That is the case with a trial Account.** This also requires the e-mail address to be maintained for SAP S/4HANA Cloud system business users.
+    |  `nameIDFormat`     | **`urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`**  | Required in case your subaccount sends the e-mail address as SAML Subject Name Identifier for authentication (configured as **Subject Name Identifier** in its SAP Cloud Identity Service Application, see [Tutorial: Set Up Trust Between SAP Cloud Identity Services and SAP BTP Cloud Foundry Environment](abap-custom-ui-trust-cf)), although SAP S/4HANA Cloud system expects user login by default. **That is the case with a trial Account.** This also requires the e-mail address to be maintained for SAP S/4HANA Cloud system business users.
 
 8.  Make sure that the **Use default JDK truststore** checkbox is ticked.
 

tutorials/abap-custom-ui-bas-connect-s4hc/abap-custom-ui-bas-connect-s4hc.md

@@ -4,8 +4,8 @@ auto_validation: true
 time: 25
 tags: [ tutorial>beginner, topic>cloud, tutorial>license, products>sap-business-technology-platform, products>sap-business-application-studio  ]
 primary_tag: topic>abap-extensibility
-author_name: Ulrike Liebherr
-author_profile: https://github.com/Liebherr
+author_name: Peter Persiel
+author_profile: https://github.com/peterpersiel
 ---
 
 # Develop a Custom UI for an SAP S/4HANA Cloud System
@@ -25,7 +25,7 @@ author_profile: https://github.com/Liebherr
 **Additional Info**
 > - This tutorial illustrates all the needed steps to build a UI with all SAPUI5 options in SAP Business Application Studio, test it, and get it into the SAP S/4HANA Cloud system. If you only require a generated UI and maybe adapting it with restricted options within the SAP S/4HANA Cloud system (in-app-extensibility) check out [Generate the UI for a Custom Business Object and grant Access](abap-extensibility-cbo-ui-generation) and [Adapt the UI of a Business Object](abap-extensibility-cbo-ui-adaptation)
 > - If you want to create a custom SAP Fiori app with developer extensibility check out [Develop an SAP Fiori App to Trigger Purchase Requisitions API](https://developers.sap.com/group.sap-fiori-app-purchase-req.html)
-> - Tutorial last updated with SAP S/4HANA Cloud Release 2302
+> - Tutorial last checked for feasibility with SAP S/4HANA Cloud Release 2408
 
 ---
 
@@ -62,21 +62,22 @@ SAP Business Application Studio offers UI generators with a wizard approach to c
 
     ![Open Dev Space](bas-dev-space-open.png)
 
-3. Go to **View > Command Palette...**.
+3. Click the three lines on top of the navigation to open **View > Command Palette...**.
 
     ![Open "Find Command"](bas-command-palette.png)
 
-4. Search for command **Fiori: Open Application Generator** and select it.
+4. Search for command **>Fiori: Open Application Generator** and execute it.
 
     ![search and choose "Fiori: Open Application Generator" command](bas-command-palette-fiori-app-gen.png)
 
 
 
-### Select floorplan
+### Select UI Project Template
 
-For **Template Type**, select the default  **SAP Fiori** (1), choose **List Report Page** (2) as **Floorplan** and click **Next** (3).
+As UI project template choose **List Report Page** (1) and click **Next** (2).
 
-![UI Wizard: Floorplan Selection](bas-appgen-floorplan-sel.png)
+<!--border-->
+![UI Wizard: UI Project Template Selection](bas-appgen-floorplan-sel.png)
 
 
 ### Select Data Source
@@ -98,6 +99,7 @@ During the **Data Source and Service Selection** step, you define which system a
 
 In this step you define the root node for your UI in the OData service.
 
+<!--border-->
 ![UI Wizard: Select Entity](bas-appgen-entity-sel.png)
 
 1. As **Main Entity**, select the custom business object root node `YY1_BONUSPLAN`.
@@ -109,6 +111,7 @@ In this step you define the root node for your UI in the OData service.
 
 In this step, you set project attributes and choose to add further optional configurations.
 
+<!--border-->
 ![UI Wizard: Set Project Attributes](bas-appgen-proj-attrs.png)
 
 1. Define a **Module name**, which will later be the folder name of the UI Project and - in combination with optional namespace - the application ID in SAP S/4HANA Cloud system. Example: `bonusplans`
@@ -126,6 +129,7 @@ In this step, you set project attributes and choose to add further optional conf
 
 In this step, you define where you want the UI project to be deployed to as a runnable application.
 
+<!--border-->
 ![UI Wizard: Configure Deployment Settings](bas-appgen-deploy-config.png)
 
 1. Leave the default `ABAP` as **target** platform and as **Destination** the one you have created earlier (see [Connect SAP Business Application Studio and SAP S/4HANA Cloud system](abap-custom-ui-bas-connect-s4hc)).
@@ -146,6 +150,7 @@ npx fiori add deploy-config
 
 The SAP Fiori launchpad (FLP) configuration is required to embed your application as a tile into the FLP.
 
+<!--border-->
 ![UI Wizard: Configure FLP settings](bas-appgen-flp-config-finish.png)
 
 1. Set a **Semantic Object**, for example `bonusplan`
@@ -161,21 +166,22 @@ The UI project is now being generated and dependencies are being installed. This
 
 ![Installation toast on bottom Right](bas-appgen-installing-after-finish.png)
 
-Once the generation finished a pop up appears to ask if and how to open it. Choose **Open Folder**
+Once the generation finished a pop up appears to ask if and how to open it. Choose **Add project to workspace**
 
-![Open project folder pop up](bas-appgen-open-folder-after-finish.png)
+<!--border-->
+![Add project to workspace pop up](bas-appgen-open-folder-after-finish.png)
 
 >Note that you can also configure the launchpad later via the command line interface by using the following command:
 ```Shell/Bash
 npx fiori add flp-config
 ```
 
 
-### Open UI project folder
+### Open UI project folder (optional)
 
-In case your SAP Business Application Studio's explorer does not show the project, do the following. 
+In case your SAP Business Application Studio's explorer does not show the project, do the following.
 
-1. To view the newly created project in the explorer, select **Open Folder**.
+1. To view the newly created project in the explorer with all features, select **Open Folder**.
 
     ![Choose Open Folder Option](bas-open-folder.png)
 
@@ -189,22 +195,46 @@ In case your SAP Business Application Studio's explorer does not show the projec
 
 In this step, you can test the UI with the preview functionality.
 
-1. Right-click the project folder and choose **Preview Application** from the context menu.
+1. After Opening the project, Business Application Studio also opens an **Application Info** tab. In its **What you can do** section click the **Preview Application** tile.
 
+    <!--border-->
     ![Start Preview](bas-preview-start.png)
 
+    > Note that in case there is no Application Info tab you can open it from the context menu of the project
+    >
+    > <!--border-->
+    > ![Open Application Info tab](bas-open-appl-info.png)
+
 2. Select the `start` option, which will perform a preview based on the configured data source system, retrieve real data and enable you to create, edit and delete data in that system.
 
+    <!--border-->
     ![Choose start preview option](bas-preview-system-data.png)
 
     A terminal is opened that automatically executes the underlying command.
 
+    <!--border-->
     ![At preview opening terminal](bas-preview-terminal.png)
 
     Once the command has reached the required state, a new browser tab with the preview is opened.
 
+    > Alternatively to Preview from Application Info tab, you can open a terminal for your project by right-clicking it and choosing **Open in Integrated Terminal** from the context menu.
+    >
+    >![Open Project in Integrated Terminal](bas-open-project-in-terminal.png)
+    >
+    > In the `cli` (command line interface) terminal, enter the following command:
+    >
+    >```Shell/Bash
+    >npm run start
+    >```
+    >
+    ><!--border-->
+    >![Enter preview command in cli](bas-cli-enter-preview-command.png)
+    >
+    >Press return.
+
 3. To view existing entries, select **GO** or **Create** to add a new entry.
 
+    <!--border-->
     ![Resulting preview browser tab](bas-preview-result.png)
 
 
@@ -213,28 +243,30 @@ In this step, you can test the UI with the preview functionality.
 
 Once the UI is set up to your needs, you can deploy it to the development SAP S/4HANA Cloud system, where it can be tested and transported to test or productive tenants.
 
-1. Open a terminal for your project by right-clicking it and choosing **Open in Integrated Terminal** from the context menu.
-
-    ![Open Project in Integrated Terminal](bas-open-project-in-terminal.png)
-
-2. In the `cli` (command line interface) terminal, enter the following command:
+1. In the **Application Info** tab, section **What you can do** click the **Deploy** tile
 
-    ```Shell/Bash
-    npm run deploy
-    ```
-    ![Enter deploy command in cli](bas-cli-enter-deploy-command.png)
+    <!--border-->
+    ![Start Preview](bas-deploy-start.png)
 
-    Press return.
+    > Alternatively to Application Info, in the `cli` (command line interface) terminal, enter the following command:
+    >
+    >```Shell/Bash
+    >npm run start
+    >```
+    >
+    >![Enter deploy command in cli](bas-cli-enter-deploy-command.png)
+    >
+    >Press return.
 
-3. Check the deployment configuration.
+2. Check the deployment configuration.
 
     ![Check deployment configuration in command output](bas-cli-check-deploy-config.png)
 
-4. Confirm the deployment by entering `y`
+3. Confirm the deployment by entering `y`
 
     ![Confirm deployment configuration](bas-cli-confirm-deployment.png)
 
-5. Deployment will start, which might take a while.
+4. Deployment will start, which might take a while.
 
     ![Deployment log](bas-cli-deployment-log.png)