Create Communication Objects for a Remote OData Service
Requires Customer/Partner License
Intermediate
45 min.
Create an inbound communication scenario, arrangement, system, and user in the provisioning system of SAP BTP, ABAP Environment.
You will learn
- In the provisioning system: How to expose a CDS view as an OData service using a Service Binding
- How to wrap this OData service in an inbound communication scenario, so that it can be accessed from another instance of SAP BTP, ABAP environment
- How to make the provisioning system available for connection from other ABAP systems
- How to test your service URL in Postman (optional)
- In the client system: How to create a new destination with an HTTP connection, pointing to the provisioning system
Prerequisites
- IMPORTANT: This tutorial cannot be completed on a trial account
- You have set up 2 instances of SAP Business Technology Platform, ABAP Environment, a provisioning system and a client system, for example by using the relevant booster: Using a Booster to Automate the Setup of the ABAP Environment
- Tutorial: Create Your First Console Application, for a licensed user, steps 1-2, for both instances
- In the provisioning system:
- The business catalog
SAP_CORE_BC_COM
is assigned to your user - The ABAP Flight Reference Scenario is available. To pull this reference scenario from
Github
, see Downloading the ABAP Flight Reference Scenario - You have exposed the data definition
/DMO/TRAVEL_U
as an OData service, using a service definition and service binding
- The business catalog
- You have read Developing a UI Service with Access to a Remote Service and its Scenario Description, since this mission is based on this tutorial series
- Optional: You have installed the Postman API Platform
This involves some overhead for one consumer; however, the advantage is that you can add several consumer systems, or users (for example, with different authentication) pointing to the same HTTP service, wrapped in the same Communication Scenario.

.
.
Mission Scenario:
You want to get data that is only available in a remote instance of SAP BTP, ABAP Environment ( provisioning system ) and display it in a second instance ( client system ).
You need to:
- Create inbound communication artifacts for an OData Service in the provisioning system
- Create a Service Consumption Model, and save this locally as a
$metadata
XML file; From this you will create proxy artifacts in the client system, representing the remote service, and use this model to generate an abstract entity - Create a Remote Client Proxy
- Build a new OData service in the client system, using a CDS custom entity and query implementation class
- Finally, display the remote data in Fiori Elements preview in your browser
