Messages and limitations of the SAP OData connector
For operations, refer to SAP OData (the top page for operations).
Message code list of SAPODATA category
The following message codes correspond to errors that occur in SAP OData Connector.
This message code is output when an undefined error occurs.
|
Cause |
Solution |
|---|---|
|
An undefined error occurred. |
Check the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code is output when an error occurs during the execution of the OData service.
|
Cause |
Solution |
|---|---|
|
An error occurred during the execution of the OData service. |
Check the error message or the detailed information of the exception. |
Corresponding error
-
S4ODataException
This message code is output when the response status code issued during the execution of the OData service is 400 or higher.
|
Cause |
Solution |
|---|---|
|
The response status code issued during the execution of the OData service was 400 or higher. |
Check the value stored in the component variable error_response_body. |
Corresponding error
-
S4ODataResponseException
-
S4ODataServiceErrorException
This message code is output if an error occurs when metadata is obtained from the OData service.
|
Cause |
Solution |
|---|---|
|
An error occurred when metadata was obtained from the OData service. |
Check Service base URL, Service, and OData version that are set for the connection resource specified in Destination. |
Corresponding error
-
S4ODataMetadataException
-
S4ODataMetadataHttpException
This message code is output when Input data is specified for Value specification method for an entity key, but there is no value for the entity key in the input data.
|
Cause |
Solution |
|---|---|
|
A value for the entity key isn't specified in the input data. |
Specify a value for the entity key in the input data. |
Corresponding error
-
SapODataEntityKeyNotFoundException
This message code is output during the execution of the OData service if the OData version specified in the SAP S/4HANA OData connection settings is not the expected data format.
|
Cause |
Solution |
|---|---|
|
An incorrect value is entered for the input data, Service, or OData version that are set for the connection resource specified in Destination. |
Check the values entered for the input data, Service, and OData version that are set for the connection resource specified in Destination. |
Corresponding error
-
SapODataVersionMismatchException
This message code is output during the execution of the OData service if the input data contains properties that are not defined in Property List (Entity key list for GET/DELETE).
|
Cause |
Solution |
|---|---|
|
The input data contains properties that are not defined in Property List. |
Check the input data and the properties that are defined in Property List. |
Corresponding error
-
SapODataInvalidPropertyException
This message code is output during the execution of the OData service if the OData version specified in the SAP S/4HANA OData connection settings is not the expected Content-Type for the response.
|
Cause |
Solution |
|---|---|
|
An incorrect value is entered for the authentication settings, Service, or OData version that are set for the connection resource specified in Destination. |
Check the values entered for the authentication settings, Service, and OData version that are set for the connection resource specified in Destination. |
Corresponding error
-
SapODataUnexpectedContentTypeException
Exception messages of SAPODATA category
|
Exception name |
Cause |
Solution |
|
|---|---|---|---|
|
InputDataNotFoundException |
Input data isn't specified. |
Specify Input data or draw data flow. |
|
|
ResourceNotFoundException Resource definition could not be found. Name: [] |
Destination or Authentication isn't specified. |
Specify Destination or Authentication. |
|
|
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>] |
The resource definition selected in Destination or Authentication isn't found. |
Check the connection resource specified in Destination or Authentication. |
|
|
PlugInException status: 403, title: Forbidden, detail: Forbidden |
You do not have the required permissions to execute the OData service. |
Receive the permissions required to execute the OData service. = Remarks =
For details, refer to List of policies and permissions. |
|
|
InvalidPropertyConfigurationException <Property name> is not specified. |
<Property name> isn't specified. |
Specify <property name>. |
|
|
jp.co.crescoes.sapodata.exception.S4ODataException <Error message> |
An error occurred during the execution of the OData service. |
Check <error message> or the detailed information of the exception. |
|
|
jp.co.crescoes.sapodata.exception.S4ODataResponseException |
The response status code issued during the execution of the OData service was 400 or higher. |
Check the value stored in the component variable error_response_body. |
|
|
jp.co.crescoes.sapodata.exception.S4ODataServiceErrorException |
|||
|
jp.co.crescoes.sapodata.exception.S4ODataMetadataException |
An error occurred when metadata was obtained from the OData service. |
Check Service base URL, Service, and OData version that are set for the connection resource specified in Destination. |
|
|
jp.co.crescoes.sapodata.exception.S4ODataMetadataHttpException |
|||
|
SapODataEntityKeyNotFoundException Entity key <Entity key> is not found |
The entity key could not be found in the input data when Input data is selected for Entity key list/Value specification method. |
Check the input data, or select Enter directly for Entity key list/Value specification method and enter a value for Entity key list/Value. |
|
|
SapODataVersionMismatchException The root element <Root element name> is not used for OData version <OData version> |
An incorrect value is entered for the input data, Service, or OData version that are set for the connection resource specified in Destination. |
Check the values entered for the input data, Service, and OData version that are set for the connection resource specified in Destination. |
|
|
SapODataInvalidPropertyException Property <Property name> is not defined in the target entity |
The input data contains properties that are not defined in Property List. |
Check the input data and the properties that are defined in Property List. |
|
|
SapODataUnexpectedContentTypeException The Content-Type <Content-Type> is not supported for OData version <OData version> |
An incorrect value is entered for the authentication settings, Service, or OData version that are set for the connection resource specified in Destination. |
Check the values entered for the authentication settings, Service, and OData version that are set for the connection resource specified in Destination. |
|
Limitations of SAPODATA category
This connector supports the following types.
OData V2
|
Type name |
Support |
Support when used as an entity key |
|---|---|---|
|
Edm.String |
Yes |
Yes |
|
Edm.Binaly |
Yes |
No |
|
Edm.Boolean |
Yes |
|
|
Edm.Byte |
Yes |
Yes |
|
Edm.Decimal |
Yes |
|
|
Edm.Double |
Yes |
No |
|
Edm.Single |
Yes |
No |
|
Edm.Guid |
Yes |
Yes |
|
Edm.Int16 |
Yes |
Yes |
|
Edm.Int32 |
Yes |
Yes |
|
Edm.Int64 |
Yes |
Yes |
|
Edm.SByte |
Yes |
No |
|
Edm.Time |
Yes |
Yes |
|
Edm.DateTime |
Yes |
Yes |
|
Edm.DateTimeOffset |
Yes |
No |
-
Yes: Supported.
-
No: Not supported.
OData V4
|
Type name |
Support |
Support when used as an entity key |
|---|---|---|
|
Edm.String |
Yes |
Yes |
|
Edm.Binaly |
Yes |
No |
|
Edm.Boolean |
Yes |
|
|
Edm.Byte |
Yes |
Yes |
|
Edm.Date |
Yes |
Yes |
|
Edm.DateTimeOffset |
Yes |
No |
|
Edm.Decimal |
Yes |
|
|
Edm.Double |
Yes |
No |
|
Edm.Duration |
Yes |
|
|
Edm.Guid |
Yes |
Yes |
|
Edm.Int16 |
Yes |
Yes |
|
Edm.Int32 |
Yes |
Yes |
|
Edm.Int64 |
Yes |
Yes |
|
Edm.SByte |
Yes |
No |
|
Edm.Single |
Yes |
No |
|
Edm.Stream |
No |
No |
|
Edm.TimeOfDay |
Yes |
Yes |
|
Edm.Geography |
No |
No |
|
Edm.GeographyPoint |
No |
No |
|
Edm.GeographyLineString |
No |
No |
|
Edm.GeographyPolygon |
No |
No |
|
Edm.GeographyMultiPoint |
No |
No |
|
Edm.GeographyMultiLineString |
No |
No |
|
Edm.GeographyMultiPolygon |
No |
No |
|
Edm.GeographyCollection |
No |
No |
|
Edm.Geometry |
No |
No |
|
Edm.GeometryPoint |
No |
No |
|
Edm.GeometryLineString |
No |
No |
|
Edm.GeometryPolygon |
No |
No |
|
Edm.GeometryMultiPoint |
No |
No |
|
Edm.GeometryMultiLineString |
No |
No |
|
Edm.GeometryMultiPolygon |
No |
No |
|
Edm.GeometryCollection |
No |
No |
-
Yes: Supported.
-
No: Not supported.
The following shows the value formats when the data type is date type.
|
Edm.Type |
OData V2 |
OData V4 |
Example |
|---|---|---|---|
|
Edm.Time |
PT{H}H{M}M{S}S |
— |
PT14H59M15S |
|
Edm.DateTime |
yyyy-MM-dd'T'HH:mm:ss |
— |
2025-12-04T14:59:15 |
|
Edm.DateTimeOffset |
yyyy-MM-dd'T'HH:mm:ss.SSSSSSS'Z' |
yyyy-MM-dd'T'HH:mm:ss.SSSSSSS'Z' |
2025-12-04T14:59:15.0456460Z |
|
Edm.Date |
— |
yyyy-MM-dd |
2025-12-04 |
|
Edm.TimeOfDay |
— |
HH:mm:ss.SSSSSSS |
14:59:15.0456460 |
Specification limits
-
The following shows the data formats when executing the OData service API.
OData version
Data format
V2
XML
V4
JSON
-
The following shows the supported query options.
Query option
OData version
Remarks
V2
V4
$filter
Yes
Yes
$select
Yes
Yes
$top
Yes
Yes
$skip
Yes
Yes
$expand
Yes
Yes
This can be specified with Query parameter.
$orderby
Yes
Yes
This can be specified with Query parameter.
$search
No
Yes
This can be specified with Query parameter.
-
Yes: Supported.
-
No: Not supported.
-
Specification limits
-
The following shows the data formats when executing the OData service API and the Content-Type headers when making requests.
OData version
Data format
Content-Type header when making requests
V2
XML
application/atom+xml
V4
JSON
application/json
Specification limits
-
The following shows the data formats when executing the OData service API and the Content-Type headers when making requests.
OData version
Data format
Content-Type header when making requests
V2
XML
application/atom+xml
V4
JSON
application/json
Specification limits
-
The following shows the data formats when executing the OData service API and the Content-Type headers when making requests.
OData version
Data format
Content-Type header when making requests
V2
XML
application/atom+xml
V4
JSON
application/json
Specification limits
-
The following shows the data formats when executing the OData service API.
OData version
Data format
V2
XML
V4
JSON
Specification limits
-
The following shows the data formats when executing the OData service API and the Content-Type headers when making requests.
OData version
Data format
Content-Type header when making requests
V2
XML
application/atom+xml
V4
JSON
application/json