For implementing the OData service, a mapping editor is provided that can be opened
using transaction SEGW.
The example below shows the mapping of the different business entity elements of the
business entities I_AIS_SalesOrderItem,
SEPM_I_SalesOrderItem and
SEPM_I_SalesOrderItemCubeResults to the corresponding properties of
the OData entity type:
Example
Figure 1:
Example of a Data Source Reference exposed through SADL (Exposure for CDS)
In the SAP Gateway Service
Builder (see Figure 1 above), the mapping editor provides the following sections for
generating OData services:
- Project tree
- Data Model tree
- Structure of the Data Source Reference service
- Exposure through SADL tree with the following levels:
- Entity types
- Complex types
- Associations
- Entity sets
- Association sets
- Function imports
- Runtime Artifacts
- Service Maintenance
- CDS View
- Icons for displaying information if analytical CDS annotations or parameters are
provided for the selected CDS view
- Exposure for CDS:
- First Level: Hierarchy of CDS views that can contain
parameters
- Second level: Associations for displaying dependencies
- Third level: Entity Sets and Association Sets for grouping entities and associations
that belong together.
- Selected: Considered for exposure
- Value Help: Defines if a value help is available
- Analytical: Defines if the entity can be used in analytical
evaluations
- Parameter: Values that are used for transferring data
- Status: Marked red in case of errors (for example, entity has been deleted)
- Description: ABAP doc that is provided for the CDS view