// Create a new ODataModel for OData v2
const oModel = new sap.ui.model.odata.v2.ODataModel("/sap/opu/odata/sap/Your_OData_Service/", {
    useBatch: false // Set this to true for batch processing support
});
// Bind data to a table
const oTable = new sap.ui.table.Table({
    visibleRowCount: 10,
    selectionMode: sap.ui.table.SelectionMode.Single,
    rows: "{/EntitySet}"
});
oTable.addColumn(new sap.ui.table.Column({
    label: new sap.ui.commons.Label({ text: "ID" }),
    template: new sap.ui.commons.TextView().bindProperty("text", "ID"),
    sortProperty: "ID",
    filterProperty: "ID"
}));
// ... other columns ...
oTable.setModel(oModel);

Now, Enter the following values for association and press enter:

2. Choose the Create pushbutton:

3. Enter the values and choose Enter:

Name	SalesOrderSalesOrderItems
Association*	SalesOrderSalesOrderItems

And finally we create a navigation property based on the referential constraint

1. Expand Data Model > Entity Types > SalesOrder and double-click Navigation Properties:

2. Choose the Create pushbutton:

3. Enter the following values and choose Enter:

Name	SalesOrderItems
Relationship Name*	SalesOrderSalesOrderItems

Now we need to re-generate the runtime objects and we’re then ready to test the service

1. Choose the Generate pushbutton:

2. Verify that the runtime objects have been generated successfully:

3. Start the Gateway Client (Transaction /IWFND/GW_CLIENT) in a separate window to run the service. Provide the following URI to get the metadata for the service: 

/sap/opu/odata/sap/ZGW100_XX_SO_SRV/$metadata

The Sales Order collection now includes a navigation property.

4. When you now select a sales order entry using

/sap/opu/odata/sap/ZGW100_XX_SO_SRV/SalesOrderCollection(‘0500000001’), for example, you can simply add the navigation link /SalesOrderItems to navigate to the line items without having to set a filter yourself:

5. And finally you can use $expand to read all sales order items for a given sales order in a single http call.

Simply provide the following URI:

/sap/opu/odata/sap/ZGW100_XX_SO_SRV/SalesOrderCollection(‘0500000001’)/?$expand=SalesOrderItems

The $expand statement is handled by the framework (no additional implementation is required). Since the framework does not know that both entities can be obtained using a single RFC call, it executes two calls to the underlying BAPI. This can be improved by manually implementing (re-defining) the GET_EXPANDED_ENTITY method.

So we are done. The Service is up and running.

1. Properties. Allows define its appearance and behavior on initialization.
2. Aggregations. It lets group controls, variables, etc. It lets define some kind of containers inside a control. For example sap.m.ListBase has different aggregations items, swipeContent, headerToolBar etc.
3. Associations. Controls can be associated with others that are not part of them. For example if we want to render a collection with next/prev functionality we could develop a previousItem / nextItem associations.
4. Events. Control events should be related to higher level events more than standard DOM events (click, mouseover, etc). For example sap.m.ListBase has some events like select, delete, swipe etc.
5. Appearance. Definition of our control in screen area. Every control has a render method in order to be rendered in HTML code.