SAP S/4HANA
SAP S/4HANA is an ERP platform used to work with business partners, sales orders, materials, and other operational business objects through OData services.
The Flowgear SAP S/4HANA Node lets you execute supported query, create, update, and delete operations against the embedded SAP service definitions by using template-selected services and operations in a Workflow. Query responses stay provider-shaped, while create, update, and delete responses add the standard Flowgear result object inside Response.Flowgear.
Revision History
0.2.0.1 - Preserved inherited fields in designer templates when OpenAPI schemas use constraints-only allOf overlays.
0.2.0.0 - Corrected mutation payloads and defaults, added sanitized request echoes, and made OData pagination automatic.
0.1.0.0 - Completed the V2 overhaul with eager first-request startup and lazy bounded continuation.
0.0.0.20 - Aligned the V2 connector contract and public help article.
Connection
The Connection stores the SAP host, authentication settings, and request behavior used by the embedded service metadata.
| Property | Type | Description |
|---|---|---|
Host |
String | The host name or IP address of the SAP S/4HANA instance. |
Port |
String | The HTTPS port exposed by the SAP Gateway. |
Username |
String | The SAP technical or dialog user used for basic authentication. |
Password |
Masked | The password associated with the SAP user. |
Timeout (seconds) |
Integer | The timeout applied to SAP calls. |
Exclude Empty Query Parameters |
Boolean | When true, query parameters with empty values are omitted from requests. |
Setup Notes
- Confirm that the target OData services, e.g.
API_BUSINESS_PARTNERorAPI_SALES_ORDER_SRV, are activated and reachable through the SAP Gateway. - Coordinate with the SAP BASIS team to allow Flowgear outbound IP addresses and provision a user with the required permissions.
- Confirm HTTPS access to the Gateway host and port, and make sure CSRF token requests are permitted for create, update, and delete operations.
Methods
The SAP S/4HANA Node exposes separate methods for query, create, update, and delete operations.
Query
Executes a GET-based SAP S/4HANA operation.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The SAP S/4HANA Connection. |
Service |
String | The target SAP service, e.g. API_SALES_ORDER_SRV. |
OperationId |
String | The operation identifier selected from the template. |
Options |
Object | Optional route and query values for the request. |
Items |
Array | Optional request body items. Query operations usually leave this empty. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The streamed response items returned by the SAP operation. Query responses do not add Flowgear mutation defaults. |
Create
Executes a POST-based SAP S/4HANA operation.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The SAP S/4HANA Connection. |
Service |
String | The target SAP service, e.g. API_SALES_ORDER_SRV. |
OperationId |
String | The operation identifier selected from the template. |
Options |
Object | Optional route and query values for the request. |
Items |
Array | The request body items to send to the SAP operation. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The streamed response items returned by the SAP operation. Each response item includes Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request inside Response.Flowgear. |
Update
Executes a PUT- or PATCH-based SAP S/4HANA operation.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The SAP S/4HANA Connection. |
Service |
String | The target SAP service, e.g. API_SALES_ORDER_SRV. |
OperationId |
String | The operation identifier selected from the template. |
Options |
Object | Optional route and query values for the request. |
Items |
Array | The request body items to send to the SAP operation. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The streamed response items returned by the SAP operation. Each response item includes Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request inside Response.Flowgear. |
Delete
Executes a DELETE-based SAP S/4HANA operation.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The SAP S/4HANA Connection. |
Service |
String | The target SAP service, e.g. API_SALES_ORDER_SRV. |
OperationId |
String | The operation identifier selected from the template. |
Options |
Object | Optional route and query values for the request. |
Items |
Array | Optional request body items. Delete operations usually leave this empty. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The streamed response items returned by the SAP operation. Each response item includes Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request inside Response.Flowgear. |
Usage Notes
- Use the template picker to select the correct
ServiceandOperationIdcombination. - Query completes the first SAP provider request while the Node invoke is awaited. Additional input is consumed lazily as the Workflow reads the response stream.
- Create, Update, and Delete complete the first batch of up to 100 items while the Node invoke is awaited. Later batches are consumed lazily, and an empty connected input sends no provider request.
- The Node handles SAP OData continuation links internally and hides
$top,$skip,$skiptoken, and provider continuation fields from templates and emitted rows. - Mutation request echoes use
Itemswhen present andOptionsfor bodyless operations. NestedContentvalues are excluded. - CSRF tokens are requested automatically for create, update, and delete operations.
- If the first SAP query call fails, the Node surfaces that provider error instead of returning a synthetic response row.
- Set
Exclude Empty Query Parameterstotruewhen the target service rejects blank query values.
Known Issues
- Only basic authentication is supported by this Node.