SAP S/4HANA Read Custom Query
In this article
Overview
Use this Snap to retrieve multiple data objects from an entity in SAP S/4HANA applications using custom OData queries.
Â
Prerequisites
A valid account that supports SAP S/4HANA, with appropriate access permissions. See Configuring SAP S/4HANA Accounts.
Support for Ultra Pipelines
Works in Ultra Pipelines.Â
Limitations and Known Issues
SAP S/4HANA On-Premise does not support server-side pagination. As a result, the $skiptoken used for server-side pagination is not supported.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| A document containing data that can be used to filter entities that need to be retrieved in SAP S/4HANA server. |
Output | Document |
|
| A document containing the data retrieved from an SAP S/4HANA entity. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. |
Snap Settings
Field Name | Field Type | Description | |
---|---|---|---|
Label* Default Value:Â SAP S/4HANA Read Custom Query | String | Specify a name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |
API object*  Default Value: N/A | String | Select the API that you want to access in SAP S/4HANA On-Premise instance. This drop-down list contains APIs available for the S/4HANA account configured in the Snap, each with a short description. | |
Entity*  Default Value: N/A | String/Expression/Suggestion | Select a business object (the Entity or Endpoint) for the API Object chosen above. | |
Subentity  Default Value: N/A | String/Expression/Suggestion | Specify or select a subentity corresponding to the entity chosen above. | |
Customized header   | Use this field set to add customized HTTP request headers for implementing specific HTTP requests other than the ones listed in the Using Customized Headers section of SAP S/4HANA Read Snap. Only one customized header can be specified in each row. | ||
Field name  Default Value: N/A | String | The field name of the customized HTTP request header. | |
Field value  Default Value: N/A | String | The field value for the above field in the customized HTTP request header. | |
Key parameter    | This field set enables you to specify the key parameters for a specific entity. Providing values for all key parameters in the drop-down list enables SAP S/4HANA to identify a unique record. Click + to add a new row in this table and define the values accordingly. Key parameters are NOT the same as filters which can return multiple records. To use a filter like normal select, use the parameters at the Filter records section instead. | ||
Field name  Default Value: N/A | String | Specify the reference parameter in this field. | |
Field value  Default Value: N/A | String | Specify the value for the reference parameter in this field. | |
Customized query  Default Value: N/A | String | This field enables you to enter your OData query. SAP S/4HANA APIs follow the OData 2.0 protocol. To make the query request for API calls, the API query should obey the OData 2.0 protocol rules. For more information, see OData 2.0 Documentation. | |
Raw response  Default Value: Deselected | Checkbox/Expression | Select the checkbox to write the raw response to the output as a single document. If this checkbox is deselected, the results are written as individual documents. | |
Has next  Default Value: N/A | String/Expression | Enter the expression that must be evaluated to true or false indicating if the Snap should fetch the next page or not. | |
Next URL Â Default Value:Â N/A | String/Expression | Enter an expression that must be evaluated to a URL that the Snap should use to proceed to the next page. | |
Disable datatype conversion  Default Value: Deselected | Checkbox/Expression | Select the checkbox to disable the datatype conversion for values of key parameters and filters. | |
Count  Default Value: Deselected | Checkbox/Expression | Select this checkbox to return the total number of records retrieved in the API response. No records retrieved For all entities specified with this check box selected, the Snap returns ONLY the count of records matching the the respective entity criteria and DOES NOT return any records from the SAP S/4HANA instance (for those entities). If this check box is not selected for one or more entities, records matching each entity's criteria are returned. | |
Allow empty result  Default Value: Selected | Checkbox/Expression | Select this checkbox to define whether output views can show empty result. If this checkbox is not selected, an error will be thrown when the output has no records. | |
Connection details | Use this field set to specify the connectivity parameters: timeout, retry count, and retry interval. | ||
 | TimeOut*  Default Value: 300 | Integer | Enter, in seconds, the duration for which the Snap must try to establish connection with SAP S/4HANA On-Premise instance. If the connection cannot be established within this duration, the Snap times out, writes the event to the log, and waits until the specified RetryInterval before attempting to reconnect. |
 | Maximum request attempts*  Default Value: 3 | Integer | Specify an integer value to set the maximum number of reconnection attempts that the Snap must perform, in case of connection failure or timeout. |
 | RetryInterval*  Default Value: 1 | Integer | Enter, in seconds, the duration for which the Snap must wait between two reconnection attempts, until the number of retries is reached. |
