OData & SAP Gateway Essentials

What is OData, and which technologies is it built on?

Where in the metadata document are the service's entity sets defined, and how do they relate to the service document?

What do the two ends of an OData association declare?

How is the trusted RFC from Gateway to the Business Suite configured?

Where do SAP Gateway administration rights come from?

What are the four subconstraints of REST's uniform interface?

From which existing SAP artifacts can SAP Gateway objects be generated?

How do you fetch a service's metadata document, and in which language is it written?

Which built-in tool executes test OData requests against a service, and where do you launch it?

Which six constraints must an application satisfy to count as RESTful?

In an OData data model, what are entity sets and associations?

The trusted RFC exists on the front end, but the trust setup still fails. What completes it?

How does the SAP system alias setup differ between embedded and central hub deployments?

Which two documents accompany every OData service, and what does each describe?

What is the difference between PUT and PATCH/MERGE in OData?

How does an OData URI navigate from a supplier to its products?

Why pair OData with SAP Gateway — what advantages does the combination bring?

Which REST constraint is optional, and what does it allow?

What ties the entities of one entity set together?

A user's Fiori UI comes up in the wrong language. Which rules govern SAP Gateway's language handling?

What does SAP Gateway connect, and what knowledge does a consumer need?

OData services are often described as read APIs for the UI. What is wrong with that picture?

Which OData query options shape a result set — and what is the gotcha with '$page'?

Which three layers make up the Fiori-with-Gateway architecture?

Where is SAP Gateway itself switched on?