Create an ABAP Core Data Services (CDS) View in ABAP On-Premise

1. Select your service definition, then choose Service Binding from the context menu, then choose Next.

   

2. Choose:

   • Name = Z_BIND_TRAVEL_XXX

   • Description = Service binding for Travel data

   • Binding Type = ODATA V2 (UI…)

   • Service Definition = Z_EXPOSE_TRAVEL_XXX

     

3. Choose the transport request; choose Finish.

The service binding automatically references the service definition and thus the exposed custom entity.

1. In the editor that appears, choose Activate.

   

2. You can now see the Service URL and Entity Set.

   

3. To open the Service Document (XML) in your browser, choose Service URL.

   

   

4. In the browser, you can also see the Metadata Document of the Business Service by adding $metadata to the URL: `/sap/opu/odata/sap/Z_BIND_TRAVEL_XXX/$metadata`.

   

1. Select the entity set and choose Preview.

   

2. Log in using your ABAP Environment user and password; the Fiori Elements preview appears.

3. By default, no columns are selected. To see the data, choose Settings, then choose Select All.

   

   

4. Display the data by choosing Go.

   

1. It would be nice if at least some fields were displayed immediately for the user. To do this, simply add the following annotation to the relevant fields in Z_I_TRAVEL_R_XXX. The start of your CDS entity will then look like this.

   BookingFee is not automatically displayed. The numbers for each field are relative to the other fields and are responsive - they do not refer to a specific pixel position or similar. For larger entities, you can specify HIGH,MEDIUM, or LOW, so that less important fields are automatically hidden on a smaller screen, such as a mobile phone.

   CDS Copy

   @UI           : {
   lineItem      : [{position: 10, importance: #HIGH}]
   }
   key TravelID;
   
   @UI           : {
         lineItem      : [{position: 15, importance: #HIGH}]
         }
   AgencyID,
   
   @UI           : {
         lineItem      : [{position: 20, importance: #HIGH}]
         }
   CustomerID,
   
   @UI           : {
         lineItem      : [{position: 30, importance: #HIGH}]
         }
   BeginDate,
   
   @UI           : {
         lineItem      : [{position: 40, importance: #HIGH}]
         }
   EndDate,
   
   BookingFee,
   
   @UI           : {
         lineItem      : [{position: 50, importance: #HIGH}]
         }
   TotalPrice,

   Show all 31 lines Show less

2. If you now refresh your Fiori Elements preview, you will notice that you do not have to choose the fields; you simply have to choose Go.

At present, you only have minimal annotations. As you add more, your CDS entity will start to get cluttered. So you should extract your UI annotations to a separate object, a metadata extensions object, as follows:

1. First add the annotation @Metadata.allowExtensions: true to your CDS entity.

2. Then, click anywhere in the editor, then choose Source Code > Extract Metadata Extension from the context menu.

   

3. Enter a name and description for your metadata extension object, clearly similar to your CDS entity name, and choose Next:

   • Z_TRAVEL_METADATA_XXX
   • Metadata for Z_I_TRAVEL_R_XXX

4. Accept the transport request, choose Next, select all elements, then choose Finish.

   

5. You will get an error, because you have not yet assigned the metadata extension to a layer. Since you are in sandbox mode, enter the value #CORE using auto-complete ( Ctrl+Space ).

   

   Layers allow customers or partners, for example, to enhance the metadata without modifying the CDS entity. You can also add industry- or country-specific enhancements.

   The metadata extensions are evaluated in a specific order. For more information, see Annotation Propagation.

6. Format, save, and activate ( Shift+F1, Ctrl+S, Ctrl+F3 ).

If you define currency amounts and currency codes semantically, then the system will apply specific rules to handle these fields appropriately. For example, in this tutorial, if you define TotalPrice as a currency amount, then the system will add the appropriate currency to the TotalPrice column automatically. There is no need to display CurrencyCode as a separate column.

1. To do this, add the following two annotations to your CDS entity:

   CDS Copy

   
   @Semantics.amount.currencyCode: 'CurrencyCode'        
   TotalPrice,
   
   @Semantics.currencyCode
   CurrencyCode,