Define and Expose a CDS-Based Travel Data Model

Right-click on your package ZTRAVEL_APP_XXX, select New > Other ABAP Repository Object.

Search for data definition, select it and click Next >.

Create a data definition:

• Name: ZI_TRAVEL_M_XXX
• Description: Data model for travel

Click Next >.

Click Finish to use your transport request.

Add associations, fields, UI semantics and the root node to your data definition. Therefore replace your code with following:

@EndUserText.label: 'Travel data XXX'
@AccessControl.authorizationCheck: #CHECK
define root view entity ZI_TRAVEL_M_XXX

  as select from ztravel_xxx as Travel

  /* Associations */
  association [0..1] to /DMO/I_Agency   as _Agency   on $projection.agency_id = _Agency.AgencyID
  association [0..1] to /DMO/I_Customer as _Customer on $projection.customer_id = _Customer.CustomerID
  association [0..1] to I_Currency      as _Currency on $projection.currency_code = _Currency.Currency

{

  key mykey,
      travel_id,
      agency_id,
      customer_id,
      begin_date,
      end_date,
      @Semantics.amount.currencyCode: 'currency_code'
      booking_fee,
      @Semantics.amount.currencyCode: 'currency_code'
      total_price,
      currency_code,
      overall_status,
      description,

      /*-- Admin data --*/
      @Semantics.user.createdBy: true
      created_by,
      @Semantics.systemDateTime.createdAt: true
      created_at,
      @Semantics.user.lastChangedBy: true
      last_changed_by,
      @Semantics.systemDateTime.lastChangedAt: true
      last_changed_at,

      /* Public associations */
      _Agency,
      _Customer,
      _Currency
}

Save and activate.

Your CDS view for travel booking is defined now. You can use and manipulate data that is persisted in your database.

Right-click on your package ZTRAVEL_APP_XXX, select New > Other ABAP Repository Object.

Search for data definition, select it and click Next >.

Create a data definition:

• Name: ZC_TRAVEL_M_XXX
• Description: Projection view for travel

Click Next >.

Click Finish to use your transport request.

Replace your code with following:

@EndUserText.label: 'Travel projection view - Processor'
@AccessControl.authorizationCheck: #NOT_REQUIRED

@UI: {
 headerInfo: { typeName: 'Travel', typeNamePlural: 'Travels', title: { type: #STANDARD, value: 'TravelID' } } }

@Search.searchable: true

define root view entity ZC_TRAVEL_M_XXX
  as projection on ZI_TRAVEL_M_XXX
{
      @UI.facet: [ { id:              'Travel',
                     purpose:         #STANDARD,
                     type:            #IDENTIFICATION_REFERENCE,
                     label:           'Travel',
                     position:        10 } ]

      @UI.hidden: true
  key mykey              as TravelUUID,


      @UI: {
          lineItem:       [ { position: 10, importance: #HIGH } ],
          identification: [ { position: 10, label: 'Travel ID [1,...,99999999]' } ] }
      @Search.defaultSearchElement: true
      travel_id          as TravelID,

      @UI: {
          lineItem:       [ { position: 20, importance: #HIGH } ],
          identification: [ { position: 20 } ],
          selectionField: [ { position: 20 } ] }
      @Consumption.valueHelpDefinition: [{ entity : {name: '/DMO/I_Agency', element: 'AgencyID'  } }]

      @ObjectModel.text.element: ['AgencyName'] ----meaning?
      @Search.defaultSearchElement: true
      agency_id          as AgencyID,
      _Agency.Name       as AgencyName,

      @UI: {
          lineItem:       [ { position: 30, importance: #HIGH } ],
          identification: [ { position: 30 } ],
          selectionField: [ { position: 30 } ] }
      @Consumption.valueHelpDefinition: [{ entity : {name: '/DMO/I_Customer', element: 'CustomerID'  } }]

      @ObjectModel.text.element: ['CustomerName']
      @Search.defaultSearchElement: true
      customer_id        as CustomerID,

      @UI.hidden: true
      _Customer.LastName as CustomerName,

      @UI: {
          lineItem:       [ { position: 40, importance: #MEDIUM } ],
          identification: [ { position: 40 } ] }
      begin_date         as BeginDate,

      @UI: {
          lineItem:       [ { position: 41, importance: #MEDIUM } ],
          identification: [ { position: 41 } ] }
      end_date           as EndDate,

      @UI: {
          lineItem:       [ { position: 50, importance: #MEDIUM } ],
          identification: [ { position: 50, label: 'Total Price' } ] }
      @Semantics.amount.currencyCode: 'CurrencyCode'
      total_price        as TotalPrice,

      @Consumption.valueHelpDefinition: [{entity: {name: 'I_Currency', element: 'Currency' }}]
      currency_code      as CurrencyCode,

      @UI: {
      lineItem:       [ { position: 60, importance: #HIGH },
                        { type: #FOR_ACTION, dataAction: 'acceptTravel', label: 'Accept Travel' } ],
      identification: [ { position: 60, label: 'Status [O(Open)|A(Accepted)|X(Canceled)]' } ]  }
      overall_status     as TravelStatus,

      @UI.identification: [ { position: 70, label: 'Remarks' } ]
      description        as Description,

      @UI.hidden: true
      last_changed_at    as LastChangedAt

}

Save and activate.

The projection is created and includes UI annotations. The projection is the subset of the fields of the travel data model, which are relevant for the travel booking application.

Right-click on your data definition ZC_TRAVEL_M_XXX and select New Service Definition.

Create a new service definition:

• Name: ZUI_C_TRAVEL_M_XXX
• Description: Service definition for travel

Click Next >.

Click Finish to use your transport request.

Replace your code with following:

@EndUserText.label: 'Service Definition for ZC_Travel_M_XXX'
define service ZUI_C_TRAVEL_M_XXX
{
  expose ZC_TRAVEL_M_XXX as TravelProcessor;
  expose /DMO/I_Customer as Passenger;
  expose /DMO/I_Agency as TravelAgency;
  expose /DMO/I_Airport as Airport;
  expose I_Currency as Currency;
  expose I_Country as Country;
}   

Save and activate.

With the service definition you are able to define which data is exposed as a business service in your travel booking application.

Right-click on your service definition ZUI_C_TRAVEL_M_XXX and select New Service Binding.

Create a new service binding:

• Name: ZUI_C_TRAVEL_M_XXX
• Description: Service binding for travel
• Binding Type: ODATA V2 - UI

Click Next >.

Click Finish to use your transport request.

Activate your service binding and then publish it.

Now your service binding is created and you are able to see your service with its entities and associations.

The service binding allows you to bind the service definition to an ODATA protocol. Therefore you are able to see the travel booking application on the UI.