PlantScanner - SAP Service Layer icon

PlantScanner - SAP Service Layer

Interact with SAP Service Layer API
Join our community

Actions26

Overview

The node interacts with the SAP Service Layer API to perform various operations on different SAP resources. Specifically, for the Item resource with the Get All operation, it retrieves multiple item records from SAP based on optional filtering, selection, expansion, and pagination parameters.

This node is beneficial in scenarios where you need to integrate SAP data into workflows, such as:

  • Extracting a list of inventory items for reporting or synchronization.
  • Filtering items by specific criteria (e.g., warehouse code or creation date).
  • Selecting only certain fields to optimize data transfer.
  • Expanding related entities to get detailed linked information.

For example, you could use this node to fetch all items created after a certain date, selecting only their codes and names, and including related attachments.

Properties

Name Meaning
Filters OData filter string to limit which items are returned. Example: WarehouseCode eq 'WH001' or CreationDate ge '2024-03-20'
Skip Number of records to skip (for pagination).
Select Comma-separated list of fields to include in the response. Leave empty to get all fields. Example: ItemCode, ItemName, PurchaseItem, SalesItem
Expand Comma-separated list of related entities to expand in the response. Example: DocumentLines, Attachments2

Output

The output is an array of JSON objects representing the retrieved items. Each object contains the fields requested via the Select property or all fields if none specified. If Expand is used, related entities will be included as nested objects or arrays within each item.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "ItemCode": "A100",
    "ItemName": "Sample Item",
    "PurchaseItem": true,
    "SalesItem": false,
    "Attachments2": [
      {
        "AttachmentEntry": 123,
        "FileName": "specs.pdf"
      }
    ]
  },
  ...
]

Dependencies

  • Requires connection credentials to the SAP Service Layer API, including URL, company database, username, password, and optionally language.
  • Uses HTTPS requests with disabled SSL certificate verification (rejectUnauthorized: false), which may require appropriate network security considerations.
  • The node logs in to SAP Service Layer at execution start to obtain a session cookie for authentication.

Troubleshooting

  • Failed to get session cookie: Indicates login to SAP Service Layer failed. Check credentials and network connectivity.
  • Operation not supported: Occurs if an unsupported operation or resource is selected. Verify correct Resource and Operation settings.
  • OData filter syntax errors: Invalid filter strings can cause request failures. Ensure filters follow OData syntax rules.
  • Empty or incomplete results: May happen if filters exclude all records or if select/expand fields are incorrect. Adjust parameters accordingly.
  • SSL issues: Since SSL verification is disabled, some environments may block connections. Consider enabling proper certificates or adjusting network policies.

Links and References

Discussion