Snap Execution  Default Value: Validate & Execute | Dropdown list | Indicates how the Snap must be executed. Available options are:
|
Troubleshooting
Error | Reason | Resolution |
---|---|---|
You have an empty value in the Field name field for the Key parameter. | The Field name field must not be empty for the Key parameter. | Enter a valid Field name for the Key parameter. |
You have an empty field in the Field name/value field for the Customized header. | The Field name/value field must not be empty for the Customized header. | Enter a valid Field name/value for the Customized header. |
ResponseCode: 500; ErrorCode: SY/530;Draft 2.0 object <Service~Entity> requires selection condition on IsActiveEntity. | Draft 2.0 object <Service~Entity> requires selection condition on IsActiveEntity For backend administrators: run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736) | Add the following query into the Customized query field: $filter=IsActiveEntity eq true or $filter=IsActiveEntity eq false.  |
Empty result found. | There is no data coming back from the API call. Possible reasons:
| Select the Allow empty result check box. |
API object does not exist. | Allowed API object format is <API ID>(Description). | Locate and select an API Object from the drop-down list. |
Entity does not exist. | The entered Entity is not found in the server. | Locate and select the Entity from the drop-down list. |
Additional information
The following contents provide some helpful information to assist you while using the SAP S/4HANA Read Custom Query Snap.
Snap General Behavior
The SAP S/4HANA Read Custom Query Snap supports the following:
GET operation to read data from the SAP S/4HANA server.
OData querying operations:Â $filter (Filter records), $select (Output field selection), $orderby (Order by), $top (Output entry limit), and $skip (Output entry offset).
OData operation $count (Count check box).
Connection-failed-retry mechanism.
Client-side pagination through $top (Output entry limit) and $skip (Output entry offset) mechanisms. For more information, see Pagination.
Customized HTTP Headers. For more information, see Using Customized Headers.
Dynamic loading of API metadata with a Parent-child dependency structure. This means that you canÂ
Select an API object from the API Object field to view only entities that are related to the API object and support GET queries (read operations).
And then, select an entity to view and specify values for only read-compatible parameters related to this entity in Key parameter field.
Pagination
Client-side pagination is supported through the use of the $top (Output entry limit), and $skip (Output entry offset) OData 2.0 operations. You can add $top and $skip system parameters to the Customized query field. $skiptoken is not supported for this release. For details of OData 2.0 query operation, see OData 2.0 Documentation.
Examples
Snap Output Setting | Pagination result |
---|---|
Output entry limit: 100 |
|
Output entry offset: 50 |
|
Output entry offset: 100, and |
|
Â
Accessing Related Entities from Snap Outputs for an Entity
Records in SAP S/4HANA Read Custom Query Snap output may contain navigation properties, typically uri fields, pertaining to some entities related to the entity specified in Snap Settings.
For example, the SAP S/4HANA Read Custom Query Snap output for the ZCRM_BUPA_OData_0001 (OData Services for Business Partner) API object and the AccountCollection entity contains navigation properties (of entities) like Contacts, Addresses, Logo, Attachments.
The navigation properties can be used to access specific details of these related entities.
In the API response, the navigation property values are displayed as URLs.
You can use one of the following methods to retrieve the details of each related entity returned in the output.
Pass the value (URL) from the Snap output as input to one of the three SAP S/4HANA Read Snaps to navigate to or access details of these related entities. OR
Parse the value (URL) from the Snap output and use it as input to Service URL field of a REST Get Snap.
Both of these methods return the properties of the corresponding related entity.
Examples
Retrieve sales order data from SAP S/4HANA server
This Pipeline example demonstrates how to use a SAP S/4HANA Read Custom Query Snap to define a custom query for retrieving sales order records from the SAP S/4HANA On-Premise instance. The Snap queries the A_SalesOrder entity via API object ZAPI_SALES_ORDER_SRV_0001 (Remote API for SD Sales Order) for sales order data.
SAP S/4HANA Read Custom Query Snap
The following settings are defined for the SAP S/4HANA Read Custom Query Snap to retrieve Sales order data from the SAP S/4HANA On-Premise instance it accesses.
API object:Â ZAPI_SALES_ORDER_SRV_0001 (Remote API for SD Sales Order)Â
Entity:Â A_SalesOrder
Filter criterion: For Plant 0001 and no other filters (Plant value equals '0001' and Condition None)
A successful validation or execution of the Snap gives the following output preview.
Â
JSON Formatter Snap
A JSON Formatter Snap is connected to the SAP S/4HANA Read Custom Query Snap to read and format its output data into standard JSON format.
File Writer Snap
A File Writer Snap is connected to the JSON Formatter Snap to save/write the JSON-formatted data into a file.
Output
To view the output JSON file, you must SSH to the target directory and open the newly-created JSON file. The preview of the output JSON file can be seen below:
Downloads
See Also
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.