Glossary

Prepackaged business logic attached to an entity type.

Metadata attached to a consumption model element.

Function that handles the OData Channel as well as the events and actions activated in the SAP Business Suite system and publishes these events and actions through SAP Gateway.

Encapsulates a single RFC call or a Web service operation call and consists of two or more classes, with a BOP data object (BOP DO) class for each BOP.

SAP Business Suite backend system.

Deployment of core software components IW_FND and GW_CORE on the SAP Gateway central hub system.

Resource that contains a set of entries, which are structured according to the entity type definition in the respective data model.

Structured types consisting of a list of properties but with no key. Can only exist as a property of a containing entity or as a temporary value.

Represents an OData service by bundling a set of SAP Gateway data models for a specific consumption use-case. Each data model will be reflected by one or more corresponding entity types or collections in the resulting service. Exposed as service document plus service metadata document in the OData world.

SAP Gateway design-time tool that enables a developer to create content quickly without having to write source code. The content is then available for use through SAP Gateway. There are three different content generators, Business Object Repository (BOR), Remote Function Call (RFC), and Screen Scraping (SCS).

Root entity representing a certain self-contained business object that defines a people-centric view on respective business information. The nodes of this hierarchy are called entity types.

Provides all application data of a service to the runtime.

Deployment of core software components IW_FND and GW_CORE on the SAP Business Suite backend system.

Entities are grouped in entity sets (for example, customers is a set of customer entity type instances)

OData-specific. An entity is an instance of an <EntityType>. It has a unique identity, independent existence, and forms the operational unit of consistency. An <EntityType> has a name, a payload consisting of one or more declared properties and a <Key> that describes the set of properties whose values uniquely identify an entity within an entity set.

Set of concepts that describe the structure of data regardless of its stored form.

Application-specific component that provides business events. SAP Gateway converts these events in OData for SAP application notifications.

Describes a service operation in an entity data model.

Programming paradigm for SAP Gateway. Infrastructure components that enable SAP Gateway content to abstract data from the exposed protocol and the business application implementation. The recommended programming paradigm for SAP Gateway is OData Channel.

SAP Gateway system.

Complete XML representation of an Entity Data Model (1:1 relation).

Provides all metadata of a service to the runtime.

Collection of data from different backend systems that is aggregated in a single service, thereby enabling a service to be made available for more than one system.

Property of an entry that represents a link from this entry to one or more related entries. A navigation property is not a structural part of the entry to which it belongs.

Programming paradigm for SAP Gateway to expose backend functionality. To use the OData Channel, you can install the software component IW_BEP on either an SAP Business Suite backend system or on the SAP Gateway system. You are no longer recommended to use SAP Gateway ODC (using the core software component IW_FND).

OData for SAP Products is a set of rules describing how to apply OData in consumption scenarios, plus a set of extensions to OData that simplify the consumption of OData services.

Develop OData services in the Service Builder to extract the data you want, when you want it, and where.

Enables quick consumption of external OData services and converts them to SAP Gateway compliant OData services.

The Open Data Protocol (OData) is a Web protocol for querying and updating data. It applies and builds upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub), and JSON to provide access to information from a variety of applications.

Used in SAP Gateway Service Builder to consolidate and store all artifacts needed to create a service and model in one place. Projects provide developers with the freedom to interrupt the service development and modeling process at any time, without being bound to runtime artifacts and without risk of losing data.

An <EntityType> can have one or more properties of the specified EDMSimpleType or ComplexType. A property can be a declared property or a dynamic property. The declared properties of an <EntityType> of <ComplexType> are defined using the <Property> element.

SAP Gateway enables people-centric applications to consume SAP Business Suite data through popular devices and platforms in an easy and standards-based fashion.

Generator for transforming ABAP dynpro screens into SAP Gateway services.

In an OData entity or a feed a self link is a link to the entity or the feed itself, for example <atom:id>.

Exposed as an OData service to be consumed by an external application (such as JavaScript-based client). Is a repository object used for routing (system aliases are assigned to a service) and authorization checks. It has a dedicated ICF node and contains one or more data models.

Is a dedicated design-time transaction, which provides a toolset for creating OData services easily and efficiently and supports the entire service development life cycle. It blends new and existing ABAP development tools in an OData-compliant modeling transaction and caters for the needs of all developers, regardless of experience and time available for service development.

Request sent to the OData service root URI or a resource path extending it.

Top-level XML representation of a consumption model (1:1 relation). It contains a list of entity sets. A document that describes the location and capabilities of one or more entity sets.

Tangible work object from a user perspective.

Entity that defines tangible work objects. A prominent entity type fulfilling additional constraints.

SAP Gateway feature (similar to the User Management capability of Business-to-Consumer (B2C) scenario) using which SAP Business Suite B2C customers can create users and manage their user profiles.