Merge branch 'sap-tutorials:main' into main

Author: MatthaeusSchuele

.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

@@ -260,7 +260,7 @@ For readability and reuse, you will create these in an interface.
 
 2. Enter the following and choose **Next**.
 
-  - Name: **`IF_TYPES_FOR_SYSTEM_INFO`**
+  - Name: **`ZIF_TYPES_FOR_SYSTEM_INFO`**
   - Description: **`Types for RFC_GET_SYSTEM_INFO`**
 
 3. Choose the transport request, then choose **Finish**.
@@ -348,7 +348,7 @@ In the class implementation, in the method **`if_oo_adt_classrun~main`**, add th
 
     DATA(lv_destination) = lo_destination->get_destination_name( ).
 
-    DATA lv_result type IF_TYPES_FOR_SYSTEM_INFO=>rfcsi.
+    DATA lv_result type ZIF_TYPES_FOR_SYSTEM_INFO=>rfcsi.
     DATA msg TYPE c LENGTH 255.
 
     ```
@@ -451,13 +451,13 @@ CLASS ZCL_SYSTEM_INFO_RFC_### IMPLEMENTATION.
 
             comm_scenario          = 'Z_OUTBOUND_RFC_###_CSCEN'   " Communication scenario
             service_id             = 'Z_OUTBOUND_RFC_###_SRFC'    " Outbound service
-            comm_system_id         = 'Z_OUTBOUND_RFC_CSYS'        " Communication system
+            comm_system_id         = 'Z_OUTBOUND_RFC_CSYS_###'        " Communication system
 
         ).
 
         DATA(lv_destination) = lo_destination->get_destination_name( ).
 
-        DATA lv_result TYPE if_types_for_system_info=>RFCSI.
+        DATA lv_result TYPE ZIF_TYPES_FOR_SYSTEM_INFO=>RFCSI.
         DATA msg TYPE c LENGTH 255.
 
         CALL FUNCTION 'RFC_GET_SYSTEM_INFO'

tutorials/abap-env-rfc/abap-env-rfc.md

@@ -104,6 +104,7 @@ You can test this in the browser:
 
  - `/ui#BusinessConfiguration-maintain` navigates to the List Report of the **Custom Business Configurations** app
  - `/ui#BusinessConfiguration-maintain?TechnicalIdentifier=ZERRORCODE###` directly navigates to the maintenance view of the Business Configuration Maintenance Object `ZERRORCODE###`
+ - `/ui#BusinessConfiguration-maintain?TechnicalIdentifier=ZERRORCODE###&ErrorCode=401` directly navigates to the object page of entity `401` of BC Object `ZERRORCODE###`
 
 
 ### Test yourself

tutorials/abap-environment-additional-functionality/abap-environment-additional-functionality.md

@@ -33,7 +33,7 @@ Always replace `####` with your initials or group number.
 The new **RAP based InA service exposure** enables the SAP Business Technology Platform ABAP Environment developers to develop analytical queries(based on ABAP-CDS analytical data models) and expose them via the `InA` (Information Access) service protocol. In this Tutorial you will create a complete Analytical Data Model for Booking data. This consists out of dimensions for Carrier, Customer, Connection and Agency data, as well as an interface CDS view for Booking data which acts as a data source for the cube and query.
 These analytical queries can be further consumed in the SAP Analytics cloud to create analytical models, stories, multi-dimensional reports and more.
 
-![overview](1.png)
+![overview](0010.png)
 
 
 ### Import templates for Analytical CDS views
@@ -491,7 +491,7 @@ This annotation is part of the template **Define a View Entity for a Cube** that
 
      - **Name**: `ZRAP500_I_BookingCube_####`
      - **Description**: `Booking Cube`
-     - **Referenced Object**: `ZRAP_I_BOOKING_####` (The booking interface view)
+     - **Referenced Object**: `ZRAP500_I_BOOKING_####` (The booking interface view)
 
      ![new cube](1270.png)
 
@@ -525,7 +525,7 @@ This annotation is part of the template **Define a View Entity for a Cube** that
 
 6. Comment out both lines of annotation `@Semantics.amount.currencyCode` and the property **Flight Price**.
 
