Introduction
This plugin would allow SAP ECC enterprise users to specify one of the Inventory Management data sources as source in Cloud Data Fusion. Typical pipeline scenario would include specifying one of the data sources as source (under Sources plugins) and BigQuery as sink. For the sake of simplicity, this document will cover one data source (Material Movements from Inventory Management - 2LIS_03_BF).
User Experience and Configuration
- SAP ECC Setup
SAP ECC users log into SAP Gateway Service Builder (segw) to create and expose the data source as SAP OData service. SAP has published following articles around this step:
User creates OData service for the data source (2LIS_03_BF). Output is RESTful OData service that can be accessed by Cloud Data Fusion.
User can also use SAP Netweaver Gateway client to test the service (with HTTP request and response)
- Cloud Data Fusion - Source configuration
- Source Data Types Mapping
User would log into their CDF instance and click on “Hub”.
Under “Plugins” section, user should be able to find “SAP ECC Source”.
This integration would provide a single JAR files for SAP ECC data sources. User would upload the JAR file and this would deploy the plugin using the JAR file.
Once uploaded, the user is prompted to provide following configuration information. Please note that all the fields below should be macro enabled.
Label | Label Description | User Widget |
|---|---|---|
Name | Name of the source | Textbox |
Description | Description of the service and the data source it is going to connect to (e.g. 2LIS_03_BF) | Textbox |
OData service URL | OData service URL exposed via SAP ECC | Textbox |
User name | Login user name for authenticating API call | Textbox |
Password | Password for authenticating API call | Textbox |
The same dialog will have “Test connection” button to allow users to validate a validation API call. If failed, the error message will be presented to the user in red next to “Test connection” button.
Once connection has been established successfully to this OData service, it can be used as a source for creating data pipelines using Cloud Data Fusion.
- Cloud Data Fusion - Sink setup (e.g. BigQuery for this specific example)
User would create a BigQuery table inside a dataset where the data extracted through OData service API will be ingested.
User needs to ensure that the table schema includes data types that have been mapped as part of this integration (see below for integration considerations section for more details)
Integration considerations
Data type mismatch - OData output has data types (section 6) different than the data types available in BigQuery. Some sort of data type conversion needs to happen before the extracted data can be ingested into BigQuery. Below is the suggested mapping of OData data types to CDAP schema data types:
OData data type | CDAP schema data type |
|---|---|
Edm.Binary | Schema.Type.String |
Edm.Boolean | Schema.Type.Bool |
Edm.Byte | Schema.Type.Byte |
Edm.DateTime | Schema.Type.DateTime |
Edm.Decimal | Schema.Type.Float |
Edm.Double | Schema.Type.Double |
Edm.Single | Schema.Type.Float |
Edm.Guid | Schema.Type.String |
Edm.Int16 | Schema.Type.Int |
Edm.Int32 | Schema.Type.Int |
Edm.Int64 | Schema.Type.Long |
Edm.SByte | Schema.Type.Bytes |
Edm.String | Schema.Type.String |
Edm.Time | Schema.Type.Time |
Edm.DateTimeOffset | Schema.Type.Timestamp |
Field Level Lineage (FLL): Field level lineage should be available for all the sources and sinks.
OData Service API
Service Metadata Document
Describes the structure of all resources in the service.
Note: service metadata document has no JSON representation.
GET: http://vhcalnplci.dummy.nodomain:8000/sap/opu/odata/SAP/ZGW100_XX_S3_SRV/$metadata
Response:
Service Document
Lists the available top-level resources.
GET: http://vhcalnplci.dummy.nodomain:8000/sap/opu/odata/SAP/ZGW100_XX_S2_SRV/
Response:
GET: http://vhcalnplci.dummy.nodomain:8000/sap/opu/odata/SAP/ZGW100_XX_S2_SRV/?$format=json
Response:
Requesting EntitySet
GET: http://vhcalnplci.dummy.nodomain:8000/sap/opu/odata/SAP/ZGW100_XX_S3_SRV/SalesOrderSet
Response:
Response:
Querying Data
Response:
For more examples, please, refer: https://www.odata.org/odata-services/
SAP ECC Source Plugin
Design
The suggestion is to use Apache Olingo as Client Library. Both OData v2 and v4 are supported by the SAP Gateway, so it could require to use Olingo v2 and Olingo v4.
Source Properties
| Section | User Facing Name | Widget Type | Description | Constraints |
|---|---|---|---|---|
| General | Label | textbox | Label for UI. | |
| Reference Name | textbox | Uniquely identified name for lineage. | ||
| OData Service URL | textbox | URL of the SAP ECC OData service. The URL must end with an external service name (e.g., http://eccsvrname:8000/sap/opu/odata/sap/zgw100_dd02l_so_srv/). | Required | |
| Resource Path | textbox | Path of the SAP ECC OData entity. For example:
| Required | |
| Query Options | keyvalue | OData query options to filter the data. For example:
The plugin copies data from the combined URL: For more information, see OData URL components. | ||
| Include Metadata Annotations | toggle | Whether the plugin should read SAP metadata annotations and include them to each record. | ||
| Credentials | Username | textbox | Username for basic authentication. | |
| Password | password | Password for basic authentication. | ||
| Output Schema | schema | Specifies the schema of the entries. |
OData V2 Data Types Mapping
Types can be mapped as follows, according to the org.apache.olingo.odata2.api.edm.EdmSimpleType and OData Primitive Data Types(section 6):
EDM primitive type | CDAP Schema Data Type | Comment |
|---|---|---|
| Edm.Binary | bytes | |
Edm.Boolean | boolean | |
Edm.Byte | int | Unsigned 8-bit integer value |
Edm.DateTime | timestamp | Datetime in the following format: 'yyyy-mm-ddThh:mm[:ss[.fffffff]]' |
Edm.Decimal | decimal | |
Edm.Double | double | |
Edm.Single | float | |
Edm.Guid | string | |
Edm.Int16 | int | |
Edm.Int32 | int | |
Edm.Int64 | long | |
Edm.SByte | int | Represents a signed 8-bit integer value |
Edm.String | string | |
Edm.Time | time | Represents the time of day with values ranging from 0:00:00.x to 23:59:59.y, where x and y depend upon the precision |
Edm.DateTimeOffset | string | Represents date and time as an Offset in minutes from GMT, with values ranging from 12:00:00 midnight, January 1, 1753 A.D. through 11:59:59 P.M, December 9999 A.D Example 1: 2002-10-10T17:00:00Z Mapped to string to avoid timezone information loss. |
OData V4 Data Types Mapping
Types can be mapped as follows, according to the org.apache.olingo.commons.api.edm.EdmPrimitiveType and OData CSDL Primitive Types:
EDM primitive type | CDAP Schema Data Type | JSON | XML | Comment |
|---|---|---|---|---|
| Edm.Binary | bytes | |||
Edm.Boolean | boolean | |||
Edm.Byte | int | Unsigned 8-bit integer value | ||
Edm.Date | timestamp | Date without a time-zone offset | ||
| Edm.DateTimeOffset | string | Represents date and time as an Offset in minutes from GMT, with values ranging from 12:00:00 midnight, January 1, 1753 A.D. through 11:59:59 P.M, December 9999 A.D Example 1: 2002-10-10T17:00:00Z Mapped to string to avoid timezone information loss. | ||
Edm.Decimal | decimal | |||
Edm.Double | double | |||
| Edm.Duration | string | "Duration@odata.type": "#Duration", "Duration": "P12DT23H59M59.999999999999S", | <d:Duration m:type="Edm.Duration">P12DT23H59M59.999999999999S</d:Duration> | Signed duration in days, hours, minutes, and (sub)seconds. |
Edm.Guid | string | |||
Edm.Int16 | int | |||
Edm.Int32 | int | |||
Edm.Int64 | long | |||
Edm.SByte | int | Represents a signed 8-bit integer value | ||
| Edm.Single | float | |||
| Edm.Stream | record | "Stream@odata.mediaReadLink": "http://placehold.it/10x10.jpg?read", "Stream@odata.mediaEditLink": "http://placehold.it/10x10.jpg?edit", "Stream@odata.mediaContentType": "image/jpeg", "Stream@odata.mediaEtag": "W/\"####\"", "Stream": "" | <link rel="http://docs.oasis-open.org/odata/ns/edit-media/Stream" title="Stream" href="AllDataTypes(3)/Stream"/> | Binary data stream. Olingo client maps this data type to java.net.URI. The proposal is to map this data type to CDAP record that corresponds to the JSON representation. |
Edm.String | string | |||
Edm.TimeOfDay | time | Clock time 00:00-23:59:59.999999999999 | ||
| Edm.Geography | - | Abstract base type for all Geography types. | ||
| Edm.GeographyPoint | record | "GeographyPoint": {
"type": "Point",
"coordinates": [142.1, 64.1]
}
| <d:GeographyPoint m:type="GeographyPoint">
<gml:Point gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:pos>15 161.8</gml:pos>
</gml:Point>
</d:GeographyPoint>
| A point in a round-earth coordinate system |
| Edm.GeographyLineString | record | "GeographyLineString": {
"type": "LineString",
"coordinates": [
[100.0, 0.0],
[101.0, 1.0]
]
}
| <d:GeographyLineString m:type="Edm.GeographyLineString">
<gml:LineString gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:pos>10 10</gml:pos>
<gml:pos>20 20</gml:pos>
<gml:pos>40 10</gml:pos>
</gml:LineString>
</d:GeographyLineString>
| Line string in a round-earth coordinate system |
| Edm.GeographyPolygon | record | "GeographyPolygon": {
"type": "Polygon",
"coordinates": [
[ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ],
[ [100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2, 0.2] ]
]
}
| <d:GeographyPolygon m:type="Edm.GeographyPolygon"> <gml:Polygon gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326"/> <gml:pos>10 10</gml:pos> <gml:pos>10 40</gml:pos> <gml:pos>40 10</gml:pos> <gml:pos>40 40</gml:pos> </d:GeographyPolygon> | Polygon in a round-earth coordinate system |
| Edm.GeographyMultiPoint | record | "GeographyMultiPoint": {
"type": "MultiPoint",
"coordinates": [
[ 2.5, 3.125],
[3.5, 4.125],
[4.5, 5.125]
]
}
| <d:GeographyMultiPoint m:type="Edm.GeographyMultiPoint">
<gml:MultiPoint gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:pointMembers>
<gml:Point>
<gml:pos>47.38 -122.7</gml:pos>
</gml:Point>
</gml:pointMembers>
</gml:MultiPoint>
</d:GeographyMultiPoint>
| Collection of points in a round-earth coordinate system |
| Edm.GeographyMultiLineString | record | "GeographyMultiLineString": {
"type": "MultiLineString",
"coordinates": [
[[1.0,1.0],[2.0,2.0],[3.0,3.0],[4.0,4.0],[5.0,5.0]],
[[99.5,101.5],[150.0,151.25]]
]
}
| <d:GeographyMultiLineString m:type="Edm.GeographyMultiLineString">
<gml:MultiCurve gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:curveMembers>
<gml:LineString>
<gml:pos>10.5 10.5</gml:pos>
<gml:pos>20.5 20.5</gml:pos>
<gml:pos>40.5 10.5</gml:pos>
</gml:LineString>
<gml:LineString>
<gml:pos>40.5 40.5</gml:pos>
<gml:pos>30.5 30.5</gml:pos>
<gml:pos>20.5 40.5</gml:pos>
<gml:pos>10.5 30.5</gml:pos>
</gml:LineString>
</gml:curveMembers>
</gml:MultiCurve>
</d:GeographyMultiLineString>
| Collection of line strings in a round-earth coordinate system |
| Edm.GeographyMultiPolygon | record | "GeographyMultiPolygon": {
"type": "MultiPolygon",
"coordinates": [
[
[[0.0,0.0],[3.0,0.0],[3.0,3.0],[0.0,3.0],[0.0,0.0]],
[[1.0,1.0],[1.0,2.0],[2.0,2.0],[2.0,1.0],[1.0,1.0]]],
[
[[0.0,0.0],[30.0,0.0],[0.0,30.0],[0.0,0.0]],
[[10.0,10.0],[10.0,20.0],[20.0,10.0],[10.0,10.0]]
]
]
}
| <d:GeographyMultiPolygon m:type="Edm.GeographyMultiPolygon">
<gml:MultiSurface
gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:surfaceMembers>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>
<gml:pos>40 40</gml:pos>
<gml:pos>45 20</gml:pos>
<gml:pos>30 45</gml:pos>
<gml:pos>40 40</gml:pos>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>
<gml:pos>35 20</gml:pos>
<gml:pos>20 45</gml:pos>
<gml:pos>5 30</gml:pos>
<gml:pos>10 10</gml:pos>
<gml:pos>30 10</gml:pos>
<gml:pos>35 20</gml:pos>
</gml:LinearRing>
</gml:exterior>
<gml:interior>
<gml:LinearRing>
<gml:pos>20 30</gml:pos>
<gml:pos>25 20</gml:pos>
<gml:pos>15 20</gml:pos>
<gml:pos>20 30</gml:pos>
</gml:LinearRing>
</gml:interior>
</gml:Polygon>
</gml:surfaceMembers>
</gml:MultiSurface>
</d:GeographyMultiPolygon>
| Collection of polygons in a round-earth coordinate system |
| Edm.GeographyCollection | record | "GeographyCollection@odata.type": "#GeographyCollection",
"GeographyCollection": {
"type": "GeometryCollection",
"geometries": [
{ "type": "Point",
"coordinates": [100.0, 0.0]
},
{ "type": "LineString",
"coordinates": [ [101.0, 0.0], [102.0, 1.0] ]
}
]
}
| <d:GeographyCollection m:type="Edm.GeographyCollection">
<gml:MultiGeometry
gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326" />
<gml:LineString gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:pos>10 10</gml:pos>
<gml:pos>20 20</gml:pos>
<gml:pos>40 10</gml:pos>
</gml:LineString>
<gml:Polygon gml:srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
<gml:pos>10 10</gml:pos>
<gml:pos>10 40</gml:pos>
<gml:pos>40 10</gml:pos>
<gml:pos>40 40</gml:pos>
</gml:Polygon>
</d:GeographyCollection>
| Collection of arbitrary Geography values. Note, that JSON representation contains type control information (`@odata.type`). Otherwise, Olingo client reports invalid value type for `Edm.GeometryCollection` and `Edm.GeographyCollection` JSON values. Since metadata does not contain component info, the proposal is to map this data type to CDAP record with the following fields:
|
| Edm.Geometry | - | Abstract base type for all Geometry types | ||
| Edm.GeometryPoint | record | Similar to Edm.GeographyPoint | Similar to Edm.GeographyPoint | Point in a flat-earth coordinate system |
| Edm.GeometryLineString | record | Similar to Edm.GeographyLineString | Similar to Edm.GeographyLineString | Line string in a flat-earth coordinate system |
| Edm.GeometryPolygon | record | Similar to Edm.GeographyPolygon | Similar to Edm.GeographyPolygon | Polygon in a flat-earth coordinate system |
| Edm.GeometryMultiPoint | record | Similar to Edm.GeographyMultiPoint | Similar to Edm.GeographyMultiPoint | Collection of points in a flat-earth coordinate system |
| Edm.GeometryMultiLineString | record | Similar to Edm.GeographyMultiLineString | Similar to Edm.GeographyMultiLineString | Collection of line strings in a flat-earth coordinate system |
| Edm.GeometryMultiPolygon | record | Similar to Edm.GeographyMultiPolygon | Similar to Edm.GeographyMultiPolygon | Collection of polygons in a flat-earth coordinate system |
| Edm.GeometryCollection | record | Similar to Edm.GeographyCollection | Similar to Edm.GeographyCollection | Collection of arbitrary Geometry values |
OData V4 Metadata Annotations Mapping
An annotation applies a term to a model element and defines how to calculate a value for the term application. The value of an annotation is specified as an annotation expression, which is either a constant expression representing a constant value or a dynamic expression.
"Include Metadata Annotations" configuration property indicates whether the plugin should read metadata annotations and include them to each record. In this case, each property will be mapped to a CDAP 'record' with exactly two fields "value" and "metadata-annotations". OData V4 metadata annotations are mapped to a record of the following fields:
- term - a simple identifier, such as "UI.DisplayName" or "Core.Description", etc.
- qualifier - a term can be applied multiple times to the same model element by providing a qualifier to distinguish the annotations.
- expression - CDAP record that corresponds to a constant expression or a dynamic expression. Please, refer the table below for expressions mapping.
- annotations - CDAP record that corresponds to nested annotations. Please, refer examples below for nested annotations mapping.
OData V4 Annotation Expression Mapping
EDM expression | Type | Example | CDAP record schema |
|---|---|---|---|
| Binary | constant | <Annotation Term="org.example.display.Thumbnail"> <Binary>T0RhdGE</Binary> </Annotation> |
|
| Bool | constant | <Annotation Term="org.example.display.ReadOnly"> <Bool>true</Bool> </Annotation> |
|
| Date | constant | <Annotation Term="org.example.vCard.birthDay"> <Date>2000-01-01</Date> </Annotation> |
|
| DateTimeOffset | constant | <Annotation Term="org.example.display.LastUpdated"> <DateTimeOffset>2000-01-01T16:00:00.000-09:00</DateTimeOffset> </Annotation> |
|
| Decimal | constant | <Annotation Term="org.example.display.Width"> <Decimal>3.14</Decimal> </Annotation> |
|
| Duration | constant | <Annotation Term="org.example.task.duration"> <Duration>P11DT23H59M59.999999999999S</Duration> </Annotation> |
|
| EnumMember | constant | <Annotation Term="org.example.HasPattern"> <EnumMember>org.example.Pattern/Red</EnumMember> </Annotation> |
|
| Float | constant | <Annotation Term="org.example.display.Width"> <Float>3.14</Float> </Annotation> |
|
| Guid | constant | <Annotation Term="org.example.display.Id"> <Guid>21EC2020-3AEA-1069-A2DD-08002B30309D</Guid> </Annotation> |
|
| Int | constant | <Annotation Term="org.example.display.Width"> <Int>42</Int> </Annotation> |
|
| String | constant | <Annotation Term="org.example.display.DisplayName"> <String>Product Catalog</String> </Annotation> |
|
| TimeOfDay | constant | <Annotation Term="org.example.display.EndTime"> <TimeOfDay>21:45:00</TimeOfDay> </Annotation> |
|
| Path | dynamic | <Annotation Term="org.example.display.DisplayName"> <Path>@vCard.Address#work/FullName</Path> </Annotation> |
|
| AnnotationPath | dynamic | <Annotation Term="UI.CollectionFacet" Qualifier="Contacts">
<Collection>
<AnnotationPath>Supplier/@Communication.Contact</AnnotationPath>
<AnnotationPath>Customer/@Communication.Contact</AnnotationPath>
</Collection>
</Annotation>
|
|
| LabeledElementReference | dynamic | <Annotation Term="org.example.display.DisplayName"> <LabeledElementReference>Model.CustomerFirstName</LabeledElementReference> </Annotation> |
|
| Null | dynamic | <Annotation Term="@UI.Address">
<Null>
<Annotation Term="self.Reason" String="Private" />
</Null>
</Annotation>
|
|
| NavigationPropertyPath | dynamic | <Annotation Term="Capabilities.UpdateRestrictions">
<Record>
<PropertyValue Property="NonUpdatableNavigationProperties">
<Collection>
<NavigationPropertyPath>Supplier</NavigationPropertyPath>
<NavigationPropertyPath>Category</NavigationPropertyPath>
</Collection>
</PropertyValue>
</Record>
</Annotation>
|
|
| PropertyPath | dynamic | <Annotation Term="Capabilities.UpdateRestrictions">
<Record>
<PropertyValue Property="NonUpdatableProperties">
<Collection>
<PropertyPath>CreatedAt</PropertyPath>
<PropertyPath>ChangedAt</PropertyPath>
</Collection>
</PropertyValue>
</Record>
</Annotation>
|
|
| And | dynamic | <Annotation Term="Core.Description"> <And> <Path>BooleanProperty1</Path> <Path>BooleanProperty2</Path> </And> </Annotation> |
|
| Or | dynamic | Annotation Term="Core.Description"> <Or> <Path>BooleanProperty1</Path> <Path>BooleanProperty2</Path> </Or> </Annotation> |
|
| Eq | dynamic | <Annotation Term="Core.Description"> <Eq> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Eq> </Annotation> |
|
| Ne | dynamic | <Annotation Term="Core.Description"> <Ne> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Ne> </Annotation> |
|
| Gt | dynamic | <Annotation Term="Core.Description"> <Gt> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Gt> </Annotation> |
|
| Ge | dynamic | <Annotation Term="Core.Description"> <Ge> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Ge> </Annotation> |
|
| Lt | dynamic | <Annotation Term="Core.Description"> <Lt> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Lt> </Annotation> |
|
| Le | dynamic | <Annotation Term="Core.Description"> <Le> <Path>SomeProperty1</Path> <Path>SomeProperty2</Path> </Le> </Annotation> |
|
| Not | dynamic | <Annotation Term="Core.Description"> <Not> <Path>SomeProperty</Path> </Not> </Annotation> |
|
| Apply | dynamic | <Annotation Term="Core.Description"> <Apply Function="odata.concat"> <String>Product:</String> <!-- AllDataTypesEntity/String --> <Path>SomeProperty1</Path> <String>(</String> <!-- AllDataTypesEntity/Int16 --> <Path>SomeProperty2</Path> <String>)</String> </Apply> </Annotation> |
Note: the proposal is to use the parameter index as a prefix for field name to avoid conflicts. In this case, parameters record will be a record of the following fields:
|
| Cast | dynamic | <Annotation Term="Core.Description"> <Cast Type="Edm.String"> <Path>SomeProperty</Path> </Cast> </Annotation> |
|
| Collection | dynamic | <Annotation Term="Core.Description"> <Collection> <String>Product</String> <String>Supplier</String> <String>Customer</String> </Collection> </Annotation> |
|
| If | dynamic | <Annotation Term="Core.Description"> <If> <Path>SomeBooleanProperty</Path> <String>Female</String> <String>Male</String> </If> </Annotation> |
|
| IsOf | dynamic | <Annotation Term="Core.Description"> <IsOf Type="Edm.Boolean"> <Path>SomeProperty</Path> </IsOf> </Annotation> |
|
| LabeledElement | dynamic | <Annotation Term="Core.Description"> <LabeledElement Name="CustomerFirstName"> <Path>SomeProperty</Path> </LabeledElement> </Annotation> |
|
| Record | dynamic | <Annotation Term="Core.Description"> <Record> <Annotation Term="Core.Description" String="Annotation on record"/> <PropertyValue Property="GivenName" Path="SomeProperty"/> <PropertyValue Property="Age" Path="Byte"/> </Record> </Annotation> |
|
| UrlRef | dynamic | <Annotation Term="Core.LongDescription"> <UrlRef><String>http://host/wiki/HowToUse</String></UrlRef> </Annotation> |
|
Notes
- An edm:Annotation element MAY contain edm:Annotation elements that annotate the annotation.
- The edm:Annotations element is used to apply a group of annotations to a single model element. These are annotations with External Targeting.
Complex Types Mapping
Both OData V2 and V4 support complex types. Complex types are keyless nominal structured types. The lack of a key means that instances of complex types cannot be referenced, created, updated or deleted independently of an entity type. Complex types allow entity models to group properties into common structures.
The example below demonstrates the definition of several complex types in the service metadata document:
<?xml version="1.0" encoding="utf-8"?>
<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
<edmx:DataServices>
<Schema Namespace="TestService" xmlns="http://docs.oasis-open.org/odata/ns/edm" Alias="self">
<ComplexType Name="City">
<Property Name="CountryRegion" Type="Edm.String" Nullable="false"/>
<Property Name="Name" Type="Edm.String" Nullable="false"/>
<Property Name="Region" Type="Edm.String" Nullable="false"/>
</ComplexType>
<ComplexType Name="Location" OpenType="true">
<Property Name="Address" Type="Edm.String" Nullable="false"/>
<Property Name="City" Type="TestService.City" Nullable="false"/>
</ComplexType>
<ComplexType Name="HomeAddress" BaseType="TestService.Location">
<Property Name="FamilyName" Type="Edm.String"/>
</ComplexType>
...
<EntityType Name="AllDataTypesEntity">
...
<Property Name="Address" Type="TestService.Location" Nullable="false"/>
<Property Name="HomeAddress" Type="TestService.HomeAddress" Nullable="false"/>
<Property Name="Size" Type="TestService.Size" Nullable="false"/>
</EntityType>
...
</Schema>
</edmx:DataServices>
</edmx:Edmx>
Properties of these types are mapped to a record with corresponding fields and each of them is mapped according to it's Edm type.
References
OData service
SAP Netweaver Gateway
Overview - https://blogs.sap.com/2013/01/24/a-simple-overview-on-sap-netweaver-gateway/
SAP Netweaver Gtw and OData Tutorials: https://sapyard.com/tutorials-on-odata-sap-netweaver-gateway/
Microsoft Data Factory - SAP ECC Connector
Plugin Type
- Batch Source
- Batch Sink
- Real-time Source
- Real-time Sink
- Action
- Post-Run Action
- Aggregate
- Join
- Spark Model
- Spark Compute