PlantScanner - SAP Service Layer icon

PlantScanner - SAP Service Layer

Interact with SAP Service Layer API
Join our community

Actions26

Overview

This node integrates with the SAP Service Layer API to retrieve, create, update, and manage various business data entities. Specifically, for the Warehouse - Get All operation, it fetches a list of warehouse records from the SAP system. Users can apply OData filters, select specific fields, expand related entities, and paginate results by skipping a number of records.

Typical use cases include:

  • Synchronizing warehouse data from SAP into other systems.
  • Reporting or analytics that require bulk warehouse information.
  • Automating workflows that depend on current warehouse details.

For example, you could retrieve all warehouses created after a certain date or only fetch warehouses with a specific code, selecting just their codes and names for a lightweight response.

Properties

Name Meaning
Filters OData filter string to narrow down the warehouses returned (e.g., WarehouseCode eq 'WH001').
Skip Number of records to skip for pagination purposes (e.g., skip the first 10 records).
Select Comma-separated list of fields to include in the response (e.g., WarehouseCode, WarehouseName).
Expand Comma-separated list of related entities to expand and include in the response (e.g., Locations).

Output

The output is an array of JSON objects representing warehouse records retrieved from SAP. Each object contains fields corresponding to the warehouse entity, filtered and selected according to the input parameters.

Example structure of one item in the output JSON array:

{
  "WarehouseCode": "WH001",
  "WarehouseName": "Main Warehouse",
  "Location": "New York",
  ...
}

If the Expand property is used, related entities will be included as nested objects or arrays within each warehouse record.

The node does not output binary data for this operation.

Dependencies

  • Requires valid credentials for the SAP Service Layer API, including URL, company database name, username, password, and optionally language.
  • Uses HTTPS requests with disabled SSL certificate verification (rejectUnauthorized: false), which may require appropriate network security considerations.
  • The node manages session authentication by logging in to SAP Service Layer and using the returned session cookie for subsequent requests.

Troubleshooting

  • Failed to get session cookie: Indicates login to SAP Service Layer failed. Verify credentials and network connectivity.
  • Operation not supported: Occurs if an unsupported operation or resource is specified. Confirm correct Resource and Operation selections.
  • OData filter syntax errors: Invalid filter strings may cause API errors. Ensure filters follow OData syntax rules.
  • Empty or incomplete responses: Check if Select or Expand fields are correctly specified; incorrect field names may result in missing data.
  • SSL issues: Since SSL verification is disabled, some environments may block connections. Adjust network or node settings accordingly.

Using the node's "Continue On Fail" option allows processing multiple items even if some fail, returning error messages in the output JSON.

Links and References

Discussion