-7. Add the following two fields alongside with a foreign key association
+7. Add the following two fields alongside with a foreign key association 
 
     ```foreignKey
         @ObjectModel.foreignKey.association: '_CustomerCountry'
@@ -636,7 +636,7 @@ This annotation is part of the template **Define a View Entity for a Cube** that
 ### Implement query as CDS view entity
 
 
-Since a query belongs to the projection layer (formerly known as consumption layer) it must have a **C** in its name according to the naming convention used in the Virtual Data Model (VDM) used in SAP S/4HANA. To create a query, there is a mandatory header annotation: **@Analytics.query: true**
+Since a query belongs to the projection layer (formerly known as consumption layer) it must have a **C** in its name according to the naming convention used in the Virtual Data Model (VDM) used in SAP S/4HANA.
 
 Again you can use a template that you have imported at the beginning of this tutorial.
 
@@ -657,9 +657,9 @@ Again you can use a template that you have imported at the beginning of this tut
 
       ![template query](1130.png)
 
-  5. Edit the code of your query and add the annotation **@AnalyticsDetails.query.axis** to all properties except the two measures `FlightPrice` and `TotalOfBookings`. All fields beside the field `CustomerCountry` get the annotation **@AnalyticsDetails.query.axis: #ROWS**, whereas the field `CustomerCountry` gets the annotation **@AnalyticsDetails.query.axis: #COLUMN**.
+  5. Edit the code of your query with removing **KEY** from `TravelID` and `BookingID`, add the annotation **@AnalyticsDetails.query.axis** to all properties except the two measures `FlightPrice` and `TotalOfBookings`. All fields beside the field `CustomerCountry` get the annotation **@AnalyticsDetails.query.axis: #ROWS**, whereas the field `CustomerCountry` gets the annotation **@AnalyticsDetails.query.axis: #COLUMN**.
 
-  6. You add a currency conversion to the field `FlightPrice` to be able to comparison all flight prices in a single currency.    
+  6. You add a currency conversion to the field `FlightPrice` to be able to comparison all flight prices in a single currency.
 
         ```
               @Semantics.amount.currencyCode: 'CurrencyCode'
@@ -676,25 +676,22 @@ Again you can use a template that you have imported at the beginning of this tut
 
       ![ADTquery](1131.png)
 
-    > Using the template the mandatory annotations for query is set automatically.
-    > **@Analytics.query: true**
     > With the annotation **@AnalyticsDetails.query.axis:<VALUE>**, the elements of the view can be positioned on multiple axes: Rows, Columns and Free. The elements can be directly annotated with their axis. All measures (elements which can be aggregated) need to be on the same axis. The annotation of the first measure will therefore be used for all measures of the query. If **@AnalyticsDetails.query.axis:<VALUE>** is not found, the system positions the measures on the columns.
 
   8. Your final code should look like the following:
 
     ```ZRAP500_C_BOOKINGQUERY_####
-    @AccessControl.authorizationCheck: #CHECK
-    @EndUserText.label: 'Query for Booking'
-
-
-    @Analytics.query: true
+    @EndUserText.label: 'Flights Query'
+    @AccessControl.authorizationCheck: #NOT_ALLOWED
 
-
-    define view entity ZRAP500_C_BOOKINGQUERY_#### as select from ZRAP500_I_BookingCube_#### {
+    define transient view entity DEF23_Flights_Query
+      provider contract analytical_query
+      as projection on DEF23_Flights_Cube
+    {
     @AnalyticsDetails.query.axis: #ROWS
-    key TravelID,
+    TravelID,
     @AnalyticsDetails.query.axis: #ROWS
-    key BookingID,
+    BookingID,
     @AnalyticsDetails.query.axis: #ROWS
     BookingDate,
     @AnalyticsDetails.query.axis: #ROWS
@@ -733,8 +730,7 @@ Again you can use a template that you have imported at the beginning of this tut
 
 ### Data preview
 
-
-Similar to the SAP Fiori Elements preview which is offered for OData V2 UI and OData V4 UI service bindings there is now an Analytical Data Preview available. This can be used by the ABAP developer to test the implementation of an Analytical Query since the preview uses the InA protocol.
+Similar to the SAP Fiori Elements preview which is offered for OData V2 UI and OData V4 UI service bindings there is now an Analytical Data Preview available. This can be used by the ABAP developer to test the implementation of an Analytical Query since the preview uses the InA protocol. 
 
 Now that you have created the query it is possible to use a data preview to test our implementation.