Git-based CTS (the evolution of the classical CTS)
An open-source Git client that allows you to import existing code into your ABAP system
A Repository is a collection of objects, their directory structure, and metadata
A transport request records all the changes in your ABAP development system. With gCTS: Once a transport request is released, the changes are pushed into your central Git repository in the cloud as a commit represented by a commit ID.
These are my notes on the steps needed to create the data model and publish it as oData service.
Place your raw data first
Data Definition (Interface View)
Relation between different tables (e.g. currency or text table)
Projection View (Consumption View)
Configure the UI depending on your scenario. Use different projection views for different usages of the same interface view and the same physical table.
Expose the projection view (and underlying associations like currency, country…) as service
How to we want to make the service available? Defines the binding type (OData V2 / OData V4) Activate it with the “Activate” Button within the editor window. Select the Entity and hit “Preview…” to see whtat we defined in our projection view.
If you’ve done this, you are able to view the data in a generated Fiori Elements app. But if you also want to create, edit, delete data, you’ll have to add some behavior functionality.
Behavior Definition on Data Definition
Created on top of the Data Definition. Will get the same name es the Data Definition. Implementation Type: Managed Defines the operations create, delete, edit.
Behavior Implementation on Definition View
The code for the behavior… For the travel app tutorial, some logic for a generated unique key and field validation. The class inherits from cl_abap_behavior_handler.
Behavior Definition on Projection View
Created on top of the Projection View. Will get the same name es the Projection View. Defines the operations create, delete, edit.